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

Similar Messages

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 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.

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

Work Manager 6.1 - Complex table Enhancement

Hi All,
I had created a custom class for a Complex Table - CodeGroup - which is attached - on top of Work Manager 5.3 Java Code.
Now we are upgrading to SMP 3.0 and Work Manager 6.1, and this class is throwing this error during transmit:
JAVA EXCEPTION CAUGHT: java.lang.AbstractMethodError: Missing implementation of interface method "com.syclo.sap.ComplexTableObject.setProperties(Lcom/syclo/sap/jco/JCO$Table;)V"
I am not sure which method am missing to implement.
Kindly help.
Regards
Ankur
Tags edited by: Michael Appleby

Hi Stephen,
Yes I am using the same call that I had on WM 5.3 on WM 6.1.
How do I implement the changes without having the source code of WM 6.1?
I have been pointed to some documentation by SAP, but it is not helping me much.
Please advice.

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 Management Service (WMS) Application on mulit-farms

Hi guys,
Is there any limitation for configuration the Work Management Service (WMS) Application on multi-farms?
I have 2 farms – farm A hosts all SAs and farm B hosts only web contents.
I understand there is dependency between WMS and search and UPS. Does that mean I cannot deploy my WMS on farm A?
Thanks

Hi,
According to your post, my understanding is that you want to configuration the Work Management Service (WMS) Application on multi-farms.
Per my knowleadge, you can deploy Work Management Service on farm A.
Though there is dependency between WMS and search and UPS, , some service applications such as Search and User Profile can be shared across server farms in SharePoint 2013.
In addition, you can also configure a SharePoint Server 2013 content farm that receives search queries to trust the SharePoint Server 2013 farm that sends the queries.
More information:
Share service applications across farms in SharePoint 2013
Configure trust for search between two SharePoint Server 2013 farms
SharePoint 2013: Work Management Service Application
Best Regards,
Linda Li
Linda Li
TechNet Community Support

SAP Work Manager setup

Hi,
We are planning to setup SAP Work manager agentry app in our environment.
What are the Add-Ons to be installed on the ERP system for the Work manager app?
Please guide.
Thanks,
Gokul.
Tags edited by: Michael Appleby

Hi Gokul,
Please check if these links might help you
For SMP 2.3
Re: Work manager with SMP 2.3
For SMP 3.0
SAP Work Manager 6.0

SAP Work Manager 6.1 deployment on SMP

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

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

Syclo Work Manager 6.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

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 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

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

SMP 3.0 - Deploying Work Manager 6.1 - Production Landscape

Similar Messages

Maybe you are looking for