2 Replies Latest reply on Feb 3, 2012 8:27 AM by Riccardo Casero

    Alignment of a BCO Test environment with the Production environment

    Renato Bonomini
      Share This:

      When assessing projects, we suggest that in our experience at Moviri a Test environment is not strictly needed for BCO, for two reasons

      1. BCO is not a business critical application and it can be easily restored without loss of data
      2. most customizations and objects can be staged and simulated safely in the production environment.


      Nonetheless, when a Test environment is available or required by policy, in order to make it significant, one should try to keep it as aligned as possible with the Production instance, spending a reasonable amount of time.


      If you have a Prod environment result of a project and you need to reproduce it on a freshly-installed test environment, find here below a minimal list of tasks to perform on the Test environment to make it aligned with Production.


      The order is not a requirement but a a suggestion:

      1. Recreate the access groups of the Prod instance
      2. Recreate the user roles of the Prod instance
      3. Configure the LDAP authentication as in the Prod environment
      4. Upload and activate the custom ETL projects in Test (including, when necessary, custom scripts)
      5. Copy the run configurations of ETLs, Tasks and Task chains
      6. Run each ETL at least once to import data
        1. for datasources based on databases, configuring the Test ETL against a Test database
        2. for file-based ETLs, copy a set of files from production
      7. Reproduce the domain tree as in the Prod environment
      8. Organize all workspace objects as in the Prod environment
      9. [new,thanks G!] Copy filters from Production environment
        1. Entity Filters
        2. Time Filters
      10. Activate all the out-of-the-box dashboards present in the Prod environment
      11. Export all custom dashboards from Production and import them into Test through the Community Export/Import utility
      12. Upload all custom advanced reports to the test environment
      13. Create an instance of each custom advanced report



      What is your experience?



      Message was edited to include first suggestions

        • 1. Alignment of a BCO Test environment with the Production environment

          Thanks Renato this is very good contribute.


          Of course, regarding step 6 ("Run each ETL at least once to import data") of course much better if you have a test env that inludes also test env of the orginal data source (e.g. a test OEM).


          I would also add recreating Entity Filters and Time Filters.




          • 2. Alignment of a BCO Test environment with the Production environment
            Riccardo Casero

            Renato, very helpful indeed.


            I just wanted to add another view to the topic. I agree with you BCO have isolation and simulation capabilities that make configuration and customization achievable directly in production, through staging. Still company policies may require (and they actually do in real cases) to build and test the solution in a Development BCO and only when validated let it move to Production BCO.


            So, under this view, most of the items you mention still apply, but the other way around: from Development to Production.


            Regarding [4] and [5] I recently worked together with BMC support on a detailed procedure on how to "elevate" a custom ETL from Development to Production, both for the first deploy and for subsequent changes (BMC knowledge base reference KA363173 on kb.bmc.com).