We are experimenting with the PASOE server in 11.7.4.
When you export your ABL Web application , the radio-selection says : Export ABL services for PAS
The war file that is generated , can this be used when deploying it in the restmanager ?
we tried it, but we get several errors when doing so
the localhost log file gives the error below
21-Mar-2019 16:17:15.173 SEVERE [http-nio-8980-exec-8] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [ManagerServlet] in context with path [/oerm] threw exception java.lang.RuntimeException: org.apache.cxf.interceptor.Fault at org.apache.cxf.interceptor.AbstractFaultChainInitiatorObserver.onMessage(AbstractFaultChainInitiatorObserver.java:115) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:322) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:211) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:213)
anyone an idea if this is possible ?
You cannot publish exported ABL Web Application (war) to rest manager. You can export ABL Web Application as incremental zip and publish paar files to rest manager. Following are the steps to publish paar files to rest manager.
1. Export ABL Web Application as zip (select 'Export services for incremental deployment' radio button)
2. Extract zip and from proenv publish paar to rest manager using the following command:
restman -i restmgr1 -appname <rest App name> -file <paar location> -republish
3. Add newly deoplyed paar entry under archiveFiles section in web.xml file
web.xml location: DLC\servers\tomcat\pdsoe\<rest service>\WEB-INF\web.xml
4. Restart rest manager. Your service will be up and running.
Hope this helps.
Additionally, since you mentioned that you want to use the PASOE, note that that is different from the rest manager.
The rest manager is running in the embedded Tomcat installation, which eventually connects to the Classic AppServer.
If you want to use PASOE, please look at the 'Progress Application Server' section on the resources page.
The default instance is called 'oepas1'.