This post
includes some of my notes on using DBC for deployment of Maximo configuration.
In case you wonder why using DBC, the short answer is, if you’re happy with
whatever method you’re using to deploy configuration, whether it is manual or
using Migration Manager, ignore this post. But if you’re looking for a way to
streamline development process for a large team by collaborating and source
controlling using GIT, or if you want to fully automate the deployment process,
DBC is the way to go.
IBM has
been using DBC script for a long time, but only recently, they published a
reference guide so third 3rd party
consultants like us can use. DBC Script can be used to automate most of the
common configuration for Maximo. It has standard commands to create/modify
common low-level objects like table, index, domains etc. For many other
configurations which don’t have a specific DBC command, we still can handle the
deployment using the <freeform> or <insert> statement
to put in anything into Maximo DB. Below are some specific notes on certain
type of changes:
