Work Manager 6.1 on SMP 3.0 HEC

Hi Experts,
I want to deploy work manager 6.1 on HANA Enterprise Cloud-HEC. Is it possible,if so please provide document or procedure.
Thanks in Advance
Regards,
Sravanthi

SMP Cloud doesn't have Agentry Support currently.

Similar Messages

Work Manager 6.1 and SMP 3.0 with Agentry new features

Hi,
I know that Work Manager 6.1 is expected to be released by the end of June but I can't find any information about the product.
Since I'm starting a new project initially thought for Work Manager 6.0 but running in SMP 3.0, I would like to know the list of new features of 6.1 version.
At the same time I would like to know if the use of SMP 3.0 brings to the Agentry applications improvements regarding error handling, logging and administration in general since that was a bit poor in the previous versions.
The only thing I found regarding 6.1 version is this PDF where new functionalities regarding localization of assets in a map are added. I hope there is more than that.
Thank you for your help.

I guess the following thread answers my questions (except regarding SMP 3.0 logging, administrating and error handling with Agentry): http://scn.sap.com/message/15086739
I copy&paste the basic things to know:
More news during/after Sapphire
New features:
Based on SMP 3.0 using websockets for communication
GIS (ESRI) integration via Open UI
Visual Enterprise 3D integration via Open UI
SAP JCO 3 Support
Crew Management
WRP Customer Service
UX Improvements

Work Manager 6.0 for SMP 2.3 - standalone server - Startup Exceptions

Hello Experts.
I am installing a standalone Agentry Server for Work Manager 6.0 on the server where we have installed SMP 2.3.
It has been installed successfully and does start up, however I get some annoying error messages during start up.
It seems that the server is running - I can succesfully synchronize to an ATE client.
Due to the results from this thread, I have changed all ports in the Agentry.ini file to separate ports numbered 7521, 7522, 7523 and 7524.
Port issues - SMP and Agentry
Errors from the startup.log:
13:26:00 05/05/2014: HTTP-XML Back End Back End: Started
13:26:00 05/05/2014: Server: Starting threads.
13:26:00 05/05/2014: 1 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: Event: 20, 4, Server v6.1.0.3
13:26:00 05/05/2014: Starting front ends
13:26:00 05/05/2014: ANGEL Front End: Starting threads.
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: 3 initial threads. Threads will auto-scale.
13:26:00 05/05/2014: ANGEL Front End: opening listen socket on port 7523
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 17, 10, 0.0.0.0:7523 open
13:26:00 05/05/2014: Event: 17, 10, ANGEL Front End v6.1.0.3
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:00 05/05/2014: Event: 0, 0, Old log files moved into Logs-Rolled\2014-05-05-132546
13:26:00 05/05/2014: Event: 0, 23, 4
13:26:00 05/05/2014: Exception: 13:26:00 05/05/2014 : 2 (Socket Error), UNKNOWN (UNKNOWN, ), ..\Socket\win32\sockets.cpp#1514:ListeningStreamSocket::OSListeningSocket::listenOn
13:26:01 05/05/2014: Event: 0, 2, Server startup is complete.
13:26:01 05/05/2014: Agentry Application startup complete
Can anybody help with the meaning and implications of these errors ?
Thank you.
Søren Hansen.

Damn... I missed one port
You are correct. The default port (8282) of Agentry is used multiple places in the Agentry.ini file, and collides with SMP.
Thanks Steve.
For others:
Please make sure the following ports of the Agentry.ini file are unique across all applications on the server. In this case I have chosen to call all my ports on this instance 752X.
Now the server starts without errors.
[ANGEL Front End Ports]
1=7523
[TCP Front End]
listenOn=7521
[Java-1]
nonStandardJavaOptions=-Xdebug -Xrunjdwp:transport=dt_socket,address=7524,server=y,suspend=n
[HTTPXML-2]
baseURL=http://localhost:7522
listenOn=7525
Søren Hansen.

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

Upgrading work manager 5.3 to 6.1 with out SMP 3.0

Hello Experts,
As per the blogs and posts, work manager 6.0 is designed for SMP 2.3 and work manager 6.1 for SMP 3.0.Can we use work manager 6.1(with its additional features)without SMP 3.0 similar to work manager 5.3.Can we have standalone work manager 6.1 server or we need to install complete SMP 3.0 runtime .
Please suggest can we upgrade work manager 5.3 to 6.1 without SMP 3.0 to have standalone Agentry server for work manager 6.1(Like standalone server for work manager 5.3)
Thanks in advance
Thanks & Regards,
Sravanthi Polu

Hi Bill,
Thanks for your reply.What about the customization's done in Work Manager 5.3, will they have impact when we upgrade from 5.3 to 6.1 on SMP 3.0.What is the better approach to retain the custom logic if we go for upgrade(SMP 3.0).As per my knowledge if we go for 6.1 on SMP 3.0, then custom logic need to be implemented again, so considering customization's as higher priority, can we migrate existing Work Manager 5.3(With custom logic(Editor,Java,ECC Changes)) to SMP 3.0.If we migrate custom logic would be retained,but can we make use of the new features in SMP 3.0 like open ui,client branding .... etc.
Please help in this regard.
Thanks in advance.
Regards,
Sravanthi

Upgrading SAP Work manager 5.3 to 6.1 on SMP 3.0

Hi Experts,
We have SMP 3.0 server,work manager 5.3.Now want to upgrade from 5.3 to 6.1 and deploy standard work manager 6.1 (without crew management,meter management,customer service,linear asset management components)on to SMP 3.0
Agentry Editor and SMP 3.0 server are in different systems
Please suggest prerequisite add-ons needed,development and customization guides(for work manager 6.1 on SMP 3.0)
Manju Venkatesha, Please suggest in this scenario.
Thanks
Siva chandu
Tags edited by: Michael Appleby

Deploying WM 6.1 on SMP 3.0 can be found in
http://scn.sap.com/community/mobile/blog/2014/08/30/quick-start-guide-sap-work-manager-6x-with-smp-agentry
Thanks
Manju

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

SAP Work Manager status STOPPED in SCC

Hi All,
We have installed and deployed SAP Work Manager 6.0 on SMP 2.3. In the SCC it shows the app was registered or started successfully, however the Agentry instance server status is STOPPED. The Task Manager shows the Agentry Server is running, and can actually accessed from ATE.
The problem is we can't see anything in any of the other tabs. The tab Configurations is blank and we are not able to see or maintain any settings and/or parameters. The other tabs are also blank, for example Logs is not pulling in the data from the log files. See screenshots below.
The startup.log is also noit giving me any indications or errors. See also below.
Any suggestions as to what might be wrong? And how this can be resolved?
Kind regards,
Edwin
STARTUP.LOG
09:16:47 03/27/2014: Starting server (64-bit Windows)
09:16:48 03/27/2014: Administration client command port is 60880, status port is 60881
09:16:48 03/27/2014: Looking for initial status connection...
09:16:58 03/27/2014: Event: 0, 2, Status connection not detected. Continuing startup
09:16:58 03/27/2014: Reading system ini file.
09:16:58 03/27/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???
09:16:58 03/27/2014: Starting log file.
09:16:58 03/27/2014: Loading message groups.
09:16:58 03/27/2014: Starting threads.
09:16:58 03/27/2014:    1 initial threads. Threads will auto-scale.
09:16:58 03/27/2014: Starting Server: Agentry v6.1.3.10212
09:16:58 03/27/2014: Event: 0, 2, System Startup
09:16:58 03/27/2014: Loading 1 front ends
09:16:58 03/27/2014: Loading front end from angelvine.dll
09:16:58 03/27/2014: ANGEL Front End: reading init files.
09:16:58 03/27/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
09:16:58 03/27/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
09:16:58 03/27/2014: Event: 0, 2, Key pair loaded successfully.
09:16:58 03/27/2014: Starting Server Agent.
09:16:58 03/27/2014: Agentry: Starting threads.
09:16:58 03/27/2014:    1 initial threads. Threads will auto-scale.
09:16:58 03/27/2014: Agentry: Adding messages.
09:16:58 03/27/2014: Event: 1, 4, Agentry v6.1.3.10212
09:16:58 03/27/2014: Loading 1 agents
09:16:58 03/27/2014: Loading agent from ag3.dll
09:16:59 03/27/2014: Starting Server
09:16:59 03/27/2014: Server: reading ini file
09:17:00 03/27/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
09:17:00 03/27/2014: SystemConnection-2: Reading configuration information.
09:17:00 03/27/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
09:17:00 03/27/2014: HTTP-XML Back End: Initialized.
09:17:00 03/27/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
09:17:00 03/27/2014: Initializing 1-Java from ag3javabe.dll
09:17:00 03/27/2014: SystemConnection-1: Reading configuration information.
09:17:00 03/27/2014: SystemConnection-1: Setting name to 'Java Back End'.
09:17:00 03/27/2014: Java Back End: Initialized.
09:17:02 03/27/2014: Java Back End: Java Virtual Machine loaded.
09:17:07 03/27/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200
09:17:07 03/27/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server
09:17:07 03/27/2014: Java Back End: Initialized.
09:17:07 03/27/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_35, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll
09:17:07 03/27/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"
09:17:07 03/27/2014: Event: 20, 152, Loading Production application definitions for default localization
09:17:18 03/27/2014: Event: 20, 153, Finished loading Production application definitions for default localization
09:17:18 03/27/2014: Event: 20, 151, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"
09:17:18 03/27/2014: HTTP-XML Back End Back End: Started
09:17:18 03/27/2014: Server: Starting threads.
09:17:18 03/27/2014:    1 initial threads. Threads will auto-scale.
09:17:19 03/27/2014: Event: 20, 4, Server v6.1.3.10212
09:17:19 03/27/2014: Starting front ends
09:17:19 03/27/2014: ANGEL Front End: Starting threads.
09:17:19 03/27/2014:    3 initial threads. Threads will auto-scale.
09:17:19 03/27/2014: ANGEL Front End: opening listen socket on port 7003
09:17:19 03/27/2014: Event: 17, 10, 0.0.0.0:7003 open
09:17:19 03/27/2014: Event: 17, 10, ANGEL Front End v6.1.3.10212
09:17:19 03/27/2014: Event: 0, 0, Old log files moved into E:\SAP\MobilePlatform\Servers\UnwiredServer\logs\com.sap.wm\Rolled\2014-03-27-091647
09:17:19 03/27/2014: Event: 0, 23, SAP Mobile Platform
09:17:19 03/27/2014: Event: 0, 2, Server startup is complete.
09:17:19 03/27/2014: Agentry Application startup complete

Hi Stephen,
We installed SP04, but we are still experiencing the same issue. We even went as far as deleting and re-deploying the app.
Again it shows the app registered successfully:
On the General tab it still shows status STOPPED:
The other tabs don't show anything, e.g. Configurations or Logs:
After restarting SMP the node completely disappears:
The Region & Language settings on the SMP server:
Any further suggestions are much appreciated.
Regards,
Edwin

SAP works manager 6.2 with ESRI maps

Dear Experts
We are using SAP Work Manager 6.2 with SMP 3.0 (SP05) Agentry and attempting to implement the ESRI location tab in the IOS agentry app but coming up with the following issue.
we have followed the exact steps in the SAP® EAM and service mobile app SDK Installation Guide with the exception that we are using Xcode 6.1 instead of Xcode 5. we have also had to include the System.Configuration framework but apart from this it has gone together without a problem.
We can run the existing SAP Works Manager app on the IPAD so we are able to successfully connect to the SMP agentry server but when we try to run the custom agentry app it halts at the following screen. We have tried different agentry users but with no success.
Could you please suggest if there are any other information available to get this working .
Following are the other SCN links we tried following
Quick Guide - Checklist to set ESRI in SAP Work Manager 6.1.X (WPF client)
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20b3f3d8-9d8f-3210-4cbc-f3e42e6df649?QuickLink=index&…

Hi Sid,
Check the SDK version that was used to build your custom Agentry Client. Not the Server version.
From the initial screen click on the Info/About icon to see which version you're using to build your client e.g.
Looking at your image you can see the input field where you're meant to enter the Work Manager URL is behind the header field. I had the same issue when I was using an old version of the SMP SDK / Agentry Client.
I suggest you download the latest SDK version from the SAP Service Marketplace and rebuild a new client using that.
SK

SMP SAP Work Manager 6.1 multi language

Hi all,
we have installed SMP 3.0 SP5 with SAP Work Manager 6.1. We would like to use multi-language functionality but field labels do not translate after our configuration changes.
We have created "localization" folder under "server\configuration\com.sap.mobile.platform.server.agentry.application\Application\Development" path and copy new ini files from language pack.
We modify the configuration property as follows:
Localization Path = Application\Development\localization
Localizations= it
In the startup server log seems no error occurs and translation file are loaded successfully.
Thank you.
Regards,
Paolo
Tags edited by: Jitendra Kansal (Moderator)

Hi Stephen,
our SMP system returned available so I copy dei multi language file of "it" country under the path that you have suggested.
When I synchronize from the agentry client seems that connection does not end successfully. In particular in the log file I found the new italian label but the synch is very slow about 2 hours.
What do you think about it?
Thanks,
Paolo

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

How to create 2 Work Manager Apps on SMP Server (Agentry)

Hi All,
I encountered a problem with my SMP 2.3 SP3 in combination with Agentry 6.1.. and Work Manager 6.0.
I have an already working version of WorkManger on my SMP Server on port 7003, but whenever I create another WorkManager version on a different port e.g. 7005 the SMP/Agentry Server displays the status STARTING but never finishes this processs state.
The version of both Work Manager instances is the same, with the exception that the section [ANGEL Front End Ports] in the file Agentry.ini contains once the port 7003 and in the other file e.g. 7005.
Has anyone a encountered a similar problem or is able to create two different WorkManager versions on the same AgentryServer?
Regards,
Thomas

Hello Steve,
thanks for your quick reply, the listenOn Port is at both applications the same I will fix that in a few seconds.
the entry nonStandardJavaOptions is at both apps empty.
the startup.log of the second application:
14:16:58 03/19/2014: Starting server (64-bit Windows)
14:16:58 03/19/2014: Administration client command port is 55086, status port is 55087
14:16:58 03/19/2014: Looking for initial status connection...
14:17:04 03/19/2014: Event: 0, 30, Admin client 10.33.160.94:55094 authenticated successfully.
14:17:04 03/19/2014: Event: 0, 27, Admin client 10.33.160.94:55094 has connected
14:17:04 03/19/2014: Reading system ini file.
14:17:04 03/19/2014: ID: SAP Work Manager Server v6.0.0.0, Name: ???, Location: ???
14:17:04 03/19/2014: Starting log file.
14:17:04 03/19/2014: Loading message groups.
14:17:04 03/19/2014: Starting threads.
14:17:04 03/19/2014: 1 initial threads. Threads will auto-scale.
14:17:04 03/19/2014: Starting Server: Agentry v6.1.3.10212
14:17:04 03/19/2014: Event: 0, 2, System Startup
14:17:04 03/19/2014: Loading 1 front ends
14:17:04 03/19/2014: Loading front end from angelvine.dll
14:17:04 03/19/2014: ANGEL Front End: reading init files.
14:17:04 03/19/2014: Event: 17, 14, ANGEL Front End v6.1.3.10212
14:17:04 03/19/2014: Event: 0, 2, Loading the Agentry Server's public/private key for password exchanges.
14:17:04 03/19/2014: Event: 0, 2, Key pair loaded successfully.
14:17:04 03/19/2014: Starting Server Agent.
14:17:04 03/19/2014: Agentry: Starting threads.
14:17:04 03/19/2014: 1 initial threads. Threads will auto-scale.
14:17:04 03/19/2014: Agentry: Adding messages.
14:17:04 03/19/2014: Event: 1, 4, Agentry v6.1.3.10212
14:17:04 03/19/2014: Loading 1 agents
14:17:04 03/19/2014: Loading agent from ag3.dll
14:17:04 03/19/2014: Starting Server
14:17:04 03/19/2014: Server: reading ini file
14:17:04 03/19/2014: Initializing 2-HTTPXML from ag3httpxmlbe.dll
14:17:04 03/19/2014: SystemConnection-2: Reading configuration information.
14:17:04 03/19/2014: SystemConnection-2: Setting name to 'HTTP-XML Back End'.
14:17:04 03/19/2014: HTTP-XML Back End: Initialized.
14:17:04 03/19/2014: Event: 24, 4, Loaded HTTP-XML Back End (HTTPXML v6.1.3.10212) from ag3httpxmlbe.dll
14:17:05 03/19/2014: Initializing 1-Java from ag3javabe.dll
14:17:05 03/19/2014: SystemConnection-1: Reading configuration information.
14:17:05 03/19/2014: SystemConnection-1: Setting name to 'Java Back End'.
14:17:05 03/19/2014: Java Back End: Initialized.
14:17:05 03/19/2014: Java Back End: Java Virtual Machine loaded.
14:17:08 03/19/2014: Java Back End: Java Back End AJAPI version 5.0, release 6.1.3.10200
14:17:08 03/19/2014: Event: 23, 101, Java Back End: AJAPI JAR version 6.1.3.10200 does not match the version of the Agentry Server
14:17:08 03/19/2014: Java Back End: Initialized.
14:17:08 03/19/2014: Event: 23, 4, Loaded Java Back End (Java v6.1.3.10212 (JVM version 1.6.0_22, AJAPI version 5.0 build 6.1.3.10200)) from ag3javabe.dll
14:17:08 03/19/2014: Event: 20, 150, Loading Production application definitions using file "SAPWM-v1-0-0-app"
14:17:08 03/19/2014: Event: 20, 152, Loading Production application definitions for default localization

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

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 not rendering on ATE iPad

Hi,
Working with Work Manager 6.1 I find the screens aren't rendering for a number of platforms in the ATE. For our current project we are using the iPad screenset but when testing via ATE the screens don't display the data (All the objects are downloaded correctly).
I couldn't find any SAP notes covering the problem.
This makes it difficult to test rules and actions because many are in screens the need to be accessed by drilling into objects. Since the data isn't visible you can't drill into the required screens.
1. Is this a known issue? If so are there plans to fix this?
2. Are there suggested workarounds?
Currently we're using 2 approaches -
a. Temporarily make the rule/action available on the main screens so they can be triggered and debugged.
b. Make the rules/actions available in the Pocket screensets and trigger them from there (Currently only the Windows CE Pocket PC Portrait platform seems to render correctly)
After successfully testing the rule/action, then remove the temp change. Both approaches can be time consuming and fiddly to implement so it would be much better if ATE just rendered the screens properly.
3. Is it possible to increase the tracing for the other Agentry Clients e.g. WPF or Agentry SMP logging so it can output trace information about rules/actions?
Development Environment -
ATE Version - 7.0.3.605
SMP Platform - 3.0.3.2
Cheers,
Stephen

Hi Michael,
My clients are below -
WPF Agentry Client - 7.0.3.605 (this renders correctly shown below)
SMP Platform - 3.0 SP03 PL02 (Not sure where to find the Agentry Sever version embedded in SMP)
ATE - 7.0.3.605
The ATE / Agentry Clients have been downloaded/installed using SMP SDK 3.0 SP04
Searching SCN I found the questions below which state that rendering in the ATE for iPad doesn't work for Agentry 6.1.x. I want to understand if this still applies for v7.x
SAP Work Manager App not displaying in ATE and iPhone
Improper screen in the Ipad and iphone platform in ATE V6.1.0.3
Cheers,
Stephen

Work Manager 6.1 on SMP 3.0 HEC

Similar Messages

Maybe you are looking for