Bookshelf Home | Contents | Index | Search | PDF

Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Preparing for Implementation on the DB2 Host >

Verifying Network Connectivity Under Windows

---

Before you install the Siebel Database Server, verify your ability to connect to the database across the network.

Verifying the Connection to the Database

Use the Client Configuration Assistant to verify the connection to the database with DB2 Connect.

To verify the connection to the database using the Client Configuration Assistant

Launch the Siebel application and choose the database alias, then click test.

The Connect to DB2 screen appears.

Type the user ID and password assigned to you for this database and click OK.

The following message indicates a successful connection:

The connection test was successful.

Verifying the Connections to the Siebel Gateway, Database Server, and Siebel File System

Use the DB2 Command Window to verify network connectivity to the Siebel Gateway, Database Server, and Siebel File System. In the example below, the command syntax is appropriate for the DB2 Command Window only. It does not work in the DB2 Command Line Processor.

To verify network connectivity using the DB2 Command Window

Use a DB2 Command Window to verify connectivity to the database.
Choose Start >Programs >IBM DB2 >Command Window, and type the following command:

DB2 connect to database_alias user user_ID using password

where user_ID is a valid user name on DB2, and password is the appropriate password for that user name.

If the connection is valid, you receive the following message:

Database Connection Information
Database Server = DB2/NT x.x.x
SQL authorization ID = SADMIN
Database alias = NAME

If the connection is not valid, verify the configuration.

To close the connection, enter the following command:

db2 terminate

NOTE:  You can also use the DB2 Command Center GUI tool to close the connection.

The Siebel Server installation creates its own ODBC data source.

Provide a network connection from the Siebel Server to the Siebel File System, using one of the two following methods:
Use a universal naming convention (UNC) share.

For UNC shares, the syntax is \Siebel_Server\sharename.

Connect a shared network drive or device.

You might elect to map a drive letter (for example, K:\) on the computer that is mapped to the Siebel File System directory.

CAUTION:  If this method is used, the drive letter must be permanently mapped to the Siebel File System, and the same drive letter must be mapped on all machines that support a Siebel Server. For this reason, it is recommended that you use a UNC sharename, rather than a shared drive, to connect to the Siebel File System.

Check that the Siebel File System directory is visible and that the Siebel Service Owner Account or Resonate Manager Account can copy files to and from it.

Network connectivity to the Siebel Gateway, Database Server, and Siebel File System is now verified.

The preceding commands should result in the display of the application version and any comments. The display should also indicate whether connectivity through the call-level interface (CLI) layer was set up correctly. Error messages at this point indicate that problems exist downstream from the CLI layer to the database, or that problems exist in the user and password combination or SSEROLE privileges for that user.

Bookshelf Home | Contents | Index | Search | PDF