IHS + WAS + Plugin

Install IHS
==> Put server name as the identification of the "web server name" which will be used for "folder name" of plugin at IHS and WAS, and also log name as unique identity.
==> Put username and password, as it will be used for registering to Http admin.
==> Http admin is a service in windows, but it isnt accessible from browser.
==> Http server is another service created by the installer.

As i remember we dont need to install plugin, since it is along with the IHS installer,
and during the ihs instalation it asked where the WAS directory is.

But incase plugin wasnt there, just install it reside in IHS installer folder called plugins.


On WAS admin console:
==> go to servers = web servers = new
==> Put servername as same as the "web server name" above, as it is a folder name in the ihs plugin config dir.
==> Put hostname as the hostname/DNS name of where the IHS server is.
==> Put the "service name" of IHS correctly as in services.msc (in oder to be able restart webserver using was admin console)


At this point, the plugin is:
1. in IHS is general plugin of WAS default instalation (context root : snoop, hello, etc)
D:\Program Files\IBM\HTTPServer\Plugins\config\webservername

2. in WAS, plugin not available yet.

At WAS console, u must generate plugin (click the webserver and button will be available):
It will be in D:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\win2003Node01Cell\nodes\win2003Node01\servers\"webservername you insert when adding webserver"\

* That folder was created when you add new web server, plugin file will be created under it
* This plugin is only for default_host VH and others if any, but not for the admin_host VH
* admin_host VH is VirtualHost where /ibm/console is (WAS admin console login)
* default_host VH is VirtualHost where /snoop, /hello, /UTC (in my case) are.
* notice there is server.xml there, there you can see the webserver username and decoded password.
* you can decode the WAS user's password by using www.sysman.nl/wasdecoder


At WAS console, u must propagate plugin:
WAS will copy above plugin to IHS plugin - webserver name folder.

Restart the IBM Http service.

Now, u have successfully made it.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

For redirecting/loadbalancing the WAS admin console using plugin, i think you must edit it manually the plugin-cfg.xml.

Allowing Web servers to access the administrative console
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_configACAccess.html

Procedure

1. Use the administrative console to change the admin_host virtual host group to include the Web server port (80 by default).
1. Click Environment > Virtual Host > admin_host > Host Aliases > New.

The default port that displays is 80, unless you specify a different port during profile creation.
2. Specify the IP address, or the name of the machine that is hosting the HTTP server.

For example, if you installed a WebSphere Application Server product on a machine that is named waslwaj.rtp.ibm.com, specify the name in this field.
2. Click Apply > Save.
3. Stop and restart the application server.

For example, to access the administrative console of a stand-alone application server, stop and restart the server1 process.
To stop server1, open a command window and navigate to the profile_root /bin directory. Then issue the following command:

./stopServer.sh server1

After receiving the following message, you can restart the application server:

Server server1 stop completed.

To start the application server, issue the following command:

./startServer.sh server1

When you receive a message that is similar to the following message, the server1 process is running:

Server server1 open for e-business; process id is 1719

4. Stop and restart a deployment manager.

For example, to access the administrative console of a deployment manager, stop and restart the deployment manager.
To stop the deployment manager, open a command window and navigate to the profile_root /bin directory. Then issue this command:

./stopManager.sh

Then issue the following command to stop the deployment manager:

./stopManager.sh

After receiving the following message, you can restart the deployment manager:

Server dmgr stop completed.

To start the deployment manager, issue the following command:

./startManager.sh

When you receive a message that is similar to the following message, the deployment manager is running:

Server dmgr open for e-business; process id is 1720

5. Edit the plugin-cfg.xml file to include the following entries:






...
...
...









...
...
...

AffinityURLIdentifier="jsessionid" Name="/ibm/console/*"/>

UriGroup="admin_host_server1_SERVER1HOSTserver1_Cluster_URIs" VirtualHostGroup="admin_host"/>


If your HTTP server has an HTTP port other than 80, add an entry to the VirtualHostGroup:



The port variable is your HTTP server port.