Service Virtualization

Hi Team,

I am trying to connect to SAP application server using the below details using SAP IDOC sender step. My intention is to send an IDoc to the SAP PI system

1. Host
2. System number
3. User
4. Password
5. client

In the host field, I have provided port number (hostname:50000) also. Tried to test the connectivity to SAP server. It is displaying the below error

ERROR       hostname 'devsppi220.unix.gsm1900.org:50000' unknown

I provided only the hostname in the host field. The below error is displayed

ERROR       partner 'devsppi220.unix.gsm1900.org:3300' not reached

It seems like, the SAP is connecting to the default port 3300. How can I make the host to connect to the specific port 50000. Is there anything else to be needed from my end.

Appreciated your support.

The SAP access credentials in the screenshot do not seem to be valid (For SAP systems, system number and client ID should not be strings). Please get in contact with your SAP administrator to provide you with valid SAP access credentials. Apart from hostname, User ID and password, these include - if you want to connect to a SAP Application Server - the two-digit system number (sys_nr), and a two- or three-digit client ID (client_ID). SAP port numbers for Application servers start at 3300. Your SAP system will be available per 'SAP Gateway' at port number 3300+<sys_nr>. Very often SAP system have strict security rules and grant access to known systems only. Hence you should make sure by contacting your SAP administrator that your test system is granted access to the SAP gateway at that specific port. You can validate your access credentials by SAP-GUI and logging into the SAP system with your SAP user ID, password AND providing the SAP client ID.

You can find some supporting informatio at SAP JCo connection settings.

Regards,

Ulrich

Hi,

I tried with system number 00 and client 100. The system number I tried are 01, 02 and 03 (available system numbers). In the screenshot, I could not put that info in community. This is the reason why I put as string. SAP team only provide the user id and password and the user they provided is an authorized user. The real problem comes at the port 50000.

I don't have a provision to use this specific port in the Lisa dialog. If I provide only the hostname, by default it is taking as 3300. According to system number 01 and 02, it is incrementing to 3301, 3302. No other way. Finally I used the advanced connection property jco.client.gwserv to provide the 50000 port. It is displaying the below error.

ERROR       connection to partner 'devsppi220.unix.gsm1900.org:50000'
broken

Detailed error log with 50000 PORT in advanced settings

Error: Initialization of destination PISOADP2:0ffbfbb382e5f7aba69f47f0751b811d@devsppi220.unix.gsm1900.org::00::100::::::false::50000::en:: failed: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=PISOADP2:0ffbfbb382e5f7aba69f47f0751b811d@devsppi220.unix.gsm1900.org::00::100::::::false::50000::en:: ASHOST=devsppi220.unix.gsm1900.org SYSNR=00 GWSERV=50000 PCS=1

LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       connection to partner 'devsppi220.unix.gsm1900.org:50000'
            broken
TIME        Mon Jan 22 13:19:51 2018
RELEASE     721
COMPONENT   NI (network interface)
VERSION     40
RC          -6
MODULE      gwxx.c
LINE        646
DETAIL      NiIRead: P=10.158.223.96:50000; L=10.156.46.114:64046
SYSTEM CALL GwRead
COUNTER     2

Detailed error log without 50000 PORT in advanced settings

Verifying Asset
Error: Initialization of destination PISOADP2:0ffbfbb382e5f7aba69f47f0751b811d@devsppi220.unix.gsm1900.org::00::100::::::false::en:: failed: Connect to SAP gateway failed
Connection parameters: TYPE=A DEST=PISOADP2:0ffbfbb382e5f7aba69f47f0751b811d@devsppi220.unix.gsm1900.org::00::100::::::false::en:: ASHOST=devsppi220.unix.gsm1900.org SYSNR=00 PCS=1

LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner 'devsppi220.unix.gsm1900.org:3300' not reached
TIME        Mon Jan 22 13:23:14 2018
RELEASE     721
COMPONENT   NI (network interface)
VERSION     40
RC          -10
MODULE      nixxi.cpp
LINE        3289
DETAIL      NiPConnect2: 10.158.223.96:3300
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT  WSAECONNREFUSED: Connection refused
COUNTER     2

Kindly helped me to come out from this issue

Thanks,

Rajesh

Hello,

for both issues I recommend querying the Internet for possible root causes.

Detailed error log with 50000 PORT in advanced settings

The error message "ERROR connection to partner 'devsppi220.unix.gsm1900.org:50000' broken" seems to indicate that the connection attempt from DevTest fails to reach/connect to the server at this port. This may be due to firewalls in your network route, the server is not listening on this port, etc. You might want to check with your network administrator to narrow down on the problem. 

Detailed error log without 50000 PORT in advanced settings

"ERROR10061 wsaeconnrefused connection refused" means that the SAP server was contacted, but actively refused the connection. This can have various reasons, too. For instance the SAP Application server is down, there is no SAP Application server listening on this port, or your client is not authorized to connect to the server. For this case, I recommend talking to your SAP administrator to check the problem in the SAP gateway log files and fix it, if possible. 

SAP Gateway ports are configured in etc/services. I have attached the default SAP service->port assignments. SAP chooses service 'sapgw<sysnr>' to connect to a SAP application server. If you change the service setting for 'sapgw00', SAP connection establishment for sysnr 00 will try to connect you to the port associated with 'sapgw00'. 'sapgw00' is the default port for SAP systems. I recommend logging into SAP system by SAP GUI first to validate your connection settings and user credentials.

Regards,

Ulrich

Thank you Ulrich.

The SAP port is 50000. We tested the connectivity from Devtest Server to the SAP server

Connection is already open from tstsvrt001.unix.gsm1900.org to the below server and port. Hence there is no connectivity or network issue.

[skabbi@tstsvrt001 ~]$ telnet devsppi220.unix.gsm1900.org 50000

Trying 10.158.223.96...

Connected to devsppi220.unix.gsm1900.org.

Escape character is '^]'.

In the advanced properties I provided jco.client.gwserv as 50000 so the port will be taken as 50000 instead of 3300. Is that the right configuration in Devtest or not? Kindly let me know.

Thanks,

Rajesh

Hello Rajesh,

DevTest uses SAP JCo API to connect to the SAP system. The parameters you are setting are SAP JCo connection settings. As you seem to have port 50000 available on your dedicated SAP system, I would configure the corresponding SAP gateway service in etc/service to use port 50000 instead of its default port. So, if the SAP system number is 00, I would set 'sapgw00' to talk to port 50000 (instead of default port 3300), if system number is 01 then set 'sapgw01' to port 50000 (instead of port 3301), and so on.

Did you verify that you can login to the SAP system per SAP-GUI with your connection settings and credentials? This should be your first validation test of those parameters, and it is independent from DevTest.

Regards,

Ulrich

Thanks Ulrich for your suggestion. I will keep you posted on the updates.

Please be informed that the JCO IDOC connection from Ca Devtest to SAP server is successful. I am not finding a provision for attaching the screenshot over here. These are the high level activities done from our end inorder to make it working

Deployed the third party jar files along with the dll in classpath & restarted the workstation

• In windows, add the following line to the end of C:\Windows\System32\drivers\etc\services file: sapgw00                3300/tcp                                                                                             
• Enabled RFC authorization for the test user from SAP VD2 server. Removed all other extensive access for the user
• Using Devtest JCO test script connected to SAP server

Thank you very much.

Regards,

Rajesh

Glad to hear that it is working now. Thanks for sharing.