Wednesday, 31 October 2018

IBM ODM - WASX7025E: Error found in String ""; cannot create ObjectName

Following on from earlier posts, I'm now building a Decision Server cluster: -

/opt/ibm/WebSphere/AppServer/profiles/Dmgr01/bin/createODMDecisionServerCluster.sh -clusterPropertiesFile /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/bin/odm/ODMDecisionServerCluster.properties -adminUsername wasadmin -adminPassword passw0rd

which almost immediately failed: -

Starting the cluster creation process, more traces are available in /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/odm

Creating ODM Decision Server cluster creation, please wait ...
ODM Decision Server cluster fail, please check /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/odm


I checked the logs: -

cat  /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/odm/step1-createODMDecisionServerCluster.log

...
WASX7017E: Exception received while running file "/opt/ibm/WebSphere/AppServer/profiles/Dmgr01/bin/odm/createODMDecisionServerCluster.py"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7025E: Error found in String ""; cannot create ObjectName.
...

I checked the source property file: -

cat /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/bin/odm/ODMDecisionServerCluster.properties

#
#   Licensed Materials - Property of IBM
#   5725-B69 5655-Y17 5655-Y31
#   Copyright IBM Corp. 1987, 2018. All Rights Reserved.
#
#   Note to U.S. Government Users Restricted Rights:
#   Use, duplication or disclosure restricted by GSA ADP Schedule
#   Contract with IBM Corp.
#

#
# Cluster base configuration 
#
cluster.name=DecisionServerCluster
virtualhost.name=default_host
res.console.server.name=RulesMgrSrv
# Specify a comma separated list of nodes to add in the cluster
cluster.member.nodes=Node1
res.console.node=Dmgr

cluster.servers.maxHeapSize=4096
cluster.servers.initialHeapSize=1096

# These JVM options are recommanded settings for better performance.
# You may have at lest 6 CPU cores to be able to enable it.
# To apply this recommandation please uncomment the following line
#cluster.servers.jvm.args=-Xgcpolicy:gencon -Xgcthreads6

#
# Database configuration
#   Supported database type:
#       - DB2
#       - Oracle
#       - MSSQL
#       - PostgreSQL
#
database.type=DB2
database.jdbcDriverPath=/opt/ibm/WebSphere/AppServer/universalDriver/lib/db2jcc4.jar;/opt/ibm/WebSphere/AppServer/universalDriver/lib/db2jcc_license_cu.jar
database.name=RESDB
database.hostname=workflow.uk.ibm.com
database.port=60006
database.user=db2user1
database.password=passw0rd

and realised where I'd gone wrong.

I had: -

res.console.node=Dmgr

whereas I should've had: -

res.console.node=Node1

as per this: -



Once I fixed it, all was well: -

/opt/ibm/WebSphere/AppServer/profiles/Dmgr01/bin/createODMDecisionServerCluster.sh -clusterPropertiesFile /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/bin/odm/ODMDecisionServerCluster.properties -adminUsername wasadmin -adminPassword passw0rd

Starting the cluster creation process, more traces are available in /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/odm

Creating ODM Decision Server cluster creation, please wait ...
Configuring ODM Decision Server datasource ...
Installing ODM Decision Server eXecution Unit ...
Installing ODM Decision Server RES Console ...
Installing ODM Decision Server HTDS in your cluster ...
Installing ODM Decision Server SSP in your cluster ...
Starting up your ODM Decision Server cluster ...
ODM Decision Server cluster statup invoked, it may make take a while before your cluster should be available.
Creating ODM Decision Server cluster configuration completed.




No comments:

GoLang - weirdness with "panic: assignment to entry in nil map"

I kept seeing this: - --- FAIL: TestClient (0.00s) panic: assignment to entry in nil map [recovered] panic: assignment to entry in nil ...