Logging on as the Siebel Administrator for the first time

Now it is time to start Microsoft Internet Explorer (we will log on to a Siebel High-Interactivity application, so this is the only supported browser) and enter the following URL:

http://localhost/callcenter_enu

Note that this URL only works on the machine where the web server and SWSE are installed. It is a valid scenario for first tests. If we wish to run our first test from a Windows machine on the network, we will have to replace "localhost" with the hostname or IP address of the web server machine.

The browser will be busy for a noticeable time. As this is the first (or "cold") start of a fresh installation, the application object manager has to load the application metadata into memory. Also, the files that have to reside on the web server, such as images or stylesheets, are now synchronized from the Siebel Server's WEBMASTER subdirectory to the SWSE's PUBLIC directory. This explains the wait time.

Finally, we should see the Siebel login page rendered in the browser, which indicates that the Application Object Manager for Siebel Call Center was able to start and establish an anonymous session. The following screenshot shows the login page for Siebel Call Center loaded in Microsoft Internet Explorer:

Now we enter SADMIN as the user ID and provide the password. We can click the arrow icon or press ENTER to continue.

The Siebel Call Center application will now launch. If this is the first launch of a Siebel High-Interactivity application on this machine, we will be prompted to allow the execution of the Siebel High-Interactivity Framework. We should check the box Always trust content from Oracle USA Inc. and click Yes.

The application continues to launch. One component of the Siebel High-Interactivity Framework is the Web Client Health Check. If any of the critical browser settings are incompatible with the check rules then a dialog similar to the following screenshot is displayed:

The dialog indicates that the Sun Java Runtime (JRE) does not have the recommended version of 1.4.2 or higher and that the browser setting Access data sources across domains is not set to Enable. We can click Auto Fix to set the parameter (but not install a newer JRE). Then, we click the Run button and acknowledge the message that indicates that the Siebel applications might not work as expected.

We will cover the client-side settings in detail in Chapter 6. If problems are encountered during the first application startup, it is generally recommended to add the web server to the browser's trusted sites list.

Finally, we should see the Siebel application's home page view with a greeting message similar to the following screenshot:

We have now completed the basic steps to install a fully operational Siebel Enterprise.

If we receive an error message instead of the Siebel login page, we must check the log files of the Siebel Server and SWSE thoroughly and verify that we have completed all installation and configuration steps correctly.

Note

On your demonstration machine, launch Microsoft Internet Explorer and navigate to http://localhost/callcenter_enu in order to verify the successful installation of the Siebel Enterprise. Depending on your machine and browser settings, you might receive warnings and messages. However, you should be able to log in as the Siebel Administrator (SADMIN). In the case of errors, you should review the log files and validate the previous steps and processes.