Tuesday, 11 July 2017

Bootstrap cannot be run against WebSphere:cell=PSCell1,node=Node2,server=dmgr because it is not a BPM deployment target.

Another thing that makes me go "Hmmmm" …

I'm running the process to bootstrap an IBM BPM 8.5.7 Process Server: -

/opt/ibm/WebSphereProfiles/Dmgr01/bin/bootstrapProcessServerData.sh - clusterName AppCluster

and I see this: -

Bootstraping data for server at /opt/ibm/WebSphereProfiles/Dmgr01 and logging into /opt/ibm/WebSphereProfiles/Dmgr01/logs/bootstrapProcesServerData.log

WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
Bootstrap cannot be run against WebSphere:cell=PSCell1,node=Node2,server=dmgr because it is not a BPM deployment target.


Now I'm not just offended that we can't get the spelling of "bootstrapping" right - even though I pointed the error out to someone in 2012 :-)

But what else can you see ?

Yeah, it took me a minute ….

I'd copied and pasted the command from a PDF and, thanks to the vagaries of PDFs, a space has crept into the command: -

/opt/ibm/WebSphereProfiles/Dmgr01/bin/bootstrapProcessServerData.sh - clusterName AppCluster

between the hyphen ( - ) and clusterName.

Once I fixed the command: -

/opt/ibm/WebSphereProfiles/Dmgr01/bin/bootstrapProcessServerData.sh -clusterName AppCluster

#LifeIsGood again

Bootstraping data into cluster AppCluster and logging into /opt/ibm/WebSphereProfiles/Dmgr01/logs/bootstrapProcesServerData.AppCluster.log

WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
Activating snapshot 8.5.7.0 in process app TWP
Activating snapshot done: 8.5.7.0 in process app TWP
Activating snapshot 8.5.7.0 in process app SYSRP
Activating snapshot done: 8.5.7.0 in process app SYSRP
'BootstrapProcessServerData admin command completed successfully.....'

No comments: