이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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.
  1. Click the Administration tab in the top menu.
  2. Select the Downloads in the left menu table.
  3. Scroll to the Bundle Deployer Download section, and click the package download link.
  4. Save the .zip file into the directory where the bundle tool should be installed, such as /opt/.
  5. Unzip the packages.
    cd /opt/
    
    unzip rhq-bundle-deployer-version.zip
    Copy to Clipboard Toggle word wrap

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.
  1. 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
    Copy to Clipboard Toggle word wrap
  2. Open the top directory of the bundle distribution, where the deploy.xml Ant recipe file is.
  3. Set the bundle deployer tool location in the PATH.
    PATH="/opt/rhq-bundle-deployer-3.0.0/bin:$PATH"
    Copy to Clipboard Toggle word wrap
  4. 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
    Copy to Clipboard Toggle word wrap
    This installs the application in /opt/exampleApp and sets a port value of 7081.
    Note
    Optionally, use the rhq.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 the rhq.deploy.id attribute on a new deployment simulates the server's ID assignment.
    Using the rhq.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.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat