Automating the Migration of an Application to Other Environments

Deploying Applications 10-3 Services Manager, use an MDS Repository. For information about the MDS Repository and registering the repository, see Section 14.3 .

10.1.2 Understanding Deployment, Redeployment, and Undeployment

When you deploy an application, you deploy it to the application server for the first time. When you redeploy an application, you can: ■ Redeploy a new version of the application; the previous version is still available, but the state is set to Retired. This is known as the production redeployment strategy. Oracle WebLogic Server automatically manages client connections so that only new client requests are directed to the new version. Clients already connected to the application during the redeployment continue to use the older version of the application until they complete their work, at which point Oracle WebLogic Server automatically retires the older application. ■ Redeploy the same version of the application or redeploy an application that is not assigned a version; the application version you select is replaced with the new deployment. ■ Redeploy a previous version of the application; the earlier, retired version is set to Active and the later version is set to Retired. When you undeploy an application, Oracle WebLogic Server stops the application and removes staged files from target servers. It does not remove the original source files used for deployment.

10.2 Understanding and Managing Data Sources

A data source is a Java object that application components use to obtain connections to a relational database. Specific connection information, such as the URL or user name and password, are set on a data source object as properties and do not need to be explicitly defined in an applications code. This abstraction allows applications to be built in a portable manner, because the application is not tied to a specific back-end database. The database can change without affecting the application code. Applications use the Java Naming and Directory Interface JNDI API to access a data source object. The application uses a JNDI name that is bound to the data source object. The JNDI name is logical and can be mapped to any data source object. Like data source properties, using JNDI provides a level of abstraction, since the underlying data source object can change without any changes required in the application code. The end result is the details of accessing a database are transparent to the application. Note: If your application contains an application-level credential store, and you are moving the application from a test to a production environment, you must reassociate the credential store, as described in Reassociating the Domain Policy Store in the Oracle Fusion Middleware Application Security Guide. See Also: Oracle Fusion Middleware Configuring and Managing JDBC for Oracle WebLogic Server for more information about data sources