Siebel Application Deployment Manager Guide > Deploying a Siebel ADM Package >

Deploying and Activating a Siebel ADM Package


Deploying and activating a Siebel Application Deployment Manager (ADM) package is a step in Process of Deploying a Siebel ADM Package. This task represents the migration and activation of the customizations for use in the target environment. This task uses the ADM command-line interface program. For information on this tool, see About the Siebel ADM Command-Line Interface Syntax.

Perform the commands in the following tasks to deploy and activate an ADM package:

  1. Creating an ADM Deployment Session
  2. Validating an ADM Deployment Environment
  3. Deploying an ADM Deployment Session
  4. Activating an ADM Deployment Session
  5. (Optional) Deploying and Activating an ADM Deployment Session

Several optional command-line flags further define the deployment and activation activities and are described in Table 8.

Table 8. Optional Command-Line Flags While Deploying and Activating ADM Packages
Flag              
Description

-async

Performs the command in asynchronous mode. The copy command returns immediately after issuing the command, but the actual deployment runs in the background. To check the status of the deployment, use the status_detail or track commands.

For more information on this command, see Reviewing an ADM Deployment's Status.

-activateonly

Specifies that this package has already been deployed and is for activation only.

-c

Lists the full set of command-line options, including default parameters not specified on the command line, to be used and prompts whether or not to execute the command. Valid with all execution modes of the deploy session (copy) command, except for -help. In quiet mode (-q), the command-line options are displayed, but there is no confirmation.

-fileservers

Deploys the package to only a subset of Siebel Servers within any Siebel Enterprise Server when used with a staged deployment on file servers. Takes the agent name, defined in the enterprise profile, as the argument.

-no_val_err

Ignores validation errors output and continues the command.

-q

Turns on quiet mode to suppress confirmations (-c option). Used with -c, the command is executed without confirmation.

-syncstatus

Updates the status of the deployment execution if any system errors occur that cause the status reporting on the ADM framework to lose the connection with the target Siebel Enterprise Server.

-t

Acts as a category filter on the ADM package when used with the arguments file, database, or repository.

-verify

Specifies that the deployment of this package is to be done in a verifiable session, and the package deployment is verified after completion. Used with the create session (create) command.

Execution of the deployment commands returns the error level values described in Table 9.

Table 9. ADM Deployment Command Completion Status Return Codes
Error Level Value
Result

0

Success. The command completed without errors.

1

Warning. The command executed, but errors were encountered.

2

Failure. The command failed to execute.

Additionally, there are several administrative commands that might be necessary to run during the deployment task, including starting and stopping the deployment, restoring the previous application customizations, and reviewing deployment status and reports. For more information on these commands, see Administering the Siebel ADM Deployment Execution.

Creating an ADM Deployment Session

The create command creates an ADM deployment session record, which represents the application customizations that are ready for migration based on the ADM package and enterprise profile referenced at that particular time.

To create an ADM deployment session

  • At the ADM command-line prompt, enter:

    deploy_enterprise_name create username password package_name

    For more information about the syntax elements of this command, see About the Siebel ADM Command-Line Interface Syntax.

    The create command can also use the following optional flags: -activateonly, -no_val_err, and
    -verify
    . For more information on these flags, see Table 8.

    NOTE:  You must use the -verify flag to enable postdeployment verification. You cannot verify the deployment of this package if the session is not set as verifiable.

Validating an ADM Deployment Environment

The validate command validates the run-time deployment environment by checking the following:

  • The schema version of the source environment (source of files) is compatible with the target environment (major schema version must match).
  • The Siebel Management Agent designated to receive the commands are online.
  • The Siebel Servers in the Siebel Enterprise Server referenced in the profile are online.

    NOTE:  The ADMProc server component must be enabled and running on each Siebel Server.

To validate an ADM deployment environment

  • At the ADM command-line prompt, enter:

    deploy_enterprise_name validate username password package_name

    For more information about the syntax elements of this command, see About the Siebel ADM Command-Line Interface Syntax.

    Only errors are returned to the command-line interface.

Deploying an ADM Deployment Session

The copy command updates the target environment with the application customizations defined by the ADM package and represented by the previously created deployment session.

NOTE:  To redeploy the same ADM package, you must acknowledge that session and create a new session to deploy the ADM data. For information on these tasks, see Acknowledging a Siebel ADM Deployment and Creating an ADM Deployment Session.

To deploy an ADM deployment session

  • At the ADM command-line prompt, enter:

    deploy_enterprise_name copy username password package_name

    For more information about the syntax elements of this command, see About the Siebel ADM Command-Line Interface Syntax.

    The copy command can also use the following optional flags: -t, -fileserver, -async, -c, -q, and -no_val_err. For more information on these flags, see Table 8.

Activating an ADM Deployment Session

The activate command activates, if possible, the new application customizations in the target environment.

To activate an ADM deployment session

  • At the ADM command-line prompt, enter:

    deploy_enterprise_name activate username password package_name

    For more information about the syntax elements of this command, see About the Siebel ADM Command-Line Interface Syntax.

    The activate command can also use the following optional flags: -t, -fileserver, -async, and -no_val_err. For more information on these flags, see Table 8.

Deploying and Activating an ADM Deployment Session

The copy_activate command is a combination command that can be used as an alternative to running the deploy (copy) and activate commands separately. It updates the target environment with the application customizations defined by the ADM package and represented by the previously created deployment session. This command also activates, if possible, the new application customizations in the target environment.

To deploy and activate an ADM deployment session

  • At the ADM command-line prompt, enter:

    deploy_enterprise_name copy_activate username password package_name

    For more information about the syntax elements of this command, see About the Siebel ADM Command-Line Interface Syntax.

    The copy_activate command can also use the following optional flags: -t, -fileserver, -async, and -no_val_err. For more information on these flags, see Table 8.

ADM Broadcast Announcement

ADM issues a broadcast announcement to all user accounts that are of the same position as the user doing the deployment.

For example, if your position is Admin-Manager and you use ADM to deploy a package, then all other users with position Admin-Manager get the announcement about the deployment. To prevent other users from getting this announcement, create a new position (for example: ADM-Deployer) just for yourself and use that position when you deploy. The announcement appears in the message bar.

Siebel Application Deployment Manager Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.