Click Apply and restart WebLogic Server.

14-28 Oracle Fusion Middleware Security and Administrators Guide for Web Services Figure 14–13 WebLogic Server Administration Console Update for JMS System User The configuration changes need to be saved in a new deployment plan. 9. Use the Save Deployment Plan Assistant to save the new deployment plan. 10. Repeat steps 7 and 8 for the second MDB. The changes are automatically saved to the new deployment plan.

11. In the Change Center, click Activate Changes.

12. Redeploy the application. For more information, see Chapter 5, Deploying Web Services Applications. 15 Managing Application Migration Between Environments 15-1 15 Managing Application Migration Between Environments This chapter describes how to migrate Web service applications between environments, such as from development or test to production. It includes the following sections: ■ Overview of Web Service Application Migration ■ Overview of Horizontal Policy Migration ■ Sample Use Cases for Deployment Descriptor Migration ■ Migrating Policies ■ Migrating Policy Configuration ■ Migrating Assertion Templates ■ Migrating Deployment Descriptors Overview of Web Service Application Migration To migrate Web service applications independently between environments, such as from test to production, or in a scaled clustered environment, you must export the policies and the deployment configuration information to the new environment so that you can deploy the application. Depending on your configuration, you may also need to migrate policy configuration artifacts and policy assertion templates. A deployment descriptor is an XML file that contains the basic deployment configuration for an application. For WebLogic Server and WebLogic Java EE Web services applications, you create a deployment plan that contains the necessary deployment descriptors for deploying the application in a new environment. For ADF Business Components and WebCenter services, however, run-time policy changes are persisted in proprietary deployment descriptor PDD files: oracle-webservices.xml and oracle-webservices-client.xml. Because these files are not included in the WebLogic deployment plan or exported with any other deployment descriptors, you must export and import these PDD files separately. You must also export and import these PDD files separately if you are scaling your application in a clustered environment. Note that the following Oracle Infrastructure Web services components provide different configuration management mechanisms. ■ For a SOA composite, Web services and Oracle WSM configurations are persisted in a composite.xml file which is included in a configuration plan used for