agentry 6.1 test backend connection without application

[Former Member]

Dear community,

we do this steps:

• installed the Agentry SAP Framework in the SAP ERP back-end.
• installed Agentry Server 6.1 and Administrator
• installed the Agentry Test Environment
• configured the agentry.ini for java connection and the JavaBE.ini for our SAP Backend

Now we want only check if we could connect succesfully with the agentry server to the SAP ERP back-end.

How can we do this without to create a demo application?

Thanx,

André

[bill_froelich · Accepted solution]

Andre,

Assuming you have the SAPCommon jar file (part of SMP 2.3 SDK) you can execute the following to verify your connection to SAP.

set classPath=./ini4j.jar;./sapjco.jar;./Java/Agentry-v5.jar;./Java/SAPCommon-122971.jar;

rem --- run the simple ConnectTest class

java -cp %classpath% com.syclo.sap.ConnectTest

The version of the SAPCommon jar that you have may be different so replace with the name of your SAPCommon jar version.  The ConnectTest class is in all the recent versions of the jar.

--Bill

[Former Member · Accepted solution]

Thanks,

that is what i need.

André

[Former Member · Accepted solution]

Dear Bill,

i execute the following to verify my connection:

set classPath=./Java/ini4j-0.4.1.jar;./Java/sapjco3.jar;./Java/Agentry-v5.jar;./Java/SAPCommon-130881.jar;

java -cp %classpath% com.syclo.sap.ConnectTest

and now i get the following print:

reading user credentials from [SERVICE_LOGON] section

connecting as...

clientNum=040

sysNum=12

host=XXX.XXX.XXX.XX

name="my username"

*** Caught exception: com/sap/mw/jco/JCO

release::releasing connection

release::complete.

Was the connection successfully established our is this a error in my JCO File that the path is not correct?

Thanx,

André

[bill_froelich · Accepted solution]

Andre,

Do you have a JavaBE.ini file for your backend connection defined?

The connectTest is looking to read system configuration information from that file to use in establishing the connection to SAP.

--Bill

[Former Member · Accepted solution]

Yes i do. And i have configured the [SERVICE_LOGON] section for the agentry server to login during initial startup.

André

here my JavaBE.ini:

[HOST]

server=XXX.XXX.XXX.XX

APPNAME="Appname"

[SERVICE_LOGON]

;The purpose of the [SERVICE_LOGON] is to set up a user(system user) for Agentry Server to login to SAP during initial startup.

ENABLED=true

UID=mySAP-UserName

UPASSWORD=mySAP-UserPassword

UPASSWORDENCODED=false

SERVERSERIALNUM=AVXMLJIOMDDIPLKH

[CONFIG]

source=SAP

[CLIENT_NUM]

CLIENT=040

[SYSTEM_NUM]

SYSNUM=52

[LANGUAGE]

LANG=DE

[LOGGING]

Level=3

[LOGON_METHOD]

LOGON_METHOD=USER_AUTH

[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=/SYCLO/HR_EMPLOYEE_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.TransactionCommitBAPI=WFD_TRANSACTION_COMMIT

com.syclo.sap.bapi.SignatureCaptureBAPI=/SYCLO/CS_DOBDSDOCUMENT_CRT

[bill_froelich · Accepted solution]

Andre,

Try adding the following section to your JavaBE.ini.   I am not positive which version of SAPCommon introduced support for JCO 3 but believe you need this setting in order for the JCO 3 to work.  Otherwise if the SAPCommon is based on JCO2 you will need to have the correct sapjco.jar for JCO2.x in your classpath instead.

Also the Appname item should not be quoted.  See my example below.

--Bill

[HOST]
server=hostname-here
;  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_61

[JCO]
CLASS=JCO3

[Former Member · Accepted solution]

Hello Bill,

thank you for the hint with the jco3 version. We use now the sapjco.jar from jco2 and now it works fine.

In JCO3 there was a error that a class could not be found. And so we changed to JCO2.

Thanx,

André

[Former Member]

Hello André Nehm , As bill said follow the steps and can you execute your agentry server ? Once you run your server you could see that you have successfully connected to backend if not then it will throw error. Thanks & Regards, Kunal Varaiya