Oracle Online Training Materials – Usage Agreement

Use of this Site (“Site”) or Materials constitutes agreement with the following terms and conditions:

1. Oracle Corporation (“Oracle”) is pleased to allow its business partner (“Partner”) to download and copy the information, documents, and the online training courses (collectively, “Materials") found on this Site. The use of the Materials is restricted to the non-commercial, internal training of the Partner’s employees only. The Materials may not be used for training, promotion, or sales to customers or other partners or third parties.

2. All the Materials are trademarks of Oracle and are proprietary information of Oracle. Partner or other third party at no time has any right to resell, redistribute or create derivative works from the Materials.

3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any Materials.  Materials are provided "as is" without warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.

4. Under no circumstances shall Oracle be liable for any loss, damage, liability or expense incurred or suffered which is claimed to have resulted from use of this Site of Materials. As a condition of use of the Materials, Partner agrees to indemnify Oracle from and against any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys' fees) arising out of Partner’s use of the Materials.

Purpose:This document provides an overview of features and enhancements included in Release 12. It is intended solely to help you assess the business benefits of upgrading to Release 12. 

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code. 

Disclaimer:

Techstack Overview

Oracle Applications Release 12

Agenda

• Oracle Application Server 10g Release 3 (10.1.3)

• File system Changes in R12

• OC4J Primer

• Forms Primer

<Insert Picture Here>

Oracle Application Server 10g Release 3 (10.1.3)

Oracle Application Server 10g Release 3 (10.1.3)

• Oracle Application Server (OAS) Component Overview• Oracle HTTP Server• OC4J• OPMNR12 does not include (not covered here)• Web Cache• OID/SSO• Portal• Discover 10.1.2

10.1.3

3-Tier Logical Architecture – Reminder

R11i Technology Stack

User Interface Application logic Database logic

Application

JSP

Forms

Reports

BC4J

Servlet

Engine(Jserv)

Web

Lis

ten

er

UIX

Client

9i or 10g

Database

9iAS 1.0.2.2

99iiR2 &R2 &10g (Optional)10g (Optional)

JInitiator

iAS 1.0.2.2.2iAS 1.0.2.2.2

User Interface Application logic Database logic

Application

JSP

Forms

Reports

BC4J

OC4J

Web

Lis

ten

er

UIX

Client

9i or 10g

Database

9iAS 1.0.2.2

3-Tier Logical ArchitectureR12 Technology Stack

Oracle HTTP Server

• Provides key infrastructure for serving the Internet’s HTTP protocol.

• HTTP Server is used to return response for both process to process and human generated requests from browsers.

• An HTTP server listener handles incoming requests and routes them to the appropriate processing utility.

• R12 uses OAS 10.1.3, HTTP Server is based on Apache 1.3.34 for integration with OAS.

• 11i uses OAS 1.0.x., Apache 1.3.19.

HTTP Server Modules

• Modules extend the basic functionality of the Web server.

• Support integration between HTTP Server and other Oracle Application Server components.

• HTTP Server includes many standard modules.• Oracle includes several modules specific to HTTP

Server.• 11i and R12 both use modules.

HTTP Server Modules

HTTP Server Modules

R12 and Mods

• R12 does not have a dedicated HTTP listener for server pl/sql requests.

• Mod_plsql is disabled in R12 to comply with more stringent security policies.

• R12 uses mod_oc4j this is a replacement of mod_jserv which is used in 11i.

• Mod_osso is used for Single Sign On integration.

Oracle Containers for J2EE (OC4J)

• Oracle Containers for Java (OC4J) Enterprise Edition (J2EE) 1.4 is the Java runtime engine of Oracle Application Server.

• Provides the containers, API’s and services required for creating, hosting portable applications.

• Release 12 runs under a managed configuration, in which OC4J is installed and managed as a component of Oracle Application Server 10.1.3

OC4J

• Servlets, JSP’s and EJB’s can be executed through OC4J .

• OC4J is the replacement to 11i Jserv for running servlets.

• Based on strict J2EE standards which include

Specific directory structure, File name and content convention, XML file definition.

• R12 uses JDK 5.0 all (web components, concurrent processing, sun java plug-in).

OC4J Standards Based

OC4J Standards Based

Mod_oc4j

• Incoming HTTP request is received by the HTTP Server listener.

• HTTP Server passes requests to an OC4J via the mod_oc4j module.

HTTP Server Process

oacoreforms

oafm

OPMN

• Oracle Process Manager and Notification Server (OPMN) is installed and configured for every AS installation.

• OPMN provides an integrated way to manage all OAS components.

• R12 delivers a set of standard control scripts for starting/stopping components, these rely on OPMN command line tool.

• The name of these AD scripts (i.e adapcctl.sh, adstrtall.sh ..) remain the same as in 11i.

OPMN

• OPMN Consists of two main pieces• Process Manager (PM)

• For every managed process, it monitors, starts, stops, does death-detection which includes automated restart of the processes.

• Oracle Notification Server (ONS)• Delivers notification between components.

• Core: Parses config file and launches scripts.

R12 Deployment

• R12 application is pre-deployed by Rapid install and maintained by adpatch.

• Autoconfig is still used to manage the configuration files.

• Opatch is used to apply patches to both 10.1.3 and 10.1.2 oracle homes.

• J2EE application is assembled and delivered as an Enterprise Archive (ear) file. This is a standard Jar file and holds all other required files.

11i Installed & Managed File System

COMMON TOP

APPL TOP

Jserv

Apache 1.3

RSF 8.1.7

iAS 1.0.2.2ORACLE HOME

Reports 6

Forms 6

RSF 8.0.6

Developer6iORACLE HOME

RDBMSComponents

RSF 10.2

DatabaseORACLE HOME

Major Components:

•Java Home: 8.1.7-based iAS 1.0.2

•C Home: 8.0.6-based Developer 6

•Database Home: 10.2

•Appl Top: Applications’ code staging area

•Common Top: Runtime location for Java, HTML, run-time generated files

R12 Installed & Managed File System

COMMON TOP

APPL TOP

Apache 1.3

OC4J

RSF 10.1

iAS 10.1.3ORACLE HOME

Reports 10

Forms 10

RSF 10.1

Developer10.1.2ORACLE HOME

RDBMSComponents

RSF 10.2

DatabaseORACLE HOME

Major Components:

•Java Home: 10.1-based iAS 10.1.3 –new

•C Home: 10.1-based Developer 10 standalone install of AS 10.1.2 phase2 –new

•Database Home: 10.2

•Appl Top: Applications’ code staging area

•Common Top: Runtime location for Java, HTML

•Instance Top: configuration and run-time generated files –newINSTANCE TOP

Desktop Client Tier

• Moving from JInitiator to Native Sun Java plug-in• Native Sun J2SE 1.5 (5.0)

• Supported Browsers:

Browser Version Client OS

Browser - IE 6.0 Windows 2000 and XP

Browser - Netscape 7.2 Windows 2000 and XP

Browser - FireFox 1.5 Windows 2000 and XP

Browser - Safari 2.0 Macintosh OSX 10.4

R12 OC4J’s

OC4J instances/applications deployed under 10.1.3 using oc4j (mod_oc4j). This currently includes

• Oacore • Forms• OAFM (Oracle Application Fusion Middleware)

Mapviewer

WebServices

…

R12 Managed

oacore

formsoafm

OPMN

Adstrtall/adstpall.sh

R12 Status./adapcctl.sh status

You are running adapcctl.sh version 120.5

Checking status of OPMN managed Oracle HTTP Server (OHS) instance ...

Processes in Instance: VIS_aaaa.aaaa.uk.oracle.com-------------------+--------------------+---------+---------ias-component | process-type | pid | status-------------------+--------------------+---------+---------OC4J | oafm | 9457 | AliveOC4J | forms | 9391 | AliveOC4J | oacore | 9275 | AliveHTTP_Server | HTTP_Server | 9553 | AliveASG | ASG | N/A | Down

adapcctl.sh: exiting with status 0

AD scripts wraps opmnctl.sh script

R12 oc4j/applications deployed to OAS.

HTTP Server is also deployed as an OC4J Application.

<Insert Picture Here>

File System Changes in R12

Release 12 File System Changes

• Rapid Install/Rapid Clone layout• db, apps, inst

• Instance Home• Configuration, logs, certificates

• JAVA_TOP• lib and classes directories

• OA_HTML• j2ee structure changes• webapps/oacore/html/WEB-INF

R12 Filesystem Overview

Default file system layout• Database (10.2.0)• Application

10.1.210.1.3 Appl_topCommon_top

• Instance ConfigLogsscripts

Release 12 Filesystem

• Rapid Install/Rapid Clone will implement• <apps_base>/db/tech_st/10.2.0• <apps_base>/db/apps_st/data

• <apps_base>/apps/tech_st/10.1.2• <apps_base>/apps/tech_st/10.1.3• <apps_base>/apps/apps_st/appl• <apps_base>/apps/apps_st/comn

• <apps_base>/inst/apps/<context_name>

Instance Home Advantages…

• Configuration and log files are centrally located in a config home

• Clear distinction between location of code, configuration and logs

• Ability to place the config home on a Network or a local file system for performance improvement

Instance Home More…

• Ability to share code (Apps, Techstack) among multiple instances ( Dev,Test, Production)

• Collection of configuration and logs is much easier since they are centrally located

• Ability to split ownership of apps and technology stack file systems

Instance Home

• Instance or Configuration Home• Contains instance specific files

• Configuration• Logs• Scripts• Default location

• <apps_base>/inst/apps/<context_name>

• Implementation of shared file system and/or read-only ORACLE_HOME’s and APPL_TOP

• Standalone instance also implemented this way

Instance Home - structure

• <apps_base>/inst/apps/<context_name> ($INST_TOP)

• /admin• /scripts ($ADMIN_SCRIPTS_HOME)

• /appl ($APPL_CONFIG_HOME)• /fnd/12.0.0/secure ($FND_SECURE)

• /certs• /logs ($LOG_HOME)

• /ora ($ORA_CONFIG_HOME)

• /10.1.2• /10.1.3 ($ORACLE_CONFIG_HOME)

• /pids• /portal

Instance Home - admin

• <apps_base>/inst/apps/<context_name>/admin• /install• /log … AutoConifg writes logs here

• /out

• /scripts adautocfg.sh - run autoconfigadstpall.sh - stop all servicesadstrtal.sh - start all servicesadapcctl.sh - start/stop/status Apache onlyadformsctl.sh - start/stop/status OC4J Formsadoacorectl.sh - start/stop/status OC4J oacoreadopmnctl.sh - start/stop/status opmnadalnctl.sh - start/stop RPC listeners (FNDFS/FNDSM) adcmctl.sh - start/stop Concurrent Manager gsmstart.sh - start/stop FNDSMjtffmctl.sh - start/stop Fulfillment Serveradpreclone.pl - Cloning preparation scriptadexecsql.pl - Execute sql scripts that update the profiles in an AutoConfig run

java.sh - Call java executable with additional args, (used by opmn, Conc. Mgr)

Instance Home - appl

• <apps_base>/inst/apps/<context_name>/appl $APPL_CONFIG_HOME *

• /admin• Empty in standalone instance where APPL_CONFIG_HOME value is APPL_TOP• Contains these files if APPL_CONFIG_HOME value is not APPL_TOP

topfile.txt, adjareas.txt, adjborg2.txt, adjborg.txt,

adovars.env, adconfig.txt, <CONTEXT_FILE>.xml

• /fnd/12.0.0/secure $FND_SECURE

* For a standalone instance APPL_CONFIG_HOME will be set to $APPL_TOP A small set of files created by AutoConfig that are used by adpatch are still required in APPL_TOP. (Context variable s_appl_config_home)In a multi node environment, only the node where adpatch is run is APPL_CONFIG_HOME set to APPL_TOP. Other nodes are set to s_config_home/appl in the context file. (AD bug 4915840 closed status 44)

Instance Home - certs

• <apps_base>/inst/apps/<context_name>/certs• /Apache• ewallet.p12

• /opmn• cwallet.sso• ewallet.p12

certs is the default directory for SSL or other certificate files used

by this instance. To use a centrally stage certificate change the

appropriate context file variables(s_web_ssl_directory and s_websrv_wallet_file) and run AutoConfig

Instance Home - logs• <apps_base>/inst/apps/<context_name>/logs $LOG_HOME

• /appl• /admin• /conc $APPLCSF

• /oam• /rgf $APPLRGF

• /ora• /10.1.2/network• /10.1.3

• /Apache• /j2ee/forms• /j2ee/oacore• /j2ee/oafm• /javacache• /opmn

• adpatch logs still created in $APPL_TOP• AutoConfig logs created in $INST_TOP/admin/logs

Instance Home – ora/10.1.2• <apps_base>/inst/apps/<context_name>/ora/10.1.2

• <context_name>.env• /forms/server

• appsweb.cfg• default.env• ftrace.cfg

/network/admin $TNS_ADMIN

• listener.ora• tnsnames.ora

This is the configuration for the ‘C’ ORACLE_HOME, set when runningConcurrent Managers and AD utilities.

Instance Home – ora/10.1.3

• <apps_base>/inst/apps/<context_name>/ora/10.1.3 $ORACLE_CONFIG_HOME

• <context_name>.env• /Apache/Apache/conf

• apps.conf, httpd.conf, oracle_apache.conf, ssl.conf• dms.conf, mod_oc4j.conf, security.conf, url_fw.conf

• /config• ias.properties (used by EM agent)

• /j2ee/oacore/config• applications.xml, default-web-site.xml, global-web-application.xml• j2ee-logging.xml, jms.xml, oc4j-connectors.xml, oc4j.properties,• rmi.xml, server.xml, system-application.xml, system-jazn-data.xml

• /j2ee/oacore /application-deployments/oacore• orion-application.xml

• /j2ee/oacore /application-deployments/oacore/html• orion-web.xml

• /j2ee/forms/config and /j2ee/oafm/config (same files as for oacore)

Instance Home – ora/10.1.3

• <apps_base>/inst/apps/<context_name>/ora/10.1.3 (continued…)

• /javacache• /network/admin $TNS_ADMIN

• listener.ora, tnsnames.ora

• /opmn• /bin/opmnctl• /conf/opmn.xml …. root of 10.1.3 configuration

• /logs *• HTTP_Server~1• OC4J~forms~default_group~1• OC4J~oacore~default_group~1

* opmn/logs directory cannot be moved from here.

Instance Home – pids

• <apps_base>/inst/apps/<context_name>/pids *• /10.1.3/Apache

• httpd.pid• httpd.lock

• /appl• reviver.sh_<context_name>.pid (for Conc. Manager)

* pids directory should be located on machines local disk

• <apps_base>/inst/apps/<context_name>/portal• aplogin.html, index.html, etc

COMMON_TOP Changes - java

• $COMMON_TOP/java ($JAVA_BASE)• /classes ($JAVA_TOP)• Contains expanded class file directories

• /lib ($AF_JLIB)• Contains zip and jar files

adovars.env changed to implement these changes.

The reason for this change is due to the way OC4J automatically includes zip and jar files into the CLASSPATH. Before making this change, including $JAVA_TOP to pick up the expanded classes directories picked all the zip and jar files causing class version conflicts at OC4J startup.

COMMON_TOP Changes - html

• $COMMON_TOP/webapps• /oacore/html ($OA_HTML)

• Contains all the .html, .jsp, .css, .xml files• This change made to meet J2EE requirements

• Extra files to meet J2EE requirements• /webapps/oacore/html/WEB-INF/web.xml

• web.xml normally contains servlet definitions and mappings. To implement shared file system, this information is configured in $ORACLE_CONFIG_HOME/j2ee/oacore /application-deployments/oacore/html/orion-web.xml

• web.xml is a basic file with no servlet definitions, shared by all instances

• /webapps/oacore/META-INF/application.xml

ApacheR12 changes from 11i• Some configuration/directives split from the main

httpd.conf into separate .conf files (ssl)• Apache/Apache/logs now written to

$LOG_HOME/ora/10.1.3/Apache

Apache/Apache/Apache/conf

These are all flat files.• apps.conf includes alias mappings.

• httpd.conf same as 11i, apache server configuration file.

• oracle_apache.conf has an include for the apps.conf. No plsql.conf.

• ssl.conf ssl configuration split out from httpd.conf into a seperate file.

• dms.conf dms configuration split from httpd.conf into a seperate file.

• mod_oc4j.conf described earlier, loads the mod_oc4j.so.

• security.conf as per 11i, includes security related restrictions.

• url_fw.conf includes rewriterules for urls which which must be allowed access and not denied access.

R12 10.1.3

• /j2ee/oacore/config• applications.xml, default-web-site.xml, global-web-application.xml• j2ee-logging.xml, jms.xml, oc4j-connectors.xml, oc4j.properties,• rmi.xml, server.xml, system-application.xml, system-jazn-data.xml

• /j2ee/oacore /application-deployments/oacore• orion-application.xml

• /j2ee/oacore /application-deployments/oacore/html• orion-web.xml

• /j2ee/forms/config and /j2ee/oafm/config (same files as for oacore)

• These files represent the core J2EE configuration files which makeup R12 deployment in OAS 10.1.3.

Configuration Files

<Insert Picture Here>

OC4J Primer

Latest Standards-Based Technology

• Oracle Application Server 10gR3 (10.1.3) is the latest production version

• OC4J is based on J2EE standards:• Specific directory structure• File requirements (content & naming convention)• XML file definition

• R12 creates 3 OC4J instances:• Oacore (runs OA Framework-based applications), Forms

(runs Forms-base applications), OAFM (ws, mapviewer, ascontrol)

Top Level Directory

• 10.1.3/...env file:ORACLE_HOME, LD_LIBRARY_PATH, PATH, TNS_ADMIN, TWOTASK ..

• /Apache/Apache/conf/apps.conf, httpd.conf ...• OC4J: oacore & forms/application (application deployed from this directory.)/application-deployment (oc4j deploys to application-

deployments and uses these when starting and restarting your application.)

/config (common settings for all J2EE applications for this instance.)

OC4J Deployment

• Servlet deployed to OC4J server must adhere to J2EE specification

• Deployment is through an Enterprise Archive (ear) file, includes the application code (JAR) and Web Application (WAR files, servlets, jsp code)

• Formsapps.ear 10.1.2 is deployed to the 10.1.3

Server.xml

• OC4J server configuration file.

J2EE application specification.10.1.3/j2ee/oacore/config/server.xml <shared-library name="oracle.jdbc" version="12.0.0" library-

compatible="true"><code-source path="/d1/home/user2/r12/visr12comn/java/jdbc14.zip"/>

<application name="oacore" path="/d1/home/user2/r12/visr12comn" start="true" />

</shared-library>

10.1.3/j2ee/forms/config/server.xml <application name="forms" path="../applications/forms.ear"

parent="default" start="true" />

Forms.ear

-bash-2.05b$ unzip -l forms.ear

689 04-29-04 14:01 META-INF/application.xml

197180 07-14-05 01:33 formsweb.war

-bash-2.05b$ unzip -l formsweb.war

Archive: formsweb.war

0 07-14-05 01:33 WEB-INF/

0 07-14-05 01:33 WEB-INF/lib/

204444 07-14-05 01:33 WEB-INF/lib/frmsrv.jar

691 07-14-05 01:33 WEB-INF/orion-web.xml

3165 07-14-05 01:33 WEB-INF/web.xml

Orion-application.xml

• OC4J definition.

10.1.3/j2ee/oacore/application-deployments/oacore/orion-application.xml

Location of apps classes:

<library path="/d1/home/user2/r12/visr12comn/java/classes" />

10.1.3/j2ee/forms/application-deployments/forms

<web-module id="formsweb" path="formsweb.war" />

Orion–web.xml

• Servlet configuration file:j2ee/forms/application-deployments/forms/formsweb/orion-web.xml <context-param-mapping

name="configFileName">/d1/home/user2/r12/visr12comn/config/VISR12_ap6001atg/forms/server/formsweb.cfg</context-param-mapping>

<virtual-directory virtual-path="/html" real-path="/d1/home/user2/r12/visr12ora/10.1.2/tools/web/html" />

<virtual-directory virtual-path="/java" real-path="/d1/home/user2/r12/visr12ora/10.1.2/forms/java" />

<virtual-directory virtual-path="/webutil" real-path="/d1/home/user2/r12/visr12ora/10.1.2/forms/webutil" />

<virtual-directory virtual-path="/jinitiator" real-path="/d1/home/user2/r12/visr12ora/10.1.2/jinit" />

OPMN Start/Stop• opmnctl stopall/startall• opmnctl stopproc type=oc4j instancename=oacoreopmnctl: stopping opmn managed processes...opmnctl statusProcesses in Instance: VISR12_ap6001atg.ap6001atg.us.oracle.com--------------------------+-------------------------+------------+---------ias-component | process-type | pid | status--------------------------+-------------------------+------------+---------OC4J | forms | 20985 | AliveOC4J | oacore | N/A | DownOC4J | home | 20947 | AliveHTTP_Server | HTTP_Server | 20946 | Alive

• opmnctl stopproc ias-component=HTTP_Server• opmnctl status –l (-l display ports)

OPMN Setting Log Level

• Edit configuration file to permanently set level:

10.1.3/opmn/conf/opmn.xml<opmn xmlns="http://www.oracle.com/ias-instance">

<log path="$ORACLE_HOME/opmn/logs/opmn.log" comp="internal;ons;pm" rotation-size="1500000"/>

<debug path="$ORACLE_HOME/opmn/logs/opmn.dbg" comp="" rotation-size="1500000"

/>

Application Server Control ASC

• Runs as a J2EE application (ascontrol) that runs within every OC4J container created.Oracle HTTP Server port(:7777/em user oc4jadmin).

• Prior releases (10.1.2, 9.0.4.. ) required a separate agent. Start emctl start iasconsole. Different Port no.

• Uses less disk space and fewer system resources• UI to deploy J2EE applications• Configure auditing, logging, security, performance• Role-Based Administration

<Insert Picture Here>

Forms10 Primer

What’s New in Forms 10

• Forms Servlet Listener is default. There is no Forms Server Listener or Client/Server mode

• Native forms runtime executable with shared library for user exits, replaces the statically linked Applications runtime executable

• Forms Trace in addition to Forms Runtime Diagnostics (FRD)

• Updated Swan UI• FORMS_ environment variables replace FORMS60_.• New environment variables e.g.

FORMS_TRACE_DIR.

What’s New in Forms10• The forms builder is not installed as part of the 10.1.2

home. • The forms builder needs to be installed separately as

part of the Developer Suite (may change based on outcome of 4758443).• $ORACLE_HOME/bin/frmbld.sh replaces f60desm for design.• Modify the frmbld.sh shell script to customize settings e.g.

FORMS_PATH.

• Generation tools are delivered as part of the Runtime Services and Developer Suite installations. • frmcmp.sh and frmcmp_batch for generation.• Modify the shell script to customize settings.

Configuration Files• $COMMON_TOP/config/<identifier>/forms/server/

• default.env• Equivalent of formservlet.ini from 11i• Defines the runtime environment variables e.g.

FORMS_USEREXITS=libfmxit.so• Autoconfig generated from txkGenDefaultEnv.tmp• Example File

• formsweb.cfg (may change to appsweb.cfg)• Equivalent to the appsbase_<identifier>.cfg from 11i • Defines parameter values used by the Forms Servlet• Autoconfig generated from forms_web_1012_cfg.tmp.• Custom sections to define specific sections.• Example File

Service Management• Applications scripts adstrtal.sh and adstpall.sh will be used to

make a call to the Oracle Process Monitoring and Notification (OPMN).

• Direct call to OPMN to stop and start through• $ORACLE_HOME_1013/bin/opmnctl startall• $ORACLE_HOME_1013/bin/opmnctl stopall

• Manually start and stop forms via• $ORACLE_HOME_1013/bin/opmnctl startproc type=oc4j

instancename=forms• $ORACLE_HOME_1013/bin/opmnctl stopproc type=oc4j

instancename=forms

• Component, process-type, pid and status can be viewed using • $ORACLE_HOME_1013/bin/opmnctl status

Servlet Logging Tools

• Invoked from URL or addition to the forms web configuration file e.g. ?serverURL=/forms/lservlet/debug

• $ORACLE_HOME_1013/j2ee/forms/application-deployments/forms/forms_default_group_1/application.log

• Default: No log messages except an entry stating the name and path of the configuration file being used i.e.

bash-2.05b$ more application.log 06/02/02 06:38:59.125 10.1.3.0.0 Started06/02/02 06:39:04.533 formsweb: FormsServlet init(): configFileName: /d1/home/user2/r12/visr12comn/config/VISR12_ap6001atg/forms/server/formsweb.cfg testMode: false06/02/02 06:39:04.569 formsweb: 10.1.3.0.0 Started

bash-2.05b$ more application.log 06/02/02 06:38:59.125 10.1.3.0.0 Started06/02/02 06:39:04.533 formsweb: FormsServlet init(): configFileName: /d1/home/user2/r12/visr12comn/config/VISR12_ap6001atg/forms/server/formsweb.cfg testMode: false06/02/02 06:39:04.569 formsweb: 10.1.3.0.0 Started

Servlet Logging Tools

• /session --the host name and IP address of the client, the runtime process id, and a unique internal session id number.

• /sessionperf --Performance summary statistics are included with the session end message.

• /perf --A performance message is written for every request from the client.

• /debug --Full debug messages.

Useful Links

Useful LinksUseful Links

OAS 10.1.3 Documentation Library

http://iasdocs.us.oracle.com/iasdl/101300doc_final/index.htm

Oracle Technology Network http://www.oracle.com/technology/products/ias/index.html

Oracle E-Business Suite Release 12 Blog

http://blogs.oracle.com/schan/release12

AQ&