Siebel management server install

Microsoft Windows Server or Windows Server Before you run the installer executable program setup. Double-click setup. Click Next. Select an instance of Siebel CRM version 8. Follow all of the prompts to complete the installation of Siebel CRM version 8. Restart the Siebel Management Server service.

The wizard requests the name of the machine that hosts the Siebel Gateway Name Server. It also requests the port number default on which the Gateway Name Server listens for requests. The wizard requests the account details of the Siebel user who administers the Siebel Management Server. The wizard requests the account details of the Siebel user who accesses Siebel Diagnostic Tool.

The wizard displays a check box that allows you to enable RC2 encryption for the Siebel user account you specified in Step 4. By default, the check box is clear.

The port number for the Diagnostic Tool default is the port number where it listens for requests. The wizard requests the location of the JRE home directory. The wizard requests the type of authentication to deploy for Siebel Management Server.

For more information about the authentication types, see Siebel Security Guide. For database authentication, after you configure the software you must edit the file odbcsecadp. The wizard requests the Microsoft Windows account details for the machine that hosts Siebel Management Server.

The wizard requests the default location of the ADM package directory—the directory that stores packages prior to deployment in the target environment. The wizard requests the host name and port number default of the machine with the first Siebel Management Agent you want to register with the Management Server.

The wizard requests the name of the monitored Siebel Server. The wizard asks you to select the type of monitored server. The wizard asks if you want to register a second Siebel Management Agent with this Management Server.

For example, clear the check box if you only have one Siebel Server with a Management Agent, or if you have more than two Siebel Servers with Management Agents. The wizard asks if you want to start Siebel Management Server. NOTE: On Microsoft Windows, if you are using database authentication, in order to select this option, you must have already installed the Siebel Database schema and seed data.

The directory must be a shared network resource that will be available to all the machines where Siebel Management Agent is installed. Enter the name of the Siebel Enterprise, then click Next.

During a basic installation, for example in a development environment, you only require a single instance of each component, but you can chose to install additional servers. For a test or production environment, it is likely that there will be more than one Siebel Enterprise Server and more than one Siebel Application Interface.

This is to provide load balancing and resiliency. This guide describes a minimal configuration, installing one of each component. For more information, see Siebel Applications Administration Guide. Run the setup. Application Install Task. If you are performing a new installation of Siebel, then select New Installation. Otherwise, select Migrate Installation. This guide focuses on new installations.

Installation Directory. You can install all Siebel components under a single parent directory. The installer adds the ses folder automatically as a subfolder under Siebel. When these components are selected, the installer issues a warning message indicating that you cannot install these components together in an end-user environment.

You are installing for a development instance, therefore you can ignore this warning. At a minimum, it is recommended that you select English ENU , even if it is not your intended primary language. Client Authentication Parameters.

Keystore Name. Truststore Name. The password you used when you created your keystores. Gateway TLS Port. This can be any available port, except in a migration installation from an earlier release of Siebel CRM, in which case, it must match the port for the previous Gateway installation.

For simplicity, we will continue the numbering sequence and use for this port. To facilitate re-installation, or additional automated installation, you are prompted to save your responses when you have completed each installation wizard.

However, although it may be installed on the same physical server as these components, it must be installed separately and into a different directory structure from the components installed previously.

In many cases, the options for installation will be the same as those used when installing the Gateway, Siebel Servers, and Database Configuration Utilities. You must use the following installation prompts and recommended responses for Siebel Application Interface, described as follows:.

This must be different from the previous directory used for the Siebel Enterprise Server. Only install Siebel Application Interface. You must install the same set of languages selected during the previous installation. Other than disk space, there is no negative impact to installing additional languages.

Username and Password. The credentials that you specify will be used for accessing the Siebel Management Console initially, which is the user interface that we will use to configure the Gateway, Enterprise, Siebel Servers, and other components. After the initial setup, that is, once you have configured the Gateway Security Profile, you will use the username and password for the configured authentication authority.

Any values are acceptable; for simplicity use: sadmin. These indicate the SSL certificate key stores that we created earlier which will be copied into the installation location for the Siebel Application Interface:. The location of the keystore we created previously. The location of the trust keystore for our certificates.

Whatever password you used when you created your keystores. Before proceeding to the configuration steps below, it is very important that you install the latest Monthly Update. While it is possible to install Updates later, it is possible that an Update could contain bug fixes, repository data, or seed data that would not otherwise be included in your Siebel database. Only the most recent Monthly Update is required for installation, as they are cumulative.

For example, if the To install the Monthly Update, run the installers on the same machines on which you previously ran the base Innovation Pack installers.

You are prompted to create a gateway — for the purposes of this test, you can ignore this message as we are just verifying the installation. Although the Siebel Enterprise Server and Siebel Application Interface components will start automatically after installation, they do not run automatically after a restart of the server. Before proceeding further, it is recommended that these be configured to start automatically. The specific method for doing this will vary by operating system.

The script to startup each component is named startup. After configuring the scripts to run automatically, restart the machine s before continuing to validate that automatic startup process is working, and then proceed to the configuration of your Siebel Database. Before you create the Siebel database, you must ensure that you have the appropriate client connectivity software. When installing the software, select the Administrator option.

Do not select the Instant Client or Runtime options. This prevents errors during the client installation process. Ensure that you run the installer as a local administrator. Microsoft SQL Server. Before we can start installing the Siebel Database, the database administrator must perform some preliminary steps. Create a tablespace in which the Siebel database objects will live. Create a database. The recommended name is siebeldb. A database administrator, who may or may not be a direct member of the Siebel development team, performs these steps.

After preparing the database, run the grantusr. There are brief instructions at the top of each script explaining how to run the script. It will prompt you for information about the preparatory work done in the previous step, for example. When the script completes, you will have an empty shell of a Siebel database with all the required users.

Note that the execution of the script is typically done by a database administrator who may or may not be a direct member of the Siebel development team.

This allows the Siebel team to have everything they need to populate the Siebel CRM Database without the need for specialized database administrator skills. The Siebel team should provide the desired passwords for the database users that the script will create. These include:. The Siebel Administrator user will be used for administering the Siebel CRM application throughout the implementation. The anonymous Guest Customer user.

This user's credentials are used automatically by customer-facing applications before a user has actually logged in, providing access to the login page itself. This allows access to non-sensitive areas of the product, such as Branch Locators, without the need for every visitor to have a login. The anonymous Employee user. This user's credentials are used automatically by employee-facing applications before a user has actually logged in. This is a generic user used by the authentication system.

The configuration wizard prompts you for information on the location of the database, database names, tableowners, tablespaces, and so on, depending on your database platform.

The following are important points to consider during database installation:. This is because you already executed the grantusr. If you do not update this selection, the installation will not continue. Ensure that the Database Encoding value is Unicode. If you are installing one and only one language, you may pick it here. However, if there is any possibility that you will ever be installing multiple languages, it is recommended that you select English as the base language.

This will default all log files and other settings to English, making it easier to debug when working with Oracle Technical Support. You will be able to install additional languages later. The Configuration Wizard displays all the information you entered, and allows you to apply the changes. Once you confirm these changes, the Siebel Upgrade Wizard displays the steps necessary to install the database.

Click OK to start the Siebel database installation. When the installation is complete, review the log files before continuing. For more information, see the installation guide for your selected database. Host Name. This is the host name where the SES components are installed and where you intend to run the Gateway.

For example: myserver. Security Profile. This sets up the security mechanism used to authenticate connections to SMC. For the Gateway, you can name it, for example, Gateway Security Profile.

For a development instance, you typically use database authentication, so you must specify the database type, for example, Oracle or Microsoft SQL Server. You also must specify the connection information, such as the location of database server, port for TNS Listener, and so on.

These are the same credentials as those used when executing the grantusr. This password may be different than the one used during the installation of SAI. If the test is successful, then SMC logs out, and prompts for login credentials. The configuration wizard prompts you for service user credentials. When you complete these steps, the Siebel Gateway service will be created, and the Siebel Deployment Hierarchy page opens.

The Siebel Enterprise maintains environment-wide settings that are shared by all components, such as the location of the Siebel File System, the database, and so on. Before continuing, it is important to understand that in the Siebel Management Console SMC , a profile represents a template that provides the information needed for a given component.

However, a profile is not an actual instance of that component. Using profiles allows us to deploy many instances of the same entity quickly, and repeatedly. You deploy the Enterprise only once, whereas a Siebel Server or Siebel Application Interface profile can be used many times.

A profile is a template for a component that can be deployed many times. To distinguish a profile from an instance of a component, it is recommended that profile name always includes the word: profile. For example, the Enterprise profile could be named EnterpriseProfile. Primary Siebel File System. The Siebel File System will be used to store documents associated with Siebel CRM data, such as spreadsheets, word processing documents, presentations, images, and so on.

This must be a network location that allows read-write access to all the servers on which Siebel Servers are eventually deployed. While the Enterprise creation requires only a single Siebel File System, it is possible to create multiple file systems to improve load-balancing and performance.

The username and password for the Siebel Gateway. Security Encryption Level. If this option is selected, it will be necessary to provide information about the Certificate Authority and other information needed to encrypt those conversations. A Siebel Enterprise must include at least one Siebel Server, but in most cases, particularly for non-development instances, there is more than one Siebel Server.

Performance and Load Balancing. Siebel CRM is very scalable horizontally. Additional Siebel Servers allow more users to connect to the system, allow the execution of more background jobs, and so on.

In addition to providing the business logic layer for active users, Siebel Servers run background jobs, such as large data import jobs or integration with other systems.

To avoid these jobs interfering with the user experience, it is common to deploy more than one Siebel Server specifically for this reason. Operating System Dependence. However, in some instances Microsoft Windows is specifically required. It is not uncommon for a customer to run most of their Siebel Servers on a UNIX platform, and to use a few Microsoft Windows servers to support these specific use cases.

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:. Supports end-user User Interface sessions. Supports background workflow processes. Supports Enterprise Integration Manager processes for bulk data loads.

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.

Each Component Group that includes the application that will be used. 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. After successfully creating the Siebel Server profile, deploy it by doing the following:. Host and Port. If you are planning to deploy immediately, select Deploy.