Deploying SAP Work Manager in Cloud

Just wondering if we can deploy the SAP Work Manager5.3 / 6.0 in AWS (Cloud).
From a logical point of view, I think its definitely possible.
Anybody tried that option?
Would love to hear more.
Thanks,
Abhishek

Hi,
I haven't noticed latency problems. If the VPN connection to the ERP system falls over, you will have a bunch of errors, but Agentry recovers well once the connection is re-established (a benefit of storing all of the state on the ERP system). We've done quite a bit of development this way without very many problems.
Please keep in mind that I am only talking about development systems and I'm not focused on measuring performance. If you were really pushing a lot of data in production, you would need to be very careful about the properties of the network. You are definitely asking the right questions!
Best regards,
Rob

Similar Messages

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

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

SAP Work Manager 6 - WPF Client & ATE Error

Hi,
I have installed SMP 2.3 SP03 L01 and have deployed the Work Manager 6 application on the server. My Agentry.ini and JavaBE.ini files seem okay. Self-Signed certificates were used properly as mentioned in the guides. connectTest.bat executes correctly, thus showing SAP backend information. The Work Manager agentry application starts correctly from SMP.
However, now that i want to test the application, I'm unable to connect to the server. The WPF and ATE errors are as below:
Can somebody help me out with these errors?
Tags edited by: Michael Appleby

Hi Abhishek,
I have figured out the problem. You are correct, the common name should be indessapd011. Other than that I had to change a couple of settings in the Agentry.ini too.
I'm now able to connect to the test environment:
However, I'm still unable to connect to the WPF client. The error is still:
Logging user into server
Communications error (14)
Connection failed
Ending transmission
Any ideas on this?

Adding a new screen on SAP Work Manager 6.0

Hi All;
I'm working on customising the SAP Work Manager 6.0 application. One of the things that I have to do is add a new screen "Pool Management". I have been trying to achieve this via the Agentry Editor 3.7.2 with no luck. So the first thing that I did was to copy an existing screen, for example the TimesheetView screen set, hoping that there would be a duplicate screen similar to this, but this doesn't seem to be adding the duplicate screen when I test via the Agentry WPF client. Please kindly advise how I would go ahead with a requirement like this. Please see image below for the screen addition that I am working on. I would really appreciate your help in going about with this!
Much appreciated!
Sizo Ndlovu

Sizo,
Steve is correct. Examine the main screenset. Choose the platform, then copy an existing screen or add a new one. Modify it as needed. It will now display as a new tab on the client.
Jason Latko - Senior Product Developer at SAP

Integrated google Map on SAP Work Manager 6.0

Hi
I am new in agentry and worked on SAP Work Manager App. I want to put customized map in Agentry and show some workorder on that map.
Can anyone give me any suggestion regarding it.
Thanks
Mohit Tyagi

Hi
Can any one help me for putting map on SAPWM 6.0 . and i am working on SMP 2.3.So please give me suggestion how can i achieve this problem. and is it possible to put map on SAPWM 6.0 without integration any API?
Thanks
Mohit Tyagi

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

Android Screensets - SAP Work Manager 6.0

Hello Experts,
We have imported Agentry applications in eclipse agentry editor using Agentry.ini file, which points to work manager and meter management app but we are not able to find android screen sets in these applications.
We are able to see Windows and Ipad/Iphone screen sets in Agentry modules but no where we can see android screen sets.
Here I’m attaching screenshots of Agentry application for your reference.
Requirement is to support SAP Work Manager app on android platfrom and able to customize this app.
Regards,
Abhishek Wajge

You won't see separate android screen sets. Android platform basically uses iOS screen sets. Depending on whether your using android smartphone or tablet , application uses iphone or ipad screens accordingly. All these settings are maintained in Screensets,ini file.
I hope it answers your quesiton.
Thanks
Manju Mobility - RIG

SAP Work Manager 6.0 Query

Hi Experts,
Can somebody tell me what BAPIs run in background when transmitting a Work Order from SAP Work Manager WPF Client to ECC?
Also, what post installations are required after installing Work Manager?
All I have done are the following:
/SMERP/SAP_WORK_MANAGER_60_REF ( Work Manager 6.0 base)
/SMERP/SAP_WORKMGR_60_EHP5_REF ( Work Manager 6.0 with LAM & inspection rounds)
Activated switch /SMERP/EPH5_EAM_BUS_FUNC (using LAM)
What are the post installations for Push Scenario? Is that post installation required for transmitting a Work Order from a client to SAP backend?

I would suggest revieiwng the documentation as it includes the post installation steps that must be taken when installing the product.

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

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.

Editing attachments in SAP Work Manager 6.0

Hello Experts,
Is there a way to edit attachments in the SAP Work Manager 6.0 application and save it back to the respective Work Order in the ECC system?
Would appreciate if you can provide some pointers
Thanks,
Abhishek

Abhishek,
This may be possible but will depend on the host OS for the mobile device (Windows can do it, iOS can't) as well as how you have your processes defined and if you have the necessary editing tools on the device.
The process will be to download the document to the device.
Launch the editing software passing the file downloaded to edit
Save the file
Attached the edited file to your Work Order
Transmit to upload the edited document.
The reason iOS can't do this is due to the nature of your applications being contained and not sharing data across applications. There may be some iOS OS enhancements coming in 7.2 and beyond which may enable this data sharing but for now you can't do it on iOS without using custom code (OpenUI on SMP3.0)
Android may work depending on where you store you downloaded documents. If they are stored in a "public" area then it might be possible to also do this on Android.
Good luck.
--Bill

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

Deploying SAP Work Manager in Cloud

Similar Messages

Maybe you are looking for