Syclo Work Manager 6.1 Deployment Issues

Hi Experts,
I am trying to Setup Syclo WM 6.1 have issues issues during the setup. I was following the Installation guide from SAP, found a clean and a neat blog from http://scn.sap.com/docs/DOC-56329#comment-506689. I am stuck at an error during deployment of the zip file to SMP 3.0 server as follows:
Can anyone suggest what could be the reason for this?
Søren Hansen hope you can help us. I have other issue which is reported on Syclo Work Manager 6.1 + SAP Connection Issue
Regards,
Nagesh
Tags edited by: Michael Appleby

Your error states that something is null.
You may go inside the SAPCommon-133461.jar library under your Java folder -> com.syclo.sap.connectTest.class and decompile it using your favorite Java decompiler.
~~~~~from the code~~~~~~~
you will see something like:
_connection.openCustomConnection(clientNum, _userName, _password, "EN", host, sysNum, 1);
~~~~~end~~~~~~~~~~~~~~~
From the list above, it takes the data from your javaBE.ini for username, password, host and sysNum and hardcoding the "English - EN". Most likely the host might be the one at fault from your picture above. It does not know what your host name is under your JavaBE.ini. It is blank hence it does not know where to connect. May want to try making things Unencoded but you need to study the Java code by de-compiling it so you may know the rules.
Make sure you are also running the connectTest under the Configuration folder of your SMP 3.0. From your picture above: C:\SAP\WM610\..\configuration\com.sap.mobile.platform.server..\javaBE.ini <-- wondering if this is under your SMP 3.0 install configuration folder.
Hope this helps.
Regards,
Mark Pe
SAP Senior Support Engineer

Similar Messages

Syclo Work Manager 6.1 + SAP Connection Issue

Hello,
I have been trying to setup Syclo Work Manger 6.1 and testing the connection between Work Manager and SAP ERP System.
I have updated the connectTest.bat with the ERP login details uder test_user, I get an "caught exception null" and the test is not successful.
I get the following error:
I have my SMP3 and WM installed in the following path:
Any suggestions to get this tested successfully.
Regards,
Nagesh

Your error states that something is null.
You may go inside the SAPCommon-133461.jar library under your Java folder -> com.syclo.sap.connectTest.class and decompile it using your favorite Java decompiler.
~~~~~from the code~~~~~~~
you will see something like:
_connection.openCustomConnection(clientNum, _userName, _password, "EN", host, sysNum, 1);
~~~~~end~~~~~~~~~~~~~~~
From the list above, it takes the data from your javaBE.ini for username, password, host and sysNum and hardcoding the "English - EN". Most likely the host might be the one at fault from your picture above. It does not know what your host name is under your JavaBE.ini. It is blank hence it does not know where to connect. May want to try making things Unencoded but you need to study the Java code by de-compiling it so you may know the rules.
Make sure you are also running the connectTest under the Configuration folder of your SMP 3.0. From your picture above: C:\SAP\WM610\..\configuration\com.sap.mobile.platform.server..\javaBE.ini <-- wondering if this is under your SMP 3.0 install configuration folder.
Hope this helps.
Regards,
Mark Pe
SAP Senior Support Engineer

SAP SYCLO Work Manager 6.1 Blueprint

Hi Friends,
I am new to syclo, going to implement syclo agentry wm 6.1 for our client in coming days.
can anybody give me the tips to create business blueprint template on sap syclo agentry work manager 6.1.
Tips on requirement gathering also appreciate.
Thanks
Rag
Tags edited by: Michael Appleby

Looks at some documents posted in http://scn.sap.com/docs/DOC-55878
and http://scn.sap.com/docs/DOC-54054 related to methodology and process for Agentry mobile application development .
Thanks
Manju

SAP Work Manager 6.1 deployment on SMP

Hi
I am facing this issue while publishing the Agentry app in SMP. I am not getting the successful message after browsing the Zip file as mentioned in the Step 8 according to this blog SMP 3.0: Custom development of SAP Work Manager 6.1 on Agentry Server. Please suggest.
Thanks
Sarika

Hi Sarika
Is this still an issue ?
I am thinking that this could be a permission issue. Do you have local Admin permissions on your PC ?
I remember I had some issues, and changed the service "SAPSMP3Service" to use "Local System Account".
I can't remember the details though.
Søren Hansen

Syclo Work Manager 6.0

Good afternoon,
us are actually implementing WM 6 according to the guide, but when we want to upload a file that is not sent to ERP. We should check?. We already checked the values of BDS (Business Document Service) / GOS (Generic Object Services), DMS (Document Management System) according to the guide.
A part of this problem we observed an error("error code: -1 se ha producido un error de red. file:///data/data/com,syclo.sap.SAPWorkMgr.cliente.android/files/aplication%20Directory/img") in the client device when we want to see the file to be attached
Tags edited by: Michael Appleby

Features:
Tablet: Huawei MediaPad
Android Version: 4.0.3
What type of client are you using?: WorkManager 6.0 for tablet.
What is the Agentry version of the clients? Agentry 6.0 + SMP 2.3
What type of files are you trying to upload? jpg, doc, pdf.
Thanks

Syclo Work Manager 6.1 SSL Configurations

Hello Experts,
We have an "Communicaiton Error 14" on Device and ATE. I have worked on WM 5.2 and 6.0 and aware of the SSL configurations. I have Generated a Self Signed Certificate and a PFX file using OpenSSL. Now, with SMP 3.0 SP03 we are not able to find how to configure the Agentry.ini and where to copy the .sst file.
Can someone help us understand on how to make this work??? Is there a workaround for HTTP communication without SSL and any document on this which can help.
Is SSL/pfx mandatory to have in 6.1 while testing with ATE?
Regards,
Sarika

Hi Stephen,
Yes, I have to change the FDQN name to IP to work with Management console, only I will get logon screen. Similarly I have tried to do the same in ATE & WPF client.
in Management Console, while have FDQN in URL,
https://jilan.wirelessap:8083/Admin/
the error is below. But when I change to IP it works.
This page can't be displayed
Make sure the web address https://jilan.wirelessap:8083 is correct.
Look for the page with your search engine.
Refresh the page in a few minutes.
Make sure TLS and SSL protocols are enabled. Go to Tools > Internet Options > Advanced > Settings > Security
Similarly, in WPF/ATE, if FDQN is in URL, I get the Communication Error(14).
Requesting Public Key from Server
Communications error (14)
Connection failed
Ending transmission
Is any mapping needed in my laptop between FDQN to IP address?
Thanks,
Jilan

Work Manager 6.1 problem with push

Dear community,
We're developing / configuring a Work Manager 6.1 application which communicates with an SMP 3.0 SP 4.
We want to set up push for work orders as well as attachments on work orders.
In the application definitions:
push is enabled on both the Angel and the Angel Lite connection
push definitions for BDSDocumentsPush, DMSDocumentsPush and WorkOrdersPush are polling enabled, currently with a 1 minute interval (for testing purposes)
In configpanel:
Push scenario's are configured
For work order, the exchange object configuration is present
In outbound trigger configuration, the server name, IP address and port are filled. The port is the same as the one configured in the SMP Admin console.
In the mobile object data configuration the push objects (SWM61_BDS_DOCUMENT_PUSH, SWM61_DMS_DOCUMENT_PUSH, SWM61_WORKORDER_PUSH) have "push enabled" checked.
We can observe that the push notifications are getting generated on the backend, because I can see them in the push instance monitor:
For attachments:
For an urgent work order:
For attachments, the status is process with current status new until the moment that you perform a synchronize on the agentry client, however long you wait. After the synchronize is finished, it gets the status completed with current status cancelled.
For work orders, it just gets the status completed, with 0 total recipients, even though I am connected in the agentry client at that time.
In user monitor, I saw that there were no active connections for my user:
But in SMP admin console (around the same time):
Other observations: when I run /SYCLO/CORE_OTRIG_RETRY_PROG on backend server, it only finds outbound triggers for those with status "process", not those with status "completed".
I have also looked at the troubleshooting document: http://scn.sap.com/community/mobile/blog/2014/03/25/troubleshooting-sap-work-manager-60-attach-document-issue, but we are already on SMERP 610_700 SP4.
I could also not find any errors in the SMP server log.
Any advice, additional things I can check, ... are highly appreciated as I currently don't know where to look anymore.
Best regards,
Annelies

Hello,
Yes, the user has the necessary permissions. And now I am sure that the port is open.
I continued testing and now attachments are received via push, but work order pushes still don't come through. I can see them in the monitor, but they always have 0 recipients, even while I am connected. Any suggestions for that?
Kind regards,
Annelies

Work Manager 6.1: Uploading pictures or documents error

Hi,
I'm working with SMP 3.0 and Work Manager 6.1 for Android platform
I'm trying to attach a picture and/or a document to a Work Order and to a Notification, but when I start the transmit the following error is displayed in the client:
Sending Document Link Picture Add For Work Order...
Unexpected disconnection from server (11)
'Angel' connection failed
I tried to debug the Java but it didn't reach any break point or "catch", I also checked the SMP 3.0 Agentry logs and there is nothing.
I went through the installation notes and documents and I haven't been able to find out if I missed some configuration. I also checked this nice blog http://scn.sap.com/community/mobile/blog/2014/03/25/troubleshooting-sap-work-manager-60-attach-document-issue with no luck.
Can you help me with this?
Thank you in advance
Tags edited by: Michael Appleby

Short update for this issue. I created a SAP incident regarding it.
It's only failing when attaching pictures in Android (iOS works fine), and it seems due a platform bug documented here: http://code.google.com/p/android/issues/detail?id=17535
But since WM 6.1 is supported for Android 4.0 or higher, I expect some help from SAP if the cause is what I think.

How to configure the work manager java code to eclipse?

Hello all,
               I am working with the syclo work manager app. I have successfully installed all components required.
               I imported the work manager mobile application and I want to import the standard work manager java code, what is the process to import java code into work space.
               Guide me with some screen shots.
               When I try to start the WM server it is giving me the following error:
How to resolve the error.
Please anyone provide me complete setup needed to run the work manager app smoothly.
Please guide me.
Thanks & Regards,
Swaroopa.

Swaroopa,
That error is telling you the SAP JCo library cannot find one of the needed DLLs on the system. The sapjco.jar loads two additional DLL files (sapjcorfc.dll and librfc32.dll). Both should be installed by default into your ServerDev directory (assuming you are running Agentry 6.0.x).
I would guess it is having trouble loading the librfc32.dll based on the message but confirm both are in the correct location.
--Bill

SAP Work Manager customization - adding a new field to equipment details screen (Syclo Agentry)

Hi Experts,
I am trying to add a field (NAME1) on the Equipment details screen under work orders in work manager 5.3 application.
I have performed the following steps, but I am getting an error while connecting to the application.
1) Create extension for Equipment class to add a new field.
2) added the new field (Name1) as the property to the standard object Equipment.
3) Added the field on the screen.
4) Added the field (name1) to the complex table ctEquipment.
5) Added the JAR file to Agentry.ini file.
6) Changed the Class mapping for parameter "Equipment" under group "SAPOBJECT" to point it to the custom (Extended) class.
7) Changed the class mapping for complex table parameter "ctEquipment" under group "CT_SAPOBJECT" to point it to the custom class.
8) after publishing the changes and re-starting the server, I get following error.
the log file generated (message.log) also has the same description.
What am I missing here? Any help would be really appreciated.

Hi Emanuel,
Thanks for looking into this issue.
I have performed the following steps as suggested by you, still it doesn't seem to work and gives the same error.
Below are the changes done on the ECC Side.
1) Copied the standard equipment class /SYCLO_CL_PM_EQUIPMENT1_DO to custom class ZSYCLO_CL_PM_EQUIPMENT1_DO. Changes made in the GET Method to get custom equipment related data
2) Modified the standard equipment structure /SYCLO/PM_EQUI_STR by adding one custom field
3) Configured this custom class as the object handler in the equipment mobile data object
4) Configured this custom class as the object handler for the equipment complex table
5) We are still using the standard BAPI Wrapper itself for getting the equipment data and the added field is reflected in the BAPI Wrapper table parameter
Is there something we are missing?

On Demand attachment download issue in SAP Work Manager 6.0

We are using SAP Work Manager 6.0 app with SMP 2.3. System is configured to download attachments for external DMS using this document http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90087094-ddad-3110-cdab-e6dbc1a12e45?QuickLink=index&overridelayout=true&59236188953046
While we tried to download the attachment, the download request was sent to SAP
We checked through Push Instance monitor in Syclo Admin panel, a push request was there for scenario ID SM60_DMS_DOCUMENT_PUSH with status PROCESS. Status was set to NEW under Subscriber view tab of this push request.
We checked following things:
1. Push was enabled for Agentry Server in JavaBE.ini
2. Port 8282 was maintained in outbound trigger settings & in Agentry.ini configurations. This port is only used by Agentry Server.
3. SCC displays the error for the WorkManager application as XFailedToSendResponse: 9,1,16, smp_mobile
Regards,
Sahil Dudeja
Tags edited by: Michael Appleby

We are still facing this issue.

Book For SAP SYCLO Agentry Work Manager 6.0

Hi Expert's,
Can any one suggest me the book for SAP SYCLO Agentry Work Manager 6.0 , Which covers End-To-End Implementation methodology?
Answer appreciates.
Thanks
Rag
Tags edited by: Michael Appleby

Moved to SAP for Mobile. Application related, not SMP.
Regards, Mike (Moderator)
SAP Customer Experience Group - CEG

SMP 3.0 - Deploying Work Manager 6.1 - Production Landscape

Hi All,
From this blog, I understood how to deploy a development version of Work Manager application on the SMP Development Server.
http://scn.sap.com/docs/DOC-56329
What is the main difference when deploying to a SMP Production Server?
Just copying the Production folder instead of Development folder while creating the archive to deploy on the SMP Server?
Kindly help. And please point to any other useful blogs which have similar information like this.
Regards
Ankur
Tags edited by: Michael Appleby

Ankur,
Deploying to production involves creating a zip file and deploying the zip file to the SMP server through the Management Cockpit..
The Work Manager documentation should also cover the steps needed to deploy the production version to the server as well.
--Bill

Syclo : Error in connecting Work Manager Client with Agentry Server

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

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.

Notification Assignment Type Issue - SAP Work Manager 6.0

Hello Experts,
We are not able to download notifications on the device for header level work center that is assignment type = 5.
We have done the below configuration.
- added the user parameter for work center in user profile.
- changed assignment type to 5 in Notification MDO.
Same configuration is working properly in case of work orders only change is assignment type set to 8 and changed in client global value Wo.AssignmentType to 8.
There is no configuration guide available which explains notification assignment types in SAP Work Manager 6.0.
Any help would be appreciated.
Regards,
Abhishek
Tags edited by: Michael Appleby

Hi,
In the notification MDO data filter, you also need to add a filter to the WORK_CNTR field. It should be user parameter type, with value "VAP".
Also, from memory, I had to disable some other filters that were set out of the box. These were filtering out my data.
Hope that helps
Michael

Syclo Work Manager 6.1 Deployment Issues

Similar Messages

Maybe you are looking for