Deployment - API Gateway

Before deploying a global package, ensure that all deployment prerequisites are met.

Prerequisites

The Global Packages feature must be enabled for the target environment through Feature Enablement in CSSP.
The Global Package must be entitled to your company. See https://docs.infor.com/sspl/latest/en-us/cssplib/default.html?helpcontent=config_mgt/emp1723144420593.html.
Deploy all dependent global packages in the target tenant before you begin.
The user performing the deployment must have the IONAPI-Administrator role.

First deployment of an editable package

When you deploy an editable global package to a target tenant for the first time, API Gateway automatically creates two instances for each resource in the package:

Live (working) instance — the customer-owned copy that you can configure and use.
Reference template instance — a read-only system-owned copy that represents the Infor-delivered baseline.

Both instances are created with the same content as delivered in the package. After deployment, any changes you make to the live instance are independent of the reference template.

Subsequent deployment of an editable package

When you deploy an editable global package to the same target tenant again, API Gateway updates the reference template instance to match the latest content delivered in the package. The live instance is not changed and continues to work as expected.

Global Packages parameters

The package parameters allow you to enter customer-specific values during deployment so that imported resources are configured automatically after deployment.

You can configure resources during global package deployment by using these parameter inputs:

API Key Value for Endpoints using API Key Target Authentication.
AWS Access Key ID and AWS Secret Access Key for Endpoints using AWS Signature.
User ID and Password for Endpoints using Basic Authentication.
GoogleServiceAccountFile for Endpoints using Google Service Account Target Authentication.
IONAPIBridgeFile for Endpoints using IONAPI Bridge Authentication.
JWT Header, JWT Payload, and Key ID for Endpoints using JWT Target Authentication.
Target Endpoint Access Key and Secret Key for Endpoints using OAuth 1.0a Target Authentication.
Username, Password, Client ID, Client Secret, JWT Header, Payload, Private Key, Passphrase, Key ID for Endpoints using OAuth2.0 Target Authentication.
Username and Password for Endpoints using WS Security Target Authentication.
Signing Certificate Fingerprint for Android-type Authorized App.