Best Practices for Keeping each Environment in Synch for Testing Purposes (Doc ID 2026709.1)

Last updated on SEPTEMBER 16, 2016

Applies to:

Oracle Knowledge - Version 8.4.2.2 and later
Information in this document applies to any platform.

Goal

At times when reproducing issues in Dev or Staging the Oracle Knowledge environments may work differently than production.  This article identifies what to look at in validating that the different environments are properly installed and configured together.

The recommended best practice for administering the system is that all application, config and dictionary changes should be made in dev and then unit tested in dev.  Then they are propagated to staging and system tested. The business should do an acceptance test.  If there are issues changes are made back in dev and the process starts over.  When testing is acceptable then the changes can be propagated to production for end user use.  With this system each environment should be working in the same way with the same components.  If a good development methodology is followed then the only thing you should have to move back to staging and dev is the IM DB (and Answerflow) from time to time.  There are times when things get out of synch because of emergency situations and need to be diagnosed and corrected.

When things are not kept in synch testing and lack of testing can cause problems and even outages in production.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms