Client for Windows User's Guide

 

This document provides instructions on installing, configuring, and using the MessageQ Client to run MessageQ applications. The MessageQ Client provides applications with the full support of MessageQ features, while using significantly fewer resources than a full message server.

 

Introduction

What is the MessageQ Client?

Benefits of Using the MessageQ Client

Architectural Overview

The Client Library Server

How the MessageQ Client and CLS Work Together

 

Installing the MessageQ Client

Installation Prerequisites

Hardware Requirements

Software Requirements

Platforms and Transports Supported

Client Platforms Supported

MessageQ Server Compatibility

Disk Space Requirements

Backing Up Your System Disk

Installing on Systems Already Running the MessageQ Client

Installing the MessageQ Client

Adding the MessageQ Client File Drive and Directory to Your Path

Uninstalling the MessageQ Client

 

Configuring the MessageQ Client

Configuring the Server Connection

Default Server

Automatic Failover Server

Configuring Message Recovery Services

Configuring Logging

Configuring Tracing

Determining MessageQ Version

MessageQ Utilities

Configuring Security Using the CLS Security Utility

Adding or Editing a Client Entry

Maintaining Modification History

Testing the Configuration Using the Test Utility

 

Using the MessageQ Client

Overview of the MessageQ Client Utilities

Developing Your MessageQ Client Application

MessageQ API Support

MessageQ Client Function Parameter Limits

Include Files for C and C++

MessageQ Client Return Codes

Byte Order Considerations for Application Developers

Sample Programs

Building C and C++ Applications

Building Visual Basic Applications

Visual Basic Sample Programs

Version 4.0 (32 bit) User-Defined Types

Running Your Application

Run-time Files

Using the MessageQ Client on Novell Networks

Managing Your Application

MRS Utility

 

Troubleshooting

Identifying Run-time Errors

Logging an Error Event

Failing to Connect to the CLS

Identifying Network Errors

Tracing PAMS API Activity

Tracing Client DLL Activity

Tracing Message Activity

Recovering from Client Crashes

Loading Incorrect WinSock DLL at Runtime

EAFNOSUPPORT Errors