OpenText Core Performance Engineering Aviator

This section explains how to integrate OpenText Core Performance Engineering Aviator within OpenText Performance Engineering solutions.

In this topic:

Overview

OpenText Core Performance Engineering Aviator is a cloud-based enterprise service that delivers Artificial Intelligence (AI) capabilities to extend functionality within OpenText Performance Engineering products that are connected to this paid service.

Supported Performance Engineering products

Core Performance Engineering Aviator can be used with the following SaaS and On-Premises products.

Product type	Product
SaaS	OpenText Core Performance Engineering OpenText Enterprise Performance Engineering OpenText Core Performance Engineering Analysis
On-Premises	OpenText Professional Performance Engineering OpenText Enterprise Performance Engineering

Core Performance Engineering Aviator provides scripting support for these products through VuGen and automated, AI‑assisted analysis through Core Performance Engineering Analysis.

Performance Engineering products do not include Generative AI capabilities by default. To enable Generative AI through Core Performance Engineering Aviator, a license must be purchased and installed. Without this license, the products will not communicate with the AI service and will not send it any data. For details, see Subscription and license management.

Supported client instances

The following client instances are supported.

Client instance	Integration
VuGen	Requires manual configuration and access keys. For details, see Integrate with Core Performance Engineering Aviator and Create access keys.
Core Performance Engineering Analysis	Works out-of-the-box without additional keys.

Back to top

Integrate with Core Performance Engineering Aviator

Core Performance Engineering Aviator is delivered as a service (SaaS) product. After you are subscribed to the Aviator cloud service, you can integrate your client instance with the Core Performance Engineering Aviator tenant.

To integrate with VuGen:

1. Purchase a Core Performance Engineering Aviator license.

2. Follow the instructions in the Welcome email.

3. Sign in to MyAccount and select Aviator service.

Back to top

Create access keys

Access keys (Client ID and Secret Key) are required to authenticate VuGen to Core Performance Engineering Aviator.

Back to top

Automatic access key expiration

For security reasons, an automatic expiration policy is enabled by default for access keys. Automatic expiration reduces the lifetime of an access key by enforcing regular changes every 90 days by default.

An account admin can activate and deactivate the auto expiration policy, and change the expiration frequency. The policy is configured at the account level in MyAccount. When automatic expiration is enabled, an email notification is sent to users that own the key, 30 days and 7 days before the key is revoked, and 1 day before the key is set to expire.

To customize the expiration policy:

1. Sign in to MyAccount and click the Settings button . For details, see MyAccount - My Products.

2. Select the account you want to modify and open the Security tab. The Custom OAuth expiration policy option is enabled by default with an expiration frequency of every 90 days.

3. In the Account configuration area, click the Edit button , and modify the expiration policy as required:

   • Select an expiration frequency between 90 and 360 days in 30 day increments.

   • To deactivate automatic key expiration (not recommended), clear the Custom OAuth expiration policy checkbox. Click Continue to confirm that you are aware of the increased security risks and assume full responsibility for deactivating the feature.

4. Click OK to save the changes. All keys of all products associated with the specific account inherit these settings, and have the same life period.

5. The OAuth client area in MyAccount displays the list of client instances that were created for the logged in user. Anyone that has a client instance can manually refresh the key in MyAccount before it expires.

Back to top

Access key guidelines and best practices

The following guidelines and best practices apply when working with access keys:

• A user cannot have more than two access keys at one time. This encourages you to rotate the active keys. To assign a new access key to a user with two access keys, revoke an existing one.

• Access keys are per tenant. If the same user exists in multiple tenants, the user must have a separate access key for each tenant.

• If your account admin chooses not to enforce an expiration policy, we still recommend rotating access keys periodically.

• The recommended lifetime of an access key is 90 days. Using an access key for more than 12 months is considered bad security and is not recommended.

• Do not embed access keys directly into your code.

• Remove unused access keys.

Your organization may have different security requirements and policies than those described in this section. The suggestions provided here are intended as general guidelines.

Back to top