ORACLE APPLICATIONS R12 ARCHITECTURE

• Oracle E-Business Suite Release-12 have a Multi-tiered Architecture, that supports Oracle Applications products.
• They are comprised of a Database Tier which manages the Oracle Database and stores all data.
• An Application Tier hosts various servers, manages communication between the desktop and database tier and contains the application file system.
• A Client Desktop through which user access Oracle Applications.

                                              Architecture-R11i vs R12

1. Desktop Tier

• The client interface is provided through HTML for HTML-based applications, and via a Java applet in a Web browser for the traditional Forms-based applications.
• In Oracle Applications Release 12, each user logs in to Oracle Applications through the E-Business Suite Home Page on a desktop client web browser.
• The E-Business Suite Home Page provides a single point of access to HTML-based applications, Forms-based applications, and Business Intelligence applications.
• Oracle JInitiator will no longer be required to run Oracle Forms in E-Business Suite Release 12.
• Oracle Forms in Release 12 will run directly in the native Sun Java2 Standard Edition plug-in.
• The Forms client applet is a general-purpose presentation applet that supports all Oracle Applications Forms-based products, including those with customization and extensions.
• The Forms client applet is packaged as a collection of Java Archive (JAR) files.
• The JAR files contain all Java classes required to run the presentation layer of Oracle Applications forms.

2. Application Tier

• The application tier has a dual role, hosting the various servers and service groups that process the business logic, and managing communication between the desktop tier and the database tier.
• This tier is sometimes referred to as the middle tier.
• Four servers or service groups comprise the basic application tier for Oracle Applications:

1. Web services
2. Forms services
3. Concurrent Processing server
4. Admin server

3. Database Tier

• The database tier contains the Oracle database server, which stores all the data maintained by Oracle Applications.
• The database also stores the Oracle Applications online help information. More specifically, the database tier contains the Oracle data server files and Oracle Applications database executable that physically store the tables, indexes, and other database objects for your system.
• The database server does not communicate directly with the desktop clients, but rather with the servers on the application tier, which mediate the communications between the database server and the clients.

Compiling Objects Manually Through SQL Commands

First find the Invalid Objects in the Database by below given query.

SELECT COUNT(*)
FROM DBA_OBJECTS
WHERE STATUS = ‘INVALID’;

For a more detailed query, use the following script :

SELECT OWNER, OBJECT_TYPE, COUNT(*)
FROM DBA_OBJECTS
WHERE STATUS = ‘INVALID’
GROUP BY OWNER, OBJECT_TYPE;

To recompile an individual object, connect to SQL*PLUS as the owner of the object (generally apps) and use one of the following depending on the object type :

alter package <package_name> compile; (package specification)
alter package <package_name> compile body; (package body)
alter view <view_name> compile; (view)

If the object compiles with warnings, use either of the following to see the errors that caused the warnings :

show errors
OR
select * from user_errors where name = ‘<OBJECT_NAME>’;

Compiling Objects Through ADADMIN Utility

1. Login OS with APPS owner.

2. Start the ADADMIN Utility from the Unix prompt with this command :

$adadmin

3. Under the Maintain Applications Database Objects Menu, select Compile APPS schema(s)
 

Step 1. Setup the profile value at user level with the following value

Profile name: “Initialization SQL Statement – Custom”

User: [%User Name from which Concurrent program Runs%]

Profile value:

BEGIN FND_CTL.FND_SESS_CTL(”,”,’TRUE’,’TRUE’,”,’ALTER SESSION SET TRACEFILE_IDENTIFIER = abc MAX_DUMP_FILE_SIZE = 5000000 EVENTS =’||””||’ 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12’||””);END;

Step 2. Find out where the trace file resides in the DB.

Goto Help -> Diagnosics -> Trace.

enable trace.

popup will show the server path where the trace will get create. Usually .trc file will get created in DB server.

The file path may be say “/u01/app/oracle/admin/prod/udump/PROD_ora_15698_abc.trc”.

the path will be stored along with the trc file name. Usually the value in the profile value TRACEFILE_IDENTIFIER=AKONDURU is used in the trace file naming

Step 3. Now we have enabled trace for your user.

Step 4. Login to the DB server. extract the file and convert to readable format.

Go to the following path in the DB server -> ‘/u01/app/oracle/admin/PROD/udump/’. Now, You have to convert it (tkprof) to make it readable. Use the following command to do so.

tkprof (input).trc output.txt EXPLAIN=()

where input.trc is the trace file and output.txt is in readable format

Step 5. After you get the trace file. make sure to remove the profile value that you have set for the profile : “Initialization SQL Statement – Custom”.

HOW to Verify and Change oc4jadmin Password

Step 1. Run the below command as applmgr user to verify oc4jadmin Password:

$ java -jar $IAS_ORACLE_HOME/j2ee/home/jazn.jar -checkpasswd jazn.com oc4jadmin -pw *****
Successful verification of user/password pair.

***** = oc4jadmin password

If the message is not successful then password can be changed through system-jazn-data.xml file:

Step 2. Shutdown all opmn services :

cd $ADMIN_SCRIPTS_HOME
adstpall.sh / adopmnctl.sh stopall

Step 3. $cd $ORACLE_HOME/j2ee/home/config

Here ORACLE_HOME= Oracle Application server home, ie, 10.1.3 HOME
Take a backup of system-jazn-data.xml and edit the below content:

<user>
<name>oc4jadmin</name>
<display-name>OC4J Administrator</display-name>
<guid>93E5A2505D1511DEBF8E89BC12E10097</guid>
<description>OC4J Administrator</description>
<credentials>!newpassword</credentials>
</user>

Marked in bold is the New Password to be changed . Note an ! mark has to prefixed with the password.

Step 4. Start all opmn services.

Run autoconfig is after this , password changes to encrypted format.