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

Similar Messages

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

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

Using work manager for third party connections

Folks we are trying implement work manager to
Allthough WL is self tuning, and you could "increase the internal socket pool", you have to fully understand the implications of this.
-It increases the # of threads, which ultimately degrades performance, due to the amount of context switching which would have to occur (this is at the application layer)... in general
-It will require additional memory, of which, we'd need to account for this, otherwise, it can run the WL instance out of memory, if we're in a fault condition
Let me explain this "fault" condition a little further...
There's a BIG difference between a 3rd party being down, and a 3rd party being able to respond to our request, but unable to process it in a timely fashion (i.e. they're overloaded, or the tcp connection is happening properly, but the application response from the 3rd party isn't properly responding/working in a timely fashion). We've seen this condition on a # of occasions and need to be able to have a max limit or governor on each 3rd party... of which, my understanding of WL work managers allows for this (I do have to note, I am not experienced with these, and my knowledge is only with what I've had time to read on). Ultimately, I'm trying to prevent the condition I've seen in a # of serious "slow downs" or hang-ups within the application... we should NOT be able to have 3rd party calls hamper the performance or availability of our application

Note that you can reduce the context switching by 'pinning' certain CPUs to handle, for example, the network interrupts.
You can use (on Linux): cat /proc/interrupts (shows information related to hard interrupts).
From http://middlewaremagic.com/weblogic/?p=8133
"In a multi-processor environment, interrupts are handled by each processor. Two principles have proven to be most efficient when it comes to interrupt handling:
Bind processes that cause a significant amount of interrupts to a CPU. CPU affinity enables the system administrator to bind interrupts to a group or a single physical processor (of course, this does not apply on a single CPU system). To change the affinity of any given IRQ, go into /proc/irq/<number of respective irq>/ and change the CPU mask stored in the file smp_affinity. To set the affinity of IRQ 19 (which in the above example is the network interface card) to the first CPU, we can use echo 2 > /proc/irq/19/smp_affinity."
To configure a work manager properly, you have to throttle the maximum threads and the capacity. The maximum number of threads are the number of threads
that are allowed to run simultaneously. Usually, you set this equal to some resource (such as the number of connections in a data source). This to prevent
contention for that resource (otherwise the thread would be waiting for the resource and thus consuming CPU cycles by polling if can go or not). When the maximum
is reached no other threads are spawned to run. The request that comes in is put into a piece of work and stays that way until an execute thread comes available
to process that work. The number of work instances you allow in your heap can be set by the capacity constraint (which thus throttles the memory consumption).
When the capacity is reached, new requests are rejected.

Nexus 7010 Management interface (Mgmt 0) connectivity issue via OOB switch

Hi Team,
We have setup as follows:
   [Nexus1]-----[Nexus2]
         |               |
     [===SW-OOB===] --------------[5k] --[5k]
(172.16.1.254 - IP address on OOB switch L3 VLAN)
Nexus 1 has three VDC :
   1. Default VDC, 2. Network VDC, 3. Common Srvices VDC
Similarly it is for Nexus 2 as well.
While we create VDC, by default Mgmt0 interface get added along with the vrf management.
in Default VDC and Network VDC, we have configured default gateway on VRF Management as 172.16.1.254 and ip address as 172.16.1.1 and 172.16.1.2 in each vdc on interface mgmt0. It is working fine.
But when i configure in Common Services VDC 172.16.1.3 on mgmt0 and default gateway as 172.16.1.254, i am unable to reach to OOB switch.
Is there any limitation on the nexus switch or some thing i am missing to configure. since there should not be a cable issue as these mgmt0 interface are logical in the VDC.
The same issue i am facing on both the nexus.
Also attached the show version of nexus for ref.
Please help in this case and as i find this is the abnormal behaviour.
I am facing issue only with these two nexus rest is working fine in accross campus.
Regards
Amit Marathe

Hi,
where your gateway resides?
can you try to connect with a PC on management VLAN and try to ping both WLC management and the gateway of the subnet?
I am suspecting the traffic is blocked somewhere. We need to isolate.
The WiSM look up and fine from the 6509 box. Service VLAN look find as well as the management.
Have you made any troubleshooting since posting this discussion?

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

Service Manager Data Ware House Connection Issue

We have 3 virtual server for SCSM. The scenario of SCSM server are in below.
SCSM management server, Console and Management Server SQL database.
SCSM data Ware House Server, reporting server and data ware house & repporting SQl database.
SharePoint server, SCSM web server and SharePoint server SQL database.
Only SharePoint SQL server running on SQL Server 2008 and the other SQL server's are running on SQL 2012. Previously data warehouse connectivity was fine. But recently data warehouse connection is not working. When I try to unregister the data source connection
in showing error. I try to check the data source by powershell Get-SCDWSource, but it not showing any source. How can we unregister and re-register datasource also with dataware house connection.
Mithun Dey Web: http://cloudmithun.wordpress.com If this may give your necessary resolution please mark it as Answre.

I've 2-3 error.
IN SCSM Management Server
Event ID: 34152
The description for Event ID 34152 from source Data Connectors cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Domain Connector
Error resolving user with domain PRIMEBANK and name as040121. Exception: System.DirectoryServices.DirectoryServicesCOMException (0x8007052E): The user name or password is incorrect.
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.PropertyValueCollection.PopulateList()
at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
at System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer()
at System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit()
at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize()
at System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx()
at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(PrincipalContext context, Type principalType, Nullable`1 identityType, String identityValue, DateTime refDate)
at System.DirectoryServices.AccountManagement.UserPrincipal.FindByIdentity(PrincipalContext context, String identityValue)
at Microsoft.EnterpriseManagement.ServiceManager.Sdk.Connectors.Lfx.Workflows.ADGroupExpander.MarkDeletions()
In DATAWAREHOUSE
Event ID: 33519
The description for Event ID 33519 from source Data Warehouse cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
bd773a44-6c16-1ad9-fe59-344395587b6d
ServiceManager.ServiceCatalog.Cubes.Library
7.5.2905.0
SM Management Group
Either the MP has failed deployment Or any of its references has failed deployment
Mithun Dey Web: http://cloudmithun.wordpress.com If this may give your necessary resolution please mark it as Answre.

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

Work Manager 6.1 Sizing Guide Query

Hi,
Looking at the official Work Manager 6.1 sizing guide and comparing it to the Work Manager 6.0 guide and it seems there has been a large jump in the suggested hardware for SMP.
I understand the WM6.0 runs on SMP 2.3 and WM6.1 is on SMP 3.0, but I'm surprised that the difference seems so large.
E.g. For a medium landscape with 1000 syncs/hour:
Work Manager / SMP
SMP SAPS (suggested)
Work Manager 6.0
2,000
Work Manager 6.1
55,500
Could someone clarify why this would be?
Thanks,
Stephen

The Sizing Document has been updated for the SMP Server and appear to be much more reasonable.
The SAP ABAP & DB Server recommondations are still the same and don't seem right.
E.g
Large Data Volume & 2000 syncs/hr
SAP DB Server - 393,500 SAPS
SAP ABAP Server - 127,500 SAPS
From the Sizing benchmarks an IBM Server with 271,080 SAPS has 8 Processors / 120 Cores / 1TB of RAM
Cheers,
Stephen

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.

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.

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

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 + SAP Connection Issue

Similar Messages

Maybe you are looking for