Steps to upgrade SOA and AIA environment from 10g to 11g

SOA Suite Server Setup

11g SOA server consists of a Domain on which Admin server and Managed server is hosted. There could be many managed servers across systems but only one Admin Server can exist within a domain. Start the SOA Suite Admin server and managed server and make the Application server changes mentioned below. At Application Server level in 11g we need to make the following custom configurations manually:

• Data Source: Data sources and Connection Factories are used by SOA code to connect to a resource or target system. In 10g these custom datasources are configured in EM Console. Whereas in 11g we need to configure all the custom datasources using the same names and setting is Weblogic Console by navigating to <Domain_Name>->Service->Data Sources.
• Connection Factory: In 10g we configure Connection factory details in EM Console via: Cluster Topology->oc4j_soa->Applications->default->Adapter->Connection Factories. In 11g we should configure these custom Connection factories in Weblogic Console by navigating to<Domain_Name>->Deployments->Adapter->Configuration-Outbound connections.
• Partitions: In 10g we have BPEL Domains to group the BPEL Processes, ESB system and service groups to group ESB services. There is no concept of these domains and service groups in 11g but concept of Partition is introduced which do not have their own configuration and logging but to group BPEL and ESB processes it can be used. With the command line utility we can create partitions with the following command: wls:/mydomain/ServerConfig>sca_createPartition(‘cdh')
• BPEL Domain Properties: Since 11g has a single domain and 10g has multiple domains we need to migrate all the BPEL domain properties from 10g to 11g.Properties in the domain.xml for each domain of 10g has to be copied manually to bpel-config.xml/soa-config.xml file. For more info on this refer the Document: http://download.oracle.com/docs/cd/E17904_01/upgrade.1111/e10127/upgrade_bpel_apps.htm#CHDFDEDB with Chapter: Specifying Domain Descriptor Properties

Other Custom Configurations done in 10g also has to Moved to 11g manually.

AIA Setup

In 11g all the artifacts which have the configuration details are stored in a central repository: MDS unlike 10g where the configurations are stored in file systems. Hence to migrate the same Custom Configuration files we need to import the changes to MDS. Following steps has to carried out for AIA setup and migration from AIA FP(2.x) to AIA FP 11g.

• AIA Configuration Properties File: Get a copy of AIAConfigurationProperties.xml file from AIA(2.x) server in SOA 10g.To migrate the AIA Config Changes the AIAConfig file present in 11g server has to be exported from MDS by running the ant command: ant -f ant-sca-deploy.xml exportSharedData with all the required parameters. Manually copy the custom configurations from current AIA config file to 11g file along with port and Hostname changes and import it back into MDS.
• Login to AIA 11g Console and navigate to Setup->System and note the configuration settings there. Login to AIA 11g (11.1.1.6) Console and login as weblogic user that has “AIAApplicationUser” group and navigate to Setup->System and configure the same settings as in AIA 2.x.
• To import CAVS test cases: Login to AIA console and export all the test cases as files. Login the AIA console 11g as weblogic user that has “AIAApplicationUser” group and under CAVS->Definitions select Import and Import the testcase files one at a time.
• Importing Custom EBO’s: Checkout the Custom EBO’s from perforce and later modify it with these custom configurations and import it into MDS.

 10g Key Artifacts Setup

In 11g all the artifacts which have the configuration details are stored in a central repository: MDS. MDS is Metadata Services repository which is database based and centralized across all midtiers. However hierarchy in MDS is similar to a file system like 10g where the configurations are stored in file systems. MDS setup is very flexible as we can browse through the setup from Jdev, export and import the artifacts back to Server by using ANT commands or through EM Console. Hence the artifacts present in 10g are stored in MDS for Migrations by following the below mentioned steps:

1. DVM Upgrade:
• Export all the DVM’s from ESB Console or from ESB slide in 10g and modify each DVM by including namespace: xmlns=http://xmlns.oracle.com/dvm and removing isNew=”true” entry.
• Change the export DVM file name extension to ‘.dvm’ instead of ‘.xml’.
• Rest of the contents remains same. These steps can also be done by running the ant build file: “upgrade-xrefdvm” target in the “ant-sca-upgrade.xml”.

2. Fault Policies:
• Pick all the fault policies from all the domain of SOA 10g(fault-binding.xml and DefaultPolicy.xml).
• Modify the fault.bindings.xml by changing the version to “3.0” and <process> tag to <composite>
• Rename DefaultPolicy.xml to fault-policies.xml.
• Change the Version in fault-policies.xml “3.0” and add a higher level fault policy node: <faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
• Create a folder in the local file system and copy both the files in this location.
• Zip up the contents and import these Fault Policies to MDS using Ant.

3. Import Shared Schemas and WSDLs: If there are shared Schema’s and WSDL’s follow the below mentioned steps:
• Export the files from SOA 10g. Please it in the local file system.
• Make sure to change the Server hostname and Port to 11g server and have the same directory structure as 10g.
• Zip the contents of these folder and import to MDS using ant command.