Page History

...

The Operating System user that runs the Web Server or Web Application should have full control privileges for the <precise_root> folder (for example: user ASPNET for IIS5 or user NETWORK SERVICE for IIS6).

The following table lists the permissions that are required for general collection on UNIX.

...

1. Go to Start > Control Panel > Programs > Programs and Features.
2. On the left Side Bar, select Turn Windows features on or off.
3. Wait for the Windows Features dialog box to open and fill, and then expand Internet Information Services.
4. SelectSelect IIS 6 Metabase Compatibility service under IIS 6 Management Compatibility.
5. Click OK.

...

To define a Microsoft IIS Tier instance

1. Select one of the available Microsoft IIS versions from the

   drop-down

   menu

   :

   .

   Info
   If the IIS version or Web site name (next step) is not auto-detected, enter it manually.

2. Select the Detected Web site name from the menu.
3. Select the Application type (Web or Siebel) from the menu.
4. Select the Application version from the menu. This textbox is unavailable  when Web is chosen.
5. Enter the Instance name. Use a free-text identifier to distinguish between multiple monitored Web sites.

6. Optional. Check Allow internet information service restart. If you leave this box empty, post-installation actions are required. 

7. Click Next.

...

1. Select the Web site from the menu.
   The fields for a WebLogic, WebSphere, and Apache Web server are auto-detected and populated when you select one of the auto-discovered Web sites in the Detected Web sites list.
   The following information appears:

   • Apache. The full path of the configuration file.

     Info

     The auto-detection mechanism is limited in different ways, depending on whether Apache is on a Windows or UNIX server. On Windows, the detection is based on the services list. Therefore, Apache will not be detected if it is not defined as a service. On UNIX, the detection is based on running processes. The Web server version is not detected if the Precise user does not have execute permission on the Apache executable (HTTPD).

2. Enter the Web site configuration file. To browse for the appropriate folder and file, click the browse (...) button.
   This input is required for Apache and Sun iPlanet. For all other web servers, it is recommended to manually enter the value to optimize the installation process. If however, the value is unavailable, the field can be left blank.
   The following values are auto-detected:
   • Apache. The full path and name of the main configuration file. For example:
     C:\WebServers\Apache\Apache13\conf\httpd.conf
     For Apache that serves Oracle applications:
     /rac_shared/env/appl/apps/tech_st/10.1.3/Apache/Apache/conf/httpd.conf
     or
     /rac_shared/env/inst/apps/VIS_pool-linux-rac-1/ora/10.1.3/Apache/Apache/conf/htt pd.conf)
   • Sun One or Sun iPlanet. The full path to the server.xml file of a specific server on a specific node in a specific cell. For example: c:\WebServers\Sun\WebServer6.1\https-admserv\config\server.xml.

   • Tomcat. The full path to the server.xml file. For example: c:\WebServers\Tomcat\conf\server.xml.

     Info
     If the auto-detected value is incorrect, you can change it manually.

3. Select the Web server version from the menu.
   The Tier installer normally auto-detects and displays the Web server version in this field. If the Web server version is not auto-detected, or incorrect, enter the inputs manually.
   Select one of the following Web server version options from the list:
   
   • Apache: 1.3.x, 2.0.x, or 2.2.x
   • Sun One: 6.1
   • Apache Tomcat 5.x, 6.x
   • Sun iPlanet 6.0
4. Select the appropriate Web Server bits from the drop-down menu.
   This input is required only when using Apache or Sun iPlanet. For other Web servers, this input field is grayed-out. Normally the Tier installer will auto-detect and display the Web server bits in this field.
   If the Web server bit number is not auto-detected, or incorrect, enter the bit number manually. Select one of the following Web server bit numbers from the list:
   • 32
   • 64
5. Select the application type from the drop-down menu.
   This is the application served by this Web server site. This information enables better configuration of the Web Tier Collectors. The following options are available:
   • Web (default)
   • Siebel
   • PeopleSoft
   • Oracle Applications
6. Select the application version from the drop-down menu.
   This is the version of the application server chosen in the previous field. Select an application server version:
   • Siebel 7.7-8.1.1x.x
   • PeopleSoft 8.44-8.50x.x
7. Enter the instance name. Use a free-text identifier to distinguish between multiple, monitored Web sites.
8. Click Next.

...

To define one of the above instances

1. Select the Web site from the drop-down menu.
   The fields for a WebLogic and WebSphere will be auto-detected and populated when you select one of the auto-discovered Web sites in the Detected Web sites list.
   The following information is shown:
   • WebLogic. The server name (if it exists) or full path of the configuration file.

   • WebSphere. The server name attribute from the server.xml file, or the full path of the configuration file.

     Info
     However, instances that are installed as Windows services will are not be detected whether even when they are running or not. On UNIX, in most configurations of HP, Linux, Sun, and AIX prior to version 5.3 patch 5, the Web servers may be partially detected or not detected at all.

2. Enter the Web site configuration file. To browse for the appropriate folder and file, click the browse (...) button.
   For non-cluster installations, it is recommended to manually enter the value to optimize the installation process. If however, the value is unavailable, the field can be left blank. For cluster installations, this is ignored.
   The following values are auto-detected:
   • WebLogic. The full path and name of the config.xml file (for example:
     c:\WebServers\bea\weblogic81\samples\domains\medrec\config.xml).

   • WebSphere. The full path to the server.xml file of a specific server on a specific node in a specific cell (for example: c:\WebServers\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\I4W-VM-SRV3Node01Cell\nodes\I4W-VM-SRV3Node01\servers\server1\server.xml).

     Info
     If the auto-detected value is incorrect, you can change it manually.

3. Select the Web server version from the drop-down menu.
   Normally the Tier installer will auto-detect and display the Web server version in this field. If the Web server version is not auto-detected, or incorrect, enter the inputs manually. Select one of the following Web server version options from the list:
   • WebLogic. 8.x, 9.x, 10.x
   • WebSphere. 6.0, 6.1-6.x, 7.0
4. Select the application type from the drop-down menu.
   This is the application served by this Web server site. This information enables better configuration of the Web Tier Collectors. The following options are available:
   • Web (default)
   • PeopleSoft
5. Enter the instance name. Use a free-text identifier to distinguish between multiple, monitored Web sites.
6. Click Next.

Anchor
DefininganOracle10gApplicationServerinstance DefininganOracle10gApplicationServerinstance

Defining an Oracle 10g Application Server instance

To define an Oracle 10g Application server instance

1. Select the application server from the drop-down menu.
   The textboxes for the Oracle 10g Application Server will be autoauto-detected detect and populated populate when you select one of the auto-discovered Web sites in the Detected Web sites list. You can manually change the auto-detected values. The auto-detection mechanism has the following limitations:
   • The Web server version is not returned if you don’t have are lacking read permissions on the inventory/ContentsXML/configtools.xml file in the Application server folder.
   • On Solaris and AIX prior to version 5.3 patch 5, the Oracle 10g Application Server may be partially or not detected.
   • Instances that are currently not running are not detected. On Windows, instances that are installed as services are not detected , whether even if they are running or not.

2. Select the Oracle Application server configuration file. To browse for the appropriate folder and file, click the browse (...) button.

   Info
   The configuration file should be named opmn.xml. Example for a configuration file path: /i4t/i3/websun1_webservers/OracleAS/10.1.3/opmn/opmn.xml.

   Info
   Normally the Tier installer will auto-detect detects and display displays the Oracle Application server configuration file and the Apache Web server configuration file (step 3) in their fields. If the server configuration files are not auto-detected, or incorrect, enter the inputs manually.

3. If there is an Integrated Apache web server running before the Oracle AS, select its configuration file. To browse for the appropriate folder and file, click the browse (...) button.
   For example, the configuration file of apache in an Oracle Applications 12 installation:
   /rac_shared/env/appl/apps/tech_st/10.1.3/Apache/Apache/conf/httpd.conf
   or
   /rac_shared/env/inst/apps/VIS_pool-linux-rac-1/ora/10.1.3/Apache/Apache/conf/httpd.conf

4. Select the Oracle Application server version, from the drop-down menu.

   Info
   Normally, the Oracle Application server version will be auto-detected. If it’s it is not auto-detected, manually enter the server version.

5. Select the application type from the drop-down menu.
6. Select the application version from the drop-down menuthe menu. The following options are available:
   • Web (default)
   • PeopleSoft
   • Oracle Applications
7. Enter the instance name. Use a free-text identifier to distinguish between multiple, monitored web sites.
8. Click Next.

...

The detected Web domains can be added manually. If you need to

To manually obtain the Listener agent ports for a server, do the following:

1. Run the netstat command to see a list of all open connections on the server machine.
2. On a UNIX server, use the lsof utility located in the

...

1. <precise_

...

1. root>/products/insight/host/bin folder on the monitored server.

To use the utility to obtain a list of all TCP/IP ports used by a service, run the following command:

lsof -P|grep LISTEN|grep listener process name

To access a list of lsof utility options, run the following command:

lsof -h

To enter a Web Tier domain

1. Mark one of the listed domains.
2. Mark the SSL box if the domain is secured (HTTPS).
   If the desired domain is not on the list, or requires editing, follow steps a-f:f
   1. Click Add or Edit.

   2. Choose either “All IPs” or “Specific IP” All IPs or Specific IP.

      Info
      If every IP address that the server listens on , is a real IP address, then they should all be specified. If the different names are actually virtual hosts, then only one should be specified. If the only difference is in the ports (same IP address with several ports), then only one of them should be specified.

   3. If a Specific IP is selected, enter the Specific specific IP name.
   4. Enter the port number for this domain.
   5. Enter the Host Header name for this domain (If , if it exists).
   6. Mark the Check SSL box if  if the domain is secured (HTTPS).
   7. Click Add.Click , and then click Next.

About the AdminPoint Tier installation preview screen

...

At this screen, you can still change any of the settings displayed. Click Back to change any of the displayed settings. Click , click Next to continue installation. Click , or 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.

...

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. See Post-installation action items for more information.

Anchor
InstallingaWebcluster InstallingaWebcluster

Installing a Web cluster

...

To add a cluster

1. From StartPoint, click the AdminPoint tab.
2. Click the Setup tab.
3. From the drop-down menu, select Instances & Clusters.
4. Click the All clusters tree item.
5. At the bottom of the Display Instances & and Clusters screen, click Add Cluster. The Add New Cluster dialog box appears.
6. Select the Web technology from the list.
7. Select the application from the list.
   If the desired application is not on the list, use the following steps:
   1. Click Add.
   2. In the In Application Name field, type in the new application name.
   3. On the In Application System field, select the system application from the list.

   4. Click OK.

      Info
      To install a cluster in an application, you must have explicit ADMINISTRATE.INSTALL permissions for the application in which you want to install the cluster. If you only have permission for a specific technology, you will only be able to install in an application that is either empty, or is comprised of only the same technology.

8. Select a Tier from the list.

9. Click OK to view the next screen.

   Info
   Always refresh AdminPoint after adding an instance.

...

To define the Web cluster property settings, you must provide the cluster name, select which Web server type you want to monitor, as well as its location.

To define the Web cluster

1. Enter a cluster name. Use a free-text identifier to provide a unique name to be shared by all instances in the cluster. In addition, a unique identifier will automatically be added to each instance.

   Info
   The unique name will be is the application server name.

2. Select one of the following Web server types , from the drop-down menu:
   • WebLogic
   • WebSphere

3. Select the server where any of the web instances running the cluster application is located, from the drop-down menu. Click Add to enter the name of a server not on the list. For more information, see see see Adding a new server.

   Info
   This is the name or IP address of the server where you want to install the Web Tier Collector with a specific operating system. The server name or IP address appears in the list only if you previously defined it as a Precise server.

   
   The Web site field will be auto-detected detects and populatedpopulates. Once you have selected select one of the auto-discovered Web sites in the Detected Web sites list, the required fields will be are automatically filled. If the fields are incorrect, they can be modified manually.

   Info

   The auto-detection mechanism is limited in different ways, depending on whether WebLogic or WebSphere is on a Windows or UNIX server. On Windows, the detection is based on running processes. Therefore, the Web server will not be detected if it is not running. However, Web servers that are installed as Windows services will not be detected whether they are running or not. On UNIX, in most configurations of HP, Linux, Sun, and AIX prior to version 5.3 patch 5, the Web servers may be partially detected or not detected at all.

4. Select the Web server version from the drop-down menu.
   Normally the installer will auto-detect and display the Web server version in this field. If the Web server version is not auto-detected, or incorrect, enter the inputs manually. Select one of the following Web server version options from the list:

   • WebLogic. 8.x, 9.x, 10.x

   • WebSphere. 6.0, 6.1-6.x, 7.0

5. Select the application type from the drop-down menu.
   This is the application served by this Web server site. This information enables better configuration of the Web Tier Collectors. The following options are available:

   • Web (default)

   • PeopleSoft

6. If PeopleSoft was is selected in the previous field, enter the relevant Application version between version 8.44 -8.498.5x.

7. Click Next.

About the AdminPoint cluster installation preview screen

...

At this screen, you can still change any of the settings displayed. Click Back to change any of the displayed settings. Click , click Next to continue installation. Click , or click Cancel to stop the installation process.

...

Perform all tasks displayed on this screen. Once all the post-installation action items have been applied on the application and the application has been deployed to the cluster Web servers, these servers will automatically be installed in the Precise application. Click Execute for Precise to perform the action items. Click Mark as done if you have performed the action items yourself. See Post-installation action items for more information.

About the AdminPoint cluster installation complete screen

...

• (Best practice) To add this script to you your application redeployment script, so it will be done automatically.

• Change the central application file (if the application is clustered and there is a central location as opposed to a local location). This way the Precise filters will stay in the application in each redeployment.

  Info
  If you do so, you will need to redeploy the application instead of performing a mere JVM restart.

  Info
  If you are installing Precise for Web on a cluster (WebLogic or WebSphere) the option to change the central application file is the only option.

• Examples of application locations:
  
  • The WebLogic 10.3 console shows the .EAR file location under “deployments”. Then click on your application name to see the path.
  • The WebSphere 6.1 console displays the names of .EAR files, but not their location. The typical location of and .EAR file is:
    <install-dir>\profiles\[profile-name]\config\cells\[cell-name]\applications\PlantsByWebSphere.ear\PlantsByWebSphere.ear
  • For Tomcat 5.x & 6.x: <tomcat-dir>\webapps\<app-name>\web-inf\web.xml
  • For Sun One 6.x: <sunone-dir>\WebServer6.1\<domain-name>\webappsWeb.xml appears inside each application.

...

When installing a Web application with multiple instances, running the psww_web_desc_modify command will create multiple EAR files, with each EAR file containing a different instanceId and i3root value, corresponding to the instances in the Web application.

To avoid creating multiple EAR files

1. Run the web desc modifier without the -instanceId and -i3root parameters.
2. Add the following parameters to the JVM command line:
   • -DPssInstanceID=<instance<instance_ID>ID>
   • -DPssI3Root=<precise<precise_root>root>

Adding Precise for Web filter(s) to the Web server classpath

...

Enabling statistics collection on WebSphere 6.1 - 6.x and 7.x.x

To enable statistics collection on WebSphere

1. Open WebSphere admin console (URL: ibm/console/login.do).
2. In the Integrated Solutions Console, click the Monitoring and Tuning tab.
3. From the drop-down menu, click on Performance Monitoring Infrastructure (PMI).
4. On the right pane, select the server upon which you want to enable statistics (for example, server1.)
5. In the next screen, click the Runtime tab.
6. On the Runtime tab, select either:
   • Basic
   • Extended
   • All

   • Custom

     Info
     If you select Custom, verify that the CommittedCount counter under Transaction Manager is enabled.

...

To verify that browser-side and server-side data is properly correlated, specify the name of the session cookie that is used by the application in the settings.xml file. Session cookie names can be JSESSIONID, _sn, SID, etc. Contact your application administrator to find the name of the cookie.

To add the session cookie name

1. In the “Registry Path” field in the Registry Editor (AdminPoint > Settings > Registry Editor), enter the following path and click Go: registry/instances/www/<server_name>/<instance_name>/settings.
2. In the Xml Editor tab, search for the <filter-session-cookie> tag.
3. Add the applicable cookie name between the tag, for example:
   <filter-session-cookie>_sn</filter-session-cookie>

4. Click Save.

   Info
   The cookie session name for J2EE (JSESSIONID) is the default value for the <filter-session-cookie> tag.

Adding post-parameters collection for

...

IIS

To add post-parameters collection for IIS, see the following sections:

...

To add a wildcard application mapping to a Web server or Web site

1. In IIS Manager, expand the local computer, expand the Web Sites folder, expand the "Default-Web-Site", right-click the virtual directory that you want to collect post parameters on, and then click Properties.
2. Click Add Wildcard Script Map.
3. In the Executable box, enter the full path or browse to the native handler (.dll or .exe file) that processes the request: <precise<precise_root>root>\products\www\instances\<instance<instance_id>id>\bin\IISFilter.dll
4. In the Name box, enter a name for the handler mapping.
5. Click OK.
6. Click Yes, to add the extension with an Allowed entry to the ISAPI and CGI Restrictions list. Repeat this for each virtual directory you want to collect post parameters in.

Add the Precise post-parameters collection extension to the trusted list

To add the Precise post-parameters collection extension to the trusted list

1. In IIS Manager, expand the local computer; expand the Web Services Extensions, Click Add a new Web service extension.
2. Put "Precise post parameters" as extension name.
3. Click Add. In the "Path to file" field type the path to the DLL:
   <precise<precise_root>root>\products\www\instances\<instance<instance_id>id>\bin\IISFilter.dll
4. Click OK.
5. Mark the “Set extension status to Allowed” check box.
6. Click OK.

Updating the collect-post-parameters tag

To update the collect-post-parameters tag

1. In the “Registry Path” field in the Registry Editor (AdminPoint > Settings > Registry Editor), enter the following path and click Go: registry/instances/www/<server_name>/<instance_name>/settings.
2. In the Xml Editor tab, change the value of the <collect-post-parameters> tag to “true”.
3. Click Save.

Adding post-parameters collection for IIS

To add post-parameters collection for IIS, see the following sections:

...

To add wildcard application mapping to a Web server or Web site, go to the Precise<precise_root> directory and run the following script:
products\www\install\psww_insert_isapi_handlers.bat <precise_root>
<instance_id> <site_name> <precise_root> <instance_id> <site_name> add-handler PreciseWebHandler <filter_path>

...

Anchor
Updatingthecollectpostparameterstag Updatingthecollectpostparameterstag

Updating the collect-post-parameters tag

To update the collect-post-parameters tag

1. In the “Registry Path” field in the Registry Editor (AdminPoint > Settings > Registry Editor), enter the following path and click Go:
   registry/instances/www/<server_name>/<instance_name>/settings/server-side.
2. In the Xml Editor tab, change the value of the <collect-post-parameters> tag to “true”.
3. Click Save.

...

Anchor
Updatingthecollectpostparameterstag Updatingthecollectpostparameterstag

Updating the collect-post-parameters tag

To update the collect-post-parameters tag

1. In the "Registry Path" field in the Registry Editor (AdminPoint > Settings > Registry Editor), enter the following path and click Go:
   registry/instances/www/<server_name>/<instance_name>/settings/server-side.
2. In the Xml Editor tab, change the value of the <collect-post-parameters> tag to "true."
3. Click Save.

Removing post-parameters collection for IIS

To remove wildcard application mapping from a Web server or Web site, go

• Go to the

...

• <precise_

...

• root> directory and run the following script:

products\www\install\psww_insert_isapi_handlers.bat

...

<precise_root> <instance_id> <site_name> remove-handler PreciseWebHandler

...

<filter_

...

path>

where:

filter_path    The path to the instance bin folder concatenated with "IISFilter", without the _32.dll or _64.dll extension.

For example: c:\precise\products\www\instances\2643\bin\IISFilter

...