Here's what's going on:

There are three plugin-cfg.xml files:
1) /config/cells/plugin-cfg.xml
2) /config/cells/ADMIN_WAS61SVR/nodes/ADMIN_WAS61SVR/servers/IHS_MIGRATION/plugin-cfg.xml
3) /config/IHS_MIGRATION/plugin-cfg.xml

* When I install my EAR file, 1) *is* getting updated.
* If I use the Websphere "Integrated Soultions Console" menu item "Environment -> Update global Web server plug-in configuration", 1) get's generated
* If I use the Websphere ICS menu item "Servers -> Web Server" select my web server, and click Generate plugin, 2) get's generated, but not the same as 1)
* From the same menu item, if I click Propagate plugin, 3) get's copied to 2).
* Lastly, 3) is what my HTTP server points to.

This is all very confusing. How can I get 1) to 2), then to 3)? Am I just supposed to copy the file? That seems prone to error...

Brian

Brian Leathem wrote:
Hello all,

Using WDSC 7, we create a .war file, and package it an EAR file (pretty
much done automatically by WDSC). The ear file is correctly configured
with the context path for the war file. However, when we push the ear
file to WAS on our system i, the plugin-cfg.xml file is not getting
update with this context path. This means none of the requests to our
webserver are getting forwarded to WAS for that application.
(The application does work if we go straight to the WAS port). I edited
the plugin-cfg.xml file myself, and got it to work, but the file gets
regenerated automagically, and my edits are lost.

Can anyone point me to a resource explaining how to get my context path
into the plugin-cfg.xml file automatically? I've tried a bunch of
redbooks, and the IBM on-line help without much success...

Thanks,
Brian Leathem



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.