The
VSAM ESM Module can be configured from the
External Security Managers Configuration dialog box on the
Define External Security Managers page in
ESCWA:
- Enabled
- If this is unchecked, then the ESF Manager will not load, initialize, or pass requests to this Security Manager.
- Name
- Specify the name used to identify the
VSAM ESM Module.
- Module
- Specify
vsam_esm as the module.
- Connection Path
- This is the fully qualified file system path to the
VSAM ESM file directory, for example,
C:\esm_file_dir\. The default path is
%PROGRAMDATA%\Micro Focus\Enterprise Developer\vsam_esm. Some previous early-access versions of the
VSAM ESM Module used
es_esm_file_directory as the default directory name.
Note: Ensure the directories and files containing the
ESM file directory have the appropriate filesystem permissions. Operating system accounts used to run
Enterprise Server components, such as
ESCWA and
enterprise server instance, that are configured to use the security manager will need at least read access to the files. Accounts used to create and
update the files, for example, by running mfsecconv, will require write access.
On Windows platforms, both forward slashes and backslashes can be used in the connection path.
- Authorized ID
- Not used by this module.
- Password
- Not used by this module.
- Description
- Optional, specify a description of the security manager.
- Configuration Information
- See
VSAM ESM Module Custom Configuration Information for the additional configuration that can be specified.
- Cache Limit
- Not used by this module.
- Cache TTL
- Not used by this module.