Symptoms
We have two different SAP servers at different locations with different listing IPs. Using K2 Connect we already created a destination for one server and successfully consuming the data from RFC. Now we have created a second destination, and we have enabled the port between K2 Q server and SAP Q server. Even though connection strings are different, K2 Connect is still trying to communicate with the first server with the second server's login credentials and getting failed with connectivity issue.
Diagnoses
- Connection strings used for the two destinations are in the following format:
ASHOST=/H//S/3300 SYSNR=00 CLIENT=800 LANG=EN USER=user PASSWD=pass ASHOST=/H//S/3301 SYSNR=00 CLIENT=800 LANG=EN USER=user PASSWD=pass
- Removing the /S/ portion allows the connection to proceed
- Analyzing the network packets using Wireshark reveals that changing the SYSNR of the connection string allows K2 connect to connect via different ports. For example, SYSNR=00 connect to port 3300, while SYSNR=01 connect to port 3301 and so on.
Resolution
1. Changed connection string to the following format: ASHOST= SYSNR=00 CLIENT=800 LANG=EN USER=user PASSWD=pass
If you have different port requirements, please change the SYSNR accordingly.
2. Please kindly refer to the document link below for steps on how to properly add and use multiple destinations: https://help.k2.com/onlinehelp/k2connect/userguide/4.7/default.htm#Post_Installation_Configuration.htm
