What it takes to migrate an existing 10g B2B Customer to 11g
By Ramesh Nittur Anantharamaiah on Jan 19, 2010
Following are list of steps to be considered for what it takes to migrate an existing 10g B2B environment to B2B 11g.
Deliver SOA/B2B 11g architecture including new features, system management, security, performance etc
Review and asses the impact the features that are not upgraded to B2B 11g
Review and asses the impact the features that are changed in B2B 11g
Review and asses the impact B2B schema upgrade steps including
+ Required patch set information
+ Message configuration
Review the current B2B 10g schema
Document the entire B2B architecture of the customer which includes the followings
+ List of all EDI trading partners and configurations
+ List of all Agreements and configurations
+ List of all existing inbound and outbound files from trading partners and their detailed definitions
+ List of all EDI guidelines if any
+ Review any requirements in terms of 10g data clean up
+ Create a detailed project plan that covers upgrade/migration steps for all 10g B2B applications in 4 SOA environments
+ List of B2B configuration properties (tip. properties)
+ List of XEngine configuration (configuration xml files under XEngine directory).
Resubmit, Error,Exception handling features in 10g/11g.
Parameters which was Global in 10g and has made interface specific i.e configurable.
OC4J configuration Vs Weblogic configuration.
Security configuration between 10g/11g i.e Oracle wallet to JKS
Performance, Scalability and HA aspects between 10g to 11g
Needless to say that there is a seamless upgrade of the 10g metadata to 11g metadata using the upgrade utility. Please refer http://download.oracle.com/docs/cd/E15523_01/upgrade.1111/e10127/upgrade_b2b_apps.htm