A package is the record and configuration created on the CTS pages in the DSP®. An archive is built from a package and is the actual item(s) and configurations moved via the CTS process.
The CTS Configuration for DSP WebApps is included by default and must not be updated on the CTS Configure pages.
The CTS Configuration for custom WebApps must be created before objects can be moved via the CTS process. Refer to Set a Baseline Configuration for a Custom WebApp.
To create a CTS package and build an archive for a delivered WebApp:
- Log in to the DSP® source instance.
- Select Admin > CTS > Build in the Navigation pane.
- Click Add.
Enter a unique name for the CTS package in the DESCRIPTION field.
NOTE: Since the CTS process for all applications on the system is managed within the System Administration Component, it is recommended to include the name of the component (for example, Collect) in the description to easily identify the application(s) relevant to the contents of an archive once it is created. As a best practice, create one package per component.
- Click Save; the Vertical View displays.
Verify the Include Objects check box is checked.
NOTE: If checked, objects added on the CTS Configure (SQL Object Registrations) page are included in the package.
Click the Show Hidden Items check box to check it.
NOTE: If checked, CTS items defined as “hidden” (CTS > Configuration > Shippable Items > Vertical View) are visible in the packing list.
- Enter additional documentation in the Comments field, for example, a description of what the package contains.
Select a value from the Trace Level list box. The default value is Warning. Values are:
- Debug — A detailed message displays to provide data about the process.
- Message — An information message displays to mark a landmark in the code.
- Warning — A message displays to inform the user that a problem could surface.
- Error — An error message displays while the process is executing; processing can continue.
NOTE: The Trace Level indicates the amount or level of detail of information that is provided in the log (which is accessed by clicking the Log icon on the CTS Build page's Horizontal View) if an error occurs when building the packing list and the archive. The order of details provided is Error, Warning, Message and Debug, where Error provides the least amount of information and Debug provides the greatest amount of information.
- Click Save.
- Click Items on the Horizontal View to specify the item(s) to include in the package.
- Click Add. If no records exist, the page automatically opens in add mode.
- Select an item to include in the package from the CTS CONFIG ITEM ID list box.
NOTE: To move the wave initially, select Console – Wave from this list box, then select the wave’s key on the CTS Item Keys page.
NOTE: The CTS CONFIG ITEM ID list box displays every item available to be moved via the CTS process for every component.
NOTE: Items in this list box display with the following names:
- DataGarage refers to Collect objects
- DSW refers to Transform objects
DataDialysis refers to dspMonitor ™ objects
- DSPCommon refers to Common objects
- CranSoft refers to platform objects
Use the following table to add the pre-defined items from the CTS CONFIG ITEM ID list box to the CTS package for each application.
NOTE: Follow the order in which the applications are listed in this table when adding applications and items.
Items to add to the CTS package
DSPCommon — dspCommon System Type
DSPCommon — Common System Type Table
DSPCommon — Common System Type Group
DSPCommon — Common System Type Table Index
DSPCommon — Schedule
DSPCommon — Common Automation Instructions
DSPCommon — Common Automation Instruction Task
DSPCommon — Common Automation Instruction Task Group
DSPCommon — Common Automation Engine Action
DataGarage — Collect Target
DataGarage — Collect – Target Source
DataGarage — Target Source Table
DataGarage — Target Source Table Rule
DataGarage — Target Source Table Index
Console — Field Group
Console — Metric Group
Console — Process Area
Console — Object
Console — Target
Console — Source
Console — Wave
Console — Wave Process Area
Console — Wave Process Area Object
Console — Wave Process Area Object Target
Console — Wave Process Area Object Target Source
Console — Execution Stage
Console — Complex Rule
Console — Simple Rule
Console — Rule Condition
Console — Target Lookup Table
cMap — Wave Process Area Object
cMap — Value Mapping Check Table
cMap — Wave Process Area Object Target
InterfaceServer — File Operation
InterfaceServer — Interface
InterfaceServer — Logical Path
dspCompose — Team
dspCompose — OrgUnits
dspCompose — Roles
dspCompose — dspCompose Template
DataDialysis — Group
DataDialysis — Object
DataDialysis — Report Repository
DataDialysis — Report
DataDialysis — Filter
Integrate — Integrate Category
Integrate — Integrate Template
Integrate — Integrate Process
Integrate — Integrate Process Template Connection
DSW — Object
DSW — Target
DSW — Target Report
DSW — Target Rule
DSW — Target Export
DSW — Target Data Services Report
DSW — Target Data Services Rule
DSW — Target Source
DSW — Target Source Report
DSW — Target Source Rule
dspConduct — 1.Category
dspConduct — 2.Business Processes
dspConduct — 3.Scenarios
dspConduct — 4.Roles
dspConduct — 5.Tasks
dspConduct — 6.Org Units
dspConduct — 7.Positions
dspConduct — Org Unit Groups
dspConduct — Workflow Defaults
CranSoft — Archive
CranSoft — Audit
CranSoft — Catalog
CranSoft — Color
CranSoft — CTS Configuration
CranSoft — Data
CranSoft — Data Source
CranSoft — Database Type
CranSoft — Dictionary
CranSoft — File
CranSoft — Folder
CranSoft — Group
CranSoft — Image
CranSoft — Language
CranSoft — Layout
CranSoft — Menu
CranSoft — Message Types
CranSoft — Page
CranSoft — Page Column Property
CranSoft — Page Event
CranSoft — Plugin
CranSoft — Queue
CranSoft — Search
CranSoft — Security Definition
CranSoft — Security Role
CranSoft — SQL Object
CranSoft — SQL Script
CranSoft — Stop Word List
CranSoft — Style
CranSoft — Translation
CranSoft — WebApp
Update the Include check box if the default value is not applicable.
NOTE: If checked, the relevant item is included when the packing list is built. If unchecked, the item is ignored when the packing list is built. Default value is enabled.
- Click Save; the Vertical view displays.
Update the Purge check box if the default value is not applicable.
NOTE: If checked, any child items related to the item that had Purge enabled are deleted when the archive is installed.
- Click Save.
- Add additional items from the CTS CONFIG ITEM ID list box or click Cancel to configure keys for the items.
Click the Keys icon for the CTS CONFIG ITEM ID.
NOTE: All required keys for the item display. Multiple keys may display, depending on the type of item included in the package. The keys required for each item are set in the CTS Configuration.
- Click Edit for the key.
- Select the specific item from the VALUE combo box.
NOTE: Each specific item included in the package has to be added individually to the CTS Items page. There is no process to add all items to a CTS package.
- Click Build in the Navigation pane.
- Click the Build Packing List icon to create a list of items and dependencies to include in the package; a confirmation message displays.
- Click OK.
- Click Log to view any messages or errors.