27.6. Testing Bundle Packages
Ant recipes can be complex, so it's important (and useful) to test a bundle before deploying it. JBoss ON includes a command-line tool that can be used to test Ant provisioning bundles quickly.
27.6.1. Installing the Bundle Deployer Tool
This tool can be downloaded and installed on any machine, independent of any JBoss ON server or agent.
- Click the Administration tab in the top menu.
- Select the Downloads in the left menu table.
- Scroll to the Bundle Deployer Download section, and click the package download link.
- Save the
.zip
file into the directory where the bundle tool should be installed, such as/opt/
. - Unzip the packages.
cd /opt/ unzip rhq-bundle-deployer-version.zip
27.6.2. Using the Bundle Deployer Tool
Important
This bundle deployment tool is only to test the provisioning process and deployed application. This tool does not interact with the JBoss ON server or agent, so JBoss ON is unaware of any applications deployed with this tool and cannot manage them.
- Unzip the bundle distribution package to check (or copy an unzipped directory that contains the application files). For example:
mkdir /tmp/test-bundle cd /tmp/test-bundle unzip MyBundle.zip
- Open the top directory of the bundle distribution, where the
deploy.xml
Ant recipe file is. - Set the bundle deployer tool location in the PATH.
PATH="/opt/rhq-bundle-deployer-3.0.0/bin:$PATH"
- Run the bundle deploy tool, and use the format
-D
input_properties to pass the values to user-defined tokens in the templatized files. For example:rhq-ant -Drhq.deploy.dir=/opt/exampleApp -Dlistener.port=7081
This installs the application in/opt/exampleApp
and sets a port value of 7081.Note
Optionally, use therhq.deploy.id
attribute to set an identifier for the deployment. The default is 0, which means a new deployment. When bundles are deployed in the UI, the server assigns a unique ID to the deployment. Using therhq.deploy.id
attribute on a new deployment simulates the server's ID assignment.Using therhq.deploy.id
attribute if there is already a previous deployment allows you to test the upgrade performance of the bundle. Performing an upgrade requires a new, unique ID number.