This topic lists the requirements and supported resources for installing the BMC Release Lifecycle Management suite:
System requirements for BMC Release Process Management 2.6.00
The following table lists the requirements and supported resources for BMC Release Process Management. For information about the deployment architecture and the performance tuning for the product, see Deployment-architecture.
System requirements for BMC Release Process Management
Resource | Requirements | Comments |
---|
Operating systems | This product supports the following operating systems: - Red Hat Enterprise Linux 5.5, 6.0, and 6.2 x86-64
- Microsoft Windows Server 2008 R2, SP1, x86-64
| None |
Port | 8080 is the default port of the server on which BMC Release Process Management is installed. | If for some reason you are unable to use the default port 8080, then you can change it at the time of installation by using the installation utility. |
Disk space | - 2 GB disk space for installing the BMC Release Process Management product
- Approximately 350 MB of database space for every 5,000 requests created
- Approximately 350 MB space for automation-related data for every 5,000 requests created
| - The disk space might vary, depending on the size of your environment.
- The space requirements for database and automation-related data are in addition to the 2 GB space required for installing the product.
|
Databases | Oracle 11g Release 1 (64-bit) Oracle 11g Release 2 (64-bit)
| - Dynamic ports are not supported for Microsoft SQL.
- For Oracle, set the following permissions on your database user:
CREATE USER RPMUSR PROFILE DEFAULT IDENTIFIED BY <password> DEFAULT TABLESPACE RPMUSR TEMPORARY TABLESPACE TEMP ACCOUNT UNLOCK GRANT CONNECT TO RPMUSR GRANT RESOURCE TO RPMUSR GRANT CREATE VIEW TO RPMUSR GRANT UNLIMITED TABLESPACE TO RPMUSR
|
Web browsers | - Internet Explorer versions 7, 8, and 9
- Mozilla Firefox versions 11.2 to 15
| BMC does not support versions of Firefox that do not support the Flash plug-in. The Flash plug-in is required for running this product. |
Integration support | This product supports integrations with the following products: - BMC Remedy IT Service Management versions 7.6.04 SP2
- BMC Atrium Orchestrator 7.6.01.04 and 7.6.02
- BMC Application Automation 8.0.00, 8.1.00, and 8.2.00
- BMC VaraLogix Q Deployment Automation 4.3.00
| BMC Remedy IT Service Management with BMC Remedy Release Management module required only if you are already using this product to manage your release cycles and if you plan to integrate it with the BMC Release Process Management product. WarningNoteTo successfully integrate BMC Remedy IT Service Management with the BMC Release Process Management product, you must install and configure BMC Atrium Orchestrator. - BMC Application Automation is required only if you are already using this product to manage your application deployments and if you plan to integrate it with the BMC Release Process Management product.
|
System requirements for BMC VaraLogixQ Deployment Automation 4.3.00
The following table provides the requirements and supported resources for BMC VaraLogix Q Deployment Automation:
System requirements for BMC VaraLogix Q Deployment Automation
| | |
---|
| - 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.
|
| 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
| |
| | 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
| |
Memory (recommended free space) | - Deployment server: 8 GB
- Additional servers: 256 MB
| |
| - 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
|
| - Internet Explorer version 9
- Mozilla Firefox versions 11.2 and 15
| |
| - A multi-core CPU (for deployment server only)
- A single-core CPU (for additional servers, if any)
| |
| - 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
| For BMC BladeLogic NSH and the RSCD Agent: - Both components (NSH and RSCD) must be of the same version.
- Version 7.6 is supported only with the Linux dispatcher (and not with the Windows dispatcher).
|