Red Hat NETSCAPE DIRECTORY SERVER 6.01 - DEPLOYMENT Installation Guide download pdf (Page 69)

CHAPTER 15

Configuring Message Server as a Standalone Node

The command runserver -node <nodename> also helps in creation of a new node.

Understanding Message Server Configuration

All the above operations can be performed by changing the default configurations in the JMS

configuration file jms-config.xml. This section provides an overview of how the configuration file

can be modified for configuring a standalone Message Server.

Configuring Large Message Handling

A JMS message is termed as ‘large message’ when the message exceeds the maximum size that the

server can handle. This maximum size is configured on each destination separately. The maximum

size of the message is specified through the following tag under each destination.

<max-message-size-kb>50</max-message-size-kb>

Also, you can specify the action for the Server, when the message exceeds the maximum size. by

configuring the <message-size-overflow-policy> value as follows:

<message-size-overflow-policy>

handle-with-persistence

</message-size-overflow-policy>

The value can be either be ‘handle-with-persistence’ or ‘throw-exception’.

If the policy is ‘handle-with-persistence’, when the sender sends a large non-persistent message, then

the server will override its delivery mode from persistent to non-persistent and continue sending the

message to the receiver. If the policy is ‘throw -exception’, then when the sender sends large message,

The default max-message-size-kb is 50 kb. The default value for the over flow policy is ‘handle-with-

persistence’. The maximum size of each message that will be kept in memory can be configured

using the max-message-size-kb property:

<max-message-size-kb>50</max-message-size-kb>

All the above mentioned default values can be changed in <default-destination-properties> of

<admin-params>.

If you don not specify the max-message-size-kb at destination, then the destination will take the

value that is specified at default-destination-properties. For temporary destinations you cannot

configure separately. It will take the value which is specified in the default-destination-properties.

Configuring JMS Persistence Framework

JMS Message server requires a local store for storing its persistent messages. The messages can be

persisted in two ways:

1 Database.

2 File System.

1 2 ... 64 65 66 67 68 69 70 71 72 73 74 ... 142 143

No comments

Red Hat NETSCAPE DIRECTORY SERVER 6.01 - DEPLOYMENT Installation Guide Page 69