Porting Oracle EBS scripts between environments

Porting Oracle EBS scripts between environments

A common situation is that you must develop scripts in one environment but conduct testing in another. This requires that your scripts be portable across environments.

Practical Solution:

There are several values that need to be parameterized in order to make your scripts portable. Parameterize and test these as early as possible to avoid frantic porting at test execution time!

The values to parameterize are:

1. Base url or app server ip

2. Web server port number which you initially connect to for login authentication

3. Forms server port number, which the nca_connect sues to connect to the Forms server

4. Configuration (“config” value in nca_connect)

5. Module (second ‘path’ value in nca_connect)

Examples of where these are used:

/*initial Oracle launch*/

web_browser("ebsr12.com:9097",

DESCRIPTION,

ACTION,

"Navigate=http://{app_srv}:{port_web}/",

LAST);

/*Forms server connect*/

nca_connect_server("{app_srv}", "{port_forms}",

"module=/ebstop/{module}/apps/apps_st/appl/fnd/12.0.0/forms/US/FNDSCSGN fndnam=APPS

record=names config='{config}' icx_ticket='.{p_ICX_Ticket}..'

resp='AR/CAN_CUSTOMER_MASTER_ADMIN' …");