[TehcNote] WebSphere v8.x Plugin - UseInsecure (Plugin <==> WAS http offload)

WAS - transport chains - secure - disable
plugin - UseInSecure = true


Plug-in regeneration updates https transports in the plugin-cfg.xml file after the WCInboundDefaultSecure transport chain is disabled

Problem(Abstract)
The plug-in regeneration persists to update the plugin-cfg.xml file with the https transport ports for the WebSphere Application Server even after the WCInboundDefaultSecure transport chain is disabled.
Symptom
The plugin-cfg.xml would still display https transport port settings for the WebSphere Application Server.

Cause
If the user prefers to disable https communications between the plug-in and the application server, there is an additional https transport chain starting with WebSphere 7.0 and higher named HttpQueueInboundDefaultSecure that uses the same port as the WCInboundDefaultSecure chain which should be disabled.
Resolving the problem
Both HttpQueueInboundDefaultSecure and WCInboundDefaultSecure chains must be disabled before regenerating the plugin.


Procedure to disable https communication between the plug-in and WebSphere Application Server:

1) Login to the WebSphere Administrative console
2) Go to Servers -> Server Types > Application Servers -> server_name -> Web Container Settings -> Web container transport chains -> WCInboundDefaultSecure
3) Uncheck the box beside the "Enabled" option.
4) Click Apply and save settings.

Using the same procedure, disable the HttpQueueInboundDefaultSecure transport chain:

5) Go to Servers -> Server Types > Application Servers -> server_name -> Web Container Settings -> Web container transport chains -> click on HttpQueueInboundDefaultSecure

6) Uncheck the box beside the "Enabled " option under HttpQueueInboundDefaultSecure

7) Scroll to the bottom of the page and Click Apply, OK then click "Save directly to the Master configuration"

8) Remove the Web Container Secure Transport entry under Host Aliases:

a) From the left hand pane of the Admin console, Go to Environment -> Virtual Hosts -> Virtual Host_Name -> Host Aliases
b) Check the box beside the Web Container Secure Transport entry (default is 9443) and click the Delete button.
c) Click Apply, OK and "Save directly to the Master configuration."
d) Regenerate and propagate the plug-in.
e) Restart the application server and the web server to re-load the updated plug-in settings

PI10757: ALLOW PLUG-IN CUSTOM PROPERTY "USEINSECURE"IN A V7 DMGR, FOR GENERATING PLUGIN-CFG.XML INTENDED FOR A V8R5 RUNTIME.

...... skip ......

Problem conclusion
This custom property was previously only settable
when generating the plugin configuration in WebSphere
Application Server V8.5 or higher but with this apar, the
custom property can be set and picked up when generating the
configuration in WebSphere Application Server V7 or V8.
NOTE-This custom property is only recognized (and
only needed) in web server plugin v8.5 and higher.

Set the custom property UseInsecure=true on the Servers >
Web Servers > Web_server_name > Plug-in properties > Custom
properties page.