Tuesday, December 31, 2013
Saturday, December 28, 2013
Rooting Android was this Years Holiday Achivement
Tired of Android 2.3.6 , It was time for rooting my device and target was to get Android 4.4 KitKat. With very few ROMs available on the market for 4.4 it was really a good experience.
So here is what I did ; It may look short and easy but it took a lot of time to understand the basics.
Rooting : I was lucky with SuperOneClickv2.3.3-ShortFuse and with one click my device was rooted.
I work for data center and mostly work with non-root users (oracle) , it is always a pride to have root access. The same with Android once you root you are the real owner of your device.
Backup : If you like to restore 2.3.6 in any case then you should backup. I used ROM Manager and Titanium Backup
ROM : There are a lot of ROMs available in Android 4 but for KitKat I decided to go with BeanStalk-4.4 and downloaded its corresponding Google Apps
So here are the steps
- Backup using ROM Manager
- Reboot into Recovery using ROM Manager
- In Recovery Manager selected install from SD Card and selected BeanStalk-4.4
- BeanStalk installation failed.
- Reason for that is a corrupt recovery so to support it I had to upgrade the kernel of 2.3.6
- Installed SGS kernel installed from play store
- Downloaded modified kernel kernel-2011-09-26.17-48.zip (there are many available you can choose)
- In Recovery Manager selected install from SD Card and selected BeanStalk-4.4
- BeanStalk-4.4 got installed
- In Recovery Manager selected install from SD Card and selected Google Apps gapps-kk-20131119.zip
- In Recovery Manager selected option to reboot the device
So here is what I did ; It may look short and easy but it took a lot of time to understand the basics.
Rooting : I was lucky with SuperOneClickv2.3.3-ShortFuse and with one click my device was rooted.
I work for data center and mostly work with non-root users (oracle) , it is always a pride to have root access. The same with Android once you root you are the real owner of your device.
Backup : If you like to restore 2.3.6 in any case then you should backup. I used ROM Manager and Titanium Backup
ROM : There are a lot of ROMs available in Android 4 but for KitKat I decided to go with BeanStalk-4.4 and downloaded its corresponding Google Apps
So here are the steps
- Backup using ROM Manager
- Reboot into Recovery using ROM Manager
- In Recovery Manager selected install from SD Card and selected BeanStalk-4.4
- BeanStalk installation failed.
- Reason for that is a corrupt recovery so to support it I had to upgrade the kernel of 2.3.6
- Installed SGS kernel installed from play store
- Downloaded modified kernel kernel-2011-09-26.17-48.zip (there are many available you can choose)
- In Recovery Manager selected install from SD Card and selected BeanStalk-4.4
- BeanStalk-4.4 got installed
- In Recovery Manager selected install from SD Card and selected Google Apps gapps-kk-20131119.zip
- In Recovery Manager selected option to reboot the device
- BINGO I now have Android 4.4.2
Thursday, December 19, 2013
Dear Readers Enjoy Reading with PacktPub with $5 eBook Bonanza
Dear Readers Enjoy Reading with PacktPub with $5 eBook Bonanza
Press release
Packt’s $5 eBook Bonanza is back!
Following on from the success of last year’s festive offer, the publisher will be celebrating the holiday season with an even bigger $5 Bonanza.
This sale covers every title in the 1700+ range and customers can grab as many as they like until January 3rd 2014 – more information is available at http://bit.ly/1jdCr2W
Saturday, December 14, 2013
R12.2 Configuration Management - Scenario on SyncContext
Configuration Management - Scenario on SyncContext
http://testserver01.oratest.com:8000/oracle_smp_chronos/oracle_smp_chronos_sdk.gif http://testserver01.oratest.com:8000/oracle_smp_chronos/oracle_smp_chronos_sdk.gif http://testserver01.oratest.com:8000 http://testserver01.oratest.com:8000/OA_HTML/AppsLogin 8000 8000
"
step="1" range="-1" label="Web Listener
Port">8000
8000
http://testserver01.oratest.com:8001/oracle_smp_chronos/oracle_smp_chronos_sdk.gif http://testserver01.oratest.com:8001/oracle_smp_chronos/oracle_smp_chronos_sdk.gif http://testserver01.oratest.com:8001 http://testserver01.oratest.com:8001/OA_HTML/AppsLogin 8001 8001 8001
http://testserver01.oratest.com:8000/oracle_smp_chronos/oracle_smp_chronos_sdk.gif http://testserver01.oratest.com:8000/oracle_smp_chronos/oracle_smp_chronos_sdk.gif http://testserver01.oratest.com:8000 http://testserver01.oratest.com:8000/OA_HTML/AppsLogin 8000 1800000 8000 8000
In Oracle E-Business
Suite Release 12.2, some configurations are managed via AutoConfig, and some
are managed natively via Fusion Middleware Control and WebLogic Server
Administration Console. A new mechanism has been introduced to keep the context
variables and the OHS configuration parameters (where applicable) in
synchronization. This mechanism is called the 'feedback loop'. The SyncContext tool is one of the tools used for explicit synchronization of
the context variables with the WLS configuration parameters.
This tool can be run
on all application tier nodes as follows:
On UNIX:
$ perl /bin/adSyncContext.pl
contextfile=
Scenario: Changing
WebPort from 8000 to 8001
$ grep 8000 $CONTEXT_FILE
$
$ pwd
/inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I
$
$ cp httpd.conf
httpd.conf_bkup
$ diff httpd.conf
httpd.conf_bkup
200c200
< Listen 8001
---
> Listen 8000
$
$ perl
$AD_TOP/bin/adSyncContext.pl
contextfile=$CONTEXT_FILE
Enter the APPS
user password:
Enter the
WebLogic AdminServer password:
The log file is /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/logs/appl/rgf/Wed_Nov_27_23_55_34_2013/adSyncContext.log
$
$ cat /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/logs/appl/rgf/Wed_Nov_27_23_55_34_2013/adSyncContext.log
..
..
Updating the below context
variables in /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
Context Variable : s_webport
Current Value : 8000
New Value : 8001
Context Variable : s_login_page
Current Value : http://testserver01.oratest.com:8000/OA_HTML/AppsLogin
New Value : http://testserver01.oratest.com:8001/OA_HTML/AppsLogin
Context Variable : s_active_webport
Current Value : 8000
New Value : 8001
Context Variable :
s_http_listen_parameter
Current Value : 8000
New Value : 8001
Context Variable : s_chronosURL
Current Value : http://testserver01.oratest.com:8000/oracle_smp_chronos/oracle_smp_chronos_sdk.gif
New Value : http://testserver01.oratest.com:8001/oracle_smp_chronos/oracle_smp_chronos_sdk.gif
Context Variable :
s_endUserMonitoringURL
Current Value : http://testserver01.oratest.com:8000/oracle_smp_chronos/oracle_smp_chronos_sdk.gif
New Value : http://testserver01.oratest.com:8001/oracle_smp_chronos/oracle_smp_chronos_sdk.gif
Context Variable : s_external_url
Current Value : http://testserver01.oratest.com:8000
New Value : http://testserver01.oratest.com:8001
Context Variable : s_contextserial
Current Value : 1
New Value : 2
Updated the
context file. Now going to upload the context file to the database..
$ grep 8001
$CONTEXT_FILE
$
Autoconfig in Check Mode
$ adchkcfg.sh
contextfile=$CONTEXT_FILE
Enter the APPS
password:
The log file for
this session is located at: /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/log/11272357/adconfig.log
AutoConfig is
running in test mode and building diffs...
AutoConfig will
consider the custom templates if present.
Using CONFIG_HOME location : /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01
Classpath : /inst122i/applmgr/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/inst122i/applmgr/fs1/EBSapps/comn/java/classes
Using Context file : /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/INST122I_testserver01.xml
Context Value
Management will now update the test Context file
Updating test Context file...COMPLETED
[ Test mode ]
No uploading of Context File and its
templates to database.
Testing templates
from all of the product tops...
Testing AD_TOP........COMPLETED
Testing FND_TOP.......COMPLETED
Testing ICX_TOP.......COMPLETED
Testing MSC_TOP.......COMPLETED
Testing IEO_TOP.......COMPLETED
Testing BIS_TOP.......COMPLETED
Testing CZ_TOP........COMPLETED
Testing AMS_TOP.......COMPLETED
Testing CCT_TOP.......COMPLETED
Testing WSH_TOP.......COMPLETED
Testing CLN_TOP.......COMPLETED
Testing OKE_TOP.......COMPLETED
Testing OKL_TOP.......COMPLETED
Testing OKS_TOP.......COMPLETED
Testing CSF_TOP.......COMPLETED
Testing IBY_TOP.......COMPLETED
Testing JTF_TOP.......COMPLETED
Testing MWA_TOP.......COMPLETED
Testing CN_TOP........COMPLETED
Testing CSI_TOP.......COMPLETED
Testing WIP_TOP.......COMPLETED
Testing CSE_TOP.......COMPLETED
Testing EAM_TOP.......COMPLETED
Testing FTE_TOP.......COMPLETED
Testing ONT_TOP.......COMPLETED
Testing AR_TOP........COMPLETED
Testing AHL_TOP.......COMPLETED
Testing IES_TOP.......COMPLETED
Testing OZF_TOP.......COMPLETED
Testing CSD_TOP.......COMPLETED
Testing IGC_TOP.......COMPLETED
Differences text
report is located at: /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/cfgcheck.txt
Generating Profile Option differences
report...COMPLETED
Differences text
report for the Database is located at: /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/ProfileReport.txt
Generating File System differences
report......COMPLETED
Differences html
report is located at: /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/cfgcheck.html
Differences Zip
report is located at: /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/ADXcfgcheck.zip
AutoConfig
completed successfully.
$
$ cat /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/cfgcheck.txt
Plenty of Changes
Some of the Important Changes
File : trusted.conf
$ cat /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/x_trusted.conf
Checking differences
between
Existing
file(<) : /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/trusted.conf
New
file(>) : /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/trusted.conf
===========================================================================
Differences
===========================================================================
171c171
<
RedirectMatch ^/OA_HTML/fwk/t/(.*) http://testserver01.oratest.com:8000/OA_IMAGE/fwk/t/$1
-----
>
RedirectMatch ^/OA_HTML/fwk/t/(.*) http://testserver01.oratest.com:8001/OA_IMAGE/fwk/t/$1
$
Some of the Important Changes
File : oacore_wls.properties
$ cat /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/x_oacore_wls.properties
Checking
differences between
Existing
file(<) : /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/oacore_wls.properties
New
file(>) : /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/oacore_wls.properties
===========================================================================
Differences
===========================================================================
38c38
<
EXTERNAL_URL=http://testserver01.oratest.com:8000
-----
>
EXTERNAL_URL=http://testserver01.oratest.com:8001
65c65
<
SOA_SERVER_URL=http://testserver01.oratest.com:8000
-----
>
SOA_SERVER_URL=http://testserver01.oratest.com:8001
$
Some of the Important Changes
File : ohwconfig.xml
$ cat /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/x_ohwconfig.xml
Checking
differences between
Existing
file(<) : /inst122i/applmgr/fs1/FMW_Home/Oracle_EBS-app1/common/config/ohwconfig.xml
New
file(>) : /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/admin/out/11272357/ohwconfig.xml
===========================================================================
Differences
===========================================================================
22c22
<
<branding imageSource="http://testserver01.oratest.com:8000/OA_MEDIA/FNDSSCORP.gif"
imageShortDesc="Oracle Logo" />
-----
>
<branding imageSource="http://testserver01.oratest.com:8001/OA_MEDIA/FNDSSCORP.gif"
imageShortDesc="Oracle Logo" />
$
Autoconfig
If autoconfig is run at this
time then changes will be in place.
Oh that is a lot of change I do
not want to do it now. So reverting back.
$ pwd
/inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I
$ cp
httpd.conf_bkup httpd.conf
$ grep -i listen
httpd.conf
# Listen: Allows
you to bind Apache to specific IP addresses and/or
# Change this to
Listen on specific IP addresses as shown below to
# Listen
12.34.56.78:80
# OHS Listen Port
Listen 8000
$
I reran the adSyncContext.pl
that will update the new values to the context file again.
$ perl
$AD_TOP/bin/adSyncContext.pl contextfile=$CONTEXT_FILE
Enter the APPS
user password:
Enter the
WebLogic AdminServer password:
The log file is /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/logs/appl/rgf/Thu_Nov_28_00_01_25_2013/adSyncContext.log
$
$ grep -i 8001
$CONTEXT_FILE
$
There are references to 8001
port which has been reverted back.
$
$ grep -i 8000
$CONTEXT_FILE
$
This scenario shows how SyncContext.pl drives the changes to HTTP Server.
Friday, December 13, 2013
R12.2 Configuration Management - Scenario on adRegisterWLSListeners
R12.2 Configuration Management - Scenario on adRegisterWLSListeners
Some Oracle E-Business Suite Release 12.2 configurations are managed via AutoConfig, and some are managed natively via Fusion Middleware Control or Oracle WebLogic Server Administration Console.
The adRegisterWLSListeners tool has been introduced to perform synchronization of context variables with the associated Oracle WebLogic Server configuration parameters.
Note: This tool does not listen for changes to the Oracle HTTP Server configuration parameters.
Execute the following command to start adRegisterWLSListeners.pl:
$ perl/bin/adRegisterWLSListeners.pl contextfile=
Once started, adRegisterWLSListeners keeps running, listening for changes to the WebLogic Server configuration and synchronizing the context files stored in the database.
Important: The adRegisterWLSListeners tool automatically stops when WebLogic Administration Server is shut down. On UNIX instances, the tool is started automatically started whenever WebLogic Administration Server is started. On Windows instances, you must start the tool explicitly every time WebLogic Administration Server is started.
For this demo I have started the tool manually to see if the changes I make is getting recorded
SQL>
SQL>
Some Oracle E-Business Suite Release 12.2 configurations are managed via AutoConfig, and some are managed natively via Fusion Middleware Control or Oracle WebLogic Server Administration Console.
The adRegisterWLSListeners tool has been introduced to perform synchronization of context variables with the associated Oracle WebLogic Server configuration parameters.
Note: This tool does not listen for changes to the Oracle HTTP Server configuration parameters.
Execute the following command to start adRegisterWLSListeners.pl:
$ perl
Once started, adRegisterWLSListeners keeps running, listening for changes to the WebLogic Server configuration and synchronizing the context files stored in the database.
Important: The adRegisterWLSListeners tool automatically stops when WebLogic Administration Server is shut down. On UNIX instances, the tool is started automatically started whenever WebLogic Administration Server is started. On Windows instances, you must start the tool explicitly every time WebLogic Administration Server is started.
For this demo I have started the tool manually to see if the changes I make is getting recorded
SQL> select * from AD_NODES_CONFIG_STATUS;
NODENAME W O C
---------------------------------------- - - -
TESTSERVER01 N N N
You can see from the above back end SQL that Weblogc , OHS and Context File are showing value N since they are not changed.
Now let us make a change in the Weblogic.
SQL> select * from AD_NODES_CONFIG_STATUS;
NODENAME W O C
---------------------------------------- - - -
TESTSERVER01 Y N N
adRegisterWLSListeners.pl has updated the database table AD_NODES_CONFIG_STATUS with status Y for WebLogic Column.
This is how weblogic changes are keep in track and synced using adRegisterWLSListeners.pl
Thursday, December 12, 2013
R12.2 Configuration Management - Using AutoConfig Tools for System Configuration
Using AutoConfig Tools for System Configuration
- adautocfg.sh - This script is used for running AutoConfig.
- adchkcfg.sh - This script may be run before running AutoConfig to review the changes on running AutoConfig.
- admkappsutil.pl - This script is used while applying patches to the database tier. Running this script generates appsutil.zip, which may be copied over to the database tier to migrate the patch to the database tier.
- adRegisterWLSListeners.pl - This script is used to listen to changes to the WebLogic Server configuration parameters and update the context variables accordingly.
- adSyncContext.pl - This script is used to explicitly pull the values of the WebLogic Server configuration parameters and synchronize the context variable values like synchronization of the OHS parameters.
- GenCtxInfRep.pl - This script can be used to find out detailed information about context variables and the templates in which they are used, given all or part of a context variable name as a keyword.
- adtmplreport.sh - This script can be used to gather information regarding the location of the AutoConfig templates, provided the location of the instantiated files and vice versa.
Run adRegisterWLSListeners Tool on the Application Tier
- The adRegisterWLSListeners tool has been introduced to perform synchronization of context variables with the associated Oracle WebLogic Server configuration parameters.
- This tool does not listen for changes to the Oracle HTTP Server configuration parameters.
- Once started, adRegisterWLSListeners keeps running, listening for changes to the WebLogic Server configuration and synchronizing the context files stored in the database.
- This tools starts/stops along with the WebLogic Admin Server.
Scenario on adRegisterWLSListeners
Run SyncContext on the Application Tier
- The adSyncContext.pl script reads the WLS configuration parameter values and synchronizes them with the context variables.
- This is used to synchronize the OHS configuration parameters with the respective context variables.
- This mechanism is called the 'feedback loop‘
- The SyncContext tool is one of the tools used for explicit synchronization of the context variables with the WLS configuration parameters.
- In Oracle E-Business Suite Release 12.2 some important configuration files like httpd.conf and ssl.conf are no longer maintained by AutoConfig. Oracle Enterprise Manager 11g Fusion Middleware Control should be used to maintain these configuration files as well as making additional changes to Context File variables.
Scenario on SyncContext
Wednesday, December 11, 2013
R12.2 Configuration Management - Using AutoConfig to Manage Oracle E-Business Suite Services
Using
AutoConfig to Manage Oracle E-Business Suite Services
- In previous Oracle E-Business Suite releases, the Applications services were categorized into service groups according to the type of service provided.
- In Oracle E-Business Suite Release 12.2, this concept has been extended by the introduction of additional services and service groups.
- Web Administration Service Group has been introduced in Release 12.2 and it contains WebLogic Administration server. It is not supported to enable WebLogic Administration server on any other Application tier node except the node on which it was enabled during Rapid Install.
- Root Service Group now comprises Node Manager and not Oracle Process Manager (OPMN)
- In R12.2 OPMN only manages Oracle HTTP Server and it is now part of the Web Entry Point Services Group
| Service Group | Service(s) | Service Control Script | |
| Root Service | Node Manager | adnodemgrctl.sh | |
| Web Administration | WebLogic Admin Server | adadminsrvctl.sh | |
| Web Entry Point Services | Oracle HTTP Server | adapcctl.sh | |
| Oracle Process Manager | adopmnctl.sh | ||
| Web Application Services | oacore | admanagedsrvctl.sh | |
| oafm | admanagedsrvctl.sh | ||
| forms | admanagedsrvctl.sh | ||
| forms-c4ws | admanagedsrvctl.sh | ||
| Batch Processing Services | Oracle TNS Listener | adalnctl.sh | |
| Concurrent Manager | adcmctl.sh | ||
| Fulfillment Server | jtffmctl.sh | ||
| Oracle ICSM | ieoicsm.sh | ||
| Other Services | Forms Server | adformsrvctl.sh | |
| Oracle MWA Service | mwactlwrpr.sh |
Modifying
AutoConfig-Managed Services and Service Groups
- Depending on the requirement of a particular Applications instance, it is possible to modify the set of Applications services and service groups that will be started and stopped via the adstrtal and adstpall scripts respectively.
- Check the value of the 'status' context variable corresponding to the service group and make it enabled/disabled as required.
- In case of the oacore, oafm, forms and forms-c4ws services, there may be more than one instance of the service. To cater for this, check that the context variable corresponding to the name of the service contains the name of the managed server to be enabled. If not, add it to the list, using a comma as a separator.
Tuesday, December 10, 2013
R12.2 Oracle WebLogic Server Requirements and Usage
Oracle WebLogic Server Requirements and Usage
Oracle E-Business Suite Release 12.2 requires WebLogic Server Basic.
This is a license-constrained version of WebLogic Server that is available in licenses for certain Oracle products.
WebLogic Server Basic is used in Oracle E-Business Suite Release 12.2 to support the following features:
Oracle E-Business Suite Release 12.2 requires WebLogic Server Basic.
This is a license-constrained version of WebLogic Server that is available in licenses for certain Oracle products.
WebLogic Server Basic is used in Oracle E-Business Suite Release 12.2 to support the following features:
- WLS Clusters. Specifically, one WLS cluster per EBS domain.
- Hardware-based load-balancers in front of a WLS cluster in an EBS domain.
- Use of the WLS proxy on an OHS server, directing load to one or more WLS instances on one or more managed servers in a WLS Cluster. The cluster is defined by AutoConfig via the configuration file deployed on the OHS server.
- Session re-instantiation from one managed server to another managed server within the same cluster. Although transactions in progress during failure of one managed server will be lost, the user’s session will be re-established and migrated to another managed server in the cluster.
R12.2 Configuration Management Tools
R12.2 Highlights
- This release is largely focused on providing new technology stack components, new configuration options, and new system management tools.
- Supports for Online Patching.
- Use of Oracle WebLogic Server instead of AutoConfig for many (but not all) of AutoConfig's previous functions.
- Use of Oracle WebLogic Server instead of Oracle Containers for Java (OC4J).
- Integration between Oracle Enterprise Manager 11g Fusion Middleware Control and Oracle Applications Manager to monitor EBS environments with Oracle WebLogic Server technology.
- Enhanced Workflow Worklist notification and management features.
Configuration Management Tools
- Fusion Middleware Control
- This tool provides a high-level view of Oracle WebLogic Server (WLS)
- It is used to configure Oracle HTTP Server
- Fusion Middleware Control also includes links to Oracle Application Manager and Oracle WebLogic Server Admin Console.
- WebLogic Server Administration Console
- Manage Oracle WebLogic Server settings and managed servers.
- Oracle Application Manager and AutoConfig
- Handles Oracle E-Business Suite settings and Database Settings
What happened to OC4J ? What is Weblogic doing ?
In Oracle E-Business Suite Release 12.2, OC4J has been replaced with Oracle WebLogic Server.
This has resulted in a reduced role for AutoConfig in the configuration of the Oracle HTTP Server and the oacore, oafm, forms and forms-c4ws services.
Configuration Management Changes in Release 12.2
Configuration Activity - Oracle E-Business Suite Database, Concurrent Processing, Oracle Developer 10g, profile options, and other Oracle E-Business Suite components.
Prior to Release 12.2
- Oracle Applications Manager.
In Release 12.2
- Oracle Applications Manager.
Configuration Activity - Changes to HTTP Configuration.
Prior to Release 12.2
- All HTTP configuration was managed via AutoConfig templates.
- Configuration changes were done by editing the respective context variables and subsequently running AutoConfig.
In Release 12.2
- Most HTTP configuration is managed via native Oracle WebLogic Server tools, Fusion Middleware Control, or manually editing of the configuration files.
- Only a limited set of HTTP configuration files are maintained via AutoConfig.
Configuration Activity - Changes to configuration of oacore, oafm, forms and forms-c4ws services.
Prior to Release 12.2
- All configuration settings for the oacore, oafm, forms and forms-c4ws services were managed via AutoConfig templates.
- Configuration changes were accomplished by editing context variables and running AutoConfig.
In Release 12.2
- Properties for the oacore, oafm, forms and forms-c4ws services, including the classpath and JVM arguments, need to be updated through native WebLogic tools such as WebLogic Administration Console.
- The context variable values are used only to set the initial values during managed server creation.
Configuration Activity - Managing JVM instances of the oacore, oafm, forms and forms-c4ws services.
Prior to Release 12.2
- The number of instances of a service was controlled via Oracle Process Manager (OPMN).
- This number could be modified by editing the nprocs context variable, running AutoConfig, then stopping and restarting the services.
In Release 12.2
- Each JVM instance of a service corresponds to a managed server of that service type.
- The number of instances needs to be controlled by explicitly creating or deleting managed servers for the service.
Saturday, December 7, 2013
FS_CLONE Phase Scenario - R12.2 Online Patching Cycle
Scenario
You
have noticed that the on the patch edition there are lot of patches applied.
You did the cutover and now customer wants to begin the next patching cycle.
Since there are lots of patches applied you decided to do file system cloning.
Before
we start, the basic requirement of the /tmp file system should be +10GB for the
cloning.
Unfortunately
not all servers can expand /tmp , so to work around you can redirect the
temporary location using the below parameter.
$
export
T2P_JAVA_OPTIONS="-Djava.io.tmpdir=/inst122i/product/tmp"
$
adop phase=fs_clone
Enter
the APPS password:
Enter
the SYSTEM password:
Enter
the WLSADMIN password:
Please wait. Validating credentials...
RUN
file system context file: /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
PATCH
file system context file: /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
*************
Start of session *************
version: 12.2.0
started at: Sat Nov 16 2013 22:06:44
APPL_TOP
is set to /inst122i/applmgr/fs2/EBSapps/appl
[START 2013/11/16 22:07:12] adzdoptl.pl run
ADOP Session ID: 8
Phase: fs_clone
Log file: /inst122i/applmgr/fs_ne/EBSapps/log/adop/8/adop_20131116_220620.log
[EVENT] [START 2013/11/16 22:07:19] CLONE Patch
File System from Run File System
[EVENT] Calling: /inst122i/applmgr/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl
Program
: started @ Sat Nov 16 22:07:22 2013
***
Log File = /inst122i/applmgr/fs_ne/EBSapps/log/adop/8/fs_clone_20131116_220620/INST122I_testserver01/TXK_SYNC_create_Sat_Nov_16_22_07_22_2013/txkADOPPreparePhaseSynchronize_Sat_Nov_16_22_07_22_2013.log
Beginning
application tier FSCloneApply - cloneContext Sat Nov 16 22:07:30 2013
This block
prepares the instance for cloning by validating the PATCH and the RUN
environment.
/inst122i/applmgr/fs2/FMW_Home/webtier/jdk/bin/java
-Xmx600M -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/oui -classpath /inst122i/applmgr/fs1/FMW_Home/webtier/lib/xmlparserv2.jar:/inst122i/applmgr/fs1/FMW_Home/webtier/jdbc/lib/ojdbc6.jar:/inst122i/applmgr/fs2/EBSapps/comn/java/classes:/inst122i/applmgr/fs1/FMW_Home/webtier/oui/jlib/OraInstaller.jar:/inst122i/applmgr/fs1/FMW_Home/webtier/oui/jlib/ewt3.jar:/inst122i/applmgr/fs1/FMW_Home/webtier/oui/jlib/share.jar:/inst122i/applmgr/fs1/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:/inst122i/applmgr/fs1/FMW_Home/webtier/jlib/ojmisc.jar:/inst122i/applmgr/fs2/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/obfuscatepassword.jar oracle.apps.ad.clone.FSCloneApplyAppsTier -e
/inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
-targ /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
-stage /inst122i/applmgr/fs2/EBSapps/comn/clone -tmp /tmp -nodbac -component
cloneContext -nopromptmsg
Log
file located at /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/admin/log/FSCloneApplyAppsTier_11162207.log
Log
file located at /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/admin/log/FSCloneApplyAppsTier_11162207.log
Target
System Fusion Middleware Home set to /inst122i/applmgr/fs1/FMW_Home
Target
System Web Oracle Home set to /inst122i/applmgr/fs1/FMW_Home/webtier
Target
System Appl TOP set to /inst122i/applmgr/fs1/EBSapps/appl
Target
System COMMON TOP set to /inst122i/applmgr/fs1/EBSapps/comn
Target
System Instance Top set to /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01
Report
file located at /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/temp/portpool.lst
Complete
port information available at /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/temp/portpool.lst
Creating
the new APPL_TOP Context file from :
/inst122i/applmgr/fs2/EBSapps/comn/clone/context/apps/adxmlctx.tmp
The
new APPL_TOP context file has been created :
/inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
Log
file located at /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/admin/log/FSCloneApplyAppsTier_11162207.log
contextfile=/inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
Completed
FSCloneApply...
Sat
Nov 16 22:07:36 2013
Beginning
application tier FSCloneStage - Sat Nov 16 22:07:42 2013
This block
zips the required files from the RUN edition and moves it to the stage
directory.
/inst122i/applmgr/fs2/FMW_Home/jrockit32/bin/java
-Xmx600M -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/oui -classpath /inst122i/applmgr/fs2/FMW_Home/webtier/lib/xmlparserv2.jar:/inst122i/applmgr/fs2/FMW_Home/webtier/jdbc/lib/ojdbc6.jar:/inst122i/applmgr/fs2/EBSapps/comn/java/classes:/inst122i/applmgr/fs2/FMW_Home/webtier/oui/jlib/OraInstaller.jar:/inst122i/applmgr/fs2/FMW_Home/webtier/oui/jlib/ewt3.jar:/inst122i/applmgr/fs2/FMW_Home/webtier/oui/jlib/share.jar:/inst122i/applmgr/fs2/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:/inst122i/applmgr/fs2/FMW_Home/webtier/jlib/ojmisc.jar:/inst122i/applmgr/fs2/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/inst122i/applmgr/fs2/FMW_Home/oracle_common/jlib/obfuscatepassword.jar oracle.apps.ad.clone.FSCloneStageAppsTier -e
/inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
-targ /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
-stage /inst122i/applmgr/fs2/EBSapps/comn/clone -tmp /tmp -component appsTier
-nopromptmsg
Log
file located at /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/admin/log/FSCloneStageAppsTier_11162207.log
Completed
FSCloneStage...
Sat
Nov 16 23:38:24 2013
Beginning
application tier FSCloneApply - Sat Nov 16 23:41:13 2013
This block
unzips the files from the staging directory into the relevant directory under
the PATCH edition.
Runs
autoconfig and deploys application into the weblogic domain.
/inst122i/applmgr/fs2/EBSapps/comn/clone/FMW/t2pjdk/bin/java
-Xmx600M -DCONTEXT_VALIDATED=false -Doracle.installer.oui_loc=/oui -classpath /inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/xmlparserv2.jar:/inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/ojdbc6.jar:/inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/java:/inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/oui/OraInstaller.jar:/inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/oui/ewt3.jar:/inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/oui/share.jar:/inst122i/applmgr/fs1/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:/inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/ojmisc.jar:/inst122i/applmgr/fs2/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/inst122i/applmgr/fs2/EBSapps/comn/clone/jlib/obfuscatepassword.jar oracle.apps.ad.clone.FSCloneApplyAppsTier -e
/inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
-targ /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
-stage /inst122i/applmgr/fs2/EBSapps/comn/clone -tmp /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/appltmp
-nodbac -component appsTier -nopromptmsg
Log
file located at /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/admin/log/FSCloneApplyAppsTier_11162341.log
Log
file located at /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/admin/log/FSCloneApplyAppsTier_11162341.log
Target
System Fusion Middleware Home set to /inst122i/applmgr/fs1/FMW_Home
Target
System Web Oracle Home set to /inst122i/applmgr/fs1/FMW_Home/webtier
Target
System Appl TOP set to /inst122i/applmgr/fs1/EBSapps/appl
Target
System COMMON TOP set to /inst122i/applmgr/fs1/EBSapps/comn
Target
System Instance Top set to /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01
Report
file located at /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/temp/portpool.lst
Complete
port information available at /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/temp/portpool.lst
Creating
the new APPL_TOP Context file from :
/inst122i/applmgr/fs2/EBSapps/comn/clone/context/apps/adxmlctx.tmp
The
new APPL_TOP context file has been created :
/inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
Log
file located at /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/admin/log/FSCloneApplyAppsTier_11162341.log
contextfile=/inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
Log
file located at /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/admin/log/FSCloneApplyAppsTier_11162341.log
Completed
FSCloneApply...
Sun
Nov 17 00:13:20 2013
cmd
= /inst122i/applmgr/fs2/FMW_Home/jrockit32/jre/bin/java -classpath /inst122i/applmgr/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/inst122i/applmgr/fs2/EBSapps/comn/java/classes
-mx256m oracle.apps.ad.tools.configuration.ADOPCustomSyncUp
-contextFile /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
-custSyncDrv /inst122i/applmgr/fs_ne/EBSapps/appl/ad/custom/adop_sync.drv
-logFile /inst122i/applmgr/fs_ne/EBSapps/log/adop/8/fs_clone_20131116_220620/INST122I_testserver01/TXK_SYNC_create_Sat_Nov_16_22_07_22_2013/txkADOPCustomSyncUp.log
-promptmsg 'hide'
Copying
PS artifacts from RUN to PATCH fs for exectier
Copying
SNO artifacts from RUN to PATCH fs for exectier
ADOP
Custom Synchorization successfully run
Program
: completed @ Sun Nov 17 00:42:44 2013
[EVENT] [END
2013/11/17 00:42:45] CLONE Patch File System from Run File System
[EVENT] [START 2013/11/17 00:43:03] Check and Stop
Patch FS Admin Server
You
are running adadminsrvctl.sh version 120.10.12020000.4
Stopping
WLS Admin Server...
Refer
/inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/logs/appl/admin/log/adadminsrvctl.txt
for details
adadminsrvctl.sh:
exiting with status 0
adadminsrvctl.sh:
check the logfile /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/logs/appl/admin/log/adadminsrvctl.txt
for more information ...
[EVENT] [END
2013/11/17 00:43:18] Check and Stop Patch FS Admin Server
[START 2013/11/17 00:43:23] Generating
AD_ZD_LOGS Report
[EVENT] Report: /inst122i/applmgr/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWLOG.sql
[EVENT] Output: /inst122i/applmgr/fs_ne/EBSapps/log/adop/8/fs_clone_20131116_220620/INST122I_testserver01/adzdshowlog.out
[END
2013/11/17 00:43:28] Generating AD_ZD_LOGS Report
[END
2013/11/17 00:43:29] adzdoptl.pl run
adop phase=fs_clone - Completed Successfully
Log file: /inst122i/applmgr/fs_ne/EBSapps/log/adop/8/adop_20131116_220620.log
adop
exiting with status = 0 (Success)
$
Subscribe to:
Posts (Atom)
Popular Posts
-
[oracle@testebsop3app01 ~]$ perl /u01/install/APPS/fs1/EBSapps/comn/clone/bin/adcfgclone.pl appltop /u01/install/APPS/fs1/inst/apps/SATURN_...
-
FS_CLONE Phase It is a stand-alone command used for file system cloning. Standard cloning (using adcfgclone.pl) cannot be used to synch...
-
Suddenly all production reports in BI Publisher failed with message " ORA-01017: invalid username/password; logon denied" The da... -
Abort Phase If for some reason either the prepare or apply phase failed or gave problems, you can abort the patching cycle. After runnin...
-
As a green field expert in data science, you would be responsible for designing and implementing data science projects from scratch. This i...
-
If you are an EBS administrator the first thing some asks you to do a health check of an environment , you return to him with a Request ID o...
-
PRVG-2031 : Owner of file "/u01/app/oracle/diag/crs/rac01/crs/lck" did not match the expected value on node "HOST1". [Ex...
-
ADOPValidations_detailed.log reported a warning message for one of the critical error "Cross Reference" ValidateFSConfigFile...
-
Ready the instance for cutover Perform the final operations like Compile Invalids , Generate Derived Objects and Pre-compute DDL to be run...
-
Scenario You have noticed that the on the patch edition there are lot of patches applied. You did the cutover and now customer wants t...