How to handle differences in web.xml in NWDI

[Former Member]

Hi all,

We are doing an upgrade of the CRM B2B application from CRM 4.0 to 6.0 and just started using NWDI. In our web.xml we have configurations for systems we integrate against. For this reason we have differences in our web.xml for TEST and PROD.

Is there some way to handle this through NWDI to not make it to painful to make changes in web.xml?

/Anders

[Former Member · Accepted solution]

You need to abstract out your connections to other business systems. Technical system information should be contained in the SLD, or at least as a destination in the J2EE engine. This way, technical details become a configuration setting of the runtime environment, rather than configuration for the application itself.

Of course, this means a code change, but using the Destination service of the J2EE engine is quite simple:

http://help.sap.com/saphelp_nw70/helpdata/EN/17/d609b48ea5f748b47c0f32be265935/frameset.htm

Hope that helps you out.

[Former Member · Accepted solution]

Hmm... so far this service is unique to this application, but in the future we might use it for other systems, so that makes sense.

Is there a way administrate URL an authentication information using some webui? We don't have direct access to our server, so using Visual Administrator means involving one more person, and all the delays that comes with that.

We also thought of the possibility to set up some custom property in XCM, and administrate the connection information there. Might this be a way to go, if we consider the service application specific? Is this hard to achieve?

[Former Member]

We will move our changes to custom XCM properties.