As with all Profiles, the Siebel Server Profile is created
in SMC: in this case, under the Profiles area, Siebel Servers node.
Unlike the Enterprise Profile, it is possible, and in fact likely
in a non-development environment, that you will create multiple Siebel
Server profiles. The following example profiles illustrate possible
examples how you might do this:
SiebSrvrUIProfile. Supports end-user
User Interface sessions.
SiebSrvrWFProfile. Supports background
workflow processes.
SiebSrvrEIMProfile. Supports Enterprise
Integration Manager processes for bulk data loads.
SiebSrvrRESTProfile. Supports REST integration.
Different profiles allow you to define specifically which
application services are available on a given Siebel Server and, if
needed, easily deploy an additional instance of that set of services
onto additional servers for high availability and scalability.
When determining how many profiles to create, you must consider
the different possible ways that users and other systems interact
with Siebel CRM. You can add more profiles and Siebel Servers at any
time, and you can deploy and redeploy a Siebel Server quickly if needed.
For assistance determining number of profiles, servers and so
on based on, customer requirements and expected usage, contact the
Oracle Advanced Customer Support team (Expert Services).
Create
the Siebel Server profile using the SMC as follows:
- From the Profiles/Siebel Servers node in SMC, create a
new Profile record.
- Select the Siebel Server Components that particular profile
will support.
At a minimum, you must create a profile which includes the
following sections:
Siebel Web Tools. This is used for making configuration changes
to the application.
Each Component Group that includes the application that will
be used. For example, if you plan to use Call Center, select the Siebel
Call Center Component Group, if you plan to use Financial Services,
select the Siebel Financial Services Component Group, and so on.
Enterprise Application Integration (EAI). It is required to
select this if you need access to the REST API.
You should also include any component group that contains a
component that is used for the specific implementation, such as Siebel
eDocuments, which is used for document generation on Windows servers
only, and so on.
Note: A Component Group typically contains many
individual server components. For example, the Enterprise Application
Interface Component Group contains more than ten server components,
each of which automatically starts when the Siebel Server service
starts. It is likely that only one or two of them is required. To
conserve resources on the server, the unwanted components can be disabled
using the Siebel Server Management utility. For more information,
see Siebel System Administration Guide in Siebel Bookshelf.
- Configure the Advanced Settings tab for load balancing
and high availability.
These are typically not required for development environments,
but can be used for other environments. For more information, see Siebel Installation Guide for Microsoft
Windows or Siebel Installation Guide for UNIX as appropriate.