Configuring the RFC Destination - trillium_quality - 17.1

Trillium Quality for SAP Reference Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Quality
Version
17.1
Language
English
Product name
Trillium Quality
Title
Trillium Quality for SAP Reference Guide
Topic type
Administration
Overview
How Do I
Configuration
Reference
Installation
First publish date
2008

You must configure an SAP RFC Destination so that the SAP system can communicate with Trillium for SAP. There are two ways to perform this task:

  •    Via transaction /nSM59

  •    Via the Address Management with Trillium IMG option

To configure an SAP RFC Destination

  1. Use transaction /nSM59 or the Address Management with Trillium IMG option.

  2. Click the Maintain RFC Destination for Trillium option.

    The RFC Destination Configuration window opens.

    Figure 1. RFC Destination Configuration Window RFC Destination Configuration Window
  3. Expand the TCP/IP entry.

  4. Click Create.

    The RFC Destination Create window opens.

  5. Enter the required values in the Technical Settings tab. See Table: Required SAP RFC Destination Parameters for a description of the parameters.

    Figure 2. RFC Destination Required Parameters (Technical Settings Tab)
    RFC Destination Required Parameters (Technical Settings Tab)
  6. Click the MDMP and Unicode tab and enter the required values. See Table: Required SAP RFC Destination Parameters for a description of the parameters.

     
    Figure 3. RFC Destination Required Parameters (MDMP & Unicode Tab)
    RFC Destination Required Parameters (MDMP & Unicode Tab)
  7. Save the changes.

  8. Click Connection Test to ensure that there is a connection between SAP and Trillium for SAP.

A success window (Figure: Successful Test Connection) or failure window(Figure: Unsuccessful Test Connection) appears.

If the test is successful, there is a connection between SAP and the TS Client for SAP. If the test is not successful, check to be sure that the TS Client for SAP is running and that the dynamic structure has been retrieved successfully.

Note: Other RFC Destination Models for best practices and other recommendations when there are multiple SAP systems (for example, R/3 and CRM) to be configured.
Table 1. Required SAP RFC Destination Parameters

Field

Description

Required entry

Technical Settings

RFC Destination

Unique name of an RFC destination.

Name of your choice (for example, TRILLIUM_CONNECTOR)

Connection type

Type of RFC connection to specify the communication method.

T = Start an external program via TCP/IP

Description

Short description of the RFC destination.

A description of your choice.

Activation Type

Activation Type

Select Registration Server Program

Program ID

Identification of a registered RFC server program.

TRILLIUM.CONNECTOR 

Note: The program ID must matchthe registration parameters (PROGRAM_ID=) setting in the SAPNWRFC.INI file previously set.

Gateway host

Gateway host name

Host name of the Gateway being used to communicate with Trillium for SAP; for example, localhost. 

Note: The name must match the GWHOST parameters setting in SAPNWRFC.INI.

Gateway service

Gateway service name

Name of Gateway service being used to communicate with Trillium for SAP; for example, sapgw00.

Note: The name must match the GWSERV parameters setting in SAPNWRFC.INI.

MDMP & Unicode Settings: Communication Type with Target System

Unicode

TrilliumSAPNW64 enabled for Unicode

Select Unicode option for the Unicode-enabled TrilliumSAPNW64.

Figure 4. Successful Test Connection Between SAP and the TS Connector Result Screen
Successful Test Connection Between SAP and the TS Connector Result Screen
Figure 5. Unsuccessful Test Connection Between SAP and TS Connector Result Screen
Unsuccessful Test Connection Between SAP and TS Connector Result Screen