Specifying How the SRC-VTA Loads Configurations from the Directory
Bootstrap properties specify how the SRC-VTA loads configurations from the directory. If you install the directory on a different host than the J2EE application server, you must modify the bootstrap properties to specify the directory host.
To configure the bootstrap properties for each VTA:
- Create a folder for the VTA on a host.
- Copy the EAR file for the VTA from the archive file to the folder that you created in Step 1.
- From the EAR file, extract the file vtacore.jar into the folder you created.
- From the file vtacore.jar, extract the file META-INF/ejb-jar.xml.
- In the folder that you created in Step 1, edit the META-INF/ejb-jar.xml file.
See Properties in ejb-jar.xml file for information about the properties in this file.
- Replace the file META-INF/ejb-jar.xml in the file vtacore.jar.
- Replace the file vtacore.jar in the EAR file.
Properties in ejb-jar.xml file
This topic describes the properties in the ejb-jar.xml file.
Config.java.naming.provider.url, Config.java.naming.security.principal, Config.java.naming.security.credentials, Config.java.naming.security.protocol
- Standard JNDI properties.
Config.net.juniper.smgt.lib.config.staticConfigDN
- Root of the static configuration properties for the SRC-VTA.
- Value—DN
- Default—I=VTA, ou=staticConfiguration, ou=Configuration, o=Management, o=umc
Config.net.juniper.smgt.lib.config.dynamicConfigDN
- Root of the dynamic configuration properties for the SRC-VTA.
- Value—DN
- Default—ou=dynamicConfiguration, ou=Configuration, o=Management, o=umc
Config.net.juniper.smgt.des.<propertySuffix>
- Defines how the SRC-VTA monitors values that it reads from the directory.
vta.namespace
- Root namespace of the SRC-VTA.
- Value—Path, relative to the root of the static configuration properties, that defines where the VTA’s configuration is stored
- Example—/Applications/Quota
