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