Monday, 19 June 2017

NullPointerException seen when using BPMConfig.sh to create a second IBM BPM Deployment Environment

I saw this earlier whilst attempting to create a second Deployment Environment, of type Process Server, within an existing BPM Advanced 8.5.7 cell, which already had a Process Centre Deployment Environment therein: -

/opt/ibm/WebSphere/AppServer/bin/BPMConfig.sh -create -de /mnt/ResponseFiles/Advanced-PS-ThreeClusters-DB2.properties

Logging to file /opt/ibm/WebSphere/AppServer/logs/config/BPMConfig_20170619-153221.log.
The 'BPMConfig.sh -create -de /mnt/ResponseFiles/Advanced-PS-ThreeClusters-DB2.properties' command failed. For more information, see the log file /opt/ibm/WebSphere/AppServer/logs/config/BPMConfig_20170619-153221.log.

I checked the logs: -

cat /opt/ibm/WebSphere/AppServer/logs/config/BPMConfig_20170619-153221.log

[19/06/17 15:39:01:391 BST] 00000001 WccmHelper    < com.ibm.bpm.config.util.ws.WccmHelper getBPMCellConfigExtension RETURN null
[19/06/17 15:39:01:391 BST] 00000001 BPMConfig     E com.ibm.bpm.config.BPMConfig main <Null Message>
                                 java.lang.NullPointerException
at com.ibm.bpm.config.BPMConfig.checkCellScopedDB(BPMConfig.java:1097)
at com.ibm.bpm.config.BPMConfig.configureDeploymentEnvironment(BPMConfig.java:641)


cat /opt/ibm/WebSphere/AppServer/logs/config/ffdc_20170619-153853/ffdc.2985516112090437880.txt 

[19/06/17 15:39:01:404 BST]     FFDC Exception:java.lang.NullPointerException SourceId:com.ibm.bpm.config.BPMConfig.main ProbeId:202 Reporter:java.lang.Class@5f390df3
java.lang.NullPointerException
at com.ibm.bpm.config.BPMConfig.checkCellScopedDB(BPMConfig.java:1097)
at com.ibm.bpm.config.BPMConfig.configureDeploymentEnvironment(BPMConfig.java:641)
at com.ibm.bpm.config.BPMConfig$Actions.createDe(BPMConfig.java:4437)

This led me to check the properties file - - within which I had: -

bpm.cell.name=PSCell1

whereas it should've been: -

bpm.cell.name=PSCell1

because I'm adding a second DE to an existing cell, with its profiles, Deployment Manager and Nodes.

Once I changed it ….

No comments: