Blog

Saturday, 05 April 2020

 Juan Antonio Ruiz

 Architecture

 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 following drawing shows the structure of the various servers for a standard Siebel installation:

Additional versions are typically provided by Oracle to be installed over the base version. These releases are known as “Maintenance Releases” and sometimes as “patch releases”.

If you add languages to your Siebel installation from an already installed application, you would have to reinstall all previous versions by adding the same languages.

Referencia: Bookshelf de Siebel: Siebel Installation Guide for WINDOWS

The Siebel server installation process requires the execution of multiple tasks that are summarized below:

• Implementation planning. This task is executed in the sizing document, where the sizing of machines, components to be used, clusters, etc. is planned.
• Determine the load-balancing strategy. Also described in the sizing paper.
• 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.
• Installation of required third-party products. See sizing document.
• 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:

This post details the installation of a small deployment of Siebel.

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.

JDK:

Before starting any Siebel Server installation, it must be verified that each machine has the latest required version of the Java environment.

After the installation is complete, you must add the following environment variables:

JAVA_HOME=C:\Program Files\Java\jre6

PATH: add %JAVA_HOME%

Oracle Client:

In all machines except the Database Server (where we have installed the database that we are going to use with the Siebel Server we have to install the Oracle Database Client 11g.

• Install Oracle Database Client 11g (Standard mode) a 32 bit software
• Copy the TNSNAMES file. ORA from the database server in the folder:

C:\oracle\product\11.2.0\client_1\network\admin (where we installed the client)

• Check ORACLE_HOME and ORACLE_SID environment variables

Verify that the database connection is working after you complete the previous steps.

THE ORACLE CLIENT HAS TO BE THE 32-BIT ONE IF NOT, THE SIEBEL ORACLE 90 DRIVER OR THE CREATION OF THE ODBC DOES NOT WORK (THIS DOES NOT COME IN THE OFFICIAL GUIDE).

• IIS Metabase and IIS6 Configuration Compatibility
• IIS 6 WMI Compatibility
• IIS 6 Management Console
• ISAPI Extensions
• We recommend that the siebel user be in the Administrators group to facilitate the tasks of configuring environments.

Database Preparation:

Run these steps before proceeding with the installation, and above all, with the Siebel configuration

• Data: 5 GB
• Indexes: 5 GB
• Temp: 2 GB (temp01)
• Undo: 1 GB (undotbs01)
• System: 2 GB
• Sysaux: 1 GB

Values in Gigabytes are the minimum initial sizes recommended for proper operation of Siebel Server 8.2.2.

Once the tablespaces are created:

create tablespace DATA datafile ‘/oradata/SIEBP/datafile/data.dbf’

size 5210M

autoextend on next 32M maxsize 10420M

extent management local autoallocate segment space management auto;

create tablespace INDEX datafile ‘/oradata/SIEBP/datafile/index.dbf’

size 5210M

autoextend on next 32M maxsize 10420M

extent management local autoallocate segment space management auto;

create undo tablespace undotbs01

datafile ‘/oradata/SIEBP/datafile/undotbs01.dbf’

size 1024M;

create temporary tablespace temp01

tempfile ‘/oradata/SIEBP/datafile/temp01.dbf’

size 2048m

autoextend on

next 32m maxsize 4096m

extent management local;

Launch grant_user.sql from a sqlplus to create the necessary users for Siebel and grant them the necessary privileges (the requested variables must be replaced by the desired passwords).

Once the script is executed, check the access to the database with the different users to confirm that it has been successful.

Also verify that users have privileges on index and data tablespaces:

ALTER USER SIEBEL quota unlimited on tablespace_name;

alter user SIEBEL quota unlimited on DATA;

alter user SIEBEL quota unlimited on INDEXES;

alter user SADMIN quota unlimited on DATA;

alter user SADMIN quota unlimited on INDEXES;

The script performs the following actions:

• Creates the SSE_ROLE role and gives CREATE SESSION privileges to this role.
• Creates the owner of the siebel schema (SIEBEL) and gives it privileges.
• It creates the user SADMIN and LDAPUSER and gives them SSE_ROLE privileges.
• Create the default tablespaces if they do not exist.
• Ask for passwords interactively for each user.

Directory Structure

Before installing Siebel Business Applications, you must create directories with the necessary permissions to successfully run the installation. These directories are detailed below:

• C:\siebel\8.2.2.0.0\ses
• gtwysrvr
• siebsrvr
• dbsrvr
• SweApp
• FS (which is a shared directory for the file system)
• C:\siebel\8.2.2.0.0\Client
• C:\siebel\8.2.2.0.0\Tools
• C:\Siebel_Install_Image
• ZIP_8.2.2.0: All downloaded software is copied here
• JAR_8.2.2.0 – All compressed .jar are extracted in ZIP_8.2.2.0

Siebel installation:

Siebel Image Creation

All versions of Siebel Business Applications released by Oracle can be found on Oracle’s Edelivery website. All files are in ZIP format, so it will be necessary to use an unpacking tool to extract the files to the JAR format, which is used as the basis for the creation of the Image.

To create Siebel Install Image it is necessary apart from the SBA (Siebel Business Applications) package to have Siebel imaging software, since any installation of any Siebel product must be installed from a created image.

Both the Siebel imaging software files and the Siebel installation software must be in the same folder (ZIP_8.2.2.0) for the image creation to be successful.

Once the necessary files have been downloaded and extracted (in JAR_8.2.2.0), the following command must be launched while inside the folder containing all the files:

• cd c:\Siebel_Install_Image\JAR_8.2.2.0

SNIC.bat

The wizard that guides us to create our image opens.

Installing Siebel Business Applications

This section details how to install the Gateway Name Server and Enterprise Name Server.

Siebel Enterprise Server is a logical Siebel Server that supports a group of users accessing a common database. Siebel Enterprise Server can be configured, managed and monitored as a single logical group, allowing the Siebel administrator to start, stop, monitor or adjust parameters of the Siebel servers it contains.

You can set parameters at the Siebel Enterprise Server level, so these parameters apply to all Siebel servers and components contained in Siebel Enterprise Server. Other parameters can be set at the level of each Siebel server.

Parameters set at the Siebel Server level always prevail over parameters set at the Siebel Enterprise Server level.

Siebel Gateway Name Server coordinates Siebel Enterprise Server and the various Siebel Servers contained therein, while providing support for the persistence of Siebel Enterprise Server configuration information, including:

• Definitions and assignments of components and component groups.
• Operational parameters.
• Connectivity Information.

Siebel Gateway Name Server also acts as a dynamic registry of the Siebel server and the information and connectivity of its various components. Each time a Siebel server is booted, it informs the Siebel Gateway Name Server of its availability to store connectivity information – such as network addresses – in the Siebel Gateway non-persistent data store (volatile information).

The various components of Siebel Enterprise Server will always query Siebel Gateway Name Server for information about the status of Siebel servers and connectivity information.

Gateway Name Server and Enterprise Name Server have to be installed on the same machine (server) for the proper functioning of the Siebel Server.

Important: The installation of

-Gateway

– Siebel Server

– Database Configuration Utilities

– EAI connector

It should be done in 4 separate steps.

Install the Gateway

To begin the installation of Siebel Gateway Name Server and Enterprise Name Server you must have a directory with the image of the Siebel installation:

C:\Siebel_Install_Image\8.2.2.0\Windows\Server\Siebel_Enterprise_Server\Disk1\install

It is important to consider the following guidelines before installing Siebel Gateway Name server:

• The name of the hostname where Siebel Gateway Name Server will be installed must not contain hyphens. It is recommended to use underscores if word separation is required. For example, host_sba81 would be a valid name while host-sba81 would not.
• The name of the hostname where the Siebel Gateway Name Server will be installed must not exceed 15 characters in length.
• It is recommended that you do not define the hostname where Siebel Gateway Name Server will be installed including domain information.
• Siebel Gateway Name Server defaults to port 2320. You can choose any available port that is not in use on the machine where you are going to perform the installation. However, port 2321 is not recommended as it is used for the SCBroker (Siebel Connection Broker).
• There are restrictions for the name of the Enterprise and Siebel Servers:
  • No more than 12 characters in length
  • Name cannot be “Server” or “Enterprise”
  • Only alphabetic, numeral or underscore characters. Don’t use hyphens
  • Must start with a letter
  • Names must be unique across each Enterprise.

Now we launch the installation by running the setup.bat (“run as Administrator”) and the wizard will open that will guide us through the installation of the Gateway server.

Install Siebel Server (not configured)

To start the installation of Siebel Server we have to have a directory with the image of the Siebel installation.

It is important to consider the following guidelines before installing Siebel Server:

• Siebel Server must be installed only once on each machine.
• when you are installing the first siebel server it is important to stop configuring the server until you have installed the database utilities configuration to have the siebel database

Database Configuration Utilities

Once the Siebel Server is installed, you must have installed Database Configuration Utilities before you can configure it.

Database Configuration Utilities is responsible for installing the Siebel database schema and importing the necessary Siebel data.

It is important to consider the following guidelines before you install Database Configuration Utilities:

• The Oracle database software must have been installed (not necessarily on the same machine) and the connection to it verified.
• Database Configuration Utilities must be installed on the same machine where Siebel Gateway Name Server and Siebel Server are installed.

The installation is done following the same steps as in the previous point.

EAI Connector

Finally, the EAI connector is installed following the same steps as in the previous point.

ENTERPRISE CONFIGURATION

To boot the configuration of each of the Siebel components, there are two ways to do it:

1. Go to “All Programs” / Siebel Enterprise Server Configuration / Config_Type, where Config_Type is one of the following values:
   1. Siebel Enterprise Configuration
   1. Siebel Server Configuration
   1. Database Server Configuration
   1. Siebel Web Server Extension Configuration
   1. Management Agent Configuration
2. From the command line:
   1. Windows/Run/cmd
   1. Siebel Root Directory
   1. Config subdirectory
   1. Run the config.bat (“run as administrator”) with the –mode mode_name option, where mode_name is one of the following, depending on what you want to configure:
      1. enterprise
      1. siebsrvr
      1. dbsrvr
      1. SWSE
      1. mgmtagent
      1. mgmtsrvr

The configuration will be executed 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 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

Gateway Configuration

The following are the screens that appear when you configure Siebel Gateway Name Server.

We run it from the command line because from Programs the “Run As Administrator” does not work and it is essential.

• Abrimos un cmd como “Run As Administrator”
• Let’s go to c:\siebel\8.2.2.0\ses\config
• We run config.bat –mode Enterprise
  
  
• The parameters to be used are:
• Port: default 2320
• Language: default ENU
• Autostart: NO (will automatically boot with Windows)
• Location of the unattended configuration file.

Enterprise Configuration

Below are the screens that appear when you set up your Enterprise. The steps are as in the previous point:

• config.bat –mode Enterprise
• New configuration
• In the next step, we will now choose “configure a new Enterprise instance”

THE GATEWAY SERVICE MUST BE STARTED (GTWYNS)In

this step the corresponding ODBC must have been automatically created SBA_82_DSN pointing to the Siebel database. For this it is essential that the oracle client is 32-bit.

Installation of the Siebel database

The grantusr must have been executed before.sql

• Table Owner
• Table Owner Password

Configuration starts with –mode dbsrvr option

ODBC is SBA_82_DSN by default (Enterprise_name + _DSN). Must have been created in the Enterprise configuration

In this step you will install both the Siebel database (Siebel schema) and the seed data (lists of values, repository objects, etc.)

It can also be done separately by running after:

SIEBEL_ROOT\siebsrvr\bin\siebupg.exe /m master_install.ucf

File System Preparation

Once the database installation is complete, the file system must be filled. To do this, simply copy the files from \dbsrvr\files to the folder where the file system is, sudirectory att,

The file system must be a shared directory in the Windows domain

Configuring the Siebel Server

To start the configuration of Siebel Server we must have finished the installation of it.

It is important to consider the following guidelines before configuring Siebel Server:

• You must verify that the gateway service is running.
• The Siebel Server name cannot exceed 12 characters in length
• The Siebel Server name cannot be ‘server’ or ‘enterprise’ (server1 or enterprise1 are accepted).
• The Siebel Server name must begin with a letter, and can only contain letters, numbers, and underscore.
• The Siebel Server name must be unique within Siebel Enterprise.

As an optional step it is also necessary to check if the database is running and the connection to the same database works with all users especially the user SADMIN.

Configuration starts with –mode siebsrvr option

The component groups to enable are chosen

Installing the Siebel Web Server Extension

To begin the installation of Siebel Web Server Extension you must have a directory with the image of the Siebel installation:

\Server\Siebel_Web_Server_Extension\Disk1\install

Run the “setup.bat” as “Run As Administrator”.

Creating and Applying the Siebel Web Server Extension Logical Profile

Once the Siebel Web Server Extension is installed, we will apply the logical profile:

To do this, we will first open a new configuration of the enterprise with the “-mode enterprise” mode to create the new logical profile:

• Create new settings
• Set up a new logical profile
  • The next step is to apply the logical profile we just created:
• First we copy the contents of the \gtwysrvr\admin\webserver folder to the \sweapp\admin folder
• We start a new configuration, but this time from: From \sweapp\config
• With “-mode swse” mode
• Apply a SWSE logical profile:
  • Load Balancer: Single Server
  • Host del Siebel Server
  • Broker Port: 2321
  • Logical profile location:  \sweapp\ADMIN
  • Answer file: \RESPONSE_FILE_WEBSERVER_APPLY.TXT

IIS7 Configuration

At the time of applying the Siebel logical profile, the virtual directories of the Siebel applications are automatically created

There may be problems with the swiss bookstore.dll

IIS error message:

%1 is not a valid Win32 Application

I solve the problem executing a script that allow IIS to execute a 32 bit dll

The request is mapped to a managed handler but the .NET Extensibility Feature is not installed

To fix this, the parameter “Enable 32-bit Applications” in the IIS7 Default Application Tool is set to TRUE

Last steps:

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