IBM C1000-138 Exam Dumps

Setting Context Variables: In Gatewayscript policies, thecontext.setfunction is used to set context variables. The syntaxcontext.set('my.vars.amount', 100)creates a JSON structure wheremy.varsis an object containing the keyamountwith the value100.

JSON Structure: This method of setting context variables generates a JSON structure, which is a common format for data interchange in APIs. The resulting structure would be{ 'my.vars': { 'amount': 100 } }.

Usage in Policies: This approach allows for easy manipulation and access to variables within the GatewayScript, facilitating dynamic API behavior based on the context.

Documentation Reference: According to the IBM Certified Solution Implementer - API Connect v10.0.3 documentation, usingcontext.setin this manner is the correct way to generate the specified JSON structure1.

1:IBM Certified Solution Implementer - API Connect v10.0.3 Documentation

In IBM API Connect v10.0.3, rate limiting for APIs can be defined in two primary places: Plan and Catalog.

Plan: Rate limiting is typically defined at the Plan level. A Plan in API Connect specifies how an API or a group of APIs is exposed to consumers. It can include rate limits, quotas, and other restrictions. Defining rate limits at the plan level ensures that each application subscribed to the plan adheres to the specified API consumption limits, such as the number of API calls allowed within a given time period.

Catalog: The Catalog is another place where rate limits can be defined. A Catalog represents a collection of APIs and their configurations, including security and rate limiting policies. Rate limits defined at the Catalog level apply globally to all APIs and applications within that Catalog, providing an overarching control mechanism to enforce consumption limits across different APIs.

These two locations allow flexibility in controlling API usage, either by restricting usage per plan (at a more granular level) or globally across all APIs within a catalog.

IBM API Connect v10.0.3 - Now Available

IBM API Connect Documentation

To find all Products in a specific Provider organization using the API Connect CLI, you can use the following command:

products:list --realm [providerOrg]

This command will list all Products that belong to the specified Provider organization. You can then use additional filtering options to find Products based on specific criteria, such as their creation date or status.

IBM API Connect: API Connect CLI Reference

IBM API Connect: Managing Products with the CLI

The Developer Portal in API Connect supports the following image formats:

JPEG (.jpg): This is a widely used image format that is commonly used for photos and other images.

GIF (.gif): This format is often used for animated images and simple graphics.

While other formats may be technically possible to use in the Developer Portal, these two are the most widely supported and recommended formats.

IBM API Connect: Developer Portal User Guide

IBM API Connect: Creating and Managing Products

API Connect supports two grant types for native and third-party OAuth providers:

Application (client-credentials): This grant type is used when the application itself is the client and does not require user interaction. It is suitable for machine-to-machine authentication.

Implicit: This grant type is used when the application obtains an access token directly from the authorization server without going through a redirect URI. It is suitable for web applications that are embedded in other applications.

IBM API Connect: Configuring a native OAuth provider

IBM API Connect: Configuring a third-party OAuth provider

OAuth 2.0 Authorization Framework: https://datatracker.ietf.org/doc/html/rfc6749