API Gateway
You can deploy the following API Gateway assets with webMethods Deployer:
![*](chapterTOC_bullet.png)
APIs
![*](chapterTOC_bullet.png)
Policy
![*](chapterTOC_bullet.png)
Policy actions
![*](chapterTOC_bullet.png)
Aliases
![*](chapterTOC_bullet.png)
Packages
![*](chapterTOC_bullet.png)
Plans
![*](chapterTOC_bullet.png)
Administrator Settings
![*](chapterTOC_bullet.png)
Assertions
API Gateway does not stage the following API Gateway assets:
![*](chapterTOC_bullet.png)
Approval Configurations
![*](chapterTOC_bullet.png)
Access Profiles
API Gateway cannot stage the following assets, but you can stage them as Integration Server assets:
![*](chapterTOC_bullet.png)
Users
![*](chapterTOC_bullet.png)
Groups
![*](chapterTOC_bullet.png)
Keystores
![*](chapterTOC_bullet.png)
Truststores
![*](chapterTOC_bullet.png)
Outbound Proxy
![*](chapterTOC_bullet.png)
URL Aliases
When using API Gateway Assets, note the following points:
![*](chapterTOC_bullet.png)
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.
![*](chapterTOC_bullet.png)
In
webMethods Deployer, you cannot redeploy an API that already exists in Active state.
![*](chapterTOC_bullet.png)
You cannot delete administrator settings and assertions using a deletion set.
![*](chapterTOC_bullet.png)
When deploying partial composites that have hard dependencies, for example policy actions for policies, the dependent assets are added in the deployment set automatically.