Chapter 4. ZIP Installation from the Red Hat Customer Portal

Procedure 4.1. Installation via ZIP file

Follow this procedure to install JBoss Enterprise Application Platform via ZIP file.
  1. Download software

    Refer to Appendix A, The Red Hat Customer Portal for file download instructions.
    Choose the Application Platform <release> Binary download. If you want to use WS CXF as the Web Services Stack for the Platform, download the jboss-ep-ws-cxf-<release> file.
  2. Unzip jboss-eap-<release>.zip to extract the archive contents into the location of your choice.
    In a Red Hat Enterprise Linux environment, use the unzip utility to extract the Zip archive.
    In a Microsoft Windows environment, right-click the file and select Extract All.
    In a Hewlett-Packard HP-UX environment, use the unzip utility to extract the Zip archive.
    This creates the jboss-eap-<release> directory, with an installation of JBoss Enterprise Application Platform using JBoss WS Native as the Web Services Stack, and JBoss Messaging as the messaging provider.
  3. Optional: Use JBoss WS CXF as the Web Service stack

    You need Apache Ant installed and configured on your machine to perform this task.
    1. Extract jboss-ep-ws-cxf-<release> and move the jbossws-cxf-installer into the jboss-as directory of the Enterprise Platform.
    2. At the command line go to the directory jboss-as/jbossws-cxf-installer and run the command ant.
      An installer script replaces WS Native with WS CXF.
  4. Optional: Install PicketLink Federation

    1. To install PicketLink Federation, copy the $JBOSS_HOME/picketlink/picketlink-federation/picketlink-core-<VERSION>.jar file to $JBOSS_HOME/common/lib and copy $JBOSS_HOME/picketlink/picketlink-federation/picketlink-jbas5-VERSION.jar file to $JBOSS_HOME/common/lib;
    2. Optionally, deploy the PicketLink web applications of your choice to the server by copying their directories to $JBOSS_HOME/jboss-as/server/PROFILE/deploy/ directory. To do so, run the following command with the WEBAPP substituted with the application directory (idp.war, pdp.war, or picketlink-sts.war):
      cp -r $JBOSS_HOME/picketlink/picketlink-federation-webapps/WEBAPP $JBOSS_HOME/jboss-as/server/PROFILE/deploy/
  5. Optional: Install Native Components

    Refer to Section 8.3, “Native Components” for Native Component installation instructions.
  6. Perform post-installation configuration

    At this point, you have JBoss Enterprise Application Platform installed. It is now recommended to perform post-installation configuration of the platform according to instructions in the Administration and Configuration Guide. For instructions on how to configure the platform's security, refer to the Security Guide.

4.1. HornetQ

HornetQ is included as an alternative JMS provider to JBoss Messaging. See the HornetQ User Guide for this release for further information about HornetQ functionality.

Procedure 4.2. Install HornetQ

Apache Ant must be installed and configured on your machine to perform this task. Refer to Appendix C, Installing Apache Ant for installation instructions.
You must have the correct entitlements to download and install HornetQ.
  1. Download the HornetQ ZIP ( from the Customer Support Portal.
  2. Extract the files from into your JBoss Enterprise Application Platform installation (the archive contains the entire jboss-eap-5.2 directory structure; therefore, merge the extracted directory with your jboss-eap-version directory).
  3. Change to $JBOSS_HOME/jboss-as/extras/hornetq.
  4. Verify the script is configured to be executable.
  5. From the command line, run the HornetQ switching script.
    [hornetq]$ ./