Maximo Open Forum

 View Only
  • 1.  Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 10-28-2020 18:47
    Hi,

    I was curious if anyone had documentation for refreshing Maximo 7.6 Dev data with Production data and what settings need to be done to get the Development environment pointed to dev servers and not production. I've found documentation for 7.5 but it is no longer recommended with 7.6. 

    When we currently try to refresh dev, the settings from production are transferring to dev and we want to make sure that when we modify work orders or any other record that it does not get updated in our production environment. 



    Examples:
    System Properties
    Database.SQL.ServerHostName
    mxe.doclink.doctypes.defpath
    #Administration
    #MaximoUserGroups

    ------------------------------
    justin
    ------------------------------


  • 2.  RE: Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 10-29-2020 08:55
      |   view attached
    Justin,
    Here is template we use. Chris Sanchez from Aquitas-Solutions gave us this template and we made a couple modifications for our environments.

    ------------------------------
    Adam Ames
    Kwik Trip, Inc.
    ------------------------------

    Attachment(s)

    txt
    DB_Refresh_TST.txt   3 KB 1 version


  • 3.  RE: Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 10-29-2020 09:07
    Justin,

    To refresh a lower environment with Production data is usually pretty straightforward since most of Maximo can be migrated using a simple database backup/restore procedure. Assuming that you have a Production Maximo application server pointed to a Production Maximo database, and a Development Maximo application server pointed to a Development Maximo database, then your steps should be something like:

    1. Obtain a backup of the Production Maximo database
    2. Stop the Development Maximo application server
    3. Restore the backup over the Development Maximo database
    4. Run some scripts against the database to match the Development environment
    5. Start the Development Maximo application server 

    For #4, there are quite a few considerations. Here are some that you may want to consider:

    • Correcting your Attached Documents paths
    • Disabling outbound emails to users (or adjusting the subject line so that it's clear the email came from the Development environment)
    • Disabling integrations (or re-pointing integrations to the appropriate Development systems)
    • Adjust your Cron Task and Escalation schedules
    • Disabling LDAP Authentication

    Hope this helps.

    ------------------------------
    Alex Walter
    A3J Group LLC
    ------------------------------



  • 4.  RE: Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 10-29-2020 10:19
    Adam and Alex gave quite a few good examples on PROD->DEV refresh that are important areas to focus on. I'll try to avoid rehashing too much, but the biggest thing we do for customers is disable a lot of the background processes (PMWOGEN, Reorder, email listener, etc.) and updating the integration information to be appropriate for that environment. These tend to be areas that cause confusion for users or data issues with your PROD system and it'll be unique to your system in what you want to do.

    The one thing I didn't see in either is a DEV environment might not be an exact replica of PROD from a configuration perspective. You should always have 1 environment that is a mirror configuration of PROD (so you can validate things prior to deploying to PROD), but a lot of organizations will have more than 1 NPE (Non-Production Environment). We'll have to remove some cluster configuration references in those smaller NPE environments (changing connection factories on JMS queues, removing server specific system properties such as cron task dorun/donotrun, etc.).

    ------------------------------
    Steven Shull
    Projetech
    ------------------------------



  • 5.  RE: Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 11-02-2020 18:22
    Hi, One more item I didn't see mentioned that I see symptoms of frequently, is to clear the taskscheduler table on the target system. Although I have heard rumors that the table should rebuild after an admin mode switch, I haven't actually seen that happen (but, things in Maximo can change over time...)

    ------------------------------
    keith simmons
    Aquitas Solutions
    ------------------------------



  • 6.  RE: Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 02-21-2023 11:24

    Hello Steven,

    Little late in the discussion but is there a way we can refresh dev database from production without refreshing specific tables  ?

    Thanks 

    VJ



    ------------------------------
    vineet joshi
    ------------------------------



  • 7.  RE: Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 02-22-2023 01:36

    What specific tables do you want to exclude from a refresh? I can see referential integrity being an issue. To answer your question, the answer is maybe. 

    The only other minor tidbit I'd add is help.host URL may need an update.

    report.custom.* if you use ERI (External Reporting Integration) may need an update.

    I also change the welcomemaximomessage to say test. You can also change the skin or an replace graphic images in webclient (e.g. different color banner/header/login screen) to help differentiate.



    ------------------------------
    sun kim
    ------------------------------



  • 8.  RE: Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 02-23-2023 11:55

    Hello Sun

    I wanted Long Description table to be excluded from the refresh which I believe should not cause much of referential integrity issues.

    This table has grown enormous over period of time, and I don't want my Dev database to be upgraded (size wise) every time during production refresh. 

    Thanks 

    VJ



    ------------------------------
    vineet joshi
    ------------------------------



  • 9.  RE: Instructions for refreshing Maximo 7.6 Dev with Production data and settings

    Posted 02-23-2023 15:35

    Hi! So many objects in Maximo are referential and LD is certainly one. You can look at the meta data in the maxrelationship table to get an idea about static relationships. To respond to your question, yes you will have referential issues if you neglect to bring the ld table(s) over. I would say that the issues are potentially manageable, but the risk is that you would break another mbo operation internally and perhaps not even know (because there aren't necessarily error traps for things that logically should never occur). You might try an alternative solution (replace the contents with shorter descriptions?)

    Anyway, just saying probably not a good approach to drop the table entirely... 



    ------------------------------
    keith simmons
    Aquitas Solutions
    ------------------------------