db2ibm-mobilefirstworklight-serverwebsphere-libertydatabase-cluster

IBM Worklight 6.2 Server Deployement error: DB2 Instance not found on server

Environment:

  1. IBM Worklight 6.2,
  2. IBM Liberty 8.5.5.1,
  3. IBM DB2 10.5 &
  4. Windows 2008 standard Edition.

For the High Availability of DB instance[WLDBINST], the following Architecture I have followed.

  1. 2 Windows Clustered Machines with IBM DB2 binary and SAN storage used to share the Database file in Common.
  2. If any 1 node is not available the other node will take over the control without any loss of the data.
  3. I have tested the DB2 instance via Cluster IP and it works fine.

The below error has been logged, when I run the Worklight Server Configuration tool, 

Instance WLDBINST not found on server. Found only [WLDBINST              C, :, DB2CLUSTER, DB2]

I have found the reason for the above issue. To list the DB2 Instances we can use the command db2ilist

C:\>db2ilist
WLDBINST        C :    DB2CLUSTER
DB2

Above result shows that we have two instances

  1. WLDBINST which is in "C" drive and part of DB2CLUSTER &
  2. DB2

Worklight Configuration tool also uses the similar DB2 tool to list the instances, I guess.

So the configuration tool considering the result as 4 instances as follows,

  1. WLDBINST C,
  2. :,
  3. DB2CLUSTER and
  4. DB2

How I can resolve this issue.

Solution

  • If the Server Configuration Tool is not able to create the database for your topology, you should create it manually before running the tool.

    For the Administration database, the doc is here: https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_creating_the_db2_database_for_wladmin.html

    For the Project Runtime databases, the doc is here: https://www-01.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.deploy.doc/admin/t_creating_the_db2_databases.html

    The server configuration tool will not do any specific configuration to ensure that Liberty reopens a connection if there is a database node switch. I recommend that you review the behavior of Liberty in this case, and add settings in the server.xml as required.