In the Enterprise Bean Configuration section of the page, enter the custom user

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. Managing Application Migration Between Environments 15-3 See Deploying Web Services Applications on page 5-1 and Testing Web Services on page 12-1. Sample Use Cases for Deployment Descriptor Migration The following sections provide sample use cases for ADF Business Control or WebCenter Web Service applications for which you must migrate the PDD files. Scaling a Deployed ADF Business Control or WebCenter Web Service Application in a Cluster The following steps describe a sample use case for scaling a deployed ADF Business Control or WebCenter Web service application within a cluster. 1. Deploy an ADF Business Control or WebCenter Web service application in a clustered WebLogic Server domain consisting of, for example, an Administration Server and two Managed Servers MServer1 and MServer2. For deployment information, see Chapter 5, Deploying Web Services Applications. 2. Using Fusion Middleware Control or WLST, modify the policy configuration. For example, attach a policy named oraclewss_username_token_service_policy to the Web service on MServer2. For more information, see Chapter 8, Attaching Policies to Web Services. The configuration changes are persisted in the PDD files. 3. Restart the application. 4. Export the PDD to a JAR file using the exportJRFWSApplicationPDD command. For more information, see Migrating Deployment Descriptors on page 15-7. 5. Using the WebLogic Server Administration Console, clone a new Managed Server named MServer3 in the cluster from MServer2. For more information, see Clone Servers in the WebLogic Server Administration Server Online Help. 6. Start the new Managed Server, MServer3. Note that MServer3 does not have the policy oraclewss_username_token_ service_policy attached because it was attached after the application was initially deployed. 7. Import the JAR file containing the Oracle WSM PDD files that you created in step 4 to MServer3 using the importJRFWSApplicationPDD command. For more information, see Migrating Deployment Descriptors on page 15-7. 8. Restart the application. Propagating Run-time Policy Changes in an ADF Business Control or WebCenter Web Service Environment The following steps describe a sample use case for propagating run-time policy changes for an ADF Business Control or WebCenter Web service application to all servers in a cluster. 1. Deploy an ADF Business Control or WebCenter Web service application in a clustered WebLogic Server domain consisting of, for example, an Administration Server and three Managed Servers MServer1, MServer2, and MServer3. For deployment information, see Chapter 5, Deploying Web Services Applications.