The JMS Channel object stores the information the JMS driver needs to send event information to a JMS Destination.
IMPORTANT: You must restart the logging server to effect any changes in Channel object configuration. For more information on restarting the logging server, refer to the Novell® Audit Administration Guide.
The following provides a description of each Channel object attribute:
Item |
Description | |
Configuration |
||
JMS Producer Log Channel Configuration |
||
|
JMS Driver Properties File |
The JMS driver's properties file. The default properties file, jmsclient.properties, is located in the Novell_Audit_install_directory\java\logdriver\ directory.
|
|
JNDI Initial Context Factory |
The fully qualified class name of the factory class that creates an initial context. The Context Factory specifies the JNDI namespace. Refer to your JMS provider documentation for the factory class name. If you are using Novell exteNd, the value is com.sun.jndi.cosnaming.CNCtxFactory. IMPORTANT: You must install the .jar file provided by your JMS provider in the Novell_Audit_install_directory\java\logdriver directory so that Novell Audit can find the JNDI Initial Context Factory class.
|
|
JMS Connection Factory |
A connection factory is a vendor-specific, JMS administered object a client uses to create a connection to a provider. A connection factory encapsulates a set of connection configuration parameters that has been defined by an administrator. Each connection factory is an instance of either the QueueConnectionFactory or the TopicConnectionFactory interface. JMS clients typically perform a JNDI lookup of the connection factory. The connection factory is specific to a domain. However, you normally cast and assign it to a ConnectionFactory object. For exteNd, the value could be topic/connectionFactory. IMPORTANT: You must install the .jar file provided by your JMS provider in the Novell_Audit_install_directory\java\logdriver directory for Novell Audit to find the JNDI Initial Context Factory class.
|
|
JMS Destination Type |
Determines which messaging model the JMS driver uses to publish events to the JMS provider.
|
|
Destination |
The name of the topic or queue that is the target for messages the JMS driver produces and the source of messages it consumes. A JMS application can use multiple queues or topics (or both). IMPORTANT: The destination must already exist. In addition to looking up a connection factory, JMS clients typically look up a destination. Like connection factories, destinations are specific to one domain. You normally assign the destination to a Destination object. To preserve the semantics of queues and topics, however, you cast the object to a destination of the appropriate type. Creating destinations is a process that is provider-specific. Therefore, consult your JMS provider documentation to learn how to create a destination. If you are using the Novell exteNd product, the destination corresponds to the topic or queue you created using the jmqutil program, such as topic/your_Topic_Name.
|
Optional Properties for Initial Context |
||
|
JMS Provider URL |
The JMS provider's URL. It can be an IP address or other vendor-supported form. Refer to your JMS provider documentation for the provider's URL requirements. More than one URL can be specified in a space-separated list. This is an optional field in iManager, but it might be mandatory for your JMS provider.
|
|
JMS Principal |
The username required to authenticate with the JMS provider so the JMS driver can send messages to the queue or topic set up for Novell Audit messages. The format of this string depends on the JMS provider's authentication scheme. It might be a fully qualified context, depending on the namespace used. The system defaults to provider default.
|
|
Principal Credentials |
The password required to authenticate with the JMS provider so the JMS driver can send messages to the queue or topic set up for Novell Audit messages. The format of this string depends on the JMS provider's authentication scheme. it could be a password, key, certificate, or other authentication credential. The system defaults to provider default.
|
|
Maximum JMS Message Length |
The maximum size of events sent to the JMS driver which, in turn, limits the JMS message size. The default size is 3072 bytes.
|
Optional JMS Message Send Attributes |
||
|
Delivery Mode |
The mode the JMS driver uses to deliver events to the JMS provider's queue or topic.
This is dependent on the JMS provider.
|
|
Priority |
The Priority of Novell Audit messages delivered to the JMS provider's queue or topic.
|
|
Time-to-Live |
How long the message can live in the queue or topic if receivers or subscribers are down. 0=unlimited. Otherwise, the value is determined in milliseconds.
|
Other Java System Properties |
||
|
System Properties |
Any implementation-specific settings in the form of name=value pairs. Refer to your provider documentation for more information. This would be equivalent to adding the information to the properties file. If you are using Novell exteNd, you need the following:
|
Status |
By default, all Channel objects are enabled. This means that the logging server loads the Channel object's configuration in memory at startup. IMPORTANT: The Channel object must be located in a supported Channel container for the logging server to find it. See Creating and Configuring Channel Objects for more information. If you select the Disabled option, you must restart the Secure Logging Server for the setting to become effective. Thereafter, the logging server cannot load the object's configuration until you select Enabled.
|
A trademark symbol (®, , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.