web server - Borland Technical Publications

Security management with the Security Map
where:
-rolename
-username
-password
-vaultfile (optional)
-vpwd (optional)
Resource role name to store in the resource vault.
Resource username to associate with the resource role.
Resource password to associate with the resource role.
Path to the vault file you write the resource role(s) to. If not
specified, ResourceVaultGen will attempt to write to the
default resource vault file . If the vault file is does
not already exist, a new vault file will be written to the
specified location.
Password to assign to the vault for access authorization. If
not specified, the vault will be created without a password.
Note
When using ResourceVaultGen, ensure that the following jars are in your
CLASSPATH:
■
■
■
■
■
■
■
■
■
■
■
lm.jar
visiconnect.jar
vbsec.jar
jsse.jar
jnet.jar
jcert.jar
jaas.jar
jce1_2_1.jar
sunjce_provider.jar
local_policy.jar
US_export_policy.jar
If you fail to include these jars in your CLASSPATH when you attempt to generate a
vault, you may end up with a vault file which is invalid. If you attempt to reuse the
invalid vault file, you will encounter an EOFException. To resolve, delete the invalid
vault file and regenerate with ResourceVaultGen, ensuring that you have the proper
jars in your CLASSPATH.
VisiConnect will use the vault if Security Map information is specified in at deployment
time for a Resource Adapter. If the resource vault is password protected, VisiConnect
will need to have the following property passed to it:
-Dvisiconnect.resource.security.vaultpwd=
If the resource vault is in a user specified location (-vaultfile ...), VisiConnect will need
to have the following property passed to it:
-Dvisiconnect.resource.security.login=
262 BES Developer’s Guide