This section includes the following topics:

Based on your application, you can install special Collectors, called Interpoints that gather information on the activities and resource consumption of special application components. The Interpoints then correlate this information with MS SQL Server information so that you can see ERP users, transactions, reports, and so on.

You can install the following Interpoints:

  • Interpoint for PeopleSoft
  • Interpoint for SAP
  • Interpoint for Siebel

See the appropriate section for installation of each Interpoint.

Pre-installation tasks

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 installing a SQL Tier instance, verify that you have performed the following tasks:

  • Use the Precise Framework Installer to install framework components
  • Create a Microsoft SQL Server login name with system administrator privileges and a password. This is optional for the SQL Server Tier; you may use the Microsoft Windows authentication option instead.
  • If you intend to install SAP Interpoints, install the SAP Remote Function Call (RFC) client on the server that the SQL Server Tier Collector is installed on. Verify that the RFC functions STUM_WP_SERVER_ACTIVITY and TH_SERVER_LIST are enabled in your application. Define an additional working process within SAP to be used by the SAP Interpoints. This additional process will help avoid a queue of working processes that may be caused by an RFC call that SAP Interpoint executes through a specially allocated SAP working process. Create an SAP user account that the SAP extension will use to access the system. If you install Precise for SAP, you can use the same user as is used by Precise for SAP.

For more details on the required authorizations, see Pre-installation tasks on page 26.

  • Close the Services window in the Control Panel if you are installing on a Windows server.
  • If you want to use the Recommend feature in Precise for SQL Server with different SQL Server versions, verify that all specific versions of the SQL Server clients are installed on the Precise for SQL Server FocalPoint server.
  • When running the Collector in remote sampling mode, the Collector Windows Service credentials requires System Administrator privileges on the remote server (by default, the Collector service is run under the Local System account, which does not have privileges on other servers).
  • If you are installing an MS SQL 2005 Collector on a Framework with an MS SQL 2008 PMDB, verify that MS SQL 2008 client tools are installed on the machine with MS SQL 2005.

Installing a SQL Tier instance

This section describes the procedures that are needed to install a SQL 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 page 200.

Internationalization

To facilitate SQL Server Internationalization verify that:

  • The locale of the PMDB, FocalPoint, PMDB instances, and BA machines and servers with monitored SQL instances are valid (and are the same for all servers).
  • The instance and database collation of the PMDB and monitored SQL instances are the same, and support chosen locale.

Adding a SQL Tier instance

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

  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 instances tree item
  5. At the bottom of the Display Instances & Clusters screen, click Add Instance. An Add New Instance dialog box appears.
  6. Select the required technology from the list.
  7. Select the application from the list.
    If the desired application is not on the list, follow steps a-d:
    1. Click Add.
    2. In the Application Name field, type in the new application name.
    3. On the Application System field, select the system application from the list.

    4. 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.

  8. Select a Tier from the list.

  9. Click OK to view the next screen.

    Always refresh AdminPoint after adding an instance.

Defining SQL property settings

To define SQL property settings

  1. Click the "SQL Server Instance / <Host>,<Port>" drop-down menu and select the SQL Server instance.

    This is the name of the SQL Server instance you want to monitor. The list includes all instances that were detected in the Local Area Network. To monitor a different instance, type the instance name. SQL Server instances that contain the ‘$’ sign are not supported. If you choose a remote SQL Server instance, you will see the remote host server in the Servers list.

    You can also insert an instance using the format "<host>,<port>," where <host> is the server name and <port> is the port of the SQL server instance. This is useful when the SQL Server browser service is disabled or deactivated.

  2. Click the "Monitor SQL Server activity from this server" drop-down menu and select the server from the list. 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 server where you want to install the SQL Server Tier Collector. The server name or IP address appears in the list only if you previously defined it as a Precise server. You can install the Collector either on the sampled server, or on a remote server. If you wish to associate the Collector with Precise for Storage, you must install the Collector on the sampled server.

    When you want to delete the server, you will have to delete the dependent instances first before you are allowed to remove this server.

  3. Click the "Connect using" drop-down menu and select the authentication type for the SQL Server.

    This is the authentication type the SQL Server Tier Collector will use to log in to the SQL Server instance. Select Windows Authentication to log in with the Windows user used to start the Precise for SQL Server service. Select SQL Server Authentication to log in with an existing SQL Server login name. To use Windows Authentication, you may need to change the user with which you log in to the Precise for SQL Server services (this means that this user needs to become the user who is defined in the SQL instance and has the Administrator permissions). If the Collector is installed on the monitored server, open the Services window and change the user with which you log in to the Precise for SQL Server Collector and the Precise Listener agent service. If the Collector is installed on a different server than the monitored instance, see step 6 below. When installing the Listener agent, you can choose to install all services with a dedicated Log In user.

  4. Enter your Login name.

    If you connect using Windows Authentication, the login is based on the login used to start the Precise for SQL Server agents. If you choose SQL Server Authentication, an existing SQL Server user name and password with system administrator privileges are required here.

  5. Enter the password.

  6. If the PMDB is using Windows Authentication, or the Collector is using remote sampling, at the bottom of the screen, under "Use different Windows Service credentials than the LocalSystem account," enter accounts with the following permissions:
    Table 18-1 Permissions

    WhenPermissionWhere
    Remote samplingUser with full control permissionOn the Precise folder

    User who is allowed to use Windows Authentication

    User with full control permission

    On the PMDB server

    On the Precise folder

    Remote sampling and PMDB using Windows Authentication

    User who is allowed to use Windows Authentication

    User with full control permission

    On the PMDB server

    On the Precise folder

    PMDB uses Windows Authentication and associating to Precise for StorageSystem AdministratorOn the monitored server

    To add the parameters

    1. On the Windows Authentication Settings screen, enter the user name.
    2. Enter the Password.
    3. Enter the Domain or Server name.
  7. Click Next.

About the AdminPoint Tier installation preview screen

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:

  • Server name or IP address
  • The name of the monitored server
  • What actions will be performed in their respective order
  • Installation folder (location)
  • Required disk space
  • Currently available disk space

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.

About the AdminPoint Tier installation progress screen

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.

About the AdminPoint Tier installation complete screen

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).

About the AdminPoint Tier Action Items screen

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.

Post-installation action items

When the SQL Server Tier is installed, post-installation tasks may be required. This may depend on whether Precise for Storage or ERP Extension is installed.

After you install SQL Server, a user who is a member of the sysadmin fixed server role must launch Database Engine Tuning Advisor before anyone else. When the sysadmin user launches Database Engine Tuning Advisor that action initializes the application for use by others. After Database Engine Tuning Advisor is initialized, any user who is a member of the db_owner fixed database role can use it to tune tables on databases they own. For more information about initializing Database Engine Tuning Advisor, see the Initializing Database Engine Tuning Advisor on the MSDN website.

Installing the product Interpoint for PeopleSoft Collector trigger

If you have installed the Interpoint Collector to monitor PeopleSoft activities, you need to create a trigger on the table PSPRCSRQST in the PeopleSoft database. In addition, you need to enable the database monitoring parameter in the PeopleSoft configuration file.

To install the Interpoint for PeopleSoft Collector’s trigger and enable the database monitoring parameter

  1. Open the PeopleSoft configuration file: psappsrv.cfg (usually under PT%version%/appserv/%domainName%). If EnableDBMonitoring=1, proceed to step 6. Otherwise, proceed to step 2.
  2. Disconnect all PeopleSoft users.
  3. Shut down all PeopleSoft servers.
  4. Edit the DB Monitoring parameter to be TRUE:  EnableDBMonitoring=1
  5. Restart the PeopleSoft application servers.
  6. Using SQL Query Analyzer, connect to the database holding the PeopleSoft tables. Verify that you are connecting with a user that is a member of the db_owner database role in the database.
  7. Execute the following batch:
              if exists (select name from sysobjects where name = 'precise_psprcsrqst_register' and type = 'TR')
              drop trigger precise_psprcsrqst_register go
              if exists (select name from sysobjects where name = 'VERITAS_psprcsrqst_register' and type = 'TR')
              drop trigger VERITAS_psprcsrqst_register go
              if exists (select name from sysobjects where name = 'Symantec_psprcsrqst_register' and type = 'TR')
              drop trigger Symantec_psprcsrqst_register go
              create trigger precise_psprcsrqst_register on PSPRCSRQST for update as
         declare @oprid char(30), @prcsinstance int, @old_status int, @new_status int, @info binary(50)
         select @old_status = RUNSTATUS from deleted select @new_status = RUNSTATUS from inserted if (@new_status <> 7) or (@old_status = 7) return
         select @oprid = OPRID, @prcsinstance = PRCSINSTANCE from inserted
         set @info = convert(binary(50), rtrim(@oprid) + ',' + convert(varchar(20), @prcsinstance))
         set context_info @info go

Save

  • No labels