PDA Management with IBM Tivoli Configuration Manager

Appendix A. Troubleshooting Web Gateway and Device Management 171

A good starting point is to check the swd_profile_name. log for the details of the

failure. Refer to the redbook

All About IBM Tivoli Configuration Manager Version

4.2

, SG24-6612, for more detail on tracing failed distributions.

Resource Manager problems

A general failure when trying to register the resource type could be due to a

communication failure with the Web Gateway or the Web Gateway is not

functioning. These errors should show up in the TRMRDBMS.log and

TRMResourceManager.log in the $DBDIR directory. There are also other

TRM*.log for the various components of Resource Manager on the TMR Server

under the $DBDIR directory. Review the appropriate log relating to the problem

you are encountering to further determine the cause of the problem. The logs for

the various components of Resource Manager are:

򐂰 TRMDGMAppMgr.log

򐂰 TRMDGMAppMgrUI.log

򐂰 TRMDGMDowncalls.log

򐂰 TRMDGMRegistry.log

򐂰 TRMGroup.log

򐂰 TRMGroupUI.log

򐂰 TRMRDBMS.log

򐂰 TRMResourceManager.log

򐂰 TRMResourceManagerUI.log

򐂰 TRMUserDB.log

򐂰 TRMUserUI.log

Log information can be changed by setting the variable in the Tivoli environment

(odadmin environ get/set):

TRM_DEBUG_LEVEL = (LEVEL_DBG_MIN/LEVEL_DBG_MID/LEVEL_DBG_MAX)

TRM_MAX_LOG_SIZE = log files max size

TRM_LOG_PATH = path to store log files

Tracing the Web Gateway

On the Web Gateway, locate the file traceConfig.properties file in the directory

app_server_dir/installedApps/dmsserver_hostname_DMS_WebApp.ear/dmserv

er.war/WEB-INF/classes.

To turn on tracing, change EnableTrace=false to EnableTrace=true.

The other components that need to be turned on (changed to true) are

traceEnable.dmserver and traceEnabled.twgapi.

172 PDA Management with IBM Tivoli Configuration Manager

Depending on the situation, your support representative may request turning on

tracing for the other components.

If the servlets are not running, start them to put the new trace settings into effect.

If the servlets are running, do one of the following to put the new trace setting into

effect without restarting the servlets:

򐂰 On any Tivoli Web Gateway (TWG) machine, perform the following:

server -app dmserver -trace set -host dmserver_hostname

򐂰 On any TWG UNIX machine, perform the following command:

./server.sh -app dmserver -trace set -host dmserver_hostname

򐂰 From any machine with a browser, go to the following URL:

http://dmserver_hostname/dmserver/TraceServlet?trace=set

The output files of the tracing are DMS_stdout.log, DMS_stderr.log, and

DMSMsg1.log, which are located in the app_server_dir/log directory. The default

for the Windows installation is C:\WebSphere\AppServer\log.

You should also provide the ApiServlet.log in the /tmp directory to your support

representative.