Syclo : Error in connecting Work Manager Client with Agentry Server

Question

Hi,
Can somebody please shed some light on work manager client-server connections? I have downloaded the "SAP_WORK_MANAGER_BY_SYCLO_5.2" package from market place and set up the Work Manager server. It can successfully connect to the SAP back-end. Environment variables are correctly set too. However, I'm failing to connect to the Work Manager server from the Work Manager clients. I have tried from the Win32 & Android clients both.
For Win32 client, the error I'm getting is:
For Android, I can't even see the server instance, although it's running (it shows up while attempting to connect from Win32). Error:
When I attempt to connect from Work Manager client to the server, it asks for username/password and for Android client it asks for Agentry user id and password. Aren't these username/password of the server where my Work Manager (Agentry) server is installed?
Also, the "Agentry Development Server" which has been set to run as a service runs with Administrative privileges.
I followed this: http://wiki.scn.sap.com/wiki/display/SAPMOB/Agentry+error+Client+Receiving+RFC+ERROR+LOGON+FAILURE+incomplete+logon+Data+when+connecting+to+server
It didn't help. Please let me know where I'm going wrong?
Tags edited by: Michael Appleby

Answer 1

Hi Michael,
I can login to SAP backend using the credentials mentioned in JavaBE.ini file.
Please take a look at the JavaBE.ini:
[HOST]
server=<SAP server host name>
;  mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10...etc
APPNAME=SMART_WORK_MANAGER_52
[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=<SAP backend username>
UPASSWORD=<SAP backend password>
UPASSWORDENCODED=false
SERVERSERIALNUM=AVKNN@NILKGGBTLD
[PUSH_LOGON]
ENABLED=false
UID=
UPASSWORD=
UPASSWORDENCODED=false
SHAREDCONNECTION=10
[CLIENT_NUM]
CLIENT=720
;CLIENT=010
[SYSTEM_NUM]
;SYSNUM=33
SYSNUM=00
[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
LOGON_METHOD=USER_AUTH
[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
;  host name or IP address of SAP Message Server
MESSAGE_SERVER=
GROUP_NAME=
SYSTEM_ID=
CLIENT=
[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
I haven't yet installed ATE and tested out any application. I just want my connections to be perfect, first.
I have a question. Are the credentials used to connect Work Manager client to the server, same as the SAP backend credentials or are they the credentials of the host on which the Work Manager server is installed?
I have tried logging in using the SAP credentials also. But that results in error too.
These credentials are valid for SAP backend and successfully logs onto it and also responds correctly to connectTest.bat. However, I think this error is logical because these are the credentials for SAP backend and not the server where Work Manager server is hosted.