Setting up Report and Notification Service
Novell Cool Solutions: Feature
By Paul Williamson
Digg This -
Posted: 11 Sep 2003
- Install RNS as per section 4 "Tracking DirXML Status" of the DirXML 1.1a documentation: "http://www.novell.com/documentation/lg/dirxml11a/index.html" (Please Note that when asked to select a Log Host you must select an object other than an NCP Server. I would recommend selecting one of the DirXML drivers or the DirXML driver set object. This object will store all of the global and module configurations for RNS and if it is removed RNS will stop working!)
- Download the patch in TID 2964958 "http://support.novell.com/cgi-bin/search/searchtid.cgi?/2964958.htm" and copy the two NLMs to the SYS:SYSTEM of the server.
- Rename SLLDAP.NLM to SLLDAP.BAK in SYS:SYSTEM because we will not be using LDAP as a reporting method
- Go to the properties of all DirXML drivers and choose the DirXML tab and select Trace Level. Set this as follows:
- This sends all errors and warnings to RNS
- If you go to the publisher or subscriber channel of a driver and select the properties and then under the DirXML Tab select Status Log. The events that are logged in this status log screen are the events sent to RNS
- Now to configure RNS we use iManager as shown in the original documentation in step 1.
- In iManager, select eDirectory Administration and Modify object. Browse to the object that you stored the RNS setting on in step 1 (Please Note that this is not the NCP Server object is must be another object e.g. a DirXML driver set object)
- Select the Report and Notification Service Tab.
- Setup a Global configuration with the settings that you want. E.g. Log file and email. Tell RNS to route for All Messages and this will use the Log Level of the driver and only send Error and Warning Messages.
- Remember paths to log files must be in the following format: sys:system/dirxml/logs/global.log
- Once your global configuration is set, then stop and start DirXML.NLM on the server.
- Then start and stop all of your drivers. This will add each driver as a module configuration in RNS.
- Go back into iManager and configure RNS through the object used in step 1. Remove all entries from the Module configurations from each driver by selecting all the red Xs except for the one next to the driver name. Then possibly add a log file name if you would like to put the events for this driver into a different log file or an email address if you want different drivers to send e-mails to different SMTP email addresses. Apply these settings.
- Either wait the default of 10 minutes for the settings to apply or stop and start DIRXML.NLM from the server console.
- If you want to see the RNS output you use DSTRACE. Turn all other DSTRACE flags off using DSTRACE -ALL then set the MISC flag using DSTRACE +MISC and you will see the RNS output as RNS:
- Read the RNS FAQ in TID 10080526 "http://support.novell.com/cgi-bin/search/searchtid.cgi?/10080526.htm" to understand how to format RNS emails through DirXML stylesheets.
- I have added an example configuration from below. The example is in XML and can be pasted into the XML tab of the RNS configuration through iManager.
<?xml version="1.0" encoding="UTF-8"?>
<email-address attachment="true" log-time="on">email@example.com</email-address>
<!-- Default sends all messages to a log file -->
<!-- Specifies the default log file name -->
<log-filename log-time="on" max-size="2048">sys:system/dirxml/logs/global.log</log-filename>
<!-- Configuration reset interval 10 minutes -->
<!-- Cache processing interval 10 minutes -->
<!-- Add module configuration elements here -->
<module name="Delimited Text Driver - SAP HR to Enterprise">
<log-filename log-time="on" max-size="2048">sys:system/dirxml/logs/sap.log</log-filename>
<log-filename log-time="on" max-size="8192">sys:system/embox/log/embox.log</log-filename>
<module name="eDir - Enterprise to Resource">
<log-filename log-time="on" max-size="2048">sys:system/dirxml/logs/resource.log</log-filename>
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com