IBM Containerized Master Data Management — Use Deployed MDM — Part III
In this article, let us focus on
- Key changes to the docker-compose yaml files from MDM v12.0.0.0
- How to add a Custom Bundle to MDM Operational Server
- How to commit the mdm_container
Changes in docker compose files since MDM v12.0.0.0
The key changes that will be noticed in the docker-compose files since MDM v12.0.0.0 include
- Externalized certificates (key.p12 in WAS)
- Passwords excluded in image
- Default passwords not used
The changes will be noticed in OpenShift templates as well.
Note: The above changes will be seen in MDM v11.6.0.12 too
The externalized certificates can be seen at the sslcerts folder which comes with the docker-compose files; there are volumes used in the docker-compose files that help the containers obtain the certificates.
The secrets, which are the passwords corresponding to WebSphere Application Server profile administrator, Database, Database SSL and the WebSphere Messaging Queue can be noticed in an encrypted format in the docker-compose files.
The password corresponding to the WebSphere Application Server trust file, ie., /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/WASHOSTCell01/nodes/WASHOSTNode01/key.p12, has been updated.
Add a CBA to the deployed MDM docker container
In the MDM deployed container, you can make use of the addCBA.sh file that found in the bin folder under WAS Profile Home to add CBAs quickly.
The steps to make use of these scripts are:
- Copy the cba(s) the the /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/CustomCBA/cba folder
- Login to the mdm_container
- Go to folder /opt/IBM/WebSphere/AppServer/profiles
- Invoke ./addCBA.sh
You can add more than one CBA at a time by placing it in the above mentioned folder
Voila, confirm it in the WAS Admin Console
Please execute the SQLs corresponding to the CBA, restart the application server, and ensure that the custom CBA works as expected.
Commit the MDM container
It is a good practice to commit docker containers that are updated, specifically the MDM container.
When we perform a docker commit a new docker image will get created. This image will hold all changes done to the container, including CBAs that have been added to the MDM Operational Server.
Below is the step used to commit MDM container.
Note: You can delete docker image using
docker rmi <repository>:<tag>
or
docker rmi <image_id>
When you come up with a new version of the MDM image, it is a good practice to take a backup of the existing docker-compose yml file (mdm-deployed.yml), update the image name corresponding to deployed mdm in the mdm-deployed.yml and use docker-compose up to bring up the file.
Once exploring deployed MDM is complete, bring the docker-compose file down with the command,
docker-compose -f mdm-deployed.yml down -v
When this command completes execution, run the below commands to ensure that there are no containers and network corresponding to mdm-deployed.yml.
docker container ls -a
docker network ls
