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:
See the appropriate section for installation of each Interpoint.
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:
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.
To facilitate SQL Server Internationalization verify that:
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 |
Click OK to view the next screen.
Always refresh AdminPoint after adding an instance. |
To define SQL property settings
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. |
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. |
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. |
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. |
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
When | Permission | Where |
---|---|---|
Remote sampling | User with full control permission | On 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 Storage | System Administrator | On the monitored server |
To add the parameters
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 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 Start and Use the Database Engine Tuning Advisor on the MSDN website.
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
psappsrv.cfg
(usually under PT%version%/appserv/%domainName%
). If EnableDBMonitoring=1, proceed to step 6. Otherwise, proceed to step 2.EnableDBMonitoring=1
| | | | | | | |