The following models are other possible methods without the use of stand-alone gateway. They will serve the communication purposes but are not the recommended methods.
Multiple SAP Systems: Different TrilliumSAPNW64 clients
Multiple TS Clients for SAP on the same server are allowed in a Linux and Windows environment.
The system shown in Figure 3 comprises two SAP systems in a Linux environment. The two systems require different TS Clients for SAP. An SAP administrator can configure the RFC Destination in each system with its own gateway and host name, and then specify in the Trillium Quality System SAPNWRFC.INI file the different gateways and host names for each system under a different Destination name.
For example:
DEST=TRILLIUM_R
PROGRAM_ID=TRILLIUM.CONNECTOR
GWHOST=hostA
GWSERV=sapgw00
TRACE=0
DEST=TRILL_CRM
PROGRAM_ID=TRILLIUM.CONNECTOR
GWHOST=hostB
GWSERV=sapgw00
TRACE=0The startups for the two TS Clients for SAP also need to be modified to point to the specified destination name; for example:
TrilliumSAPNW64620
TrilliumSAPNW64620
Multiple SAP Systems: Single TrilliumSAPNW64
Figure 4 illustrates the possibility for multiple SAP systems to go through one RFC Destination configuration for communication with Trillium Quality where both systems required the same TrilliumSAPNW64.
In this model, the CRM RFC destination is configured to go through the SAP gateway and host for postal validation and duplicate check processes.
For example, the SAP gateway and host names are sapgw00 and hostA. This information is to be used to configure the RFC Destination in both SAP systems. The same information is required in the TS Client SAPNWRFC.INI file.
