1

Cloning An Apps 11i Environment � Step-By-Step Raman Batra Legerity Inc. Introduction The paper presents a step-by-step approach for completely cloning an Oracle Applications 11i environment, including Port Selection, Forms Server and WebDB 2.2, Reports Server, TCF Server, Apache and Web DB 2.5, Concurrent Processing, startup and shutdown scripts. The paper includes both forms based and self-service web applications, and will mention the architectural differences between the two applications types. An appendix to the paper lists the files which need to be be changed for the cloning process. The word �cloning� refers to the process of making a working copy of the database, concurrent processing and application stack(s).

Legerity's Oracle Implementation Legerity has chosen Oracle 11i applications to support Financial, Human Resources, Order Management, and Manufacturing functions of the business and has standardized on Oracle's database products for all business applications development. System Configuration With Oracle Applications Release 11i, the Rapid Installer gives the choice of a Production, Test or Vision Demo environments. At our site, we used the Rapid Installer to install a fully configured Production environment in a multi-node configuration and then cloned it for Development, Testing and Quality Assurance environments. As part of this setup, our installation is a two-node, in which the database, administration, reports and the concurrent processing stacks are installed on the same server, and the forms and the webserver are installed on another server.

Table 1. System Configuration

System Configuration Multi-node, two servers Database, Administration and Concurrent Processing Server

HP 9000/800 N-Class, 4 x 400 Mhz

Forms and Web Server HP-9000 L Class, 2 x 250 Mhz Platform HP-UX 11.0 32-bit Database Version 8.1.6.1.0 Application Version 11.5.1.0.0 (May release) Forms Client Connectivity Jinitiator (1.1.7.27) User Interface Forms, HTML/Javascript (Self-service Web)

Major Components of the 11i Architecture The Oracle Applications stack has changed considerably since versions 10.7 NCA and 11.0.3. The stack includes two distinct interfaces - the �traditional� Forms (ERP applications) interface and Web Interface (Self Service, CRM and Workflow).

Copyright © 2000 by (Raman Batra)

2

The key components of the technology stack are: 1. Database Server: This is the Oracle Database engine, and hardly needs any introduction. The version

being deployed with Applications 11i is 8i (8.1.6.1.0), although as reviewed later on we still need two ORACLE_HOMES on the application stack (8.1.6.1.0, and 8.0.6.0.0).

2. Forms Server: This is a combination of a WebDB 2.2 HTTP listener process and the Oracle Forms 6.0

server. Since Forms 6.0 is certified with Oracle 8.0.6, we need an Oracle 8.0.6 Home on the Forms Server.

3. Reports Server (version 6.i): This normally runs on the database server. At Legerity, we use a mixture

of Oracle Discoverer and third-party tools for our reporting requirements. Discoverer is an optional component of the End User Layer and is used for Business Intelligence functions. Oracle Graphics is a component which runs closely with Oracle Reports.

4. Self Service/Web/CRM: In this interface, the end users view HTML pages served by HTTP listeners of

the WebDB 2.5 and the Apache Web Server . WebDB 2.5 uses a PL/SQL cartridge while the Apache Server delivers Java Applets and Java Server Pages (Jserv 1.1). Both of these connect to the RDBMS using JDBC. With Release 11.5.2, the Apache Server uses a modified PL/SQL gateway to facilitate PL/SQL procedural calls when needed.

5. Concurrent Processing Server: The concurrent processing server runs each of the jobs submitted by the

Oracle Applications software. These may be interactive jobs, such as print a specific invoice, or an automated process such as analyze all database objects. At our implementation we kept concurrent processing on the same physical tier as the database server.

6. Administration Server: Each of the other tech stacks needs an administration component in order to

perform tasks such as patching the stack, re-linking executables and re-creating Java Archives. As a consequence, an Administration component is present on the database server, Concurrent Manager server, forms server and Web server. The utilities adpatch and adadmin are part of the Administration tech stack.

7. Thin Client Framework (TCF Server): Since release 11 of Oracle Applications, certain product forms

support graphical display of hierarchical data using Java Applets. At Legerity�s implementation, our MRP module used the TCF Server process for viewing a tree during �pegging�. It comprises of a TCF listener process called SocketServer which can be configured using either HTTP/HTTPS/Socket mode. On Unix, the command jre oracle.apps.fnd.tcf.ServerControl <port#> status tells you about the status of the listener process.

8. HTTP/Web Listeners: In Apps 11.5.1, WebDb 2.2, WebDB 2.5 and the Apache Server (version 1.3.9)

facilitate communication between the above components and the client. From Apps version 11.5.2, WebDb 2.2 and 2.5 have been replaced by the Apache Server (1.3.9).

9. Java: The Java environment is used heavily in Apps 11i. In release 11.5.1, the components are Java

Runtime Environment 1.1.8 (JRE 1.1.8), Java Development Kit 1.1.8 (JDK 1.1.8) and Jserv 1.1. 10. JInitiator: This Browser Plug in (version 1.1.7.27) is installed on the client, which in most cases is a

PC. The cloning techniques discussed here should obviate the need for any cloning required on the client/PC. Version 1.1.7.27 has been replaced by a higher version, since the original install of 11.5.1.

3

Backup Methodology As detailed later on in this paper, the process of cloning the application and database stack involves restoration from a backup. The application stack, with the exception of the log and out folders of the concurrent manager stack is �static� and can be restored from a file-system level backup. However care must be taken to make sure database and file-system backups (application backups) are consistent with each other. This is very important, since patches change the database and/or the application stack. Database backups may be online or offline, depending upon your site strategy and uptime requirements. Stack Userid and Ownership In our setup the application stack is installed under the ownership of the Unix userid applmgr, belonging to the group apps. The database stack is installed under the Unix userid oracle, belonging to the group dba. However, there are file systems such as $COMMON_TOP, which are owned by oracle, yet they have sub-folders owned by applmgr, so it can be somewhat tricky while restoring. It is recommended to let the userid root do the restore, just to avoid the pains of file permissions and privileges.

Cloning � The Nutshell Narrative If the entire cloning process were to defined in a nutshell, we could just describe it the following steps: ! Document your source and targets (file systems, paths, port numbers) ! Create Database Binaries (if not sharing) ! Create Common Tops ! Create Application Tops ! Clone the database instance and rename it ! Update key Application related Database Profile tables ! Edit key Configuration and Environment files on the related nodes ! Relink Applications Programs on related nodes ! Create a new banner (logo.gif, if applicable) ! Regenerate Java Archive Files (JAR Files) Cloning Step-by-Step However, the above is easier said that done, so the step-by-step approach is detailed in the paper. After planning your storage requirements, you can start the first steps needed to clone your environment. It is highly recommended to maintain a document as you restore/copy the file systems to create a new environment.

Both Nodes:

1. Allocate Port Numbers: These ports would have been selected by you the first time you installed the Applications from the Rapid Installer. Table 1 shows a sample listing of source and target ports. (The UNIX command netstat is very useful and gives useful information about the status of your ports, including listeners and connected processes.) This can be tricky, so good housekeeping principles would definitely help.

4

Table 1. Port Selection

Port Name Source Value Example

Target Value Example

FNDFS Listener Port 1529 1539 Database Listener Port 1524 1534 Apache Jserv Self Service Port 8880 8889 Metrics Server Request Port 9010 9019 Metrics Server Data Port 9020 9029 WebDB2.2 Listener Port 8000 8009 WebDB2.5 Listener Port 2000 2009 Reports 60 Port 7000 7009 TCF Socket Server Port 15000 15009 Apache Listener Port 8800 8809 Reports Server Port 9800 9809

2. Review source and target file system locations and plan your new layout: Ensure you have enough space to locate your new Oracle Homes, Application Tops and Common Tops. Database/Concurrent Processing/Administrative/Reports Server:

3. Create a new Application Top: ($APPL_TOP) Copy the file systems on your target system referenced by environment variable $APPL_TOP. You may restore these from an operating system backup consistent with a database backup. Document the source and target locations.

4. Create Common Top and Oracle Database Binaries: ($COMMON_TOP, $ORACLE_BASE, Oracle Homes) Copy the file systems on your target location referenced by environment variable $COMMON_TOP. This is owned by the userid oracle, however has sub folders owned by applmgr. It may be a good idea to do the restore as root. The userid oracle maintains two sets of binaries on the database server, one installed under Oracle version 8.1.6 and the other under Oracle version 8.0.6. You don�t have to install a �fresh� set of Oracle binaries for cloning. However, for the sake of completeness, this paper documents a technique to do so. Also, you should copy your ORACLE_BASE, assuming you are using it. Please see Table 2 for an example. Note: In your new init<SID>.ora, please edit the parameter utl_file_dir as determined by your target environment. Table 2. Database/Concurrent/Administrative Processing Server Restore Log

File System/Environment Variable

Owner/Userid

Source Example Target Example

APPL_TOP applmgr /u01/app/11i/PROD /u04/app/11i/DEV COMMON_TOP oracle /u01/app/oracle/prodcomn /u03/app/oracle/devcomn ORACLE_BASE oracle /u01/app/oracle/admin /u03/app/oracle/admin ORACLE_HOME * oracle /u01/app/oracle/product /u03/app/oracle/product

5

*At our site, the two sets of Oracle Homes were /u01/app/oracle/product/8.1.6 and u01/app/oracle/product/8.0.6. By copying /u01/app/oracle/product, we get both the versions of the Oracle binaries.

5. Edit files on Database /Concurrent Processing/Reports Stack: This is one of the most laborious and time-consuming steps and seems to take the longest time, besides being the most error-prone. You would do well to automate this step, since the time saved can be dramatic. These files are listed in Appendix A. You have to change the locations, such as /u01/app/11i now becomes /u06/app/11i, or port numbers (in start and shutdown scripts), or links. Note: It would be a good idea to maintain a log of your changes, since you may have to debug changes to understand why a portion of the stack is not working.

6. Check your environment:

Login as oracle, and set your environment with the <SID.81>.env or the <SID80.env> file. Make sure you navigate to the correct 8.1.6 home, 8.0.6 home, $COMMON_TOP etc. Then login as applmgr, and make sure you can navigate to the $APPL_TOP, $ORACLE_HOME and $COMMON_TOP.

7. Clone the database (online or hot backup):

This is something very site-specific and you may be using a variety of methods �RMAN, third-party software, homegrown scripts, etc. Once you have a valid backup of datafiles, you will have to create a new control file, reset logs and rename the instance name (SID) and basically have a new instance. You can test the instance comes up fine by �bouncing� it a few times.

8. Set Concurrent Processing Environment: Set the environment variable APPLCSF, and create LOG and OUT file locations on your target concurrent processing node. Make sure your environment variable APPLCSF in your environment refers to the correct location. Copy the contents of your LOG and OUT folders to the new location, if you care about accessing old logs and out files. This environment variable can be set in the $APPL_TOP/<SID>.env file. The unix owner applmgr needs to set its environment before the concurrent manager processes are started up.

9. Startup Database And TNS Listener: This is done so that you can login and make a few profile changes but not startup concurrent managers yet.

10. Disable Your Production Specific Concurrent Manager Jobs (if applicable):

You could to this by running the following SQL Script: update FND_CONCURRENT_PROGRAMS set ENABLED_FLAG = �N� where concurrent_program_name = �Your Program Name�. If your Production and Development System are identical to the point where data feeds, interfaces are exactly the same, then you need not worry about changing this.

11. Change FND Profile Options: As a general rule, whatever �points� to Production has to be changed to the new location. You will be changing FND_PROFILE_OPTION_VALUES table. Some example scripts are given below, which work for our site. The table FND_PROFILE_OPTION_VALUES can also be regenerated by the script $COMMON_TOP/admin/install/adupdprf.sql. You can edit adupdprf.sql and then simply run it.

6

Table 3. FND Profile Option Changes

Profile Option Sample SQL Script TCF Host

update FND_PROFILE_OPTION_VALUES set profile_option_value = REPLACE(profile_option_value, 'PROD', 'DEV') where profile_option_value like '%PROD%' and profile_option_id = '3071';

TCF Port update FND_PROFILE_OPTION_VALUES set profile_option_value = REPLACE(profile_option_value, '15000', '15009') where profile_option_value like '%15000%' and profile_option_id = '3072';

Includes HELP_TREE_ROOT, HELP_WEB_AGENT, ICX_REPORT_LINK, ICX_REPORT_SERVER, SITENAME, TWO_TASK, TCF Host

update FND_PROFILE_OPTION_VALUES set profile_option_value = REPLACE(profile_option_value, 'PROD', 'DEV') where profile_option_value like '%PROD%';

12. Update APPS.ICX_PARAMETERS Table:

You could run a script such as:

update apps.icx_parameters set home_url = REPLACE(home_url, '<old WebDb 2.5 Port>', '<new WebDb 2.5 Port>') update apps.icx_parameters set home_url = REPLACE(home_url, '<source WebDB 2.5 host>', '<target WebDB 2.5 host>')

-- Example update apps.icx_parameters set home_url = REPLACE(home_url, '2000', '2009')

update apps.icx_parameters set home_url = REPLACE(home_url, 'dbwebsrv.acme.com', 'dbwebsrv2.acme.com')

13. Update Concurrent Request Paths:

The table to be updated is update applsys.fnd_concurrent_requests, and the columns are logfile_name and outfile_name. If you don�t care about accessing old log and outfiles, then you could ignore this step. The update should concur with the value of the APPLCSF environment variable which needs to be set for concurrent processing.

14. Correct a link on the Database /Concurrent Processing/Reports Stack: There is a link for the Vertex Application ($PAY_TOP/vendor/quantum)

15. Relink Application Programs: This is done using the adadmin utility.

16. Verify Startup And Shutdown Scripts: On most platforms they should be located under $COMMON_TOP/admin/scripts. Table 4 lists them.

17. Startup database/concurrent processing stack to make sure components come up, including concurrent

managers. Table 4 shows examples of scripts contained in $COMMON_TOP/scripts, as well as commands needed to test the working of each component.

7

Table 4. Startup/Shutdown Scripts On Database Server

Check Type Start/Stop Script

Check Command Port #

Database addbctl.sh ps �ef | grep smon_$SID N/a TNS (Net 8) Listener (Oracle 8.1.6 Home) addlnctl.sh Lsnrctl status $SID 15xx FNDFS Listener (Oracle 8.0.6 Home)/ Reports Review Agent

adalnctl.sh Lsnrctl status FNDFS_$SID 15xx

Reports Server adrepctl.sh ps �ef | grep rwmts60 700x Concurrent managers (1 per instance) adcmctl.sh ps -ef | grep FNDLIBR | grep

CPMGR N/a

Forms/Web Server: 18. Create a new Application Top: ($APPL_TOP)

Create an Application Top on the Forms/Web Server from a copy of an Application Top of one environment/instance on the Forms/Web Server. This is done because the application top is different on the two nodes. Do Not Copy the $APPL_TOP from your database/concurrent processing server to create an $APPL_TOP on your Forms/Web Server. Note: It is better to copy/clone the application top with the forms/web server stack shut off, otherwise a couple of lock files remain open which can prevent parts of the application stack from coming up again. Oracle grabs the process id and keeps it in a file, to prevent it from restarting a listener which is running. (An example is $APACHE_TOP/Apache/logs/httpd.pid)

19. Create a new Common Top and Oracle Database Binaries: Similar to Step 2. Copy the $COMMON_TOP, and ORACLE_HOME(s) from the source instance on the Forms/Web Server to another location on the same or different Forms/Web Server depending upon your architecture. There will be no ORACLE_BASE on the forms/web server.

Table 5. Forms/Web Server Restore Log

File System/Environment Variable

Owner/Userid

Source Example Target Example

APPL_TOP applmgr /u02/app/11i/PROD /u06/app/11i/DEV COMMON_TOP oracle /u01/app/oracle/prodcomn /u03/app/oracle/devcomn ORACLE_HOME * oracle /u01/app/oracle/product /u03/app/oracle/product

*At our site, the two sets of Oracle Homes were /u01/app/oracle/product/8.1.6 and u01/app/oracle/product/8.0.6. By copying /u01/app/oracle/product, we get both the versions of the Oracle binaries. 20. Edit files on Forms/Web Server Stack:

This is one of the most laborious and time-consuming steps and seems to take the longest time, besides the most error-prone. You would do well to automate this step, since the time saved can be dramatic. These files are listed in Appendix A. Note: It would be a good idea to maintain a log of your changes, since you may have to debug changes to understand why a portion of the stack is not working.

21. TCF Server: Special Note: You may need to do the following for proper configuration and working of the TCF Server:

8

1. Delete any rows from APPLSYS.FND_APPLICATION_SERVERS. If your source webserver server was the same, you don�t need to do this. 2. On the Forms/Web Server navigate to $FND_TOP/SECURE. Remove any files with hostname_sid.dbc names. Run adgendbc.sh from $COMMON_TOP/admin/install/ folder. However, if the source webserver is the same as the target, you can rename and edit the file hostname_sid.dbc and you may not have to delete the file. The same file gets called by the tcfctl.sh script for starting up the TCF Server.

22. Review Links:

There may be several links which may get �broken� or out of synchronization. A few are listed below: 1. /u01/app/oracle/product/webdb/JRE is linked to /u01/app/oracle/product/jre/1.1.8. In our case, this is the JRE of our Production Instance. 2. /u01/app/oracle/product/webdb/network/admin/tnsnames.ora may be linked to another TNSNAMES.ORA on your system, especially when you copy filesystems. We linked it to our 8.0.6 Home�s tnsnames.ora file, i.e to /u01/app/oracle/product/8.0.6/network/admin/tnsnames.ora. 3. $COMMON_TOP/admin util/jre/1.1.8/bin/javakey is linked to $COMMON_TOP/ /util/jre/1.1.8/bin/.java_wrapper. 4. $COMMON_TOP/util/jre/1.1.8/bin/rmiregistry is linked to $COMMON_TOP/jre/1.1.8/bin/.java_wrapper. Steps 3 and 4 may be platform/site specific and you may have to review your post-install steps for accuracy.

23. Verify Startup And Shutdown Scripts: On most platforms they should be located under $COMMON_TOP/admin/scripts. Table 6 has more details.

Table 6. Startup/Shutdown Scripts On Forms/Web Server

Check Type Start/Stop

Script Check Command Port #

Self Service Webdb 2.5 HTTP Listener adwdbctl.sh ps �ef | grep wdblsnr | grep PORT 200x Self Service Apache & Jserv HTTP Server

adapcctl.sh ps �ef | grep Apache | grep -i SID 8889, 7 processes

Webdb 2.2 HTTP Forms Server Listener adwlnctl.sh ps �ef | grep wdblsnr.ctl | grep -i SID Port = 800x Forms Server Listener adfroctl.sh ps �ef | grep f60srvm | grep PORT Port = 900x Forms Metric Request Server adfmsctl.sh ps-ef | grep d2ls60 | grep PORT Request Port =

902x Forms Metric Client adfmcctl.sh ps �ef | grep d2lc60 | grep PORT Data Port = 901x TCF Server adtcfctl.sh jre oracle.apps.fnd.tcf.ServerControl

STATUS PORT# Port = 1500x

24. Check your environment:

Login as oracle, and set your environment with the <SID.81>.env or the <SID80.env> file. Make sure you navigate to the correct 8.1.6 home, 8.0.6 home, $COMMON_TOP etc. Then login as applmgr, and do the same with the <SID>.env.

25. Relink Application Programs: This is done using the adadmin utility.

9

26. Replace Banner: This is the logo ($OA_MEDIA/logo.gif). At our site, we use a simple paint package to write our environment name onto this logo. This helps avoid confusion, especially when navigating between multiple environments.

27. Digital Certificate and Jinitiator: In the list of files to be edited, we intentionally do not edit a file used while creating a digital certificate. ($APPL_TOP/admin/adsign.txt). When you run the adjkey utility, it creates a digital certificate ($APPL_TOP/admin/appltop.cer) file. Having a site with multiple digital certificates can cause problems on the clients and you may have to reinstall Jinitiator every time you switch application environments. This is because each JAR file is signed with a digital certificate, which is also use to package Jinitiator. If you have multiple web servers and also between multiple environments, you could simply copy the $OA_HTML/oajinit.exe to your target environments.

28. Regenerate Java Archive (JAR) Files: This is also done using the adadmin utility.

29. Finish: That�s it. Done! Your environment is cloned now!

Logon Page You could logon using two routes: 1. http:// <WebDB 2.5 Hostname>:Webdb 2.5 Port #/OA_HTML/US/ICXINDEX.htm or 2. http://<WebDB 2.2 Hostname>:Webdb 2.2.Port #/index.html � this takes you to the apps logon pages. Testing You want to make sure everything comes up fine. Trouble shooting and debugging individual components of the stack is beyond the scope of this paper. However, the best comparison is to have a Production environment available, while you create a new environment. That way, you can debug individual files and trace your way through the many files, which need to be edited. At a very minimum, we login to the new environment through both the forms and self-service web interfaces, and then run a few concurrent manager jobs. Conclusion This paper details the process of completely cloning a full Oracle Applications Production environment to other environments. Although, this technique is not supported by Oracle Support, yet we found a fairly high degree of success and this also helped us pursue our development and testing efforts. Also, this procedure applies to the May release (11.5.1) of Oracle Applications. The architecture has changed slightly with releases 11.5.2 and 11.5.3. (The Web DB listeners have been replaced by an Apache Listener). Accordingly, the procedures may have to be modified to suit individual site requirements. At Legerity, our architecture is a multi-node with two nodes. About Legerity Inc. Legerity (www.legerity.com) is a communication integrated circuit (IC) company providing system solutions that accelerate the deployment of integrated voice and data networks. Legerity combines IC design expertise and unique process technology with global applications support for leading communication OEMs worldwide.

10

About The Author Raman Batra has over 6 years experience with Oracle systems in different roles ranging from Application Development, Project Management, Disaster Recovery, Database Architecture and Administration. He has worked with a variety of ERP implementations on Oracle including Lawson, Peoplesoft and Oracle Applications. Currently Raman is working on an Oracle Apps 11i implementation in Austin, TX as a DBA Manager. An Oracle Certified Professional DBA, he has co-authored "Using Oracle8", Que., (1998) and is an active presenter at several Oracle conferences. He can be reached at batrahome@yahoo.com.

11

Appendix A

Table 7. Files To Be Edited After An Instance Refresh

Filename Owner Port SID Path Host

$ORACLE_HOME/SID.env (8.1.6) oracle - Yes Yes - $ORACLE_HOME/SID.env (8.0.6) oracle - Yes Yes - $ORACLE_HOME/DB.env (8.1.6) oracle - Yes Yes - $ORACLE_HOME/DB.env (8.0.6) oracle - Yes Yes - $ORACLE_HOME/ORACLE.env (8.1.6) oracle - - Yes - $ORACLE_HOME/ORACLE.env (8.0.6) oracle - - Yes - *$WEBDB /SID.env oracle - Yes Yes - *$WEBDB/DB.env oracle - Yes Yes - *$WEBDB/ORACLE.env oracle - Yes Yes - $HOME/applmgr/SID.env applmgr - Yes Yes - $HOME/sid81.env oracle - Yes Yes - $HOME/sid80.env oracle - Yes Yes - $APPL_TOP/APPSORA.env applmgr - Yes Yes - $APPL_TOP/APPLSYS.env applmgr Yes Yes Yes - $APPL_TOP/SID.env applmgr Yes Yes Yes - $ORACLE_HOME/tools/web60/html/runform.htm (8.0.6) oracle Yes - - Yes $ORACLE_HOME/tools/web60/html/runrep.htm (8.0.6) oracle Yes - - Yes $ORACLE_HOME/forms60_server (8.0.6) oracle - Yes $ORACLE_HOME/reports60_server (8.0.6) oracle Yes - Yes Yes $APACHE_TOP/Jserv/etc/jserv.conf oracle Yes - Yes Yes $APACHE_TOP/Jserv/etc/jserv.properties oracle Yes - Yes Yes $APACHE_TOP/Jserv/etc/zone.properties oracle - - Yes - $APACHE_TOP/Apache/bin/apachectl oracle Yes - Yes - $APACHE_TOP/Apache/bin/apachectl oracle Yes - Yes - $APACHE_TOP/Apache/conf/httpd.conf oracle Yes - Yes Yes $COMMON_TOP/html/bin/appsweb.cfg oracle Yes Yes - Yes $COMMON_TOP/portal/aplogon.html applmgr Yes Yes Yes Yes $COMMON_TOP/admin/install/adgendbc.sh applmgr Yes Yes Yes Yes $COMMON_TOP/portal/logon_s.html Oracle Yes Yes Yes Yes $COMMON_TOP/portal/appetmp.html oracle - Yes Yes - $COMMON_TOP/portal/applist.html oracle - Yes Yes - $APPL_TOP/admin/adconfig.txt applmgr - Yes Yes - $APPL_TOP/admin/adovars.env applmgr - - Yes - $APPL_TOP/admin/topfile.txt applmgr - - Yes - $APPL_TOP/fnd/11.5.0/secure/node_sid.dbc applmgr - Yes - Yes $TNS_ADMIN/listener.ora (8.0.6) oracle Yes Yes Yes Yes $TNS_ADMIN/listener.ora (8.1.6) oracle Yes Yes Yes Yes $TNS_ADMIN/tnsnames.ora (8.0.6) oracle Yes Yes Yes Yes $TNS_ADMIN/tnsnames.ora (8.1.6) oracle Yes Yes - Yes *$WEBDB/network/admin/tnsnames.ora oracle Yes Yes - Yes ♣$SCRIPTS/adalnctl.sh oracle - Yes Yes - ♣$SCRIPTS/adapcctl.sh oracle - Yes Yes -

12

♣$SCRIPTS/adcmctl.sh applmgr - Yes Yes - ♣$SCRIPTS/addbctl.sh oracle - Yes Yes - ♣$SCRIPTS/addlnctl.sh oracle - Yes Yes - ♣$SCRIPTS/adfmcctl.sh oracle Yes Yes Yes - ♣$SCRIPTS/adfmsctl.sh oracle Yes Yes Yes - ♣$SCRIPTS/adfractl.sh applmgr Yes Yes Yes - ♣$SCRIPTS/adfroctl.sh oracle Yes Yes Yes - ♣$SCRIPTS/adrepctl.sh oracle Yes Yes Yes - ♣$SCRIPTS/adtcfctl.sh applmgr Yes Yes Yes - ♣$SCRIPTS/adwdbctl.sh oracle Yes Yes Yes - ♣$SCRIPTS/adwlnctl.sh oracle Yes Yes Yes - $PAY_TOP/vendor/quantum (link) applmgr - - Yes - $ORACLE_BASE/admin/SID/pfile/initSID.ora oracle - Yes Yes - $ORACLE_HOME/dbs/initSID.ora (linked to above) oracle - Yes Yes - $ORACLE_HOME/listener/cfg/wdbsvr.app (8.0.6) oracle - Yes - - *$WEBDB/listener/cfg/wdbsvr.app oracle - Yes - - $ORACLE_HOME/listener/cfg/wdbsvr.cfg (8.0.6) oracle - - Yes - $WEBDB/listener/cfg/wdbsvr.cfg oracle - - Yes - $OA_MEDIA/logo.gif applmgr - Yes - - $OA_HTML/US/ICXINDEX.htm applmgr - Yes - - $APPL_TOP/admin/SID (directory) applmgr - Yes - - $WEBDB/bin/wdblsnr.ctl oracle - - Yes - $WEBDB/bin/wdbstart oracle - - Yes - $ORACLE_HOME/reports60/server/Rep60<SID>.ora (8.0.6)

oracle - - Yes -

$ORACLE_HOME/reports60/server/CGIcmd.dat (8.0.6) oracle - - Yes - $ORACLE_HOME/tools/web60/html/runform.htm (8.0.6)

oracle Yes - - Yes

$ORACLE_HOME/tools/web60/html/runrep.htm (8.0.6) oracle Yes - - Yes $ORACLE_HOME/forms60_server (8.0.6) oracle - Yes

Note: This is a comprehensive list of files, and some of these files exist on both Database/Concurrent processing stack as well as Forms/Web Server Stack. Editing some files on a stack may be redundant and may vary depending upon your architecture, however all files are listed above for completeness. * We have a custom environment variable called $WEBDB. An example of $WEBDB in our environment is /u01/app/oracle/product/webdb. This file system contains a TNS_ADMIN folder which is used by the webdb listener. ♣ $SCRIPTS=$COMMON_TOP/admin/scripts