Explains some of the main components and concepts used in API Gateway policy development, and shows examples of how they are displayed in Policy Studio.
0 minute read
Quick reference to Policy Studio, including working with projects, deploying configuration, and adding APIs and web services to a project.
A Policy Studio project is a design-time store of API Gateway configuration on a local file system, which can be deployed to a running API Gateway instance on a server.
Learn about and set up the example policies available in the
samples directory of your API Gateway installation.
Learn how to configure policies manually, and how to configure global policies and policy assemblies.
Schedule the execution of any policy on a specified date and time.
Configure API Gateway to work with Apache ActiveMQ, IBM WebSphere MQ, and other messaging systems that support the JMS standard.
Learn how to configure both local and distributed caches in API Gateway, and how to configure a policy to cache responses.
Use a Key Property Store to store data that can be referenced by policies running on an API Gateway.
Configure alert destinations for API Gateway system alerts.
Import and export configuration data to share it in a development environment and to manage differences and references.
Compare the currently loaded API Gateway configuration with a configuration stored in a deployment package (
.fed file) and merge any differences.
Detect and analyze upgrade issues in Policy Studio.
A selector is a special syntax that enables API Gateway configuration settings to be evaluated and expanded at runtime based on metadata values (for example, from message attributes, a Key Property Store (KPS), or environment variables).
Configure preferences and viewing options for Policy Studio.
Check the compliance of your configuration against security standards.
Configure Oracle SSM and Kerberos settings.
Configure API Gateway to produce or consume messages for TIBCO Rendezvous.