Thursday, 20 September 2018

IBM Business Automation Workflow (BAW) and the Insufficient Memory

I'm just getting to grips with the (relatively) new package, IBM Business Automation Workflow (BAW), which includes new ( to me ) ECM capabilities such as Content Navigator.

Having installed the binaries: -

com.ibm.cic.agent_1.8.9001.20180709_1302
com.ibm.bpm.ADV.v85_8.6.10018001.20180628_0740
com.ibm.websphere.ND.v85_8.5.5013.20180112_1418
8.6.10018001-WS-BPM-IFJR59569_8.6.10018001.20180829_1311
8.6.10018001-WS-BPM-IFJR59939_8.6.10018001.20180905_0257
8.6.10018001-WS-BPMPCPD-IFPD59569_8.6.10018001.20180829_1322


and updated the Deployment Environment (DE) properties file, I started to create the DE: -

/opt/ibm/WebSphere/AppServer/bin/BPMConfig.sh -create -de ~/Advanced-PC-ThreeClusters-DB2.properties

This ran for a while ( whilst I was out at lunch ) and then borked with: _

...
The HTTP and HTTPS ports for server MEClusterMember1 on node Node1 are added to the virtual hosts list.
The HTTP and HTTPS ports for server AppClusterMember1 on node Node1 are added to the virtual hosts list.
/opt/ibm/WebSphere/AppServer/bin/BPMConfig.sh: line 87:  7581 Killed                  "$JAVA_HOME/bin/java" $EXTRA_X_ARG $WAS_DEBUG $CONSOLE_ENCODING $CUSTOMPWDPROPS -Declipse.bundle.setTCCL=false -Dws.ext.dirs="$WAS_EXT_DIRS" -Djava.endorsed.dirs="$WAS_ENDORSED_DIRS" -Dwas.install.root="$WAS_HOME" $PERF_JVM_OPTIONS ${JAASSOAP:+"$JAASSOAP"} $WAS_LOGGING $EXTRA_D_ARG $JVM_EXTRA_CMD_ARGS -classpath "$WAS_CLASSPATH":"$WAS_HOME"/lib/j2ee.jar:"$WAS_HOME"/BPM/Lombardi/lib/xbean.jar:"$WAS_HOME"/plugins/com.ibm.ws.prereq.rxa.jar:"$WAS_HOME"/ECMClient/updateUserInfo.jar:"$WAS_HOME"/properties com.ibm.wsspi.bootstrap.WSPreLauncher -nosplash -application com.ibm.ws.bootstrap.WSLauncher com.ibm.bpm.config.BPMConfig "$@"



with no other obvious symptoms.

Working on a hunch, I checked the free memory on my Red Hat Enterprise Linux (RHEL) VM :-

free 

              total        used        free      shared  buff/cache   available
Mem:        1865252      482608      972292        3200      410352     1194476
Swap:       2138108      726300     1411808


Using the assumption that 1.8 GB may well NOT be enough to build the DE etc. I quadrupled the RAM in the VM, and rebooted.

Now it looks better: -

 free 

              total        used        free      shared  buff/cache   available
Mem:        7992312      543908     6665304       59204      783100     7115580
Swap:       2138108           0     2138108


More importantly ….

...
The HTTP and HTTPS ports for server MEClusterMember1 on node Node1 are added to the virtual hosts list.
The HTTP and HTTPS ports for server AppClusterMember1 on node Node1 are added to the virtual hosts list.
The HTTP and HTTPS ports for server SupClusterMember1 on node Node1 are added to the virtual hosts list.
Configuring the REST services end points.
Saving configuration changes...
Synchronizing node Node1.
ADMU0116I: Tool information is being logged in file
           /opt/ibm/WebSphere/AppServer/profiles/AppSrv01/logs/syncNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0401I: Begin syncNode operation for node Node1 with Deployment Manager
           workflow.uk.ibm.com: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node Node1 has been synchronized with
           Deployment Manager workflow.uk.ibm.com: 8879
Stopping deployment manager profile Dmgr01.
ADMU0116I: Tool information is being logged in file
           /opt/ibm/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr/stopServer.log
ADMU0128I: Starting tool with the Dmgr01 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3201I: Server stop request issued. Waiting for stop status.
ADMU4000I: Server dmgr stop completed.

The 'BPMConfig.sh -create -de /home/wasadmin/Advanced-PC-ThreeClusters-DB2.properties' command completed successfully.


Coincidence ?

Methinks not !

Synology DS414 - From Megabits to Gigabits

I'd noticed that my DS414 was, for no obvious reason, only giving me 100 Mb/s on ONE of the two Ethernet interfaces: -


The solution ?

Switch the Ethernet cable …..

Like most folks, I have a huge Box O' Bits, including a bunch of Ethernet cables - so I picked a nice Cat. 6 cable, which did the job nicely :-)

I need to ditch the old "faulty" cable 'cos who wants 100 Mb/s when one can have 1000 Mb/s :-)

Now this is what I get: -


Nice :-)

Wednesday, 19 September 2018

Re-using someone else's brilliance - Figuring out CPUs and Sockets - Updated!

I found this: -


whilst helping a colleague dig into the underlying capacity of a multi-socket / core Linux box.

The article includes tips such as: -

lscpu | grep "socket"

Core(s) per socket:    1

cat /proc/cpuinfo | grep "physical id" | sort -u | wc -l

4

egrep -e "core id" -e ^physical /proc/cpuinfo|xargs -l2 echo|sort -u

physical id : 0 core id : 0
physical id : 2 core id : 0
physical id : 4 core id : 0
physical id : 6 core id : 0


dmidecode | grep -i product


Product Name: VMware Virtual Platform
Product Name: 440BX Desktop Reference Platform


grep -i "physical id" /proc/cpuinfo | sort -u | wc -l 

4

dmidecode |grep -i cpu

Socket Designation: CPU #000
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #001
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #002
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #003
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #004
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #005
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #006
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #007
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #008
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #009
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Socket Designation: CPU #010
Version: Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz

...

cat /proc/cpuinfo |egrep 'sibling|cores'

siblings : 1
cpu cores : 1
siblings : 1
cpu cores : 1
siblings : 1
cpu cores : 1
siblings : 1
cpu cores : 1


grep -i "processor" /proc/cpuinfo | sort -u | wc -l 

4

lscpu | grep -i thread

Thread(s) per core:    1

dmidecode -t4 | egrep 'Designation|Status'

Socket Designation: CPU #000
Status: Populated, Enabled
Socket Designation: CPU #001
Status: Populated, Enabled
Socket Designation: CPU #002
Status: Populated, Enabled
Socket Designation: CPU #003
Status: Populated, Enabled
Socket Designation: CPU #004
Status: Populated, Disabled By BIOS
Socket Designation: CPU #005
Status: Populated, Disabled By BIOS


etc.

Nice find !!

Aide Memoire - Auto-starting DB2 on RHEL 7

More fun with DB2 auto-starting on Linux: -

/opt/ibm/db2/V11.1/bin/db2level 

DB21085I  This instance or install (instance name, where applicable: 
"db2inst1") uses "64" bits and DB2 code release "SQL11012" with level 
identifier "0203010F".
Informational tokens are "DB2 v11.1.2.2", "s1706091900", "DYN1701310100AMD64", 
and Fix Pack "2".
Product is installed at "/opt/ibm/db2/V11.1".


cat /etc/redhat-release 

Red Hat Enterprise Linux Server release 7.5 (Maipo)

So the instances were not auto-starting …

I checked all of the following: -

As db2inst1

db2set DB2AUTOSTART=YES

db2greg -getinstrec instancename="db2inst1"

Retrieved record:
   Service      = |DB2|
   Version      = |11.1.2.2|
   InstanceName = |db2inst1|
   InstancePath = |/home/db2inst1/sqllib|
   Usage        = |N/A|
   StartAtBoot  = 1
   Maintenance  = 0
   InstallPath  = |/opt/ibm/db2/V11.1|
   RemoteProf   = |N/A|
   Comment      = |N/A|




As db2inst2

db2set DB2AUTOSTART=YES

db2greg -getinstrec instancename="db2inst2"

Retrieved record:
   Service      = |DB2|
   Version      = |11.1.2.2|
   InstanceName = |db2inst2|
   InstancePath = |/home/db2inst2/sqllib|
   Usage        = |N/A|
   StartAtBoot  = 1
   Maintenance  = 0
   InstallPath  = |/opt/ibm/db2/V11.1|
   RemoteProf   = |N/A|
   Comment      = |N/A|


As root

cat /etc/systemd/system/db2fmcd.service 

# DB2 fault monitor 
# Starts fmcd
# Note: any customizations to this file will be lost the next time this is updated

[Unit]
Description=DB2 v11.1.2.2

[Service]
ExecStart=/opt/ibm/db2/V11.1/bin/db2fmcd
Restart=always

[Install]
WantedBy=default.target

ls -al /opt/ibm/db2/V11.1/bin/db2fmcd

-r-xr-xr-x. 1 bin bin 176288 Sep 17 13:18 /opt/ibm/db2/V11.1/bin/db2fmcd

/opt/ibm/db2/V11.1/instance/db2iset -i db2inst1 -all

[i] DB2COMM=TCPIP
[i] DB2AUTOSTART=YES
[g] DB2SYSTEM=lt.uk.ibm.com
[g] DB2ADMINSERVER=dasusr1


/opt/ibm/db2/V11.1/instance/db2iset -i db2inst2 -all

[i] DB2COMM=TCPIP
[i] DB2AUTOSTART=YES
[g] DB2SYSTEM=lt.uk.ibm.com
[g] DB2ADMINSERVER=dasusr1


systemctl |grep -i db2

db2fmcd.service                                                    loaded active running   DB2 v11.1.2.2

ps -ef | grep db2fm

root        793      1  0 10:34 ?        00:00:00 /opt/ibm/db2/V11.1/bin/db2fmcd
dasusr1    1540      1  0 10:35 ?        00:00:00 /opt/ibm/db2/V11.1/das/bin/db2fmd -i dasusr1 -m /opt/ibm/db2/V11.1/das/lib/libdb2dasgcf.so.1


/opt/ibm/db2/V11.1/bin/db2fm -i db2inst1 -U
/opt/ibm/db2/V11.1/bin/db2fm -i db2inst1 -u

/opt/ibm/db2/V11.1/bin/db2fm -i db2inst2 -U
/opt/ibm/db2/V11.1/bin/db2fm -i db2inst2 -u


/opt/ibm/db2/V11.1/bin/db2fm -i db2inst1 -s

Gcf module '/opt/ibm/db2/V11.1/lib64/libdb2gcf.so' is INSTALLED PROPERLY but NOT ALIVE

/opt/ibm/db2/V11.1/bin/db2fm -i db2inst2 -s

Gcf module '/opt/ibm/db2/V11.1/lib64/libdb2gcf.so' is INSTALLED PROPERLY but NOT ALIVE

/opt/ibm/db2/V11.1/bin/db2fm -i db2inst1 -S

Gcf module 'fault monitor' is NOT operable

/opt/ibm/db2/V11.1/bin/db2fm -i db2inst2 -S

Gcf module 'fault monitor' is NOT operable

Finally …..

The following appeared to resolve things: -

/opt/ibm/db2/V11.1/bin/db2fm -i db2inst1 -f on

/opt/ibm/db2/V11.1/bin/db2fm -i db2inst2 -f on

in that both DB2 instances ( and thus the listeners ) now start on reboot :-) 

Yay!

Tuesday, 18 September 2018

Things that make me go "Hmmm" #12312 - DB2

I was seeing this: -

[18/09/18 13:09:51:395 BST] 0000009f DSConfigurati W   DSRA8201W: DataSource Configuration: DSRA8040I: Failed to connect to the DataSource jdbc/mashupDS.  Encountered java.sql.SQLException: [jcc][t4][10262][11223][4.21.29] Unexpected Throwable caught: null. ERRORCODE=-4228, SQLSTATE=null DSRA0010E: SQL State = null, Error Code = -4,228.

when testing a newly created BPM 8.6 environment.

Having confirmed that DB2 was up-and-running, and that there wasn't a firewall in the way ( both WAS and DB2 are on the same box ), I started digging into the JDBC provider - DB2 Using IBM JCC Driver (XA) - and checked the class path: -

${DB2_JCC_DRIVER_PATH}/db2jcc4.jar
${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar
${DB2_JCC_DRIVER_PATH}/db2jcc_license_cisuz.jar
${PUREQUERY_PATH}/pdq.jar
${PUREQUERY_PATH}/pdqmgmt.jar


and the native path: -

${DB2_JCC_DRIVER_NATIVEPATH}

the latter of which we can ignore as we're using a Type 4 JDBC driver ( db2jcc4.jar ).

I then checked the relevant WebSphere variables: -

DB2_JCC_DRIVER_PATH = ${WAS_INSTALL_ROOT}/jdbcdrivers/DB2  
UNIVERSAL_JDBC_DRIVER_PATH = ${WAS_INSTALL_ROOT}/jdbcdrivers/DB2  
WAS_INSTALL_ROOT = /opt/ibm/WebSphere/AppServer  


and finally checked the files: -

ls -al /opt/ibm/WebSphere/AppServer/jdbcdrivers/DB2

total 3812
drwxr-xr-x. 2 wasadmin wasadmins      83 Sep 18 11:59 .
drwxr-xr-x. 3 wasadmin wasadmins      16 Sep 18 11:59 ..
-rw-r--r--. 1 wasadmin wasadmins 3894263 Sep 18 11:59 db2jcc4.jar
-rw-r--r--. 1 wasadmin wasadmins    2068 Dec  8  2017 db2jcc_license_cisuz.jar
-rw-r--r--. 1 wasadmin wasadmins    1534 Dec  8  2017 db2jcc_license_cu.jar


against that which is provided with my DB2 environment ( v11.1.2.2 ): -

ls -al /opt/ibm/db2/V11.1/java/db2jcc4.jar

-r--r--r--. 1 bin bin 3924511 Jun 11  2017 /opt/ibm/db2/V11.1/java/db2jcc4.jar

Just in case it was a driver conflict, I copied the DB2 driver across: -

mv /opt/ibm/WebSphere/AppServer/jdbcdrivers/DB2/db2jcc4.jar /opt/ibm/WebSphere/AppServer/jdbcdrivers/DB2/db2jcc4.RAJ

cp /opt/ibm/db2/V11.1/java/db2jcc4.jar /opt/ibm/WebSphere/AppServer/jdbcdrivers/DB2

and restarted the Node Agent.

This time around, I got: -

[18/09/18 14:02:54:556 BST] 00000072 DSConfigurati W   DSRA8201W: DataSource Configuration: DSRA8040I: Failed to connect to the DataSource jdbc/mashupDS.  Encountered java.sql.SQLException: null DSRA0010E: SQL State = 58031, Error Code = -1,031.
java.sql.SQLException: null DSRA0010E: SQL State = 58031, Error Code = -1,031


At this point, I started to doubt myself, and double-checked the DB2 server: -

su - db2inst2
db2 list db directory

 System Database Directory

 Number of entries in the directory = 0

Hmmmmm :-( 

Then I realised …..

When I created the databases, I did so as the WRONG USER 

My DB2 server is hosting databases for BOTH MDM *AND* BPM.

The MDM database is hosted by the db2inst1 instance and the BPM databases should be hosted by the db2inst2 instance.

Yes, you've guessed it - I did this: -

su - db2inst1

when I created the BPM databases, rather than this: _

su - db2inst2

Can you say PEBCAK ? I bet you can ……

IBM Master Data Management - "Cannot invoke Configure_MasterDataManagement for RDM installation"

Whilst building out a MDM Advanced Edition 11.6.0.5 box: -

cd /opt/ibm/MDM/mds/scripts
./madconfig.sh Configure_MasterDataManagement

Buildfile: build.xml
Trying to override old definition of task executeUpdateScript

initialize_taskdef_libs:

Configure_MasterDataManagement:
Cannot invoke Configure_MasterDataManagement for RDM installation

BUILD SUCCESSFUL
Total time: 1 second


Hmmmm

Thankfully, there's a -debug switch: -

./madconfig.sh -debug Configure_MasterDataManagement

but that didn't tell me much more: -

Configure_MasterDataManagement:
Setting project property: tstamp.Configure.MasterDataManagement -> 20180917155806
Override ignored for property DSTAMP
Override ignored for property TSTAMP
Override ignored for property TODAY
setting a recorder for name ../../logs/madconfig/Configure_MasterDataManagement_20180917155806.log
Property ${user.mdm.im.offering.id} has not been set
Cannot invoke Configure_MasterDataManagement for RDM installation

BUILD SUCCESSFUL
Total time: 1 second

Similarly, nothing much of use in the log: -

locate Configure_MasterDataManagement_20180917155806.log

cat /opt/ibm/MDM/logs/madconfig/Configure_MasterDataManagement_20180917155806.log

Cannot invoke Configure_MasterDataManagement for RDM installation

BUILD SUCCESSFUL


I double-checked that I had installed MDM: -

/opt/ibm/InstallationManager/eclipse/tools/imcl listInstalledPackages -features

com.ibm.cic.agent_1.8.9001.20180709_1302 : 
com.ibm.websphere.ND.v85_8.5.5013.20180112_1418 : com.ibm.sdk.6_64bit,ejbdeploy,embeddablecontainer,thinclient
com.ibm.mdm.advanced.0.5_11.6.0.FP05IF000_20180326-1642 : com.ibm.mdm.install.feature
com.ibm.mdm.mdph.0.5_11.6.0.FP05IF000_20180326-1642 : com.ibm.mdm.ds.ui.feature

I even went down the rabbit hole of Java SDKs, wondering whether the fact that I only had Java 8 installed …..

but it wasn't that

...

In a fit of pique, I uninstalled and reinstalled the MDM binaries etc.

...

and then realised what the problem was …..

Yes, it's another PEBCAK ….

My notes said, in part: -

Setup MDM Installer Properties File

vi /opt/ibm/MDM/properties/mdm_install.properties


which is fine ….

*BUT* I then simply REPLACED ALL OF THE CONTENT OF THATFILE with a few lines: -

user.was.password=passw0rd
user.db.password=passw0rd
user.was.admin.password=passw0rd
user.bla.name=passw0rd
user.bla.password=passw0rd
user.mq.password=passw0rd
user.kafka.statistics.enable=no
user.table.space.4k=TBS4K
user.table.space.8k=TBS8K
user.table.space.16k=TBS16K
user.table.space.index=IDXSPACE
user.table.space.long=LOBSPACE
user.table.space.eme.1=EMESPACE1
user.table.space.eme.2=EMESPACE2
user.was.type=ND
user.was.profile.home=/opt/ibm/WebSphere/AppServer/profiles/AppSrv01/
user.deploy.port=8879
user.deploy.host=lt.uk.ibm.com
user.was.cell=MDMCell1
user.was.node=lt86Node01
user.was.server=MDMClusterMember1
user.was.cluster=MDMCluster
user.was.cluster.flag=true
user.trust.file.url=/opt/ibm/WebSphere/AppServer/profiles/AppSrv01/etc/DummyClientTrustFile.jks

In other words, I replaced ~200 lines of probably quite important stuff with 24 lines of my own custom stuff, meaning that I had lost lines such as: -

wcc.install.home=/opt/ibm/MDM
user.mdm.bla.name=MDM-operational-server-EBA-E001
user.mdm.bla.description=MDMBLA

all of which are rather important.

The moral of the story ?

Update the documentation to say "APPEND" rather than "REPLACE"

….

./madconfig.sh Configure_MasterDataManagement

Buildfile: build.xml
Trying to override old definition of task executeUpdateScript

initialize_taskdef_libs:
Trying to override old definition of task EncryptDBPassword

Configure_MasterDataManagement:


--------------                                           ------------ 
--------------          Installing Feature Pack 11.6.0.5 ------------ 
--------------                                           ------------ 


Trying to override old definition of task executeUpdateScript
Trying to override old definition of task EncryptDBPassword
Trying to override old definition of task executeUpdateScript

ComponentDisplay:
#################################################################################
# #
# The following features will be configured in this process #
# - Database  #
# - Operation Server #
# - Consent Management UI #
# #
#################################################################################
set JAVA_EXT_DIRS=/opt/ibm/WebSphere/AppServer/java_1.7.1_64/jre/lib/ext
NOTE:  all specified passwords already encoded in target file == /opt/ibm/MDM/mds/scripts/soap.client.props


Now isn't that better ?

Thursday, 13 September 2018

WebSphere Application Server - _setupsdk1.6_64.sh: No such file or directory

I saw this: -

/opt/ibm/InstallationManager/eclipse/tools/imcl -input /mnt/ResponseFiles/upgradeBPM857_to_86.rsp -acceptLicense

Updated to com.ibm.bpm.ADV.v85_8.6.201803.20180316_1456 in the /opt/ibm/WebSphere/AppServer directory.
WARNING: 
Configuration errors were detected during the installation.  You should view the log file(s) under /opt/ibm/WebSphere/AppServer/logs/wbi/install directory to investigate the severity of the errors. 
WARNING: /opt/ibm/WebSphere/AppServer/bin/sdk/_setupSdk.sh: line 36: /opt/ibm/WebSphere/AppServer/bin/sdk/_setupsdk1.6_64.sh: No such file or directory


today, having installed WAS ND 8.5.5.13 and BPM 8.5.7, and then having upgraded BPM to 8.6 without doing owt else.

Other commands also failed in the same way: -

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

/opt/ibm/WebSphere/AppServer/bin/sdk/_setupSdk.sh: line 36: /opt/ibm/WebSphere/AppServer/bin/sdk/_setupsdk1.6_64.sh: No such file or directory

/opt/ibm/WebSphere/AppServer/bin/managesdk.sh 

/opt/ibm/WebSphere/AppServer/bin/sdk/_setupSdk.sh: line 36: /opt/ibm/WebSphere/AppServer/bin/sdk/_setupsdk1.6_64.sh: No such file or directory

I checked the relevant location: -

ls -al /opt/ibm/WebSphere/AppServer/bin/sdk

total 24
drwxr-xr-x.  2 wasadmin wasadmins    60 Sep 13 07:36 .
drwxr-xr-x. 11 wasadmin wasadmins 12288 Sep 13 07:21 ..
-rwxr-xr-x.  1 wasadmin wasadmins    95 Dec 19  2017 _setupsdk1.8_64_bundled.sh
-rwxr-xr-x.  1 wasadmin wasadmins  1144 Sep 13 07:08 _setupSdk.sh


which explains a lot.

WAS 8.5.5.X and BPM 8.5.7 can both tolerate Java 6, but BPM 8.6 certainly doesn't play that way.

I suspect that the BPM 8.5.7 to 8.6 upgrade "killed" Java 6, and removed the JDK altogether.

*BUT* someone needs to tell WAS to use Java 8 from now on….. that's why managesdk exists.

In the best traditions of Jim Kirk, I cheated: -

ln -s /opt/ibm/WebSphere/AppServer/bin/sdk/_setupsdk1.8_64_bundled.sh /opt/ibm/WebSphere/AppServer/bin/sdk/_setupsdk1.6_64.sh

which creates a symbolic link between the correct Java 18 script and the required - but deprecated - Java 6 script.

Now we have this: -

ls -al /opt/ibm/WebSphere/AppServer/bin/sdk

total 24
drwxr-xr-x.  2 wasadmin wasadmins    86 Sep 13 07:37 .
drwxr-xr-x. 11 wasadmin wasadmins 12288 Sep 13 07:21 ..
lrwxrwxrwx.  1 wasadmin wasadmins    26 Sep 13 07:37 _setupsdk1.6_64.sh -> _setupsdk1.8_64_bundled.sh
-rwxr-xr-x.  1 wasadmin wasadmins    95 Dec 19  2017 _setupsdk1.8_64_bundled.sh
-rwxr-xr-x.  1 wasadmin wasadmins  1144 Sep 13 07:08 _setupSdk.sh


and now we can validate the default JDK: -

/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -getCommandDefault

CWSDK1006I: COMMAND_DEFAULT_SDK = 1.6_64 
CWSDK1001I: Successfully performed the requested managesdk task.


/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -getNewProfileDefault

CWSDK1007I: New profile creation SDK name: 1.6_64
CWSDK1001I: Successfully performed the requested managesdk task.


and see what's available: -

/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -listAvailable

CWSDK1003I: Available SDKs :
CWSDK1005I: SDK name: 1.8_64_bundled
CWSDK1001I: Successfully performed the requested managesdk task.


and use it: -

/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -setCommandDefault -sdkName 1.8_64_bundled

CWSDK1021I: The command default SDK name is now set to 1.8_64_bundled.
CWSDK1001I: Successfully performed the requested managesdk task.


/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -setNewProfileDefault -sdkName 1.8_64_bundled

CWSDK1022I: New profile creation will now use SDK name 1.8_64_bundled.
CWSDK1001I: Successfully performed the requested managesdk task.


and finally validate: -

/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -getNewProfileDefault

CWSDK1006I: COMMAND_DEFAULT_SDK = 1.8_64_bundled 
CWSDK1001I: Successfully performed the requested managesdk task.


/opt/ibm/WebSphere/AppServer/bin/managesdk.sh -getCommandDefault

CWSDK1006I: COMMAND_DEFAULT_SDK = 1.8_64_bundled 
CWSDK1001I: Successfully performed the requested managesdk task.


and now we're golden: -

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

...
Logging to file /opt/ibm/WebSphere/AppServer/logs/config/BPMConfig_20180913-080506.log.
Validating the profile registry.
[]
Configuring the deployment manager.
Creating the deployment manager profile.
INSTCONFSUCCESS: Success: Profile Dmgr01 now exists. Please consult /opt/ibm/WebSphereProfiles/Dmgr01/logs/AboutThisProfile.txt for more information about this profile.
CWMCB0135W: The deployment manager SOAP port 8880 in the property file '/mnt/ResponseFiles/Standard-PC-ThreeClusters-DB2.properties' does not match the actual SOAP port (8879).
Starting deployment manager profile Dmgr01.
CWUPO0001I: Running configuration action detectNewProducts.ant
The 'BPMConfig.sh -create -de /mnt/ResponseFiles/Standard-PC-ThreeClusters-DB2.properties' command completed successfully.