Maximo List Archive

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.



Environment-specific data?

From: Killeen, Sean J. (2012-09-26 12:19)

Hi all,
In our setup, we have 3 instances of Maximo - Development, Test, and Production.
Our DBA team is quite capable and would like to regularly refresh the test and development environments so that they contain production data.
However, just copying all of the database data would wipe out environment-specific things like communication templates, permissions structures, settings, etc.
Has anybody had to deal with this before? If so, how did you identify and account for environment-specific considerations between your environments?
Thanks,
Sean


From: shannon sutton (2012-09-26 09:43)

If you restore the Prod data base over the Dev and Test then Dev and Test will still hold all config changes that Prod has.. There are a few steps in updating the database after it is restored over Dev or Test, but at that point they will be an exact snap shot of Prod..
 
________________________________
From: "Killeen, Sean J." <sean.killeen@jhuapl.edu>
To: "MAXIMO@yahoogroups.com" <MAXIMO@yahoogroups.com>
Sent: Wednesday, September 26, 2012 12:19 PM
Subject: [MAXIMO List] Environment-specific data?

 
Hi all,
In our setup, we have 3 instances of Maximo - Development, Test, and Production.
Our DBA team is quite capable and would like to regularly refresh the test and development environments so that they contain production data.
However, just copying all of the database data would wipe out environment-specific things like communication templates, permissions structures, settings, etc.
Has anybody had to deal with this before? If so, how did you identify and account for environment-specific considerations between your environments?
Thanks,
Sean


From: Hanna, Christopher CTR (2012-09-26 16:12)

Yep, we have that same issue. I basically just provided our DBA with a script that he can run post import that will update all the environment specifics. It's kind of always a work in progress to a certain extent. One of the things we struggled with a little bit was how to handle external system end points for the MIF, since we obviously didn't want test to suddenly start pumping data into some production system. We ended up just having the script set all external systems to disabled post refresh and then we just activate them and set the end points only when they need to be tested.
There may be more elegant solutions, but this is effective in our case.
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Killeen, Sean J.
Sent: Wednesday, September 26, 2012 12:19 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Environment-specific data?

Hi all,
In our setup, we have 3 instances of Maximo - Development, Test, and Production.
Our DBA team is quite capable and would like to regularly refresh the test and development environments so that they contain production data.
However, just copying all of the database data would wipe out environment-specific things like communication templates, permissions structures, settings, etc.
Has anybody had to deal with this before? If so, how did you identify and account for environment-specific considerations between your environments?
Thanks,
Sean


From: Luca Truffarelli (2012-09-27 08:56)


The parameters that we identified needed to be modified are the
following PROPVALUE in the table MAXPROPVALUE (note we have Oracle):
Database.Oracle.InstanceName
Database.Oracle.ServerHostName
Database.Oracle.ServerPort
mxe.db.url
mxe.doclink.doctypes.defpath
mxe.doclink.path01
mxe.doclink.path02
mxe.doclink.path03
mxe.int.globaldir
mxe.int.webappurl
On 26/09/2012 18:43, shannon sutton wrote:
>
> If you restore the Prod data base over the Dev and Test then Dev and
> Test will still hold all config changes that Prod has.. There are a
> few steps in updating the database after it is restored over Dev or
> Test, but at that point they will be an exact snap shot of Prod..
>
>
> ________________________________
> From: "Killeen, Sean J." <sean.killeen@jhuapl.edu
> <mailto:sean.killeen%40jhuapl.edu>>
> To: "MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>"
> <MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>>
> Sent: Wednesday, September 26, 2012 12:19 PM
> Subject: [MAXIMO List] Environment-specific data?
>
>
>
> Hi all,
>
> In our setup, we have 3 instances of Maximo - Development, Test, and
> Production.
>
> Our DBA team is quite capable and would like to regularly refresh the
> test and development environments so that they contain production data.
>
> However, just copying all of the database data would wipe out
> environment-specific things like communication templates, permissions
> structures, settings, etc.
>
> Has anybody had to deal with this before? If so, how did you identify
> and account for environment-specific considerations between your
> environments?
>
> Thanks,
> Sean
>
>


From: Sean Clark-McCarthy (2012-09-27 15:33)

In just about all the deployments I do that has period refreshes we do a few things. If there are property changes from one system to another, we put those instance specific properties into the MAXIMO.properties file. Properties in the file will override properties in the database. DB Connection string is a perfect example of this in action. You can do this for any property.
For data specific items (MIF, Comm Templates, etc), we identify things that need to change when the environment shifts and have scripts to update those via SQL after the refresh is done and prior to the application starting up.
--- Sean Clark-McCarthy
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Killeen, Sean J.
Sent: Wednesday, September 26, 2012 12:19 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Environment-specific data?
Hi all,
In our setup, we have 3 instances of Maximo - Development, Test, and Production.
Our DBA team is quite capable and would like to regularly refresh the test and development environments so that they contain production data.
However, just copying all of the database data would wipe out environment-specific things like communication templates, permissions structures, settings, etc.
Has anybody had to deal with this before? If so, how did you identify and account for environment-specific considerations between your environments?
Thanks,
Sean