Using a Repository with Application Messaging

The common messaging interface enables you to store information about message queues in either the local SAS registry or a distributed Lightweight Directory Access Protocol (LDAP) repository or a combination of both. The information that can be stored and retrieved include the following:

Transport alias

is an alias name that describes a transport (MQSeries (refers to WebSphere MQ), MSMQ, Rendezvous, or Rendezvous-CM)

Queue alias

is an alias name that describes a transport and queue

Dynamic queue model

is a model name that describes a queue's properties

Transport model

is a model name that describes a Rendezvous or Rendezvous-CM transport

Data map description

is a map name that describes the format of data within a message.

Placing this type of information in storage provides both reusability and encapsulation. A repository can contain all queue definitions, thereby enabling you to focus on the application usage rather than the specific definition of a queue. By using an LDAP Server repository, you can access queues across your network, including queues defined by other users.

The SAS registry provides methods for defining your own queues or overriding globally defined queues. It provides you with complete control and flexibility over a queue. You might be required to use the SAS Registry if LDAP services are not available on your network.

If you are using both the SAS registry and an LDAP server, the local SAS registry is searched first. If the required information is not found, the distributed LDAP server is searched.

To bypass the SAS Registry altogether, specify the following macro variable:

%let REGISTRY_BYPASS=1.

Please see the following sections for more information about using a repository with application messaging:

• Using the SAS Registry with the Common Messaging Interface
• Using an LDAP Server with the Common Messaging Interface