API Gateway
Beginning with release 10.15, API Gateway deprecates support for webMethods Deployer and the Asset Build Environment. For information about the deployment and staging functions that API Gateway supports and that you can use to replace Deployer and ABE, see the API Gateway documentation.
You can deploy the following API Gateway assets with webMethods Deployer:
APIs
Policy
Policy actions
Aliases
Packages
Plans
Administrator Settings
Assertions
API Gateway does not stage the following API Gateway assets:
Approval Configurations
Access Profiles
API Gateway cannot stage the following assets, but you can stage them as Integration Server assets:
Users
Groups
Keystores
Truststores
Outbound Proxy
URL Aliases
When using API Gateway Assets, note the following points:
APIs, global policies, and packages are maintained in the same state on the target servers as the state they had when built into composites using
Asset Build Environment.
In
webMethods Deployer, you cannot redeploy an API that already exists in Active state.
You cannot delete administrator settings and assertions using a deletion set.
When deploying partial composites that have hard dependencies, for example policy actions for policies, the dependent assets are added in the deployment set automatically.