Deployment examples

This section contains examples of some of the deployments that can be used for configuring on-premises or cloud environments.

Note: These examples are used to illustrate functional capabilities only. In a real deployment, you can mix and match components to create a deployment plan that best suits your needs.

For full installation and configuration instructions, see the Installation Guide (available from Install).

Basic deployment example

The basic deployment requires an OpenText Enterprise Performance Engineering server, host, load generators, and back end components (including database and repositories).

Note: A load balancer is required only when you have two or more servers.

Over firewall deployment example

When testing applications that are located behind a firewall relative to the server or host machine, you must configure an MI Listener, a load generator over a firewall, and possibly a monitor over a firewall.

Advanced deployment example

This deployment illustrates the ability to integrate with different Application Performance Management (APM) tools such as New Relic, Dynatrace, and AppDynamics. You can also integrate with Kubernetes for dynamic provisioning of load generators (see Dockerized host deployment example below).

Load generator cloud deployment example

You can provision load generators in the cloud using your cloud account. Load generator provisioning is supported with Amazon EC2 and Microsoft Azure cloud accounts. For more details, see Manage elastic cloud hosts.

Note:

The ports used in this diagram are the common HTTP ports. You can configure the cloud load generator ports as required.
For the most secure load generator connectivity, use TLS (SSL) with a client certificate.

Full cloud deployment example

You can deploy the full installation (on-premise OpenText Enterprise Performance Engineering server, hosts, and load generators) on your cloud provider platform as long as it meets the requirements in theSupport Matrix and the correct ports are open. For more details, see Provision elastic cloud load generators.

Note:

To improve performance, it is preferable to deploy the servers, hosts, and database in the same region.
The required ports must be open for incoming requests to the relevant server.
Cloud load generator ports are configurable. When all the components are in the cloud, the ports to use are defined by the cloud provider (they are not based on internal IT policies).
For the most secure load generator connectivity, use TLS (SSL) with a client certificate.

Dockerized host deployment example

You can provision Dockerized (elastic) load generators using a Docker Kubernetes orchestrator. For more details, see Provision Docker hosts automatically.

*For the required ports, see the Docker Kubernetes documentation.

SaaS deployment example

You can move OpenText Enterprise Performance Engineering from on-premises to SaaS to deliver continual non-disruptive functionality updates. For more details, see SaaS deployment.