How to set up the Nsure Audit MySQL Channel
(Last modified: 15Nov2004)
This document (10091164) is provided subject to the disclaimer at the end of this document.
How to set up the Nsure Audit MySQL Channel
Novell Nsure Audit 1.0
Novell Nsure Audit 1.0.1
This procedure can be done from WebAdmin:
- Go to the Logging Services Container, and create a new object, for object type select Nsure Audit MySQL Channel.
- When prompted for the name, provide the name, and continue.
- When the object details screen appears, the configuration should be displayed, all values will be blank.
- Under the Host Section, fill in the following values: Host should be the IP address of the MYSQL server, OR localhost is the MySQL database is running on the same server as the SLS; User should be populated with the username supplied during the account configuration (click here for MySQL server configuration instructions); Password should contain the password created during the user account creation.
- In the Database section, the following values should be provided: Name is the name of the database created to store Nsure Audit records (example naudit); Table can be any value, most configurations will use the name 'log'.
- Refer to the Nsure Audit Documentation for the Advanced Options.
- If you want to use the MySQL channel as the primary log channel for the Secure Logging Server, you need to make this change on the SERVERNAME Logging Server object in the Logging Services container. The Log Channel needs to point to the MySQL channel, and not the file channel. Without specifying the MySQL channel as the log channel on the SLS, or creating a Notification object to send data to the MySQL channel, the MySQL channel will not receive any information.
This procedure can also be done from iManager:
In iManager, expand the Nsure Audit task, and select Server Configuration.
Click on the channels tab.
Click the check box next to the Channels container, and then click New.
Create a channel of type MySQL. Any name will be fine.
When returned to the channels container screen, click the check box next to the MySQL channel under the channels container, and then click edit.
When the edit MySQL channel screen appears, fill in the following information. ALL FIELDS ARE CASE SENSITIVE!
Host: IP address of the server running MySQL.
If MySQL is installed on the same server as the logging server, and the account created to access the Nsure Audit databse is auditusr@'%', then this should be the logging servers IP address.
Password: Password for auditusr@'%'
Advanced Create Table Options: Blank
SQL Expiration Commands:
create table newtable ($T) $e;RENAME TABLE $l TO l$n, newtable TO $l
This script does the following:
Creates a new table using the CREATE TABLE Options.
Renames the current table so it includes the date and time in decimal.
Renames the new table with the default table name.
Expire at time or interval: Mondays
This means that the expiration script will run at every Monday at Midnight.
Click apply, then close.
Click on the General Tab (general tab of Logging Server object)
In the Log Channel Field, use the magnifying glass to browse for the MySQL channel that was just created (example, mysql.Channels.Logging Services) - This tells the logging server to send all data to the MySQL channel.
Click Apply to save the changes.
Test the configuration:
From the server console load lengine -d.
If the Nsure Audit 1.0.1 console loads, then everything is configured correctly. If it does not load, check the Logger Screen on the Netware Server for error messages. Double check your accounts created for MySQL. Was the user created auditusr@'%' or was it auditusr@localhost? Does case match for the username and password. Is MySQL loaded? If you created auditusr@localhost but not auditusr@'%', then it is necessary to change the address on the MySQL channel to be 127.0.0.1. Based on the experiences from Technical Support, it is best to use auditusr@'%'.
If everything is configured correctly, continue the installation process..
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
- Document ID:
- Solution ID: NOVL95434
- Creation Date: 12Feb2004
- Modified Date: 15Nov2004
- NovellManagement Products
Did this document solve your problem? Provide Feedback