Using script : With the IHS installation, The configurewebserver1.bat is created in the plugin bin folder of the IHS installation. Copy the script to the remote server deployment manager bin and run the script. This script will create the webserver1 configuration. Once the script is run, Restart the DMGR and access the console, You should be able to see the webserver1 definition created.
Manual Creation:
Login to the WebSphere Application server console and navigate to the webservers section.
Click on new -> Choose the server node and add a server name -> I have given webserver1 -> Type is IBM HTTP Server -> Next
Next
Enter the IHS server details
Finish
IHS and WAS on same Server: (Standalone Node)
Now click on the check box of the webserver1, Generate Plugin and Propagate Plugin. This is copy the plugin.xml to the webserver. Now the communication between the websphere application server and the webserver is successful.
IHS on remote server: (Remote Node)
When you have the IHS and WAS on different server, Then remote server management comes into picture. Ensure the firewall port is open between the two servers so that the communication doesn't break during the generation and propagation of plugin. Click on remote server management and specify the userid and password for the IHS. These credentials were specified when you are installing the IHS webserver.
Test:
Access any of the sample deployed applications via IHS url
ex: WAS URL : http://localhost:9080/PlantsByWebsphere
Now IHS URL : http://localhost/PlantsByWebsphere - Here you are able to access the application via IHS.
0 comments:
Post a Comment