This document covers the following topics:

• Tracing

• Using the Broker and RPC User ID/Password

• Using Internationalization with the DCOM Wrapper

• Setting Transport Methods for the DCOM Wrapper

---

Tracing

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

Using the Broker and RPC User ID/Password

EntireX supports two user ID/password pairs: a broker user ID/password pair and an (optional) RPC user ID/password pair sent from RPC clients to RPC servers. With EntireX Security, the broker user ID/password pair can be checked for authentication and authorization.

The RPC user ID/password pair is designed to be used by the receiving RPC server. This component's configuration determines whether the pair is considered or not. Useful scenarios are:

• Credentials for Natural Security

• Impersonation under z/OS (CICS, Batch, IMS) | z/VSE (CICS)

• Web Service Transport Security with the RPC Server for XML/SOAP, see XML Mapping Files

• Service execution with client credentials for EntireX Adapter Listeners, see Configuring Listeners

• etc.

Sending the RPC user ID/password pair needs to be explicitly enabled by the RPC client. If it is enabled but no RPC user ID/password pair is provided, the broker user ID/password pair is inherited to the RPC user ID/password pair.

With the standard wrapper property NaturalLogon (see below) sending the RPC user ID/password pair is enabled for the DCOM RPC clients. If you do so, we strongly recommend using SSL/TLS. See SSL/TLS and Certificates with EntireX.

To use the broker and RPC user ID/password

1. Specify a broker user ID and broker password in the Standard Wrapper Properties UserID and Password.

2. Set the standard wrapper property NaturalLogon to Y to enable sending the RPC user ID/password pair.

3. If different user IDs and/or passwords are used for broker and RPC, use the standard wrapper properties RPCUserID and RPCPassword to provide a different RPC user ID/password pair.

4. By default the library name sent to the RPC server is retrieved from the IDL file (see library-definition under Software AG IDL Grammar in the IDL Editor documentation). The library name can be overwritten. This is useful if communicating with a Natural RPC server. Specify a library in the standard wrapper property Library.

Using Internationalization with the DCOM Wrapper

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, and vice versa. The codepage name is also transferred to the broker to tell the broker the encoding of the data. If you want to adapt the locale settings of your Windows system, use the Regional and Language Options in the Windows Control Panel.

A DCOM Wrapper programmer can override the default Windows ANSI codepage the DCOM Wrapper uses. Use the Windows codepage number in numerical form to specify a different one, see the property Codepage in the section Standard Wrapper Properties. If a codepage is provided, it is transferred to the Broker. Use CP_ACP to send the default Windows ANSI codepage to the Broker.

Enable character conversion in the broker by setting the service-specific attribute CONVERSION to "SAGTRPC". See also Configuring ICU Conversion under z/OS | UNIX | Windows | BS2000 | z/VSE. More information can be found under Internationalization with EntireX.

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 | z/VSE.