Category Archives: Siebel

Installing Siebel 8.2.2 on Linux x86-64 Part-3

In this part we will Siebel database configuration tool to populate Siebel  database but fire we need to some preparation tasks as explained in following section.

4. Preparing to run the Siebel Database Configuration Tool.
 In This section we will prepare our system for running the Siebel database configuration tool.
Our aim is to prepare our database to be populated with  Siebel data.We will run grantusr.sql in dbsrvr directory.

  • Update grantusr.sql in dbsrvr ,to  add GUESTERM  and GUESTCST
  • It is recomended  take a backup of grantuser.sql
  • Add the following line to grantusr.sql
    Note:- It is very important to keep in mind that  grantuser.sql does not create GUESTERM  and GUESTCST user we need to manually add lines to grantuser.sql  to create these two users. :-)
  • Run the updated grantusr.sql
  • Enter username , password for Siebel Database Object
    {In earlier versions of grantuser.sql Siebel user was by default table owner but in this new version of grantusr.sql we can manually specify Table owner user} .
  • Select Table space created earlier when asked for default table space.
  • Also Enter Passwords for SADMIN and LDAPUSER users {It is highly recommended not to change SADMIN user}.
  • TO test we can connect to database as SADMIN user
    sqlplus SADMIN@OBIDB as sysdba
  • Next step is to Populate the Siebel database but first create environment file from scripts located inside siebsrv directory
    # cd /u01/siebel/8.2.2.0.0/ses/siebsrvr/install_script/install
  • Run CreateDbSrvrEnvScript as
    # ./CreateDbSrvrEnvScript /u01/siebel/8.2.2.0.0/ses ENU Oracle
    Here first argument is SIEBEL Base and  ENU is for language English , Oracle For dbserver database type.
  • It will create
    dbenv.csh and dbenv.sh files under siebsrvr directory.
  • Source the newly created file.
  • Modify LD_LIBRARY_PATH and add 32-bit database client libraries to this path as :-
  • Note:- It is very important to add 32-bit database client libraries.
  • Above step is a very important step because , .odbc.ini file uses SEor825.so file and all of its supported libraries are not present until we add database client libraries to LD_LIBRARY_PATH.{We can also manually edit dbenv.sh file to include database client libraries to LD_LIBRARY_PATH }
  • Now we can test database connection using a tool “ odbcsql “ present in the siebsrvr/bin directory . We can use this tool as :-
    [dbuser@vm50 bin]$ ./odbcsql /source Veebrij_8_DSN /user SADMIN /password SADMINPASSWORD
  • If all went well you should be able to connect successfully.
  • and as we can see we were able to connect successfully.
  • Now we are ready to run Siebel database configuration tool and populate the Siebel database. (Explained in next step)

5 . Running Siebel Database tool to populate the Siebel Database.
In this section we will do the following :-

  1. Run database Configuration tool
  2. Populate and Test Siebel database.

To run database configuration tool:-

  • Navigate to config sub-directory
  • Run the configuration tool in dbsrvr mode as
    # ./config.sh -mode dbsrvr
  • Installer will automatically detect Siebel Server and Gateway name Server directory from the Environment file that we sourced earlier.
  • Select Oracle here :-
  • Select Install Database option.
  • Select Installation operation
  • As we have already run grantusr.sql script earlier , we can click next.
  • Select encoding type :-
  • Enter the ODBC data source that we tested earlier.
  • Enter database username and password created earlier (when we ran grantusr.sql).
  • If there is any error after above step, we need to retest database connectivity and environment variables settings.
  • Enter the table space owner name and password.
  • Now it will ask for Index table space name {Which we have created earlier in Part-1.}
  • Note: – In Siebel 8.2.2.0 grantusr.sql script assumes there is only one table and does not grant permission on Index Table Space.
    So we will manually need to grant permissions as:-
    SQL>alter user SADMIN quota unlimited on SIEBELINDEXTS;
    SQL>alter user SIEBEL quota unlimited on SIEBELINDEXTS;
  • Enter the tablespace name that we created earlier(Part-1).
  • Enter the Product license key. Siebel  License Key can be obtained from
    http://www.oracle.com/us/support/licensecodes/siebel/index.html
  • Follow the GUI for next steps.
  • In linux Configuration tool generates a master_<Process>.ucf file in $SIEBEL_ROOT/siebsrvr/bin directory. We now need to use Siebel Server Upgrade Wizard to run that file.
  •  Click next to execute settings.
  • Click exit after you get a success message.

Our Next step is to run Server upgrade Wizard with the master install file that was created by the configuration tool in siebsrvr/bin directory. For this

  • Navigate to siebsrvr bin directory and call Server Upgrade wizard as
    # ./srvrupgwiz /m master_install.ucf
  • It will take a while to complete the process(around 60 minutes.)
    and screen like following will appear.
  • After completion you should get screen like below :-
  • Note that it took 60 minutes to complete the process.
  • Once the import is complete we can test if the tables are populated or not. As :-
  • Also we can check size of the SIEBELTS Table space which has grown up-to 1 GB
    So we are fairly confident that database has been populated.

Installing Siebel 8.2.2 on Linux x86-64 Part-2

3.Installing and Configuring a Siebel Enterprise Server
In this Part we will :-
a. Install Siebel Enterprise Server
b. Configure a Siebel Gateway Name Server
c. Configure a Siebel Enterprise within a Gateway Name Server.
d. Create a Siebel Web Server Extension Logical Profile.

3.1.1 Installing Servers:-
Install the servers in the following sequence:-
Siebel Gateway Name Server
Siebel Server
Database Configuration Utilities (with the first Siebel Server)}

  • Create a destination Directory for Siebel Installation and provide permissons accordingly.
    #mkdir /u01/siebel
    #chown oracle:oinstall /siebel
  • Run “runInstaller” with oneClick option.
    # ./runInstaller -oneclick
  • Specify Oracle Home and Oracle Location
  • Select the product and Language to be installed .
  • We can Skip Security Update .
  • As the installer is checking the system for a 32 bit installation , and we are on a 64 bit platform Installer will through errors while performing System Check. Ignore System Check messages.
    Ref:- OUI-11104 Warning While Installing Siebel Enterprise Server 8.2.2 on OEL 5.5 (Oracle Enterprise Linux) [ID 1476556.1]
  • Click Install on the Summary Screen to proceed with the Installation.
  • We can monitor the Installation Procedure from Installation Screen.
  • And if everything goes alright a success message will appear as :-
  • Press Exit to End Installation.

3.2.2 Configure the Siebel Enterprise :-

  • Now that Siebel Installation is complete , next step will be to configure Siebel Enterprise.
  • We need to configure :–
    a. Siebel Gateway name Server
    b. Siebel Enterprise on/within Siebel Gateway Name Server     computer.
    c. {To Configure the Siebel Web Server Extension}. Create a Siebel Web Server Extension Logical Profile.

1.We will use configuration tool located in Gateway Server’s bin directory.

  •  Change to installation directory
    # cd /u01/siebel/8.2.2.0.0/ses/gtwysrvr
  • source the environment file , cfgenv.sh as
    [dbuser@vm50 gtwysrvr]$ source cfgenv.sh
  • Navigate to the config subdirectory
    Invoke config.sh to configure Siebel Server and so on
    #./config -mode mode_name
    Here mode_name specify the Configuration Wizard to run.
    Here in our case it’s “enterprise” as we are configuring Siebel Enterprise.
    [dbuser@vm50 config]$ ./config.sh -mode enterprise
  • Click on Create New Configuration.
  • First we will be configuring Gateway Name Server.
  • Choose a network TCP/IP port to use with the Gateway Name Server.
    Default Port is 2320
  • If you want to save a response file later usev(Like Silent/Console Install ) you can save it on this screen , otherwise leave it blank.
  • Click next to continue.
  • It should return a success message.
  • Click exit to End Configuration Wizard.

2. Rerun to the configuration Wizard to Configure Siebel Enterprise     within Gateway   Name Server .

  • Enter Gateway Name Server User Name and password.
  • Enter machine name when asked for Gateway Name Server Host Name.
  • Enter the network TCP/IP port that we are using with Gateway Name Server. {Remember we assigned 2320 when we were configuring Name Server}
  • Note:-If our Gateway name server is running then after clicking next everything will be fine , thus we are also testing if our gateway name server is running or not{which we didn’t perform earlier;-) }
  • Enter Siebel Enterprise Name and description.
  • Next step is to provide primary Siebel File System. Installer will not create this automatically SO ?
    Note: – “ We need Create Siebel File System Manually as it will not do so by itself.”
    # [dbuser@vm50 ~]$ cd /u01/siebel/8.2.2.0.0/ses/gtwysrvr
    # mkdir fs {File System Should be accessed to every Siebel Server}
  • Select Oracle as RDBMS Owner and Database Table owner
  • Enter the Oracle SQLNet Connect String:
  • Enter Database Username Password for Siebel Database User account{We will be creating this in next Part}.
  • In the Authentication profile we will be using database authentication .
  • As we are configuring Enterprise for first time we must select propagate Authentication Setting to Gateway Name Server.
  • Click next on summary to deploy our Enterprise .
  • Click exit after success message.

3. Rerun for third Time to configure Web Server extension logical    Profile.

  • Enter Siebel Enterprise Name , Entered Earlier
  • Enter location for Profile .Configuration tool will create this directory automatically.
  • To enable application specific statistics reporting. When disabled, only basic statistics will be collected on the statistics Web page for a Siebel Web Server Extension with the assigned profile.
  • Select the compression type to be used for messages exchanged between Siebel Web Server Extension and Siebel Server.
  • Enter Login Session and Active Session Time Out values(In seconds)
  • Note:-HTTP PORT 80 is reserved in Linux only Root can Access it so we need to change it.
  • We will use default employee login and Customer Login.
  • Employee is :- GUESTERM
    Also Enter Employee Password
  • Similarly enter Default Customer Name and Password.
  • Enter the Security Token and Default statistic page.
  • Select TCPIP as connection Protocol
  • Click next on summary screen to complete configuration
  • You should get a success message .Click exit after Success message.
  • Run Post Installation Tests.
    Source newly created siebenv.sh in gtwysrvr directory.
    Note :- “As we have not configured database till now we will not be able to use gateway Name server”.
    So test for now we can check if any process is listening on 2320
  • also we can check if any sieb process is running or not ?
  • So above two test’s are positive.
    There is also a useful tool in the bin directory (in gateway name server directory)
    list_ns allow us to track currently running gateway servers
    For Example :-

Installing Siebel 8.2.2 on Linux x86-64 Part-1

1. Verifying Siebel Prerequisites and Installing the Database   Client .
The first step will be to check all the Prerequisites required for sieble installation.So we will be .
a.checking the operating system prerequisites for    installing a Siebel Enterprise Server on Linux, including      verifying the operating system, user, and database.
b.download and install the 32-bit Oracle database client, a prerequisite for configuring a Siebel Enterprise that uses an Oracle database.

1.1.1 Configuration details:-

  • 64 bit 11g Database
  • 32 bit Database Client
  • Java Developer Kit (JDK) version 1.6
  • Siebel 8.2.2
  • OEL & Kernel Version
    #cat /etc/*-release ———{EL server 5.4 }
    # uname –a   {To varify kernel Version}
    For Example:-
  • Linux vm50.vTest.localdomain 2.6.32-200.13.1.el5uek #1 SMP Thue Jun 18 02:02:33 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
  •  Oracle Validate Package Installed or Not?
    # rpm -qa | grep oracle-validated

1.1.2 Install Oracle Database 11g as per oracle documentation.

  • Oracle Database 11g 64 bit
  • Oracle Database user and Groups
    # whoami {To determine which one is current user}
    # groups  {To determine all the groups of current user}
  • Varfy oracle Database , ORACLE_HOME and other Environment variables are set , Tnsping to ping database ,
  • # echo $ORACLE_HOME
    # tnsping SIEBLE_DB_NAME

1.1.3 Create Tablespaces for Siebel
We need to create table-space for the Siebel Database that we will be populating later.
We have created two tables , siebelts and siebelindexts {for siebel indexes}.

1.1.4 Install 32 bit Oracle Database Client to support Siebel Application.
 Go to http://www.oracle.com/technetwork/index.html
Select Oracle Database Software for Linux x-86 as we are installing 32 bit Oracle Database Client.

Download  “Oracle Database 11g Release 2 Client (11.2.0.1.0) for Linux x86 ”
Unzip the downloaded File and go to newly created directory
# unzip -o linux_11gR2_Client.zip
# cd client

  • Run “runInstaller” script to install Oracle Database Client 11g.
    “On a side note we need to install oracle ODBC drivers as  Oracle Siebel installation uses Oracle ODBC drivers to connect to the database.”
    # rpm -qa | grep unixODBC  {To check Unix ODBC Drivers are Installed on the computer before Installing the client}
    Result should be like for example :-
  • {Twice because we will have one for 32-bit version and other for 64-bit version}
  •  Now run “runInstaller” select Custom Installation
  • Select language :-
  • Installer detects oracle database already installed on the system and select s/w home automatically. But as we know that database installed is 64 bit and client that we are installing is 32 bit so they are Incompatible.
  • Change the Software location Directory.
  • Components to Select are: –
    Oracle Database Utilities, SQL*Plus and Oracle ODBC Driver.
  • Click finish on the summary screen to install components.
  • Run the root script {But we already have Oracle database installed hence we will not run root script?}
  • Click ok and you should get a success message as
  • Test the 32-bit database client by running the 32-bit version of sql*plus , Verify ORACLE_HOME is set and go to client directory
    # echo $ORACLE_HOME
    # cd $ORACLE_HOME
    #cd ../client
    #cd bin
    Now Run the local Version of the sqlplus and confirm that it connects to the database.
    # sqlplus sys@obidb as sysdba

So we conclude that have installed 32 bit client successfully.

2. Downloading the Siebel Software and Creating an Installation Image.

2.1. Download Siebel Software.

2.2 Creating Installation Image

  • Create a directory Where you want to stage Image ,
    #mkdir Siebel_Install_Image
    #mkdir Siebel_Install_Image/JAR_Files
    #chown -R oracle:oinstall Siebel_Install_Image/JAR_Files
  • Unzip all the files to a directory , Lets say /u01/Siebel_Install_Image/JAR_Files
  • We need to extract following Files{Downloaded from Edelievery} :-
    Third-Party Applications , Base Applications , English Language pack and Image Creator files.
  • go to the Jar Directory ,These jar files will be used by “Siebel Network Image Creator” to create the installation image used to install Siebel Enterprise and Siebel Web Server Extension.
  • snic.sh {Siebel Network Image Creator Script}, used to create installation Images.
  • Set JAVA_HOME Environment Pointing to java installation.
    # export JAVA_HOME=../../jdk1.6.0_29
  • Run Image Creator Script {}.
    # ./snic.sh {Invokes Siebel Image Creator Utility that has simple set of screens}
  • Select create a new image option.
  • Select a directory where you want to copy product install images. As we are following slandered Oracle Procedure we keep it as /u01/Siebel_Install_Image
  • Select Linux as Platform
  • Select the product for image creation.
  • Select Language English.
  • Image creator will now extract all the files which can be screen on the command prompt.
  • Click finish to complete Siebel Installation wizard.
  • We created Two Installers:-
    One for Siebel Enterprise Server.
    Other for Siebel Web Server Extension

 

Installing a Siebel CRM 8.1.1.11 on Windows 7 64 bit

With the beginning of a new year, many of us try to catch up with the latest Siebel developments such as Open UI or simply want an easy-access self-study environment consisting of the Siebel Developer/Mobile Web Client, Sample Database and Siebel Tools. The following post is an updated version of the installation instructions I compiled some time ago.

It will guide you through all necessary steps to download, extract, install and setup Siebel CRM Developer Web Client, Tools and the Sample Database for Siebel 8.1.1.11, including Open UI.

Process for installing a Siebel CRM 8.1.1.11 self-study environment:

  1. Register/log in at Oracle’s Software Delivery Cloud (aka E-Delivery)
  2. Read and understand the license agreement
  3. Use a download manager
  4. Verify hard- and software
  5. Download the installation archives
  6. Extract the installation archives
  7. Run the Network Image Creator
  8. Prepare the browser
  9. Change compatibility settings and privileges for installer executables
  10. Install the Siebel Mobile/Developer Web Client base version (8.1.1.0)
  11. Apply the Siebel Mobile/Developer Web Client patch (8.1.1.11)
  12. Install the Siebel Sample Database
  13. Install Siebel Tools base version (8.1.1.0)
  14. Apply the Siebel Tools patch (8.1.1.11)
  15. Copy the new SRF file
  16. Change permissions on Siebel installation folders
  17. Modify the tools.cfg file and client .cfg files
  18. Manage shortcuts
  19. Get started with the Siebel Sample Database
(Note: Steps 1 and 3 to 7 can be skipped if you’re lucky enough to find the installers on one of your corporate network drives)
Step 1: Register/log in at Oracle’s Software Delivery Cloud (aka E-Delivery)

 

Oracle makes Siebel CRM software available for download on its Software Delivery Cloud. If you want to download software from there, you have to register with your name, company and e-mail address. You will receive a notification after approximately one business day that you can now use the Software Delivery Cloud.
Step 2: Read and understand the license agreement
Oracle provides an unlimited developer license for its software. The license agreement (from the OTN software download page) grants
“a nonexclusive, nontransferable limited license to use the programs only for the purpose of developing, testing, prototyping and demonstrating your application, and not for any other purpose”
Step 3: Use a download manager
Because of the size of the .zip archives you’re going to download onto your hard disk, it is highly recommended to use a download management tool such as Free Download Manager (FDM).
FDM is my tool of choice because of a nice feature called “ZIP Preview” which allows you to preselect the content of the zip file before starting the download.
The ZIP Preview is especially useful to uncheck all the unneeded language packs, so that your final download size is much smaller (and faster).

When you decide to install FDM, you will notice that it creates plug-ins for your browser(s). To initiate the download in FDM, you simply click the link within your browser as usual and the download will be forwarded to FDM.

Step 4: Verify hard- and software
If you have access to My Oracle Support, you can access the system requirements and platform documentation via the Certifications tab as indicated here. For a self-study environment as installed in this article, you are fine if you have a recent laptop or desktop with at least 4 GB of RAM and (of course) Windows 7 64 bit. If you use virtual machines, ensure that you place them on high-speed disks and reserve enough RAM for best performance.

In addition, ensure that you have installed modern versions of your favorite browser, keeping in mind that if you intend to run Siebel in High-Interactivity (aka “ActiveX”) mode, you must have Microsoft Internet Explorer 7 or 8 and not any higher version available. For best performance of Siebel Open UI, you should consider installing Google Chrome or Mozilla Firefox in addition to MS IE.

Personally I prefer virtual machines because of the greater flexibility. Some companies do not allow their employees to install software on corporate laptops, so running a (privately owned) virtual machine is sometimes the only option (sad, but true).
Step 5: Download the installation archives
Now it’s time to log in to Oracle’s Software Delivery Cloud and search for Siebel CRM forMicrosoft Windows (64 bit). As we are going to download and install Siebel Industry Applications (SIA) 8.1.1, we have to click the hyperlink for
Siebel Industry Applications Innovation Pack 2013 Release 8.1.1.11 Media Pack for Microsoft Windows
Then we download the following archives and save them in a single directory. If your download manager allows to control the files to download within an archive, please refer to the list of .jar files below each package. Note that in this article we only cover the English-American (enu) language pack. If you want to download additional language packs, please ensure to include the language-specific files identified by the three-letter language code as part of the name (e.g. deu for German).
Siebel Industry Applications Version 8.1.1.11 Siebel Client (Starter Installation Requirement): V39882-01.zip
SBA_8.1.1.11_Base_Windows_Siebel_Web_Client.jar
SBA_8.1.1.11_enu_Windows_Siebel_Web_Client.jar

Siebel Industry Applications Version 8.1.1.11 Siebel Tools (Starter Installation Requirement): V39881-01.zip
SBA_8.1.1.11_Base_Windows_Siebel_Tools.jar
SBA_8.1.1.11_enu_Windows_Siebel_Tools.jar

Siebel Industry Applications Version 8.1.1.11 Sample Database Files: V39852-01.zip
SBA_8.1.1.11_Base_Windows_Siebel_Sample_Database.jar
SBA_8.1.1.11_enu_Windows_Siebel_Sample_Database.jar

Siebel Industry Applications Version 8.1.1.11 ImageCreator Files (Starter Installation Requirement): V39861-01.zip
all files

Siebel Industry Applications Version 8.1.1.11 Siebel Repository Files: V39883-01.zip
srf.zip (extract this file and keep only the files for the languages you want to install)

Siebel Business Applications Version 8.1.1.0 Siebel Client: V36459-01_1of2.zip
SBA_8.1.1.0_Base_Windows_Siebel_Web_Client.jar
SBA_8.1.1.0_enu_Windows_Siebel_Web_Client.jar

Siebel Business Applications Version 8.1.1.0 Siebel Tools: V36460-01.zip
SBA_8.1.1.0_Base_Windows_Siebel_Tools.jar
SBA_8.1.1.0_enu_Windows_Siebel_Tools.jar

Step 6: Extract the installation archives

Most probably you are using a Microsoft Windows machine for the files, so it is recommended to use 7-Zip to extract the content of the downloaded zip archives into a single folder.
As a result of the extract, we have a folder full of .jar files and the files for the Network Image Creator.

Click to enlarge.

Step 7: Run the Network Image Creator

The Siebel Network Image Creator (snic) is needed to create the final installer directories and files. To launch it, you have to open a Windows command shell (aka DOS box) and navigate to the directory containing the extracted .jar files. Next, set the JAVA_HOME environment variable to the location of the Java runtime environment (JRE) on your machine using a command similar to the following (of course, if you haven’t installed the JRE yet, it is time to do so now):

set JAVA_HOME=C:\Program Files\Java\jre1.7.0_45

Your Java version and install folder might vary.

Next, launc the image creator by issuing the following command:

snic.bat

The wizard will launch and guide you through the network image creation process. Basically the image creator asks for the following:

  1. Whether you want to create a new image or add a language pack (select “create a new image”).
  2. Enter the path where to store the installer images. (enter a suitable path)
  3. The version (8.1.1.0 or 8.1.1.11, see below)
  4. The OS platform (select “Windows”)
  5. The products (select “Siebel Tools”, “Siebel Web Client” and “Siebel Sample Database”)
  6. The languages (select at least “ENU”)

Because the Siebel Developer Web Client and Siebel Tools must be installed with the base installer (8.1.1.0) first and then applying the patch (8.1.1.11), we must invoke the snic twice, once for each version. When the second run has finished, you will find the following directory structure in the location you provided in step 2.


Step 8: Prepare the browser
As indicated above, you should have a version of Microsoft Internet Explorer not higher than 8. The following settings are recommended for running the Siebel High-Interactivity client flawlessly. You might not be able to complete this step because of security restrictions on your laptop or in your corporation. In this case, please contact your IT administrator.
Make IE the default browser

Because the installer for the Siebel Developer Web Client will try to pre-load the ActiveX controls, it launches an HTML page. This will only work as intended when Internet Explorer is the default browser for your system. To set IE as the default browser, open the Windows Control Panel, go to Default Programs, and click Set your default programs.

Next, select Internet Explorer in the list and click Set this program as default.

Note: you can change your default browser to the one you love more than IE once the installation is finished.

Pop-up Blocker settings:
  1. In Internet Explorer, go to Tools – Pop-up Blocker – Pop-up Blocker Settings.
  2. Add http://localhost, http://%5Bshort machine name] and http://%5Bfully qualified machine name] to the allowed sites list (see screenshot below for an example)

Alternatively, set the blocking level to “Low” or disable the Pop-up Blocker entirely (if applicable).

Security settings:
  1. In Internet Explorer, go to Tools – Internet Options – Security.
  2. Select the Trusted Sites icon and click the Sites button.
  3. Add http://localhost, http://%5Bshort machine name] and http://%5Bfully qualified machine name] to the Websites list (see screenshot below for an example)
  4. Set the security level for the Trusted Sites zone to “Low”.
    Alternatively, click the Custom Level… button and set all ActiveX related entries to “Enable” or “Prompt”.
Internet Explorer settings for trusted sites.
Internet Explorer 9 settings
For those on Internet Explorer 9, you should say a big thank you to Richard who postedthese additional steps:

  1. Add http://localhost, http://%5Bshort machine name] and http://%5Bfully qualified machine name] to the list of compatibility mode sites.
  2. Go to Tools – Manage Add-ons and set the Java Add On parameter to “Enabled“.
Note: Even if you manage to run the web client in IE 9, you will face problems with the Siebel Tools applet editor as described by siebelish here. (Note that in IP 2013 this problem should be corrected, but I wasn’t yet able to verify that).
Step 9: Change compatibility settings and privileges for installer executables
Since we are installing on Windows 7 and Siebel 8.1.1.x clients are not officially supported on that OS, we have to switch the compatibility mode for oui.exe, module.exe (for Siebel_Web_Client and Siebel_Tools), install.exe and setup.exe (for the sample Siebel_Sample_Database) back to “Windows XP“. To be on the safe side, also check the “Run this program as an administrator” flag. To do so, right-click on the file in Windows Explorer, go to Properties and in the Compatibility tab, change the settings similar to the screenshot below.
Here is a list of files and their location for which you will have to change the compatibility settings as described above:

..\8.1.1.0\Windows\Client\Siebel_Web_Client\Disk1\install\oui.exe
..\8.1.1.0\Windows\Client\Siebel_Tools\Disk1\install\oui.exe
..\8.1.1.11\Windows\Client\Siebel_Web_Client\Disk1\install\module.exe
..\8.1.1.11\Windows\Client\Siebel_Tools\Disk1\install\module.exe
..\8.1.1.11\Windows\Client\Siebel_Sample_Database\install.exe
..\8.1.1.11\Windows\Client\Siebel_Sample_Database\Setup.exe

Step 10: Install the Siebel Mobile/Developer Web Client base version (8.1.1.0)

The following procedure describes the installation of the Siebel Mobile Web Client for use with the Siebel Sample Database. Important: Don’t use or start any other programs until the installation is finished.
  1. Navigate to the 8.1.1.0\Windows\Client\Siebel_Web_Client\Disk1\install folder of the installation image and double-click the oui.exe file.
  2. Follow the wizard and keep the default settings (except where noted below). Take a note of the installation folder (you need it for the sample database installer).
  3. Select the desired language packs (always include American English).
  4. At the client type selection, select “Mobile Web Client”.
  5. Keep the defaults in the remaining dialogs. You can always change the settings later in the client configuration file (.cfg).
  6. During the installation, Internet Explorer is launched to pre-load the Siebel ActiveX controls. When prompted, allow the execution of any ActiveX content. You will be prompted to close the IE window so that the installer can continue.
Step 11: Apply the Siebel Mobile/Developer Web Client patch (8.1.1.11)
Next, we will apply patch 8.1.1.11 (aka Innovation Pack 2013) right away as follows:
  1. Navigate to the 8.1.1.11\Windows\Client\Siebel_Web_Client\Disk1\install folder of the installation image and double-click the setup.bat file.
  2. Click Next in the Welcome screen.
  3. Ensure that the client home you defined in step 10.2 is selected and click Next.
  4. Click Install.
  5. Wait until the dialog displays a success message and exit the installer.
Step 12: Install the Siebel Sample Database
The installer for the Siebel Sample Database can be found in the Siebel_Sample_Database folder of the installation image. We can follow the procedure below to install the sample database. Again: Don’t use or start any other programs until the installation is finished.
  1. Double-click the install.exe file in the Siebel_Sample_Database folder.
  2. Select a language for the installation dialogs.
  3. Keep the defaults in all dialogs except for those described below.
  4. Select the custom installation type.
  5. Change the installation directory to the client’s installation folder (this is important).
  6. In the language selection, select only “English (American)”. Selecting additional language packs only copies non-english seed data files and does not change the database. You can use these seed data files to produce a sample database specific to a language pack of your choice but you can only import one language.
  7. Keep the defaults in the remaining dialogs and wait for the installation to finish.
Step 13: Install Siebel Tools base version (8.1.1.0)
To install the Siebel Tools base version (8.1.1.0), follow these steps:
  1. Double-click the oui.exe file in the8.1.1.0\Windows\Client\Siebel_Tools\Disk1\install folder of the installation image.
  2. Keep the defaults in the dialogs except for the following.
  3. Choose a suitable path and home.
  4. In the file system path dialog select the path which points to the SAMPLE\FILES folder in the client installation directory.
  5. Wait for the installer to finish before you use or launch any other program.
Step 14: Apply Siebel Tools patch (8.1.1.11)
To apply the Siebel Tools patch (8.1.1.11), follow these steps:
  1. Double-click the setup.bat file in the 8.1.1.11\Windows\Client\Siebel_Tools\Disk1\install folder of the installation image.
  2. Click Next in the Welcome screen.
  3. Ensure that the client home you defined in step 10.2 is selected and click Next.
  4. Click Install.
  5. Wait until the dialog displays a success message and exit the installer.

Step 15: Copy the new SRF file

Copy the siebel_sia.srf file you extracted from the srf.zip archive to the correct language specific directory in the OBJECTS folder of both the Developer Web Client and Siebel Tools.

Step 16: Change permissions on Siebel installation folders

To be able to edit .cfg files and for other reasons, we should ensure that our user account has full control over all files and subfolders in the installation directories. One way to do that is as follows:

  1. In Windows Explorer, navigate to the uppermost installation folder for the Siebel software.
  2. Right-click the folder and select Properties.
  3. Click the Security tab.
  4. Select the Authenticated Users group.
  5. Click the Edit button.
  6. Set the Full Control permission level to “Allow”.
  7. Click OK.
  8. Click the Advanced button.
  9. Click the Change Permissions button.
  10. Click the check box named “Replace all child permissions….“.
  11. Click OK.
  12. Click Yes.
  13. Click OK.
Step 17a: Modify the tools.cfg file for use with the Siebel Sample Database
 
The following steps are necessary to be able to connect Siebel Tools to the Siebel Sample Database. Remember we installed the sample database into the client installation directory. What we do is change the ConnectString parameter in the tools.cfg file to point to the sample database file (sse_samp.dbf) in the client directory.
  1. Open the uagent.cfg file in the client’s BIN\ENU directory with Notepad.
  2. Copy the value of the ConnectString parameter in the [Sample] section of theuagent.cfg file to the clipboard.
  3. Open the tools.cfg file in the Siebel Tools BIN\ENU directory with Notepad.
  4. Overwrite the value of the ConnectString parameter in the [Sample] section of thetools.cfg file with the value you copied in step 6.
  5. Save and close all files.
Step 17b: Modify the client .cfg files
Now, we prepare the client configuration files and (optionally) create .cfg files for running the Siebel Client in Open UI mode.

  • Navigate to the client install folder and open the BIN\ENU directory.
  • Open the client .cfg file of your choice (e.g. uagent.cfg for Siebel Call Center)
  • Set the EnableFQDN parameter to FALSE.
  • To create a .cfg file for Open UI, it is recommended to copy an existing .cfg file and rename it to something like uagent_oui.cfg.
  • In the copied file, find the [InfraUIFramework] section and add the following line:
    EnableOpenUI = TRUE

Repeat these steps for every application you want to use. For example, for Siebel Marketing, you would choose the market.cfg file.

Step 17: Manage Shortcuts
 
The installers place a bunch of pre-built shortcuts into your start menu. To ensure proper execution of your shortcuts, set the compatibility for all shortcuts you want to use to “Windows XP” and check the “Run this program as administrator” flag.
If you don’t have MS Internet Explorer set as your system default browser, you must add a string similar to the following to the shortcuts which launch high-interactivity clients.
/b “C:\Program Files (x86)\Internet Explorer\iexplore.exe”
Here is an example shortcut to launch Siebel Call Center in Open UI mode in the default browser:

D:\siebel\client\BIN\siebel.exe /c D:\siebel\client\bin\enu\uagent_oui.cfg /d sample /u SADMIN /p SADMIN

If you want to switches siebel.exe and siebdev.exe:
siebel.exe, as we all know, is the engine behind the non-zero-footprint flavour of Siebel applications, namely the Mobile Web Client or the Developer Web Client. Some call it fat client, some call it dedicated web client, depending mostly on the year when they first heard about it. Discussions whether the Mobile Web Client is a different installer than the Developer Web Client and whether the Developer Web Client is the same thing as the fat client often reach religious depths.

The installer places a bunch of shortcuts in the windows start menu which usually follow the syntax of

<path to siebel.exe> /c <path to .cfg file>

So /c is a mandatory switch because any Siebel applications consists of the very same executable along with a different configuration file from which it reads the rest of its knowledge.

In order to please the more inquisitive among you, find below a complete list of switches that you can use with siebel.exe. If you know of any other switch, please inform us.

Typical switches (used in shortcuts)

/c Path to .cfg file (required), directory path defaults to <client_installdir>\bin\enu
/d Datasource (as in .cfg file), defaults to local
/l language (optional, language pack must be installed), defaults to enu
/u Username (optional)
/p Password (optional)
/s Path to spool file (optional, to spool all SQL generated by siebel.exe)

Extra switches

/b Path to Browser executable (optional, for multi-browser testing of customer or partner (SI) applications)
/h Debug Mode (used with Siebel Tools for debugging)
/ctsim (often confused with /ctisim, which does not work 😉 CTI Simulation mode (used for demo; no longer valid with Siebel 8.1.1.x and later because Oracle removed the demo driver dll)
/editseeddata allows modification of seed data, often referred to in maintenance release guides
/webservice (followed by a port number) can be used since fix pack 8.1.1.2 to use the Developer Web Client to test Siebel inbound web services.
/z will cause the Developer Web Client to navigate to the Workflow Simulator Wait View. This switch is obviously intended for the Workflow Simulator functionality.

And now for siebdev.exe:

siebdev.exe is the engine behind Siebel Tools, which is the only application that does not run in a browser window. However, Siebel Tools is defined in the Siebel Repository and the siebdev.exe works just like the siebel.exe. That is, it reads a .cfg file and an .srf file (the file that newbies usually try to compile to during their first steps with Siebel Tools).

So siebdev.exe accepts most of the switches that siebel.exe does, namely /c, /d, /u, /pand /s.

But there are some additional switches, used in conjunction with the “classic” ones. They have been passed along from consultant mouth to consultant ear for eons before they found their way into the documentation.

/bv runs all validation rules for the entire repository, so take your time
/batchimport automates the import of .sif files
/batchexport automates the export of objects to .sif files
/bc allows to run batch compilation
/tl language (typically used with /bc for multiple language deployments)
/applybatchpatch is used for applying batch patches, or patches in batches.

Step 18: Get started with the Siebel Sample Database
Congratulations! You can now launch all Siebel CRM applications from the Start Menu and connect to the Sample data source.
Of course, there’s the Siebel Administrator account (SADMIN) to start with. The passwords in the sample database are equal to the account name. But there are more meaningful demo user accounts in the sample database.
Make sure you take a look into the Demo Users Reference (in the Siebel bookshelf) so you are one step ahead of the competition ;-).

Siebel Call Center 8.1.1.11 (slightly altered vanilla theme) in Open UI mode.

Dynamically Show-Hide UI controls in Product Configurator

Dynamically Show-Hide UI controls in Product Configurator


Dynamic User properties allows us to

  1. Show or Hide UI controls for product such as relationships, groups, products, tabs, attributes, linked items or resources.
  2. Make User Interface controls read-only
  3. Show or hide images, based on the choices that the user makes in Siebel Configurator.

Requirement: Based on the Product selected by the user, set of attributes should be hidden.

Scenario:

  • We have a root product “Test Product Import” with Attribute “Test Attribute”  Root Product has 3 Sub Products
    • Test Product Import 1
    • Test Product Import 2
    • Test Product Import 3
  • Test Attribute has values “None” and “1” to “6”

clip_image002[1]

  • When the user selects “Test Product Import 1”, some of the values from the “Test Attribute” should be hidden (ex. Values 1 , 2 and 3) as shown in the below screenshot.

clip_image004[1]

  • When the user selects “Test Product Import 2”, some other values from the “Test Attribute” should be hidden ( ex. Values 4 , 5 and 6) as shown in the below screenshot.

clip_image006[1]

Technical Details:

The above solution is achieved by using the Dynamic UI Properties on Root product using function cfgEval(), which returns value “Y” or “N” and using the function returned value in Attributes  to hide the values based on the selection made by the user.

Function cfgEval():  Use CfgEval() to access instance information inside Siebel Configurator, for example, to whether a user has set an attribute or selected a component product. Using the CfgEval() function to create simple expressions that reference session values such as the product quantity and attributes that the user selects.

Here are some examples of how to use this function:

  • Check whether the user has selected an attribute on the Root Product:
    • CfgEval($.[RootProduct]#1.xa[AttributeName].xf[Value])=’ABC’)
  • Check whether the user has selected an attribute on the Child Product:
    • CfgEval($.[RootProduct]#1.[RelationshipName]#[ChildProductName].xa[AttributeName].xf[Value])=’AB’)
  • Check the quantity of a child product:
    • CfgEval($.[RootProduct]#1.[RelationshipName]#[ChildProductName].xf[Quantity]) =‘2′)
  • To return an attribute value of a child product:
    • CfgEval($.[RootProduct]#1.[RelationshipName]#[ChildProductName].xa[AttributeName].xf[Value])
  • To return the quantity of a child product
    • CfgEval($.[RootProduct]#1.[RelationshipName]#[ChildProductName].xf[Quantity])

Now back to the solution. Create below mentioned UI Properties on Root Product or Attributes as mentioned in the table and the screenshot shown below

S.No Property Name Value Level
1 CfgUIStateModel Y Root Product
2 Expr1 CfgEval($.[Test Product Import]#1.[Relationship 1]#[Test Product Import 1].xf[Quantity]) =’1′ Root Product
3 Expr2 CfgEval($.[Test Product Import]#1.[Relationship 2]#[Test Product Import 2].xf[Quantity]) =’1′ Root Product
4 DynamicHide Expr1 Y Attribute
5 DynamicHide Expr2 Y Attribute

clip_image008[1]

clip_image010[1]

You will be able to see the behavior described above once you have completed the changes mentioned above

Note: cfgEval() is a very useful function and can be used to control dynamic behavior of Product/Attribute selection. Dynamic UI property can also be used to display set of products based on the attribute selected. The only difference will be in the Expression written on the Root product. To fetch the value of the attribute selected by the user, the expression will be

Expr1: CfgEval($.[Root Product Name]#1.xa[Attribute Name].xf[Value])=Attribute Value’ .