Photo Guide : Installation of Siebel IP 2017

It wouldn't be the same without the Siebel Hub team working hard to give you the news on
the very recent release of Siebel Enterprise. IP 2017 promises to be big, bold and…I cannot
think of another word beginning with "B" except "bug" and that is obviously not at all the
case. Siebel IP 2017 has undergone significant beta testing and the Siebel Hub is looking
forward to working with this truly ground-breaking release. So let's get started with the
Installation of Siebel IP 2017!

As you may remember, last time out for IP 2016 we delivered a Photo Guide in the manner of
a 1970's teenage photo romance (my sister used to read them). For IP 2017 we are going to be
doing the same thing. The good news is that the first part of the process has not changed, and
the Shopping List is pretty similar.

IP 2017 Shopping List

 Oracle VirtualBox as the virtualization tool

 Windows 2008 R2 Evaluation Version which is your operating system
o NOTE : You will probably want to use Windows 12 Server 64bit
 MS SQL Server 2012Evaluation Version which is the database platform you will
install on your virtual PC
 Java JDK which you will need to download in both 32 bit and 64 bit versions
 Downloaded NET to 4.5.2. for the installer of MS SQL Management Studio to work
properly
 SQL Server Management Studio version 17.1.
 The Siebel IP17 Starter Installation Requirements – called Siebel CRM Base release
17.0.0.0.0 from edelivery.oracle.com

Part One, create the VM, install Windows and SQL Server (for the purposes of the rest of the
guide, I used the same versions of Windows (2008 64bit R2) and SQL Server (2012)
mentioned above).

TIP : rename your VM to something very short (eight characters for example)

Prepare your VM

A requirement : in the naming dialog in Windows, click More… and add a DNS suffix of
local. So the fully qualified name of your VM will be XXXXXXXX.local. You will need this
in the next steps when you set up secure communication and certificates.
Part Two, download the software from edelivery.oracle.com, unzip and use SNIC to create
the install images is exactly the same, up to and including the picture labelled "IP17 Join
Here". Yes, you guessed it, I just added that today.

TIP : You should however know that the 2 files called V86670-01_10f2.zip and V86670-
01_20f2.zip, although they are not marked as Starter Requirements, are required to be able to
create the installer of the Server software. So I figure you will need them.

Create Install Images

Assuming you have now unzipped and SNICced everything, here is the first "new" part of the
story. As before this guide, I've just mentioned it, was written for MS SQL Server, using
Windows 2008 R2 64 Bit, English United States. Before you do any further Siebel-related
installing, you are going to need a certificate for the installation of Siebel IP 2017.

One of the new and important changes in Siebel IP 17 is the requirement for secure
communication everywhere. So whenever you connect to the new Siebel Management
Console to manage your Siebel environment, you will do so with the S in HTTPS. Whenever
your Management Console talks to the Siebel Enterprise, it will use TLS (Transport Level
Security), the successor to SSL.

TIP : Download OpenSLL from this site. Specifically I downloaded version 1.0.2.L 64 bit .
Install the software and make sure you add the OpenSSL bin folder to your PATH in the
Windows Environment Variables.

Creating a Certificate and Key Store

Run the following commands. These are a mixture of OpenSSL commands and keytool
commands. Keytool is a Java key and certificate management utility. It allows users to
manage their own public/private key pairs and certificates. It also allows users to cache
certificates. Java Keytool stores the keys and certificates in what is called a keystore. By
default the Java keystore is implemented as a file.

TIP: The file you create will be used multiple times during the install of the Siebel software
for IP 2017. To make your life easier, you should create two folders on your virtual hard disk
: one called CA and one called KEYS. These will be used in the upcoming steps.

TIP : Before you begin, create a text file called serial.txt in your KEYS folder. You could do
it by running this command in Windows

 echo 1234 > c:\CA\serial.txt

Now we make the certificate magic happen:

 openssl req -new -keyout c:\CA\cakey.pem -out c:\CA\careq.pem

 openssl x509 -signkey c:\CA\cakey.pem -req -days 3650 -in c:\CA\careq.pem -out
c:\CA\caroot.cer -extensions v3_ca
 keytool -genkeypair -alias siebel -keyalg RSA -keystore C:\keys\siebelkeystore.jks -
keysize 2048
 keytool -import -trustcacerts -alias ca -file c:\CA\caroot.cer -keystore
c:\keys\siebelkeystore.jks
 keytool -certreq -alias siebel -keystore C:\keys\siebelkeystore.jks -file
C:\keys\ALLINONE.csr
 openssl x509 -CA c:\ca\caroot.cer -CAkey c:\ca\cakey.pem -CAserial c:\ca\serial.txt -
req -in c:\Keys\ALLINONE.csr -out c:\Keys\ALLINONE.cer -days 365
 keytool -import -keystore C:\keys\siebelkeystore.jks -file c:\keys\ALLINONE.cer -
alias siebel

So I can here just a few of you staying "What the ?". Lets go back through the steps and see
what you have just done.

 created a new CA root certificate

o TIP: Keep a note of the passwords and of every item you enter here.
ALWAYS enter the same information whenever asked.
o TIP: The Common Name must be the fully qualified name of your virtual
machine XXXXXXXX.local
 self-signed the CA root certificate
 created a keystore file and a new public / private key pair
  imported the CA root certificate into our keystore file
 created a certificate Signing Request
 signed the request
 imported the signing reply into our keystore.

So you now have a very important file in your KEYS folder. The siebelkeystore.jks file will
be required for the next steps. You can now install the software of the Siebel Enterprise and
the Siebel Application Interface.

Installation
By now you should have two folders with your software installed. If you have been really
lucky, you may even have two instances of javaw.exe running in your Task Manager. Do
NOT touch them :). If you have to restart your machine for whatever reason, you will find the
necessary files to restart the backend in the c:\Siebel\SES\applicationcontainer\bin\setenv.bat
and startup.bat and the equivalent in the folder you installed the AI into as well. Open a
Command Prompt and run them in the order shown. That's four in total to restart the AI and
SES.

What's next? Well, thank goodness it is time for some easy stuff.

Grant USR

Open Microsoft SQL Server Management Studio and login as sa. Open a Connection to your
Server. Create a database as described in the IP 16 guide. Open the
c:\Siebel\dbsrvr\MSSQL\grantusr.sql file and edit it so that you can just run the important
bits:
Install Schema

Next, install the Database Schema. The old, rotating globe Siebel DB Configuration Tool is
the only one that has survived from the previous release. You will find it in the Windows
Start menu. Choose Install a New Database, and confirm you have already run the
GRANTUSR script.
TIP : This process will also set up Workspaces for you, so expect the process to be a little
longer than normal.

Activate License Keys

Now you need to activate the license keys you need. The utility for doing so is in the
c:\Siebel\SES\siebsrvr\bin folder and you can run it by double-clicking the batch
file LicenseKeyModule.bat.
TIP: As you can see above, for MS SQL Server, there appears to be a (frequent, seen before
elsewhere) that requires you to replace the Table Owner (for example SIEBEL) with the
database name followed by a period (for example SIEBELDB.).

Open Management Console

Now, in theory you are ready to rock. Assuming your two javaw.exe are running, open a
browser and enter https://allinone.local:9001/siebel/smc or whatever your equivalent is. The
port number is from the AI install, the HTTPS port to be precise.
TIP : When you first login, use the Username and Password that you hard-coded during the
install (see ***When you first start the Management Console, use this username and
password*** above). After setting up the Authentication Profile you will not be able to use
that login and password any more, and you will be required to use the Database SADMIN
and associated password, as you will have switched to Database Authentication. Think of it
as a "one shot" bootstrap login.

You should now be looking at this, your new (empty) environment: