Data Transformation Engine HTTP Adapter Reference Guide

HTTP Adapter Reference Guide

Chapter 5 - Troubleshooting

For information about error codes and messages returned by the adapters, see

Appendix A - Return Codes and Error Messages.

Various troubleshooting tools are available if you encounter problems using the

HTTP adapter for data sources or targets for a map. If you run a map that uses

the adapter and encounter problems or do not receive the expected results, use

the adapter trace file (.mtr) as a troubleshooting tool.

Adapter Trace File

The adapter trace file contains detailed information provided by the adapter by,

recording the actions that are taking place such as connections established and

statements executed. The trace file is produced during the adapter execution and

can be used as a debugging aid. To produce a trace file for the adapter, use the

adapter command –TRACE. The default adapter trace file name is located in the

map directory. See the Trace (-T or -TRACE) adapter command for more

information.

Sample Adapter Trace File

Mercator HTTP Adapter, Version 6.0 (560)

Built for WIN32 - INTEL on Mar 23 2000 at 13:43:07 by BocaBuild.

Mercator Command Server is 'C:\Mercator6.0\mercnt.exe'.

Retry Count is 0. Retry Interval is 0. Rollback is OFF.

Fetch Unit is 0. Burst Mode is OFF.

Run Started at 14:54:02.600 on 03/28/00.

Options used: trace,name,url

Winsock Client ID 1 enabled.

Server host is 'www.mercator.com'.

Using port '80' for the connection.

Connecting to 'www.mercator.com'.

Socket Opened.

Connected.

<GET / HTTP/1.0

User-Agent: Mercator-HTTP-Adapter/1.0.1

Content-Type: application/octet-stream

Content-Length: 0

>HTTP/1.1 200 OK (S)

(57 lines received)

Server type is 'Apache/1.3.1 (Unix) FrontPage/3.0.4.2'.

Socket Closed.

Connection closed.

Winsock Client ID 1 disabled.

Run Completed at 14:54:03.341 on 03/28/00.