Audience

Those who need to upgrade configuration files for Servant-generated JBoss 4.0.x servers, and have JBoss 3.2.5 servers they wish to use as models.

Purpose

To generate JBoss 4.0.x servers automatically.

Prerequisites

• access to CVS with appropriate permissions to access the servant and maven-repo projects
• an XML editor, such as Oxygen

Changes to Config Files between Servant for JBoss 3.2.5 & JBoss 4.0.x

The following steps allow conversion from an XML properties file used to generate JBoss 3.2.5 servers, to an XML properties file used to generate JBoss 4.0.x servers. For information on the nature and appropriate values for each of these and other properties in the file, cf. this HowTo.

• Third-party libraries are no longer obtained from the ist-jxde project in the CVS repository; nor are streek dependencies obtained from a locally built streek/target directory. Instead, they are obtained from the maven-repo project, which is a local Apache-Maven repository maintained in the UCB-IS&T installation of CVS (in the /usr/local/cvsrep/proj/streek repository). If the local copy of this repository does not contain a specified third-party JAR file, Servant will attempt to download it via HTTP from the Maven repository at ibiblio.org. Note that this implies the updated local repository (maven-repo) should be checked-out into the workspace prior to a Servant build. To accomodate these changes from the prior version of Servant, the following changes need to be made:
  1. The new property streek.dependencies must be added (under the jmx.console.security node) in order to secure the JMX and Axis consoles
  2. The property lib.third.party.jar.files.dir must be deleted; it is no longer used, and is no longer included in the DTD for the *-properties.xml file.
  3. The new property lib.third.party.jar.files.tomcat may optionally be inserted after (and as a sibling to) the property jms.files; its value specifies jar files to be written to the common/lib directory of the generated server's embedded Tomcat instance. Cf. final bullet in this list
  4. The property lib.third.party.jar.files.jboss replaces lib.third.party.jar.files; cf. final bullet in this list
  5. The property client.third.party.jar.files remains valid; cf. final bullet in this list
  6. The properties that specify third-party JAR files must specify the libraries using the Maven style, e.g., commons.beanutils.version=1.7.0
• The following services must be omitted from the services.files property as these services are not controlled from jboss-service.xml in JBoss 4 (instead, they are hot-deployable):
  • beanshell-deployer.ent
  • ejb-deployer.ent
  • ear-deployer.ent
• The following services are new to jboss-service.xml in JBoss 4, and they may be added to the services.files property as appropriate:
  • xmbean-persistence.ent
  • threadpool-service.ent
  • jdbc-type-mapping-metadata.ent
• Multiple self-signed certifications may be generated for keystore used by embedded Tomcat by inserting the following (optional) XML fragment directly following the opening of the generated-key tag and setting the value attribute of alias-cn-base-names according to the included directions:

            
            <!-- 
              if the comma-delimited list of alias/community base
              names are uncommented, the alias and distinguished.name.cn 
              properties will be ignored.  the list of base names will be used
              to generated alias values ( ${basename}-key ) and
              distinguished.name.cn values ( ${basename}.berkeley.edu )
              in the servant/jboss4/build-servers.xml script.
              
              note that other values are shared between all generated keys 
             -->
            <multiple-key-names>
              <alias-cn-base-names value="basename1,basename2,basename3" />
            </multiple-key-names>
            
          

• Validate that the modified file conforms to the DTD in servant/jboss4/conf/dtd/servant-properties.dtd