ISA CTS Overview
To move SAP Information Steward (IS) and SAP Information Steward Accelerator (ISA) content between development tiers (environments), a set of steps must be followed in the order specified due to the interrelationships that exist between the data elements in the two applications (Projects, Rules, Rule Bindings and other elements).
The process is performed in:
- SAP IS by a technical IS user
- SAP ISA by a user familiar with ISA
- SAP Central Management Console (CMC) by the Administrator of the CMC environment
- Data Stewardship Platform (DSP)® by an Administrator or technical lead
Refer to the CTS section in System Administration for general information about CTS.
Before the promotion of the code to the target environment:
- The client environment must be running ISA version 6.5.3 or later.
- Both the source and target environment must be on the same version level.
Additionally, to move the data elements:
- The user performing the code promotion must be familiar with both IS and the ISA.
- The user must have knowledge of the CTS application used for the code promotion of the ISA. Refer to CTS in System Administration for more information.
- The source environment must have been built out so that the IS and ISA configuration is aligned and able to be executed successfully for the IS Project that is to be promoted.
- The source and target Collect environments must have been configured to point to the respective IS repository sources.
To CTS ISA objects:
-
Import the CTS Package of Schedules into the Target Environment
-
Open the Project Summary page to align the metadata
Export IS Project Content in IS
To export the project:
-
Open the Information Steward Project to be promoted.
-
Click the Export project and associated objects drop-down menu and select Project from the top right of the Workspace Home page.
-
Export the Project contents and save to a zip file.
NOTE Do not update the file name that is automatically generated by IS.
-
Copy the .zip file to a directory that the Target IS environment can access.
Create the CTS Package of ISA Content
To create the package:
-
Select Admin > CTS in the Navigation pane.
-
Click Add.
-
Enter a description in the DESCRIPTION field.
-
Click Save.
-
Enter a comment in the Comments field if necessary.
-
Click Save.
-
Click the Items icon for the newly created CTS package.
-
If no records exist, the page displays in add mode. Otherwise, click Add.
NOTE: For each item added, there is a corresponding Project or Project Distribution being promoted. For example, if one Project that has two Project Distributions is being promoted, add three items, one Project and two Project Distribution records.
**NOTE:**It is best practice to create one CTS Package for one Project.
-
Select dspMonitor_AccPak – Project from the CTS CONFIG ITEM ID list box.
-
Click Save.
-
Click Save on the Vertical View.
-
Select dspMonitor_AccPak – Project Distribution from the CTS CONFIG ITEM ID list box.
-
Click Save.
-
Click Save on the Vertical View.
-
If no additional items need to be added, click Cancel. Otherwise, continue to add Project and Project Distributions.
-
Click the Keys icon for the Project record.
-
Click Edit.
-
Enter the name of the ISA/IS Project being promoted in the VALUE list box.
NOTE: A list of available projects that match the entry display.
-
Select the project name from the list.
-
Click Save.
-
Click the back arrow on the browser to return to the CTS Items page.
-
Click the Keys icon of a Project Distribution record.
-
Click Edit.
-
Enter the name of the ISA Project Distribution being promoted in the VALUE list box.
NOTE: A list of available project distributions that match the entry display.
-
Select the project distribution name from the list.
-
Click Save.
-
Click the back arrow on the browser to return to the CTS Items page.
-
Continue adding Project Distribution keys until all of the Project Distributions have been included in the Project being promoted.
-
Click the back arrow to return to the CTS Build page.
-
Click the Build Packing List icon to build the packing list based on the keys entered; a confirmation message displays.
-
Click Ok.
-
After the Packing List build is complete, click the Build Archive icon; a confirmation message displays.
-
Click OK.
-
Locate the archive file created in the <installation folder>\Archives (e.g., C:\Program Files (x86)\BOA\DSP\Archives) and copy the file to the target environment into the same location.
Create the CTS Package of Schedules
To create the package:
-
Select Admin > CTS in the Navigation pane.
-
Click Add.
-
Enter a description in the DESCRIPTION field.
-
Click Save.
-
Enter a comment in the Comments field if necessary.
-
Click Save.
-
Click the Items icon for the newly created CTS Build.
-
If no records exist, the page displays in add mode. Otherwise, click Add.
NOTE: For each item added, there is a corresponding Schedule being promoted. If your ISA Project Distributions reference multiple Schedules then add multiple records to the CTS Archive
NOTE: All Schedules can be added to a single CTS Archive.
-
Select DSPCommon - Schedule from the CTS CONFIG ITEM ID list box.
-
Click Save.
-
Click Save on the Vertical View.
-
If no additional items need to be added, click Cancel. Otherwise, continue to add Schedules.
-
Click the Keys icon for the Schedules record.
-
Click Edit.
-
Enter the name of the Schedule being promoted in the VALUE list box.
NOTE: A list of available Schedules that match the entry display.
-
Select the Schedule name from the list.
-
Click Save.
-
Click the back arrow on the browser to return to the CTS Items page.
-
Continue adding Schedule keys until all of the Schedules have been included in the ISA Content being promoted.
-
Click the back arrow to return to the CTS Build page.
-
Click the Build Packing List icon to build the packing list based on the keys entered; a confirmation message displays.
-
Click Ok.
-
After the Packing List build is complete, click the Build Archive icon; a confirmation message displays.
-
Click OK.
-
Once the archive build is complete, the DATE CREATED is updated and the LOG should not show any entries.
-
Locate the archive file created in the <installation folder> \Archives (e.g., C:\Program Files (x86)\BOA\DSP\Archives) and copy the file to the target environment into the same location.
Create the Target Environment Project and Connections
NOTE: Confirm the names of the Project and connections from the source instance. These must be entered exactly when creating the project and connections in the CMC.
To create the target project and source connections in CMC.
-
Log on to the Central Management Console.
-
Navigate to the Information Steward area.
-
Right-click Manage and choose New > Data Insight Project.
-
Enter the name of the Project in the ISA source environment in the DSP®.
NOTE: The name must match the Project name in the ISA’s source instance or the import process will fail to align the source and target environments.
-
Enter a description.
NOTE: The description is required.
-
Click Save.
-
Right-click Manage and choose New > Connection.
-
Enter the connection details to the ISFailedData database on the DSP® database server, again ensuring that the name of the connection matches the name of the source environment IS failed data database.
-
Right-click Manage and choose New > Connection.
-
Enter the connection details to any other connections required by the IS project being exported. Ensure that the name of the connections is identical to the name used in the source environment.
-
Test all of the connections to ensure they connect to the target database environment correctly.
Import the IS Project into the Target IS Environment
The next step in the CTS process for ISA is to import the file that was exported in IS. .
To import the IS Project content from the source to the target:
-
Open the Information Steward Project that is being promoted into on the target environment.
-
Click the Import project and associated objects button on the Workspace Home window.
-
Click the Browse button next to the Import ZIP file path field on the Import window.
-
Select the IS export file created in the source environment.
-
Select the check box to overwrite existing objects.
-
Select the check box to automatically approve imported rules.
NOTE: This step is optional.
-
Select Select Administrators from the list box with the value Select Default Observer.
-
Click Next.
-
Map the connections contained in the Export file to the connections created in the target environment.
-
Click Import.
NOTE: If there are errors during the import that cannot be resolved, contact SAP support.
-
Click Close.
-
Click Finish.
Create Users in the Target ISA Environment
In the CTS process for ISA, the target environment must be set up with the user accounts required to support the ISA Project Distributions. If these user accounts do not exist in the target environment, they must be added by an Administrator user. Refer to Create User Accounts in System Administration for more information.
If user accounts that are assigned to ISA Project Distributions in the source environment are not present in the target environment, then those users will be automatically removed from the Project Distributions on import to the target environment.
Align the IS Metadata Repository with ISA
To run the Collect process that aligns the metadata:
- Select Collect in the Navigation pane.
- Select the dgRepository_IS Target record.
- Select the ISSAP Target Source on the Target Sources page.
- Click the Refresh icon to pull the latest metadata from IS into the ISA repository.
NOTE: If this is the first execution in the Target environment then a Build is required prior to the Refresh. Click the Build and Refresh icon.
NOTE: The Refresh must be successfully completed for all tables in the Collect ISSAP package.
Run Tasks Associated with the IS Project
To run tasks associated with the IS project:
- Open the Information Steward Data Insight Project that has been promoted into on the target environment.
- Click the Tasks tab on the left side of the window.
- Select each of the Tasks and click the Run Now button.
NOTE:To ensure that the Tasks are pointing to the correct Failed Data Connection, click the Edit button to view the Task properties.
Import the CTS Package of ISA Content into the Target Environment
Additionally, the CTS package created on the source system must be transferred to the following directory on the target ISA environment: <installation folder> \Archives e.g. C:\Program Files (x86)\BOA\DSP\Archives.
To import the CTS package:
- Select Admin > CTS> Archives in the Navigation pane.
- Click the Detect Archives icon.
- Refresh the Archives page until the CTS Archive created in the source environment displays.
- Click the Install icon for the CTS package containing the ISA content.
- Wait for the installation process to complete and check the Log to ensure correct import execution has occurred.
Import the CTS Schedules Package into the Target Environment
Additionally, the CTS package created on the source system must be transferred to the following directory on the target ISA environment: <installation folder> \Archives e.g. C:\Program Files (x86)\BOA\DSP\Archives
To import the package:
- Select Admin > CTS> Archives in the Navigation pane.
- Click the Detect Archives icon.
- Refresh the Archives page until the CTS Archive created in the source environment displays.
- Click the Install icon for the CTS package containing the Schedules.
- Wait for the installation process to complete and check the Log to ensure correct import execution has occurred.
Open the Project Summary Page to Align the Metadata
The final step in the CTS process for ISA is to access the Project Summary page.
To complete the CTS process for ISA:
-
Click Information Steward Accelerator > Project Summary in the Navigation pane.
NOTE: This triggers the alignment process stored procedure that runs on loading the project summary.
-
Review the Project / Project Distribution details to ensure they are aligned with the source ISA environment as expected.
Was this article helpful?
Sorry about that.
Why wasn't this helpful? (check all that apply)
Thanks for your feedback.
Want to tell us more?
Send an email to our authors to leave your feedback.
Great!
Thanks for your feedback.