Page History

...

Granting permissions to schema user

Connect to the Oracle instance on which the corresponding collector is installed as DBA user and run query:

grant execute on DBMS_PIPE to <collector_schema_user>

Activating the Interpoint for Oracle Applications

To activate an Interpoint for Oracle Applications

1. Log in to the server and run the following script to install the Interpoint:
   Windows
        \products\oracle\SID\schema\install_oracle_apps.bat
   UNIX
        ./products/oracle/SID/schema/install_oracle_apps.sh
   where <precise_root> is the name of the Precise root folder.
2. To verify that the installation was successful, run the following script:
   Windows
        verify_install_oracle_apps.bat
   UNIX
        verify  verify install oracle apps.sh
3. Configure the Oracle Applications application.
   For more information on how to configure the Oracle Applications application, see Configuring an Interpoint for Oracle Applications for data collection on page 29.
4. Restart the Precise for Oracle Collector agent for this instance.

Anchor
ConfiguringanInterpointforOracleapplicationsfordatacollection ConfiguringanInterpointforOracleapplicationsfordatacollection

Configuring an Interpoint for Oracle applications for data collection

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 involves these tasks:

• Manually updating the customization library
• Manually updating Oracle Applications’ system profile (Oracle applications 11.5 or higher)

Anchor
Manuallyupdatingthecustomizationlibrary Manuallyupdatingthecustomizationlibrary

Manually updating the customization library

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:

• CUSTOM.pld
• CUSTOM.pll
• CUSTOM.plx

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 a 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.

To update the customization library on UNIX

1. Find the CUSTOM.pll and CUSTOM.plx files, usually located in your Oracle Applications folder.
2. Back up the CUSTOM.pll and CUSTOM.plx files and, if it exists, also the CUSTOM.pld file.
3. Verify that no Oracle Applications user is currently logged on to the database or any other database using the CUSTOM.pll and CUSTOM.plx files.
4. Change to the folder that contains the CUSTOM.pll file. This folder is pointed to by the application variable $FORMS60_PATH.

5. To extract the CUSTOM.pld file, run the following command using the Oracle account of Oracle Applications (such as APPS):
        f60gen Module=CUSTOM.pll Module_Type=LIBRARY userid=user/password script=yes

   Info
   For Oracle Applications version R12, replace f60gen command with frmcmp_batch.

6. Run the following command to edit the file:
        vi CUSTOM.pld
7. Find the EVENT procedure, locate the first BEGIN after the commented sample code, and insert the following code, starting with BEGIN.
   Do not insert the script into commented sample code. You can easily mistake sample code for real code.
   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;
8. To regenerate the CUSTOM.pll file from the CUSTOM.PLD file, run the following command using the Oracle account of Oracle Applications (such as APPS):
   1. For Oracle Application version under R12 (exclusive):
      f60gen Module=CUSTOM.pld Module_Type=LIBRARY userid=user/password parse=yes
   2. For Oracle Applications version R12:
      frmcmp_batch Module=CUSTOM Module_Type=LIBRARY userid=user/password parse=yes

9. To regenerate the CUSTOM.plx file from the CUSTOM.pll file, run the following command using the Oracle account of Oracle Applications (such as APPS):
        f60gen Module=CUSTOM.pll Module_Type=LIBRARY userid=user/password compile_all=yes

   Info
   For Oracle Applications version R12, replace f60gen command with frmcmp_batch.

10. To verify the CUSTOM library change, run the following script:
         <precise_root>/products/oracle/<sid>/schema/pss_verify_oa_customer_pll.sh

To