Minimum hardware and software requirements

This topic contains the following sections:

BMC product requirements and compatibility

BMC BladeLogic requirement

BladeLogic Portal 2.2 requires at least one of the following products:

BMC BladeLogic Network Automation 8.9
BMC BladeLogic Server Automation
Supported versions:
- Version 8.7 patch 3, patch 4, patch 5
- Version 8.8.x
- Version 8.9.x
Note

TrueSight Server Automation version 20.02 or later is not supported with the fresh or upgraded installation of BladeLogic Portal version 2.2.x.

Compatibility with other BMC products

Some features of BladeLogic Portal work in conjunction with other BMC products and versions:

BMC Discovery 11.0 or later
BMC Atrium Orchestrator Content version 20.16.02.00 or later
BMC Atrium Orchestrator Platform version 7.9.0 or later
BMC Remedy ITSM version 9.1 or later

Deployment sizing requirements

BladeLogic Portal supports a variety of deployment configurations. Most configurations require the BladeLogic Portal server and the DCA Index Server to be installed on separate notes. The following table details minimum requirements based on various deployment sizes.

Requirement	Large	Medium	Small	Compact
Number of concurrent users	150	50	25	Trial and demonstration purposes only
Number of BladeLogic Portal servers	6	2	1	1
Number of DCA Index Servers	6	2	1	1
CPUs per portal server	8	8	8	4
CPUs per DCA Index Server	8	8	8	N/A
CPUs per database server	32	16	8	4
Portal server memory (GB)	16	16	16	16
DCA Index Server memory (GB)	16	16	16	N/A
Database server memory (GB)	64	32	16	16
Portal server disk space (GB)	100	100	100	150
DCA Index Server disk space (GB)	100	60	50	N/A
Database disk space (GB)	150	120	100	N/A

What conditions were used to develop these sizing requirements?

Condition	Value
Number of existing vulnerability instances in database	15 million
Number of servers managed by BladeLogic Portal	100000
Number of concurrent users (per node)	25
Maximum scan data file size	1 GB
Average number of vulnerabilities per server	300
Number of servers enrolled in Threat Director	All

If you require a deployment larger than the Large deployment described above, extrapolate the system requirements based on the information in the table.

In the table above, a Compact deployment assumes the portal server and the DCA Index Server are hosted on the same machine. All other deployments assume portal servers and DCA Index Servers are hosted on separate machines. Memory requirements refer to total memory, not heap size.

Other Windows installation requirements

In addition to the requirements listed in the table above, BladeLogic Portal has the following installation requirements on Microsoft Windows:

64-bit Microsoft Windows 2008, 2008 R2, 2012, or 2012 R2
MInimum CPU processor speeds of 1.6 GHz
Network speed minimum of 100 Mbps
Java RunTime Environment (JRE) version 1.8
The installation program installs and uses its own version of JRE 1.8.

Other Linux installation requirements

In addition to the requirements listed in the table above, BladeLogic Portal has the following installation requirements on Linux:

64-bit Red Hat Enterprise Linux versions 6.0 (or later) or 7.0 (or later)
Minimum CPU processor speeds of 1.6 GHz
Network speed minimum of 100 Mbps
Java RunTime Environment (JRE) version 1.8
The installation program installs and uses its own version of JRE 1.8.

Database installation requirements

Installation requirements vary by database vendor.

Oracle

Oracle 11.2 or later or Oracle 12c
Operating system—64-bit Red Hat Linux
Processor—2 Xenon with 2 GHz (recommended that you use 4 Xenon with 3 GHz or better)
AL32UTF8 character set (to provide Unicode support)
Click here for information about determining the character set.
By default, Oracle does not create a database with the UTF-8 character set. When you create a new database, ensure that you select AL32UTF8 in the Oracle database setup.
To determine whether a database is using the correct character set, you can run a script that BMC provides.
1. In the installation files, cd to this directory:
  installation_file_location/linux/BMCAutomationPortal/Disk1/utility/oracle/utils/configuration
2. As the Oracle system user, run the following command:
  
  sqlplus system/system_user_password@<SID> @showcharset.sql
SGA and PGA settings—Typically, default values are sufficient.
Click here for information about SGA and PGA.
To determine the current SGA value, run the follow command as the Oracle system user:
show sga
On 64-bit Windows platforms and 32-bit platforms not running Windows, when either MEMORY_TARGET or MEMORY_MAX_TARGET is specified, the value of SGA_MAX_SIZE is set to the larger of those parameters.
PGA tuning is enabled by default and is usually 20% of SGA.

SQL Server

SQL Server 2012 x64 or SQL Server 2014 x64
Operating system—64-bit Windows
Processor—2 Xenon with 2 GHz (recommended that you use 4 Xenon with 3 GHz or better)

Elasticsearch

The DCA Index Server runs Elasticsearch version 1.7.3.

Installation stack combinations

Currently, BladeLogic Portal supports the following installation stacks:

BladeLogic Portal OS	Supported databases
64-bit Microsoft Windows 2008 R2 Service Pack 1 (or later), 2012, or 2012 R2	SQL Server 2012 x64 SQL Server 2014 x64
64-bit Red Hat Enterprise Linux version 6.0 or later	Oracle 11.2 or later Oracle 12c

Required ports

BladeLogic Portal requires the following ports for a standard installation. As noted below, your firewall must allow communication through some of these ports for the associated components to function.

Port	Protocol	Configured on	User can choose port number?	Firewall exception needed?	Description
8005	TCP	Portal server	Yes	No	Default port used by the portal server for administrative purposes
8080	TCP	Portal server	Yes	Yes	Default port used to access the portal application using HTTP
8443	TCP	Portal server	Yes	Yes	Default secure port used to access the portal application using HTTPS
9200	HTTP	DCA Index Server (may be configured on the same machine as the portal server)	Yes	Yes - if DCA Index Server is installed on separate machine. No - if DCA Index Server is configured on same machine as portal server.	Default port used for monitoring the DCA Index Server. The DCA Index Server can use a range of 100 ports, skipping any ports in use within that range. By default, the installation uses 9200 as the low end of the 100-port range. After installation, you can disable HTTP traffic with the DCA Index Server if an open HTTP port is a security concern.
9300	TCP	DCA Index Server (may be configured on the same machine as the portal server)	No	Yes	Default port used for required transport layer traffic with the DCA Index Server. The DCA Index Server can use a range of 100 ports, skipping any ports in use within that range. Port 9300 is chosen by default as part of the install process.
9875	TCP	Portal server	No	No	Internal communication port needed by the portal server (PORTAL_JMX_PORT)
9843	TCP	BMC Server Automation Application Server	Yes	Yes	Default web services port configured on the BMC Server Automation Application Server for REST queries
443	TCP	BMC Network Automation Application Server	Yes	Yes	Default port configured on BMC Network Automation Application Server for REST queries

Supported browsers

Google Chrome 52 or later
Mozilla Firefox 48 or later
Microsoft Internet Explorer 10 or 11

Minimum resolution

The minimum resolution BladeLogic Portal supports is 1280 x 1024.

Supported target platforms

This section identifies the platforms that can be managed using different capabilities of BladeLogic Portal.

Threat Director and Vulnerability Manager

The full functionality of Threat Director and Vulnerability Manager is available for the following platforms. Auto-mapping, which is a core feature of the portal, is only possible on those platforms.

Windows
Red Hat Enterprise Linux
SuSE Linux

For other platforms, the portal allows manual mapping of vulnerabilities, although manual mapping of patch catalogs is not supported. Thus, you can use Threat Director and Vulnerability Manager to operate on other platforms as long as you manually map vulnerabilities.

Operations other than Threat Director and Vulnerability Manager

For other operations, BladeLogic Portal supports the same target servers as those supported by BMC Server Automation for the same job type.

Where to go next

Enabling web services in BMC Server Automation