This section includes the following topics:
If you intend to use an SAP scenario in which you monitor access via Web, then you need to perform the installation of the Precise for Web Tier too! However for some of the most common SAP scenarios, including SAP GUI Windows client access to SAP ERP and Precise for BW ETL process chain scenarios, the installation of the Precise for Web Tier is not needed. |
Before beginning the installation process, review the instances you want to install and choose the most applicable type of installation per your needs.
Web instances can be installed in either of the following ways:
Each instance in the cluster is given a name that includes both the user defined cluster name and an automatically generated unique identifier.
It is recommended to install a cluster when the following conditions apply:
After completing the pre-installation tasks, see Installing a Web cluster.
When using Apache 2.0 and higher, or IIS, as a proxy to J2EE application servers, it is recommended to install client-side and server-side on the proxy tier and not on the J2EE application server. If you need to install Precise for Web on the J2EE application server, only install the server-side and not client-side collection on the J2EE tier.
Figure 1 Web client-side and server-side monitoring when using Apache 2.0 and higher, or IIS, as a proxy
When using Apache 1.3 or iPlanet as a proxy to J2EE application servers, it is recommended to install both server-side and client-side collection on J2EE application servers.
Figure 2 Web client-side and server-side monitoring when using Apache 1.3 or iPlanet as a proxy
Most of the screens for this installation require you to input details regarding your information systems. Before performing this installation, compile a list of all required user inputs based on the procedures below.
Before you install a Web Tier, you need to grant special file and folder permissions (including all subdirectories) to the UNIX or Windows user that you intend to use during the installation.
The permissions in the general collection table on UNIX are not needed for the ongoing operation, only for installation. Auto-detected values will be shown. If this user does not have these permissions during installation you do not see these auto-detected values and you will have to supply them manually.
The Operating System user that runs the Web Server or Web Application should have full control privileges for the <precise_root
> folder.
The following table lists the permissions that are required for general collection on UNIX.
Table 1 Permissions for the general collection on UNIX
Web Server | File or Folder | Required Permission |
---|---|---|
iPlanet |
site name/config | RX (X for all subdirectories) |
iPlanet |
site name/config/server.xml | R |
Apache | configuration directories (typically: apache root/config ) and subdirectories | RX (X for all subdirectories) |
Apache | configuration files (typically: httpd.conf ) | RX |
WebLogic | Server installation folder (
WL root
) | RX (X for all subdirectories) |
WebLogic |
WL root/site name | RX (X for all subdirectories) |
WebLogic |
WL root/site name/config.xml | R |
WebSphere |
WL root/properties/version/platform.websphere and
WS root/properties/version/WAS.product | R |
WebSphere | Node folder and all subdirectories such as, .../cells/cell1/nodes/node1 | RX |
WebSphere | Node serverindex.xml and server.xml files such as .../cells/cell1/nodes/node1/serverindex.xml and .../cells/cell1/nodes/node1/servers/server1/server.xml | R |
Oracle Applications Server |
OC root/inventory/ContentsXML/configtools.xml | R |
Tomcat | Configuration folder (typically:
tomcat root/config ) and all subdirectories | RX |
Tomcat | server.xml file (typically:
tomcat root/conf ) | R |
Sun ONE | Configuration folder (typically:
sunone root/domains/domain1/config ) and all its subdirectories | RX |
Sun ONE | domain.xml file (typically:
sunone root/domains/domain1/config ) | R |
Oracle Applications Server OPMN | Configuration folder (typically:
oracle as root/opmn/conf ) and all subdirectories | RX |
Oracle Applications Server Apache | Configuration folder (typically:
oracle as root/Apache/conf ) and all subdirectories | RX |
Oracle Applications Server OPMN | Configuration files (typically:
oracle as root/opmn/conf/opmn.xml ) and all subdirectories | R |
Oracle Applications Server Apache | Configuration files (typically: | R |
The following table lists the permissions that are required for the general collection on Windows.
Table 2 Permissions for the general collection on Windows
Web Server | File or Folder | Required Permissions |
---|---|---|
iPlanet |
site name/config | Read + List Folder Contents |
iPlanet |
site name/config/server.xml | Read |
Apache | Configuration directories (typically:
apache root\conf ) | List Folder Contents |
Apache | Configuration files (typically: httpd.conf ) | Read |
WebLogic | Server installation folder | List Folder Contents |
WebLogic |
WL root\site name
| List Folder Contents |
WebLogic |
WL root\site name\config.xml | Read |
WebSphere | Node folder and all subdirectories such as, ...\cells\cell1\nodes\node1 | List Folder Contents |
WebSphere | Node serverindex.xml and server.xml files such as ...\cells\cell1\nodes\node1\serverindex.xml and ...\cells\cell1\nodes\node1\servers\server1\server.xml | Read |
Tomcat | Configuration folder (typically:
tomcat root\conf ) and all subdirectories | List Folder Contents |
Tomcat | server.xml file (typically:
tomcat root\conf ) | Read |
Sun ONE | Configuration folder (typically:
sunone root\domains \domain1\config) and all subdirectories | List Folder Contents |
Sun ONE | domain.xml file (typically:
sunone root\domains\domain1\config ) and all subdirectories | Read |
Oracle Applications Server OPMN | Configuration folder (typically:
oracle as root\opmn\conf ) and all subdirectories | List Folder Contents |
Oracle Applications Server Apache | Configuration folder (typically:
oracle as root\Apache\conf ) and all subdirectories | List Folder Contents |
Oracle Applications Server OPMN | Configuration files (typically:
oracle as root\opmn\conf\opmn.xml ) and all subdirectories | Read |
Oracle Applications Server Apache | Configuration files (typically:
oracle as root\Apache\conf\*.conf ) and all subdirectories | Read |
To install a Web instance on IIS7.x, the IIS6 Metabase Compatibility service and ISAPI filters must be installed.
To enable IIS6 Metabase Compatibility and ISAPI filters on Windows 2008
To enable IIS6 Metabase Compatibility on Windows 7
At the end of the installation, you must provide the path to the application file you wish to monitor (.EAR
, .WAR
, or web.xml
file of the application).
For more information, consult with your Web Administrator.
This section describes the procedures needed to install a Web Tier instance. Before installing the instance verify that the type of installation best suits your needs. 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 screen information below. |
To add a Tier instance
Click OK.
To install an instance in an application, you must have ADMINISTRATE.INSTALL permission for the application in which you want to install the instance. 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. |
Click OK to view the next screen.
Always refresh AdminPoint after adding an instance. |
To define the Web Tier property settings, you must first select which Web server type you want to monitor, as well as its location.
To select the Web server type and its location
Other J2EE
The options Apache, SAP WAS J2EE, Sun iPlanet, Oracle Application Server, Sun ONE, and other J2EE Web servers are supported, but currently without Web server statistics. Client-side instrumentation is not supported by Sun iPlanet and Apache 1.3. |
From the menu, select the server where the Web server instance is located. Click Add to enter the name of a server not on the list. For more information, see see Adding a new server.
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. If using Microsoft IIS, you cannot install on a UNIX platform. |
The next installation screen is dependent upon which Web server type is selected. Click the relevant link below to view the installation procedure for the selected Web server:
To define a Microsoft IIS Tier instance
Select one of the available Microsoft IIS versions from the menu.
If the IIS version or Web site name (next step) is not auto-detected, enter it manually. |
Optional. Check Allow internet information service restart. If you leave this box empty, post-installation actions are required.
A Web site configuration file is mandatory for Sun iPlanet and Apache servers, but is optional for other servers. During installation, the Web site configuration file is editable. If it is not inserted, you must enter Web server listening ports manually on the next screen (Domain Information). |
To define one of the above instances
Apache. The full path of the configuration file.
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). |
C:\WebServers\Apache\Apache13\conf\httpd.conf
/rac_shared/env/appl/apps/tech_st/10.1.3/Apache/Apache/conf/httpd.conf
/rac_shared/env/inst/apps/VIS_pool-linux-rac-1/ora/10.1.3/Apache/Apache/conf/htt pd.conf
)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
.
If the auto-detected value is incorrect, you can change it manually. |
A Web site configuration file is optional for WebSphere and WebLogic. During installation, the Web site configuration file is editable. If it’s not inserted, you will have to enter Web server listening ports manually on the next screen (Domain Information). |
To define one of the above instances
WebSphere. The server name attribute from the server.xml file, or the full path of the configuration file.
However, instances that are installed as Windows services are not detected even when they are running. 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. |
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
).
If the auto-detected value is incorrect, you can change it manually. |
To define an Oracle 10g Application server instance
Select the Oracle Application server configuration file. To browse for the appropriate folder and file, click the browse (...) button.
The configuration file should be named opmn.xml. Example for a configuration file path:
|
Normally the Tier installer auto-detects and 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. |
/rac_shared/env/appl/apps/tech_st/10.1.3/Apache/Apache/conf/httpd.conf
/rac_shared/env/inst/apps/VIS_pool-linux-rac-1/ora/10.1.3/Apache/Apache/conf/httpd.conf
Select the Oracle Application server version, from the menu.
Normally, the Oracle Application server version will be auto-detected. If it is not auto-detected, manually enter the server version. |
Precise for Web monitors Web instance performance and availability. The domains screen displays a list of all detected Web domains. If the domains are not detected automatically, manually enter them.
Only in Apache, the SSL ports are detected as regular ports, so you should pay attention and set the SSL check box accordingly. |
The detected Web domains can be added manually.
To manually obtain the Listener agent ports for a 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
The lsof utility is only available if the Insight Savvy for Network is installed. If you want to run this utility before completing the Savvy installation, log in as the root user and locate the |
If there is more than one ip:port combination shown, only real IP addresses should be fully specified. |
To enter a Web Tier domain
Choose All IPs or Specific IP.
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. |
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, 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 displays the progress of actual installation on selected servers.
The Add Servers screen enables you to add servers to a cluster. This can be done by moving servers to the table on the right. The new cluster server may get an indication that action items are pending and after the executing them, a list of cluster instances related to this cluster will be shown instead. Click Next to continue installation.
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. See Post-installation action items for more information.
This section describes the procedures that are needed to install a Web cluster. A Web cluster is defined as a set of WebLogic or WebSphere JVMs that share the same configuration and are started from a shared location. Installing a Web cluster has two parts. The first one, described below, consists of creating a repository for the cluster configuration based on the definition of any of the cluster's JVM and performing the action items on the shared location. Once the action items are performed and JVMs are restarted, the second part of the installation takes place and each JVM instance is installed automatically and Precise starts to monitor it.
For information on editing or removing an existing instance, see Editing or removing tier instances or clusters.
Before adding a cluster, create a list of all required inputs based on the screen information below. |
Installing a cluster is only supported for WebSphere and WebLogic web servers. |
To add a cluster
Click OK.
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. |
Click OK to view the next screen.
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
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.
The unique name is the application server name. |
Select the server where any of the web instances running the cluster application is located, from the menu. Click Add to enter the name of a server not on the list. For more information, see Adding a new server.
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 auto-detects and populates. Once you select one of the auto-discovered Web sites in the Detected Web sites list, the required fields are automatically filled. If the fields are incorrect, they can be modified manually.
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. |
Select the Web server version from the 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
WebSphere
Select the application type from the 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
If PeopleSoft is selected, enter the relevant Application version between version.
Click Next.
The preview screen signifies that the AdminPoint cluster 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, or click Cancel to stop the installation process.
At this point, the cluster definitions are saved and an agent is only installed on the specified server. For servers that will be added after this point, the agent will be installed only once the instance is started. |
This screen appears when the AdminPoint cluster installer is actually performing installation. Installation may take several minutes.
The progress screen visually displays the progress of actual installation on selected servers.
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.
This screen appears when the AdminPoint cluster installer has completed installation of the cluster. Click Finish (it will be the only option available) to complete the cluster installation.
When the Web Tier Collectors have been installed, post-installation action items may be required. There might be additional action items not listed below, that are required in each installation. Upon finishing your installation, verify that all action items have been completed by checking the list generated on the Action Items screen.
To monitor the application(s), you need to register the Precise for Web agent(s) as Web application filters. This section describes how to add Precise for Web technology to the Web application(s) Web descriptor files.
If you have installed a cluster, this is the only documented post-installation action item. Verify that no additional action items are needed by checking the list Action Items screen. |
As an input to that script you need to provide the location of the .EAR
, .WAR
, or web.xml
file(s) of the application(s).
Note that if you change a locally deployed application, then any application redeployment may override this action item, so you will need to do it again. If you do not want to do this after every redeployment, you have 2 options:
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.
If you do so, you will need to redeploy the application instead of performing a mere JVM restart. |
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. |
.EAR
file location under “deployments”. Then click on your application name to see the path..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
<tomcat-dir>\webapps\<app-name>\web-inf\web.xml
<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
To monitor the application, the Precise for Web agent(s) jar(s) must be loaded. Consult with your Web Administrator on where the right location is to do so. Examples:
Tomcat 5.x & 6.x. <tomcat-dir> \bin\setclasspath.bat(sh)or click the Tomcat executable, and in the Apage Tomcat Properties dialog box go to the Java tab. There you can see the Java classpath.
You will also need to add the servlet-api.jar file manually to the classpath. It can be found at: e.g. <tomcat- dir>\common\lib\servlet-api.jar. |
To enable statistics collection on WebSphere
Custom
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
Click Save.
The cookie session name for J2EE (JSESSIONID) is the default value for the <filter-session-cookie> tag. |
To add post-parameters collection for IIS, see the following sections:
By inserting wildcard application mapping, you can instruct IIS to allow ISAPI applications known as interceptors to intercept and examine every request before the requested page is sent to its mapped application. The effect is an application mapping that handles every file name extension.
You must be a member of the Administrators group on the local computer to perform the following procedure or procedures. As a security best practice, log in to your computer by using an account that is not in the Administrators group, and then use the runas command to run IIS Manager as an administrator. At a command prompt, type run as /User:Administrative_AccountName"mmc systemroot\system32\inetsrv\iis.msc". |
To add a wildcard application mapping to a Web server or Web site
To add the Precise post-parameters collection extension to the trusted list
To update the collect-post-parameters tag
To add post-parameters collection for IIS, see the following sections:
By inserting wildcard application mapping, you can instruct IIS to allow ISAPI applications known as interceptors to intercept and examine every request before the requested page is sent to its mapped application. The effect is an application mapping that handles every file name extension.
You must be a member of the Administrators group on the local computer to perform the following procedure or procedures. As a security best practice, log in to your computer by using an account that is not in the Administrators group, and then use the runas command to run IIS Manager as an administrator. At a command prompt, type run as /User:Administrative_AccountName"mmc systemroot\system32\inetsrv\iis.msc". |
It is highly recommended to install the Microsoft hotfix mentioned in KB 2505146 (http://support.microsoft.com/kb/2505146) as this solves a Microsoft IIS7 issue. Should you not apply the hotfix and continue to perform the following steps, your application will stop working. |
To add wildcard application mapping to a Web server or Web site, 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> add-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
For example: products\www\install\psww_insert_isapi_handlers.bat "E:\Precise Installation" 2442 Petshop add-handler PreciseWebHandler "E:\Precise Installation\products\www\instances\2442\bin\IISFilter"
To update the collect-post-parameters tag
To add post-parameters collection for all other supported Web servers, see the following section:
This feature is not supported for Apache 1.3. |
To update the collect-post-parameters tag
registry/instances/www/<server_name>/<instance_name>/settings/server-side
.To remove wildcard application mapping from a Web server or Web site
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
For example: products\www\install\psww_insert_isapi_handlers.bat
"E:\Precise Installation" 2442 Petshop remove-handler PreciseWebHandler "E:\Precise Installation\products\www\instances\2442\bin\IISFilter"
| | | | | | | |