P8BPMWSBroker.properties demystified
Document was originally created on 4 March 2008
Document was updated on 24 Feb 2010
Document was updated on 24 Feb 2010
Document was moved to the new system and some data generalized on 2 March 2022
This document describes the properties stored in the P8BPMWSBroker.properties file. They are grouped here according to the components that set them.
This file is laid down during the PE client installation on the application engine, stored in the installed directory of the P8 application engine (AE/XT)’s WEB-INF directory. It contains properties necessary for the configuration of Process Orchestration. Figure 1 shows the different components

Note that most of the keys are suffixed with .<connectionPointName>, to denote that those are the values for that particular connection point. The ones without the suffix serve as the “starting” or default values for connection points that are not yet created (for the Component Manager)... Potentially, when there are multiple CMs with the same connection point name (different queues), the values can be overwritten unpredictably. The recommendation is when different queues is used for starting CM, only one is processing WS-Request queue, then only use that instance to set the values for Web Services-related properties.
The router.path property is required, since this contains the real location for the file, that is, the installed directory of Workplace or Workplace XT web application.
The ramifications are:
- P8BPMWSBroker servlet needs credentials and connection information to log on to the PE server when a WSDL is requested
- This information can then be supplied by the Process Task Manager UI.
- However, PTM only knows about the installed directory of Workplace/WorkplaceXT, since it is set on the classpath.
- Therefore, the router.path is set to enable the P8BPMWSBroker servlet to get to the information.
P8BPMWSBroker servlet need the following properties:
- router.path for the real location of the file
- listener.connection, filenet.pe.bootstrap.ceuri, cm.uid (pw if not encoded), cm.name (username, or -1 if encoded pw) to authenticate with the PE
If any of those properties are missing, we have a problem getting the WSDL... HTTP 500 error!!!
Note to rebuild a corrupted P8BPMWSBroker.properties file, the following sequence is suggested:
- Stop Process Task manager, App server.
- Make sure that the P8BPMWSBroker.properties of both installed and deployed directories have the router.path to be: router.path=c\:/Program Files/FileNet/AE/Workplace/WEB-INF
- Remove problematic properties (filenet.pe.bootstrap.ceuri typically) ** when the infamous testdom is set for this property, will need to create a WEB-INF\classes subdirectory for the deployed Workplace\WEB-INF directory and put the WcmApiConfig.properties there **
- Restart the Process Task Manager.
- Create or reapply an instance of Component Manager for the connection point being used by the applet. This sets the cm.uid, cm.name, and cm.router
- Restart the app server and invoke one of the Process applet again (in example Process Designer). This sets the listener.connection and filenet.pe.bootstrap.ceuri properties.

Process Task Manager and Component Manager expect that the properties file should be in the classpath. Thus
you’d see that <installed directory>\WEB-INF is in their classpaths.
P8BPMWSBroker and vwsoaprouter servlet discovered the file by getting the Servlet Context path + /WEB-
INF. From the file, they use router.path to get to the real location.
The file location can also be passed to the processes by specifying this system property
filenet.ws.listener.properties.location, in example
-Dfilenet.ws.listener.properties.location=C:\myloc
#P8BPM WS Listener/WS Request Properties
#Tue Mar 04 08:56:34 PST 2008
Initial Values
router.path=c\:/Program Files/FileNet/AE/Workplace/WEB-INF
aeinstallhome.path=C\:/Program Files/FileNet/AE
This box represents properties that are set by Process Task Manager on the AE
General Tab
cm.router=TestServer_600
cm.router.TestServer_600=TestServer_600
cm.uid=TESTjQT6oj5HekeMmh1zsB1U+N8NahyM000\=
cm.uid.TestServer_600=TESTjQT6oj5HekeMmh1zsB1U+N8NahyM000\=
cm.name=-1
cm.name.TestServer_600=-1
cm.CEURI=http\://TestServer02\:9080/wsi/FNCEWS40DIME/
cm.CEURI.TestServer_600=http\://TestServer02\:9080/wsi/FNCEWS40DIME/
Web Services/Web Services Setting tab
listener.base.url=http\://TestServer02\:9080/Workplace/P8BPMWSBroker
listener.base.url.TestServer_600=http\://TestServer02\:9080/Workplace/P8BPMWSBroker
listener.local.host=TestServer02\:9080
listener.local.host.TestServer_600=TestServer02\:9080
filenet.ws.request.concurrent.threads=1
filenet.ws.request.concurrent.threads.TestServer_600=1
Web Services/JSSE Settings tab
cm.truststore=C\:\\Program Files\\FileNet\\AE\\Router\\JRE/lib/security/cacerts
cm.certificates.autoaccept=true
cm.truststore.uid=TESTnl9Jr7bTnkGFahaLbx0000\=\=
cm.truststore.TestServer_600=C\:\\Program
Files\\FileNet\\AE\\Router\\JRE/lib/security/cacerts
cm.keystore.uid=TESTnl9Jr7bTnkGFaxiPahe000\=\=
cm.keystore.uid.TestServer_600=TESTnl9Jr7bTnkGFaxiPahe000\=\=
cm.truststore.uid.TestServer_600=TESTnl9Jr7bTnkGFahaLbx0000\=\=
cm.keystore=C\:\\Program Files\\FileNet\\AE\\Router\\JRE/lib/security/cacerts
cm.keystore.TestServer_600=C\:\\Program Files\\FileNet\\AE\\Router\\JRE/lib/security/cacerts
listener.connectionpoint=TestServer_600
cm.certificates.autoaccept.TestServer_600=true
Web Services/Reliable Messaging Settings tab
filenet.wsrm.acknowledgement.interval=200
filenet.wsrm.acknowledgement.interval.TestServer_600=200
filenet.wsrm.client.listener.port=3462
filenet.wsrm.client.listener.port.TestServer_600=3462
filenet.wsrm.inactivity.timeout=600000
filenet.wsrm.inactivity.timeout.TestServer_600=600000
filenet.wsrm.base.retransmission.interval=3000
filenet.wsrm.base.retransmission.interval.TestServer_600=3000
These properties are used by WSRequest(0)/Advanced Adaptor (after CM is started
cm.ws.request.polling.interval=5000
cm.ws.request.max.polling.interval=60000
These properties are set by P8BPMWSBroker servlet. The values are discovered via
searching for WcmApiConfig.properties in the servlet’s classpath. Note that WEB-INF Is not
in servlet classpath – it’s added manually by PE code after cannot find
WcmApiConfig.properties in the classpath. WEB-INF\classes is though....
filenet.pe.bootstrap.ceuri=iiop\://TestServer02\:2809/FileNet/Enginefilenet.pe.bootstrap.ceuri.hqruby_600=iiop\://TestServer02\:2809/FileNet/Engine
This property is set by vwsoaprouter servlet when applets access the appserver, the
property is used by P8BPMWSBroker servlet to make sure that it’s using the same
connection point with the applets
listener.connectionpoint.TestServer_600=TestServer_600
property is used by P8BPMWSBroker servlet to make sure that it’s using the same
connection point with the applets
listener.connectionpoint.TestServer_600=TestServer_600
These properties are set automatically when the file was first accessed, typically by
Process Task Manager with default values. They are not exposed via UI, but can be
manually modified using a text editor to trigger certain behaviors such as tracing,
caching, tracking SOAP requests via HTTP filter etc.
filenet.ws.request.cache.timeout=4
filenet.ws.listener.cache.timeout=4
filenet.pe.po.tracking.TestServer_600=true
filenet.pe.po.tracking=true
att.handler=filenet.vw.idm.trident.WSSession
PORT.ASSIGNMENT.DONE.BY=filenet.ws.listener.http.WSListenerServlet.checkCPNameInPathInfo(
WSListenerServlet.java\:493)
last.updated=2008.03.04 08\:56\:34 at
filenet.ws.listener.http.WSListenerServlet.getCEURI(WSListenerServlet.java\:1617), object
created by
filenet.ws.listener.http.WSListenerServlet.getWSListenerProperties(WSListenerServlet.java
\:206)
filenet.wsrm.client.listener.host=localhost
filenet.wsrm.client.listener.port.next=3463
For tracing SOAP messages coming out of WS-Request in CM
filenet.ws.request.tracing=true
filenet.ws.request.tracefile=c\:\\wsinvoke.log
filenet.ws.request.tracefilesize=5000000
For tracing SOAP messages coming into P8BPMWSBroker servlet in Workplace
filenet.ws.listener.tracing=true
filenet.ws.listener.tracefile=c\:\\wsinvoke.log
filenet.ws.listener.tracefilesize=5000000