System requirements

This topic lists the requirements and supported resources for installing BMC Release Lifecycle Management Suite.

System requirements for BMC Release Process Management 5.0

The following table lists the requirements and supported resources for BMC Release Process Management. For information about the deployment architecture and performance tuning for the product, see Deployment architecture.

Resource

Requirements

Comments

Operating systems

  • Microsoft Windows Server 2012 R2 (x86-64)
  • Red Hat Enterprise Linux 7.0 (x86-64)
  • Red Hat Enterprise Linux 6.5 (x86-64)
  • Oracle Solaris v10 (Enterprise) x86 (only for BRPM 5.0.00)
    Note: Starting with BRPM 5.0.01.00, Oracle Solaris is not supported.

None

Ports

VERSION 5.0.03.004 OR LATER

  • SSL (HTTPS) port: 8443
  • Messaging port: 5445

VERSION 5.0.03.003 OR EARLIER

  • HTTP port: 8080
  • Messaging port: 5445
  • Stomp port: 8675
  • Stomp secure port: 8676
  • SSL (HTTPS) port: 8443
  • The default port is the port of the server on which BRPM is installed. If you are unable to use the default port 8080, then you can change the port during the installation.
  • Both the stomp port and stomp secure port can be edited in RLMhome/server/jboss/standalone/configuration/standalone.xml.
CPU cores4None
Physical memory16 GB

Tip: You can calculate the optimal physical memory size for your environment using this formula.

Disk space

  • 2 GB disk space for installing BRPM
  • 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 required for installing the product in addition to the 2 GB space.

Web browsers

  • Mozilla Firefox (version 83)
  • Google Chrome (version 87)
  • Microsoft Edge (version 87.0.664.57)
  • Safari (Deprecated)

Adobe Flash dependency is now removed. For customers who want to continue to use the Flash-based BMC products, see Impact of Adobe Flash Player end of life for more details.

Integration support

This product supports integrations with the following products:

  • BMC Atrium Orchestrator Platform 7.6.02
  • BMC Atrium Orchestrator Content 20.16.01
  • BMC Release Package and Deployment version 5.0.00, 5.0.01, 5.0.02, 5.0.03 for BMC Release Process Management version 5.0.00, 5.0.01, 5.0.02, 5.0.03
  • BMC Remedy IT Service Management Suite 9.1.02
  • BMC Remedy IT Service Management Suite 7.6.04 and 8.1 (Deprecated)
  • UPDATED IN 5.0.03.001 JIRA 7.9.2

  • NEW IN 5.0.03.001 Teamcity 2017.2.3 (build 51047)

  • BMC Application Automation

    BRPM versionTrueSight Server Automation (formerly called BMC Server Automation)
    5.0.04 5.0.03.005 5.0.03.00420.02 and 20.02.01
    5.0.03.0038.9.04.001
    5.0.03.0028.9.04
    5.0.03.0018.9.02
    5.0.038.9.01
  • To successfully integrate BMC Remedy IT Service Management with BRPM, you must install and configure BMC Atrium Orchestrator.
  • Support for BMC Remedy IT Service Management Suite 7.6.04 and 8.1 is deprecated.

System requirements for BMC Release Package and Deployment 5.0

The following table provides the requirements and supported resources for BMC Release Package and Deployment.

Resource

Requirements

Comments

Operating systems

    • Microsoft Windows Server 2016 (x86-64)
    • Windows Server 2012 R2 (x86-64)
    • Red Hat Enterprise Linux 7.0 (x86-64)
    • Red Hat Enterprise Linux 6.5 (x86-64)
  • This configuration requirement applies to deployment server, any additional server, and dispatchers.
  • The RPD server hosts the management console and engines that control the remote actions. The server can be physical or virtual. For better performance, either the management console or the engines should be run on the server.
  • When RPD is running on Red Hat Enterprise Linux, the Microsoft SQL Server database is not supported.
  • When RPD is running on Windows, PowerShell 3.0 or higher is required.
  • Starting with 5.0.02, installation in bridge mode is not supported.
  • (Windows) If you plan to use TLS 1.2, ensure that you have enabled TLS 1.2 and SSL 3.0 in Microsoft Windows registry.

Supported targets

OSs supported by Network Shell (NSH), SSH, Chef, or Puppet protocols

The target is a system that you want to manage using the RPD application.

Ports

  • RPD user interface: 80 (the default port)
  • Dispatcher/Bridge in the legacy bridge mode: 50005 and 50006-5000n
  • Dispatcher/Bridge: 50004 and 50006-5000n
  • If you cannot use the 80 port for the RPD user interface, you can change it during installation.
  • For the dispatcher in the legacy bridge mode:
    • The engine pings the bridge/dispatcher over the 50005 port.
    • The dispatcher returns the above in range port for communication.
    • For 5000n, n=6+number of engines.
  • For the dispatcher, the communication is performed over one port.

CPU cores

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

None

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

Disk space

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

None

Databases

  • Microsoft SQL Server 2016 (64-bit)
  • SQL Server 2014 (64-bit)
  • SQL Server 2008 R2 (64-bit) (Deprecated)
  • Oracle Real Application Clusters (RAC) 12c
  • Oracle 12c (64-bit)
  • Oracle 11g R2 (64-bit)
  • PostgreSQL 9.5.4 (64-bit)
  • PostgreSQL 8.4 (64-bit) (Deprecated)
  • Microsoft SQL Server supports the following authentication modes:
    • Local
    • Domain (only if the RPD services run under the Windows domain user who has database credentials)
  • The Microsoft SQL Server database is not supported when RPD is running on Red Hat Enterprise Linux.
  • The database contains instances of the application content and the system configuration data. 
    The database server can be installed on the same system that is used for the deployment server (not recommended).
  • The database server can reside on any operating system. The deployment server must have the appropriate PHP modules installed for communication with the database server.
  • Dynamic ports are not supported for the Microsoft SQL Server database.
  • For Oracle, set the following permissions on your database: 

    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 11
  • Mozilla Firefox (latest version)
  • Google Chrome (latest version)
  • Microsoft Edge (Microsoft Windows 10)
  • Safari (Deprecated)

Cookies and JavaScript must be enabled in your web browser.

Integration support

  • BMC Middleware Automation 8.5
  • BMC BladeLogic Network Shell (NSH) 8.9.00 and RSCD Agent 8.9.00
  • PuppetLabs Puppet 2.7, 3.0, Enterprise 2.5.1 (all experimental)
  • Opscode Chef 10.14 (experimental)

RPD requires both Network Shell (NSH) and Remote System Call Daemon (RSCD) agents as targets. You must have the RCP/NSH client and the RSCD agent installed on your dispatcher host to use the RPD product.

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

Was this page helpful? Yes No Submitting... Thank you

Comments