{"id":73119,"date":"2016-04-13T10:07:23","date_gmt":"2016-04-13T10:07:23","guid":{"rendered":"https:\/\/www.red-gate.com\/simple-talk\/uncategorized\/siebel-crm-part-8-configuring-and-starting-the-siebel-sandbox\/"},"modified":"2021-07-14T13:07:08","modified_gmt":"2021-07-14T13:07:08","slug":"siebel-crm-part-8-configuring-and-starting-the-siebel-sandbox","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/databases\/oracle-databases\/siebel-crm-part-8-configuring-and-starting-the-siebel-sandbox\/","title":{"rendered":"Siebel CRM Part 8:- Configuring and Starting the Siebel Sandbox"},"content":{"rendered":"

In the last article in this series, we completed the installation of all of the Siebel components for our sandbox. In this article we will configure all those components so that we can start the Siebel application up.<\/p>\n

Siebel has to be configured in a specific sequence:<\/p>\n

    \n
  1. Create a Gateway Name Server.<\/li>\n
  2. Configure an enterprise in the Gateway Name Server.<\/li>\n
  3. Check the ODBC connection strings.<\/li>\n
  4. Run the DB Configuration utilities to install the Siebel Database.<\/li>\n
  5. Configure the Siebel Application Server.<\/li>\n
  6. Create a web server logical profile.<\/li>\n
  7. Apply the logical profile to the Siebel Web Server.<\/li>\n<\/ol>\n

    Based on the sequence above, we now need to start the configuration.<\/p>\n

    Create a Gateway Name Server<\/h2>\n

    Log on to the Amazon server named Siebel Web_Gateway_Server.<\/strong><\/p>\n

    Click on Start -> Programs -> Siebel Enterprise Server 15.0.0.0.0 and choose Siebel Enterprise Configuration<\/strong> as shown below:<\/p>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Select “Create New Configuration” and Click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select “Configure and New Gateway Name Server” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Keep the default port of 2320 and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Keep the option selected and Click on Next.<\/strong><\/p>\n

    \"\"<\/p>\n

    Click on Next <\/strong>on the summary screen and wait for the execution to finish. This takes only a couple of seconds.<\/p>\n

    \"\"<\/p>\n

    Click on OK<\/strong> on the Success window.<\/p>\n

    This completes the creation of the Siebel Gateway Name Server. The Gateway Name Server is a new Windows service which is created by performing the above steps.<\/p>\n

    Configure an Enterprise in the Siebel Gateway Name Server<\/h2>\n

    The next step is to configure an enterprise in our newly-created Siebel Gateway Name Server. Bring up the Enterprise configuration wizard again:<\/p>\n

    \"\"<\/p>\n

    Click on “Create New Configuration” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select “Configure a New Enterprise in a Gateway Name Server” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    For the Gateway Name server Authentication, enter SADMIN for the user name. Use the password which was created while running the Grantusr Script from the 6th<\/sup> article in the series (Configuring the Siebel Database<\/a>). Once this is done, click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Keep the defaults and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Type in the name for the Enterprise and the Description and click on Next<\/strong>. Make sure that the enterprise name is stored somewhere. We will require this when configuring the Siebel Application Servers.<\/p>\n

    \"\"<\/p>\n

    In the article “Ancillary Software Installation<\/a>” we had created the Siebel File system share on the Amazon server named Siebel Database Server. <\/strong>Enter the UNC path (\\\\<IP_Address>\\<Share_Name>\\<\/code>). Click Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select “Oracle Database Enterprise Edition” and Click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Enter SIEBEL as the Database Table Owner Name and the TNS string for the Oracle Database. Click Next<\/strong> once done.<\/p>\n

    \"\"<\/p>\n

    In the Siebel Database User Account Name type SADMIN. Enter the password for the SADMIN user and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select the “Database Authentication” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Keep the default for the Security Adapter name and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Click on Next<\/strong> and allow the changes to go to the Gateway Name Server.<\/p>\n

    \"\"<\/p>\n

    Since this is a sandbox instance, we do not need to configure any additional enterprise tasks. Click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Click on Next<\/strong> in the summary screen and wait for the execution to finish.<\/p>\n

    \"\"<\/p>\n

    Click on OK<\/strong> on the success screen. This concludes the creation of the Siebel Enterprise.<\/p>\n

    Checking the ODBC connection Strings<\/h2>\n

    Configuring a Siebel Enterprise also creates the corresponding ODBC connections for the Siebel Application to use on the Windows server. Before we go any further, we need to ensure that the ODBC connection we created is working properly. We also need to keep in mind that while Siebel works only on 64-bit architecture, the application on its own is still 32 bit and uses the 32-bit ODBC drivers. To check the connection, open Windows Explorer and navigate to C:\\Windows\\SysWOW64<\/code>.<\/p>\n

    \"\"<\/p>\n

    Execute ODBCAD32.EXE.<\/p>\n

    \"\"<\/p>\n

    Choose the System DSN Tab and click on Configure.<\/strong><\/p>\n

    \"\"<\/p>\n

    Make sure that the ODBC Oracle Driver Setup is as shown above. The Client version must be selected to 10GR1 and later. Click on Test Connect. <\/strong>Make a note of the Data Source Name <\/strong>as it is required when we install the Siebel Database.<\/p>\n

    \"\"<\/p>\n

    Type in the SADMIN Username and Password and click on OK<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Click on OK<\/strong> once the connection is established. Repeat the same steps for the SIEBEL user as well. Once successfully completed, the ODBC connection has been tested and is ready for our next configuration steps.<\/p>\n

    Installing the Siebel Database<\/h2>\n

    Click on Start -> Programs -> Siebel Enterprise Server 15.0.0.0.0, and choose Database Server Configuration as shown below:<\/p>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Accept the defaults and click on Next.<\/strong><\/p>\n

    \"\"<\/p>\n

    Choose “Oracle Database Enterprise Edition” and click on Next.<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Install Database” and click on Next.<\/strong><\/p>\n

    \"\"<\/p>\n

    Select “Install Siebel Database” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Choose “Yes I wish to install a new Siebel Database” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Since we have already run the grantusr script, choose “GRANTUSR.SQL has been run by the DBA to create Siebel users and roles” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Choose UNICODE database and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    While checking the ODBC Connection strings, we made a note of the Datasource name. Enter this value in the ODBC Data Source Name field and click on Next.<\/strong><\/p>\n

    \"\"<\/p>\n

    For the Database User Name Authentication, type in the SADMIN user and the corresponding passwords and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    For the Database Table Owner, type in the SIEBEL User and the corresponding passwords. Click on Next<\/strong> once done.<\/p>\n

    \"\"<\/p>\n

    In the article “Configuring the Siebel Database” we had created two table spaces, one each for the indexes and tables. Type in the corresponding values and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select “Uses the Oracle Parallel Indexing option” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Keep the default and click on Next<\/strong>. The SSE_ROLE is a role created when we run the grantusr script.<\/p>\n

    \"\"<\/p>\n

    Keep the default for the log output directory and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Select “Yes apply configuration changes now” and click on Next<\/strong>.<\/p>\n

    \"\"<\/p>\n

    Click Next<\/strong> on the summary screen to start the wizard.<\/p>\n

    \"\"<\/p>\n

    Click OK <\/strong>to start the installation. Please note that this process takes a while.<\/p>\n

    \"\"<\/p>\n

    \"\"<\/p>\n

    Wait for the wizard to finish. Click on OK<\/strong> once all the steps are completed. This concludes the installation of the Siebel Database.<\/p>\n

    Configure the Siebel Application Server<\/h2>\n

    Up to this point we have completed the following steps:<\/p>\n

      \n
    1. Created the Siebel Gateway Name Server.<\/li>\n
    2. Configured the Siebel Enterprise.<\/li>\n
    3. Installed the Siebel Database.<\/li>\n<\/ol>\n

      Now we need to configure the Siebel Application servers. Click on Start -> Programs -> Siebel Enterprise Server 15.0.0.0.0, and choose Siebel Server Configuration as shown below:<\/p>\n

      \"\"<\/p>\n

      \"\"<\/p>\n

      Select “Create New Configuration” and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Since we have already completed the steps, click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Type in the SADMIN username and password and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      We made a note of the Gateway Name Server name when we were configuring the Gateway Name Server. Enter the value in the Gateway Name Server Host Name field. Accept the default port and click on Next<\/strong>. Please note that the Gateway Server Service MUST be running for this to work.<\/strong><\/p>\n

      \"\"<\/p>\n

      While configuring the Siebel Enterprise, we made a note of the Enterprise name. Enter this value in the Siebel Enterprise Name field. Give meaningful names for the Siebel Server name and the description. Click on Next<\/strong> once done.<\/p>\n

      \"\"<\/p>\n

      Select the Sales Component group and click on Next. <\/strong>We can enable and disable component groups once the instance is up and running. We need to enable one of the object managers so that we can log onto the instance once the configuration is finished.<\/p>\n

      \"\"<\/p>\n

      Keep the defaults and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      We do not need to choose any specific tasks for the additional tasks. Click Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Select “Register External Oracle DB ODBC Driver” and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Since our instance is not clustered, Choose “Not Clustered” and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Do not autostart the Siebel Server Services. This is done so that we have control over the sequence in which the services are started. Click Next<\/strong> after de-selecting the option.<\/p>\n

      \"\"<\/p>\n

      As before, do not start the Siebel Server Service. Click on Next <\/strong>after de-selecting the option.<\/p>\n

      \"\"<\/p>\n

      Click on Next<\/strong> on the summary screen and wait for the execution to complete. Until now we have been connected to the Amazon Server named Siebel Web_Gateway_Server<\/strong>. We now need to connect to the other two servers (Siebel Database Server<\/strong> and Siebel_Application_Server<\/strong>) to configure the Siebel Application server on them.<\/p>\n

      Please note that we ONLY need to perform the Siebel Server Configuration steps on the remaining two servers. Pay extra caution while putting the name of the gateway name server. <\/strong><\/p>\n

      After finishing the Siebel Server configuration on all the servers we now have a complete instance, with only the Web server configuration remaining.<\/p>\n

      Creating the Logical Profile<\/h2>\n

      Log on to the Amazon server named Siebel Web_Gateway_Server.<\/strong><\/p>\n

      Click on Start -> Programs -> Siebel Enterprise Server 15.0.0.0.0 and choose Siebel Enterprise Configuration as shown below:<\/p>\n

      \"\"<\/p>\n

      \"\"<\/p>\n

      Select “Create New Configuration” and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Select “Configure a New Siebel Web Server Extension Logical Profile” and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Type in the Siebel Enterprise Name as noted earlier and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Give a path e.g. D:\\Logical_Profile<\/code> for the directory holding the profile and click Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Select “Collect Application-Specific Statistics”. While this is not required, it is advisable since Siebel is capable of identifying query times and statistics relevant to tuning the performance of the application. Since we are not using any compression, choose “None” and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Select HTTP1.1-Compliant Firewall and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Choose the defaults and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      The website name refers to the website on the web server, i.e. IIS which will hold the Siebel virtual directories. Since we are using IIS, keep the default and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Keep the defaults for the ports and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      The FQDN can be left empty. We can also fill it with the Amazon FQDN as shown in the Amazon Instances screen. Click on Next <\/strong>once done.<\/p>\n

      \"\"<\/p>\n

      Since we created only three users, use the SADMIN user for the High Interactivity User login. Type in the username and the passwords and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Select “Standard Interactivity Password Encryption” and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      For the Standard Interactivity User Name, use the LDAPUSER account. Fill in the relevant details and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Type in a value for the Siebel Enterprise Security token. Store this value in a secure place. This is the token used for encryption and communication with the Siebel servers. Click on Next<\/strong> once done.<\/p>\n

      \"\"<\/p>\n

      Keep the defaults and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Since we are using TCPIP and not TLS, choose the value and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Select “None” for TLS and click Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Click Next <\/strong>on the summary screen and wait for the execution to complete.<\/p>\n

      \"\"<\/p>\n

      Click on OK <\/strong>on the success screen.<\/p>\n

      This completes the section on creating the logical profile.<\/p>\n

      Applying the Logical Profile<\/h2>\n

      The last part in the creation of the sandbox is the application of the logical profile to complete the configuration.<\/p>\n

      Log on to the Amazon server named Siebel Web_Gateway_Server.<\/strong><\/p>\n

      Click on Start -> Programs -> Siebel Web Server Extension 15.0.0.0.0 and choose “Siebel Web Server Extension Configuration” as shown below:<\/p>\n

      \"\"<\/p>\n

      \"\"<\/p>\n

      Select “Apply an SWSE Logical Profile” and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Since we only have one server hosting the object managers and are not load balancing the application, choose Single Siebel Server. This is despite the fact that we have 3 Siebel servers installed. Click on Next<\/strong> once done.<\/p>\n

      \"\"<\/strong><\/p>\n

      Type in the hostname for the Amazon server named Siebel_Application_Server. <\/strong>Accept the default port and click on Next<\/strong>.<\/p>\n

      \"\"<\/p>\n

      Choose the folder which was created in the previous section and click on Next.<\/strong><\/p>\n

      \"\"<\/p>\n

      Click on Next<\/strong> on the summary screen and wait for the completion of the execution.<\/p>\n

      \"\"<\/p>\n

      Click on OK<\/strong> on the success screen.<\/p>\n

      This completes the configuration of the Siebel application.<\/p>\n

      Shutdown and Startup Sequence<\/h2>\n

      Before we log on to the Siebel application, we need to stop and restart the Siebel servers. The sequence in which this is performed is extremely important and is described below.<\/p>\n

      Log on to the Siebel Web_Gateway_Server.<\/strong><\/p>\n