For usage tracking to occur, you need to make sure the UsageServer process is running. If the UsageServer process is not installed, or for information about configuring the process, refer to Managing the Maintenance and UsageServer Processes .
In addition, the Maintenance process also needs to be running. If the UsageServer becomes unavailable, the Maintenance process closes the usage records for any applications that were being tracked. Even if the users continue to use the applications, they are only charged for the time up to the point that the UsageServer became unavailable. This ensures that they will not be charged for time they did not use.
To start the UsageServer process:
At the NetWare® server console, enter usageserver.ncf.
or
At the Windows server command prompt, change to the directory where the Usage Server was installed (by default, \ondemand\bin), then enter usageserver.bat.
Enter the password for the Admin or Admin-equivalent user that the Usage Server will use to authenticate to Novell eDirectoryTM through the LDAP server.
If you can't remember which user is being used for authentication, the user's context is stored in the commerceserver.cfg file, located in the \ondemand directory.
You can install additional UsageServer processes or change the default configuration for this process. For information, see Managing the Maintenance and UsageServer Processes .
At the NetWare server console, enter commercemaintenance.ncf.
or
At the Windows server command prompt, change to the directory where the Maintenance process was installed (by default, \ondemand\bin), then enter commercemaintenance.bat.
Enter the password for the Admin or Admin-equivalent user that the Usage Server will use to authenticate to eDirectory through the LDAP server.
If you can't remember which user is being used for authentication, the user's context is stored in the commerceserver.cfg file, located in the \ondemand directory.
You can install additional Maintenance processes or change the default configuration for this process. For information, see Managing the Maintenance and UsageServer Processes .