Oracle Apps Creating Custom Concurrent Managers:

- Define Combined Rule

nav: Concurrent:Manager:Rule
- Define workshift
nav: Concurrent:Manager:Workshifts

- Define Manager & attach combined rule + workshift
nav: Concurrent:Manager:Define
Note:
Cache Size=1 for long running jobs
Cache Size=4/5 for short running jobs

- Activate the manager
nav: Concurrent:Manager:Administer

- Exclude the combined rule from "Standard Manager"

nav: Concurrent:Manager:Define
Query the "Standard Manager"

- Submit any conc program that is part of combined rule
and check whether Custom Manager is Picking the request or not.
nav: Concurrent:Manager:Administer

AD Utilites Oracle Apps EBS

adadmin:


1. Generate Applications Files
adadmin 1-1. Generate message files
adadmin 1-2. Generate form files
adadmin 1-3. Generate report files (.rdf)
adadmin 1-4. Generate product JAR files (.jar)


2. Maintain Applications Files menu


adadmin 2-1. Relink Applications programs (To relink non-ad utilties)
ex: WFLOAD,FNDLOAD ....
adadmin 2-2. Copy files to destinations
(To copy the html & java files from COMMON_TOP to the _TOPs)
adadmin 2-3. Convert character set (ex: from US7ACII to UTF8)
adadmin 2-4. Maintain snapshot information
(The application files information is maintained in db tables.)
adadmin 2-5. Check for missing files
o/p file: $APPL_TOP/admin//out/admvrf.lst

3. Compile/Reload Applications Database Entities menu


adadmin 3-1. Compile APPS schema
adadmin 3-2. Compile menu information
adadmin 3-3. Compile flexfields
adadmin 3-4. Reload JAR files to database

4. Maintain Applications Database Entities menu
adadmin 4-1. Validate APPS schema
o/p file: $APPL_TOP/admin//out/APPS.lst
adadmin 4-2. Re-create grants and synonyms for APPS schema
adadmin 4-3. Maintain multi-lingual tables
adadmin 4-4. Check DUAL table

5. Change Maintenance Mode
adadmin 5-1. Enable Maintenance Mode
adadmin 5-2. Disable Maintenance Mode


adident: It is to check Applicaton files version.
adrelink.sh : It is to relink ad utilites.
ex: adadmin, adpatch, adctrl ......

Upgrade 11i to R12 Oracle Apps EBS

(1) Upgrade 9i to 11g


- Take backup of complete Application system
- Apply latest AD patch (AD.I.6= p6502079...)
- Run TUMS utility(patch: 7705743)


The Upgrade Manual Script
- Apply IOP patch (p6328363..)
pre-requisite patches for IOP.
(3384350, 3453499,3180816,2368042,4489303,2864765,3882116,3262159)
- Apply the required Application patches
A.T.G patch(RUP6 = p5903765... -----> pre-requisite patch: 4489303),
P7456837(optional)
p7011280 & p9535311
pre-requisite patches: 6328363 or 6372396-(2032040,3313291,3764779)
- Install 11g s/w(11.1.0.6) & create env file
- Apply 11g patchset1 (11.1.0.7)---> (p6890831)
- UPgrade db 9i to 11g using dbua
- Enable autoconfig


(2) Upgrade EBS 11i to R12


- Install R12 in upgrade mode
- Now we can start the db with R12's 11g ORACLE_HOME
- Run AD preparation scripts(patch: 7197489)
- Apply AD 12.1.1 patch (upgrade driver patch: 7461070)
- Apply Maintenance Pack patch (driver= u6678700.drv)
cd $AU_TOP/patch/115/driver
ls u6678700.drv
adpatch options=nocopyportion,nogenerateportion
note:
in adctrl option 8 is hidden: It is to skip ad worker

Single Sign-on (Oracle apps EBS)

What is Single Sign-On Server (SSO) ?
As name says Single-Sign On Server is set of services (Software) which enables login to Application once which will allow you to login to Ppartner Applications with no need to login again. Lets assume I have configured single SSO Server for Portal , E-Business Suite, Collaboration Suite plus some other other applications, Now if I login to any one of them & after that if I wish to login to other applications I should be able to login without supplying passwords again.

How will I log off then ?

This is called as Single Sign-Off which is part of SSO server , If you logout from any one application SSO server will log off from all applications.


What are Technology Stack components of SSO Server ?

SSO consist of OC4J_Security & HTTP Server which are part of Oracle Identity Management which inturn part of Oracle Infrastructure Server which in turn part of Oracle Application Server. SSO server uses Oracle Internet Directory to store User Credentials in encrypted format for Partner Applications . If some one ask you to bounce SSO server , you bounce either of them or both . Oracle components uses mod_osso which is part of Oracle HTTP Server to connect to SSO server.


Partner Application & External Applications ?

As mentioned above lot of time about Partner Applications ; Partner Applications are the one which delegates their authentication to SSO server (like Portal, Discoverer, E-Business Suite, Collaboration Suite) where as External Applications are applications which don't delegate their authentication to SSO Server (like yahoo, google, hotmail applications).
What does delegating Authentication means here ? Delegating authentication means partner application will ask sso to verify if a user is authenticated properly or not where as external application will check username/password at their end sso server will simply hold username/password in OID (If users select remember external application password)


Request Flow when SSO is used ...

Very important to understand request flow when a application is configured with SSO & user tries to access Application .
1) User first time tries to access application (like portal, collabsuite, apps 11i) configured with sso server
2) Application checks that there is no login cookie set into User(Clients) browser so Application redirects it to Single Sign-On Server via mod_osso
3) Single Sign-On Server returns login page to user & user enter his/her username/password
4) SSO validates these password against one stored in Oracle Internet Directory
5) If password matches then SSO return a token to client with list of all applications which user has access and return client back to original application
6) This token is stored as part of cookie in user's/client's browser & further connections from client to applications will be allowed (as authentication token is already in cookie)

Test application connectivity in Oracle apps (EBS )

AOL/J Diagnostic test: To test the application connectivity & to verify .dbc file & its settings. open the browser & enter the AOL/J Diagnosis URL ex: http://node105.apps.com:8005/OA_HTML/jsp/fnd/aoljtest.jsp Environment Type: non-rac Apps Schema name: apps Apps passwd: apps Oracle SID: PROD Hostname: node105.apps.com Port number: 1521 Click TEST Enter AOL/J setup test

DBC File in Oracle apps (EBS ) and EBS Login Flow

Q. What is *.dbc file & whats is location of dbc file ? dbc as name stands for is database connect descriptor file used to connect to database. This file by default located in $FND_TOP/secure directory also called as $FND_SECURE directory DBC file is quite important as whenever Java or any other program like forms want to connect to database it uses dbc file. Typical entry in dbc file is GUEST_USER_PWD APPS_JDBC_URL DB_HOST

EBS Configuration Files Oracle apps (EBS )

Services	Configuration File
Apache Server	httpd.conf
Form Server	appsweb.cfg
OPMN	opmn.xml
	server.xml
	orion-application.xml
	orion-web.xml
APPL_TOP Environment File	<contextname>.env
Consolidated Environment File	APPS<contextname>.env
Web Home Environment File	<contextname>.env
Tools ORACLE_HOME Environment File	<contextname>.env
	adovars.env

Oracle EBS Tracing

1)Tracing form based form:
->open the form:help:diagnostics:trace:trace with waits
-Trace will be generated in udump.
- perform some transaction
->Disable the trace
help:diagnostics:trace:notrace
->Use tkprof to convert the trace file to understandable format.
$cd $ORACLE_HOME/admin/PROD_node11/udump
2)Tracing html based form:
->Enable Diagnostic menu
nav:profile:system
profile: FND_Diagnostics
Site: Yes

->To trace html based application.
Click on diagnostics
Diagnostics: Set Trace Level
* Trace with waits
* Disable trace
-> Go to Udump & use tkprof
3)Tracing Concurrent Program:

nav: Concurrent:Program:Define (Query the CP. ex: Active Users)
* Enable Trace & save
- Run the CP
- Disable the trace & save
- Go to udump & use tkprof utility.

Oracle EBS Patch Management (Non-Interactive Mode)

- Applying patch in non-interactive mode:

                                File: $APPL_TOP/admin/<SID>/adalldefaults.txt

                                - Download the patch

                                - unzip the patch

                                - Go to patch dir & review README.txt doc

                                - Stop the appl services

                                - Enable Maintenance Mode

                                - Run adpatch

                                - Disable Maintenance Mode

                 Applying patch in non-interactive mode:

                                File: $APPL_TOP/admin/<SID>/adalldefaults.txt

                                - Download the patch

                                - unzip the patch

                                - Go to patch dir & review README.txt doc

                                - Stop the appl services

                                - Enable Maintenance Mode

                                - Run adpatch

                                - Disable Maintenance Mode

                                - Start the app services

                Patch History:

                                - We can check the patch history from

                (1) DB tables                                           (2) OAM

                - DB Tables:

                                (1) AD_BUGS: It contains the patches info that are applied by the installer &                                         also the patches info that are applied by user.

                                (2) AD_APPLIED_PATCHES: It contains the patches info that are applied by user.

                                (3) AD_PATCH_DRIVERS: It contains patch driver actions info(C,D,G).

                Note:

                                One-off   -> Kbs

                                Minipack -> mbs

                                Family pack -> mbs/gbs

                                Maintenance Pack -> gbs

                Saving Patch time:

                                - Apply the patch in non-interactive mode

                                Response file: $APPL_TOP/admin/<SID>/adalldefaults.txt

                                - Download & unzip the patch

                                - Review the README.txt doc

                                - Stop the app services

                                - Enable Maintenance Mode

                                - Run adpatch in non-int.. mode

                                                File: $APPL_TOP/admin/PROD/adalldefaults.txt

                                                Note:

                                                .lgi file contains informational messages

                                                (ie.. files copied, backed up)

                                - Check logfile & disable M.M

                                - Start the applcation services

                - Merging the patches (ex: NLS patches..)

                                Note: Patches are platfrom dependent & version dependent.

                                5 Languages

                                1 -base = US English

                                4 -(AR,UK,..)

                                ex: P12345

                                - Apply base lang patch (US English)

                                - Merge the NLS Patches...(4 patches)

                                utility :admrgpch

                                - Download the patches

                                - Create src & dest dir

                                - Go to src dir & unzip the patches

                                - Go to patch dir & review README.txt

                                - Merge the patches

                                - Stop the app services

                                - Enable Maintenance Mode

                                - Run adpatch in non-interactive mode

                                - Disable Maintenance Mode

                                - Start the app services

                - Skipping Patch driver actions:

                                Actions: C,D,G

                                $adpatch options=nodatabaseportion

                                $adpatch options=nocopyportion,nogenerateportion            // EBS Upgradation

                - Skipping Post patch activities:

                                Activities: Compiling invalid objects, compiling JSP, Running autoconfig ...

                                ex:

                                8457584  $adpatch options=nocompiledb,nocompilejsp,noautoconfig                (skip)

                                5474548 $adpatch options=nocompiledb,nocompilejsp,noautoconfig   (skip)

                                9589858 $adpatch options=compiledb,compilejsp,autoconfig             (Don't skip)

                - adpatch options:

                                                $adpatch preinstall=Yes  ( To upgrade ad utilites)

                                $adpatch options=hotpatch  (To apply hot patch. No downtime required)

                                                ex: Document Patches

                                $adpatch Apply=no (To run adpatch in testmode)

                - Checking Patch history using OAM:

                                - Login as SYSADMIN

                - Select "System Administrator" resp

                - nav: Oracle Applications Manager: Patching and Utilites

                ex:   codeline

                R12.0.x                    R12.A

                R12.1.x                    R12.B

                                                Product                    codelevel

                R12.0.4                    AD                           R12.AD.A.4

                R12.1.1                    AD                           R12.AD.B.1              --------->  R12.AD.B.3             

                Table: ad_trackable_entities

                -> Patch Wizard:

                                                It is a tool to create patch filters, download patches, analyze the patch impact ..

                                - nav: Oracle Applications Manager:DASHBOARD :

Oracle EBS Patch Management

                - Patch Tool Kit:

                                - adpatch

                                - adctrl

                                - admrgpch

                                - adadmin

                                - autoconfig

                - Types:

                                - One-Off               

                                - MiniPack

                                - Family Pack

                                - Maintenance Pack

- Uitlity: adpatch

                - Steps:

                                - Download the patch

                                - Unzip the patch

                                - Go to patch dir & review the README.txt doc

                                                * Patch Description

                                                * Pre-requisite info

                                                * How to apply the patch      

                                                * post install tasks

                                - Stop the application services

                                                $cd $ADMIN_SCRIPTS_HOME

                                                $./adstpall.sh apps/apps

                                - Enable Maintenance Mode

                                                adadmin 5-1

                                - Run adpatch to apply the patch

                                                Logfile: $APPL_TOP/admin/<SID>/log

                                                patch top location: /u02/9239089

                                                patch driver file: u9239089.drv

                                                no: of workers: 6

                                                - Open a terminal & login as applmgr

                                                - Run adctrl to check adworkers status

                                - After applying the patch check logfile

                                                $cd $APPL_TOP/admin/<SID>/log

                                - Disable Maintenance Mode

                                                adadmin 5-2

                                - Start the application services

                                                $cd $ADMIN_SCRIPTS_HOME

                                                $./adstrtall apps/apps

Oracle EBS AutoConfig

Autoconfig as name suggests is automated configuration of Oracle Applications 11i.

 Well if this is configuring oracle applications 11i question comes from where its getting configuration information. File from where Autoconfig runs picks parameter to configure 11i , in Oracle's terminology is called Context File. Power of configuring whole applications via this single file (One for Application Tier & other for Database Tier) makes this file quite powerful. Rest all I discuss in terms of questions answers or FAQ format about Autoconfig.
 
What is Autoconfig in 11i ?
Autoconfig is method of configuring Oracle Applications . All the information required to configure Oracle Apps 11i is stored in file called as Context file. So there are two context file, one for Database Tier & Second for Application Tier. Context file is repository for configuration stored in xml format. Its xml file and file name format is <SID>_<HOSTNAME>.xml so if your machine name is machine1 & SID is VISION then context file name will be VISION_machine1.xml
 
What are different Contexts w.r.t. Autoconfig in 11i ?
There are two context files, one for database tier called as Database Context second for Application tier called as Application Context.
 
What is location of Contexts file in 11i ?
Database Context file is under Database $ORACLE_HOME/appsutil/<SID>_<HOSTNAME>.xml
Application Context file is under $APPL_TOP/admin/<SID>_<HOSTNAME>.xml



How to run Autoconfig in 11i ?
You will use script adautocfg.sh (on both Database & Application tier) which inturn will call adconfig.sh , which further will calladconfig.pl. You should not worry about later two scripts its for information only. adautoconfig.sh is script which you use to run autoconfig.

 
Where to check log files after autoconfig is executed ?

•On database tier its under $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MM_DD_YYYY/adconfig.log

•On Application tier its under $APPL_TOP/admin/$CONTEXT_NAME/log/MMDDYYYY/adconfig.log

where CONTXT_NAME is <SID>_<HOSTNAME>
 
What if my Context file itself is corrupted, Can I create one ?
Yes you have utility called adbldxml to build xml file(Context File).
 
How to change some parameter in Context/xml file ?
If you are an expert then you can open xml file via any editor & change it but these days Oracle is recommending to use Context Editor or if you are on OAM.H or higher then use OAM (Oracle Application Manager) to change context file.

How to submit a concurrent request? Oracle apps (EBS )

- Using SRS(Standard Request Submission) form.

- Using SRS form we can

* submit a request

* View details

* view log

* view output

* Hold request

* Cancel request

...

- Steps:

- Open any form

- Go to menu bar-> view -> Requests -> Submit a new request -> Single request ....

FNCPASS UTILITY to Change password Oracle apps (EBS )

$ FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS WELCOME
$ FNDCPASS apps/apps 0 Y system/manager ORACLE GL GL1
$ FNDCPASS apps/apps 0 Y system/manager USER VISION WELCOME

Note: The FNDCPASS has a new mode, "ALLORACLE", in which all Oracle Application schema passwords can be changed in one call.
Apply the patch (Patch No# 4745998) to have this option, if not available currently with your Apps.
Syntax:
FNDCPASS 0 Y ALLORACLE
Example:
$ FNDCPASS apps/apps 0 Y system/manager ALLORACLE WELCOME


To change APPS/APPLSYS password, we need to give mode as SYSTEM
To change product schema passwords, i.e., GL, AP, AR, etc., we need to give mode as ORACLE
To change end user passwords, i.e., SYSADMIN, OPERATIONS etc., we need give mode as USER

Where the FNDCPASS utility is located?
Concurrent node @FND_TOP/bin