Page History

...

• Before you install a Web AppTier, you need to grant special file and directory permissions (including all subdirectories) to the UNIX or Windows user that you intend to use during the installation.

  Info
  The permissions in the general collection table 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 will not see these auto-detected values and you will have to supply them manually.

  NOTE

• The Operating System user that runs the Web Server or Web Application should have full control privileges for the <i3_root> directory (for example: NETWORK SERVICE for IIS6).

  Info
  For the installation of a Web AppTier, you will need a user with Web administrator privileges.

  NOTE

   
• Permissions that are required for the GENERAL collection on UNIX and Windows.

...

• To install a Precise for Web instance on IIS7.x, the "IIS6 Metabase Compatibility" service and ISAPI filters must be installed.
• If you are going to install SAP WAS ABAP, the following two prerequisites are needed:
  • The import of the Precise for Web transport to the monitored SAP system.
  • The download of the SAP Java Connector (JCo).

  • The installation of SAP Java Connector (JCo) on the server on which Precise for Web FocalPoint is installed.

    Info

    Before installing SAP WAS ABAP, check whether Precise supports your version of SAP WAS ABAP in the Precise Support Matrix that can be found on the Precise Customer Portal. Precise for Web does not provide the following features for the supported SAP WAS ABAP versions: - application user collection - server-side monitoring - client-side monitoring of new browsers, such as IE8, Chrome, and Firefox 3

    NOTE

     
  To enable IIS6 Metabase Compatibility on Windows 2008

...

...

NOTE

...

To download the SAP JCo

1. Open the following URL in a browser window. http://service.sap.com/connectors
2. Enter your SAP Service Marketplace user name and password, and click OK.
3. In the tree view, go to Connectors>SAP Java Connector>Tools and Services.
4. Review the JCo Release notes for the available versions and choose one that is relevant for the operating system of the i³ for Precise for Web FocalPoint server. Note that the JCo may require other prerequisite software as described in the release notes. Use the JCo version as described in the note above.

...

...

NOTE

...

To install the SAP JCo

1. Unzip the contents of the downloaded file to a directory of your choice on the Precise for Precise for Web FocalPoint server.
2. From the directory to which you unzipped the downloaded file: Copy the .JAR file(s) to <i3_root>\java\3rd_party directory on your Precise for Web FocalPoint server.
3. If the Precise for Web FocalPoint is installed on Windows: Copy the .DLL files (from the directory to which you unzipped the downloaded file) to: <i3_root>\products\www\bin directory on your Precise for Web FocalPoint server.
4. If the Precise for Web FocalPoint is installed on UNIX/Linux: Copy the .SO files (from the directory to which you unzipped the downloaded file) to: <i3_root>\products\www\bin directory on your Precise for Web FocalPoint server.
5. Make sure the gateway port between the Precise for Web FocalPoint and the SAP Application Server is open in both directions: The gateway port is 33xx, where xx has to be replaced by the instance number of the SAP Application Server.
6. Maintain the SAP communication ports the services file in: Windows %windir%\system32\drivers\etc\services UNIX /etc/services
7. Replace the following <SID> and <instance-number> with the values from your environment: sapms<SID> 36<instance-number>/tcp sapgw<SID> 33<instance-number>/tcp sapdp<SID> 32<instance-number>/tcp e.g. for a SAP system with the SID = PRD and Instance Number 01: sapmsPRD 3601/tcp # SAP Message Server sapgwPRD 3301/tcp # SAP Gateway sapdpPRD 3201/tcp # SAP Dispatcher

...

...

NOTE

...

• Make sure that the user used to monitor the Sybase instance is a member of the mon_role and sa_role server roles

  Info
  To grant the mon_role server role, run the following command: grant role mon_role to user name. (For example, if you connect as system administrator, run the command as: grant role mon_role to sa).

  NOTE

   
• The following tables must be activated:
  • monProcessSQLText
  • monProcess

...

• Make sure that the master.sysservers table includes the following entry: sp_addserver logical name,'local',physical name where: logical name is the name used to address the server on your system and physical name is the name of the instance as it appears in the interface file ((this file is usually located in the sybase root dir/ini/sql.ini directory or the sybase root dir/interfaces directory)

  Info
  The entry points to the Sybase instance as the local server (srvclass=0). If this entry does not exist, add it to the table.

  NOTE

   
• To function properly, the Statistics workspace requires that you comply with the following requirements:
  • Run the sp_sysmon system stored procedure with the noclear option set only. (i.e. for example: sp_sysmon "00:01:00", noclear)
• When the PMDB is installed using Windows authentication, you need to provide a user that can connect both to the PMDB and to the monitored instance

...

• Refer to the Precise Support Matrix for information on supported DB2 versions and FixPak levels
• Precise software components are installed on each monitored DB2 server. You require a dedicated Precise OS user to be created on each monitored server. The name "precise" is used as an example. Windows On Windows, generally a domain user is created, who is then granted local administrator permissions as required on monitored servers. UNIX For UNIX servers, you need to create a Precise user on every monitored server. For monitored DB2 servers, create the Precise user as follows:
  • Non-null password, not containing special characters, and has a maximum length of 15 characters
  • Connected to the DB2 SYSADM group (as reported by the DB2 GET DBM CFG command)
  • Login shell is ksh, with "dot" (.) in the Path variable
  • The shared library path (LD_LIBRARY, SHLIB_PATH, LIB_PATH) is not set in this user's environment

• For monitoring purposes, the Precise user must have the DBADM and SYSMON privileges or SYSADM privileges

  Info
  The Precise for DB2 AppTier installation creates a schema in either an existing or new tablespace. If you prefer to create a new tablespace, the user must also have DBADM and SYSCTRL privileges or SYSADM privileges.

  NOTE

   
• When monitoring DB2 on HP, make sure the database default charset isn't roman8 (CP1051)
• Close the Services window in the Control Panel if you are installing on a Windows server

...

...

NOTE

...

• Database Specific
  • Precise for SQL Server: Precise Collector can be installed remotely while the EMC Solution Enabler Daemon must be installed on the monitored server.
  • Oracle and DB2 (on UNIX/Linux platforms): The user ROOT is required for the installation.
  • DB2 only: the Precise users (of the Listener) must be in the OS group of DB2 adm. For example, db2adm1.
• EMC - CLARiiON
  • If CLARiiON is the attached storage media, the storage agent of Precise for Oracle or Precise for SQL Server needs to be able to run and gather storage array metrics from the CLARiiON on a periodic basis, and therefore Statistics Logging must be enabled via the CLARiiON software Navisphere

...

• FORMS LISTENER MODE: The relevant port number is defined by the FORMS_PORT environment variable in the adfrmctl.sh script found in the Oracle Applications installation directory

  Info
  If the Precise Insight Savvy for OA is to be deployed, the Forms server must be a UNIX server and must have the Precise Listener and Insight Savvy for Network agents installed to monitor the Forms Tier of Oracle Applications.

  NOTE

   
• FORMS SERVLET MODE: If the Precise Insight Savvy for OA is to be deployed, the Forms server must be a UNIX server and must have the Precise Listener and Precise for J2EE agents installed to monitor the Forms Tier of Oracle Applications
• Access to the Oracle Database with a userid having sysdba priveliges
• Must be able to run command: GRANT EXECUTE ON DBMS_PIPE TO <COLLECTOR_SCHEMA_USER>
• Verify that the Oracle Applications server can be brought down for a short window of time (approximately 30 minutes)
• To make the required modifications:
  • No users can be logged on to the Oracle Applications server
  • No batch jobs or reports can be running on the Oracle Applications server
  • The Concurrent Manager must be shut down
• Verify that you can change the CUSTOM.pll and CUSTOM.plx forms library

...

...

NOTE

...

Custom Apps and Tuxedo

The additional requirements for Custom Apps and Tuxedo are:

...