JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for Siebel Guide

    Oracle Solaris Cluster 4.1SPARC Platform Edition

search filter icon
search icon

Document Information

Preface

1.  Installing and Configuring HA for Siebel

HA for Siebel Overview

Installing and Configuring HA for Siebel

Planning the HA for Siebel Installation and Configuration

Configuration Restrictions

Configuration Requirements

Standard Data Service Configurations

Configuration Planning Questions

Preparing the Nodes and Disks

How to Prepare the Nodes

Installing and Configuring the Siebel Application

Installing the Siebel Gateway

How to Install the Siebel Gateway on the Global File System

How to Install the Siebel Gateway on Local Disks of Physical Hosts

Installing the Siebel Server and Siebel Database

How to Install the Siebel Server and Siebel Database on the Global File System

How to Install the Siebel Server and Siebel Database on Local Disks of Physical Hosts

Verifying the Siebel Installation and Configuration

How to Verify the Siebel Installation and Configuration

Installing the HA for Siebel Package

How to Install the HA for Siebel Package

Registering and Configuring HA for Siebel

Setting HA for Siebel Extension Properties

How to Register and Configure HA for Siebel as a Failover Data Service

How to Register and Configure the Siebel Server

Verifying the HA for Siebel Installation and Configuration

How to Verify the HA for Siebel Installation and Configuration

Maintaining HA for Siebel

Tuning the HA for Siebel Fault Monitors

Operation of the Siebel Server Fault Monitor

Operation of the Siebel Gateway Fault Monitor

A.  Oracle Solaris Cluster HA for Siebel Extension Properties

Index

Verifying the Siebel Installation and Configuration

This section contains the procedure you need to verify the Siebel installation and configuration.

How to Verify the Siebel Installation and Configuration

Use this procedure to verify the Siebel gateway, Siebel server, and Siebel database installation and configuration. This procedure does not verify that your application is highly available because you have not installed your data service yet.

  1. Verify that the logical hostname is online on the node on which the resource will be brought online.
  2. Manually start the Siebel gateway as the user who will launch the Siebel gateway.
  3. Manually start the Siebel server as the user who will launch the Siebel server.
  4. Use odbcsql to verify connectivity to the Siebel database.
    # odbcsql /s siebsrvr_siebel_enterprise /u dbuser /p dbpassword

    Note - For Siebel 8.0, the data source name is DSN. Use the following command for Siebel 8.0.

    # odbcsql /s siebel_enterprise_DSN /u dbuser /p dbpassword

  5. Run list servers subcommand under srvrmgr.

    Before the Siebel server is configured to be highly available, the HOST_NAME parameter for the Siebel server shows the physical host name.

    After the Siebel server is configured to be highly available, the output from this command depends on the version of Siebel that you are using.

    • If you are using Siebel 7.7 or later, the HOST_NAME parameter for the Siebel server shows the physical host name of the node where Siebel server is running. Therefore, running this command at different times might show different names, depending on whether the Siebel server resource has failed over or has been switched over.

    • If you are using a version of Siebel earlier than 7.7, the HOST_NAME parameter for the Siebel server shows the logical host name.

  6. If you are using Siebel 7.7 or later, confirm that the serverhostaddress parameter is set to the IP address of the Siebel server's logical host name resource.
    $ srvrmgr:hasiebel> list advanced param serverhostaddress
  7. Test various Siebel user sessions, such as sales and call center using a Siebel dedicated client and supported thin client (browser).
  8. Manually stop the Siebel server as the user who started the Siebel server.
  9. Manually stop the Siebel gateway as the user who started the Siebel gateway.