So, it’s finally arrived – Siebel 17 is here!
Of course, I’ve immediately hammered my home broadband to download all 20 delightful gigabytes of installation material to give you the low down on how to set it all up.
I’ve prepared 4 VMs for my Siebel 17 environment:
- Siebel Web – will hold the Apache Tomcat applications for both the Siebel Management Console (SMC) and the OM “Application Interface” component – the new name for SWSE
- Siebel App – will hold the Gateway and Siebel Server components
- Siebel DB – runs an Oracle 12c database
- Siebel Client – we’ll put Tools on here, just for old times sake!
At the moment, we’re only really interested in the first three.
I take a moment, these days, to prep my machines before installing anything. This typically involves an installation of a Java SDK, an Oracle Client, all Windows updates, SQL Developer and so on. My machines were ready to go by the time I’d used SNIC.BAT to produce me some installers.
Installing the Application Interface
Running the installer, I see a familiar sight in the usual Siebel install wizard:
Clearly, there are some new additions this time around! Installing the Application Interface requires the creation of a keystore and truststore, concepts that will be familiar to anyone who has used Tomcat in the past. I ran a few quick commands from my Java JDK bin folder to generate both. Note that there are some specific requirements for these files documented in Bookshelf and full instructions can be found in article Doc ID 2294567.1 on My Oracle Support. Note, you’ll need to substitute your host FQDN in place of <my-host.local>:
keytool -genkey -alias siebel -keystore siebel_keystore.jks -keyalg RSA -sigalg SHA1withRSA -dname "cn=my-host.local"
openssl req -new -keyout c:\ca\private_key_file -out c:\ca\certificate_authority_name -subj "/CN=my-host.local"
openssl x509 -signkey c:\ca\private_key_file -req -days 3650 -in c:\ca\certificate_authority_name -out c:\ca\caroot.cer -extensions v3_ca
keytool -certreq -alias siebel -keystore siebel_keystore.jks -file c:\keys\keystore_file.csr
echo 1234 > c:\ca\serial.txt
openssl x509 -CA c:\ca\caroot.cer -CAkey c:\ca\private_key_file -CAserial c:\ca\serial.txt -req -in c:\keys\keystore_file.csr -out c:\keys\keystore_file_signed.cer -days 365
keytool -import -alias localhost -file c:\ca\caroot.cer -keystore C:\keys\siebel_keystore.jks
keytool -import -alias alias_name -file C:\keys\keystore_file_signed.cer -keystore C:\keys\siebel_keystore.jks
Specify the siebel_keystore.jks for both the keystore and truststore files created above in the installation process, along with your chosen password.
During the installation process, you need to choose and note down ports for each of the Tomcat REST facades that will sit atop the Siebel components. These facades abstract a management interface that allows configuration and maintenance centrally, from the Siebel Management Console. It’s important that you write these down, though they can be derived by referring to the Tomcat configuration files within the applicationcontainer folder in each of your component installations. I’ve opted to use a standard range for each component across the HTTPS, HTTP and Shutdown ports respectively:
- Application Interface: 9011, 9012, 9013
- Gateway: 9021, 9022, 9033 (with 9034 as the Gateway TLS port)
- Siebel Server 1: 9031, 9032, 9033
Installing the Enterprise Server
The Enterprise Server installation is much the same and I elect to install the Gateway and Siebel Server separately, by invoking the installer two more times, picking a different installation folder and set of ports for each.
Not much else to do now but click “Next” and await success.
Okay, so I’ve only just scraped the tip of the Siebel 17 iceberg, by installing the base software. There’s a lot more to do to get my Siebel 17 environment up and running. Stay tuned for the next instalment!