This section includes the following topics:
Most of the screens in this installation require you to input details regarding your information systems. Before installing an Oracle Applications Tier instance, compile a list of all required user inputs based on the screen names below.
Before installing an Oracle Applications Tier instance, verify that you have performed the following tasks:
GRANT EXECUTE ON DBMS_PIPE TO <COLLECTOR_SCHEMA_USER>
This section describes the procedures that are needed to install an Oracle Applications Tier instance. You have the option of adding a new instance, as well as adding a new application. For information on editing or removing an existing instance, see Editing or removing tier instances or clusters.
On the AdminPoint Instances screen, you can add a new Tier instance.
Before adding a Tier instance, create a list of all required inputs based on the information below. |
To add a Tier instance
Click OK.
To install an instance in an application, you must have |
Click OK to view the next screen.
Always refresh AdminPoint after adding an instance. |
You can install both an Interpoint for Oracle Applications and the Insight Savvy for Oracle Applications to monitor the Forms Tier of Oracle Applications. To use an Interpoint for Oracle Applications, the database instance must first be monitored by an Precise for Oracle Collector agent.
To monitor the Forms Tier of Oracle Applications by the Insight Savvy for Oracle Applications, the following conditions must be met:
The first two textboxes are the database details (which should have already been installed as a Precise instance), with the third and fourth textboxes, the Oracle Applications forms details.
To define property settings for Oracle Applications
Select from the drop-down menu, the Oracle Applications database instance name.
The name of the Oracle instance or database used by Oracle Applications. If you also want to install an Interpoint for Oracle Applications, you need to install the Oracle Tier agents for the database SID previously installed. If this database is part of a Real Application Cluster (RAC), this is detected during the installation. In this case, you have to define the RAC later on. |
Select from the drop-down menu, the Oracle Applications forms server. Click Add, to select a server that is not listed on the drop-down menu.
This is the name or IP of the server where Oracle Applications forms are installed. This server is the Oracle Applications forms server, and it must be defined as a Precise Server. |
Select from the drop-down menu, the Oracle Applications instance.
The instance is usually auto-detected when the forms server is selected. In any event, you can select Other, from the drop-down menu. |
The Oracle Applications instance ID textbox is auto-filled with the instance ID, when the instance is selected. You can manually change the value as well.
Oracle Applications can have more than one forms server on one machine. The instance ID is a logical name that Insight uses to determine the specific forms server where you want to install this Oracle Applications Tier agent. If the Oracle Applications instance has been auto-detected this field is auto-filled. |
Click Next.
Forms Listener Mode is also known as Forms Socket Mode and is the default configured mode for Oracle Applications 11i. Check with your Oracle Applications administrator to determine which configured mode is running for the Oracle Applications Forms server in your application. |
If you selected Forms Listener Mode, you can integrate Insight with the Oracle Applications instance. This enables you to correlate activities within your Oracle Applications domain with other activities in your application and measure Oracle Applications-related network time, and to do so, you need to configure the TCP/IP ports to be used by the Oracle Applications Forms Server Listener. This option is only relevant if your Oracle Applications Forms Server is running on a UNIX server that has the Insight Savvy for Network installed. The relevant port number is defined by the FORMS_PORT application variable in the adfrmctl.sh script (located in the Oracle Applications installation folder). This script is used to start up or shut down the Forms Listener. The default values for the ports are auto-detected.
To integrate Insight with the Oracle Apps instance
To integrate Insight with the Oracle Apps instance
If there is a RAC, the RAC Cluster dialog box will appear, with the left table listing all monitored Oracle instances. The right table lists only instances that are part of the RAC (not including the instance defined in the Oracle Applications Tier - Instance Properties dialog box).
The right table must include all of the Oracle instances that are part of the RAC. Verify that this table is updated whenever you add or remove instances from your RAC configuration. |
To define the RAC cluster
The preview screen signifies that the AdminPoint Tier installer has gathered enough information to begin the installation phase.
The preview screen displays the following details before installation begins:
At this screen, you can still change any of the settings displayed. Click Back to change any of the displayed settings. Click Next to continue installation. Click Cancel to stop the installation process.
This screen appears when the AdminPoint Tier installer is actually performing installation. Installation may take several minutes.
The progress screen visually displays the progress of actual installation on selected servers.
This screen appears when the AdminPoint Tier Installer has completed installation of all Tier instances.
If there are no action items, click Finish (it will be the only option available) to complete the instance installation. If there are action items, click Next (it will be the only option available).
After a Tier instance is installed, you must perform post-installation tasks as may be required. Only after completing any post-installation tasks required can you start using the Tier instances you have just installed.
Perform any tasks displayed on this screen. Click Execute for Precise to perform the action items. Click Mark as done if you have performed the action items yourself.
When the Oracle Applications Tier Collectors have been installed, post-installation tasks are required. Depending on your application settings, you may need to stop all Insight Savvies that are currently running on the respective server and restart them. In addition, you need to grant permissions to schema user as described below and activate an Interpoint for Oracle Applications, as well as configure the Interpoint for Oracle Applications for the purpose of data collection.
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>
To activate an Interpoint for Oracle Applications
\products\oracle\SID\schema\install_oracle_apps.bat
./products/oracle/SID/schema/install)_oracle_apps.sh
<Precise_root>
is the name of the Precise root folder.verify_install_oracle_apps.bat
verify install oracle apps.sh
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:
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 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.
The file names may appear lowercase or uppercase (for example CUSTOM.pll). In the following task, all filenames are uppercase. If you copy-paste this information, verify that the case matches the actual file names on your system. |
To update the customization library on UNIX
CUSTOM.pll
and CUSTOM.plx
files, usually located in your Oracle Applications folder.CUSTOM.pll
and CUSTOM.plx
files and, if it exists, also the CUSTOM.pld
file.CUSTOM.pll
and CUSTOM.plx
files.CUSTOM.pll
file. This folder is pointed to by the application variable $FORMS60_PATH
.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
For Oracle Applications version R12, replace |
vi CUSTOM.pld
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;
CUSTOM.pll
file from the CUSTOM.pld
file, run the following command using the Oracle account of Oracle Applications (such as APPS):f60gen Module=CUSTOM.pld Module_Type=LIBRARY userid=user/password parse=yes
frmcmp_batch Module=CUSTOM Module_Type=LIBRARY userid=user/password parse=yes
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
For Oracle Applications version R12 replace |
<precise_root>/products/oracle/<sid>/schema/pss_verify_oa_customer_pll.sh
To update the customization library on Windows
CUSTOM.pll
and CUSTOM.plx
files, usually located in your Oracle Applications folder.CUSTOM.pll
and CUSTOM.plx
files.CUSTOM.pll
and CUSTOM.plx
files.Run the %ORACLE_HOME%\bin\if60gen.exe
tool (sometimes called ifbld60.exe
).
For Oracle Applications version R12 replace |
CUSTOM.pll
and click Open. 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;
%ORACLE_HOME%\bin\ifcmp60.exe
.CUSTOM.PLL
(that we changed before)To have an Interpoint for Oracle Applications identify interactive forms in Oracle Applications 11.5 or higher, you must manually update the system profile of Oracle Applications with site-specific initialization code. As a result, Oracle Applications forwards the required information - the user, form, and application name for interactive work and the concurrent program and application name for batch work - to an Interpoint for Oracle Applications.
Before updating Oracle Applications' system profile, you must verify that an Interpoint for Oracle Applications was installed successfully. Otherwise, updating the profile may halt Oracle Applications.
To avoid interfering with anyone's work before changing the system profile, you can alternatively change the profile for only one user to first test the outcome.
To verify that an Interpoint for Oracle Applications was installed successfully, run the following script:
\products\oracle\SID\schema\verify_install_oracle_apps.bat
./products/oracle/SID/schema/verify install oracle apps.sh
To update Oracle Application's system profile
Init%SQL%Custom
begin veritas_custom_profile; end;
If the form opens cleanly, you can start working with the Interpoint for Oracle Applications.
If an issue occurs, verify again that the Interpoint for Oracle Applications was installed successfully. If it was installed successfully, most likely the issue was caused by erroneous text in the system profile. If the issue persists, contact Precise Customer Support.
To update the system profile for one user only
Init%SQL%Custom
begin veritas_custom_profile; end;
If the form opens cleanly, you can update the Oracle Applications' system profile.
For more information, see Manually updating Oracle Applications system profile (Oracle applications 11.5 or higher).
If an issue occurs, verify again that the Interpoint for Oracle Applications was installed successfully. If it was installed successfully, most likely the issue was caused by erroneous text in the system profile. If the issue persists, contact Precise Customer Support.
When the Interpoint for Oracle Applications does not correlate some of its information with the Collector agent, the following scenario may be applicable:
The Interpoint for Oracle Applications collects some of its data from the Oracle Applications using the initialization of every form that is declared in the System Profile. The System Profile contains 4 profile levels, one for each level. Listed from the weakest to the strongest are: Site, Application, Responsibility, User. The Interpoints' code is on the weakest link here, meaning, Site level. When you customize one or more profiles at a stronger level, the code that resides at Site level is hidden.
In this query we expect to have Interpoints' code ( |
To find problematic profiles
select a.profile_option_value, DECODE(a.level_id, 10001, 'Site',
10002, 'Application', 10003, 'Responsibility', 10004, 'User', a.level_id) as "System Profile Level", a.level_value, to_char (a.last_update_date, 'YYYY-MON-DD') LAST_UPDATE_DATE
from FND_PROFILE_OPTION_VALUES a, FND_PROFILE_OPTIONS b, fnd_profile_options_tl c
profile_option_id = b.profile_option_id
andprofile_option_name = c.profile_option_name
anduser_profile_option_name = 'Initialization SQL Statement - Custom' order by a.LEVEL_ID;
profile_option_value
looks like: "begin veritas_custom_profile; <customer code goes here (or empty)> end;"
This query shows all relevant profiles affecting the code.
Typing errors in the system profile may prevent Oracle Applications forms from opening, including the system profile form. To validate that there is no other definition that overrides your profile definition and to correct any typing errors, you need to log in to the Oracle database externally using SQL*Plus.
To correct typing errors
Select * from FND_PROFILE_OPTION_VALUES where PROFILE_OPTION_VALUE like '%veritas%';
'%veritas%'
in the where clause with the string you are looking for. For example, to search for the profiles that were entered on July 13, 1975, execute the following command:Select * from FND_PROFILE_OPTION_VALUES where last_update_date=
to_date ('13-JUL-75', 'DD-MON-YY');
update FND_PROFILE_OPTION_VALUES set PROFILE_OPTION_VALUE =
'begin veritas_custom_profile; end;'
PROFILE_OPTION_VALUE like '%veritas%';
'%veritas%'
in the where clause with the string you are looking for. For example, to update all profiles that were entered on July 13, 1975, execute the following command:update FND_PROFILE_OPTION_VALUES set PROFILE_OPTION_VALUE='begin veritas_custom_profile;end;'
where last_update_date=to_date ('13-JUL-75', DD-MON-YY');
| | | | | | | |