Configuration of MSSQLISPacStsTest

This test monitors the packages that are running on SSIS and alerts administrators if any package fails or stops abruptly. Packages that are pending processing are also brought to the attention of administrators, as such processes are indicative of a processing bottleneck. Detailed diagnostics reported by the test reveal which package is in which state of execution presently, thus pointing administrators to the problematic packages and greatly shortening troubleshooting cycles.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the host for which the test is to be configured has to be specified.

• In the PORT text box, enter the port number at which the target host being monitored listens.

• This test runs queries on the SSIS database and reports metrics. To enable the test to connect to and execute queries on the SSIS database, this test has to be configured with the name of the SSIS database. By default, the ssisdb is the name of the SSIS database. If you have assigned a different name to this database in your environment, then override the default name by changing the value of the DATABASE NAME parameter.

• This test runs queries on the SSIS database and reports metrics. To enable the test to connect to and execute queries on the SSIS database, you need to configure this test with the correct port number at which the SSIS database listens in the DATABASE PORT NUMBER text box. To know how to determine the DATABASE PORT NUMBER of the SSIS database, refer to Monitoring Microsoft SQL Integration Server document.

• To run queries on the SSIS database and report metrics, this test requires the permissions of a SYSADMIN user. Therefore, specify the credentials of a SYSADMIN user in the USER AND PASSWORD text boxes.

  However, if, owing to security constraints, administrators prefer not to expose the credentials of a SYSADMIN user, then you can create a special user on the Microsoft SQL Server with SSIS_LOGREADER rights to the SSIS database. To know how to create such a user, refer to Monitoring Microsoft SQL Integration Server document. Once the user is created, pass the credentials of this user to the test using the User and Password parameters.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• Specify the name of a specific SQL Integration Server instance that is to be monitored in the INSTANCE text box. The default value of this parameter is “default”. However, if the Microsoft SQL Server hosting the SSIS database uses named instances, then do the following:

  • Configure the INSTANCE parameter with the name of the SQL Server instance that hosts the SSIS database.

  • Do not change the default value of the PORT parameter.

• By default, none is displayed in the DOMAIN text box. If the ‘SQL server and Windows’ authentication has been enabled for the server being monitored, then the Domain can continue to be none. On the other hand, if ‘Windows only’ authentication has been enabled, then, in the Domain text box, specify the Windows domain in which the SSIS database that this test connects to exists. Also, in such a case, the User name and Password that you provide should be that of a user authorized to access the Microsoft SQL server hosting the SSIS database of interest.

• In some Windows networks, NTLM (NT LAN Manager) may be enabled. NTLM is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. NTLM version 2 NTLMv2 was concocted to address the security issues present in NTLM. By default, the IS NTLMv2 flag is set to No, indicating that NTLMv2 is not enabled by default on the target Microsoft SQL server hosting the SSIS database. Set this flag to Yes if NTLMv2 is enabled on that Microsoft SQL server.

• By default, this flag is set to No, indicating that the Microsoft SQL server hosting the SSIS database is not SSL-enabled by default. On the other hand, if the SSIS database is hosted by a Microsoft SQL server that is SSL-enabled, then, set this flag to Yes.

• To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.