Features: QuickStart Templates

Easily publish and modify services on the gateway using QuickStart templates and a JSON document.

JSON Meta-Policy for the CA Microgateway

The CA Microgateway uses a JSON meta-policy to provision the Gateway. This allows you to build your policies offline and then submit them to the Gateway without needing to use the Policy Manager.

The QuickStart online documentation lists the JSON meta-policies for each of the predefined encapsulated assertions.

You can deploy the JSON meta-policy using either of the following scenarios:

Scenario 1: Fluid environment, with possible frequent API changes (Dynamic API Mode)

Scenario 2: Strong governance required, APIs seldom change (Fixed API Mode)

JSON Meta-Policy for the CA Microgateway

The CA Microgateway uses a JSON meta-policy to provision the Gateway. This allows you to build your policies offline and then submit them to the Gateway without needing to use the Policy Manager.

The QuickStart online documentation lists the JSON meta-policies for each of the predefined encapsulated assertions.

You can deploy the JSON meta-policy using either of the following scenarios:

Scenario 1: Fluid environment, with possible frequent API changes (Dynamic API Mode)

Scenario 2: Strong governance required, APIs seldom change (Fixed API Mode)

Using the CA Microgateway in Dynamic API Mode

In the Dynamic API mode, you can publish and change your APIs at any time. There is no need to redeploy the CA Microgateway.

This is the default mode and is ideal for environments where the lifecycle of an API is not tied to the lifecycle of the microgateway container.

Using the QuickStart Templates, you can publish, update, or delete a service at any time. Simply modify the JSON payload and then submit it to the CA Microgateway. This topic uses curl commands as examples, but you can use your preferred method for submitting REST commands.

Using the CA Microgateway in Dynamic API Mode

In the Dynamic API mode, you can publish and change your APIs at any time. There is no need to redeploy the CA Microgateway.

This is the default mode and is ideal for environments where the lifecycle of an API is not tied to the lifecycle of the microgateway container.

Using the QuickStart Templates, you can publish, update, or delete a service at any time. Simply modify the JSON payload and then submit it to the CA Microgateway. This topic uses curl commands as examples, but you can use your preferred method for submitting REST commands.

Using the CA Microgateway in Fixed API Mode

In the Fixed API mode, the CA Microgateway retrieves the JSON payload from a predetermined directory. This API is then "fixed" for the life of the Docker container and cannot be changed unless you shut down the CA Microgateway and redeploy it with a new custom image.

This mode is ideal for environments where tight governance is required and the lifecycle of the API matches the lifecycle of the Microgateway container.

Using the CA Microgateway in Fixed API Mode

In the Fixed API mode, the CA Microgateway retrieves the JSON payload from a predetermined directory. This API is then "fixed" for the life of the Docker container and cannot be changed unless you shut down the CA Microgateway and redeploy it with a new custom image.

This mode is ideal for environments where tight governance is required and the lifecycle of the API matches the lifecycle of the Microgateway container.

Chat
What would you like to chat about?
Support
Contact
Call us at1-800-225-5224
Call us at1-800-225-5224
Contact Us