|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Hi Nicolas,
can you better describe your setup?
are you using IHS (or ApacheHTTPD/IIS) plus Websphere Plugin in front of the application server?
if yes, when deploying a new EAR or WAR within a EAR , than you must regenerate and propagate plugin configuration file. It will be automatically picked up after some min.
This is needed both cluster or single server
@Greg:
This should be a standard behaviour in case of deployment both cluster or single server when using the WAS Plugin...
If you think this can be done I think it is better to start a separate improvemnt ticket on this... do you agree?
Regenerating and propagater the plugin confing file is done same way as the deployment (via admin console using IBM API)
Ref:
http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftxml_pluginconfig.html
https://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=%2Frzamy%2F50%2Fadmin%2Fhelp%2Frxml_plugin.html
but there could be some other parameters to be passed to the deployed plugin (i.e the virtualhosts). If you nedd any info/support on this, just ask...
if no and you just using the reverse proxy feature of web servers, than I think this is nothing to do with WebSpehre deploy plugin...
@Greg:
do you agree? any clue which can be a proper plugin candidate for this?
Best Regards,
Leonardo