Help banner

Creating and Configuring Application Objects

Applications that log to or request information from Nsure Audit are represented in eDirectory by an Application object. Application objects store the information the logging server needs to authenticate logging applications. They also identify which users have rights to monitor the application’s events, and they store the application’s log schema.

NOTE: For more information on the authentication process and monitoring an application's events, see the Novell Nsure Audit Administration Guide.

In addition to facilitating system authentication and monitoring, Application objects store the application’s log schema. The log schema catalogs the events that may be logged for a given application. For more information, see Log Schema Files.

Application objects can only be created within Application containers. Application containers provide a reference point through which the logging server can locate Application objects. At startup, the logging server scans its list of Application containers and loads the included Application object configurations in memory where it can quickly access the information when authenticating applications.

The Application container under Logging Services is automatically created during installation; however, additional Application containers may be created anywhere in the tree.

IMPORTANT: The logging server only loads the Application object configurations that are located in supported Application containers. Therefore, if you create a new Application container or Application object, you must ensure the Application container is included in the logging server’s Application container list.

 

Creating Application Objects

Application objects are automatically created when an Nsure Audit-enabled application is installed into your tree.

NOTE: The Application objects for the eDirectory and NetWare Instrumentations are automatically created when Novell Nsure Audit is installed.

If necessary, Application objects may also be manually added to the tree through the Log Applications screen in the logging server's Server Configuration task. If you manually create the Application object, you must have the product’s Application Identifier and the Application ID. While these should be available in the product’s documentation, they are also included in the product’s Log Schema file.

To create a new Application object,

  1. In the Container list, checkmark the box next to the Application container in which you want to create the Application object. If the container you wish to use is not listed, you can add the Application container.

  2. Click New Application. The New Log Application menu appears.

  3. Type a name for the object in the Log Application Name field, and enter the path to the log schema file (.lsc).

  1. Click OK to create the Application object.

After the Application object is created, you must configure the object.

 

Configuring Application Objects  

Application objects can be configured from the Log Applications screen in the logging server's Server Configuration task.

To configure an Application object,

  1. In the Container list, checkmark the box next to the Application object you want to configure. If the Application object isn't visible, click the plus icon next to the object's Application container to expand the object list.

  2. Click Edit Application. The Modify Object menu for that application appears.

Modify Object menu

Configuration

 

 

Application Identifier

The name the logging application uses to identify itself to the logging server.

The Application Identifier is stored in the application’s certificate.

The Application Identifier is also part of the Component string for every event logged from the current application. For more information, see Event Structure.

This field is automatically populated when the Application object is created during install. If you manually create the Application object, you can find the Application Identifier in the application’s Log Schema file. For more information, see Log Schema Files.

 

 

Application ID

The four digit hex value assigned to the current application.

All Application IDs are assigned through Novell Developer Support and are maintained in the Nsure Audit central registry.

The Application ID is also part of the Event ID for every event logged from the current application. For more information, see Event Structure.

This field is automatically populated when the Application object is created during install. If you manually create the Application object, you can find the Application ID in the application’s Log Schema file. For more information, see Log Schema Files.

NOTE: The logging server uses the Application ID to manage Access Control. The users designated in the Access Control field can monitor all events containing this Application ID.

 

Access Control

The users that have rights to monitor the current application’s events. For more information, see the Novell Nsure Audit Administration Guide.

Click the Object Selector button to select User objects in the directory tree. You may also click the Object History button  to select User objects from a list of objects selected during this iManager session.

 

Status

By default, all Application objects are enabled. This means that the logging server loads the Application object’s configuration in memory at startup.

If the Application object is disabled, the logging server does not load that object’s configuration at startup.

IMPORTANT: The Application object must be located in a supported Application container in order for the logging server to find it.

 

  1. When finished modifying the Application object, click OK.

IMPORTANT: The logging server loads the Application object configurations from its supported Application containers at startup. Therefore, if you modify an Application object, you must restart the logging server for the changes to take effect. For information on restarting the logging server, refer to the Novell Nsure Audit Administration Guide.

For more information on Application containers, see Adding and Removing Application Containers.
For more information on the logging server, see Configuring the Secure Logging Server.
For more information on using Nsure Audit, see Nsure Audit Help.

A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For information on trademarks, see Legal Notices.