OPMS Deployment Information

Use the following configuration for firewall, HTTP proxy, partition layout, and automated deployment of an On-Premise Monitoring Station.
cacm82
Use the following configuration for firewall, HTTP proxy, partition layout, and automated deployment of an On-Premise Monitoring Station.
Installation Resources
Download the OPMS installation file from the ASM Downloads page.
Firewall Settings
OPMS requires access to outbound ports 443. The installer issues HTTPS requests to
api.asm.saas.broadcom.com
,
apt.asm.saas.broadcom.com/
yum.asm.saas.broadcom.com/
and
registry.asm.saas.broadcom.com/
. During installation, the package manager sends requests to distribution repositories, as listed in
/etc/apt/sources.list.d/ or /etc/yum.repos.d/
directory. During the normal operation, OPMS establishes a WSS (Web Socket Secure) connection to
opp1.asm.saas.broadcom.com
and
opp2.asm.saas.broadcom.com
.
We recommend that you do not add firewall rules by the IP addresses of the hosts. These rules are subject to change and might be location-dependent. If extra security is needed, we recommend that you set up an HTTP Proxy.
HTTP Proxy
You can set OPMS to direct all service requests through an HTTP proxy and, optionally, with plaintext authorization. Requests issued by monitors are not routed through the proxy.
Debian
Enter the proxy configuration during Debian installation. The OPMS installer picks up the configuration from
/etc/apt/apt.conf
. To change the proxy, edit the
/etc/apt/apt.conf
file.
RHEL / CentOS 7 / Oracle Linux
To enter proxy configuration, edit
/etc/yum.conf
after installation:
proxy=http://<proxy address>:<port> proxy_username=<username> proxy_password=<password>
Partition Layout
We recommend that you do not split the file system into separate partitions. If you use a different layout, ensure that you allocate enough space for
/tmp
(at least 1 GB) and for
/opt
where all the assets (Full Page and Real Browser monitor snapshots and HARs) are stored. If you use lots of FPM and RBM monitors, the assets might need as much as 50 GB.
Virtualization
You do not need any special requirements to run the OPMS as a virtual machine. For optimal performance, we recommend that you install virtualization tools on the guest machine. For details, refer to the documentation of your virtualization solution provider.
Automated Deployment
To automate the process of installing OPMS, use silent installation.
Follow these steps:
  1. Run the installer using the following command:
    # sh ./asm-opms-<version>.bin -r /tmp/opms.response
  2. Specify your preferred OPMS settings in the wizard.
  3. Start the installer with the response files as argument:
    sh ./asm-opms-<version>.bin -i silent -f /tmp/opms.response
    The software is installed.
Deploying OPMS by cloning an existing installed VM is not supported. Instead, clone a clean OS installation, change the hostname, and then run the installer.
Docker Limitations
The monitors that use Docker face limitations when accessing internal hostnames.
When referring to an internal hostname, the monitor must be resolved by DNS. This limitation applies to the following monitors:
  • RBTM
  • (JMeter) Script
  • WebDriver