Question

Database post-refresh activities

  • 16 January 2023
  • 2 replies
  • 155 views
T
Rank
Badge +3
  • Tim
  • Sidekick (Customer)
  • 9 replies

We have just had our hosted DEV database refreshed (cloned) from PRD. APPS9

 

Does anyone have a comprehensive list of activities to be performed post-refresh? For instance, stopping & changing Scheduled tasks.

 

Does anyone have any clever ideas on how to automate any of this (for instance diverting/rebranding emails when NOT sent from PRD to be clear these are not LIVE messages).

 

Thanks in advance.

2 replies

E
Rank
Userlevel 4
Badge +7

Wow - this is a loaded question.  There can be quite a few places to look, depending on which features of the IFS application are used at your site.

For starters, look at the Integration section of your new IFS environment.  Check the connections, messaging and interfaces configured in the IFS Connect section of the application.  Make sure these connections and interfaces are pointed to the databases and destinations you need (and not to Prod environments).

In a similar fashion look into the Connectivity and Events subcategories.  Be sure to also look at the reports in use within IFS.  Focus on your customized reports.

You’ll need to check database connections used by any add-on features of IFS in use at your sites, i.e. Demand Planner, Constraint Based Scheduling, BI, Business Analytics, Touch Apps, etc.  Each of these add-on features will contain database connection info which should be validated.

You’ll want to check on any customized packages and other mods applied by your company too.

If you can automate this process you’re ahead of the game.

william.klotz
Rank
Userlevel 7
Badge +21

Hi @Tim ,

 

We use RMAN to duplicate our IFS Application 10 production database to either a test or development environment but we have to go through a number of steps once the duplication and middleware server reconfiguration has completed on the target environment.  

 

Here’s some of what we go through when we duplicate production to non-production databases.

  1. Go to Solution Manager -> Integration -> IFS Connect -> Setup IFS Connect to disable the EDI interface for 850.
  2. Go to Solution Manager -> Integration -> Routing Rules -> Inbound to disable the EDI interfaces for 850 and 860 documents.
  3. Go to Solution Manager -> Integration -> Routing Rules -> Outbound to disable the EDI interfaces for 856 and 810 documents.
  4. Go to Solution Manager -> Integration -> Routing Rules -> Outbound to disable the Ignition Integration interfaces.
  5. Disable document management from storing or removing files set to Shared or FTP storage types.
  6. Delete all built-in scheduled reports.
  7. Disable schedule quick reports in application server tasks.
  8. Disable custom event notifications.
  9. Disable built-in event actions which are emailing users.
  10. Disable users used for barcode scanning and picking so no one accidentally uses non-production environments.

 

Regards,

William Klotz

Reply


Terms & ConditionsCookie settings