Release 11i – 11.5.10.2
Release 12
Client Tier
1)R12 Replaces Jinitiator (oajinit.exe)
2)Sun’s 1.5 Java Runtime Environment (JRE)
3)Repacked into oaj2se.exe
4)Netscape support for Applications and ADI
Database Tier
1)10g Release 2 ORACLE_HOME
2)Oracle Database (Enterprise Edition)
3)XDK -Database
4)XDB - Database
5)Workflow
6)InterMedia option
7)Spatial option
8)Data Mining option
9)JDK 5.0 to support Autoconfig
Application Tier
1)OracleAS 10g 10.1.2 for Forms & Reports Services
Replaces the 8.0.6-based Oracle_Home
2)OracleAS 10g 10.1.3 for Oracle Containers for Java (OC4J)
Replaces the 8.1.7-based Oracle_Home provided by iAS 1.0.2.2 in 11i
3)JDBC 10.2
4)JDK 1.5 for web & concurrent processing
5)Servlet Container: JServ -> OC4J(OC4J is Oracles J2EE container)
6)Apache: 1.3.19 -> 1.3.31
7)Forms/Reports: 6i -> 10g
Application Server 10.1.3
1)The Java Oracle Home
2)HTTP Listener
3)Oracle Containers for J2EE (OC4J)
4)Oracle Process Manager and Notification Server
5)Application Server Control (ASControl)
6)JDK 5.0
Application Server 10.1.2
1)The Forms or ‘C’ Oracle Home
2)Forms and Reports
3)Delivers native runtime executables for
Forms (frmweb)
Reports (rwrun)
4)No relinking of native executables. User exists (Applications C Code) is now dynamically linked at runtime.
5)10.1 Required Support Files (RSF’s)
Another Look
==========
few major technical difference.
Database:
Database Version in 11i (11.5.9 & 11.5.10) was 9i Rel 2 where as in Release 12 its 10g R2 (10.2.0.2)
Application Tier:
Tech Stack in Application Tier consist of iAS(1.0.2.2.2) & Developer 6i (Forms & Reports 8.0.6) but in Applications R12 it is build on Fusion Middleware (10g Web Server and 10g Forms & Reports)
Sub component in Application Tier
A) HTTP Server or Web Server in R12 is Version 10.1.3 which is built on Apache version 1.3.34. In apps 11i it is Version 1.0.2.2.2 built on Apache Version 1.3.19
B) Jserv in apps 11i is replaced by OC4J (mod_jserv is replaced by mod_oc4j)
C) Forms Version 6i in Apps 11i is replaced by Forms 10.1.2.0.2 in R12
D) Reports Version 6i in Apps 11i is replaced by Reports 10.1.2.0.2 in R12
E) JDBC version is changed from version 9 in apps 11i to version 10.2.0 in Apps R12
F) modplsql or mod_pls is removed from Apps R12 (What will happen to my mod plsql applications- coming soon* )
G) Java processes use JDK/JRE version 1.5.0 in R12 against JDK version 1.3.1 or 1.4.2 in Apps 11i
H) For various environment variable changes check below picture
I) New top INSTANCE_TOP added in Release 12 for configuration and log files
If you are familiar with Oracle Apps 11i , you can easily understand picture on your right. This is file system for 11i with various TOP's , APPL_TOP, ORA_TOP, COMMON_TOP, DB_TOP and DATA_TOP. With Multiple Middle Tier configuration came shared APPL_TOP (only APPL_TOP used to be shared ) . After shared APPL_TOP came shared Application Tier (All three TOP's on Application Tier, APPL_TOP, ORA_TOP and COMMON_TOP were shared across servers). With this came challenge of configuration files which are specific to a server mainly iAS & 806 configuration file. If you have configured Shared Application Tier (sharing ORA_TOP as well) in 11i then this problem was overcome by creating conf directory in COMMON_TOP.
In Oracle Apps R12, You can see new TOP called INSTANCE_TOP in Application Tier. This TOP will now hold any configuration files (specific to that server) , Certificates (If SSL is enabled SSL Certificates & any other certificates specific to that server) and related log files or pid files (for Apache or any other process). In diagram tops with <>ST can be shared across servers (Shared Tier) and INSTANCE_TOP will be specific to Server.
Next three pictures are taken from Ivo Dujmovic's presentation at Oracle Open World "Deep Dive: Oracle E-Business Suite Release 12 New Technology Stack". These Pictures are self explanatory & will help you in understanding Oracle Apps R12 File System.
This shows Oracle E-Business Suite Release 12 File System Layout
This shows Directory/File Structure for Instance TOP in R12
Yet Another View
==============
R12 10g iAS Techstack Directory Structure Changes
The need to separate Oracle Apps into three parts
Also, in a shared file system, MUTEX files, related to Apache, cause access related problems as IAS_ORACLE_HOME is mounted on NFS.
With the new file structure, this issue is also resolved as all the configuration files can be stored on the local server instead of NFS.
A general overview of the Middle-tier and DB directory structure
Notice that in the new R12 directory structure, the above dir locations do not contain the $TWO_TASK.
11i:
Changes in the env file naming convenstion and environment variables.
Instance top contains all the config files, log files, ssl certificates, document root etc. This is a new directory introduced in R12TS. Addition of this directory makes the middle-tier more organised, since data is kept seperate from config/log files. Another advantage is that, multiple instances can easily share the same middle tier / DB. To create a new instance that shares an existing middle-tier, just create a new instance_top with proper config files and nfs mount the middle tier in the server.
adpatch requires a few files created by adconfig to be present on the $APPL_TOP. Hence, the node where patches are applied to the env (INSTANCE-3), $APPL_CONFIG_HOME is set to $APPL_TOP. So, in this node, when adconfig is run, the config files for this env are generated on the central appltop (and not its instance top)
For all other shared instances (1, 2, 4), $APPL_CONFIG_HOME should be set to their respective instance tops so that the config files are generated/read from $INST_TOP/appl which enables you to easily have custom config files for each env.
All the AD Scripts for managing the middle-tier services are moved to instance top
For standalone instances, $APPL_CONFIG_HOME is set to $APPL_TOP.
In that case, the config files will be in the usual location ($APPL_TOP/admin).
A small set of files created by autoconfig, that are used by adpatch, are still requried to be in APPL_TOP (Context variable s_appl_config_home).
Hence, in a multinode environment, $APPL_CONFIG_HOME should be set to $APPL_TOP in the node where adpatch will be run.
While configuring wallet, SSL certificates to be placed under $INST_TOP/certs
certs is the default directory for SSL or any other certificate files used by this instance.
To use a centrally staged certificate, change the appropriate context file and run autoconfig
All Log file locations have changed. They are now placed under the Instance top
Oracle offers a new method for reporting diagnostic messages.
This new method, Oracle Diagnostic Logging (ODL), presents a common format for diagnostic messages and log files, and a mechanism for correlating all diagnostic messages from various components across Oracle Database.
Using ODL, each component logs messages to its own private local repository. A tool called LogLoader collects messages from each repository and loads them into a common repository where messages can be viewed as a single log stream, or analyzed in different ways.
For more info, check this link
Components:
Logging configuration:
$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/
httpd.conf
This is a server configuration file which typically contains directives that affect how the server runs, such as user and group IDs it should use, and location of other files.
apps.conf
Contains alias to html,media,temp etc (E-biz settings)
dms.conf
Oracle iAS DMS configuration file. This config file enables you to monitor performance of site components with Oracle’s Dynamic Monitoring Service (DMS).
mod_oc4j.conf
OC4J Apache module config file. Usually a stub.
oracle_apache.conf
Oracle Specific HTTP server configuration file. Used for including other config files
security.conf
Used for loading security modules
$ORA_CONFIG_HOME/10.1.3/config/
ias.properties
iAS related properties in this file, like Apache home locaiton, version, server etc.
$ORA_CONFIG_HOME/10.1.3/javacache/admin/
javacache.xml
Javacache xml config files for oacore apps
$ORA_CONFIG_HOME/10.1.3/j2ee/forms/config/
j2ee-logging.xml
Logging configuration file for OC4J
application.xml
Global Application configuration file for forms application
jms.xml
JMS Configuration file for forms application
oc4j-connectors.xml
Connector Configuration file for forms application
oc4j.properties
OC4J properties file. Various parameters like log filenames etc are specified here.
rmi.xml
RMI Configuration file for forms application. RMI stands for Remote Method Invocation. (The Java RMI system allows an object running in one Java Virtual Machine to invoke methods on an object running in another VM)
server.xml
Various directory locations are specified in this file
system-application.xml
This is the global application config file that is the parent for all other applications on the server. This file imports and loads various web modules
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/oa_servlets/
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/html/
orion-web.xml
Replacement for zone.properties. The same file is located in both the above oa_servlets and html directories
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/
orion-application.xml
Used for applications level configuration. Used for specifying applications.log file location, OC4J connector context file etc.
$ORA_CONFIG_HOME/10.1.3/network/$TWO_TASK
tnsnames.ora
Apache’s tnsnames.ora file.
$ORA_CONFIG_HOME/10.1.2/forms/server
appsweb.cfg ($FORMS_WEB_CONFIG_FILE)
appsweb.cfg moved to this location. Contains info on serverName, serverPort etc
default.env
Contains most of the env variables (classpath, product tops, oracle home etc)
$ORA_CONFIG_HOME/10.1.2/network/admin
tnsnames.ora
Contains tns entries for fndsm, db etc
listener.ora
Middle-tier Oracle home listener.ora file
It is highly recommended that configuration changes should be done in the context file and then run adconfig. Manually changing configuration files will most likely get lost once you run AutoConfig. Also making changes to the wrong file may cause problems. The context file should be the place to make changes. These wont get lost once you run AutoConfig and the customization variables should apply the changes to the correct place.
The most commonly used customization variable in your environments would probably be s_oacore_prepend_classpath.
This variable can be used to preprend custom directories, jar or zip files to the oacore classpath.
To add a single directory is easy. Set s_oacore_prepend_classpath to /home/myname/myclassesdir. If you want multiple entries then is is a little more complicated. The format is:
The orion_application.xml template file contains:
e.g.: it already has the start and end tags. So the first entry in the variable starts with just the directory/file name and ends with a closing tag, and the last entry in the list omits the end tag. The others, if there are any, are complete format.
(To get a clear picture, replace the red part in the above library tag with the red part in CDATA and you will see that it forms 3 properly structured tags)
Other customizations you may require are:
s_oacore_prepend_ld_lib_path
s_oacore_append_classpath
s_oacore_jvm_start_options
s_adovar_classpath
s_adovar_afclasspath
s_adovar_ldlib
For jsp development you may need to change setting for:
s_jsp_cache_dir
s_jsp_dbg_mode (default is false)
s_jsp_main_mode (default is justrun, you may need recompile)
The $AD_TOP/admin/template/adctxinf.tmp file contains descriptions of the context variables. This file is used to show the context variable descriptions when editing the context file via OAM.
- Why the New File Structure?
- File System Changes
- JAVA_TOP Restructured
- Environment Variables
- Instance Top
- AD Scripts
- Config Files
- SSL Certificates
- Various Log Files
- XML Configuration Files
- opmn.xml
- server.xml
- orion-application.xml
- orion-web.xml
- appsweb.cfg
- ODL – Oracle Diagnostic Logging
- OPMN – Oracle Process Manager and Notification server
- OPMN – Log Files
- Apache Log Files (Text)
- Apache Log Files (ODL)
- OC4J Log files (Text)
- OC4J Log files (ODL)
- Apache Config Files
- Form Server Config Files
- MT Oracle Home Config Files
- How To Make Configuration Changes
Why the New File Structure?
The need to separate Oracle Apps into three parts
- Data
- Code
- Config
Also, in a shared file system, MUTEX files, related to Apache, cause access related problems as IAS_ORACLE_HOME is mounted on NFS.
With the new file structure, this issue is also resolved as all the configuration files can be stored on the local server instead of NFS.
File System Changes
A general overview of the Middle-tier and DB directory structure
FILESYSTEM CHANGES | ||
APPMGR | ||
OLD | NEW | |
APPL_TOP | $HOME/ | $HOME/apps/apps_st/appl |
COMMON_TOP | $HOME/ | $HOME/apps/apps_st/comn |
ORACLE_HOME | $HOME/ | $HOME/apps/tech_st/10.1.2 |
IAS_ORACLE_HOME | $HOME/ | $HOME/apps/tech_st/10.1.3 |
ORACLE | ||
OLD | NEW | |
ORACLE_HOME | $HOME/ | $HOME/db/tech_st/10.2.0 |
ORADATA | $HOME/ | $HOME/db/apps_st/data |
INSTANCE TOP | ||
OLD | NEW | |
INST_TOP | N/A | $HOME/inst/apps/ |
JAVA_TOP Restructured
11i:
- $JAVA_TOP = $COMMON_TOP/java
- Class
- Archives
- $JAVA_TOP = $COMMON_TOP/java/classes
- Classes
- $AF_JLIB = $COMMON_TOP/java/lib
- Archives
Environment Variables
Changes in the env file naming convenstion and environment variables.
OLD | |
Env Source File | APPSORA.env |
Context File (MT) | $APPL_TOP/admin/$TWO_TASK.xml |
OA_HTML | $COMMON_TOP/html |
JAVA_TOP, OA_JAVA | $COMMON_TOP/java |
AF_JLIB | N/A |
JAVA_BASE | N/A |
FND_SECURE | $FND_TOP/secure/ |
ADMIN_SCRIPTS_HOME | $COMMON_TOP/admin/scripts/ |
LOG_HOME | $APPL_TOP/admin/ |
FORMS_WEB_CONFIG_FILE | N/A |
NEW | |
Env Source File | APPS $ORA_CONFIG_HOME/10.1.2/$TWO_TASK.env $APPL_CONFIG_HOME/$TWO_TASK.env |
Context File (MT) | $APPL_CONFIG_HOME/admin/$TWO_TASK.xml |
OA_HTML | $COMMON_TOP/webapps/oacore/html |
JAVA_TOP, OA_JAVA | $COMMON_TOP/java/classes |
AF_JLIB | $COMMON_TOP/java/lib |
JAVA_BASE | $COMMON_TOP/java/ |
FND_SECURE | $INST_TOP/apps/fnd/12.0.0/secure/ |
ADMIN_SCRIPTS_HOME | $INST_TOP/admin/scripts/ |
LOG_HOME | $INST_TOP/logs |
FORMS_WEB_CONFIG_FILE | $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg |
Instance Top
Instance top contains all the config files, log files, ssl certificates, document root etc. This is a new directory introduced in R12TS. Addition of this directory makes the middle-tier more organised, since data is kept seperate from config/log files. Another advantage is that, multiple instances can easily share the same middle tier / DB. To create a new instance that shares an existing middle-tier, just create a new instance_top with proper config files and nfs mount the middle tier in the server.
adpatch requires a few files created by adconfig to be present on the $APPL_TOP. Hence, the node where patches are applied to the env (INSTANCE-3), $APPL_CONFIG_HOME is set to $APPL_TOP. So, in this node, when adconfig is run, the config files for this env are generated on the central appltop (and not its instance top)
For all other shared instances (1, 2, 4), $APPL_CONFIG_HOME should be set to their respective instance tops so that the config files are generated/read from $INST_TOP/appl which enables you to easily have custom config files for each env.
INSTANCE TOP – STRUCTURE | |
$INST_TOP: | |
/admin | |
/scripts | ADMIN_SCRIPTS_HOME: Find all AD scripts here |
/appl | APPL_CONFIG_HOME. For standalone envs, this is set to $APPL_TOP |
/fnd/12.0.0/secure | FND_SECURE: dbc files here |
/admin | All Env Config files here |
/certs | SSL Certificates go here |
/logs | LOG_HOME: Central log file location. All log files are placed here (except adconfig) |
/ora | ORA_CONFIG_HOME |
/10.1.2 | ‘C’ Oracle home config, Contains tnsnames and forms listener servlet config files |
/10.1.3 | Apache & OC4J config home, Apache, OC4J and opmn This is the ‘Java’ oracle home configuration for OPMN, Apache and OC4J |
/pids | Apache/Forms server PID files here |
/portal | Apache’s DocumentRoot folder |
AD Scripts
All the AD Scripts for managing the middle-tier services are moved to instance top
AD SCRIPTS | |
$ADMIN_SCRIPTS_HOME: $INST_TOP/admin/scripts | |
adautocfg.sh | run autoconfig |
adstpall.sh | stop all services |
adstrtal.sh | start all services |
adapcctl.sh | start/stop/status Apache only |
adformsctl.sh | start/stop/status OC4J Forms |
adoacorectl.sh | start/stop/status OC4J oacore |
adopmnctl.sh | start/stop/status opmn |
adalnctl.sh | start/stop RPC listeners (FNDFS/FNDSM) |
adcmctl.sh | start/stop Concurrent Manager |
gsmstart.sh | start/stop FNDSM |
jtffmctl.sh | start/stop Fulfillment Server |
adpreclone.pl | Cloning preparation script |
adoafmctl.sh | Xbuild6+ introduces adoafmctl.sh to start/stop/status OC4J oafm (webservice, mapviewer) ascontrol to come later |
adexecsql.pl | Execute sql scripts that update the profiles in an AutoConfig run |
java.sh | Call java executable with additional args, (used by opmn, Conc. Mgr) |
Config Files
For standalone instances, $APPL_CONFIG_HOME is set to $APPL_TOP.
In that case, the config files will be in the usual location ($APPL_TOP/admin).
A small set of files created by autoconfig, that are used by adpatch, are still requried to be in APPL_TOP (Context variable s_appl_config_home).
Hence, in a multinode environment, $APPL_CONFIG_HOME should be set to $APPL_TOP in the node where adpatch will be run.
CONFIGURATION FILES | |
$APPL_CONFIG_HOME/admin | |
topfile.txt | product top info |
adjareas.txt | adjareas.txt |
adjborg.txt | adjborg.txt |
adjborg2.txt | adjborg2.txt |
adovars.env | adovars.env |
adconfig.txt | AD tools related parameters |
context file | Context file |
SSL Certificates
While configuring wallet, SSL certificates to be placed under $INST_TOP/certs
certs is the default directory for SSL or any other certificate files used by this instance.
To use a centrally staged certificate, change the appropriate context file and run autoconfig
SSL CERTIFICATES | |
$INST_TOP/certs | |
/Apache/ewallet.p12 | |
/opmn/cwallet.sso | |
/opmn/ewallet.p12 | |
certs is the default directory for SSL or any other certificate files used by this instance. To use a centrally staged certificate, change the appropriate context file and run autoconfig |
Various Log Files
All Log file locations have changed. They are now placed under the Instance top
LOG FILES | |
Location of various log files | |
AD Script log files (adapcctl.sh,…) | $INST_TOP/logs/appl/admin/log |
CM Log Files ($APPLCSF/$APPLLOG) | $INST_TOP/logs/appl/conc/log |
AD tools log files (adpatch, …) | $APPL_CONFIG_HOME/admin/$TWO_TASK/log |
OPMN Log Files (Text & ODL) | $ORA_CONFIG_HOME/10.1.3/opmn/logs (Techstack team is trying to get this moved to $INST_TOP/logs/10.1.3/opmn) |
Apache Log Files (Text & ODL) | $INST_TOP/logs/10.1.3/Apache/ |
OC4J Log Files (Text) | $INST_TOP/logs/10.1.3/j2ee/oacore/ |
OC4J Log Files (ODL) | $INST_TOP/logs/10.1.3/j2ee/oacore/log/oacore_default_group_1/oc4j |
XML Configuration Files
- opmn.xml
- server.xml
- orion-application.xml
- orion-web.xml
opmn.xml
- Used by Oracle Process Manager and Notification Server (OPMN)
- Contains details of all the OC4J instances deployed on the server
- Location of the log files for OPMN
- Various ports used by OPMN
- File Location: $ORA_CONFIG_HOME/10.1.3/opmn/conf/
server.xml
- •Used by OC4J
- •Contains details of all the Applications deployed under that OC4J instance
- •Details like name of the application, where it is deployed, shared libraries if any….
- •Path for the j2ee-logging configuration file, RMI configuration file, JMS configuration file….
- •Location: $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config/
orion-application.xml
- Used by application instance
- Contains details of all the web-modules deployed under that Application
- Also includes library path where it should look for the java code
- Location: $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/applications-deployment/oacore
orion-web.xml
- Used by web module
- Contains details of all servlet aliases and the mapping to servlet classes
- Location: $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/applications-deployment/oacore/html/
appsweb.cfg
- Forms Socket mode is not present in R12, only Servlet mode is available
- appsweb.cfg
- default.env (replacement of formservlet.ini in 11i)
- Location: $ORA_CONFIG_HOME/10.1.2/forms/server
- appsweb.cfg file’s location is also set in the env variable $FORMS_WEB_CONFIG_FILE
ODL – Oracle Diagnostic Logging
Oracle offers a new method for reporting diagnostic messages.
This new method, Oracle Diagnostic Logging (ODL), presents a common format for diagnostic messages and log files, and a mechanism for correlating all diagnostic messages from various components across Oracle Database.
Using ODL, each component logs messages to its own private local repository. A tool called LogLoader collects messages from each repository and loads them into a common repository where messages can be viewed as a single log stream, or analyzed in different ways.
For more info, check this link
OPMN – Oracle Process Manager and Notification server
OPMN or the Oracle Process Manager and Notification Server is used to manage the following Application server Components- HTTP Server and OC4J
- Oracle Notification Server (ONS)
- Responsible for communications among the components.
- Process Manager (PM)
- Responsible for start, stop, restart and death detection
- Location:
- $ORA_CONFIG_HOME/10.1.3/opmn/bin/opmnctl status (do not use this directly to start services)
OPMN – Log Files
Log files generated by OPMN are of two types:- Plain text
- Oracle Diagnostic Logging (ODL)
- opmn.log
- opmn.dbg
Components:
- internal
- ons
- pm
- none, fatal, error, warn, notify (Plain text)
- debug1, debug2, debug3, debug4 (Plain text)
- $ORA_CONFIG_HOME/10.1.3/opmn/logs
Apache Log Files (Text)
Apache Log files are defined in :- $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
- LogLevel (emerg, alert, crit, error, warn, notice, info, debug)
- ErrorLog
- CustomLog
- $INST_TOP/logs/10.1.3/Apache/
Apache Log Files (ODL)
To enable ODL logging for Apache, need to add the following directives in- $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
- OraLogMode (oracle, odl, apache)
- OraLogSeverity (INTERNAL_ERROR, ERROR, WARNING, NOTIFICATION, TRACE)
- Specify message level: 1-32 (1 most severe, 32 least)
OC4J Log files (Text)
OC4J Log files are defined in- $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployment/oacore/orion-application.xml
- $INST_TOP/logs/10.1.3/j2ee/oacore/
OC4J Log files (ODL)
Logging configuration:
- s_config_home/ora/10.1.3/j2ee/oacore/config/j2ee-logging.xml
- ERROR:1
- WARNING:1
- NOTIFICATION:1
- NOTIFICATION:16
- TRACE:1
- $INST_TOP/logs/10.1.3/j2ee/oacore/log/oacore_default_group_1/oc4j
Apache Config Files
$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/
httpd.conf
This is a server configuration file which typically contains directives that affect how the server runs, such as user and group IDs it should use, and location of other files.
apps.conf
Contains alias to html,media,temp etc (E-biz settings)
dms.conf
Oracle iAS DMS configuration file. This config file enables you to monitor performance of site components with Oracle’s Dynamic Monitoring Service (DMS).
mod_oc4j.conf
OC4J Apache module config file. Usually a stub.
oracle_apache.conf
Oracle Specific HTTP server configuration file. Used for including other config files
security.conf
Used for loading security modules
$ORA_CONFIG_HOME/10.1.3/config/
ias.properties
iAS related properties in this file, like Apache home locaiton, version, server etc.
$ORA_CONFIG_HOME/10.1.3/javacache/admin/
javacache.xml
Javacache xml config files for oacore apps
$ORA_CONFIG_HOME/10.1.3/j2ee/forms/config/
j2ee-logging.xml
Logging configuration file for OC4J
application.xml
Global Application configuration file for forms application
jms.xml
JMS Configuration file for forms application
oc4j-connectors.xml
Connector Configuration file for forms application
oc4j.properties
OC4J properties file. Various parameters like log filenames etc are specified here.
rmi.xml
RMI Configuration file for forms application. RMI stands for Remote Method Invocation. (The Java RMI system allows an object running in one Java Virtual Machine to invoke methods on an object running in another VM)
server.xml
Various directory locations are specified in this file
system-application.xml
This is the global application config file that is the parent for all other applications on the server. This file imports and loads various web modules
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/oa_servlets/
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/html/
orion-web.xml
Replacement for zone.properties. The same file is located in both the above oa_servlets and html directories
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/
orion-application.xml
Used for applications level configuration. Used for specifying applications.log file location, OC4J connector context file etc.
$ORA_CONFIG_HOME/10.1.3/network/$TWO_TASK
tnsnames.ora
Apache’s tnsnames.ora file.
Form Server Config Files
$ORA_CONFIG_HOME/10.1.2/forms/server
appsweb.cfg ($FORMS_WEB_CONFIG_FILE)
appsweb.cfg moved to this location. Contains info on serverName, serverPort etc
default.env
Contains most of the env variables (classpath, product tops, oracle home etc)
MT Oracle Home Config Files
$ORA_CONFIG_HOME/10.1.2/network/admin
tnsnames.ora
Contains tns entries for fndsm, db etc
listener.ora
Middle-tier Oracle home listener.ora file
How To Make Configuration Changes
It is highly recommended that configuration changes should be done in the context file and then run adconfig. Manually changing configuration files will most likely get lost once you run AutoConfig. Also making changes to the wrong file may cause problems. The context file should be the place to make changes. These wont get lost once you run AutoConfig and the customization variables should apply the changes to the correct place.
The most commonly used customization variable in your environments would probably be s_oacore_prepend_classpath.
This variable can be used to preprend custom directories, jar or zip files to the oacore classpath.
To add a single directory is easy. Set s_oacore_prepend_classpath to /home/myname/myclassesdir. If you want multiple entries then is is a little more complicated. The format is:
CDATA means character data. CDATA is the text that will NOT be parsed by a parser. Tags inside the text will NOT be treated as markup and entities will not be expanded. Hence the text inside the inner nested sqare brackets ([]) will not be treated as XML by the parser For more info on XML DTD, read this tutorial |
The orion_application.xml template file contains:
So the format for multiple entries has to take into consideration what already is in the template
e.g.: it already has the start and end tags. So the first entry in the variable starts with just the directory/file name and ends with a closing tag, and the last entry in the list omits the end tag. The others, if there are any, are complete
(To get a clear picture, replace the red part in the above library tag with the red part in CDATA and you will see that it forms 3 properly structured tags)
Other customizations you may require are:
s_oacore_prepend_ld_lib_path
s_oacore_append_classpath
s_oacore_jvm_start_options
s_adovar_classpath
s_adovar_afclasspath
s_adovar_ldlib
For jsp development you may need to change setting for:
s_jsp_cache_dir
s_jsp_dbg_mode (default is false)
s_jsp_main_mode (default is justrun, you may need recompile)
The $AD_TOP/admin/template/adctxinf.tmp file contains descriptions of the context variables. This file is used to show the context variable descriptions when editing the context file via OAM.
No comments:
Post a Comment