Siebel Application Deployment Manager Guide > Siebel ADM Supported Data Types >

Siebel ADM Data Type Details

The Siebel Application Deployment Manager (ADM) deployment process can vary slightly or have limitations or configurations associated with it, depending on the data type selected for migration. Review the following subset of data types for further details to configure or take into account during ADM deployment and activation.

You can create hierarchy for any objects you migrate using ADM. If your data type is close to a standard data type, then you can create a new data type. To do this, navigate to the Application Deployment Manager screen, then the Data Type Details view. Select the existing data type, choose Copy Record, and then modify the new data type record.

For example, the AssignRule data type has a child type Workload Rule. If the assignment rule does not have a workload rule, then this data type cannot be used to deploy assignment rules. You can create a new ADM data type by copying the AssignRule data type and giving it a different name. After creating the new data type, delete its child data type Workflow Rule. To do this, navigate to the Application Deployment Manager screen, then the Data Type Explorer view. In general, it is recommended not to modify the standard data type.

The following ADM data types are some of those that have additional ADM details:

• List of Values.
• Organizations, Divisions, and Positions.
• Personalization - Actions.
• Personalization - Event Defs.
• Personalization - Rules.
• Run-Time Business Service.
• SmartScript. See also Validating the SmartScript Data Type.
• UI Theme.
• Workflow Policy.
• Workspace Projects.

List of Values

The List of Values (LOV) data type has the following behavior when deployed using ADM: the hierarchy in the List of Values Explorer view is different from the hierarchy in the List of Values list view. The List of Values Explorer view defines relations between different LOV types. To define relations within the same LOV type, use the Parent LIC field in the List of Values list view instead.

NOTE:  Hierarchical LOV data for the same LOV type that is defined in the List of Values Explorer view cannot be migrated using ADM. An error is generated during data export in this case.

Organizations, Divisions, and Positions

Organizations, divisions, and positions are implemented as a hierarchy as follows:

Organizations
   Divisions
      Positions

You cannot implement divisions without first implementing organizations. Similarly, you cannot implement positions without implementing organizations first and then divisions.

Personalization - Actions

The Personalization - Actions data type has the following behavior when deployed using ADM: this data type is imported together with, but before, Personalization - Events data type. Both data types require the same activation and restore activation, which are defined only for Personalization - Events.

Personalization - Event Defs

The Personalization - Events Def data type has the following behavior when deployed using ADM: this data type is imported together with, but before, the Personalization - Events data type. Both data types require the same activation and restore activation, which are defined only for Personalization - Events.

Personalization - Rules

The Personalization - Rules data type has the following behavior when deployed using ADM: this data type is imported together with, but before, the Personalization - Applets data type. Both data types require the same activation and restore activation, which are defined only for Personalization - Applets.

Run-Time Business Service

The Run-Time Business Service data type has the following condition when packaging this data with ADM: the Run-Time Business Service data is only allowed in Synchronize deployment mode.

SmartScript

The SmartScript data type has the following limitations when deploying with ADM:

• The new version of existing SmartScripts are activated when all users have stopped using old version.
• Make sure SmartScripts deployed using ADM are valid. For information on how to validate SmartScripts, see Validating the SmartScript Data Type.

Validating the SmartScript Data Type

SmartScripts deployed using ADM must be valid. If you export unverified SmartScripts, then the generated XML file is incorrect. For more information on SmartScripts, see Siebel SmartScript Administration Guide.

To validate SmartScripts

1. Navigate to the Administration - SmartScript screen, then the Scripts view. Select a SmartScript.
2. From the Menu button, select Verify.
3. The wizard starts and displays the Verify Intro view.

   For more information on this task, see Siebel SmartScript Administration Guide.

UI Theme

Perform the step below to access the UI Theme data type when packaging it with ADM.

To access the UI Theme data type when packaging it with ADM

• Click the UI Themes data type link from the Deployment Projects, Data Type list to display the ISS Product Administration View.

  From this view, you can access UI Theme records in the pick applets of the Base Theme or Product Theme fields in the Administration - Product screen, User Interface list applet.

Workflow Policy

The Workflow Policy data type requires additional attention when activating it after an ADM deployment. Perform the following task to make sure additional configurations are satisfied.

To make sure Workflow Policy data type is ready for activation

1. Make sure the Workflow Management (alias Workflow) component group is enabled. For information on this procedure, see Siebel System Administration Guide.
2. Update the following parameters for the Generate Triggers (alias GenTrig) server component:
   • PrivUserName to Table Owner Name (for example, SIEBEL)
   • PrivUserPass to table password (for example, db2)

     NOTE:  PrivUserName is the Table Owner Name.

3. Update the named subsystem ADMJavaSubsys:
   1. Navigate to the Administration - Server Configuration screen, then Enterprises, and then the Profile Configuration view.
   2. In the Profiles list, select ADMJavaSubsys.
   3. In the Profile Parameters list, select the JVM Classpath parameter, and add siebelmgrclient.jar to the class path.

      NOTE:  The number of characters in the class path must not exceed 100 characters.

4. Synchronize batch server component Application Deployment Manager Processor (ADMProc).

   For information on this task, see Siebel System Administration Guide.

5. Make sure the Workflow Policy Activation Server (WfPolicyActSrvr) in the ADM enterprise profile is the name of the correct server.
6. Restart Oracle's Siebel Server.

Workspace Projects

The Workspace Projects data type has the following variations to general ADM deployment behavior:

• The deployment mode selection in the ADM Deployment Project view is set to custom for Workspace Projects, because this data type implements its own migration method (similar to synchronize) to make sure that the entire Workspace Project is fully migrated.
• The Workspace Project data type has its own syntax for the deployment filter field:

  [Name] = "Any joint workspace name" [Full] = "Y/N"

  where:

  • [Name] is required.
  • [Full] is optional. The filter field defaults to N if no value is specified.

    The optional Y or N flag indicates a full structure export or single object export for the objects included in the Workspace Project. In other words, Y indicates a full structure export, and N indicates a single object export.

    For example, if a Workspace Project named Vehicle Products includes a Product called Car, then if [Full] is set to Y, then the associated product attributes like colors, options, accessories, and so on, are also exported, but if set to N, then they are not exported. Also, only one Workspace Project name can be specified in the filter and be exported for each entry.