MDM v11.6 FP10: Configuring and deploying ISC on docker containers

This post primarily focusses on option Installable MDM with IBM Stewardship Centre and DB2 container (local) but can also be used for reference for remote DB containers.

 MDM ISC container is built on Business Automation Workflow v18.0.0.2 (BAW) with the Process Center and Process Server in it. The bpmdb_container has eight databases in it, namely CMNDBPC, BPMDBPC, CPEDBPC, PDWDBPC, CMNDBPS, BPMDBPS, CPEDBPS and PDWDBPS.

To configure ISC on the mdmisc_container, we have to login to the container as the root user and execute the Configure_ISC_Interactive.sh script from the tmp folder. It is good if we follow the below pre-requisites before invoking this script.

 1. Login to the bpmdb_container and ensure that the databases are up and running.
docker exec -it bpmdb_container bash
su - db2inst1
db2 list db directory
db2 connect to CMNDBPS user db2inst1 using db2inst1
Check BPM Databases
2. Login the mdm_container and ensure that the application server is up and running. When ISC is configured, there are certain certificate exchanges between BPM and MDM and certain resource creation on MDM. To enable this, the application server should be in STARTED state in mdm_container.
docker exec -it mdm_container bash
$WAS_PROFILE_HOME/bin/serverStatus.sh server -username mdmadmin -password mdmadmin
Please start the application server in case it is in stopped state.

3. Login to the mdmisc_container as root user. Before executing the Configure_ISC_Interactive.sh, execute the below lines and wait for upto 5 minutes.
sh /opt/ibm/Workflow/v18.0/bin/BPMConfig.sh -start -profile DmgrProfilePC -de ProcessCenter
sh /opt/ibm/Workflow/v18.0/bin/BPMConfig.sh -start -profile DmgrProfilePS -de ProcessServer

 Ensure that the servers in BPM are up and running by executing the below scripts
/opt/ibm/Workflow/v18.0/profiles/Node1Profile/bin/serverStatus.sh SingleClusterMember1 -username bpmadmin -password bpmadmin

 /opt/ibm/Workflow/v18.0/profiles/NodeProfilePS/bin/serverStatus.sh SingleClusterMember1 -username bpmadmin -password bpmadmin

 Although Configure_ISC_Interactive.sh has statements to start the servers in BPM, we are started it before, to ensure that there are no failures in case the servers take a longer time to start.
Check server status for servers in BPM Cluster
4. Commit the mdm_container after the Configure_ISC_Interactive.sh completes execution. This image has to be used with ISC in container orchestration systems like Kubernetes and OpenShift.

 5. Incase you have configured MDM using WMQ for using multiple replicas, there is a possible that the MDM.BPM.LINK bus does not start up. This occurs because the user ws9admin cannot create a schema and buses in the Derby filesystem database. To create the bus, follow the below workaround at the mdm_container.
i) Login as root user
docker exec -itu root mdm_container bash
ii) Restart the server
$WAS_PROFILE_HOME/bin/stopServer.sh -username mdmadmin -password mdmadmin
$WAS_PROFILE_HOME/bin/startServer.sh
iii) Execute /tmp/clear_cache.sh
iv) Execute the below statements
chmod -R 775 /opt/IBM/WebSphere/AppServer
chmod -R g=u /opt/IBM/WebSphere/AppServer
v) Exit the container
vi) Login to the container as the default user ws9admin
vii) Ensure that the MDM_BPM_LINK is working by starting the application server

$WAS_PROFILE_HOME/bin/startServer.sh
Commit the image after performing the steps mentioned above and use it in container orchestration systems.


As root user, clear cache and give permissions to users in root group


Start the server as ws9admin user
6. In container orchestration systems expose port 7276 from mdmhost and 8032 from bpmpshost, both at the Deployment and at the Service. Expose these ports with type ClusterIP at the corresponding Service resources.

 
docker exec -it bpmdb_container bashdocker exec -it bpmdb_container bash
docker exec -it bpmdb_container bashdocker exec -it bpmdb_container bash

Comments

Post a Comment

Popular posts from this blog

Creating MDM image from docker container to deploy on OpenShift ?

To create a docker image for MDM, that can be deployed on OpenShift or Kubernetes, we create a docker container by selecting MDM Installable docker compose option.  This container has WebSphere Application Server Base installed, a WAS Base Profile created and MDM extracted using Installation Manager.  We execute the Configure_MDM_Interactive.sh script in the /tmp folder to configure database and deploy MDM applications on the WAS Profile. The default user in this mdm_container is ws9admin.  The ws9admin user is the owner of all the files and folders under the WAS home directory.   Volumes are used in the docker compose file mdm-installable-remotedb.yml - the file that used to bring up the Installable MDM container.  When a directory within the docker container is mapped as a volume to a folder in the host machine, there is an issue noticed with the owner such folders, when the docker container is committed as an image and a new container is created fro...
Read more

Reduce the size of customized MDM docker image using multi-stage builds

The MDM container has Installation Manager, WAS Base, a Profile, MDM and certain utilities such as DB drivers to connect to the database in it.   For the MDM container to function, it is sufficient if the WAS Base installation along with the profile and the database driver(s) are available in the container.  In addition, we can have the IVT folder under MDM to enable us to confirm that the product is functional.  Incase the Business Administration UI is part of the container, certain jars under a folder in MDM also need to be included.   We can reduce the size of the runtime image that can be used in container orchestration systems like Kubernetes and OpenShift, by creating a new image having only the required files and folders.  To achieve this, we can use Docker multi-stage builds. Below is a sample script: FROM <CUSTOMIZED_MDM_IMAGE> AS MDM FROM  us.icr.io/mdmaese/ubuntu-18.0.4-ossc ENV JAVA_HOME=/opt/IBM/WebSphere/A...
Read more