Why and when to perform this task
The WebSphere HTTP Plug-in for z/OS ships as part of the WebSphere Application Server for z/OS product. To use this plug-in, you must have an IBM HTTP Server for z/OS or OS/390 Version 5.3 configured as part of a z/OS system.
After the application server, the HTTP Server and the plug-in are properly configured:
Note: The HTTP Server interprets a blank in a directive specification as a delimiter and a number sign (#) as the beginning of a comment that should be ignored. Therefore, if you need to use a blank or number sign in a directive, you must include a backslash (\) before the blank or number sign to enable the HTTP Server to correctly process the directive.
To Install and configure the WebSphere HTTP Plug-in for z/OS:
Steps for this task
Note: Whenever service is applied to the WebSphere Application Server for z/OS product, you must FTP a new copy of the WebSphere HTTP Plug-in for z/OS from the install_root/bin directory.
chmod 777 ihs390WAS50Plugin_http.so extattr +p ihs390WAS50Plugin_http.so
Example: The ServerInit directive is split here for printing purposes. In the actual httpd.conf file, enter this directive on a single line.
ServerInit /http_plugin_dir/bin/ ihs390WAS50Plugin_http.so:init_exit /http_plugin_conf/ plugin-cfg.xml ServerTerm /http_plugin_dir/ihs390WAS50Plugin_http.so:term_exit
Specify the full path to where you put the plugin-cfg.xml file for the variable http_plugin_conf.
The value you specify for the variable http_plugin_dir depends on whether or not the HTTP Server is on the same LPAR as the WebSphere Application Server.
Note: If v5.0.2 APAR PK02800 or v5.1.0 APAR PK02801 is applied to the WebSphere Application Server for z/OS environment, the value for the http_plugin_dir must be set to WAS_HOME/bin/.
Note: Whenever service is applied to the WebSphere Application Server for z/OS product, you must FTP a new copy of the WebSphere HTTP Plugin-in for z/OS from the install_root/bin directory to this directory on your HTTP Server system.
Example: The Service directive is split here for printing purposes. In the actual httpd.conf file, enter this directive on a single line.
Service /webapp_contextroot/* /http_plugin_dir/ ihs390WAS50Plugin_http.so:service_exit
Specify the application's context root for the variable webapp_contextroot.
The value you specify for the variable http_plugin_dir depends on whether or not the HTTP Server is on the same LPAR as the WebSphere Application Server.
Note: If v5.0.2 APAR PK02800 or v5.1.0 APAR PK02801 is applied to the WebSphere Application Server for z/OS environment, the value for the http_plugin_dir must be set to WAS_HOME/bin/.
Note: Whenever service is applied to the WebSphere Application Server for z/OS product, you must FTP a new copy of the WebSphere HTTP Plugin-in for z/OS from the install_root/bin directory to this directory on your HTTP Server system.
ServiceSync On
Both methods will create the plug-in configuration file, plugin-cfg.xml, in EBCDIC format, which is the proper format for execution in a z/OS environment.
To use the Update Web Server Plug-in Configuration page in the administrative console:
You can set the TrustedProxy property to true from either the Web container Custom Properties page or the HTTP Transport Custom Properties page. If you set it on the Web container Custom Properties page, all transports will support private headers.
Note: If you try to use private headers without setting the TrustedProxy property to true, the request containing the private headers is rejected, and you might receive either a "403 Request Not Permitted," a "HTTP/1.1 404 Not Found," or some other error message that indicates that the request was rejected. After you set the TrustedProxy property to true, the transport trusts all private headers it receives. Therefore, you must ensure that all paths to the HTTP or HTTPS transport are trusted.
The configuration is complete. To activate the configuration, stop and restart both the application server and the HTTP Server. If the WebSphere HTTP Plug-in for z/OS comes up when the HTTP Server starts again, you receive messages similar to the following:
WebSphere HTTP Plug-in for z/OS Version x.x Service Level x is starting WebSphere HTTP Plug-in for z/OS initializing with configuration file : fully_qualified_path_to_the_plugin-cfg.xml_file WebSphere HTTP Plug-in for z/OS initialization went OK :-)