SAP Work Manager 6.2 Installation Problem

[Former Member]

Environment:

SMP 3.0 Server SP04 PL2

SMP 3.0 SDK SP05 PL5

Windows Server 2012

SAP Work Manager 6.2

I am trying to install the Work Manager 6.2 app into my SMP 3.0 server. I've followed the steps in the installation guide (and the quick start guide) but the backend tab for the application remains empty.

There are no errors in the Agentry start up log file, but I don't get the SAPWM62: Openening webSockets servlet for sub-URL/SAPWM message (like I do for other Agentry apps) either. Here's a snippet from the startup.log file:

14:32:59 12/10/2014: Starting SAPWM62

14:32:59 12/10/2014: Event: 22, 4, SAPWM62 v7.0.4.17

14:32:59 12/10/2014: Starting front ends

14:32:59 12/10/2014: Starting front end FlightBooking

14:32:59 12/10/2014: FlightBooking: Opening WebSockets servlet for sub-URL /FlightBooking

14:32:59 12/10/2014: Event: 17, 10, FlightBooking v7.0.4.17

14:32:59 12/10/2014: Starting front end Inventory2

14:32:59 12/10/2014: Inventory2: Opening WebSockets servlet for sub-URL /Inventory

14:32:59 12/10/2014: Event: 17, 10, Inventory2 v7.0.4.17

I do see the following in the event.log file:

12/10/2014 14:33:00, 0,        22,         5, Thr       5476, SAPWM62

12/10/2014 14:33:00, 0,        22,       150, Thr       4208, Loading Production application definitions using file "SAPWM-v1-0-0-app"

12/10/2014 14:33:00, 0,        22,       152, Thr       4208, Loading Production application definitions for default localization

12/10/2014 14:33:13, 1,         3,         9, Thr       4208, HTTPXML-2, Chickaming HTTPXML, xmlAllowXSLTScript, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

12/10/2014 14:33:13, 1,         3,         9, Thr       4208, HTTPXML-2, Chickaming HTTPXML, xmlResolveExternals, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

12/10/2014 14:33:13, 1,         3,         9, Thr       4208, HTTPXML-2, Chickaming HTTPXML, xmlValidateOnParse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

12/10/2014 14:33:13, 0,        24,         4, Thr       4208, Loaded HTTP-XML Back End (HTTPXML v7.0.4.17) from ag3httpxmlbe.dll

12/10/2014 14:33:13, 1,         3,         9, Thr       4208, Java-1, Chickaming Java, initialHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

12/10/2014 14:33:13, 1,         3,         9, Thr       4208, Java-1, Chickaming Java, maxHeapSize, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

12/10/2014 14:33:13, 1,         3,         9, Thr       4208, Java-1, Chickaming Java, nonStandardJavaOptions, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

12/10/2014 14:33:13, 1,         3,         9, Thr       4208, Java-1, Chickaming Java, reduceOSSignalUse, File: , ..\agentry\SystemLogger.cpp#792:DTLoggerHandler::badKey

12/10/2014 14:33:14, 1,        20,        18, Thr       4208, JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Invalid login username or password (repeat logon)

12/10/2014 14:33:15, 0,        22,       153, Thr       4208, Finished loading Production application definitions for default localization

12/10/2014 14:33:15, 0,        22,       151, Thr       4208, Finished loading Production application definitions using file "SAPWM-v1-0-0-app"

12/10/2014 14:33:15, 0,        17,        14, Thr       5476, SAPWM62 v7.0.4.17

12/10/2014 14:33:15, 0,        22,         4, Thr       5476, SAPWM62 v7.0.4.17

12/10/2014 14:33:16, 0,        17,        10, Thr       5476, SAPWM62 v7.0.4.17

So the problem is probably the invalid login but I don't know where to change this (agentry.ini file no longer exists).

I can reach the application via the browser (I am here!) with https://<ipaddress>:8081/SAPWM (should it be SAPWM62?).

Any help in resolving this problem would be greatly appreciated.

Thanks,

Dave

[mark_pe · Accepted solution]

Dave,

1. Review your application zip that creates the Agentry node in the SAP Mobile cockpit.

- In this zip file what's in it? What is the javaBE.ini or agentry.ini you used? This should be the final one.

- in SAP Mobile Platform 3.0 you are not allowed to do any javaBE.ini changes as it is assumed all the changes will be done in the cockpit.

- If you are planning on changing something outside the cockpit (ex: javaBE or agentry.ini) it is recommended to redo the application zip that creates the Agentry node or application (SAPWM62).

- you may have to re-unzip the zip file and modify all the files that needs to be modified (agentry.ini, javaBE.ini and others).

- The point of a production publish is that it is the official frozen zip file.

My suggestion: your error is all tied to the zip file you used is not final yet.  Hence you are seeing it being regenerated.  it is in fact being regenerated to the original version you used.

2. After you review item 1 above, the next thing to do is to clear and redo the agentry application. Make sure you restart SMP 3.0 and after restart, verify that the old folder was removed on startup.

3. Create the Agentry application again (SAPWM6.2) with all the final files in it (including the certificates, java folder, all the ini (make sure it is final).

4. After 3, review the contents of the configuration/Agentry/com*.*.SAPWM62 (or whatever the application name is).

- If something is missing recopy it from step 1 above. So sometimes you may be missing an application folder so any thing that may be missing copy it from your zip file.

5. As soon as you do any of the copying. Restart the Agentry application in the Cockpit (you may notice that your backend may now get connected.

Regards,

Mark Pe

SAP Senior Support Engineer

[Former Member · Accepted solution]

Hi Mark,

Thanks for your detailed response. The application zip file contains the following files:

The agentry.ini file contains standard information. I don't see anything specific to this implementation.

The javaBE.ini file contains connection information including the server name, user ID, password (encoded), etc. Basically all of the information I was prompted for when running  SAPWorkMgr620Deployment.exe

I repeated the steps as you described but I am getting the same result. I don't think there is an issue with the application's deployment into SMP. That all seems correct.

I suspect that the issue is with the backend server. I either have the server value in the HOST section entered incorrectly, or there is a problem with the user ID and password.

The server value in the [HOST] section of JavaBE looks like this:

server=vcxxxecxci.xxx.sac.hec.sap.biz

(Note: the value xxx has been substituted here for the client's name for confidentiality)

That is the value I use to connect to the ECC sandbox server from SAPGUI. I am using the same user ID and password as I use in SAPGUI but in the event log I'm still seeing:

12/11/2014 09:51:27, 1,        20,        18, Thr       8656, JAVA EXCEPTION CAUGHT: com.syclo.agentry.AgentryException: Invalid login username or password (repeat logon)

I'm assuming it is reaching the server or the error message would be different, but we all know how obtuse Java errors can be.

Any suggestions on how to troubleshoot this would be greatly appreciated.

Thanks,

Dave

[mark_pe]

Dave,

With respect to your question about:

Question:

I can reach the application via the browser (I am here!) with https://<ipaddress>:8081/SAPWM (should it be SAPWM62?).

Answer:

SAP Mobile Platform and Agentry uses an internal keyword to name the application. When you design an Agentry application from scratch (Eclipse editor) you have to define the application name and/or display name. You will then have to published this. It will generate files that looks like this:  SAPWM-v1-0-0.app.agpz and SAPWM-v1-0-0.app.ini.  If the internal name inside the SAPWM-v1-0-0.app.agpz (unzip it and open it up in a text editor - search for the internal name) was not changed then that will indicate that the designers or product developers published it with that named or the internal name never got changed.

This is especially true for add-ons.  Let us say you have Work Manager basic then you want to add on Meter Management. Normally in the past, you will need to import or merge Eclipse editor export file in the base product. It may occur that the merge didn't change the name of the base.  So during export or publish, the same internal name SAPWM may have been used. Again, you can check this by opening up the agpz file (this is my best guess).  There could be a setting that the SAPWM62 may have the same internal name.

But hopefully the new feature of SMP 3.0 can help you here.

In SAP Mobile Platform 3.0 at least SP06 or SP05 there is a feature in the cockpit to show you the default internal name of the Agentry application you are using. You can see this in the cockpit. If you do not like this name you may change it to whatever you want provided that you  bounce or restart SMP 3.0 to take affect and make sure the application restarts.

I hope I was able to give you some answers to your questions and made it more transparent in the community.

Have a good day and happy install.

Best Regards,

Mark Pe

SAP Senior Support Engineer

[Former Member]

Thanks for the detailed explanation. Makes sense. I just wanted to make sure I was using the right app name in the URL.

[mark_pe]

Dave,

I just spoke to the Work Manager team a few minutes ago (to discussed this particular issue). They designed or delivered the Work Manager to be fully named SAPWM.  Any add ons like Meter Management will not be named SAPWM-METERMANAGEMENT in the editor or anything similar to that. It will be named SAPWM still. So the Internal name will be SAPWM. The areas where you can modify the name will be in the agentry.ini for urlPath or SMP 3.0 (Cockpit). Each of the delivered files in SAP Service Marketplace for a MeterManagement will have all the files configured (like agentry.ini and javaBE.ini). The internal name will still be SAPWM.

Regards,

Mark Pe

SAP Senior Support Engineer

[Former Member]

Update: I found the settings in the JavaBE.ini file. The password is encrypted so I don't know if it is correct. I'm pretty sure I entered it correctly during the install though.

I've verified that I can login to the ECC using SAP GUI with the same credentials. Not sure what to do next.

Thanks,

Dave

[Former Member]

I see you have 2 applications load on the Server. WM 6.2 and FlightBooking.  Because the error is the events log file and not in the startup log file  was there a user trying to connect to the FlightBooking application with an bad username \ Password?

or is there anything in the Startup.log file around the same time (14:33:14) as the events.log?

[Former Member]

The FlightBooking application uses OData to access the SAP Demo server. I'm the only one using the server (its a sandbox development server) so no one would be accessing the system but me.

I checked the log files immediately after restarting the SMP server. I could be wrong but I think the error occurs when the Work Manager app tries to connect to the backend system.

I'm not sure what is needed (or where) for the backend tab to be populated in the management cockpit for the app.

Thanks,

Dave

[Former Member]

That error would be caused by the user in the JavaBE.ini for connecting into the SAP System.

[Former Member]

I edited the JavaBE.ini file but the changes aren't retained after a server restart. It seems like this file is getting regenerated.

Thanks,

Dave