IBM Support

Test connection or Bootstrapped EAR file error when creating profile for CPE

Troubleshooting


Problem

Bootstrapped Ear fails to create when using FileNet P8 Content Platform Engine (CPE) command line Configuration Manager tool. Using Configuration Manager graphical user interface (CMUI) test connection fails.

Symptom


    Running the command line command: configmgr_cl execute -profile <profile_name>

      Error:  
      The task Deploy Application has the following invalid property values:
      Bootstrapped EAR file:
      The path or file does not exist.

    Running CMUI to create or edit the WebSphere Application Server properties, click Test Connection errors:

      Connection error:  Verify your application server port number and confirm that the application server is running.

    WebSphere error reported:

      !ENTRY com.ibm.ecm.configmgr.app.ce 4 0 2013-06-25 16:25:24.030
      !MESSAGE An error occurred while retrieving the cell name from the
      specified web application server.
      WebSphere:process=as-c85dv5-a-2-fntcpe52-2,type=ConfigService,*
      !STACK 0
      com.ibm.ecm.configmgr.engine.ConfigurationManagerException: An error
      occurred while retrieving the cell name from the specified web
      application server.
      WebSphere:process=as-c85dv5-a-2-fntcpe52-2,type=ConfigService,*
      at
      com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethod
      s(JMXInvoker.java:238)
      at
      com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethod
      (JMXInvoker.java:142)
      at
      com.ibm.ecm.configmgr.engine.jmx.WebSphereJMXInvoker.connect(WebSphereJM
      XInvoker.java:85)
      at
      ...
      Caused by: javax.management.InstanceNotFoundException:
      WebSphere:process=as-c85dv5-a-2-fntcpe52-2,type=ConfigService,*
      at
      com.ibm.websphere.management.configservice.ConfigServiceProxy.<init>(Con
      figServiceProxy.java:67)
      at
      com.ibm.ecm.configmgr.utils.websphere.WebSphereJMXUtil.getCells(WebSpher
      eJMXUtil.java:306)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at
      sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
      a:60)
      at
      sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
      Impl.java:37)
      at java.lang.reflect.Method.invoke(Method.java:611)
      at
      com.ibm.ecm.configmgr.engine.jmx.JMXInvoker.invokeConnectMethodAndMethod
      s(JMXInvoker.java:198)
      ... 20 more

Cause

The port provided for the Application server SOAP port is incorrect. When Content Engine is installed on WebSphere Application Server Network Deployment (WAS ND), the SOAP port provided when creating the configuration profile (either via the command line utility or CMUI) must be that of the Deployment Manager and not an individual node.

Environment

WebSphere Application Server Network Deployment.

Diagnosing The Problem

Determine the SOAP port on the Deployment Manager (DMGR)

  1. Launch the WebSphere Console
  2. Navigate to System administration > Deployment Manager
  3. Under Additional Properties, select Ports
  4. The SOAP port for the DMGR is named SOAP_CONNECTOR_ADDRESS (the default port is 8879)

Note: For WAS ND, you can not use a SOAP_CONNECTOR_ADRESS for an individual server. The SOAP ports for individual servers are found in the WAS console under Servers > Application servers> your_server> Ports. If a port for an individual server was used in the profile for the Application Server SOAP port, change it to the SOAP port listed under System administration > Deployment Manager > Ports.

Resolving The Problem

Use the steps above to locate the correct DMGR SOAP port, then follow either the command line or CMUI steps below to correct the Appication Server SOAP port entry to the DMGR SOAP port:

Steps if using the Command line configmgr:

  1. Edit the applicationserver.xml and correct the entry for the Application Server SOAP port to the soap port for the DMGR.
  2. Retry the command to create the profile:
    • configmgr_cl execute -profile <profile_name>
Steps using the graphical CMUI:
  1. File, Edit Application Server Properties...
  2. Change the Application server SOAP port to the SOAP port for the DMGR.
  3. Click Test Connection to validate.
[{"Product":{"code":"SSNW2F","label":"FileNet P8 Platform"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Content Engine","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"5.0;5.1;5.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

More support for:
FileNet P8 Platform

Software version:
5.0, 5.1, 5.2

Operating system(s):
Windows, AIX, HP-UX, Linux, Solaris

Document number:
227649

Modified date:
17 June 2018

UID

swg21643922

Page Feedback