PDA Management with IBM Tivoli Configuration Manager

Appendix A. Troubleshooting Web Gateway and Device Management 161

Common Web Gateway and Device Management

problems

Here are some typical problems when using the Web Gateway and Device

Management components.

Problems with starting the Web Gateway

The following are possible problems and solutions with starting the Web

Gateway:

򐂰

Problem:The following message appears in the DMS_stdout.log file when

Web Gateway is starting in WebSphere Application Server:

java.lang.ClassCastException

Solution: The wrong JDBC driver is being used. Web Gateway requires the

JDBC 2.0 driver. You must configure DB2 to use the JDBC 2.0 driver and

reinstall Web Gateway with the JDBC driver home installation parameter set

to the JDBC 2.0 driver.

򐂰

Problem: The following message appears in the DMS_stdout.log file when

Web Gateway is starting in the WebSphere Application Server:

DYM2794E: Failed to create the database connection pool.

COM.ibm.db2.jdbc.DB2Exception: [IBM][JDBC Driver] CLI0616E Error opening

socket. SQLSTATE=08S01

Solution: Ensure that DB2 is started and that the DB2 client is configured

correctly.

򐂰

Problem: When starting Web Gateway in the WebSphere Application Server,

the following message appears in the DMS_stdout.log file:

DYM2718E: An error occurred while trying to initialize the Policy Director

environment.

Solution: This message occurs when the IBM Tivoli Access Manager Java

Runtime Environment is not installed and configured correctly on the Web

Gateway server. Verify that the IBM Tivoli Access Manager Java Runtime

Environment is installed on the Web Gateway server.

򐂰

Problem: When starting Web Gateway on the WebSphere Application Server,

the following message appears in the DMS_stdout.log file:

DYM2719E: An error occurred while trying to create a Policy Director

context.

Solution: The Web Gateway server is not configured correctly. Open the

twgConfig.properties file to verify that the PD_ADMIN_USERID and

PD_ADMIN_PW values are correct. To verify these values, log on to the

162 PDA Management with IBM Tivoli Configuration Manager

pdadmin command-line utility on the IBM Tivoli Access Manager Server. Then

type the following:

pdadmin –a sec_master –p password

This message also occurs when the IBM Tivoli Access Manager Java

Runtime Environment is not installed and configured correctly on the Web

Gateway Server.

򐂰

Problem: When starting Web Gateway on the WebSphere Application Server,

the following message appears in the DMS_stdout.log file.

com.tivoli.pd.jutil.PDExceptionjava.io.FileNotFoundException:

pd_config_file (No such file or directory)

Solution: The Web Gateway server is not configured correctly. Open the

twgConfig.properties file to verify that the PD_CONFIG_FILE value exists on

the Web Gateway Server.

򐂰

Problem: Unable to log in to Web Gateway Server.

Solution: Do the following:

– Use the IP address instead of the host name for the Web Gateway Server

to check if it is a DNS issue.

– For a Palm OS device, check the settings in the config.ini used to create

the Config.PDB file. You can regenerate a corrected Config.PDB and

install it on the Palm device or, alternatively, modify the settings on the

device.

– If you are using a IBM Access Manager WebSEAL Server, make sure to

include the WebSEAL_hostname and junction_name in the URL for the

server.

򐂰 HTTP 400 error when connecting. Check name resolution. Make sure the

host PC can contact the Web Gateway server.

– Conduit returns an error/HTTP error code 500. Make sure the service IBM

WebSphere Admin Server 4.0 is started.

– Could not connect to the server. Check the proxy setting and port number.

The port number should be 80.

– HTTP error 404. Check the servlet name.

– Palm OS device using network/modem connection when device is

attached to host PC with a cradle. Use AttachmentOption=2 to specify that

the Palm device should always use the cradle connection. A new

Config.PDB file will need to be generated and copied to the Palm device.