Siebel Installation Guide for UNIX > Installing and Configuring Siebel Management Agents and Siebel Management Server >
About Configuring Siebel Management Agents and Siebel Management Server
This topic provides background information about configuring Siebel Management Agents and Siebel Management Server.
Siebel Enterprise and Siebel Gateway Name Server
When you are configuring an instance of Siebel Management Server for use with Siebel Application Deployment Manager (Siebel ADM), the Siebel Enterprise and Siebel Gateway Name Server that you specify during configuration must be those for the target environment (not the source environment) for any data migration operations that you will be performing. See also Siebel Application Deployment Manager Guide.
NOTE: It is possible to configure Siebel Management Server to support multiple Siebel Enterprises. It is recommended that you keep configuration as simple as possible for a deployment of this type. For example, where a Siebel user is specified during configuration, specifying a standard Siebel administrator account, such as SADMIN, simplifies the overall deployment.
Secure Sockets Layer
Configuring Siebel Management Agents and Siebel Management Server includes steps for specifying Secure Sockets Layer (SSL) encryption for communications between components. Before configuring, review topics about SSL encryption in Siebel Security Guide.
Default Port Numbers for the Siebel Management Framework
The following port numbers are used by default by components of the Siebel Management Framework:
- Siebel Management Agent: port 1199 (RMI registry)
- Siebel Management Server: port 1099 (RMI registry)
If you are using nondefault port numbers, then you can specify the correct port numbers in the Configuration Wizard for Siebel Management Agent or Siebel Management Server.
As noted in Using Perl Scripts to Finish Configuring Siebel Management Agents and Siebel Management Server, an intermediate file output by a Perl script assumes the default Siebel Management Agent port number of 1199. Update this file as necessary to reference the correct port number.
Anticipate whether you might have port number conflicts with other components on individual computers and take steps to avoid conflicts. For example, the Siebel Charts server also uses port 1099. For more information, see Installing Siebel Charts.
Siebel Management Server uses Apache Tomcat internally. If this Siebel module and another product using Apache Tomcat are installed on the same computer, then you might encounter port conflicts. If necessary, edit the file server.xml to specify unique port numbers. For Siebel Management Server, this file is located in the
tomcat\conf subdirectory of the installation directory. Port 8005 is used for Tomcat shutdown.
To change the port number
Requirements for the Siebel ADM Package Directory
Note the following requirements for the Siebel ADM package directory. This directory stores packages before deployment in the target environment. You specify the default location while configuring Siebel Management Server.
- The directory that you are specifying as the default location must already exist before you configure Siebel Management Server. The Siebel Management Server Configuration Wizard does not create this directory.
- Users who deploy ADM packages must have read and write permissions in this directory.
- The directory must be a shared network resource that is available to the Siebel Management Server and to Siebel Management Agents on all of the Siebel Server computers.
- For deployments using only Siebel Servers on Microsoft Windows, set a value with a fully qualified path, as in this example:
- For deployments using one or more Siebel Server on a Windows server computer and one or more Siebel Server on a UNIX server computer, set a value with two fully qualified paths (one for Windows and one for UNIX), separated by a semicolon, as in this example:
NOTE: Siebel Management Server is supported only on Microsoft Windows, while Siebel Management Agent and Siebel Server are supported on both Windows and UNIX operating systems. The paths defined in the setting of ADM_PACK_LOC must specify the same location as it would be accessed from servers on both Windows and UNIX.
- After you run the Siebel Management Server Configuration Wizard and run the admconfig.pl script, the value that you specify is stored in the batch file deploy_enterprise_name.bat as the value of the parameter ADM_PACK_LOC. This file is created in the Siebel Management Server installation directory:
\pref\system. For more information about this file, see Using Perl Scripts to Finish Configuring Siebel Management Agents and Siebel Management Server.
For information about how to use the file deploy_enterprise_name.bat and about the task for configuring the ADM enterprise profile, see Siebel Application Deployment Manager Guide.
- For deployments in which Siebel Management Agent is installed on one or more UNIX computers, a cross-platform networking tool such as Samba might be required to help provide access to the ADM package directory and to the Siebel Management Server on Windows.
Perl Scripts for Configuring Siebel Management Agent and Siebel Management Server
A series of Perl scripts is provided with Siebel Business Applications as a mandatory part of configuring Siebel Management Agent and Siebel Management Server for use with Siebel ADM. The execution tasks are described in Using Perl Scripts to Finish Configuring Siebel Management Agents and Siebel Management Server.
The Perl scripts provided are:
- getservers.pl. This script is provided with both Siebel Management Agent and Siebel Management Server.
- makeagentconfig.pl. This script is provided with both Siebel Management Agent and Siebel Management Server.
- admconfig.pl. This script is provided with Siebel Management Server only.
Location of the Perl Scripts
On Siebel Management Agent, the Perl scripts (getservers.pl and makeagentconfig.pl only) are located in:
In this path, MgmtAgentInstallDir is the Siebel Management Agent installation directory, such as
C:\siebel\126.96.36.199.0\ses\siebsrvr\mgmtagent (on Windows) or
/siebel/188.8.131.52.0/ses/siebsrvr/mgmtagent (on UNIX).
On Siebel Management Server, the Perl scripts (getservers.pl, makeagentconfig.pl, and admconfig.pl) are located in:
In this path, MgmtSrvrInstallDir is the Siebel Management Server installation directory, such as
C:\sba82\mgmtsrvr (on Windows only).
Requirements for Executing the Perl Scripts
Review the following requirements for executing the Perl scripts:
- The Siebel Server, Siebel Management Agent, and Siebel Management Server must be up and running, and the Siebel ADM server components must be enabled and running.
- Use the minimum supported version of Perl, as noted in the Certifications tab on My Oracle Support.
- Execute the Perl scripts getservers.pl and makeagentconfig.pl on a computer on which you have installed a Siebel Server because these scripts have to run srvrmgr.
In general, this topic assumes that you execute these Perl scripts on a computer where you have installed both Siebel Server and Siebel Management Agent. By contrast, you execute the script admconfig.pl on a computer where you have installed Siebel Management Server.
What the Perl Scripts Do
Executing getservers.pl and makeagentconfig.pl invokes the srvrmgr executable program to retrieve information from the Siebel Gateway Name Server about installed Siebel Servers and Siebel Management Agents. Executing the Perl scripts generates XML files containing data needed by Siebel Management Server, which registers all of the Siebel Management Agents with the Siebel Management Server.
You execute admconfig.pl on the Siebel Management Server computer after executing the scripts getservers.pl and makeagentconfig.pl. The admconfig.pl script generates the files deploy_enterprise_name.bat and entprofile_enterprise_name.xml. In these file names, enterprise_name is the name of the Siebel Enterprise.
After verifying or updating port numbers in these files, you then copy the XML files to the Siebel Management Server (updating existing files).
Execute the Perl scripts additional times in the following cases:
- If you add more Siebel Servers with Siebel Management Agents later. These instances of Siebel Management Agent must be registered with the Siebel Management Server.
- If your Siebel Management Server must work with more than one Siebel Enterprise, such as if Siebel ADM must support multiple Siebel Enterprises.
- If multiple instances of Siebel Management Servers are required for any reason. (For two or more Siebel Enterprises with the same name, you must install a separate instance of Siebel Management Server for each unique Siebel Enterprise name.)