Quick Start Guide to install SAP Work Manager 6.3 with SMP 3.0
If you are the first time to use the work manager application, especially for 6.3 version, this quick start guide about Work Manager 6.3.x deployment will be good for you to start.
Note: All the contents of this article are the minimum requirement on this topic.
- Fully installed in the SAP Mobile Platform
- Start the SMP 3.0 Services and make sure the SAP Management Cockpit is active
- User configured the SAP Add-on for Work Manager 6.3 (it is similar with Work Manager 6.2, so you can also check the link – http://scn.sap.com/community/mobile/blog/2014/12/04/work-manager-62)
SAP Mobile Platform 3.0 SP10
Work Manager 6.3.x
WPF Agentry Client v70.11.0
Step by Step guide:
Download the Work Manager 6.3 from SAP ONE Support Launchpad following the link below.
Each available software to be downloaded are standalone. For example: Deployment, Crew Management or Meter Management. Users has to choose which one they want and work on it from there.
Unzip the installation file and run the workmanager.server-6.3.0.exe
Enter the Work Manager Backend Server address, Client number, Sys Number and User information, and then select directory to generate the application.
During the installation, the workmanager.server-6.3.0.exe will produce the SAP Work Manager 6.3.x application definition, libraries and other configuration files in a zip file “SAPWorkMgr630Deployment-20151103.0552.zip” that will be used in the SAP Mobile Platform Management Cockpit.
Ini files – Configuration files used in Work Manager 6.3, for example: JavaBE.ini file will include the backend connection information that we just input in the previous step; Java folder will include many *.jar files – Java class files used to interface with SAP backend;
Open the SMP Management Cockpit and create a new application with type “Agentry” and set the Authentication providers with ‘No Authentication Challenge” option.
Save the application and the Agentry application node will be created under the SMP configuration folder, generic ini configuration files area would be generated.
Restart the SMP server, check the startup.log and you can see the message about there is no application and backend loaded yet for this new application. Once Restarted, open the application in the management cockpit and navigate to “APP SPECIFIC SETTINGS”, press the Browse button to import the application zip file “SAPWorkMgr630Deployment-20151103.0552.zip” under Publish tab.
After loading the application zip file, the backend will be shown in the configuration screen and include the contents in the Agentry.ini file before.
Note: sapsso.jar is only for sso setup and is not part of the out of box deployment files.
Save the application and restart SMP server. Check startup.log and event.log, make sure the work manager 6.3 application has been loaded successfully in the SMP/Agentry Server.
Check from IE if you can connect the application in the SMP and see “I am here” by typing https://SMPServerAddress:8081/ApplicationName, open the SMP cockpit and navigate to the configuration screen of this Agentry application, then you can get the application name from the ‘urlPath’ field under APP SPECIFIC SETTINGS.
During the SMP 3.0 installation, the smp_crt.cer file would be generated under the Server/configuration folder. In order to get the approval for accessing SMP server from Agentry Client, we need to install the certificate file in the mobile device.
In this scenario, copy the smp_crt.cer file to the root folder of WPF Agentry Client and install it under the Trust Root Certification Authorities.
Open the WPF Client, input the Agentry Backend user name and password, enter the URL “https://SMPServerAddress:8081/ApplicationName” that can access the work manager 6.3 deployed in the SMP server and you will see the transmit has started in the popup screen.
At last, if you open the SMP Management Cockpit and navigate to “USERS” option under the APPLICATIONS tab, you would find that the connect information for this user on this Agentry application.