RFC Error communication while connecting to message server

[karanshaheri]

Hello,

I am using SMP 2.3. I have configured JavaBE.ini file to connect to Message server for Load Balancing.

I am getting following error.

18:09:20 04/06/2015: Exception: 18:09:20 04/06/2015 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: RFC_ERROR_COMMUNICATION Connect to message server failed), Connect_PM  MSHOST=ascs01ECP.tpc.co.in, R3NAME=ECP, GROUP=SPACE

I am pasting my JavaBE.ini file for reference.

Please , , can you help me out with this issue. User has full RFC authorisations.

JavaBE.ini file contents.

[HOST]

server=172.16.214.26

;  mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10...etc

APPNAME=SAP_WORK_MANAGER_60

[CONFIG]

;  Used to get the SAP Configutaions from SAP if source=SAP or from JavaBE ini file

;  SAP Configurations are [ENABLE_TABLE], [TABLE_CHECK], [TABLE_REFRESH], [BAPI_WRAPPER],

;  [SAPOBJECT], [CT_SAPOBJECT], [CT_BAPI_WRAPPER], [CT_RETURN_TABLE], [CT_DELETE_TABLE].....etc

source=SAP

[TEST_LOGON]

UID=

UPASSWORD=

UGUID=

SERVERSERIALNUM=

;  Service login user is used to get the SAP Configutaions from SAP if source=SAP

;  Set ENABLED=true if source=SAP or ENABLED=false if source=INI

;  If ENABLED=true, set the UID, UPASSWORD and SERVERSERIALNUM

;  SERVERSERIALNUM is the Agentry server serial number

[SERVICE_LOGON]

ENABLED=true

UID=syclo_srv

UPASSWORD=tata@123

UPASSWORDENCODED=false

SERVERSERIALNUM=SAP_WORK_MANAGER_60

[PUSH_LOGON]

ENABLED=true

UID=syclo_srv

UPASSWORD=tata@123

UPASSWORDENCODED=false

SHAREDCONNECTION=10

[CLIENT_NUM]

CLIENT=500

;CLIENT=010

[SYSTEM_NUM]

;SYSNUM=33

SYSNUM=04

[LANGUAGE]

LANG=EN

[LOGGING]

;1=Fatal, 2=Error, 3=Warning, 4=Info, 5=debug, 6=trace

Level=4

[LOGON_METHOD]

;  USER_AUTH if standard UID/Password authentication is used

;  USER_AUTH_GLOBAL if pooled connections using single UID/Password is used

;  USER_AUTH_GROUP if UID/Password authentication with SAP Message Server

;   (load balancing) is used

;  USER_AUTH_SSO if SSO2 ticket authentication with SAP Portal Server is used

;  USER_AUTH_CUSTOM for a custom login module setup

LOGON_METHOD=USER_AUTH_GROUP

[GLOBAL_LOGON]

;  referenced when LOGON_METHOD=USER_AUTH_GLOBAL

;  uses a pool of connections to the SAP backend all utilizing a single

;    UID/password

UID=

UPASSWORD=

SHAREDCONNECTION=100

[GROUP_LOGON]

;  referenced when LOGON_METHOD=USER_AUTH_GROUP

;  individual user authentication using an SAP Message Server which distributes

;  client connections among a "group" of SAP application servers based on load

;  balancing criteria

;

UID=syclo_srv

UPASSWORD=tata@123

SHAREDCONNECTION=50

;  host name or IP address of SAP Message Server

MESSAGE_SERVER=ascs01ECP.tpc.co.in

R3_NAME=ECP

GROUP_NAME=SPACE

SYSTEM_ID=ECP

CLIENT=500

[USER_AUTH_SSO]

; referenced when LOGON_METHOD=USER_AUTH_SSO

; SSO related information for use in LoginModuleSSO to facilitate login to

; an SAP system using tickets from a message server.

;

PORTAL_URL=https://server:port/irj/portal

; verificaiton file from the portal. Not required, but if portal names are different from the authenticated username, it will be needed to decode the name.

VERIFICATION_USE=false

;VERIFICATION_FILENAME=verify.pse

;VERIFICATION_PASSWORD=

;VERIFICATION_PASSWORD_ENCODED=false

; key store for client authentication to the server if required

KEY_STORE_USE=false

;KEY_STORE_TYPE=WINDOWS-MY

;KEY_STORE_FILENAME=keystoreFileName

;KEY_STORE_PASSWORD=

;KEY_STORE_PASSWORD_ENCODED=false

; trust store for server authentication to the client (accepting only trusted servers to prevent MITM attacks)

TRUST_STORE_USE=true

TRUST_STORE_TYPE=WINDOWS-ROOT

;TRUST_STORE_FILENAME=truststoreFileName

;TRUST_STORE_PASSWORD=

;TRUST_STORE_PASSWORD_ENCODED=false

COOKIE=MYSAPSSO2

HTTPTYPE=https

SSL_VERSION=SSLv3

JAVA_SECURITY_DEBUG=false

JAVA_NET_DEBUG=false

; classes to instantiate for the sso client and the callback handler

SSOCLIENT_CLASS=com.mysap.sso.SSOClient

CALLBACK_HANDLER_CLASS=com.syclo.sap.auth.CallbackHandler

[USER_AUTH_CUSTOM]

; referenced when LOGON_METHOD=USER_AUTH_CUSTOM

; custom defined login configuration that use JAAS for authentication

;

MODULE_CLASS_1=com.syclo.sap.auth.LoginModuleBasic

MODULE_CLASS_1_FLAG=REQUIRED

MODULE_CLASS_1_OPTION_1_KEY=CLIENT_NUM

MODULE_CLASS_1_OPTION_1_VALUE=clientNum

MODULE_CLASS_1_OPTION_2_KEY=HOST

MODULE_CLASS_1_OPTION_2_VALUE=serverHostName

MODULE_CLASS_1_OPTION_3_KEY=SYS_NUM

MODULE_CLASS_1_OPTION_3_VALUE=sysNum

;MODULE_CLASS_2=

;MODULE_CLASS_2_FLAG=

;

;MODULE_CLASS_3=

;MODULE_CLASS_3_FLAG=

; class to instantiate for the callback handler

CALLBACK_HANDLER_CLASS=com.syclo.sap.auth.CallbackHandler

[REQUIRED_BAPI_WRAPPER]

com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK

com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT

com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET

com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET

com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD

com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD

com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET

com.syclo.sap.bapi.GetEmployeeDataBAPI=/SMERP/HR_DOEMPLOYEE_DATA_GET

com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL

com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET

com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD

com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT

com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL

com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET

com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT

com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL

com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET

com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL

com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL

com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD

com.syclo.sap.bapi.SignatureCaptureBAPI=/SMERP/CORE_DOBDSDOCUMENT_CRT

[karanshaheri · Accepted solution]

Hello,

Issue got resolved. My SMP and message server are on a different system. There was host entry missing for Message server in my server where SMP was installed.

[karanshaheri]

Hi I am getting following error now.

java.lang.InstantiationException: For input string: ""

        at com.syclo.sap.Server.setInitialParameters(Server.java:397)

        at com.syclo.sap.Server.initServer(Server.java:276)

        at com.syclo.sap.Server.<init>(Server.java:257)

        at com.syclo.sap.workmanager.Server.<init>(Server.java:30)

Exception: 17:01:17 04/07/2015 : 20 (Agentry3), JavaBackEndError (JAVA EXCEPTION

CAUGHT: com.syclo.agentry.AgentryException: For input string: ""),

Failed to init Java Back End (Java v6.1.4.179 (JVM version 1.7.0_25, AJAPI versi

on  build )) from ag3javabe.dll

[bill_froelich]

That error appears to be related to a missing parameter value in your JavaBE.ini or Agentry.ini /Management Cockpit.  Double check your JavaBE.ini I don't see anything that jumps out at me as missing.

--Bill

[bill_froelich]

Karan,

I checked one of my configurations where I used this and it is very similar to yours.  The only difference is I don't specify the R3_NAME under [GROUP_LOGON].  Otherwise you will need to confirm values you are using with your SAP team.

--Bill

[karanshaheri]

Hi,

I didn't give R3_NAME. It got populated automaticaly.

One more question. I have maintained [SYSTEM_NUM] section. But if I am connecting to messaging server is it necessary to give System number of SAP system?

[bill_froelich]

I have maintained it in mine as well but I do not think it is needed if you are using USER_AUTH_GROUP.

--Bill