Enter the name of the custom user in the JMS System User field and click Apply.

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 15-2 Oracle Fusion Middleware Security and Administrators Guide for Web Services deployment configuration. The SOA framework provides its own mechanism for composite services and configuration lifecycle and synchronizations. ■ ADF Web Service data control configuration stores connection details for WebCenter services in a connections.xml file and all post-deployment changes as customizations in the Metadata Services MDS repository. The general steps for migrating a Web service application from a development or test environment to a production environment are as follows: 1. Install and configure the production environment with the components that you need. 2. Migrate security information, such as users and groups, the identity and policy stores, and credentials. For more information, see Migrating Policy Configuration on page 15-5. 3. Migrate policies and deployment configuration data as required. For more information, see Migrating Policies on page 15-4 and Migrating Deployment Descriptors on page 15-7. Modify any information that is specific to the new environment such as host name or ports. 4. Deploy the applications in the new environment. For information about migrating Fusion Middleware applications between environments, see Advanced Administration: Expanding Your Environment in Oracle Fusion Middleware Administrators Guide. Overview of Horizontal Policy Migration The following steps describe a typical scenario for how to create a policy and migrate the policy horizontally through the different stages of the application development and deployment cycles. 1. Use Oracle Enterprise Manager Fusion Middleware Control to create a policy. For more information, see Creating Web Service Policies on page 7-4. 2. Export the policy to a file. For more information, see Migrating Policies on page 15-4. 3. Copy the policy file to policy store location in the Oracle JDeveloper environment. 4. Create a Web service in Oracle JDeveloper and attach the policy to the Web service. For more information, see Using Policies with Web Services in the Developing with Web Services section of the JDeveloper online help. 5. Deploy the Web service to the staging server, and test the Web service. For more information, see Developing Web Services in the JDeveloper online help. 6. Import the policy to the production server environment. For more information, see Migrating Policies on page 15-4. 7. Migrate the following information, as required: ■ Policy configuration. See Migrating Policy Configuration on page 15-5. ■ Assertion templates. See Migrating Assertion Templates on page 15-7. 8. Deploy the application into the production environment, and test the Web service.