Isetup And its Prerequisite

iSetup is a module provided within the E-Business Suite that allows to easily migrate setups using a user-friendly interface.

Oracle itself recommend it to migrate functionality from tested/crp environment to production environment, but recommended way to use it on first test environment instead of production directly.

Hence using isetup, all functionality driven data will be validated and data consistency is guaranteed. It requires good amount of setup functional knowledge and bit of technical knowledge to use this tool. 

This tool consists of the Migrator and the Reporter:

  The Migrator helps you to migrate setup data from one instance of the Oracle E-Business Suite to another. Following are the steps to migrate data:

• Extract select data from an Oracle E-Business Suite instance.

• Transform select attributes of the extracted data objects as per your requirements.

 (This is optional)

• Load data to the target Oracle E-Business Suite instance.

The Reporter helps you to generate reports. You can:

• Generate reports on the extracted data.

• Compare two sets of extracted data to identify differences.

Prerequisite setup for Instance Mapping to work     

·      ATG patch set level should be same across all EBS instances.

·      Copy DBC files of each other EBS instances participating in migration under $FND_SECURE directory (refer note below for details).

·      Edit sqlnet.ora to allow connection between DB instances (tcp.invited_nodes=(<source>,<central>))

·      Enter host name and ip address in host file.

·      Make sure that same user name with iSetup responsibility exists in all EBS instances participating in migration.

Note:- iSetup tool is capable of connecting to multiple EBS instances. To do so, it uses dbc file information available under $FND_SECURE directory. Let us consider three instances A, B & C, where A is central instance, B is source instance and C is target instances. After copying the dbc file on all nodes, $FND_SECURE directory would look like this on each machine.

A => A.dbc, B.dbc, C.dbc

B => A.dbc, B.dbc

C => A.dbc, C.dbc