Subsequent Tasks for Environments
  • 25 Mar 2024
  • 2 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Subsequent Tasks for Environments

  • Dark
    Light
  • PDF

Article summary

This topic is related to the following sections:

Once the Environments are in place and the Working Datasources are assigned with Report Cache Datasources for each, the team may work on the subsequent tasks for this process. 

  • Copy from the DEV working database to the LOAD working database all Tables, Views, Stored Procedures using the Working DB Object Promotion - this is a repeated process.

  • Setup within SAP Data Services the Substitution Parameter Configurations for both DEV and LOAD and point the $$REPORT_ENVIRONMENT parameter to the correct environment within Migration.

  • Setup within SAP Data Services each Working Datastore for multiple Configurations - names DEV and LOAD that stores the Datasource and System information.

  • Setup within SAP Data Services the System Configurations for DEV and LOAD to provide a system wide update for all Datastores from one Configuration to another Configuration. 

There is no need to alter the Dataset or Mappings in Migration.  There is no need to build out the XML as the current Datastore is used - these point to the DEV reporting environment by using the working database for DEV.  The Reports shown within Mappings remain pointing to the DEV Working database and DEV Report database because it is in the Mappings that the developers work. 

However, the users toggle between the DEV and LOAD reports within Pathway - Validate > Migration Reports OR Validate > Deployment Reports.  The run of the DS migration project generates the report data and store it in the correct REPORT database based upon the settings. 

null
Migration Reports: Select the Environment

Select from the list of available Environments. The banner tab at the top of the page grid displays in the color of the new Environment.

null
Migration Reports: Select the Environment

The Environments are identified within Substitution Parameter Configurations so that at time of a Mock, this parameter can be switched so that all Reports generate to the correct Database.  Use Pathway in Data Services - Tools > Substitution Parameter Configurations.

null
SAP Data Services: Substitution Parameter Configuration

The Datastores for each working database that is included in the Reporting Environments need to be setup for multiple Configurations as shown below:

null
SAP Data Services:  Datastores: Configurations

As the Datastores are finalized with multiple configurations to store the multiple Databases for these Working Instances, the team needs to setup the System Configurations to set the default from one location for all Datastores as shown below.  Use pathway in Data Services - Tools > System Configurations

null
SAP Data Services: System Configurations


Was this article helpful?

What's Next
ESC

Eddy, a generative AI, facilitating knowledge discovery through conversational intelligence