System requirements

Operating systems

• Red Hat Enterprise Linux 5.5, 6.0, and 6.2 x86-64
• Microsoft Windows Server 2008 R2, SP1, x86-64

• This configuration requirement applies to both the deployment server and any additional servers.
• The BMC VaraLogix Q Deployment Automation server hosts the management console and the engines, which control remote actions. The server can be physical or virtual. For best performance, it should be dedicated to running only the management console and engines.

Targets supported

Your target is the system that you want to manage by using BMC VaraLogix Q Deployment Automation. The following target types are supported:

• Windows Server 2003, 2008, 2008 R2, 2008 R2 SP1, x86-64
• Windows Server 2000, 2003
• Red Hat Enterprise Linux 5.5, 6.0, 6.2 x86-64
• Oracle Solaris 9, 10, and 11 (x86 and Sparc)
• IBM AIX versions 4, 5 and 6 (required for actions supported for the BMC Middleware Automation integration)
• Ubuntu 10.04
• SUSE Linux Enterprise Server 11
• CentOS

None

Port

80 (default)

If for some reason you cannot use the default port 80, you can change it during installation.

Disk space (recommended free space)

• Deployment server: 500 MB
• Database server: 500 GB
• Additional servers: 256 MB

None

Memory (recommended free space)

• Deployment server: 8 GB
• Additional servers: 256 MB

Databases

• Oracle 11g, Release 1 or Release 2
• MSSQL 2008, R2 
• PostgreSQL 8.2, 8.4.x

• The database contains instances of application content as well as the system configuration data.* The database server can be installed on the same system used for the deployment server (not recommended).
• The database server can reside on any operating system. The deployment server must have appropriate PHP modules installed for communication with the database server.
• Dynamic ports are not supported for MSSQL.

• For Oracle, set the following permissions on your database user: 

  CREATE USER RLMUSR
  PROFILE DEFAULT IDENTIFIED BY sa
  DEFAULT TABLESPACE RLMUSR
  TEMPORARY TABLESPACE TEMP ACCOUNT UNLOCK
  GRANT CONNECT TO RLMUSR
  GRANT RESOURCE TO RLMUSR
  GRANT CREATE VIEW TO RLMUSR

Web browsers

• Internet Explorer version 9
• Mozilla Firefox versions 11.2 and 15

Cookies and JavaScript in your web browser must be enabled.

Other requirements

• A multi-core CPU (for deployment server only)
• A single-core CPU (for additional servers, if any)

None

Integration support

• BMC Middleware Automation: version 8.2.03, Patch 3 or later
• BMC BladeLogic Network Shell (NSH) and RSCD Agent: version 7.6, 8.2, or 8.3

NSH and RSCD agent requirements

BMC VaraLogix Q Deployment Automation requires require both Network Shell (NSH) and Remote System Call Daemon (RSCD) agents as target. You must have RCP/NSH client and RSCD agent installed on your dispatcher host to use the BMC VaraLogix Q Deployment Automation product.

• 
  
  1. On at least one of the hosts where the dispatcher service is installed, install the BSA RCP client. BSA RCP client contains NSH and an authentication tools for connecting to the NSH Proxy. For the BSA RCP client installation information, see Installing NSH and RSCD agents.
  2. RSCD agents must be installed on every target that you want to retrieve files from or deploy to. RSCD agents mjust be configured on the same port as the NSH client installed on the dispatcher host. For the RSCD agent installation information, see Installing NSH and RSCD agents.