Maximo

Hi Fellow Maximo People!

The standard way of deploying your product customisations/configurations for Manage is to use the customisation archive zip file. This standard process is very handy and simple, and everything is automated which is cool.

However, because the process follows a standard build procedure, each time the EAR is rebuilt, redeployed and the DBC files ran. Hence, the process can take a long time.

Has anyone figured out a way to skip the EAR rebuild and only run the DBC files, in the instances where an EAR rebuild is not required? Or do you have some other method of deploying your DBC files?

Thanks

Aneesh

------------------------------
Aneesh Joseph
------------------------------

Hi Aneesh,

you're touching on an important subject which I would wish myself to be addressed by IBM.

IBM MAS Manage operator doesn't really get into the customization archive contents and therefore assumes that new admin and server bundle's images build is required. In general, even if your new customization archive does not affect Maximo EAR (or any of the other WAR files which might be generated for other types of server bundles) then your DBC files included in the customization archive(-s) need to somehow end up in the maxinst POD to be used by the updatedb process, hence it triggers a image build. I guess you're aware of this anyway.

When we're in a need to somehow optimize the deployment time and need to run DBC scripts only then we're:

1. taking Manage down first (set ManageWorkspace CR .spec.settings.deployment.mode = down)
2. uploading DBC scripts to the maxinst POD where they are supposed to be located (oc cp)
3. running the DBC scripts remotely - one by one (oc exec  along with /opt/IBM/SMP/maximo/tools/maximo/internal/runscriptfile.sh)
4. updating upgrade MAXVARS to match the latest executed script
5. taking Manage up back again (set ManageWorkspace CR .spec.settings.deployment.mode = up)

I guess this is one of the things you could report as a new idea using https://ideas.ibm.com/ portal.

Hi Fellow Maximo People!

The standard way of deploying your product customisations/configurations for Manage is to use the customisation archive zip file. This standard process is very handy and simple, and everything is automated which is cool.

However, because the process follows a standard build procedure, each time the EAR is rebuilt, redeployed and the DBC files ran. Hence, the process can take a long time.

Has anyone figured out a way to skip the EAR rebuild and only run the DBC files, in the instances where an EAR rebuild is not required? Or do you have some other method of deploying your DBC files?

Thanks

Aneesh

Hi Fellow Maximo People!

The standard way of deploying your product customisations/configurations for Manage is to use the customisation archive zip file. This standard process is very handy and simple, and everything is automated which is cool.

However, because the process follows a standard build procedure, each time the EAR is rebuilt, redeployed and the DBC files ran. Hence, the process can take a long time.

Has anyone figured out a way to skip the EAR rebuild and only run the DBC files, in the instances where an EAR rebuild is not required? Or do you have some other method of deploying your DBC files?

Thanks

Aneesh

And just interesting, what type of changes (customizations?) you deploying by DBC files ? I thought DBC files standing for more complex chganges? 

Why do not use deployment packages for that ?

Hi Fellow Maximo People!

The standard way of deploying your product customisations/configurations for Manage is to use the customisation archive zip file. This standard process is very handy and simple, and everything is automated which is cool.

However, because the process follows a standard build procedure, each time the EAR is rebuilt, redeployed and the DBC files ran. Hence, the process can take a long time.

Has anyone figured out a way to skip the EAR rebuild and only run the DBC files, in the instances where an EAR rebuild is not required? Or do you have some other method of deploying your DBC files?

Thanks

Aneesh

And just interesting, what type of changes (customizations?) you deploying by DBC files ? I thought DBC files standing for more complex chganges? 

Why do not use deployment packages for that ?

Hi Fellow Maximo People!

The standard way of deploying your product customisations/configurations for Manage is to use the customisation archive zip file. This standard process is very handy and simple, and everything is automated which is cool.

However, because the process follows a standard build procedure, each time the EAR is rebuilt, redeployed and the DBC files ran. Hence, the process can take a long time.

Has anyone figured out a way to skip the EAR rebuild and only run the DBC files, in the instances where an EAR rebuild is not required? Or do you have some other method of deploying your DBC files?

Thanks

Aneesh

Hi Andrey

DBC stands for Database Change. It is the mechanism used by the IBM product team to build Maximo add-ons. It allows you to script all your work into configuration as code (similar to infrastructure as code). The advantage here is that you can commit your configuration to source control and use automation for your deployment and builds. And also version your product as Andrzej mentioned. It really helps to scale up your project.

And just interesting, what type of changes (customizations?) you deploying by DBC files ? I thought DBC files standing for more complex chganges? 

Why do not use deployment packages for that ?

Hi Fellow Maximo People!

The standard way of deploying your product customisations/configurations for Manage is to use the customisation archive zip file. This standard process is very handy and simple, and everything is automated which is cool.

However, because the process follows a standard build procedure, each time the EAR is rebuilt, redeployed and the DBC files ran. Hence, the process can take a long time.

Has anyone figured out a way to skip the EAR rebuild and only run the DBC files, in the instances where an EAR rebuild is not required? Or do you have some other method of deploying your DBC files?

Thanks

Aneesh