This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BladeLogic Application Release Automation - Standard
BMC BladeLogic Application Release Automation - Standard
Getting the below error during application deploy. All other tasks like , snapshot, creation of resources, etc works fine.
Issue Summary: unable to deploy application to new system, getting file upload error
If the target WAS Application Server is behind a firewall and you get these error that means some of the required ports are not opened. Below are the ports that are needed to be opened:
1. Target WAS DMGR SOAP_CONNECTOR_ADDRESS - this is needed for BARA to connect to the DMGR for almost all transactions.
2. Target WAS DMGR WC_adminhost (HTTP)
3. Target WAS DMGR WC_adminhost_secure (HTTPS)
We need the HTTP and HTTPS ports for the DMGR added in the firewall because the EAR file upload always happens through the https://WAS-target:port/FileTransfer. This url is provided by Websphere to upload the file and the port here is the HTTP or HTTPS port of the DMGR. If the target WAS is secure then the port is HTTPS.
The connection time out issue caused if the ports are not opened in firewall. Opening the ports mentioned above resolves the problem.
- BMC BladeLogic Application Release Automation - Standard