IBM WAS v6.1 Administration Unit 4 Web server Start/Stop & custom plugin-cfg.xml

IBM HTTP Server administration server

There is no difference in previous versions of IBM HTTP Server on UNIX platforms. The functionality in V6 has been extended to Windows platforms.

* IBM HTTP Server administration server runs as a separate instance of IBM HTTP Server
* Admin component for IBM HTTP Server V6 includes:
IBM HTTP Server admin configuration file (admin.conf)
Default port for the IBM HTTP Server admin server is 8080
* IBM HTTP Server admin authentication password file (htpasswd.admin)
Initially blank, which prohibits access to IBM HTTP Server admin
Administrator updates IBM HTTP Server admin password file using: htpasswd -cm ..\conf\admin.passwd
*To start/stop the administration server
/bin/adminctl start
/bin/adminctl stop
Or use Windows service for Windows platforms

Web server custom plugin-cfg.xml

Web server definitions are created to allow the mapping of J2EE enterprise applications to specific Web servers.
* Can be done through the administrative console
* Alternately use the script generated during the installation of the plug0in which can automate the mapping of all the applications to the Web server.
configure.sh(bat) in /bin as in C:\...\configurewebserver002.bat

Mapping the applications to specific Web servers will cause the custom plugin-cfg.xml file for only those Web servers to include the information for those applications
* Web servers target specific applications running in a cell
* Automatically generated by the deployment manager

Managing plugin-cfg.xml files

Is performed from the console /Web Servers/webserver_name/plug-in properties

* plugin-cfg.xml files are automatically generated and propagated
This behaviour is the default, but can be changed
This behaviour is configurable through the console

* plugin-cfg.xml can be generic to a cell or custom to Web server
Generating a cell generic plugin-cfg.xml file
Use the command line script \bin\GenPluginCfg.bat
Not available through the console

Generating a Web server custom plugin-cfg.xml
* Use the administrative console
Need to map applications to Web servers
Can customize each Web server's plug-in settings

Managing Web server plug-in properties
* Each Web server can have customized plugin-cfg settings (not just application mappings)

NOTE: If you ever generate a new plugin you must stop/start