Maximo database refreshes

While developing for Maximo you will sometimes need to refresh your development environment from production so that you can have fresher data or work with, or to return your development environment to the production baseline if something has gone awry.

There are some configuration items I have updated in the past before starting the app back up and disabling Admin Mode.

If you have maxmessages that reference your environment name, you should update these.

UPDATE maximo.maxmessages
   SET value = 'DEV - ' || value
 WHERE msggroup = 'system'
   AND msgkey = 'example';

Disable External Systems so that you can control which start processing in your development environment. Maybe you have some that are only intended for production.

UPDATE maximo.maxextsystem
   SET enabled = 0;

Update URLs for your BIRT, Cognos, hostname, webapp, etc.

-- BIRT
UPDATE maximo.maxpropvalue
  SET propvalue = 'https://mydevenv.com'
WHERE propname = 'mxe.report.birt.viewerurl'
;

-- COGNOS
UPDATE maximo.maxpropvalue
   SET propvalue = 'https://mydevenv.com'
 WHERE propname = 'mxe.report.cognos.serverURL'
   ;

-- webappurl
UPDATE maximo.maxpropvalue
   SET propvalue = 'https://mydevenv.com'
 WHERE propname = 'mxe.int.webappurl'
 ;

-- hostname
UPDATE maximo.maxpropvalue
   SET propvalue = 'https://mydevenv.com'
 WHERE propname = 'mxe.hostname'
 ;

 --help host

 UPDATE maximo.maxpropvalue
   SET propvalue = 'https://mydevenv.com'
 WHERE propname = 'mxe.help.host'
 ;

Update your DOCLINKS settings to point to the correct URL

UPDATE maximo.maxpropvalue
  SET propvalue = 'C:\mydoclinks=https://mydevenv.com'
WHERE propname = 'mxe.docklink.path01'
;

These are a just a few things you may want to update when doing a refresh. There may be other things specific to your environment you would want to do, such as setting the status or permissions of certain users and ensuring certain crontask instances are configured properly for the target environment.