Siebel Installation Guide for UNIX > Installing and Configuring Siebel Management Agents and Siebel Management Server > Process of Configuring Siebel Management Agents and Siebel Management Server >

Configuring Siebel Management Agents


This topic describes how you configure the Siebel Management Agents after installation. You configure each instance using the Siebel Management Agent Configuration Wizard.

NOTE:  On Microsoft Windows, if you are using database authentication, then, in order to select the Configuration Wizard option to start the Siebel Management Agent immediately, you must have already installed the Siebel database schema and seed data. For more information about performing these tasks, see Installing the Siebel Database on the RDBMS.

This task is a step in Process of Configuring Siebel Management Agents and Siebel Management Server.

To configure Siebel Management Agents

  1. Review About Configuring Siebel Management Agents and Siebel Management Server and Requirements for Installing and Configuring Siebel Management Agents and Siebel Management Server.
  2. To start the Siebel Management Agent Configuration Wizard at the command line, first open a new command window.
  3. Set the following environment variables, according to your operating system. (In Step 4, you start the wizard at the command line in the same command window.)
    • AIX:

    setenv LIBPATH $SIEBEL_ROOT/siebsrvr/mgmtagent/lib:{LIBPATH}

    setenv PATH $SIEBEL_ROOT/siebsrvr/mgmtagent/bin:{PATH}

    • HP-UX:

    setenv SHLIB_PATH $SIEBEL_ROOT/siebsrvr/mgmtagent/lib:{SHLIB_PATH}

    setenv PATH $SIEBEL_ROOT/siebsrvr/mgmtagent/bin:{PATH}

    • Linux and Oracle Solaris:

    setenv LD_LIBRARY_PATH $SIEBEL_ROOT/siebsrvr/mgmtagent/lib:{LD_LIBRARY_PATH}

    setenv PATH $SIEBEL_ROOT/siebsrvr/mgmtagent/bin:{PATH}

    In these commands, $SIEBEL_ROOT is the parent directory for the installation.

    NOTE:  It is recommended that you save the commands that you require into a shell script.

  4. Start the Siebel Management Agent Configuration Wizard.

    A screen appears that requests the account details of the Siebel user who accesses Siebel Management Agent.

  5. Enter the Siebel user name and password, confirm the password, and then click Next.

    Specify a Siebel administrator user, such as SADMIN.

    The wizard requests the location of the Java Runtime Environment (JRE) home directory.

  6. Click Browse to navigate to the JRE home directory. Select the directory, and click Next.

    The wizard displays a check box that allows you to enable RC2 encryption for the Siebel user account that you specified in Step 5. By default, the check box is clear. For more information about RC2 encryption, see Siebel Security Guide.

  7. Take the appropriate action:
    • To enable RC2 encryption of the Siebel user's password, select the check box, and click Next. Specify the full path to the RC2 key file.
    • To leave the Siebel user's password encoded in base64 Content-Transfer-Encoding, leave the check box clear, and click Next.

      The wizard requests the port number for the RMI Registry. Requests to connect to this Siebel Management Agent use this port number (default 1199).

  8. Enter the port number for the RMI Registry, or accept the default, and then click Next.

    The wizard requests the type of authentication to deploy for Siebel Management Agent. You must select the same type of authentication for both Siebel Management Server and any Siebel Management Agents that connect to this Siebel Management Server. For more information about authentication types, see Siebel Security Guide.

  9. Select the type of authentication. Do one of the following, and click Next:
    • If you selected LDAP or Database, then go to Step 10, and specify the path to the security adapter file. Use one of these options for production deployments.
    • If you selected None, then go to Step 11. This option is not suitable for production deployments.

      NOTE:  Selecting None allows the user specified in Step 5 to perform Siebel ADM deployment operations without any other authentication.

  10. Specify the path to the security adapter file (located in the bin subdirectory of the Siebel Management Agent installation directory), and click Next.
    • For LDAP, specify the file secadp.cfg.
    • For database authentication, specify the file odbcsecadp.cfg.

      The wizard asks if you want to deploy the Secure Sockets Layer (SSL) protocol for Siebel Management Agent. For more information about SSL, see Siebel Security Guide.

  11. Take the appropriate action:
    • To deploy with SSL, select the SSL radio button, and click Next. Go to the next step.

      For more information about configuring SSL for Siebel Management Agent and Siebel Management Server, see Siebel Security Guide.

    • To deploy without using SSL, select the NoSSL radio button, and click Next. On Windows, go to Step 16. On UNIX, go to Step 18.
    • To deploy for local communications only (with no SSL between different computers), select the LoopBack radio button, and click Next. Go to Step 16.

      This option binds to a loopback address and accepts connections only from the same computer. You can use this option when Siebel Management Agent and Siebel Management Server are installed on the same Windows computer.

  12. Take the appropriate action:
    • To use the SSL protocol for communications from the client, select Client, and click Next. (The client in this context is the Siebel Management Server.) The wizard requests the Private Key File Name and Private Key File Password. Go to Step 14.
    • To use the SSL protocol for communications in both directions (between the Siebel Management Server and the Siebel Management Agents), select Dual, and click Next. The wizard requests the name of the SSL provider.
    • To use the SSL protocol for communications from the server, select Server, and click Next. (The server in this context is the Siebel Management Agent.) The wizard requests the name of the SSL provider.
  13. For Dual or Server configuration, specify the name of the SSL encryption provider, and click Next. Specify one of the following:
    • JSSENoStubProviderWrapper
    • RSAProviderWrapper
    • SunJSSEProviderWrapper

      For more information about these options, see Siebel Security Guide.

      The wizard requests the Private Key File Name and Private Key File Password.

  14. Enter values for the Private Key File Name and Private Key File Password, and click Next.

    The wizard requests the name of the Truststore file.

  15. Enter the name of the Truststore file, and click Next:
    • On Microsoft Windows, go to the next step.
    • On UNIX, go to Step 18.
  16. Enter the Windows User Account and the Windows User Account Password, confirm the password, and then click Next.

    The wizard asks if you want to start Siebel Management Agent.

  17. Take the appropriate action:
    • To start Siebel Management Agent when configuration completes, select the check box, and click Next.

      NOTE:  On Microsoft Windows, if you are using database authentication, then, in order to select this option, you must have already installed the Siebel database schema and seed data. For more information about performing these tasks, see Installing the Siebel Database on the RDBMS.

    • To start Siebel Management Agent at a later time, leave the check box clear, and click Next.

      The wizard summarizes the selections that you have made.

  18. Review this information, and take the appropriate action:
    • If the information is correct, then click Next to complete the configuration. A dialog box appears that asks if you want to execute the configuration. Go to the next step.
    • If the information is incorrect, then click Back to return to the parameter that you want to modify.
  19. Click OK to execute the configuration, and complete the configuration of the Siebel Management Agent.

    After you have configured all of the Siebel Management Agents, do one of the following:

Siebel Installation Guide for UNIX Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.