Goals To install and configure the Siebel Developer Web Client Time 25 – 30 minutes
Instructions:
In this practice, you will install the Siebel Developer Web Client, and confirm that you can connect to the Siebel database whether or not the Siebel Server is running. You will then examine the configuration file to see how to set various connection options.
Note: You are installing the Developer Web client at this point to help you debug any later
configurations. The Developer Web client is an extremely useful tool in dealing with misconfigured enterprises. However, if you do not complete this practice, it will not affect future practices.
1. Install the Siebel Developer Web Client:
a. Using Windows Explorer, navigate to
D:\labs\8.1_Install\Installers\Client\Siebel_Web_Client\Disk1\install
b. Double-click oui.exe. Note that this is not the same as the setup.exe executable you have run for every other installer so far.
c. Click Next on the Welcome screen.
d. Enter the installation parameters below, clicking Next to proceed through the installation:
Parameter Value Purpose
Name Siebel_Web_Client_81 Name of the Program Folder containing the shortcuts.
Path D:\OUClient Location in which to install the files.
Product-Specific
Prerequisite Checks Next Click Next. Click Yes to proceed through the warning; it is generated because you do not have Microsoft Word installed on your classroom
machine.
Oracle Internal & Or acle Academy Use Only
Database Alias SIEBELDB Connection information for contacting the database; in this case, the connection string already created for the Oracle database.
Table Owner SIEBEL Used to read database schema.
File System Server D:\siebfile Used to read data from the enterprise’s Siebel File System. See the note below with regards to using an absolute file path.
Siebel Remote Server localhost Used for synchronization with a Siebel Server, if desired. See the note below with regards to using localhost.
Gateway Name
Server Address localhost Used to connect to the Siebel Gateway Name Server. See the note below with regards to using localhost.
Enterprise Server
Name OUEnt Used to collect enterprise information.
Request Server Name OUSrvr The name of a Siebel Server on which the Server Request Broker component is running.
Search Server
Hostname localhost Location of the search server, if any. Since there is no search server, leave this value at its default.
See the note below with regards to using localhost.
Search Server Port
Number 2048 Leave this at its default.
Summary Screen Install Click the Install button.
Note: You would normally use machine names rather than localhost on these machines, as well as a network file path. In the classroom environment, your machine name has been added to the Trusted Sites list, which hides some of the client behavior you would see in a production environment. By using localhost rather than machine name, you see this behavior.
e. During installation (after around 1-2 minutes), the installer invokes an instance of Internet Explorer in order to download the required ActiveX controls for the Developer Web client.
Dismiss any warnings and allow the download to complete.
Note: You may see a yellow bar at the top of the window warning you about blocked content.
Right-click the bar and select Allow Blocked Content, then click Yes. After that, you may be asked whether to install Outlctrix.cab. Clck Install.
f. Once the Internet Explorer window indicates that the download is complete, close Internet Explorer and return to the installer window. The installer should continue running.
g. Once installation completes, click Exit and then click Yes.
h. If necessary, in the Finish Admin Install dialog box click Next and then click Finish to dismiss it.
2. Create a new Developer Web Client shortcut to use uagent.cfg, the Siebel Call Center
configuration file. This allows you to compare the Developer Web Client version of Siebel Call Center with the Web client version you have been using in the rest of this class.
a. Select Start > Programs > Siebel_Web_Client_81 > Siebel Web Client 8.1, but do not select any application.
Oracle Internal & Or acle Academy Use Only
Lesson 6: Installing the Siebel Developer or Mobile Web Client
b. Right-click a convenient application such as Siebel Oil, Gas & Chemicals - ENU and select Send To > Desktop.
c. Select the desktop and locate the new shortcut.
d. Right-click the shortcut and select Properties.
e. Under the Shortcut tab, in the target field, scroll to the left to change the beginning to D:\OUClient\BIN\siebel.exe /c D:\OUClient\bin\ENU\uagent.cfg. This should only involve changing the name of the configuration file to uagent.cfg.
f. Click the General tab.
g. Change the name of the shortcut to Siebel Call Center - ENU.
h. Click OK.
Course Note: This shortcut is also provided in D:\labs\8.1_Install\Solutions\DeveloperWebClient.
i. Double-click the Siebel Call Center - ENU shortcut. Notice that this login screen includes a Connect To field. This field allows you to select which database the Developer Web client connects to. By default, you can select a Local, Sample, or Server database. You can add additional data sources by editing the application configuration file.
Oracle Internal & Or acle Academy Use Only
l. If necessary, click Auto Fix in the Browser Health Check and then click Run.
3. Compare the functionality of the Developer Web (thick) client with the Siebel Server and Gateway Name Server running and stopped:
a. Navigate to Administration - Server Management > Enterprises:
i. Click the Site Map icon near the top of the screen.
ii. Scroll down and click the Administration - Server Management link.
iii. Click the Enterprises link.
b. Note that you can monitor and administer servers from within the thick client, as the Siebel Server is available for administration. In particular, note that the Server is shown and its state is Running.
c. In Microsoft Windows, return to the Services window and stop the Siebel Server [OUEnt_OUSrvr] service.
i. Right-click the Siebel Server [OUEnt_OUSrvr] service and select Stop.
Note: Because of the heavy load on your classroom machine, you may receive a message that the service could not be stopped in a timely manner. This is harmless;
click OK to dismiss the warning and proceed with the practice.
ii. Minimize the Services window.
d. Return to the thick client and click the Accounts tab. Note that you can continue to navigate through the application even though the Siebel Server is not running.
e. Click the My Accounts link. Notice that there are no account records in the server database.
f. Click the browser’s Back button until you return to the Administration - Server Management
> Enterprises view. Notice that you can still access this view, but that the Siebel Server is listed as unavailable. (Most likely because the handshake failed).
g. Select Help > Technical Support. Notice that the connect string to the enterprise database is SIEBELDB, the Oracle SQLNet connect string you provided when installing the Siebel Enterprise. The enterprise uses both ODBC and direct (native) connections to the database, depending on the situation. For example, for authentication it uses the ODBC connection.
h. Close the Technical Support dialog box.
i. In Microsoft Windows, return to the Services window.
j. Stop the Siebel Gateway Name Server service.
k. Minimize the Services window.
l. Return to the thick client.
m. Click the Contacts tab. Note that you can continue to navigate even without the gateway name server service. The thick client connects directly to the server database, bypassing the Siebel Server and Siebel Gateway Name Server.
n. Click the browser’s Back button to return to the Administration - Server Management screen.
This time the screen returns an error. The gateway name server must be available in order to use this screen.
o. Log out of the thick client.
i. From the application-level (blue) menu, select File > Log Out.
Oracle Internal & Or acle Academy Use Only
Lesson 6: Installing the Siebel Developer or Mobile Web Client
4. Examine the Siebel Call Center configuration file to learn about the customizations available for the Developer Web Client:
a. Use Notepad to open D:\OUClient\BIN\ENU\uagent.cfg. This is the configuration file for Siebel Call Center.
b. Examine the [Siebel] section. It includes overall parameters such as ODBC data source names (the ODBC connections are created by the installer), application title, and so forth.
The only parameter that is frequently edited in this section is EnableFQDN; by default, the Developer Web Client uses an address of the form <machine name>.<full domain name>, where the <domain name> is specified by the FQDN parameter. Setting EnableFQDN to FALSE causes the Developer Web Client to use localhost instead.
c. Examine the [InfraSecMgr] section. This determines the security adapter used by the Developer Web Client. The [DBSecAdpt] and [LDAPSecAdpt] sections farther down in the file provide connection information for the security adapter. Note that the [DBSecAdpt]
section is populated by the installer; the [LDAPSecAdpt] section must be manually edited to enable LDAP authentication for the Developer Web Client.
d. Examine the [Datasources], [Local], [Sample], and [ServerDataSrc] sections. These frequently-edited sections determine how the Developer Web Client connects to various data sources. You may add custom data sources here by creating a new datasource entry and another datasource section.
e. Close uagent.cfg, not saving any changes.
5. Using Windows Explorer, navigate to D:\OUClient\OBJECTS\ENU. This directory contains the Siebel repository file (.srf) used by the Developer Web Client. Recall that this is a compiled, compressed version of the Siebel Repository, and contains the object definitions defining the business logic and appearance of the application.