OEManager is not installed during tcman create

OEManager is not installed during tcman/pasman create.
 

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.

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: 

•  What are the differences between a PASOE Development Server and a PASOE Production Server? 

Progress Articles:

 Where to find information about PASOE Deployment?  
 How to deploy a webapp and/or services from development to a PASOE production instance  
 What are the differences between a PASOE Development Server and a PASOE Production Server?  
 What are the wtbman asbman equivalents for PASOE  
 How to capture a stack trace from a PAS for OE ABL Session?