<precise_col_username> identified by enable editions <precise_col_username> Install the Precise for Oracle collector agent with a user account with Editions Enabled as mentioned in the previous section. If either the Precise PMDB Oracle instance or the EBS Oracle database instance is on Oracle 12c, switch to using the 12c tuner by modifying the registry or use the sqlnet.ora workaround as mentioned in the following IDERA solution: https://idera.secure.force.com/precise/50133000000f80n?srPos=0=501.
Install Precise for Web collector agent and monitor the Web Apache and Web Weblogic instances.
For Web Apache, the httpd.conf file is in a location such as:
/u01/install/VISION/fs1/FMW_Home/webtier/instances/EBS_web_EBSDB_OHS1/config/OHS/EBS_web_EBSDB
For Web Weblogic, add the following jar to the classpath of oacore and oafm servers:
/products/www/instances/<instance id>/lib/psww_filter.jar
In Web Weblogic, instance installation action items for adding filter content for oacore and oafm servers using the web.xml are in a location similar to:
/u01/install/VISION/fs1/FMW_Home/Oracle_EBS-app1/applications/oacore/html/WEB-INF/web.xml
/u01/install/VISION/fs1/FMW_Home/Oracle_EBS-app1/applications/oafm/webservices/WEB-INF/web.xml
Install Precise for J2EE collector and monitor the OA Core, FM, and Forms J2EE instances. If EBS is based on a Weblogic Server, then the update of some arguments is done via Weblogic Console as mentioned in the action items screen. Once the Forms J2EE instance is installed, you can include custom instrumentation by adding a custom invocation type FORMS to Custom.xml under j2ee/config/<jvm>/ and the methods to instrument as well. Here is an example of adding the startProcess method of the class oracle.forms.servlet.RunformProcess.
<instrumenter-config>
<custom-config>
<java-classes>
<java-class>
<invocation-type>
FORMS
</invocation-type>
<class-name>
oracle.forms.servlet.RunformProcess<
</class-name>
<methods>
<method>
<name>
startProcess
</name>
</method>
</methods>
</java-class>
</java-classes>
</custom-config>
</instrumenter-config>
You can add more methods as per your requirement. If you need all the methods under the class oracle.forms.servlet.RunformProcess, you can edit the custom.xml as following:
<instrumenter-config>
<custom-config>
<java-classes>
<java-class>
<invocation-type>
FORMS
</invocation-type>
<class-name>
oracle.forms.servlet.RunformProcess
</class-name>
<methods>
<method>
<name>
*
</name>
<apply-to-subtypes>
true
</apply-to-subtypes>
</method>
</methods>
</java-class>
</java-classes>
</custom-config>
</instrumenter-config>
Add the Oracle Applications tier instance and configure the Forms server jvm to be used by this instance. EBS 12 is based on Forms 10g and is configured to run in servlet mode by default.
Add the following tag to the registry under instances/j2ee/<instance server>/<jvm>.xml:
<oa_collection_mode>forms_servlet</oa_collection_mode>
Restart the Precise for J2EE agent and restart the FORMS JVM.
The Interpoint for Oracle Applications identifies activities of Oracle Applications by monitoring the events that are called by forms. Configuring an Interpoint for Oracle Applications to collect the relevant data using the following steps.
To have the Interpoint for Oracle Applications collect forms data, you must manually add some information to the customization library of the Oracle Applications forms. This information includes user, form, and application names. The customization library consists of the following files:
You can only modify the CUSTOM.pld file. This file does not exist by default but can be extracted from the CUSTOM.pll file. For the changes to take global effect in the customization library after they are implemented in the CUSTOM.pld file, you need to regenerate the CUSTOM.pll and CUSTOM.plx files from the CUSTOM.pld file. Note that the file names may appear lowercase or uppercase (for example CUSTOM.pll). In the following task, all filenames are uppercase. If you copy and then paste this information, verify that the case matches the actual file names on your system.
To update the customization library on UNIX:
f60gen Module=CUSTOM.pll Module_Type=LIBRARY userid=user/password script=yes frmcmp_batch.BEGIN
IF (event_name='WHEN-NEW-FORM-INSTANCE') THEN
DECLARE
cursor_name INTEGER;
rows_processed INTEGER;
del CHAR(1) := SUBSTR(get_application_property(CURRENT_FORM),1 ,1);
BEGIN
IF (del != '/') THEN
del := '\';
END IF;
cursor_name := dbms_sql.open_cursor;
dbms_sql.parse(cursor_name,
'begin .VERITAS_APPS_LOG( ''F'' , :username , :application , :form , NULL) ; end ;'
,1);
dbms_sql.bind_variable(cursor_name,':username' , FND_PROFILE.VALUE( 'USERNAME'));
dbms_sql.bind_variable(cursor_name,':application' , SUBSTR( get_application_property(CURRENT_FORM),
instr(get_application_property(CURRENT_FORM),del , -1)+1, LENGTH(SUBSTR( get_application_property( CURRENT_FORM),
instr(get_application_property(CURRENT_FORM), del,-1)+1))-4)); dbms_sql.bind_variable(cursor_name,':form' ,
Name_In( 'system.current_form')); rows_processed := dbms_sql.execute(cursor_name); dbms_sql.close_cursor(cursor_name);
EXCEPTION
WHEN OTHERS THEN
BEGIN
dbms_sql.close_cursor(cursor_name);
EXCEPTION
WHEN OTHERS THEN
NULL;
END;
END;
END IF;
EXCEPTION
WHEN OTHERS THEN
NULL;
END;f60gen Module=CUSTOM.pld Module_Type=LIBRARY userid=user/password parse=yesfrmcmp_batch Module=CUSTOM Module_Type=LIBRARY userid=user/password parse=yesf60gen Module=CUSTOM.pll Module_Type=LIBRARY userid=user/password compile_all=yes f60gen command with frmcmp_batch./products/oracle//schema/pss_verify_oa_customer_pll.shAfter configuring the interpoint refer to Precise Installation guide for Manually updating Oracle Applications system profile (Oracle applications 11.5 or higher).