The Maintenance process cleans up purchase and usage records in eDirectory and closes out usage tracking of applications when the UsageServer becomes unavailable. It needs to be running at all times.
The UsageServer process enables application usage to be tracked. It needs to be running if you want to be able to charge for an application based on the number of times or minutes it is used.
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 .
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 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 UsageServer processes or change the default configuration for this process. For information, see Managing the Maintenance and UsageServer Processes .