With indirect messaging, two or
more applications communicate
with each other indirectly using message queues. Therefore, the applications
do not have to be running at the same time. The data is sent in the form of
a message and is saved on a message queue until the receiving application
is ready to fetch it. As a precaution, messages are written to disk. Therefore
even if your queue terminates, the application can retrieve its messages.
A typical server application that uses
indirect messaging would execute the following steps:
- Initialize the messaging environment.
- Check queue(s) for
any messages.
- Respond to messages when required.
- Repeat steps 2 and 3 as
needed.
- Shut down the messaging environment.
A typical client application that uses
indirect messaging would execute the following steps:
- Initialize the messaging environment.
- Locate the
collection manager.
- Establish communication with queue(s).
- Send or receive messages from an opened
queue(s).
- Repeat steps 3 and 4 as desired.
- Release queue(s).
- Shut down the
messaging environment.
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
