Pages

Tuesday, November 27, 2012

GRC Upgrade from 8.6.3.6001 to 8.6.3.6036 for TOMCAT


Pre Checks

1. Note down the configuration Home page settings
 login to the GRC url with admin user/password
 Note: If you face issues to get GRC application page, Uncheck all the settings in your Web Browser LAN Settings Section in Connect Tab and try again.
 Click on Navigator(Drop down from top left corner) --> Administration Management --> Manage Application Configurations
 (Take screen shoot of all the tabs and also note down all the values)

Upgrade steps

2. login as tomcat user to the tomcat Application server
   Shut down the Tomcat application server
    /<sid>/ias/AACG863/tomcat/bin/shutdown.sh
   login as db user to DB server
    Shutdown database
    sqlplus "/as sysdba"
    SQL> shut immediate
    SQL> exit
   Stop Listener
    lsnrctl stop <Listener Name>

3. Take cold backup of df -h /sid/* file systems. Make sure cold snap is taken before proceeding onto next step

4.Start the DB and Listener
  Login as db user to DB server
   sqlplus "/as sysdba"
    SQL> startup
    SQL> exit
    lsnrctl start <Listener Name>

5.login as tomcat user to the tomcat Application server
  Remove the directory <TomcatHome>/webapps/grc
     rm -rf /sid/ias/AACG863/tomcat/webapps/grc
  Remove the grc directory from the Tomcat work area (<TomcatHome>/work/Catalina/localhost/grc).
     rm -rf /sid/ias/AACG863/tomcat/work/Catalina/localhost/grc

6.  Run the file grc_tomcat_setup.sh to upgrade 8.6.3.6012 , Patch: 13931550
   ## ./grc_tomcat_setup.sh <grc_patch_stage>/dist <TomcatHome> JavaHomePath
 ex:  /<patch location>/13931550/dist/grc_tomcat_setup.sh /<patch location>/13931550/dist /sid/ias/AACG863/tomcat  /usr/java/jdk1.6.0_24/

7. Start the Tomcat application server.
   /sid/ias/AACG863/tomcat/bin/startup.sh

8.Access GRC at https://hostname.domain:port/grc, and fill out configuration as previously noted down in Step 1 and fill configurations

9. In the Manage Application Configurations page, click on Actions ? Save. GRC tests the values you’ve entered and, if they are valid, saves them.
(If any are in-valid, an error message instructs you to re-enter them.)

10. Exit the Manage Application Configurations page.

11. Shut down the Tomcat application server.
   /sid/ias/AACG863/tomcat/bin/shutdown.sh

12. Start the Tomcat application server.
   /sid/ias/AACG863/tomcat/bin/startup.sh

13. Wait till we see message like "Application Deployment Complete Successful" in grc.log file(tail -100f grc.log).
location : /sid/ias/AACG863/tomcat/webapps/grc/log
This will display the upgrade messages (Note: if Debug option was selected then additional upgrade messages will appear).

14. In a web browser, enter the GRC URL, You will be redirected to a GRC logon page. Log on to the application and check about for version of GRC.

15. After the successful patch deployment, run the data sync
 Drop down tab Navigator --> Administration Management --> Manage Application Data --> highlight EBS Instance datafiled line --> Synchronize --> Run Now --> Access -- Confirmation OK
Wait until the re-sync of ETL's from EBSO Data source is successful. (watch grc.log which will show you the status of the job).
  ##Check the GRC version, it should give 8.6.3.6012
  $ grep -i version /sid/ias/AACG863/tomcat/webapps/grc/WEB-INF/conf/grc.properties
                # GRC build version
                grc.version = GRC-all-8.6.3.6012
                grc.required.version = GRCC-8.6.0

16.upgrade from 8.6.3.6012 to 8.6.3.6025
  Shut down the Tomcat application server
    /<sid>/ias/AACG863/tomcat/bin/shutdown.sh
  unzip the patch
  Repeat the same steps from 5 to 15 again for 8.6.3.6025 , Patch: 14119308

17.upgrade from 8.6.3.6025 to 8.6.3.6031
   Shut down the Tomcat application server
    /<sid>/ias/AACG863/tomcat/bin/shutdown.sh
   unzip the patch
   Repeat the same steps from 5 to 15 again for 8.6.3.6031 , Patch: 14238616 

18.upgrade from 8.6.3.6031 to 8.6.3.6032
   Shut down the Tomcat application server
    /<sid>/ias/AACG863/tomcat/bin/shutdown.sh
   unzip the patch
   Repeat the same steps from 5 to 15 again for 8.6.3.6032 , Patch: 14258741

19.upgrade from 8.6.3.6032 to 8.6.3.6036
   Shut down the Tomcat application server
    /<sid>/ias/AACG863/tomcat/bin/shutdown.sh
   unzip the patch
   Repeat the same steps from 5 to 15 again for 8.6.3.6036 , Patch: 14572366



Reference Document IDs:
Upgrade Paths to Governance and Risk Compliance Controls (EGRCC) 8.6.4 (8.6.4.5259) (Doc ID 1225726.1): 
Critical Patch Information for Oracle AACG/TCG (Upto Version 8.6.3) (Doc ID 978690.1):
GRC Suite Certification Matrix (Doc ID 741001.1) 

Tuesday, November 13, 2012

Forms Servlet mode to Socket mode changing


1. Shutdown the middle tiers.
2. Change to servlet mode as follows:
i. Change to servlet mode
Login to the concurrent manager middle tier as ap<sid> user and do the following:
Replace the below command with the "Apps password"
$FND_TOP/bin/txkrun.pl -script=ChangeFormsMode \
-contextfile=$CONTEXT_FILE \
-mode=servlet \
-runautoconfig=No \
-appspass=<APPS password>

ii. Run autoconfig for servlet mode to take effect
Login to the concurrent manager middle tier as ap<sid> user and do the following:
$ cd $AD_TOP/bin
$ ./adconfig.sh contextfile=$CONTEXT_FILE appspass=<apps pwd>
Make sure the log file has no errors.
3. Change oc4jadmin password
Login to the concurrent manager middle tier as ap<sid> user and do the following:
a. Back up the original system-jazn-data.xml file
$ cp -pr $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
$INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml.ori
b. Change oc4jadmin password
$ vi $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
Change the below line alone as follows in the file so that it looks like below after change:
<credentials>!welcome</credentials>
========= with change ============================
                        <user>
                                <name>oc4jadmin</name>
                                <display-name>OC4J Administrator</display-name>
                                <description>OC4J Administrator</description>
                                <credentials>!welcome</credentials>
                        </user>
                       <user>
===================================================
4. Startup the opmnctl servers alone
Login to the concurrent manager middle tier as ap<sid> user and do the following:
$ cd $SCRIPT_TOP
$ ./adopmnctl startall
5. Deploying a New Forms EAR File
a. Run the following command to make sure your password is correct :
$AF_JRE_TOP/bin/java -jar $ORACLE_HOME/../1013/j2ee/home/admin_client.jar deployer:oc4j:opmn://iehibu08.iehibdom.com:6510/forms oc4jadmin welcome -validateURI
b. If the above script in Step 5.a. succeeded then Run deployment script as follows:
$ $FND_TOP/bin/txkrun.pl -script=CfgOC4JApp
Enter the following when prompted:
Enter Application name for re-deployment ? forms
Enter Oc4j Instance password for re-deployment ? welcome
Run Autoconfig <Yes/No> ? No
Check the logfile for any errors
c. Shutdown the opmnctl servers
Login to the concurrent manager middle tier as ap<sid> user and do the following:
$ cd $SCRIPT_TOP
$ ./adopmnctl stopall
Make sure all the processes running as ap<sid> are down.
d. Carry out post-deployment tasks (Carry this out if Step 5.b. above had no errors)
i. Restore backed up file
$ cp -pr $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
$INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml.passwdchg
$ mv $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml.ori
$INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
6. Startup middle tiers services.