Promoting Assets from API Gateway User Interface
Before you begin
- You must define a stage to represent the asset's lifecycle such as development, test, and production. For details about how to add a stage, see Adding a Stage.
- You must have the Manage promotions functional privilege assigned to perform this task.
About this task
Promoting assets from one (source) stage to another (target) stage includes the following high-level steps:
- Authorization server promotion: Promote
Authorization server in one of the following ways:
- Export the authorization server from one environment and import it into another, if you want to use the same authorization server across multiple environments.
- Create the authorization server with the same name as in the current environment, if you want to use a different authorization server instance.
Proceed to the next step once the authorization server is ready.
- Select assets for promotion: During this step,
you search for assets by using a keyword and by performing a type search that
sorts and filters the results.
- Search using a keyword. You can search for all assets whose string attributes (asset name, description, and so on) contain a certain keyword (character string).
-
Search using a Type. You can
search for assets on the basis of types.
You may use the Search by type filter to restrict the types on which the search is conducted. In the Search by type panel, API Gateway shows you a list of supported asset types.
- Search by team. You can search for assets assigned to team(s). Click the team(s) to view the assets that are assigned tot he selected team(s).
- Search using two keywords.You can provide more than one keyword by separating the keywords using a pipe symbol (|). For example, to search for assets whose names contain pet and test, you can provide pet|test in the search field.
- Search using wild card characters. You can use wild card characters in your search keyword. For example, to list all assets that start with graph, you can provide graph*.
- Optionally select assets' dependencies for
promotion: During this step, you specify whether the dependencies (for
example, a list of applications that are registered for an API, subscriptions
for a package, and so on) of the selected assets will be included for the
promotion.
Note: As groups and users are part of the team, if you want to promote the Groups and Users (optional dependencies) of the team that the selected asset belongs to, you have to set the enableTeamWork extended setting to true. Only then the Groups and Users sections appear.
- Select the stages to promote: During this step, you specify one or more target stages to which you want to promote the selected assets and their dependencies.
- Configure the promotion details: During this step, you provide the promotion-specific information.
- With API Gateway version 10.15 Fix 19, you can promote assets from API Gateway versions 11.0 and 11.1 into version 10.15.
However, the following restrictions apply:
- You cannot promote Keystores and Truststores from API Gateway 11.0 and 11.1 to version 10.15.
- You cannot promote Approved Configurations from API Gateway 11.0 and 11.1 to version 10.15.
- You cannot promote the standard teams - Administrators, API-Gateway-Providers, and Default from API Gateway 11.0 and 11.1 to version 10.15.
Important: If you plan to perform bulk promotion of assets from a source stage
to a target stage, Software AG recommends you to perform the following:
- Increase the value of maxRegexLengthInSearchQuery setting on the Extended Settings page under Administration > General in both the source and target stages, considering that the generated RegEx search query length may become longer during bulk promotion of assets. The default value of this property is 37000. When you increase the value, it can lead to higher memory and CPU utilization, particularly when dealing with complex regular expressions. Therefore, Software AG recommends to closely monitor any spike in memory and CPU usage while promoting assets. For example, if your RegEx search query's length is more than 37000, asset promotion fails indicating that the length of RegEx used in RegEx Query request has exceeded the allowed maximum. In such case, you must increase the value of maxRegexLengthInSearchQuery setting to more than the value specified in the error message.
- Increase the value of the
pg.gateway.elasticsearch.http.socketTimeout property, located
at
SAG_Install_Directory/IntegrationServer/instances/IS_Instance_Name/packages/WmAPIGateway/config/resources/elasticsearch/config.properties
. The default value of this property is 3000. To bulk promote assets, for example, 50 numbers, you would set the value of this property to 60000. Depending on the number of assets you want to promote, increment the value as 70000, 80000, and so on. You must restart API Gateway for changes to this property to take effect.
To promote assets