Vous êtes sur la page 1sur 6

Lab-1 Goal: To change the Webport Number You need to change the web port number from current

port to current+20 1. Start all services if down. 2. Log on to Oracle Applications as SYSADMIN 3. Choose a responsibility that includes Oracle Applications Manager as an option. 4. Click AutoConfig under Oracle Applications Manager. 5. Click the pencil icon in the Edit Parameters (rightmost) column of the application tier context file row. 6. Click each of the parameter tabs to become familiar with the various parameters you can update. 7. Click the oa_ports tab. 8. In the Title column, click on the + sign to expand oa_ports (if it is not expanded already). 9. Make a note of the existing Active Web Port (s_active_webport) port number, then update the value of this parameter to "current+20" 10. Click Save 11. Answer "Yes" to any prompt, "The following parameters depend on the parameter you just changed. Do you also want to update them?" 12. Log out of Oracle Applications Manager.

Lab-2 Goal: To run Autoconfig in Test mode 1. Run the AutoConfig script in test mode. Script located at $AD_TOP/bin $ sh adchkcfg.sh 2. Respond to the prompts. 3. View the AutoConfig Configuration report.

Lab-3 Goal : Running autoconfig normally 1. Go to $ADMIN_SCRIPTS_HOME 2. Run sh adautoconfig.sh 3. Answer the prompts To make the Lab-1 changed ineffect (restart Apache/HTTP Server) 1. Go to $APDMIN_SCRIPTS_HOME 2. Run sh adapcctl.sh stop 3. Run sh adsapcctl.sh start

Access the application with the new port http://hostname.domainname:port

Lab 4 Goal: Rolling back an autoconfig session Each execution of AutoConfig creates a roll back script in case you want to revert back to the previous configuration settings. For this we perform the following steps: Step 1 :Shut down all services: $ cd $ADMIN_SCRIPTS_HOME $ adstpall.sh APPS/<APPS password>

Step 2:Restore AutoConfig session. $ cd $INST_TOP>/admin/out/MMDDhhmm $ restore.sh

Step 3 : Restart all services: $ $ADMIN_SCRIPTS_HOME/adstrtal.sh APPS/<APPS password> This will restore the application to the old webport number.

Lab 5 Goal: To change the forms mode from servlet to socket. Follow the below steps for changing from forms servlet mode to forms socket mode. Also note that both these modes cannot co-exits. 1) Stop all services using adstpall.sh present in $ADMIN_SCRIPTS_HOME location. Note that while stopping this will call adformsctl.sh script for stopping forms services. This is because the current mode is servlet mode. 2) Run the following command to enable Forms Socket Mode: $FND_TOP/bin/txkrun.pl -script=ChangeFormsMode [-contextfile=<CONTEXT_FILE>] -mode=socket [-port=<Forms port number>] -runautoconfig=<No or Yes> -appspass=<APPS password> Example : $FND_TOP/bin/txkrun.pl -script=ChangeFormsMode -contextfile=$INST_TOP/appl/admin/mycontext.xml -mode=socket -port=9095 -runautoconfig=No If you get any conflict please change the port number.

After running the above script then run autoconfig. I think you might be aware of the script now !!!! 3) start the services using adstrtall.sh present in $ADMIN_SCRIPTS_HOME Note that this time it will use adformsrvctl.sh script to start the forms. This is the script for starting forms in socket mode. After converting to forms socket mode the profile option ICX_FORMS_LAUNCHER will take below form. http://hostname.domainname:port/OA_HTML/frmservlet Also adopmnctl.sh will not list the forms process now. Check it by running

$adopmnctl.sh status

Vous aimerez peut-être aussi