Enter the property
name and value. For
the sample, enter the following two properties. It is assumed that
the users.props file and the groups.props file
are in the customer_sample directory under the
product installation directory. You can place these properties in
any directory that you choose and reference their locations through
custom properties. However, make sure that the directory has the appropriate
access permissions.
Table 1. Additional properties. This table lists additional custom properties when configuring
stand-alone custom registries.
Property name |
Property value |
usersFile |
${USER_INSTALL_ROOT}/customer_sample /users.props |
groupsFile |
${USER_INSTALL_ROOT}/customer_sample /groups.props |
Attention: The
QEJBSVR user
profile must have Execute (*X) authority for the directory that contains user.props and groups.props files.
Additionally, QEJBSVR must have Read and Execute (*RX) authority for
the user.props and groups.props files.
Samples
of these two properties are available in users.props file and groups.props file.
To use the users.props and
the groups.props files on the z/OS® platform,
save these files in the ASCII format before calling them from the
administrative console.
The Description, Required,
and Validation Expression fields are not used and can remain
blank.
In a WebSphere Application Server, Network Deployment environment
where multiple WebSphere Application Server
processes exist, such as cell and multiple nodes in different machines,
these properties are available for each process. Use the USER_INSTALL_ROOT relative
name to locate any files, as this name expands to the product installation
directory. If this name is not used, ensure that the files exist in
the same location in all the nodes.
WebSphere Application Server version 4-based
custom user registry is migrated to the custom user registry based
on the com.ibm.websphere.security.UserRegistry interface.