Maximo Open Forum

 View Only

 Cloning a Maximo Application Suite/Manage Environment

  • Maximo Application Suite
Eric Burkland's profile image
Eric Burkland posted 05-14-2024 13:24

In Maximo 7.6 cloning an environment from production to a test environment is fairly simple.  It involves stopping the app server, copying database files, running a sql to change system properties, and then bringing up the app server.  In Maximo Application Suite if I attempt this it triggers a whole unnecessary activation process and it rebuilds the maxinst and 'all' pods. 

Does anyone know how I can avoid reactivation when cloning from one environment to another? 

Thank you,

Eric

Eric Burkland's profile image
Eric Burkland posted 05-15-2024 19:15

We are on Oracle.  We also perform nightly cold backups since our database is small.  I have attached a few files if anyone is interested:  BTW I had to rename them as .txt so they could be attached

  1. masctl.txt - allows you to scale the pods (i.e. Bounce/Restart the application)
  2. maxstg.config -  used to set environment variables specifically KUBECONFIG so you can login to the cluster using oc cli.  It is sourced in the masclone bash script
  3. MAXSTG_REFRESH.txt - Post SQL Clone script - to update emails and such
  4. masclone -
    1. Source config
    2. Stop Manage Application -masctl
    3. Export MAXPROP, MAXPROPVALUE, MAXVARS, SERVERSESSION from target database using datapump to dump file
    4. Copy Database files from Cold Backup (i.e. Source Database) to Target Database - BTW I just hardcode the values in the script source host, source Oracle SID and backup Path
    5. Create the Control File for Target Database
    6. Import MAXPROP, MAXPROPVALUE, MAXVARS, SERVERSESSION from dump file to Target Database
    7. Run Post Clone SQL Script
    8. Restart Manage Application -masctl

Other notes:

  • The reason for exporting and importing those tables is otherwise a reactivation of manage will be triggered.
  • https://www.ibm.com/support/pages/how-resolve-crypto-and-cryptox-encryption-keys-mismatch-error-during-manage-activation  I referred to this document to set MXE_SECURITY_CRYPTO_KEY, MXE_SECURITY_CRYPTOX_KEY, MXE_SECURITY_OLD_CRYPTO_KEY, MXE_SECURITY_OLD_CRYPTOX_KEY to avoid Crypto issues between Production and a test environment.  Basically both environments are the same but you have to make it that way
  • This does not clone or deal with the MongoDB for Maximo Application Suite.  This is just manage.

Happy Cloning!

Eric

Related Content