Siebel client installation guide

This option is recommended for experienced administrators only. If you want to create custom reports you must perform a custom setup and check the report source code component. Select a destination directory and click Next. The Choose Languages screen appears. Select the language you want to install and click Next. The Server Database screen appears.

Select the database client and server, and click Next. The File System Server Information screen appears. Type the Siebel File System directory path. The Remote Server Information screen appears. Type the Siebel Remote Server host name network name or the machine name to which this client will connect.

The Database Information screen appears. Specify the database identification in the worksheet in Deployment Planning Worksheet. Type the database alias for your Siebel Database, as recorded in the worksheet.

Table Owner. Type the name of the database account that owns the Siebel tables, as recorded in the worksheet. Oracle Database Alias. Process of Installing the Siebel Web Client. Process of Installing Siebel Tools. Installing and Using the Siebel Sample Database. Requirements for Installing Siebel Web Clients.

Requirements for Installing Siebel Tools. A status bar in the Setup Status dialog box indicates the progress of the installation. The Event Log dialog box appears after the installer starts copying files. It describes the steps the installer completes during your Siebel Tools installation. A message appears, stating that language files are being installed. The installer completes the installation and displays the Event Log screen. Then navigate to the directory where the installer is located.

Double-click install. The Choose Setup Language screen appears. Select the language in which you would like to run the installer. If you have an existing Siebel Tools installation, you can choose to add Language Packs to this installation.

If you do not have an existing installation, go to the next step. If you are installing a new instance of the Siebel Tools client, click Next. If you are adding languages to an existing Siebel Tools installation: Select the check box next to the line identifying the existing installation to which you are adding languages, then click Next.

Select the check box next to each language you are installing, then click Next. Proceed to Step 7. The Welcome screen appears. Click Next to proceed. 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. Siebel Server Name. It is recommended that you use the name of the physical host. For example, if your host is myserver.

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. 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.

Launches Siebel CRM processes to host these components. This includes user interface channels, such as employees, customers, and partners using browsers to interact with the application, as well as integration with other applications through REST or Web service calls. Normally a development instance requires a single SAI, but as with the Siebel Server, the Application Interface can be enabled on multiple servers to provide load balancing and high availability.

The key parameters of the SAI are those that are affect client interactivity, such as session timeouts. Creating or more SAI profiles. For many environments, it is likely that you only need one a single profile, even if you will have Application Interfaces running on multiple machines. You might consider creating multiple profiles for one of the following reasons:.

Differing authentication. For example, using a different authentication authority for your internal users from that which you will use for your Internet users. For example, to place Application Interfaces supporting customer-facing applications on one set of servers and employee-facing applications on another. It is recommended that the profile name contains the word: profile. For example, SiebelAppIntProfile.

Basic Information Tab: Enter the following information. HTTP 1. Configure Fully Qualified Domain Name. If you have a single machine hosting an Application Interface, or are using a single entry point, for example a load balancer, set this parameter to TRUE. You must also specify the fully-qualified domain name, for example, myserver. Authentication Information.

Enter the relevant information for your environment. You can accept the default values. However, if you are debugging a problem, you can enter different values. Applications Tab: Define the entry points that users use for connecting to Siebel CRM through the browser and that other applications use for integration.

Application Name. This is the entry point that the user uses to navigate to Siebel CRM. Object Manager. Select the object manager that maps to the Siebel CRM application, as defined in the runtime repository that will be mounted at this entry point. Select the language that you want to expose. To expose a language, you need to have selected this language during the installation of both the Siebel Enterprise Server SES and SAI components, and also you need to have imported the language using the Database Configuration Wizard.

For many environments, this field does not require configuration. Other Information. Accept the default parameters, unless you encounter specific instructions documented in Siebel Bookshelf to support your business requirements.

Application Interface Node. Siebel CRM requires you to activate valid license keys in the database. Without valid license keys, any attempt to connect causes the following browser error: The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.

Siebel Server Location. The root of the siebsrvr folder. The database credentials specified when the grantusr. DB Platform. Log folder. This can be any valid path.

In Siebel Innovation Pack , you perform most configuration changes, such as adding custom fields or validation rules, using Siebel Web Tools. However, there are some types of configuration that require the Siebel Tools client, such as development of Workflow processes or Task-Based UI, as well as certain functions associated with upgrades, such as reviewing conflicts, that are identified by the Incremental Repository Merge IRM process.

For this reason, you need to install Siebel Tools on all machines that you use for these purposes for all Siebel CRM configuration team members. Siebel Tools must have database connectivity software. Before proceeding, install the required software for your database platform on each machine where you install Siebel Tools. To install Siebel Tools, first install the base Innovation Pack release, for example Monthly Updates are always cumulative.

If there is more than one patch set available, you only need to install the latest version. During the installation, all the information that Siebel Tools requires is requested.

The majority of this information was specified during previous steps. For example, the server where the Gateway Server is deployed, the name of the Enterprise, and so on. You will be required to provide the following new information:.