SAP Pre-Installation Checklist - trillium_discovery - trillium_quality - 17.1

The following information should be available prior to installation.

• What version of SAP is implemented?

• What version of SAP Basis is implemented?

• Is the SAP operating system installed on a Windows system or a Linux system?

• Are you creating a stand-alone gateway for the two systems to communicate? (This is highly recommended for failover.)

• Typically, the following team members should be available during installation:

• SAP Basis Administrator – to install the Add-On

• SAP function team member – to perform the configuration

• Other (system administrator)

Optional components include:

SAP Client: The SAP NW client and a sample project for the SAP Connector, which you can use to test your SAP Connector installation.

Cleansing Service: A service that handles data cleansing requests. The default service name is TSQSAPCleanser17.

Matching Service: A service that handles data matching requests. The default service name is TSQSAPMatcher17.

To install the SAP Client

1. When you install the SAP Client, you are prompted for the following:

   Director Port: Verify that the port number is the same as the port number on which the Director is listening. The default is 17400.

   Director Host: The host name or IP address of the node on which the Director is running.

   SAP Client Maximum Threads: The maximum concurrent requests that the client can handle. The default is ten (10).

   SAP Client Configuration File: The path and filename of the Trillium Quality SAP configuration file, by default /conf/TrilSAP.cfg.

   A summary of your selections displays.

2. Enter 1 to continue and press Enter.

3. Set the following TS Quality Client for SAP RFC parameters:

   Destination: Unique destination name entry. Defaults to TRILLIUM_R.

   Gateway Host: The SAP Gateway server host name.

   Gateway Service: SAP Gateway server name, generally the value “sapgw” followed by the two-digit system number.

   Program ID: The registered SAP RFC server program name. Defaults to TRILLIUM.CONNECTOR.

   SAP Version: Defaults to 610.

   SAP Client: The SAP customizing client where the TS Quality Connector is activated.

   System ID: Unique SAP application system name, for example C5W.

   Language: Defaults to EN (English).

   User Name: The SAP RFC service user name, for example TRILLRFC.

   User Password: The SAP RFC user’s password that was set by the Security Administrator.

   User Logon Group: Application server’s group name (optional); default is “Default”.

   Message Server Host: Host name of the message server, for example localhost.

   A summary of your selections displays.

4. Enter 1 to continue and press Enter. The next prompt displays depends on the components you have selected for installation.

To install the Cleansing Service for SAP

1. When you install the Cleansing Service for SAP, you are prompted for the following:

   Director Host: The host name or IP address of the node on which the Director for this client is running.

   Director Port: Verify that the port number is the same as the port number on which the Director is listening. The default is 17400.

   Cleansing Server Port: The port number on which the cleansing service will listen for requests. Ensure that the same port is not used by multiple services. The default is 17420.

   Cleansing Configuration File: Accept the default path and file name for the sample Trillium Quality configuration file, /tsq/software/samples/projects/sap_proj/settings/TrilSAP.cfg, or type a new path and name.

   Cleansing Processing Level: The Processing Level determines how requests will be queued for handling by the server. The optimum processing level is dependent on your hardware configuration. In general, using one thread for each processor yields optimum performance.

   At all levels, the maximum number of concurrent attaches is 128. The processing level options are:

   1. Minimum - No threads will be spawned for cleansing. Requests will be placed in a queue. The client that has been waiting the longest for a request to be serviced (based on when the server last processed a request for that client) is processed next. Note that the network queue limits the number of attach requests that can be waiting.

   2. Default - One thread will be actively cleansing; another thread will be listening for requests on the network. Other requests will wait until the request is completed. This level is most appropriate for a system with one or two execution cores.

   3. High - Eight threads will be actively cleansing. Other requests will wait until a request is completed. This level is most appropriate for a system with more than four cores.

   4. Maximum - A thread will be created for each incoming request, within the limit of 128 concurrent attaches. This level can increase performance depending on the overall load on the system, for example, if some records require more processing resources.

   A summary of your selections displays.

2. Enter 1 to continue and press Enter. The next prompt displays depends on the components you have selected for installation.

To install the Matching Service for SAP

1. When you install the Matching Service for SAP, you are prompted for the following:

   Director Host: The host name or IP address of the node on which the Director for this client is running.

   Director Port: Verify that the port number is the same as the port number on which the Director is listening. The default is 1717400400.

   Matching Server Port: The port number on which the matching service will listen for requests. Ensure that the same port is not used by multiple services. The default is 17422.

   Search Matching Server Port: The port number on which the Fuzzy Search matching service will listen for requests. Ensure that the same port is not used by multiple services. The default is 17424.

   Matching Configuration File: Accept the default path and file name for the sample Trillium Quality configuration file, /tsq/software/samples/projects/sap_proj/settings/TrilSAP.cfg, or type a new path and name.

   Search Matching Configuration File: Accept the default path and file name for the sample Trillium Quality configuration file for Fuzzy Search,/tsq/software/samples/projects/sap_proj/settings/TrilSAP001.cfg, or type a new path and name.

   Processing Level: The Processing Level determines how requests will be queued for handling by the server. The optimum processing level is dependent on your hardware configuration. In general, using one thread for each processor yields optimum performance.

   At all levels, the maximum number of concurrent attaches is 128. The processing level options are:

   1. Minimum - No threads will be spawned for matching. Requests will be placed in a queue. The client that has been waiting the longest for a request to be serviced (based on when the server last processed a request for that client) is processed next. Note that the network queue limits the number of attach requests that can be waiting.

   2. Default - One thread will be actively matching; another thread will be listening for requests on the network. Other requests will wait until the request is completed. This level is most appropriate for a system with one or two execution cores.

   3. High - Eight threads will be actively matching. Other requests will wait until a request is completed. This level is most appropriate for a system with more than four cores.

   4. Maximum - A thread will be created for each incoming request, within the limit of 128 concurrent attaches. This level can increase performance depending on the overall load on the system, for example, if some records require more processing resources.

   A selections summary displays.

2. Enter 1 to continue and press Enter.

3. After Trillium Quality for SAP installation, you must set the following environment variables:

• TRILLDIRADDR: Name of the host or IP address (in dotted decimal format) of the node on which the Director listens. Set on client and cleansing/matching service machines.

• TRILLDIRPORT: Port on which the Director listens for incoming requests. Set on client and cleansing/matching service machines.