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.