on 06-16-2014 5:38 PM
Hello Experts,
I follow the flightbooking tutorial to create a Material application to get material list. I can start the agentry server but when I connect to SAP server and get data, I face below issue
Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER
I check the parameters name in SAP Agentry Config panel, all are correct. Why cannt it get the data. Do I have to add anything in javaBE.ini? Please help me. Thank you very much.
My javaBE
[HOST]
server=be1.vdc.csc.com
APPNAME=ZCH_MATERIALLIST
[CLIENT_NUM]
CLIENT=800
[SYSTEM_NUM]
SYSNUM=01
[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=0
GET_PERSONNEL_INFO=
[SERVICE_LOGON]
ENABLED=true
UID=hngu3
UPASSWORD=xxxxxxx
UPASSWORDENCODED=false
[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=
[LANGUAGE]
LANG=EN
[LOGGING]
Level=4
[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
Hi PH,
It seems that Agentry server cannot access to BAPI name that you provided in admin panel. Make sure you have provided exactly same package name in your java class and in BAPI_WRAPPER.
Tahir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
nothing to do with javaBE.ini.
All you need to double check is,
1. Java class name, it is case-sensitive
2. BAPI name, with package name
3. Make sure your BAPI is ACTIVE.
4. The config is active (I can see it is active in the image)
80% of errors like this comes from these reasons.
Let me know if it fixes
I checked and found another problem.
The Agentry test environment always show the error on com.syclo.sap.material.bapi.materialbapi regardless of the bapi Java class name I put into the config panel.
For example, If I change the bapi class name into com.syclo.sap.material.bapi.Material, it still shows the error on com.syclo.sap.material.bapi.materialbapi.
I dont know why. Please help.
Thanks Kevin Hu
1. Java class name, it is case-sensitive
My java bapi class name is com.syclo.sap.material.bapi.MaterialBapi, the config name in config panel is also com.syclo.sap.material.bapi.materialbapi. I dont know why it always shows com.syclo.sap.material.bapi.materialbapi on error log.
2. BAPI name, with package name
The BaPi name is correct.
3. Make sure your BAPI is ACTIVE.
yes, it is active already
Hi Tahir, please help me check the log below
Agentry Runtime Worker Thread###throwExceptionToClient::begin |
Agentry Runtime Worker Thread###throwExceptionToClient::com.syclo.sap.material.steplet.MaterialSteplet::throwExceptionToClient::397::MaterialSteplet - Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER |
Agentry Runtime Worker Thread###Exception: 17:15:35 06/17/2014 : 20 (Agentry3), Java Business Logic Error (com.syclo.agentry.BusinessLogicException: MaterialSteplet - Error in getting the BAPIWrapper name from the ini file or SAP mobile configuration. Please check the ini file or the mobile configuration for the bapi key (com.syclo.sap.material.bapi.materialbapi) either in sections BAPI_WRAPPER or REQUIRED_BAPI_WRAPPER), |
Agentry Runtime Worker Thread###loggedOut::begin |
Agentry Runtime Worker Thread###HNGU3: SESSION END |
Agentry Runtime Worker Thread###BAPI::begin |
Agentry Runtime Worker Thread###create::nulled repository::created new repository |
Agentry Runtime Worker Thread###create::/SYCLO/CORE_MDW_SESSION1_DEL Connection ID: com.sap.mw.jco.JCO$Client@2656ed99 |
Agentry Runtime Worker Thread###create::Function /SYCLO/CORE_MDW_SESSION1_DEL created |
User | Count |
---|---|
78 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.