IBM Support

Cannot publish a FileNet Process Engine (PE) Web service to an external UDDI if you do not configure Object Store->Workflow System->General Tab->Process Orchestration in ACCE

Troubleshooting


Problem

When trying to publish a FileNet Process Engine (PE) workflow to UDDI, an error like the following occurs: Failed to publish workflow "POD": No valid CCEPOWSBrokerURL was defined "GP ECM FileNet P8 Development":Refresh...

Symptom

A workflow with the first step as a Receive web service step is being used. This workflow has run fine on P8 3.x, P8 4.5.x and P8 5.1.x.  A development server has been upgraded to P8 5.2 and the PE Isolated Region has been rebuilt and there is a need to republish this PE workflow web service to the external UDDI server so that the calling application can launch this PE web service workflow.               
                                                                      
The document "PCC Cannot publish to UDDI.PNG" (below) shows the "Failed to publish workflow..." error that is seen in Process Configuration Console (PCC) when the publishing to UDDI is attempted.         
PCC_Cannot_publish.PNGPCC_Cannot_publish.PNG

They try to retrieve the WSDL for this web service workflow, using this URL:                                                  
http://<hostname>:9080/WorkplaceXT/P8BPMWSBroker/wscpReg01CP/wc/POD?wsdl     
                                                                    
In all prior releases of P8, this would return the wsdl for the currently published instance of this workflow.  
                                                                      
When they visit the wsdl URL above, the following error is seen instead of the wsdl:

2014/01/29 10:25:55 [WebContainer : 2] FATAL filenet.ws.listener.http  CCEPOWSBrokerURL je bio neispravno definiran. 
at filenet.ws.listener.http.WSListenerServlet.doGet(WSListenerServlet.java:690) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) 
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1214) 
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774) 
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456) 
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178) 
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125) 
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92) 
at com.filenet.ae.toolkit.server.servlet.filter.ThreadLocalCleanupFilter.doFilter(ThreadLocalCleanupFilter.java:40) 
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) 
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) 
at com.filenet.ae.servlet.filter.SecurityPluginFilter.doFilter(SecurityPluginFilter.java:162) 
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) 
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) 
at com.filenet.ae.toolkit.server.servlet.filter.PostprocessorFilter.doFilter(PostprocessorFilter.java:38) 
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) 
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) 
at com.filenet.ae.toolkit.server.servlet.filter.ContainerBasedFilter.doFilter(ContainerBasedFilter.java:228) 
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) 
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) 
at com.filenet.ae.toolkit.server.servlet.filter.SessionStateFilter.doFilter(SessionStateFilter.java:158) 
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) 
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) 
at com.filenet.ae.toolkit.server.servlet.filter.PreprocessorFilter.doFilter(PreprocessorFilter.java:118) 
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192) 
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89) 
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:926) 
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1023) 
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87) 
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:895) 
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662) 
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195) 
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458) 
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:522) 
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:311) 
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:282) 
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) 
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) 
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) 
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) 
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) 
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) 
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) 
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) 
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) 
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1783)       

Cause

The Object Store->Workflow System->General Tab->Process Orchestration hasn't been configured in ACCE

Diagnosing The Problem

The customer can point their browser to the following url
http://< /font><hostname>:9080/WorkplaceXT/P8BPMWSBroker/admin/help

If the problem is occurring, you will see the second line like this:
POURLS: NULL

Resolving The Problem

1. Go to ACCE, navigate to the Object Store->Workflow System->General Tab->Process Orchestration, input the following values:

Broker servlet URL: http://<hostname>:9080/ibmccepo
Public listener URL: http://<hostname>:9080/WorkplaceXT




2. Start the PTM by running routercmd.bat under IBM/FileNet/WebClient/Router as shown below:



Right click on “Component Managers” node, click “new”. Input the username and password as necessary. Here, this is all you need to do. You don’t have to start the component manager you just added.

Verify the configuration by going to the following url again
http://<hostname>:9080/WorkplaceXT/P8BPMWSBroker/admin/help

Confirm that the second line, POURLS has a value now. Then, you can perform what you were trying to perform and you shouldn’t get the 500 error and "Exception:No valid CCEPOWSBrokerURL was defined" error.

[{"Product":{"code":"SSNW2F","label":"FileNet P8 Platform"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Process Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"5.2","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21674626