Welcome to Installing Siebel 220.127.116.11 on Windows 2008R2 Server Part 3 of the series
In this part we will install and configure the Siebel Gateway and the Siebel Enterprise server Software.
To Install a Siebel Development Server we will go through the following steps
- Install the Prerequisite Software – this was completed in part 2 (here)
- Install and Configure the Siebel Enterprise Server (this step)
- Install and Configure the Siebel Database Server
- Install and Configure the Siebel Server
- Install and Configure the Siebel Web Server
- Patching and Postinstallation Tasks
- Installing Siebel Charts
- Enabling OpenUI
Run this entire installation as the siebel service user, which must have full local administrator rights.
My installation media is the SIA 18.104.22.168 base. Start with the Siebel Enterprise Server Software (aka SES).
My Installer speaks Danish. I do not want that, so I change the locale of the Siebel Service user to English (United States). Apply changes so they take effect, and then start the installer again.
It seems there are no command line property to control the language of the installer anymore ??? annoying!
This is better:
Provide your oracle user support identification if so desired.
Choose New Installation
Provide your home name, and the home location. I do not use the defaults, so I record this and everything else in a documentation sheet for my later reference.
I Install everything
Add any additional Language Packs if you so desire, by doing these upfront, the installers will configure object managers for all chosen languages automatically.
Provide a folder name (this will be the start menu entry in windows start > programs). I don’t use the default.
Review the configuration Summary for any errors:
Hit Install and watch the installer do it’s thing.
Be Patient – this takes quite a long time.
Success! or was it ??
Now looking at my target directory and it’s completely empty !!!? Damn Oracle – Completed With Success ?? What Log File ??
If your target directory seems ok, there are files in there – you can skip my ramblings below and continue to the configuration!
After A LOT of tinkering around I found that is is possible to start the module installer with -debug switch, it makes the installer spit out lots of information about the installation process, and it turns out here was a permissions error:
Install API: OUI-10038:You do not have the necessary permissions to write to the inventory at C:\Program Files (x86)\Oracle\Inventory. Please make sure that you have the appropriate permissions to perform the installation.
oracle.sysman.oii.oiic.OiicInstallAPIException: OUI-10038:You do not have the necessary permissions to write to the inventory at C:\Program Files (x86)\Oracle\Inventory. Please make sure that you have the appropriate permissions to perform the installation.
As it turned out I got the account type set wrong for my Siebel Service User – It was not a local administrator!
So I fixed this a did the entire thing again, and:
The Installation started, only to throw out OUI-7000 errors like these at me (they did not abort the installation):
I Uninstalled the whole server application set again (using the oracle installer provided with the Oracle x32 Client install as the Siebel Home was not created proper). This was also caused by not having the full local machine administrator rights. I corrected the rights, and did the installation again – this time it worked. I hope you read my precursor, where i mentioned that the Siebel Service User should have local machine admin rights 🙂
Next is the configuration of the Siebel Gateway Server
Run the “Siebel Enterprise Configuration” Option from the Start > Programs > Siebel Folder Name
Create a New Configuration. Hit Next.
We are configuring a New Gateway Server. Hit Next
Don’t change the default port. Hit Next. Note that generally – it is possible to change all configurable ports, as long as you document the changes for later reference. For most installations I would recommend that you do not change the ports, but rather configure firewall rules to allow the standard Siebel ports. It may however be appropriate to change all ports in a high security environment.
If you installed more than one language select your primary language now.
Set the Gateway to start automatically. Hit Next.
We do not use a response file. Hit Next.
Verify Configuration Options, notice the error in the primary language configuration options – that’s an oracle installer feature/error – as the language is selected correct.. Hit Next to complete the configuration.
Check that the Gateway starts correct. (in the services control panel).
Next is the configuration of the Enterprise itself.
Run the “Siebel Enterprise Configuration” Option from the Start > Programs > Siebel Folder Name (again).
We will create a New Configuration. Hit Next.
We are configuring a New Enterprise in the Gateway. Hit Next.
This is the Server Authentication user Name, by that they mean the Siebel Application Administrator aka SADMIN. Hit Next.
Define SADMIN’s password (which cannot be the same as the username), the password is case sensitive! Record these settings in a document for you later perusal. Hit Next.
This is the NETBIOS name for the gateway server – it cannot be a fqdn! Hit Next.
The Gateway Server Port – still 2320, you did not change it – right ?? Hit Next.
Define the siebel Enterprise Name, in a multi server installation you could name your enterprise after eg. your company and the servers roles, and the subsequent servers appropriately – to maybe avoid confusing names where everything is just named Siebel. Hit Next.
Provide a Description for the Enterprise. Hit Next
Provide an UNC path to the Siebel File System. Hit Next.
We use Oracle. Hit Next.
Define the table Owner (Usually SIEBEL). Hit Next.
Provide the SQLNet Name for the Database Created earlier. Hit Next.
Provide SADMIN’s username. Hit Next.
And the Password (same as Before), Note its Still Case Sensitive! Hit Next.
For Development choose Database Authentication, for Test and Production use choose one of the other options as appropriate. Hit Next.
For Development do not Change the SecurityAdapters Subsystem Name. It relates to the selection before. Hit Next.
Set Checkmark in Propagate, Hit Next.
You do not need to do more configuration (We will do Charts later). Hit Next.
We do not use a response file. Hit Next.
Verify the Configuration Parameters, and Hit Next to Complete the Configuration.
Then we’re good, and the Enterprise was Configured OK.
Now we are ready to start the installation of the Siebel Database Server. Read on in the next part in the series “Install and Configure the Siebel Database Server“