E business suite r12.2 changes for database administrators, outlining few major changes in R12.2 compared to previous releases.

1. E-Business suite R12.2 changes
for Database Administrators
Pavan Marti
Oracle Apps Consultant

2. ABOUT PYTHIAN
• Recognized Leader:
– Global industry-leader in remote database administration services and consulting for Oracle,
Oracle Applications, MySQL and Microsoft SQL Server
– Work with over 250 multinational companies such as Forbes.com, Fox Sports, Nordion and
Western Union to help manage their complex IT deployments
• Expertise:
– Pythian’s data experts are the elite in their field. We have the highest concentration of Oracle
ACEs on staff—9 including 2 ACE Directors—and 2 Microsoft MVPs.
– Pythian holds 7 Specializations under Oracle Platinum Partner program, including Oracle
Exadata, Oracle GoldenGate & Oracle RAC
• Global Reach & Scalability:
– Around the clock global remote support for DBA and consulting, systems administration,
special projects or emergency response
© 2015 Pythian Confidential2

3. AGENDA
• Architecture
• Installation
• Online Patching
• Password Management
• Apps Password change
• Configuration Management
• Customization
• Cloning
• OAM integration
© 2015 Pythian Confidential3

4. ARCHITECTURE
• Application with Dual
File System
a)Run
b)Patch
• Database uses Edition-
Based Redefinition
• WebLogic Server in E-
Business suite,
managed servers
replaced oc4j
components.

5. R12.2 FILE SYSTEM LAYOUT
• 10.1.2 OH holds the AS
components for Forms
and Reports
• Fusion Middleware
Home contains
WebLogic Server,
HTTP configuration
files
• INST_TOP contains
only maintenance
scripts

6. R12.2 FILE SYSTEM LAYOUT
• Fusion middleware home contains the following directories
– EBS_Domain: E-Business Suite weblogic domain, contains all domain-specific configuration and log files.
– wlserver_10.3: Binaries and libraries required to support WebLogic Server
– oracle_common: Java Required Files (JRFs) used by EBS.
– webtier: HTTP configuration and log files used by EBS.
– Oracle_EBS-app1: Contains configuration files related to oacore, forms, oafm, and forms-c4ws
• FS_NE contains files needed by both the file systems
– Patch staging area, ADOP log files & ADOP utility
• Not all log files are not stored under $INST_TOP
– HTTP log files are located under the native instance home ($FMW_HOME/webtier)
– Oracle WebLogic Server log files are located under the domain home ($EBS_DOMAIN_HOME)
– Concurrent processing log files are located on the none-editioned file system (fs_ne)

7. INSTALLATION
• Rapidwiz prompts
details for dual file
system
• Default startCD installs
JDK & JRE6
• Recommended to
download latest
startCD, provides JDK &
JRE7
• Latest startCD contains
bug fixes and helps in
easy installation

8. INSTALLATION
• Install 11g Cluster
before starting
RapidWiz
• Setup ASM Diskgroups
to host the datafiles on
ASM
• Provide Cluster nodes &
ASM Diskgroup details
during installation

9. ONLINE PATCHING
• ADOP utility is used for online patching
• New edition called PATCH edition is created during a patching cycle
• Cross-Edition Triggers enable data changed by online users propagate to patch
edition during a patching cycle
• Can apply patches directly to RUN edition using hotpatch option
• Can apply multiple patches simultaneously using merge option
• Fs_clone option clones the PATCH fs from RUN fs.
• Mandatory to Keep AD & TXK patchsets at same level
• AD patches are online, don’t need downtime.
• $APPL_TOP_NE/ad/custom/adop_sync.drv is used to sync CUSTOM Code

10. ONLINE PATCHING
• Prepare
– Synchronizes patch edition and run edition on the file system.
– Creates a new patch edition in the database.
• Apply
– Executes patch drivers to update patch edition.
– Patches applied: can be one or many, including customizations.
• Finalize
– Compiles invalid objects.
– Generates derived objects
• Cutover
– Configures patch edition file system & database to be the new run edition file system.
– Restarts application tier services.
• Cleanup
– Delete obsolete code and seed data to recover space.

11. PASSWORD MANAGEMENT
• FNDCPASS and AFPASSWD utilities can be used for setting Oracle E-Business Suite
schema passwords
• It is recommended that the FND_USER and FND_ORACLE_USERID tables are backed up
before system passwords (APPLSYS, APPS, APPS_NE) are changed
• AFPASSWD is an enhanced version of FNDCPASS, only prompts for passwords required
for the current operation.
AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] -f <FNDUSER> (Application Users)
AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] -o <ORAUSER> (Apps Product users)
AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] –a (All Apps Product users)
AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] -l <ORAUSER> <TRUE|FALSE> (Locks Single User)
AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] -L <TRUE|FALSE> (Locks non-essential users)
AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] -s <APPLSYS> (Changes APPLSYS)
AFPASSWD [-c <APPSUSER>[@<TWO_TASK>]] -m <HASH-MODE> [MIGRATE] (Migrated to non-
recoverable Hashing scheme passwords)

12. APPS PASSWORD CHANGE
• Shut down the application tier services
• Change the APPLSYS password using FNDCPASS or AFPASSWD utility.
• Start AdminServer using the adadminsrvctl.sh script from your RUN filesystem
• Update the “apps” password in WLS Datasource as follows:
– Log in to WLS Administration Console.
– Click Lock & Edit in Change Center.
– In the Domain Structure tree, expand Services, then select Data Sources.
– On the “Summary of JDBC Data Sources” page, select EBSDataSource.
– On the “Settings for EBSDataSource” page, select the Connection Pool tab.
– Enter the new password in the “Password” field.
– Enter the new password in the “Confirm Password” field.
– Click Save & Click Activate Changes in Change Center.
• Execute Autoconfig to update all application tier files
• Start all the application tier services using the adstrtal.sh script.

13. APPS PASSWORD CHANGE

14. APPS PASSWORD CHANGE
• Log in to WLS Administration Console, Under Domain Structure tree select Data Sources.
• On the “Summary of JDBC Data Sources” page, select EBSDataSource.
• On the “Settings for EBSDataSource” page, select Monitoring > Testing.
• Select “oacore_server1” & click Test DataSource
• Look for the message “Test of EBSDataSource on server oacore_server1 was successful”.

15. CONFIGURATION MANAGEMENT
• In R12.2 release, Autoconfig can perform limited set of configuration changes with the
introduction of Oracle WebLogic Server.
• Feedback Loop, mechanism to keep the OHS & WebLogic configuration changes in sync
with context file
• adRegisterWLSListeners tool performs automatic synchronization of context variables with
the corresponding Oracle WLS configuration, automatically stops if WLS Admin server is
shutdown.
• perl $AD_TOP/bin/adRegisterWLSListeners.pl contextfile= <context file>
• SyncContext tool is used for explicit synchronization of the context variables with the
WebLogic Server and Oracle HTTP Server configurations.
• Its capable of performing OHS server changes as well, needs Node Manager and the
WebLogic AdminServer to be up and running.
• perl $AD_TOP/bin/adSyncContext.pl contextfile=<CONTEXT_FILE>

16. OHS CONFIGURATION
• Seeded OHS configuration is managed using Fusion Middleware Control, leaving limited
change options to autoconfig.
• Changes needs to be reflected to context file to keep the database profile options in sync
with the changes.
• Following steps needs to be performed for changing the OHS protocol or port
number.
– Login to Oracle Fusion Middleware Control Console.
– Select Web Tier Target under EBS Domain.
– Select Administation > Advanced Configuration.
– Edit the relevant file to update the respective HTTP configuration parameter value.
– Run the following command on all application tier nodes:
– $ perl <AD_TOP>/bin/adSyncContext.pl contextfile=<CONTEXT_FILE>
– Run AutoConfig on all application tier nodes.

17. WLS CONFIGURATION
• Managing managed server configurations needs Weblogic administration console or WLST
tool.
• $AD_TOP/patch/115/bin/adProvisionEBS.pl utility can be used for
– Application server node addition/deletion
– Managed serer (addition/deletion/start/stop/enable/disable/property/startup parameters)
• Following command helps in getting the options of this utility
– perl $AD_TOP/patch/115/bin/adProvisionEBS.pl help -contextfile=$CONTEXT_FILE
– perl $AD_TOP/patch/115/bin/adProvisionEBS.pl help -contextfile=$CONTEXT_FILE -
option=<option>
• Following command helps in changing the server classpath of a managed server.
– perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl ebs-set-managedsrvproperty
-contextfile=<CONTEXT_FILE> -managedsrvname=<MANAGED SERVER NAME>
-managedsrvclasspath="<COMPLETE MANAGED SERVER CLASSPATH>”
• Following command helps in changing the JVM arguments of managed server.
– perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl ebs-set-managedsrvproperty
-contextfile=<CONTEXT_FILE> -managedsrvname=<MANAGED SERVER NAME>
-serverstartargs="<COMPLETE LIST OF JVM ARGUMENTS>"

18. WLS CONFIGURATION
• Following steps needs to be performed for changing the port numbers of managed
server
• Update WebLogic configuration through admin console.
– Log on to the WebLogic Server Administration Console, click unlock configuration changes and then servers
– Click on the respective managed server and Update the configuration parameters as needed.
– Click the 'Save' button to save the configuration changes.
– Once the customizations are complete and saved, click the Activate Changes
• From Run edition, perform below steps to remove entries in OHS configuration files
mod_wl_ohs.conf and apps.conf
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl
-contextfile=<CONTEXT_FILE>
-configoption=removeMS
-oacore=<host>.<domain>:<port>
-oafm=<host>.<domain>:<port>
-forms=<host>.<domain>:<port>
-formsc4ws=<host>.<domain>:<port>
-ekanban=<host>.<domain>:<port>
-accessgate=<host>.<domain>:<port>
-yms=<host>.<domain>:<port>

19. WLS CONFIGURATION
• Execute below command to add the managed server on new port.
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl
-contextfile=<CONTEXT_FILE>
-configoption=addMS
-oacore=<host>.<domain>:<port>
-oafm=<host>.<domain>:<port>
-forms=<host>.<domain>:<port>
-formsc4ws=<host>.<domain>:<port>
• For non-shared multi node systems, update the deployment plan in
$EBS_ORACLE_HOME and bounce the managed server to get the changes reflected.
• Quick commands for changing the oacore managed server port from 7205 to 7305
perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl -contextfile=<CONTEXT_FILE> configoption=removeMS -
oacore=testserver.example.com:7205
perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl -contextfile=<CONTEXT_FILE>
-configoption=addMS -oacore=testserver.example.com:7305

20. WLS CONFIGURATION
• Following steps needs to be performed for addition of new managed server
• No active patching cycle should exists, next prepare/fs_clone phase syncs up Patch edition
with Run edition during configuration change detector process
• Execute adProvisionEBS.pl script for creating managed server and adding entry in context
file.
perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl
ebs-create-managedserver -contextfile=<CONTEXT_FILE>
-managedsrvname=<MANAGED_SERVER_NAME> -servicetype=<SERVICE_TYPE>
-managedsrvport=<MANAGED_SERVER_PORT> -logfile=<LOGFILE>
• Execute txkSetAppsConf.pl to update the OHS configuration files mod_wl_ohs.conf and
apps.conf on the current node
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl
-contextfile=<CONTEXT_FILE>
-configoption=addMS
-oacore=<host>.<domain>:<port>
-oafm=<host>.<domain>:<port>
-forms=<host>.<domain>:<port>
-formsc4ws=<host>.<domain>:<port>
• Re-Start OHS service if enabled along with new managed server

21. WLS CONFIGURATION
• Following steps needs to be performed for deletion of new managed server
• Deletion should be performed on RUN edition with no active patch cycle, next
prepare/fs_clone phase syncs up Patch edition
• Bring down managed server, that is planned to delete
sh <ADMIN_SCRIPTS_HOME>/admanagedsrvctl.sh stop <MANAGED SERVER NAME>
• Execute adProvisionEBS.pl script to delete the managed server and remove entry in
context file
$ perl <AD_TOP>/patch/115/bin/adProvisionEBS.pl
ebs-delete-managedserver
-contextfile=<CONTEXT_FILE> -managedsrvname=<MANAGED_SERVER_NAME>
-servicetype=<SERVICE_TYPE> -logfile=<LOGFILE>
• Execute txkSetAppsConf.pl to update the OHS configuration files mod_wl_ohs.conf and
apps.conf on the current node
$ perl <FND_TOP>/patch/115/bin/txkSetAppsConf.pl
-contextfile=<CONTEXT_FILE> -configoption=removeMS -oacore=<host>.<domain>:<port>
-oafm=<host>.<domain>:<port> -forms=<host>.<domain>:<port>
-formsc4ws=<host>.<domain>:<port>
-ekanban=<host>.<domain>:<port>
-accessgate=<host>.<domain>:<port>
-yms=<host>.<domain>:<port>
• Re-Start OHS service if enabled

22. CUSTOMIZATION
• Adsplice should be used for registering the custom applications. This process enables
– New user edition-enabled
– Edition-based redefinition (EBR) for the custom objects.
– Next prepare phase runs fs_clone to sync up the two file systems
• Adsplice needs to be executed if Applications are upgraded to R12.2 release with the same
application id and application name to make it ready for online patching
• Oracle recommends to run adsplice after upgrading to R12.2.2 or above & not during
R12.2 because of file synchronization issues
• Patch 3636980 (IZU Diagnostic) can be used as a template for setting the custom top
• If Customizations includes Java & BC4J code objects, then Patches 17217965 & 17217772
needs to be applied.

23. CUSTOMIZATION
• Following approach should be used for migrating the application data objects from
Development to Production
• Create the initial table definition in your development database
• Upgrade the table for Online Patching using the AD_ZD_TABLE.UPGRADE
procedure, enables editioned view
• Extract the table definition from your development database using the xdfgen.pl utility
– perl xdfgen.pl <apps_user>/<apps_password>@<DB_SID> <OBJECT_NAME>
• Create and Apply the patch in Production
– perl xdfcmp.pl <applsys_user>/<applsys_password>@$TWO_TASK
$FND_TOP/patch/115/xdf/<object_name>.xdf <apps_user>/<apps_password>

24. CLONING
• Prepare the Source System for
database tier and application
tier & Copy database tier to
target system
• Copy the application tier node
from the Source Run Edition
File System to the Target Run
Edition File System
• Copy the application tier node
from the Target Run Edition File
System to the Target Patch
Edition File System
• Configure the Target System for
both database tier and
application tier

25. CLONING
• Database cloning remains same
• Application tier copy involves only <APPL_TOP>, <COMMON_TOP>, <OracleAS
Tools 10.1.2 ORACLE_HOME>
• adpreclone.pl generates the following files to copy/configure the Oracle Fusion
middleware components
– <COMMON_TOP>/clone/FMW/FMW_Home.jar
– <COMMON_TOP>/clone/FMW/WLS/EBSdomain.jar
– <COMMON_TOP>/clone/FMW/WLS/plan/moveplan.xml
– <COMMON_TOP>/clone/FMW/OHS/ohsarchive.jar
– <COMMON_TOP>/clone/FMW/OHS/moveplan.xml
• Application tier, all the ORACLE_HOME environments (oracle_common,
webtier,EBS_ORACLE_HOME) should be properly registered in inventory
• adcfgclone.pl uses weblogic utilities to build the FMW_HOME on target environment

26. OAM INTEGRATION
• R12.2 has inbuilt OHS &
WebLogic Server
• Webgate can be deployed on
top of R12.2 OHS 11g home
• Accessgate can be deployed as
a separate managed server
( oaea_server1 ) on top of
R12.2 weblogic
• Reduces the number of moving
parts in the OAM integration
EBS & effort involved.

27. THANK YOU !