3Setting Up Siebel ADM
Setting Up Siebel ADM
This chapter contains topics describing tasks for setting up Siebel Application Deployment Manager (ADM). It includes the following topics:
Siebel ADM Run-Time Requirements
The proper functionality of Siebel Application Deployment Manager (ADM) depends on run-time requirements for the following items:
Server Components That Must Be Enabled and Online
This topic is part of Siebel ADM Run-Time Requirements.
Specific server components must be enabled and online to run an Application Deployment Manager (ADM) deployment. See the following table for the server component groups that must be enabled to run an ADM deployment.
Table Server Component Requirements for ADM Deployment
Component Group |
Export |
Deploy from File |
HTTP Deployment |
---|---|---|---|
Auxiliary System Management (alias SystemAux) |
Required |
Required |
Required |
Enterprise Application Integration (alias EAI) |
Optional |
Optional |
Required |
System Management (alias System) |
Required |
Required |
Required |
Workflow Management (alias Workflow) |
Optional |
Optional |
Required |
Siebel Objects That Must Not Be Modified or Removed
This topic is part of Siebel ADM Run-Time Requirements.
If certain Siebel objects are modified or removed, then Application Deployment Manager (ADM) might fail to function properly. The following Siebel objects must not be modified or removed during the deployment:
Siebel Workflows
Do not modify or remove the following workflows:
ADM Deployment
ADM Restore
UDA Acknowledgement
UDA Batch Deployment
UDA Batch Import (Exception: before using this workflow to import customizations from the command line, you must update the Import File Directory property for this workflow.)
UDA Data Query
UDA Deployment
UDA Environment Verification
UDA HTTP Transport
UDA Import File
UDA Target Workflow
Siebel Business Services
Do not modify or remove the following business services:
ADM JDB Service
XML Converter
ADM Service
ADM Status Report Business Service
Access Controlled BS Cache Clear Service
Access Controlled Task Cache Clear Service
Configuring ADM Workflows
This topic describes configuring ADM workflows by activating the workflows, and is a necessary task before running an ADM deployment.
Activating a Siebel CRM workflow is a standard workflow administration procedure. For more information about workflows and activating workflows, see Siebel Business Process Framework: Workflow Guide.
You can also activate ADM workflows directly from the ADM screens by using the following procedure.
To activate ADM workflows
Navigate to the Application Deployment Manager screen, then the Data Type Details view.
In the Data Types list, click the Menu button, and then click Activate ADM Workflows.
About Siebel ADM Configurations for New Data Types
Siebel Application Deployment Manager (ADM) can be extended to support additional database and file data types for deployment. Creating a new database data type for deployment requires a new integration object and a new content object.
The following topics describe ADM system administration or configuration tasks that are sometimes necessary when preparing for ADM deployments of new data types:
For information about specific data type attributes used for creating new data types, see Siebel ADM Support for Additional Data Types. For other deployment and activation details for ADM data types, see Siebel ADM Supported Data Types.
Creating Integration Objects for ADM
This topic is part of About Siebel ADM Configurations for New Data Types.
Creating an integration object for Application Deployment Manager (ADM) allows you to migrate a new database data type using ADM.
The integration object specifies the format and structure of the set of data that you want to migrate.
Use the EAI Object Wizard in Siebel Tools to create integration objects. For more information about the integration objects and on using the EAI Object Wizard, see Integration Platform Technologies: Siebel Enterprise Application Integration.
To create an ADM integration object
Identify the business object that corresponds to the data type that you want to migrate using ADM.
This business object must have only one primary business component.
Start Siebel Tools or Siebel Web Tools.
Create a new workspace.
Choose File, then New Object.
From the New Object screen, select Integration Object.
The EAI Object Wizard guides you through the process of setting up an integration object.
Remove any unwanted fields or integration components from the new integration object.
Adjust the user keys of the integration object.
For more information about user keys for integration objects, see Integration Platform Technologies: Siebel Enterprise Application Integration.
Validate the integration object by selecting the integration object and clicking Validate.
Review the report, and modify your integration object as needed.
Creating Content Objects for ADM
This topic is part of About Siebel ADM Configurations for New Data Types.
Creating a content object for Application Deployment Manager (ADM) allows you to migrate new database data types using ADM.
Before creating a content object, make sure that you have created an integration object for the data that you want to migrate. See Creating Integration Objects for ADM.
The content object specifies the data to be migrated from one Siebel application to another. Each content object is composed of a business object and an integration object. Content objects are workspace-enabled.
Content objects are also used by Content Center. The following procedure references properties that are necessary for ADM functionality. For Content Center functionality, additional properties must be set for the content object. For more information about Content Center, see Siebel Applications Administration Guide.
To create a content object for ADM
Log in to Siebel Tools or Siebel Web Tools as an administrator.
Create a new workspace.
Navigate to the Content Objects type.
Create a new record.
Add the data type business object to the content object record.
Add the data type integration object to the content object record.
Create child records. On the child record, enter the name of a view that does not have any visibility setting (admin view) by selecting from the picklist.
The child record determines which view is used during the preview functionality in the ADM GUI. This view must correspond to the business object of the data area.
Configuring Integration Objects for ADM Deployment
This topic is part of About Siebel ADM Configurations for New Data Types.
Many Application Deployment Manager (ADM) data types have hierarchical structures of different objects that consist of parent-child relationships. In some cases, you might want to control how these hierarchies are deployed by removing the child entities from ADM deployments.
For example, the responsibility data type also migrates users as well as responsibilities, because responsibilities are associated with users and these users would need to be included with the responsibility. However, in this example, you might not want to migrate users between environments, because this migration deploys development users to a production environment.
To deploy only parent records of hierarchical relationships, you must disable the child integration component of the respective data type integration object. Perform the following procedure to configure this behavior.
Intermediate-level knowledge of the Siebel EAI architecture and integration is a prerequisite before performing these tasks. For more information about Siebel EAI, see Overview: Siebel Enterprise Application Integration.
For more information about using the synchronization wizard and configuring integration objects, see Integration Platform Technologies: Siebel Enterprise Application Integration.
To configure an integration object for ADM deployment
Start Siebel Tools or Siebel Web Tools.
Create a new workspace.
Select the integration object that you want to update.
Click Synchronize in the Integration Objects list.
The Integration Object Synchronize wizard appears.
Click the plus sign (+) to list all related integration components.
Select the checkboxes next to the integration components that you want to include in the integration object. Clear the checkboxes next to the integration components that you do not want to include (such as to disable a child integration component that you do not want to migrate).
Complete the wizard, and click Finish to synchronize the Siebel integration object and the Siebel business object.
Right-click the integration object, and select Validate to validate the integration object.