Work Manager 6.1.0.4 configuration

Hi all,
currently Im trying to create connection from a iphone (work manager app installed) to an SAP Backend. Everything is set up and running (agentry server). Everytime i want to reach the server i get the next error message:
(On my iPhone)
Requesting Public Key from Server
SSL Invalid Chain
Communications error (14)
Connection failed
Ending transmission
(On backend log)
error:2006F067:BIO routines:BIO_read:connect error, ..\Socket\openSSLsockets.cpp#893:OpenSSLstreamSocket::SSLStreamSocket::checkSSLerror
Please can someone help me with this?
Thank you!

The error you are seeing indicates that the certificate presented by the Agentry server to the client (iPhone) is not trusted or the name on the certificate does not match the server name entered on the Agentry Client.
If you generate your own certificate for the Agentry server you will need to install the root CA certificate used to sign it as a trusted authority on the iPhone. I usually just email the root certificate file to myself and open it from the mail app on the phone to install.
Secondly even if the root CA is trusted, the name you enter when connecting the first time must match the name on the certificate. For example if the certificate is generated for myserver.mydomain.com but when I enter the server infomration on the iPhone I only enter myserver as the name even though the netowrk will properly route the connection to the server using only the hostname I will still get an error since what I entered doesn't match what is on the certificate. I believe you will get a different error message but it is still a key thing to consider.
--Bill

Similar Messages

Work manager configuration

All,
I'm prototyping work manager configuration for our app under WLS 9.2.
I think I want 2 work managers: one for async batch-type operations and one for sync operations. The async work involves making parallel calls and not necessarily waiting for a response. The sync work involve parallel calls and waiting for a response (such as a web service request resulting in 2 parallel backend calls.) Mainly I don't want to allow the async operations to hog the resources and cause slow responses or timeouts for the users. At the same time, however, I don't want to articifically handicap the async processing during periods of low sync load. If I create 2 fairshare work managers with a 50% share each, during the night when users are not submitting sync requests, will the async batch work manager be allowed to scale up?
A long time ago I wrote a parallel processing facade that used a single JMS queue to achieve paralelism. I quickly learned the hard way that if you have parallel calls that call back into the framework (that is, thread A spawns thread B and C and waits for replies and thread B spawns thread D and E and waits for replies,) then you can wind up blocked forever because A can't complete without B, but B can't complete without D, but D can't run because A and B are hogging all the threads. Is this a risk with the WLS work manager? It seems that as long as I don't cap the thread count, then it might be sufficient to have just 1 big pool. My concern is what will happen when WLS decides not to spawn any more threads and instead just queues up incoming work?
thanks

First Part:
If you are setting the fairshare to 50 % then the server will split the requests equally between the sync and async apps during a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads.In this case the thread pool is equally utilized by each app.
Now, during the night time the sync WM is not working and this will free the thread pool for the async WM alone. The async work manager will utilize the whole thread pool and hence will scale up.
Second part:
Correct me if I'm wrong, I don't think there is a point where WLS will decide not to spawn a new thread. Spawning threads is a continuous process until the server goes down. The self-tuning thread pool would also adjust its pool size automatically based on the throughput history that WLS gathers.
You will have to kill the stuck threads to free up the pool or setup a max thread constraint and allow only a limited number threads to execute requests. I think you would also need to setup a capacity constraint to reject all the requests that are queued up for work.

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?

How to publish Work Manager 6.0 on SMP3.0 ?

Hi SCN Community,
I'm trying to get the Work Manager 6.0 running on SMP 3.0 (running on Linux). Currently the events.log within the Agentry folder states, that the Agentry Server was started. But If I look into the Threads*.log I see there might be a problem and I'm also not able to connect to the server.
Unfortunately I couldn't find any manual or post where someone described the steps to get a work manager running on SMP 3.0. The SMP 3.0 server manual as well as the SDK manual just describing in general how to publish an application to the SMP 3.0. But for Work Manager, there might be some special things to be done ...
Any help/hints are welcome!
Here what I did so far:
Install SMP 3.0 up to SP02 on Suse SLES 11
Install SAP JCo 2.1.11 (test successful: java -jar /DVD_HANA/jco/sapjco.jar -stdout )
Create a new application in SMP with type Agentry and select security profile default
Install SMP3.0 SDK SP02 (Agentry)
Setup Eclispe 4.2.2 with Agentry Plugin 7.0.2
Import a Work Manager 6.0 from Teamshare
Export Agentry Project as a production version and point to the Agentry.ini which is in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application
Include all jar files to the ZIP file
Import the ZIP file within Agentry application in SMP 3.0
Create JavaBE.ini in folder /opt/SAP/MobilePlatform3/Server which is copied from WM6.0 server
Adjust Agentry.ini in folder /opt/SAP/MobilePlatform3/Server/configuration/com.sap.mobile.platform.server.agentry.application (see section config files)
Restart Server
Config files:
Agentry.ini
[Server Administration]
authenticationCertificateStore=AgentryServer.pfx
authenticationCertificateStorePassword=Rzdrj~SwixoAqzmbVxgi
authenticationCertificateStorePasswordEncoded=true
[System Connections]
2=ag3httpxmlbe.dll
1=ag3javabe.dll
[Configuration]
apnsCertificateDirectory=apnsCertificates
apnsCertificatePassword=Rzdrj~SwixoAqzmbVxgi
apnsCertificatePasswordEncoded=True
apnsEnabled=True
applicationGlobalsFile=Globals.ini
applicationStringsFile=ApplicationText.ini
clientStringNamesFile=ClientStringNames.ini
clientStringsFile=ClientText.ini
developmentServer=False
enableFailedTransactionLogging=True
enableOverrideFile=Enables.ini
enableTransactionFailureHandling=False
failedTransactionFilenameFormat=%{userid} %{transaction_name} %{date} %{time}-%{count}.xml
failedTransactionsQueue=FailedTransactionsQueue
gcmEnabled=True
gcmServerAuthorizationKey=Authorization:key=AIzaSyDi0qWQEewdbmNSV_o9QNtSQrlxPnBXtBM
gcmServerLink=https://android.googleapis.com/gcm/send
imagesPath=Application\Development\Images
localizationPath=
localizations=
overrideInfoTableDirectory=OverrideInfoTable
overrideTypesFile=OverrideTypes.ini
postedTransactionDirectory=posted
postedTransactionFile=%{device}.pli
scriptsPath=Application\Development\Scripts
spinDocIniFile=
threadCount=0
transmitConfigurationFile=TransmitConfigurations.ini
trustedCertificateStore=
updateIdleWait=60
updatePeriod=60
urlPath=
[HTTPXML-2]
authenticationCertificateStore=MY
authenticationCertificateStorePassword=
authenticationCertificateStorePasswordEncoded=False
autoDequote=True
baseURL=http://localhost:8282
basicAuthenticationPassword=
basicAuthenticationPasswordEncoded=False
basicAuthenticationUserID=
constantsFile=httpxml_sd.ini
enableAuthentication=False
enablePreviousUserAuthentication=False
httpConnectTimeout=60
httpReceiveTimeout=300
httpResolveTimeout=60
httpSendTimeout=300
listenOn=
name=2
timeZoneName=
timeout=300
trustedCertificateStore=
useSSL=False
xmlNamespaces=
[Java-1]
classPath=./ini4j.jar;./Agentry-v5.jar;./Z_SAPWM-6.0.0.0.jar;./SAPWM-6.0.0.0.jar;./SAPCommon-130881.jar;
constantsFile=
deleteSource=True
enableAuthentication=True
enablePreviousUserAuthentication=True
name=Java-1
outputDirectory=.
performCompile=True
printBusinessLogicStackTrace=False
printStackTrace=False
scriptsPath=
serverClass=com.syclo.agentry.Server
sourceDirectory=.
timeZoneName=
[SpinDoc]
facePath=sql\custom;sql
facepath=sql\custom;sql
[TimeZoneAlias]
Log files:
events.log
02/27/2014 18:51:45, 0,         0,         0, Thr 140352349296384, New files opened events.log, messages.log
02/27/2014 18:51:45, 0,         0,         2, Thr 140352349296384, Agentry Startup
02/27/2014 18:51:45, 0,        17,        14, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:51:45, 0,         1,         4, Thr 140352349296384, Agentry v7.0.2.151
02/27/2014 18:51:45, 0,        20,       150, Thr 140352200132352, Loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:51:45, 0,        20,       152, Thr 140352200132352, Loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       153, Thr 140352200132352, Finished loading Production application definitions for default localization
02/27/2014 18:52:07, 0,        20,       151, Thr 140352200132352, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
02/27/2014 18:52:08, 0,        24,         4, Thr 140352349296384, Loaded 2 (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/27/2014 18:52:08, 0,        23,         4, Thr 140352349296384, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/27/2014 18:52:08, 0,        20,         4, Thr 140352349296384, Server v7.0.2.151
02/27/2014 18:52:08, 0,        17,        10, Thr 140352349296384, WebSockets Front End v7.0.2.151
02/27/2014 18:52:08, 0,         0,         0, Thr 140352349296384, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-27-185145
02/27/2014 18:52:08, 0,         0,        23, Thr 140352349296384, Agentry startup is complete.
Thread-140352200132352.log
2014/02/27 18:52:07.310: Opening log file
2014/02/27 18:52:07.310: + Thread=140352200132352
2014/02/27 18:52:07.310:   + Server=Agentry
2014/02/27 18:52:07.310:     + Load Loop=Production
2014/02/27 18:52:07.310:       + AppIniFile=SAPWM-v1-0-0-app
2014/02/27 18:52:07.310:         + Module=PM
2014/02/27 18:52:07.310:           + Service Event=WorkOrderPushHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkOrderPushHTTPListener'
2014/02/27 18:52:07.310:           + Service Event=WorkorderPushByOperationHTTPListener
2014/02/27 18:52:07.310:             Failed to load definition for Service Event 'WorkorderPushByOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushBySubOperationHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushBySubOperationHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=BDSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'BDSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=DMSDocumentPushHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'DMSDocumentPushHTTPListener'
2014/02/27 18:52:07.311:           + Service Event=WorkorderPushByMRSHTTPListener
2014/02/27 18:52:07.311:             Failed to load definition for Service Event 'WorkorderPushByMRSHTTPListener'
When trying to connect with the WPF client I get a communication error (14) and nothing is shown in the log files ..
Best Regards,
Michel

Jason,
deleting the service events was helpful regarding the error shown in the Thread log file. After publishing a new version the server seems to start, but has no activity to SAP. I expected at least an initial logon to the SAP system using the service user.
Current log files are:
events.log:
02/28/2014 06:16:36, 0,         0,         0, Thr 140136552040192, New files opened events.log, messages.log
02/28/2014 06:16:36, 0,         0,         2, Thr 140136552040192, Agentry Startup
02/28/2014 06:16:36, 0,        17,        14, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:16:36, 0,         1,         4, Thr 140136552040192, Agentry v7.0.2.151
02/28/2014 06:16:36, 0,        20,       150, Thr 140136413689600, Loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:16:36, 0,        20,       152, Thr 140136413689600, Loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       153, Thr 140136413689600, Finished loading Production application definitions for default localization
02/28/2014 06:17:06, 0,        20,       151, Thr 140136413689600, Finished loading Production application definitions using file "SAPWM-v1-1-0-app"
02/28/2014 06:17:06, 0,        24,         4, Thr 140136552040192, Loaded HTTP-XML Back End (HTTPXML v7.0.2.151) from ag3httpxmlbe.dll
02/28/2014 06:17:06, 0,        23,         4, Thr 140136552040192, Loaded Java-1 (Java v7.0.2.151) from ag3javabe.dll
02/28/2014 06:17:06, 0,        20,         4, Thr 140136552040192, Server v7.0.2.151
02/28/2014 06:17:07, 0,        17,        10, Thr 140136552040192, WebSockets Front End v7.0.2.151
02/28/2014 06:17:07, 0,         0,         0, Thr 140136552040192, Old log files moved into /opt/SAP/MobilePlatform3/Server/log/agentry/rolled/2014-02-28-061636
02/28/2014 06:17:07, 0,         0,        23, Thr 140136552040192, Agentry startup is complete.
messages.log is empty and Thread*.log doesn't exist anymore.
Any further idea how to get this up and running?
Best Regards,
Michel

Work Manager 6.1: java.lang.reflect.InvocationTargetException

Hi all,
Please, I need your help with this issue. I installed Work Manager 6.1 over SMP 3.0.3.
I added a field to complex table ctCatalogGroup. The field was already contemplated on the backend so I only had to add it in Agentry. It worked fine for a while but suddenly it started giving me this error during transmit every time since then:
My Java class looks like this:
And I added the field in Agentry accordingly:
Config Panel parameters for this are:
The first thing I noticed is this error in the SMP log:
2015/04/23 08:29:12.540: + WorkFunction=00000001496AF658
2015/04/23 08:29:12.540: + User=invpos_out30
2015/04/23 08:29:12.540: + Server=Agentry
2015/04/23 08:29:12.540: + Complex Table=ctcatalogprofile
2015/04/23 08:29:12.540: Update BHT 'ctcatalogprofile' for 'User': Client last data update 12:00:01 a.m. 01/01/1900
2015/04/23 08:29:12.540: Update BHT 'ctcatalogprofile' for 'User': Getting back end connections
2015/04/23 08:29:12.540: client last data update=12:00:01 a.m. 01/01/1900
2015/04/23 08:29:12.540: Backend step is configured as a Java Class; using Java class com.syclo.sap.ComplexTable
2015/04/23 08:29:12.540: Using Java Class com.syclo.sap.ComplexTable for ComplexTable
2015/04/23 08:29:12.555: + BackEnd=Java-SAPJavaConnection
2015/04/23 08:29:12.555: Exception while starting complex table update for table 'ctcatalogprofile': JavaBackEndError: JAVA EXCEPTION CAUGHT: java.lang.reflect.InvocationTargetException in AgentryComplexTableFactory::createComplexTable at AgentryComplexTableFactory.cpp:129
As well as this other one in the events.log:
04/23/2015 08:23:32, 0, 20, 16, Thr 9240, Threads in thread pool 'Runtime' expanded to 2. Adding thread 3580
04/23/2015 08:25:13, 1, 29, 1, Thr 3580, java/net/SocketException, java.net.SocketException: Connection reset by peer: socket write errorAngelJavaStreamsConnection.cpp#189:AngelJavaStreamsConnection::handleException
04/23/2015 08:25:13, 1, 4,3221225477, Thr 3580, EXCEPTION_ACCESS_VIOLATION, 000000018000DE02, 0, R, 0000000000000000, ..\agentry\threadManager.cpp#354:ThreadManager::WorkerThread::function
04/23/2015 08:25:27, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: 97E1F7AF-4E38-4ECB-8D3C-2E2D4AFEA2AE
04/23/2015 08:25:56, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: 15FAC37B-A017-46AB-B528-B2B4610423CC
04/23/2015 08:26:27, 0, 0, 6, Thr 7572, invpos_out30: relogin failed at ANGEL: B4A91958-A9A4-46F8-B323-20C61E7E76E8; attempt from ANGEL: BFDB1CBE-12D9-4A66-8EBA-A855B2B90D23
04/23/2015 08:29:12, 1, 20, 18, Thr 3580, JAVA EXCEPTION CAUGHT: java.lang.reflect.InvocationTargetException
I would like to know if anyone faced something like this before or any suggestions on how to dig deeper for a solution. What confuses me is that it worked ok at first and now I can no longer start the client. That is as far as I can get.
Best regards!
Leonardo.

Hi,
Can you modify the step
public void setProperties(Table tbl) throws Exception {
        super.setProperties(tbl);
        setShortText(tbl.getString("KURZTEXT")).trim());
to
public void setProperties(Table tbl) throws Exception {
        super.setProperties(tbl);
        setShortText(tbl.getString("KURZTEXT"));
Thanks & Regards,
Sravanthi

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.

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

Required steps to add standard SAP field to Work Manager 6.0

Dear Agentry experts,
I need some help on how to add standard SAP backend fields to the Work Manager 6.0 application. The application is freshly setup and not yet customized apart from filters, so we are also new to develop it.
Specifically we want to add fields QMTXT and QMCOD from Notification Header. We have checked and the fields are activated in the backend configuration, so I hope there are no changes required to the backend. However, when checking the data in the ATE, the fields are currently not added / available in the Notification Collection.
I have searched this forum and found several pointers, but they deal with adding a full new field, and I want to keep changes limited. Can you please advise what specific steps I need to do on the Agentry / Eclipse side to close the gap between SAP backend and the Notification Collection. (I know how to add the fields to the UI if they are in the collection). Do we need to create custom Java Classes? Can I solve this by just Agentry configuration?
Thank you very much for your kind advice!

Look at the attachment, diagram depicts a data flow across the systems. You have to extend Java code for the object your trying to enhance and plus you have to make necessary changes on Agentry side as well.
if you have access to Service Market place , check out SAP-WM-6.0-EnhancementsGuide.pdf document under Work Manager 6.0 documentation which describes the steps involved in enhancing application.
Alternatively you can also check this blog Syclo Customization Extension-First Steps.
Syclo Customization Extension-First Steps
Thanks
Manju.

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

SAP Work Manager 6.0 - Creating notification on mobile device (customizing the default Start and End date)

Dear all,
When I create a notification in SAP Work Manager 6.0, the notification gets created in the back-end with Start Date equal to Current Date + 1 day and End Date equal to Current Date + 3 days.
Can you advise where I can customize this behaviour, so that the Start Date is for example equal to the Current Date and End Date being 14 days in the future? Is this something that would need to be configured in Agentry Editor or within the ABAP stack?
Many thanks for your support.
Pavel
Tags edited by: Michael Appleby

Hi Jason,
We went this route and identified the initial values, and tried to modify those.
No impact though, as if those values are being overwritten elsewhere (whatever value we set, no change on the backend).
Please see the attachments with screenshots of Agentry Editor.
Many thanks.
Pavel

Custom Data Table in Work Manager 6.1 / SMP 3.0

Hi folks,
was trying to create a custom Data Table in Work Manager. Unfortunately I was not successful to get it working - probably I am missing out something.
Have created the DataTable in the Agentry Editor and configured the Java Class to use the DataTable class like for the other DataTables. Then created the 4 config values in the parameters of the Mobile Application Configuration (DT_MDOID, TABLE_CHECK, TABLE_REFRESH, ENABLE_TABLE). Also created a MDO that is mapped to the DT_MDOID which is derived from the /SYCLO/CL_CORE_DT_HANDLER class.
During sync, I am getting the following errors in the server logs - in the client it is Error 13 => Java...
08/13/2014 18:18:36, 1,         0,         2, Thr      10364, class RCP<class DT::DataTable>, D:\Syclo_BuildBot\rc_7.0server\Syclo\refcount.h#220:RCP<class DT::DataTable>::operator ->
2014/08/13 18:18:36.505:             + BackEnd=Java-SAPJavaConnection
2014/08/13 18:18:36.505:               Using Java code for <DATA_TABLE_NAME>
2014/08/13 18:18:36.506:               Java Exception "<DATA_TABLE_NAME>" Update Data Table: - java.util.NoSuchElementException
Do you have some pointers on what I may miss out?
Cheers,
Florian

Make sure that 'DT_MDOID" parameter entries are maintained correctly "That there is no typo's" in config panel. I don't think you need any entries for TABLE_CHECK, TABLE_REFRESH, ENABLE_TABLE parameters which are only relevant for complex table. Same in Agentry the data table should match with SAP name.
Let me know if you still have issues.
Thanks
Manju

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.

Work Manager 6.0 Push Notification not working

Hi All,
I have configured Standard Work Manager 6.0 application and now I am trying to configure Work Manager 6.0 Push Notification.
I have completed all Post Installation(optional and required) which are mentioned in Standard product document.
I am getting new work order entries in /SYCLO/PSH01 and /SYCLO/PSH02. After that Agentry server is also calling /SYCLO/PM_DOPUSHWORKORDER_GET Function Module and /SMERP/CL_PM_PUSHWORKORDER_DO Class Handler.
I am getting result in final export table(ls_mdo_output_vals) of /SMERP/CL_PM_PUSHWORKORDER_DO.
My problem is still I am neither getting this work order into ATE nor push notification message.
When I went to Syclo Admin panel, status of the push notification is also NEW.
I have configured 8282 port in [HTTPXML-2] section of Agentry,ini and Syclo Config panel outbound trigger.
Kindly let me know what can be an issue?
Regards,
Mohit Verma.
Message was edited by: Michael Appleby

Mohit,
I noticed the following in your Backend-Java.log.
~~~~~~~~error 1~~~~~~~~
2014/06/27 17:37:36.947: Error in initializing the StepHandler from the ini file or SAP configurations (com.syclo.sap.component.serviceorder.stephandler.ServiceOrderRemovePushStepHandler). Please check the JavaBE.ini file. java.lang.ClassNotFoundException: com.syclo.sap.component.serviceorder.stephandler.ServiceOrderRemovePushStepHandler
~~~~~~~~end~~~~~~~~~
<-- Make sure this is corrected. For some reason your java code is not being detected during start up. Check your Java folder in the root directory of your Work Manager 6.0 to see if it can be seen.
Based on history of Support tickets the following SAP Note is mandatory to make Push work:
1. Do mandatory SAP Note: 1954444
2. Please review: 1828657 - Release strategy for the ABAP add-ons SMFND, SMERP, SMISU, and SMCRM (Make sure you installed the correct add-on - look at the spelling in detail)
3. SCN Push threads that may help: http://scn.sap.com/thread/3494003
See if any of the comment above will work for you.
4. After you tried the above and it didn't work for you to try the latest SMP 2.3 SP04 version and let us know. This is for what I can see on the logs.
~~~~~~~~Error 2: Backend-java log~~~~~~~~~
2014/06/27 17:40:35.471:             Getting Java results in the the 'WorkOrderPushForEventSteplet' step (java class com/syclo/sap/component/workorder/steplet/WorkOrderPushForEventSteplet)
2014/06/27 17:40:35.471:             : 1 lines, 0 non-printing characters, 20 total characters
The module is 'PM'
2014/06/27 17:40:35.471:             The root object is 'WorkOrder'
2014/06/27 17:40:35.471:             Trying to read results by calling getReturnData()
2014/06/27 17:40:35.471:             : 1 lines, 0 non-printing characters, 81 total characters
getReturnData() method returned null, falling back to reading _returnData field
2014/06/27 17:40:35.471:             Processing public field _returnData: Ljava/lang/Object;
2014/06/27 17:40:35.471:             _returnData is a single object: 'Ljava/lang/Object;'
2014/06/27 17:40:35.472:             Mapping public fields of Java Class 'java/lang/Object' to Agentry object 'WorkOrder'
2014/06/27 17:40:35.472:             No public field userid found in java/lang/Object for user ID, and not in per-user mode: cannot determine user for data.
~~~~~~~~~end~~~~~~~~~~~~~~~~~~
The log comment above is stating that the push is trying to be sent to the PDA/handheld but it does not know where to send it to. This is proven from your backend setup and when you have no errors in your push retry.
The last line above is still a mystery to me as there are lots of upgrades with patches and SMP 2.3 SP# and with the userid is not found (especially when it states it is not in per-user mode: cannot determine user for data) then the Agentry Server cannot determine where to send the push to.   Hopefully somebody in this thread knows this.
Regards,
Mark Pe
SAP Senior Support Engineer (Mobility)

Accessing attachments stored in Open text (ECC) with Work manager 6.0

Hello Experts,
We are using Open text in one of our ECC systems to store documents, files, pdfs and other attachments for the Work Orders and Notifications.
We want to configure the Work Manager 6.0 application hosted on SMP2.3, in order to fetch all the Work orders in the mobile device.
Now the question is - Can we access the attachments on the mobile device, from the out of the box Work Manager configuration.
Or, is there a need to install any plug-ins in the ECC/Agentry side to enable the same.
Thanks,
Abhishek

Hi Abhishek,
This isn't out of the box functionality for Work Manager so you'll need to enhance the existing functionality.
To access OpenText Attachments (via ArchiveLink) in WorkManager try looking at the following->
1. Get Attachments
BAPI Wrapper - /SMERP/CORE_DOBDSDOCUMENT_GET
MDO Class - /SMERP/CL_CORE_KWDOCUMENT_DO (Method - GET)
You'll see the above GET method calls (If you GOS_ACTIVE flag is true) - GOS_DOCUMENT_GET_INFO
This is responsilbe for getting the attachment metadata returned to the Work Manager Client ->
ET_COMPONENTS
ET_SIGNATURE
ET_CONNECTIONS
To get the attachment metadata stored in OpenText via ArchiveLink look at the below Function Modules -
ARCHIV_GET_CONNECTIONS
ARCHIVOBJECT_STATUS
You could enchance the GOS_DOCUMENT_GET_INFO method with a Post-Exit method or Implement the BADI /SMERP/MDO_CORE_DOCUMENTS - END_BDS_FETCH
2. Create Attachments
BAPI Wrapper -/SMERP/CORE_DOBDSDOCUMENT_CRT
MDO Class - /SMERP/CL_CORE_KWDOCUMENT_DO (Method - CREATE)
This calls the method BDS_DOCUMENT_CREATE to create the file and store it against the Work Order / Notification.
You could look at following Function Modules ->
ARCHIVOBJECT_CREATE_TABLE (Create the file on the OpenText server)
ARCHIV_CONNECTION_INSERT (Link the newly created file with the Work Order / Notification)
The BADI doesn't provide a corresponding Create method so you could enhance the MDO class /SMERP/CL_CORE_KWDOCUMENT_DO with new method that calls the ArchiveLink Logic instead of the BDS_DOCUMENT_CREATE method. The new method can be configured via the Syclo Config Panel to be called instead of the standard CREATE method.
Also check out the document - Document Upload & Download handling in SAP Work Manager 6.0
Section 7 & 8 covers the BAPI Wrappers/Class Handlers & Ehancement Spots for Document handling
Hope that helps.
Cheers,
Stephen

Work Manager 6.1.0.4 configuration

Similar Messages

Maybe you are looking for