Page History

...

1. Mark the "Integrate with Insight" box.
2. Specify the port numbers used by the Oracle Applications listener forms.
3. Click the arrow (>>) button to add port numbers to the list.
4. Click Next.
   If you selected Forms Listener Servlet Mode, you can integrate Insight with the Oracle Apps instance. This enables you to correlate activities within your Oracle Applications domain with other activities in your application and measure Oracle Applications-related response time, and to do so, you need to configure the Oracle Applications forms server JVM to be used by the Oracle Applications Forms Server agent. This option is only relevant if the Oracle Applications forms server works in Forms Listener Servlet Mode and has the J2EE Collector installed.

...

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 update the customization library on Windows

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.
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. Run the %ORACLE_HOME%\bin\if60gen.exe tool (sometimes called ifbld60.exe).

   Info
   For Oracle Applications version R12 replace f60gen.exe command with frmcmp.exe.

5. In the welcome wizard, select Open an existing form, followed by OK.
6. Choose custom CUSTOM.pll and click Open.
7. Under PL/SQL Libraries > Custom > Program Units right-click on Package body and select the PL/SQL Editor.
8. Find the EVENT procedure, locate the first BEGIN after the commented sample code, and insert the following code, starting with BEGIN.
   Verify that the script was not inserted 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;
9. Click File > Save.
10. Run %ORACLE_HOME%\bin\ifcmp60.exe.
11. Fill in the following fields:
    1. File                        CUSTOM.PLL (that we changed before)
    2. Userid                   APPS
    3. Password              APPS password
    4. Database              database name
    5. Module Type         LIBRARY
    6. Module Access     FILE
12. Click OK.

...