- Developing and Deploying Siebel CRM
- Deploying the Siebel Server Profile
Deploying the Siebel Server Profile
After successfully creating the Siebel Server profile, deploy it by doing the following:
- In the Siebel Management Console (SMC), navigate to the Siebel Deployment Hierarchy and click the plus (+) icon.
- Select Siebel Server.
- Enter the following information:
Host and Port. This the host where the Siebel Enterprise Servers (SES) components are installed and the HTTPS port number that was specified during that installation (for example, myserver.mycompany.com:9010).
Action. If you are planning to deploy immediately, select Deploy.
Siebel Server Name. It is recommended that you use the name of the physical host. For example, if your host is myserver.mycompany.com, then use myserver as the host. On rare occasions, you might deploy more than one Siebel Server per machine, for example, where Siebel Servers are clustered in Active-Active configuration for high availability. In this scenario, add an identifier to the server name to distinguish each from the other, for example, myserver_01, myserver_02, and so on.
Languages. These define all the languages this server supports. This selection is applicable to all Object Manager components, for example, user interface applications such as Call Center or Financial Services, and EAI integration components. However, this does not apply to components that are language-independent, such as Enterprise Integration Manager.
Creates a Window Service or a UNIX daemon to host the selected components.
Launches Siebel CRM processes to host these components. You can view these processes in Windows Task Manager or the output of the ps utility on UNIX. All Siebel processes will match the pattern: sieb*.
- Refresh the Siebel Deployment Hierarchy page until the
Siebel Server shows as fully deployed.
This might take several minutes. If deploying additional Siebel Servers to other machines using the same or different profile, you can deploy these profiles in parallel without waiting for earlier deployment(s) to complete.