System Administration

CTS Overview

The Change and Transport System (CTS) process migrates objects from a source instance to a target instance of the Stewardship Tier. In order to CTS objects, the user must have access to the CTS menu in System Administration and the target and source instance must be defined.

A user can build a CTS Package that automatically contains all of the items required to successfully promote the entirety of a Wave (and all its dependents) to another environment using the CTS process. Refer to Create a CTS Package and Build Archive in Source Instance or more information.

The Stewardship Tier can also generate a baseline CTS configuration for custom WebApps. In this case, the Stewardship Tier uses a crawler to locate the object’s registrations, dependencies and relationships and adds the records to the appropriate CTS Configuration page. The user then sets the registrations and shippable items based on the autogenerated data. Refer to Set a Baseline CTS Configuration for a Custom WebApp for more information.

NOTE: If Encrypted columns are included in the CTS, then either both the Source and Target Stewardship Tier instances must use the same encryption keys or the encrypted columns must be updated in the Target System

NOTE: The maximum archive size is 4MB by default. The 4MB setting can be changed in IIS.

Each WebApp has a pre-defined set of items that can be moved from a source instance to a target instance. Refer to the following table for a list of objects that can be moved between instances via the CTS process (as in, Shippable Items):

Application

Object to Move Via CTS

Assemble

CranPort Packages

Automate

File Operations, Interfaces, Logical Paths

Collect

Targets, Sources, Tables, Rules, Indexes

Common

Automation Engine (Instruction Task Groups, Instruction Tasks, Tasks, Engine Actions, Instructions), System Types (Groups, Tables. Table Indexes), Schedules 

Console

Waves, Process Areas, Objects, Targets, Sources, Target Lookup Tables, Rules (Simple, Complex and Conditions), Field Groups, Metric Groups, Execution Stages, Execution Groups, Load Cycles, Milestone Types, Page Column Auto Add Field, Page Group Column Status, Planning Group, Wave Execution Group Value, Wave Load Cycle, Wave Load Cycle Object Exclusion, Wave Load Cycle Planning Group, Wave Milestone, Wave Milestone Planning Group, Wave Planning Group

DSP

(Stewardship Tier)

Archives, Audits, Catalogs, Color, CTS Configs, CTS Config Item, Database Types, Data Sources, Dictionaries, Groups, Images, Languages, Layouts, Menus, Menu Link, Message Types, Pages, Page Columns, Page Extension, Page Events,Page Event Rule, Page Event Validation, Plugins, Queues, Roles, Searches, Security Definitions, Stop Lists, Styles, Translations, WebApps

dspCompose

(Mass Maintenance)

Org Units, Roles, Teams, Templates

Data Dialysis

Enhanced Migration Reporting

Groups, Objects, Report Repositories, Reports, Filters

Integrate

Categories, Templates, Processes, Process Template Connections

ISA

Project and Project Distributions

Map

Value Mapping Check Tables, Wave Process Area Object, Target Mappings

Transform

Objects, Object Execution Template, Targets (Rules, Reports, Exports, Data Services Rule), Sources (Rules, Reports), Target Data Services (Rules, Reports)

NOTE: Notes specific to ISA, Mass Maintenance, Data Quality are available.

NOTE: A package is the record and configuration created on CTS pages in the Stewardship Tier. An archive is built from a package and is the actual item moved via the CTS process.

To CTS an object:

  1. Set up the instances (for example, DEV and QA).
  2. Create package and build the archive on the source instance (for example, DEV).
  3. Export the archive to the target instance (for example, QA).
  4. Import the archive. The CTS process installs or updates the appropriate application objects from the archive.
  5. Validate the new objects to ensure all functionality is updated correctly.