Oracle SOA Application Migration - Lift and Shift

Oracle SOA Source Details
Weblogic Version - 12.2.1.0.0
SOA Suit Version - 12.2.1.0.0
Oracle Linux Version - 6.0

Oracle SOA Target Details 
As this is a lift and shit migration there is no upgrade hence the version of application remains same
Weblogic Version - 12.2.1.0.0
SOA Suit Version - 12.2.1.0.0
Oracle Linux Version - 7.0

Steps to Migrate Oracle SOA using lift and shift method.
1) Copying the binaries from source to target
2) Configuring the domain with new database or existing database
3) Verifying the Domain configuration
4) Starting the application

To start with this migration in details, assuming that you already have a database with all existing metadata schema available. As this is a lift and shift method you will even need to have all your existing schema exported and imported to the database where your migrated SOA will connect.

1) Copying the binaries from source to target

This step includes copying your full application binaries with same mount-point name on target, best way is to use RSYNC to copy the binaries from source to target.

You will need to sync two location, HOME location and the APPLICATION location. HOME location is mandatory as it contains your bash_profile and .ssh saves your connection information.

If you are using key based authentication
rsync -Pavz -e  "ssh -i path_to_key" source_location user@host:target_location

If you are using password authentication
rsync -Pavz source_location user@host:target_location

2) Configuring the domain with new database or existing database

Once the binary copy is completed we will now proceed with the configuration

Open a new VNC session, go to $ORACLE_HOME/oracle_common/common/bin

Run below command,

./config.sh

After you run this command your domain configuration wizard opens up,

Click on Update an existing domain and click Next

We will not make any changes on the template as this is from existing configuration hence no changes are required here, please click Next

All existing Datasources are already synced you just need to do next and test all your Datasource, if in case some failed to connect please reach out to your network team to fix the issue and try again.

This is a critical step as we will now link the application to the database,

1. Under Service, please update your database service name.
2. Under Hostname, please update your database hostname.
3. Under Schema Owner, please give your STB schema name.
4. Under Schema Password, please give your existing STB schema password.
5. After all the above information click on Get RCU Configuration, This will get all your RCU information synced in the domain. Click Next

Select all and update the Service, Hostname for all schema and test the configuration. Upon successful test your domain will now be ready for new database configured in it.

Next is to update only your managed server listener address and nodemanger listener address, rest all configuration will remain as is.

Update Listen address for managed server

Update Listen Address for node manager.

Rest all configuration remain as is, please click Next and End the configuration wizard.

3) Verifying the Domain configuration

At times it happens only config.xml is update while the fmwconfig is still pointing to old dataase connection.

Go to $DOMAIN_HOME/config/fmwconfig/*.xml

All xml under this folder needs to be verified if it is linked to new database, if it is still pointing to old database, update the connection manually.

4) Starting the application

Start the node manager first.
Start the Admin Server
Start managed server.

Verify the environment, at this stage you have successfully migrated SOA from one machine to another.