Professional Documents
Culture Documents
STOP
cd $ADMIN_SCRIPTS_HOME
./mwactlwrpr.sh stop sysadmin/pwd
Log Directories:
mwa.logdir= $INST_TOP/logs
CFG file:
$INST_TOP/admin/install/mwa.cfg
Forms & Report version (aka developer 6i) in 11i >> Log in as Application user, set environment
variable and run below query
$ORACLE_HOME/bin/f60run | grep Version | grep Forms
output like
Forms 6.0 (Forms Runtime) Version 6.0.8.25.2 (Production)
Check fourth character in version 25 which means Forms 6i patchset 16 (25-9)
Forms & Report version in R12/12i Log in as Application user, set environment variable and run below
query
$ORACLE_HOME/bin/rwrun | grep Release
or rwrun help=yes | grep Release
Output should be like
Report Builder: Release 10.1.2.2.0
You can safely ignore warnings
Log in as Application user, set environment variable and run below query
grep jinit_ver_comma $CONTEXT_FILE
or
strings $AU_TOP/resource/.pll | grep -i header
OA Framework Version
http:// hostname.domainName:port/OA_HTML/OAInfo.jsp (Only for 11i); Log in as Application user, set
environment variable and run below query
$ORACLE_HOME/bin/oidldapd -version
output should look like
version: 1
dn:
orcldirectoryversion: OID 10.1.4.0.1
Application Server
Oracle Application Server (Prior to Oracle WebLogic Server)
If application server is registered in database (Portal, Discoverer) check from database
SQL> select * from ias_versions;
or
SQL>select * from INTERNET_APPSERVER_REGISTRY.SCHEMA_VERSIONS;
Oracle Portal
SQL> select version from portal.wwc_version$;
Database Component
I) Oracle Database
To find database version
SQL> select * from v$version;
or
All component version in database
i) adstrtal.sh
Master script to start all components/services of middle tier or application tier. This script will use
Service Control API to start all services which are enabled after checking them in context file
(SID_HOSTNAME.xml or CONTEXT_NAME.xml)
ii) adstpall.sh
Master script to stop all components/services of middle tier or application tier.
iii) adalnctl.sh
Script to start / stop apps listener (FNDFS and FNDFS). This listener will file will be in 10.1.2
ORACLE_HOME (i.e. Forms & Reports Home)
listener.ora file will be in $INST_TOP/apps/$CONTEXT_NAME/ora/10.1.2/network/admin directory
(Mostly similar to one in 11i with only change in ORACLE_HOME i.e. from 8.0.6 to 10.1.2 )
iv) adapcctl.sh
Script to start/stop Web Server or Oracle HTTP Server. This script uses opmn (Oracle Process Manager
and Notification Server) with syntax similar to opmnctl [startstop]proc ohs
like opmnctl stopproc ohs .
(In 11i this script directly used to call apachectl executable but now calls opmnctl which in turn calls
apachectl. In 11i web server oracle home was 1.0.2.2.2 but in R12 its 10.1.3)
v) adcmctl.sh
Script to start / stop concurrent manager, Similar to one in 11i. (This script in turn calls startmgr.sh )
vi) adformsctl.sh
Script to start / stop Forms OC4J from 10.1.3 Oracle_Home. This script will also use opmnctl to
start/stop Forms OC4J like
opmnctl stopproc type=oc4j instancename=forms
vii) adformsrvctl.sh
This script is used only if you wish to start forms in socket mode. Default forms connect method in R12
is servlet.
If started this will start frmsrv executable from 10.1.2 Oracle_Home in Apps R12
viii) adoacorectl.sh
This script will start/stop oacore OC4J in 10.1.3 Oracle_Home. This scripts will also use opmnctl
(similar to adapcctl & adformsctl) to start oacore instance of OC4J like
opmnctl startproc type=oc4j instancename=oacore
ix) adoafmctl.sh
This script will start/stop oafm OC4J in 10.1.3 Oracle_Home. This scripts will also use opmnctl (similar
to above) to start oacore instance of OC4J like
opmnctl startproc type=oc4j instancename=oafm
x) adopmnctl.sh
This script will start/stop opmn service in 10.1.3 Oracle_Home. opmn will control all services in 10.1.3
Oracle_Home like web server or various oc4j instances. If any services are stopped abnormally opmn
will/should start them automatically.
xi) jtffmctl.sh
This script will be used to start/stop one to one fulfilment server.
xii) mwactl.sh
To start / stop mwa telnet server where mwa is mobile application.
Instance Top is new TOP added in R12 (to read more click here)
—–
If your clone on DB Tier fails while running txkConfigDBOcm.pl (Check metalink note - 415020.1)
During clone step on DB Tier it prompts for “Target System base directory for source homes” and
during this you have to give like /base_install_dir like ../../r12 and not oracle home like
../../r12/db/tech_st_10.2.0
—–
2) Application Tier
$ORACLE_HOME/j2ee/DevSuite/log
$ORACLE_HOME/opmn/logs
$ORACLE_HOME/network/logs
Tech Stack Patch 10.1.3 (Web/HTTP Server)
$IAS_ORACLE_HOME/j2ee/forms/logs
$IAS_ORACLE_HOME/j2ee/oafm/logs
$IAS_ORACLE_HOME/j2ee/oacore/logs
$IAS_ORACLE_HOME/opmn/logs
$IAS_ORACLE_HOME/network/log
$INST_TOP/logs/ora/10.1.2
$INST_TOP/logs/ora/10.1.3
$INST_TOP/logs/appl/conc/log
$INST_TOP/logs/appl/admin/log
Target system service groups - Enable Web Entry Point Services [disabled] :
Clone Context uses the same port pool mechanism as the Rapid Install.
Once you choose a port pool, Clone Context will validate the port availability.
Enter the port pool to be used for the target system node [0-99] :
1
1. /d01/oratst/inst/apps/TEST_servername1/appltmp
2. /usr/tmp
3. /d02/oratst/db/tech_st/10.2.0/appsutil/outbound/TEST_servername1
4. /d02/oratst/db/tech_st/10.2.0/appsutil/outbound/TEST_servername1
5. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1] : 2
Target system service groups - Enable Web Entry Point Services [disabled] : enabled
Target system service groups - Enable Web Application Services [disabled] : enabled
Target system service groups - Enable Batch Processing Services [enabled] : disabled
Do you want to continue (y/n) ? Type y to continue with current value of Configuration home. Type n
to abort. : y
Database port is 1522
Do you want the the target system to have the same port values as the source system (y/n) [y] ? :
Complete port information available at
/d01/oratst/apps/apps_st/comn/clone/bin/out/TEST_servername1/portpool.lst
1. /d01/oratst/inst/apps/TEST_servername1cosxaor0k/appltmp
2. /usr/tmp
3. /d02/oratst/db/tech_st/10.2.0/appsutil/outbound/TEST_servername1
4. /d02/oratst/db/tech_st/10.2.0/appsutil/outbound/TEST_servername1
5. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1] : 2
Services
(new concept introduced in R12) define the set of processes that will be started on each application
node. These services can be activated or deactivated on a specific application tier/node.
i) Root Service - Oracle Process Manager and Notification (OPMN) is part of Oracle Application Server
10G R2/R3. OPMN is used for inter process communication (between OC4J, HTTP Server), death
detection and start/stop of Services for 10g R3.
ii) Web Entry Point Services - HTTP Server is part of Oracle Application Server 10G R3 and built on
Apache (aka Oracle Apache. All web request to R12 first hit HTTP Server.
iii) Web Application Services - OACORE OC4J, Forms OC4J, OAFM OC4J - These are set of 3 OC4J
(Oracle Container for J2EE) to run application.
iv) Batch Processing Services - This set of service consist of Apps Listener (FNDFS & FNDSM), Concurrent
Manager, Fulfillment Server and Interaction Server
v) Other Services - Oracle Forms Service, Forms Metric Client/Server and Mobile Web Application
(MWA)Service
Important:
1) When you select Root services, Web Services are automatically selected i.e. First three Services
Root, Web Entry Point and Web Application Services can only be enabled or disabled together.
If you want Web Entry Point Services, Web Application Services, and Root Services to be installed on
different nodes then use autoconfig after installation.
2. In R12 with introduction of Services there is NO concept of Forms node or Web Node.
3. With default installation all services Root, Web Entry Point, Web Application Services, Batch
Processing and Otherservices are enabled.
406558.1 Configuring Applications Node Services in Oracle Applications Release 12 (Metalink Note)
Chapter2 of "Oracle® Applications Installation Guide: Using Rapid Install Release 12" at
http://download.oracle.com/docs/cd/B40089_10/current/acrobat/120oaig.pdf
JSP in R12
Here is the explaination why we need to compile jsp when ever we clear JCache.Here clearing JCache
means removing class files from JSP pages which will be there under the directory called
$COMMON_TOP/_pages.
So in Release 11i when ever we clear the JCache and after bouncing apache, new class files
are created automatically when the JSP page is called from a browser session and JSP was rendered
fine.
But incase of Release 12 it's observed that when calling the JSP no class file is created in the diretciry
$COMMON_TOP/_pages so we need to create it manually. We have an alternative method, but it is not
recommended.
An alternative is to change the value for the main_mode parameter to recompile (instead of justrun)
This can be achieved with the following steps
Use the Context editor to change the value for "s_jsp_main_mode" in the .xml file used by autoconfig
and change value from justrun to recompile
Run Autoconfig to propagate the changes to the configuration files
Verify that now the $INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-
web.xml has
main_mode
recompile
Test the scenario failing before.
See that now a new _.class is created when the JSP page is called.
For production environment the manual 'ojspcompile.pl' method is recommended for the following
reasons
With 'justrun' a fixed set of JSP is used which can not change due to maintenance actions. With
'recompile' the JSP pages replacing exsiting ones will recompile automatically while environment is up-
and-running. This may lead to errors for the users when compilation fails or different version of the JSP
being used within a single session.
Using 'justrun' skips the check if compilation is needed and therefor improves performance