Question & Answer
Question
During deployment of CPE 5.5.4 users added context root prefix 'ecm' to CE (Content Engine). They did not apply the context root prefix 'ecm' to PE (Process Engine). While logging in from vwtool, users receive this error message:
Connecting to http://localhost:9080/ecm/peengine/api/petoolsapi
Error: java.lang.RuntimeException: Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri: /ecm/peengine/api/petoolsapi
Error: java.lang.RuntimeException: Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri: /ecm/peengine/api/petoolsapi
Why does vwtool look for context root prefix 'ecm/' while Process Engine is not deployed with it?
Cause
Customer deployed the CPE with the following context root:
Context root for Engine-init.war: ecm/FileNet
Context root for Engine-health.war: ecm/P8CE
Context root for IBM Filenet P8 CEWS: ecm/wsi
Context root for IBM Filenet BPM PEWSI: pewsi
Context root for IBM Contect Case Engine: peengine
Context root for Engine-health.war: ecm/P8CE
Context root for IBM Filenet P8 CEWS: ecm/wsi
Context root for IBM Filenet BPM PEWSI: pewsi
Context root for IBM Contect Case Engine: peengine
The WcmApiConfig.properties value is set to match. This is about CE URL (cpeuri vs peuri)
RemoteServerURL = http://ECMDEMO1:9080/ecm/wsi/FNCEWS40MTOM/
RemoteServerURL = http://ECMDEMO1:9080/ecm/wsi/FNCEWS40MTOM/
Users did not deploy the context root prefix 'ecm' for PE as they did for CE.
Answer
The vwtool unable to find URI /ecm/peengine/api/petoolsapi because the peengine is deployed without context root prefix 'ecm'. The context root prefix 'ecm' should be deployed for both CE and PE in order for vwtool to work such as the following:
Context root for Engine-init.war: ecm/FileNet
Context root for Engine-health.war: ecm/P8CE
Context root for IBM Filenet P8 CEWS: ecm/wsi
Context root for IBM Filenet BPM PEWSI: ecm/pewsi
Context root for IBM Contect Case Engine: ecm/peengine
Context root for Engine-health.war: ecm/P8CE
Context root for IBM Filenet P8 CEWS: ecm/wsi
Context root for IBM Filenet BPM PEWSI: ecm/pewsi
Context root for IBM Contect Case Engine: ecm/peengine
Note, whatever prefix the site uses must be consistent for both the CE and PE context roots. In theory, they can use whatever is allowed (in terms of characters, special characters, etc.). The term "ecm" in this use case is just an example.
Be aware that if users make use of context root prefix during deployment, it is a requirement that context root prefix of CE and PE to be matched.
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNW2F","label":"FileNet P8 Platform"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB45","label":"Automation"}}]
Product Synonym
CPE 5.5.4
Was this topic helpful?
Document Information
Modified date:
01 July 2020
UID
ibm16242352