Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025

 


Article

OEManager is not installed during tcman create

« Go Back

Information

 
Article Number000083366
EnvironmentProduct: OpenEdge
Version: 11.5.x,11.6.x,11.7.x
OS: All supported platforms
Question/Problem Description
OEManager is not installed during tcman/pasman create.
 
Steps to Reproduce
Clarifying Information
Error MessageFrom Progress Developer Studio:

Publishing failed
The oemanager web application is not accessible
URL invoked: http://localhost:9090/oem/containers/localmachine/pas/localhost:resource.openedge.pas.oepas1/applications/oepas1/agents/sessions
Defect/Enhancement Number
Cause
This is expected behavior. Creation of a PAS instance does not automatically create the OEM interface for the PAS as it is unknown if the user intends to use the OEM interface.
Resolution
Windows:
cd %CATALINA_BASE% (like c:\openedgework\oepas1)
bin\tcman.bat deploy -u user:password %DLC%\servers\pasoe\extras\oemanager.war
Linux:
cd $CATALINA_BASE (like /usr/wrk/oepas1)
bin/tcman.sh deploy -u user:password $DLC/servers/pasoe/extras/oemanager.war

There are important differences about PASOE Production versus PASOE Development, like all transports (APSV, SOAP, REST, WEB) are disabled by default in PASOE Production and enabled in PASOE Development,  the same thing for publishing applications from a PDSOE (Developer Studio) to a PASOE Production instance  not supported once oemanager application is not installed in a PASOE Production instance by default for security purposes.  For more information about these differences refer to the Article: 
Workaround
Notes
Attachment 
Last Modified Date3/29/2019 8:16 AM