Bookshelf Home | Contents | Index | PDF     

Siebel Application Deployment Manager Guide > Configuring and Administering the ADM Framework > Process of Configuring the ADM Framework after Installing Siebel Management Server and Siebel Management Agent >

Configuring the ADM Enterprise Profile after Installation

This topic describes how to configure the initial ADM enterprise profile following the installation of Siebel Management Server and Siebel Management Agents. For more information, see Process of Configuring the ADM Framework after Installing Siebel Management Server and Siebel Management Agent.

For configuration updates to this file at later times and for more information on this file and its parameters, see:

To configure the enterprise profile after installation

  1. Navigate to MgmtSrvrInstallDir\ADM and open the entprofile_enterprise_name.xml file using the XML editor Microsoft Office InfoPath.
  2. Verify that the value for AgentName corresponds to xxx as specified in the following files:
    • agentconfig.xml file, located in MgmtAgentInstallDir\pref\system

      <entry key="registryhost" value="xxx">

    • configuration.agent.xml, located in MgmtSrvrInstallDir\pref\system

      <entry key="xxx" value="...">

  3. (Multiserver setup) Verify and update the SCBroker port number in the connect string for the server. The port for the SCBroker component is defined in the PortNumber component parameter.

    NOTE:  Only one server must be defined, since all servers will connect to the same database.

  4. Change the values in the DeployServer parameter.
    • (Single-server setup) Replace all the values for the DeployServer parameter with the value of AgentName as determined in Step 2, for example, <DeployServer>xxx</DeployServer>.
    • (Multiserver setup) List the deployment servers for the file, database, and repository data type categories in the DeployServer parameter with the value of the corresponding AgentNames, for example:

      <DeployServer>xxx</DeployServer> (for deploying on the server where the xxx agent is running)

      <DeployServer>yyy</DeployServer> (for deploying on the server where the yyy agent is running)

      NOTE:  For the file category, every deployment server in the enterprise must be listed. For the database and repository categories, only 1 of the deployment servers in the Siebel Enterprise Server must be listed, since all servers will connect to the same database.

      NOTE:  Entries for this parameter are case-sensitive.

  5. Provide the path for the ADM backup directory in the database and repository sections by changing all occurrences of <ADMBackupDir>\\net\CHANGE_ME\shared;\\CHANGE_ME\upload</ADMBackupDir> to:
    • For Windows, <ADMBackupDir>\\MachineName\upload</ADMBackupDir>

      where MachineName is the host name of the targeted machine.

      NOTE:  The entry is case-sensitive.

    • For UNIX, <ADMBackupDir>/tmp/upload</ADMBackupDir>

      The /tmp/upload path must be UNC qualified with full permissions.

      The path must be accessible from the Management Server and Management Agent, and the ADM backup directory must be a shared location. The user under whom the Management Agent process runs must have read/write access to the ADM backup directory.

      NOTE:  Management Server is supported only on a Microsoft Windows platform, while Management Agent is supported on both the Windows and UNIX platforms.

  6. To automatically run validation as part of all copy and activate commands during the deployment, set the value for the PerformValidation parameter to Yes:

    <PerformValidation>Yes</PerformValidation>

    If this value is set to Yes, then the validation automatically runs before any deployment or restore command. If it is set to No, then the validation will not be performed unless explicitly run as a separate command.

  7. Navigate to MgmtSrvrInstallDir\ and open the deploy_enterprise_name.bat file.
  8. Verify that the value of the deployment package location corresponds to the following and that the path is fully qualified:
    • For Windows, set ADM_PACK_LOC=\\MachineName\packages
    • For UNIX, set ADM_PACK_LOC=/mnt/packages

      The path must be accessible from the Management Server and Management Agent.

      NOTE:  Management Server is supported only on a Microsoft Windows platform, while Management Agent is supported on both the Windows and UNIX platforms.

  9. Create a directory share, upload, and make it network accessible with full permissions.

    For example, access the directory as follows:

    \\MachineName\upload

    This directory can be used as a backup location for ADM deployments. Siebel Management Agent users and Siebel Server users must have read and write access to this directory.

NOTE:  Do not add the ADMBackupDir flag to file data types in the enterprise profile. The backup, by default, is taken from the ADMFile directory on the Siebel Management Agent.

  
Siebel Application Deployment Manager Guide Copyright © 2007, Oracle. All rights reserved.