Migrating Existing Java EE Applications to AS Java

Use this procedure to prepare applications developed for other platforms than SAP NetWeaver AS for Java for running on AS Java. Preparation includes configuring platform-dependent settings such as the data source name, the JDBC connection URL, JNDI lookup Strings, and other environment entries.

In AS Java, there are two alternative ways to configure platform-specific settings:

• Programmatically, by using the SAP-specific deployment descriptors ( data-source-aliases.xml , ejb-j2ee-engine.xml , web-j2ee-engine.xml , application-j2ee-engine.xml and appclient-j2ee-engine.xml ) inside the application

  This approach is useful if your Java EE applications are to run on a single platform only. Each application carries environment information in its application archive, so you do not have to configure the respective settings additionally after deploying.

• On the fly, by using the respective configurable properties in SAP NetWeaver Administrator

  This approach is useful if your applications are to run on multiple platforms. Different platforms have different landscapes, IP addresses, and other specifics, so it is impossible to use the same deployment descriptor information for them. Instead, you can configure the related properties in SAP NetWeaver Administrator on each platform after you deploy an application. In this way, the application does not need to contain that information in itself.