Installation guide
57
CHAPTER 15
Configuring Message Server as a Standalone Node
Stopping Standalone Message Server
To stop a connected Standalone Message Server, click ‘Stop Server’ on the Console. To exit from
the Console, click ‘Logout’.
In the Server Administration Service Home page, the ‘Connect’ option changes back to ‘Start’.
Note: You must refresh the main page to verify the status.
Removing Standalone Message Server
You can remove a Standalone Message Server only if it is not running. To remove a server:
1 On the Server Administration Service Home page, select the server that is to be removed.
2 Click ‘Delete’.
Using Loaded Send Queues
Loaded Send operation in Pramati Message is used in situations where there is a fast sender and a
slow receiver. Normally, messages are kept in-memory. If the number of messages that are sent are
increased, this may increase the memory usage infinitely. There are two ways to overcome this
limitation:
• Setting Max Queue Size based on the application activity
•Loaded Send
Setting the max queue size to the maximum possible value based on the activity of the application
however has its disadvantages. Here the client cannot send messages beyond the maximum size
specified, in case messages cross the max limit.
To overcome this, the loaded send queues can be used. In the next section we will discuss how to
configure the Message Server for loaded queues.
Configuring the Message Server for Loaded Queues
The following components are required to configure the Message Server for loaded queues.
• A properties file
• A temporary store for storing messages in a database table
The loaded send feature uses a property file (loadedsend.props) where the maximum and
minimum number of messages that can be maintained are specified. This file can be placed
anywhere. The server should be started with the following system property specifying the path to the
properties file:
-Dcom.pramati.loadedsendprops = <path>/<to>/<the>/<loadedsend.props file>
Here is how the loadedsend.props property file looks:
queues=JMSQueue,SellQueue
minruntimesize=100
maxruntimesize=2000