Sunday, 02 December 2021
Introduction
In the latest version of Siebel they have eliminated the categories to which we were accustomed of SEA and SIA, that is, horizontal and vertical solutions. From now on there will only be the SIA version, adapted according to the licenses and components enabled in each client.
Installation in Unix or Windows environments is similar, changing only the way the administrator interacts with the operating system.
Although it may seem that an installation on Windows is easier, you can see that if you have a minimum of basic knowledge to handle in unix environments, it is ultimately easier to install in the latter.
The basic architecture of a Siebel environment can be drawn like this:
Although the official Siebel guide details all the aspects to take into account during an installation, there are details that do not appear and that are essential to bring it to fruition.
The Siebel server installation process requires the execution of multiple tasks that are summarized below:
- Implementation planning. Where the dimensioning of machines, components to be used, clusters, etc. is planned.
- Determine the load-balancing strategy.
- Creation of the DB instance. You can create the DB instance at any time before running the Siebel “Database Configuration Wizard” utility. Most database tasks do not apply if you already have a Siebel database installed, such as in an upgrade environment.
- Obtaining Siebel software and creating a Siebel installation image on the network (available on https://edelivery.oracle.com)
- Installation of required third-party products.
- Creation of the Siebel directories and the Siebel File System.
- Creation of the necessary Siebel accounts.
- Installation and configuration of Siebel Enterprise Server components.
- Gateway
- Siebel Server
- Database configuration utilities
- Siebel Configuration Wizard to Configure Gateway, Siebel Enterprise, and Siebel Web Server Extension (SWSE) Logical Profile
- Running the Database Configuration Wizard on the Siebel server where the Database Configuration Utilities is installed. The “Install Siebel Database” task runs, which creates the RDBMS schema and adds the Siebel seed and repository data
- File System Preparation
- Siebel Server Configuration
- Post-installation tasks
- Installation of the Web Server, and installation and configuration of the SWSE (logical profile application)
- Installation of Siebel Mobile Web Clients (optional) or Developers Web Clients.
- Installing Siebel Tools for developers.
- Installing Siebel add-on modules (optional)
- Installation Verification Tool (EVT-Environment Verification Tool) (optional)
This image summarizes the different steps of the installation:
In a large deployment, it is generally required that there are different Siebel servers installed on different machines. These servers can be configured so that each contains a particular set of applications, or they can be similarly configured for a participation in a load balancing.
Hardware requirements
The following are Oracle’s recommended hardware requirements for the various components of Siebel Business Applications:
Software requirements
- Java Virtual Machine
- 32-bit Oracle client. This is an important point that is not described in the official bookshelf. If the Oracle client is not 32-bit, even though the server is 64-bit, the necessary odbc (with the Siebel Oracle 90 driver) will not be created correctly for the correct connection of the Siebel server to the database.
- IIS 6 or IIS7 Web server with required version 6 support.
The database must meet a series of characteristics to function correctly in the Siebel environment. Here are some of the most common:
- CHARACTER SET: AL32UTF8
- CURSOR_SHARING: EXACT
- DB_FILE_MULTIBLOCK_READ_COUNT: 32. If NAS storage is being used, make it 8 to reduce network traffic issues.
- MEMORY_TARGET. One recommendation is to put the value of physical memory minus 1 GB
- NLS_DATE_FORMAT. Needed. Default DD-MON-YY
- OPEN_CURSORS. Minimum 1000 and maximum 2000. It should be adjusted according to the observation of the use of the database.
- OPTIMIZER_FEATURES_ENABLE. Enables optimization features based on an Oracle version. Configure this parameter according to the release of the Oracle database.
- OPTIMIZER_INDEX_COST_ADJ: 1
- OPTIMIZER_MODE: ALL_ROWS
- NLS_SORT=binary_sort_mode
Verify that the tables spaces DATA, INDEXES, TEMP, exist and that the different tablespaces are correctly configured:
- Data: 5 GB
- Indexes: 5 GB
- Temp: 2 GB (temp01)
- Undo: 1 GB (undotbs01)
- System: 2 GB
- Sysaux: 1 GB
It is also recommended to have run before starting, the grant_usr.sql in the database, with the SYS user, who creates the users and roles necessary for the installation.
Steps to follow during the installation of the Siebel server:
- Creating the installation image
- Installing the Gateway Name Server
- Installing Siebel Server (not configured)
- Database Configuration Utilities
- EAI Connector
Then run the configuration in the following order:
- Configure “a new Gateway Name Server”
- Set up “a new Enterprise on a Gateway Name Server”
- Install the SIEBEL database
- Configure the file system.
- Configure the Siebel Server
- Run “Post-Installation” tasks
- Installing and configuring the SWSE (Siebel Web Server Web Extension)
- Install the SWSE
- Configure the logical profile for the SWSE on the Gateway Name Server
- Apply the logical profile on the web server
- Installing mobile clients and developers
- Installing Siebel Tools
- Verifying the installation
Once the server is installed, the clients will be installed on each of the machines of the users who will enter Siebel remotely and also the developers.
- Siebel dedicated Web Client
- Tools
A very important last step and without which the installation will not be finalized, is the introduction of the licenses acquired from Oracle. At this point it is still impossible to enter the system, so what is usually done is to enter the licenses through a dedicated client.
Siebel licenses can be found at http://www.oracle.com/us/support/licensecodes/siebel/index.html
Finally, local databases for developers must be extracted, which we will explain in another article.
