Now that the Siebel 17 installation is complete, we can start the logical configuration and deployment process. It’s at this point you’ll want to apply any Patch Sets or whatever – just remember to shutdown the containers for the AI and Enterprise (via the applicationcontainer\bin\shutdown.bat script) and stop the Gateway service.
Before starting with the logical deployment, quickly check the regional settings on your host, if you’re running Windows. This must be set to “English (United States)” or the deployment process will fail. Oracle are fixing this under bug 27348563.
The Siebel Management Console is where all the activities take place. Think of this as an abstraction over the old configuration batch files, the shortcuts for which used to be installed in your start menu. There’s an order to the deployment tasks, so let’s go through them one by one.
Deploy the Enterprise
- First up, create a Siebel Fileshare folder somewhere on the host. I used “D:\Siebel\siebel_fs”
- Start the deployment process by navigating to the Profiles > Enterprise tab on the left side of the Siebel Management Console (hereafter referred to as SMC)
- Clone the sample profile and give it a name, for example “siebel_enterprise_profile”. The clone button is the one with two squares overlapping
- On the first tab, set the primary file system to the absolute path of the fileshare folder that you created. For example, “D:\Siebel\siebel_fs”. Enter the SADMIN username and password in the authentication section
- On the next tab, enter your database platform details. See an example from my Oracle Database Server below:
- On the next tab, select the “Gateway” authentication profile that you created when first logging in to the SMC
- On the last tab, you can leave the encryption type field unchanged
- Now submit the profile
- Now click the Deployment tab on the left of the SMC, and click the “+” button to create a new deployment action. Click the “Enterprise” item
- Select your Enterprise profile, give it a name, and select the “Deploy” radio button before submitting the activity
- After a great deal of whirring and clunking, your new Enterprise will be deployed into the ZooKeeper keystore and made available within the Gateway. You’ll also see a file system structure in place, a Gateway service and an ODBC datasource
Deploy the Siebel Server
Deployment of the Siebel Server is more of the same.
- Start the deployment process by navigating to the Profiles > Siebel Server tab on the left side of the SMC
- Clone the sample profile and give yours a name. For example, “siebel_server_profile”
- Enter the SADMIN username and password and the GUESTCST username and password, as you setup in your database
- Pick which Component Groups you want to enable and leave the port numbers as is
- On the last tab, leave everything as is. You’re all set to submit the profile
- Now click the Deployment tab on the left of the SMC, and click the “+” button to create a new deployment action. Click the “Siebel Server” item
- Select your Siebel Server profile, and enter your FQDN and HTTS port number. For example, “SIEB17.siebel-tech.com:9021”
- Give your Siebel Server a name, pick your languages and you’re ready to submit your Siebel Server deployment
- With a bit of luck, you’ll find a Siebel Server Services awaiting you!
Deploy the Application Interface
There’s a bit more to do to deploy the Application Interface, the replacement for the Siebel Web Engine.
- Start the deployment process by navigating to the Profiles > Application Interface tab on the left side of the SMC
- Clone the sample profile and give yours a name. For example, “ucm_appinterface_profile”
- You don’t need to worry much about what’s here, but you’ll want to specify the GUESTCST password as you defined it during the database setup
- Pick your object manager and specify your REST response base URL. For example, “https://SIEB17.siebel-tech.com:9011/siebel/v1.0/”
- On the second tab, give the application a name, for example “ucm” and choose the object manager. I’ve gone for “ucmobjmgr_enu”. Update the anonymous GUESTCST user password as before
- The third and forth tabs can remain unchanged. Simply submit your profile
- Now click the Deployment tab on the left of the SMC, and click the “+” button to create a new deployment action. Click the “Application Interface” item
- Specify the FQDN and HTTPS port number again. For example, “SIEB17.siebel-tech.com:9021”
- Select your profile and give the new AI a name and description before submitting the deployment
- You should see green lights all around!
You can now access your Siebel 17 user interface using your host plus the name of your AI profile. For example, “https://sieb17.siebel-tech.com:9011/siebel/app/ucm/enu”
Having installed the Siebel 17 software, there’s one more step before we can set up the logical Gateway, Enterprise, Siebel Server and Application Interface (what used to be the SWSE): install the Siebel database.
As part of the Siebel Server installation, you’ll have installed the Siebel Database Server components. You can find a traditional shortcut to the configuration tool on your start menu, just like the good old days. Invoke this, enter your database connectivity details and sit back while the installer does its thing:
I noted that the installation process is significantly quicker than it used to be, even though the database installer has a lot more work to do in setting up the repository tables for workspaces. After just over an hour, I have a Siebel database ready to use.
Within the Siebel Server bin folder, you’ll find a shortcut to the license key deployment tool (LicenseKeyModule.bat). Double click this and enter your database connection details:
Select the components you’d like to use in your development environment. Click “Apply” to finish the job:
We’re ready to rock – tune in tomorrow for a detailed guided to the Siebel Management Console and the process to deploy the Gateway, Enterprise, Siebel Server and AI.
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.
Haley, what are you still doing here?
Installing the Application Interface
Running the installer, I see a familiar sight in the usual Siebel install wizard:
Some familiar and not so familiar installation options
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. I’ve written a new post that contains a Windows batch file that you can amend and simply run to produce the appropriate keystore and truststore files.
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.
War file deployed, installation complete. Phew!
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!
Oracle XE is a a bit of beast, a pain in the proverbial to install and overkill for the purpose of a local Siebel database. However, it is at least an Oracle database and not a Sybase database, as it was in days gone by.
What this means is that it is possible to use Oracle tools to access and manipulate the data. Gone are the days of disql and it’s more than limited functionality. We can now access the local and sample databases using SQL Developer and other Oracle tools, such as import / export and data pump. I used this fact to my advantage, recently, to populate a fresh Siebel 16 server installation with demo data. This lets me use the full gamut of thin client apps, with useful data and users.
Terry Smythe’s Accounts!
Install the Sample DB
First up, we need to install the XE sample using the Tools or Client installers. All straight forward (as of 16.2, anyway) and you’ll be left with an XE Service that’s running and listening on localhost, port 1521.
Reset the System Password
We now need to get access to the system account, so that we can mess around. Bring up a command prompt and enter:
connect / as sysdba
alter user system identified by system;
This will reset the “system” password. Note that SADMIN and SIEBEL use the equivalent value for logging in.
Export the XE Sample Data
You can use Oracle Data Pump (impdp / expdp) to do this, but I found it to be a bit of a hassle – my target is an RDS instance on Amazon, so I’d have to push a load of files up in order for data pump to suck them in. As it is, I used the old fashion import / export (imp / exp) commands in XE to do the job.
First up, we don’t want all the data from sample – we really only want “S_” tables and we want to exclude the Repository tables. As such, I selected out the tables I wanted directly from S_TABLE:
SELECT NAME FROM SIEBEL.S_TABLE
WHERE TYPE <> 'Repository'
AND NAME LIKE 'S_%'
ORDER BY NAME ASC
I then saved this to a text file (tables.par) and modified this to work as a parameter file input into the “exp” command:
I then initiated an export from my XE database. Note that the exp command can be found in the Tools installation folder, <TOOLS>\oraclexe\app\oracle\product\11.2.0\server\bin:
exp SIEBEL/SIEBEL@SAMPLE_XE BUFFER=16384 FILE=C:\Oracle\Exp\Sample.dmp GRANTS=N TRIGGERS=N CONSTRAINTS=N STATISTICS=NONE PARFILE=C:\Oracle\Exp\tables.par
This took roughly 15 minutes to complete and I’m left with a “.dmp” file of around 4GB in size.
Import the Sample Data into Oracle Server
You can probably guess the next step – using the “imp” command to import the data into my Server Oracle instance. The process is much the same as for export – the main point of note here is that we want to explicitly ignore errors. Even though we’re pushing sample data into a “clean” Siebel Database, there’s still a load of seed data in there that we don’t want duplicated. By ignoring errors, the indexes will keep duplicates out while allowing the whole process to complete without terminating:
imp SIEBEL/SIEBEL@TARGET FROMUSER=SIEBEL TOUSER=SIEBEL BUFFER=16384 FILE=C:\Oracle\Exp\Sample.dmp IGNORE=Y PARFILE=tables.par
Create our test users
Now that we have all the sample data in the server DB, we must create some users to match the thousand or so S_USER records that have been created for our use across the sample system. Again, I put Oracle’s own tools to good use and created a SQL script in SQL Developer:
SELECT 'GRANT CONNECT TO ' || LOGIN || 'IDENTIFIED BY ' || LOGIN || '; ' || 'GRANT SSE_ROLE TO ' || LOGIN
WHERE LOGIN NOT IN ('SADMIN', 'SIEBEL', 'GUESTCST', 'GUESTERP', 'LDAPUSER')
Execute this script and users will be created. Be careful to exclude any users you don’t want to affect (SIEBEL and SADMIN being the main ones) as the script will reset their passwords. You can find a list of relevant test users for each Siebel vertical in this Bookshelf Guide.
Login as Casey Cheng!
It’s what you’ve always wanted, right? Fire up Siebel Call Center and login as CCHENG. Ah, memories!
Now sit back and enjoy perusing the sample data from the comfort of your full Siebel installation.
Well, it was only a matter of time before I ended up working with Siebel again!
I’ve been introduced recently to Amazon Web Services – AWS to you and me. So this is what Cloud Computing is all about! I’m utterly gob-smacked by the power of this platform, the stuff you can do and the speed at which you can do it.
I was tasked with building a Siebel 16 installation using AWS and it is amazingly straight forward. Not to mention incredibly cost effective, compared to using physical hardware and on-premise virtualisation.
I thought I’d share with you the process of spinning Siebel up “in the Cloud”!
First up, my architecture involves two AWS instances – an RDS instance for the database and an EC2 instance for the Application and Web Servers. Using RDS, I’m able to spin up an Oracle Enterprise Edition 12c database in less than 10 minutes. It’s literally a few clicks and you’re done – no more slaving away with OUI, downloading files and the installation and configuration process. AWS captures parameters from simple web pages and does the rest – lightening fast. AWS will even keep my Oracle installation up to date, automatically applying minor patch updates during a maintenance windows that I can define.
So, I have a database instance up and running. I then spin up a new Windows 2012 R2 server. Again, the process is ludicrously quick. I choose from a number of types that have varying RAM, CPU and bandwidth allocations, allocate C and D drives with 60 and 120GB respectively and click a button. Less than 10 minutes later, I have an RDP file to download to my laptop that allows me to connect to the new server. I then jump on to Oracle eDelivery and download the Siebel installation media – I’m getting speeds of nearly 70MBs (that’s mega BYTES, not BITS!) and download the full Siebel installation in under 15 minutes. I unzip the media and backup the installation files to Amazon’s storage offering, S3.
I download and install a Java SDK, Oracle 12c 32-bit Client and SQL Developer then set up my TNSNAMES. I then run SNIC to extract everything and prepare my Siebel installation media and kick off my Siebel installation. Within another couple of hours I have a fully functioning Siebel environment.
While this is all pretty much “installing Siebel on a remote server”, the real benefit comes of now saving my Siebel Server installed as an Amazon Machine Image (AMI). This will allow me to VERY quickly spin up new Siebel 16 server environments for whatever I need – training, dev environments, the list is endless.
I’ve always been a bit of a cynic when it comes to “Cloud” computing but AWS has got me converted. This stuff is HUGE and it is AWESOME – with this stuff, server rooms are sure to become a thing of the past.