Skip to content

Latest commit

 

History

History
69 lines (46 loc) · 3.48 KB

securegateway_requirements.md

File metadata and controls

69 lines (46 loc) · 3.48 KB
Raw
copyright lastupdated
years
2015, 2018
2018-08-10

Requirements to run the Client

System Requirements

{: #system}

The Secure Gateway Client is supported in the following environments:

Name Versions
Windows Desktop 7, 8.1, 10 and greater
Windows Server 2012 R2 and greater
Red Hat Linux 6.5 and greater
CentOS 7.2 and greater
SuSE Linux 11.0* and greater
Ubuntu Linux 14.04 (LTS) and greater
Power Machine ppc64el architecture
Ubuntu Z-Linux -
AIX 7.1 and greater
Mac OS X 10.10 (Yosemite) and greater
Docker 1.7.0 and greater, all supported operating systems

* - SLES 11 support is only with Service Pack 4

Note: Only 64-bit environments are currently supported for native client installation.

Network Requirements

{: #network}

The Secure Gateway Client uses outbound port 443 and port 9000 to connect to npm registry and the {{site.data.keyword.Bluemix}} environment :

  • Port 443 for npm installation

    • During the installation, the installer will connect to npm registry and run npm install to install the dependencies required by Secure Gateway Client. Before the installation, please make sure the machine which the client will be installed on can connect to a npm registry website. npm is configured to use npm, Inc.'s public registry at https://registry.npmjs.org by default.

      If there's npm Enterprise server in your environment, please whitelist all of the dependencies of Secure Gateway Client on the npm Enterprise server. For the list of dependencies, please refer to <Installation_directory>\ibm\securegateway\client\package.json file.

  • Port 443 for gateway authentication

    Region Host
    US South sgmanager.ng.bluemix.net
    US East sgmanager.us-east.bluemix.net
    United Kingdom sgmanager.eu-gb.bluemix.net
    Germany sgmanager.eu-de.bluemix.net
    Sydney sgmanager.au-syd.bluemix.net

  • Port 9000

    The node of the SG gateway, which can be found in the configuration of the gateway, each gateway will not be on the same node, please confirm the hostname of the node every time you create the gateway

Ensure you check or modify additional firewall and IP Table rules that might apply. If your network administrators require specific IPs, please contact support to request these for your environment.

Determining Hardware Requirements

{: #hardware}

The specifications of the machine running the Secure Gateway Client is largely dependent on the traffic that will be passing through each connection. Each client instance is an individual process that provides up to 250 concurrent connections. To approximate an average maximum that the machine would need to support, determine the average size of a transaction across the client (both request and response) and then scale that to 250 concurrent transactions. Given that this number has combined both request and response sizes, the client should not exceed this memory footprint. For more precise estimates, a mixture of request sizes and response sizes should be used to better simulate a real-world transaction scenario.

For running a single instance of the Secure Gateway Client, we suggest a minimum of 2 cores and 4 GB of memory.

For HA scenarios that will be running multiple instances of the client on the same machine, we suggest a minimum of 4 cores and 8 GB of memory.