Version 9.6
 —  EntireX DCOM Wrapper  —

Writing Applications with the DCOM Wrapper

This document covers the following topics:


Tracing

There are several possibilities to trace the DCOM Wrapper. For details, see Tracing webMethods EntireX under UNIX | Windows | BS2000/OSD | z/VSE.

Top of page

Using Internationalization with the DCOM Wrapper

It is assumed that you have read the document Internationalization with EntireX and are familiar with the various internationalization approaches described there.

The DCOM Wrapper uses by default the Windows ANSI codepage (CP_ACP) to convert the Unicode (UTF-16) representation within BSTRINGS to the multibyte or single-byte encoding sent to/received from the broker. This codepage is also transferred as part of the locale string to tell the broker the encoding of the data if communicating with a broker version 7.2.x and above.

If you want to adapt the Windows ANSI codepage refer to the Regional Settings in the Windows Control Panel and your Windows documentation.

The following applies to the property codepage:

If communicating with a Broker version 7.1.x and below and if no locale string is provided by the DCOM Wrapper programmer, an administrator can force a locale string to be sent with the environment variable ERX_CODEPAGE.

When setting the codepage with the environment variable ERX_CODEPAGE:

Example:

ERX_CODEPAGE=LOCAL

Top of page

Setting Transport Methods for the DCOM Wrapper

The procedure for setting the transport methods and timeout for the EntireX DCOM Wrapper is the same as for the Broker stubs.

See Transport Methods for Broker Stubs under z/OS | UNIX | Windows | BS2000/OSD | z/VSE | z/VM.

Top of page