Wednesday, 13 February 2013

(L)user error when attempting to import a Deployment Environment into an IBM BPM Advanced 8.0.1 configuration

Whilst using a response file to import a Deployment Environment ( for Process Center ) into my newly minted IBM BPM Advanced 8.0.1 configuration, I saw this exception: -

WASX7209I: Connected to process "dmgr" on node PCDMNODENode using SOAP connector;  The type of process is: DeploymentManager
INFO: Importing the topology file /stage/inst/scripts/responseFiles/../PCDeployEnv.resp as deployment environment PCDeployEnv
INFO: Generating the artifacts for the deployment environment PCDeployEnv
WASX7017E: Exception received while running file "/stage/inst/scripts/createDepEnv.py"; exception information: com.ibm.wbiserver.nd.topology.exceptions.WBINDException: com.ibm.wbiserver.nd.topology.exceptions.WBINDException: Topology PCDeployEnv is not ready to be configured as its status is null


with this corresponding message in the Deployment Manager's SystemOut.log: -

[13/02/13 14:36:53:528 GMT] 0000001c WBITopologyCm W com.ibm.wbiserver.nd.topology.commands.WBITopologyCmdMgr validate CWLDB9025E: Deployment environment PCDeployEnv is invalid. Reason Role AppTarget's base runtime WPS is not supported by Node PCNODE1's runtime [].

Knowing that both Deployment Manager and Node profiles were of the right "type" : -

$ cat /opt/IBM/WebSphere/AppServer/properties/profileRegistry.xml

<?xml version="1.0" encoding="UTF-8"?><profiles>
    <profile isAReservationTicket="false" isDefault="true" name="PCDMNODE" path="/opt/IBM/WebSphere/AppServer/profiles/PCDMProfile" template="/opt/IBM/WebSphere/AppServer/profileTemplates/management">
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/BusinessSpace/dmgr.bspace"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/BPM/base/profileTemplates/dmgr.bpm"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/dmgr.wbicore"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/dmgr.bpc"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/dmgr.wbiserver"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/BPM/dmgr.procctr"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/BPM/dmgr.procctr.adv"/>
    </profile>
    <profile isAReservationTicket="false" isDefault="false" name="PCNODE1" path="/opt/IBM/WebSphere/AppServer/profiles/PCN1Profile" template="/opt/IBM/WebSphere/AppServer/profileTemplates/managed">
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/BusinessSpace/managed.bspace"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/BPM/base/profileTemplates/managed.bpm"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/managed.wbicore"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/managed.bpc"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/managed.wbiserver"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/BPM/managed.procctr"/>
        <augmentor template="/opt/IBM/WebSphere/AppServer/profileTemplates/BPM/managed.procctr.adv"/>
    </profile>

I knew the error must be somewhere else.

I looked back through my notes and, lo and behold, I'd forgotten to add ( federate ) my node into the DM-managed cell :-)

Can you say "Doh!" ?

Once I added the node into the cell ( using addNode.sh ) and removed the partially imported Deployment Environment, I re-ran my script to import the DE, and it went in like Flynn: -

WASX7209I: Connected to process "dmgr" on node PCDMNODENode using SOAP connector; The type of process is: DeploymentManager
INFO: Importing the topology file /stage/inst/scripts/responseFiles/../PCDeployEnv.resp as deployment environment PCDeployEnv
INFO: Generating the artifacts for the deployment environment PCDeployEnv

with corresponding happy messages in the DM's SystemOut.log: -

[13/02/13 14:44:20:965 GMT] 0000003e InstallSchedu I   ADMA5013I: Application RemoteAL61 installed successfully.
[13/02/13 14:44:54:517 GMT] 0000003f InstallSchedu I   ADMA5013I: Application REST Services Gateway installed successfully.
[13/02/13 14:45:48:713 GMT] 00000040 InstallSchedu I   ADMA5013I: Application IBM_BPM_Portal_PCSR01.AppTarget installed successfully.
[13/02/13 14:45:59:760 GMT] 00000041 InstallSchedu I   ADMA5013I: Application IBM_BPM_ProcessAdmin_PCSR01.AppTarget installed successfully.
[13/02/13 14:46:28:742 GMT] 00000042 InstallSchedu I   ADMA5013I: Application IBM_BPM_Teamworks_PCSR01.AppTarget installed successfully.
[13/02/13 14:46:36:421 GMT] 00000043 InstallSchedu I   ADMA5013I: Application IBM_BPM_WebAPI_PCSR01.AppTarget installed successfully.
[13/02/13 14:46:50:038 GMT] 00000044 InstallSchedu I   ADMA5013I: Application IBM_BPM_Help_PCSR01.AppTarget installed successfully.
[13/02/13 14:46:52:117 GMT] 00000045 InstallSchedu I   ADMA5013I: Application IBM_BPM_Repository_PCSR01.AppTarget installed successfully.
[13/02/13 14:47:00:841 GMT] 00000046 InstallSchedu I   ADMA5013I: Application IBM_BPM_PerformanceDW_PCSR01.Support installed successfully.
[13/02/13 14:47:06:796 GMT] 00000047 InstallSchedu I   ADMA5013I: Application mm.was_PCSR01.WebApp installed successfully.
[13/02/13 14:47:09:217 GMT] 00000048 InstallSchedu I   ADMA5013I: Application HumanTaskManagementWidgets_PCSR01.WebApp installed successfully.
[13/02/13 14:47:12:388 GMT] 00000049 InstallSchedu I   ADMA5013I: Application BSpaceHelp_PCSR01.WebApp installed successfully.


No comments: