User guide

Chapter 2: Security Measures
2-22
Security Measures for Event Service
Event service can be used with the following products:
• Interstage Application Server Enterprise Edition
• Interstage Application Server Standard Edition
• Interstage Application Server Plus
Unauthorized Access to Resource Files
Event service has environment definition files as listed below:
• Event Service configuration information (essystem.cfg) (*1)
• Event channel operating environment (esgrpX.grp) (*1)
• Event channel group management information (esmnggrp.db) (*1)
• Unit definition file (file with the def extension) (*1)
• Log file (ESLOG.log) (*2)
*1 For the locations where the files are stored, refer to "Backing Up and Restoring Resources" -
"Outline and Applicable Resources" in Maintenance (Resource Backup) in the Operator's Guide.
*2 For the locations where the files are stored, refer to "Messages Output by the Event Service" in
Messages Output to a Log File in the Messages.
If a unit definition file is set during unit creation (when the 'esmkunit' command is executed) for
nonvolatile operation, the following directories are maintained:
• Directory to store a transaction file specified by "trandir."
• Directory to store a system file specified by "sysdir."
• Directory to sore an event data file specified by "usedir."
These files and directories may be exposed to the threat of unauthorized access from an ill-intentioned
person.
To protect these files and directories from this threat, make these files and directories inaccessible by
end users. For this purpose, it is recommended to allow access only to users having administrator
authorization (superuser for a Solaris OE/Linux system, and Administrator for Windows(R) system).