G.0 Using JMS with Novell Audit

The following procedure outlines the steps required to configure the JMS channel driver.

  1. Install a JMS Provider such as the Novell exteNd™ Java Messaging Platform.

  2. Copy the .jar files required for additional Java channels you are using with Novell Audit to the Novell Audit Java classpath or a subdirectory thereof.

  3. Configure the data store.

    1. Install a storage database supported by your JMS Provider.

      For example, if you are using the Novell exteNd Java Messaging Platform, install MySQL.

    2. Create a database for Novell Audit event data. For example, nauditDB.

    3. Create the required database tables for Novell Audit event data.

      If you are using MySQL, execute the dbinit -create command.

  4. If it was not installed with your JMS Provider, install the Java 2 Platform v1.4 Enterprise Edition (J2EE*).

    J2EE provides the JMS interface required by all the JMS components—that is, the JMS Producer driver, the JMS provider, and the JMS Consumer application.

  5. Provide the required classpath settings.

    If you are using Novell exteNd Java Messaging Platform, add the following to the classpath:

    • mp-jms.jar

      This file is located in the exteNd_install_directory/mp/lib directory.

    • mysql-connector-java-version-bin.jar

      This file is part of the MySQL installation. If you installed MySQL with the Novell exteNd Java Messaging Platform, the file is exteNd_install_directory/MySQL/jdbc/mysql-connector-java.3.0.10.stable-bin.jar .

    • NAuditDriver.jar

      This file is part of the Novell Audit installation.

  6. Provide the required PATH settings.

    • If you are using Novell exteNd Java Messaging Platform, add the following directories to the PATH:
      • exteNd_install_directory/mp/bin/win32
      • j2ee1.4.2sdk/bin
      • j2ee1.4.2skd/jre/bin/server
    • If you are using the JMS Channel on a Windows machine, add the jvm.dll directory path to the Path system variable. For example, c:\j2sdk1.4.2_09\jre\bin\server\. You must reboot the machine for the changes to take effect.
    • On Linux/Solaris, the LD_LIBRARY_PATH variable needs to point to the paths for libverify.so, and libjvm.so. You must reboot the machine for the changes to take effect.

  7. Configure the JMS Provider.

    If you are using Novell exteNd Java Messaging Platform, edit the exteNd_install_directory/mp/lib/msgsvc.properties file and define the following properties:

    • msgsvc.name=JMQ0 (This value ends in a zero.)
    • msgsvc.port=53506
    • msgsvc.logdir=log_directory

      For example, msgsvc.logdir=c:\\exteNd5\\MP\logs

    • msgsvc.store=MySQL
    • msgsvc.jdbc.driver=com.mysql.jdbc.Driver
    • msgsvc.jdbc.url=jdbc:mysql://localhost:3306/Novell_Audit_database_name
    • msgsvc.jdbc.user=administrator_account
    • msgsvc.jdbc.password=administrator_account_password
    • msgsvc.jdbc.minpoolsize=10
    • msgsvc.jdbc.maxpoolsize=20

  8. Start the JMS Provider service.

    If you are using Novell exteNd Java Messaging Platform, execute jmqserv. You can set the -debug and -verbose options to view the system connections, identify problems, and track actions as they are happening. The syntax is as follows:

    jmqserv -debug -verbose

  9. Create the required topics and queues.

    If you are using Novell exteNd Java Messaging Platform, run the following commands to create topics and queues:

    jmqutil [-verbose] -createTopic Topic_name

    jmqutil [-verbose] -createQueue Queue_name

    Run dbinit -info to show all the topics and queues.

    Run dbinit -info Topic_name|Queue_name to view information about a specific topic or queue.

  10. Copy the mp-orb.jar and mp-jms.jar files to the Novell Audit install location.

    If you are using Novell exteNd Java Messaging Platform, these files are located in the exteNd_install_directory/mp/lib directory.

    The mp-orb.jar and mp-jms.jar files contain the JMS Provider’s client-side JMS implementations. (Every JMS Provider has its own implementation of the JMS interface.) The Novell Audit JMS driver uses this information to map event information into JMS messages.

  11. (Optional) Build and run the sample Producer and AsyncConsumer JMS client applications as stand-alone Java applications to ensure the property settings for JNDI, JMS Messages, and the JMS Provider are correctly configured.

    1. Edit the CLASSPATH settings in both the buildTest.bat and run.bat files for your system.

    2. Execute the following sample consumer:

      run aconsumer [debug] topic|queue destination [browse]

      For example, run aconsumer topic topic/nauditTopic waits for messages to appear on the specific topic it has subscribed to.

      Execute run aconsumer -? to display command help.

    3. On a separate console window, execute the sample producer:

      run producer text count=n

      For example, run producer test count=8 topic topic/nauditTopic sends eight test messages to the topic. If the consumer is running, it will receive the eight test messages.

      Execute run producer -? to display command help.

  12. Configure the JMS Channel object. For more information, see Section 6.8.2, JMS Channel Object.

  13. Start the JMS client consumer application.

    It should be waiting for JMS messages.

  14. Start the Secure Logging Server, lengine.

  15. Check the Novell Audit log files for status (jmsProd.log), or check the consumer status.