user manual

Chapter 27: Using VisiConnect 295
Security Management with the Security Map
where:
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
Note 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.
-rolename Resource role name to store in the
resource vault.
-usermame Resource username to associate with the
resource role.
-password Resource password to associate with the
resource role.
-vaultfile (optional) 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
<install_dir/var/domains/base/
configurations/<configuration_name>/
mos/<partition_name>/adm/properties/
management_vbroker.properties>. If the
vault file is does not already exist, a
new vault file will be written to the
specified location.
-vpwd (optional) Password to assign to the vault for
access authorization. If not specified,
the vault will be created without a
password.