Red Hat SummitEste conteúdo não está disponível no idioma selecionado.
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
Copiar o linkLink copiado para a área de transferência!
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
.zipfile into the directory where the bundle tool should be installed, such as/opt/. - Unzip the packages.
cd /opt/ unzip rhq-bundle-deployer-version.zip
cd /opt/ unzip rhq-bundle-deployer-version.zipCopy to Clipboard Copied! Toggle word wrap Toggle overflow
27.6.2. Using the Bundle Deployer Tool
Copiar o linkLink copiado para a área de transferência!
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
mkdir /tmp/test-bundle cd /tmp/test-bundle unzip MyBundle.zipCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Open the top directory of the bundle distribution, where the
deploy.xmlAnt recipe file is. - Set the bundle deployer tool location in the PATH.
PATH="/opt/rhq-bundle-deployer-3.0.0/bin:$PATH"
PATH="/opt/rhq-bundle-deployer-3.0.0/bin:$PATH"Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Run the bundle deploy tool, and use the format
-Dinput_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
rhq-ant -Drhq.deploy.dir=/opt/exampleApp -Dlistener.port=7081Copy to Clipboard Copied! Toggle word wrap Toggle overflow This installs the application in/opt/exampleAppand sets a port value of 7081.NoteOptionally, use therhq.deploy.idattribute 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.idattribute on a new deployment simulates the server's ID assignment.Using therhq.deploy.idattribute 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.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}