Enhanced new Application DBA features of Oracle
E-Business Suite Release 12.2.5
Script to Automate
Changing Oracle WebLogic Server Administration User Password (Conditional to be
on patch set level R12.AD.C.Delta.7 and R12.TXK.C.Delta.7 )
- The
procedure used to change the Oracle WebLogic Server Administration User
Password has been simplified and largely automated by the introduction of
a new utility that performs what were previously manual steps.
You can set the Oracle WebLogic Server Administration User password to a non-default value during Oracle E-Business Suite installation. if you need to change the password at a later time, you can do so on the run file system by shutting down all application tier services except the Admin Server, then running the new$FND_TOP/patch/115/bin/txkUpdateEBSDomain.pl script with the -action=updateAdminPassword option.
Support for Middle
Tier EBS Technology Checker
- The
new middle tier checker (MT-ETCC) technology script complements the
original ETCC database checker script (now called DB-ETCC). The scripts
report respectively on any missing middle tier and database tier bugfixes
and patches that are required for Release 12.2.
Simplified
Procedure for Changing WLS Data Source
- Changing
the APPS schema password in the WLS Data Source with FNDCPASS or AFPASSWD
has now been simplified and partially automated. The required sequence of
actions on the run file system of the primary node includes shutting down
the application tier services; starting AdminServer with the adadminsrvctl.sh script; running thetxkManageDBConnectionPool.pl script and choosing
the 'updateDSPassword' option; and finally restarting the application tier
services. Reference: Chapter 6, Basic DBA Tasks, Oracle E-Business
Suite Maintenance Guide.
Improved Delete
Node and Delete Managed Server APIs
- The
improvements include addition of more validations.
- Definition
of the following is mandatory in the pairs file used for standard clone
and for addition of nodes:
- s_webentryurlprotocol
- s_webentryhost
- s_webentrydomain
- s_active_webport
- These
include cleanup of existing integrations following run of Rapid Clone.
- This
now takes place automatically, instead of as a manual step after database
tier cloning.
- These
include enhancemente to validations, logging and security.
3.1 Enhanced adop user interface
Category
|
Description
|
Parameters
|
Changed UI
|
The UI of the adop utility has been significantly
enhanced, to display more selective information on the console. Messages,
prompts and other elements have also been extensively refined to increase the
ease of use of the various patching commands.
|
Dependent on operation
|
Category
|
Description
|
Parameters
|
New features
|
Progress of an online patching cycle can be followed
by running the new Online Patching Monitoring utility (adopmon). This utility
can be used to follow the overall progress of a patching cycle, as well as
identifying the various individual adop actions being taken.
|
$ adopmon
|
Before you start a new patching cycle by running the prepare phase, you can optionally check your system's readiness by running adop with the 'validate' option. If you do this while a patching cycle is in progress, validation will take place for the cutover phase. |
$ adop -validate
|
Category
|
Description
|
Parameters
|
New feature
|
Support for an instance-specific EBS Installation
Central Inventory has been introduced as an option for the application tier
on UNIX platforms. The inventory is identified by <s_base>/oraInventory/oraInst.loc.
This feature is useful where multiple Oracle E-Business Suite installations
exist on the same host, helping to avoid issues when fs_clone is
run simultaneously on different instances.
To use the EBS Installation Central Inventory, all application tier Oracle Homes registered in the global inventory for the instance must be migrated to the new inventory. |
Not applicable
|
To use the EBS Installation Central Inventory, all application tier Oracle Homes registered in the global inventory for the instance must be migrated to the new inventory. This is done by running the following steps on the primary application tier node:
1. Source the run
edition file system.
2. Edit the context
file and set the value of the context variable s_ebs_central_inventory to 'true'.
3. Run AutoConfig.
4. Run the following
command:
$ perl
<FND_TOP>/patch/115/bin/txkMigrateInventory.pl -contextfile=<CONTEXT_FILE>
Ensure
that all application tier Oracle Homes have been migrated to the EBS
Installation Central Inventory.
Repeat all the above steps on any non-shared nodes and shared
master nodes (for example, in a hybrid setup). For all shared slave nodes,
perform Steps 1 to 3 (only) on each node.
Once the inventory is migrated, any subsequently added nodes will be automatically configured to use the EBS Installation Central Inventory, and any new target instance cloned from this instance will automatically be configured to use it.
Once the inventory is migrated, any subsequently added nodes will be automatically configured to use the EBS Installation Central Inventory, and any new target instance cloned from this instance will automatically be configured to use it.
Category
|
Description
|
Parameters
|
New options
|
|
-DserverType=wlx
|
|
s_deploy_portlet
|
|
New mode
|
The default value of s_forms-c4wsstatus is
now set to 'Disabled'.Thus, the formsc4-ws servers are no longer started
during a 'start all' operation.
|
s_forms-c4wsstatus
|
- A
new -DserverType=wlx start argument for
managed servers reduces their memory footprint, by preventing startup of
the Enterprise JavaBeans (EJB), Java EE Connector Architecture (JCA), and
Java Message Service (JMS) services.
- The
default value of s_forms-c4wsstatus is now set to
'Disabled'.Thus, the formsc4-ws servers are no longer started during a
'start all' operation.
- To
reduce oacore startup time, the Portlet Producer libraries are no longer
deployed to the EBS domain. A new context variable, s_deploy_portlet, has been introduced to
cater for cases where portlet-related configuration is required, such as
in instances needing Webcenter integration.
3.5 New 'dualfs' option in standard cloning
Category
|
Description
|
Parameters
|
New option
|
A new 'dualfs' option is available when performing a
standard clone, as well as while adding a new node. With the 'dualfs' option,
both the run and patch file systems are cloned and configured in a single
operation.
|
dualfs
|
No comments:
Post a Comment