Siebel Application Deployment Manager Guide > Overview of the ADM Architecture > About the ADM Orchestration Environment >
About the Siebel Management Server and ADM Deployment Engine
The Siebel Management Server is the prime infrastructure component that orchestrates an ADM deployment; that is, from initial loading to deployment. It also activates or restores the ADM deployment packages, if applicable, and tracks the status of the ADM deployment during this process. The Siebel Management Server maintains connections to Siebel Management Agents to initiate the ADM deployment process on the target environment. It also maintains connections to the ADM local database to store necessary details of the ADM deployment.
The ADM deployment engine resides in the Siebel Management Server along with the other system management and monitoring components. The ADM deployment engine is the portion of the Siebel Management Server that manages the deployment of an ADM package. It includes the following functionality:
- Enterprise Profile Manager. This component of the ADM deployment engine manages the ADM enterprise profile, which stores the following information:
- ADM Package Manager. This component of the ADM deployment engine opens an ADM package, loads the descriptor contents and dependencies into memory, validates the package, and manages the section of an ADM enterprise profile for the opened package. This module performs validation on the integrity of the individual files and the existence of all the files included in the ADM package.
- Environment Validator. This component of the ADM deployment engine verifies that all file deployment target Siebel Servers are able to handle file deployment, the Siebel Server root path and deployment path are accessible, and database or repository deployment target Siebel Servers are able to run ADM server components.
- Dependency Manager. ADM deployment dependencies between ADM deployment units can be organized in two places:
- In the ADM package descriptor file. The deployment of units is performed in the sequence listed in the ADM package descriptor file. By modifying the package descriptor file, you can control the deployment sequence so that the prerequisite items are deployed before the dependent items.
- In the Category Dependency section of the enterprise profile. By modifying the Category Dependency parameters, you can define the dependency of one category on another category's status for an action to start. For example, the execution of an action on the database category can depend on the status of the repository category to be MIGRATION_COMPLETE. This ensures that database units are not deployed unless all the repository units have the status of MIGRATION_COMPLETE.
- Item Deployer. This component of the ADM deployment engine sends deployment requests to the Siebel Management Agent on Siebel Server machines through the JMX interface. It passes the necessary information to the Siebel Management Agent and the target MBean (either Data MBean or File MBean).
- Status and History Manager. This component of the ADM deployment engine monitors the status of each deployment subsession and records the deployment history. It receives notifications from Siebel Management Agent about the deployment status and stores it in the ADM local database.
Siebel Management Server Installation and Configuration
For installation and configuration information on Siebel Management Server, see Siebel Installation Guide for the operating system you are using. For information on administering Siebel Management Server, see Siebel System Administration Guide.
For ADM-specific configuration information on Siebel Management Server, see Configuring the Siebel Management Server and Siebel Management Agent after Installation.