Setting Context Variables : In Gatewayscript policies, the context.set function is used to set context variables. The syntax context.set( ' my.vars.amount ' , 100) creates a JSON structure where my.vars is an object containing the key amount with the value 100.

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, using context.set in this manner is the correct way to generate the specified JSON structure 1 .

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

In IBM API Connect, an app is typically associated with a single Client ID and secret to maintain a unique identity and secure access to APIs. Each app is expected to use this unique Client ID and secret for authentication and authorization purposes. Therefore, only one Client ID and secret pair is allowed per app, and additional Client IDs and secrets cannot be requested or generated for the same app.

In IBM API Connect v10.0.3, the product_name field in the API Event Record will indicate " N/A " if a client ID is not used or is invalid on the API. This field typically shows the name of the API product associated with the request, but if no valid client ID is present, it cannot associate the request with a product, resulting in " N/A. "

Other options are incorrect:

api_id would display the API identifier.

log_policy relates to the logging policy and would not be " N/A " due to an invalid client ID.

org_id refers to the organization ID and is unrelated to client ID validity.

References :

IBM API Connect v10.0.3 Documentation: API Event Record Fields

The Consumer APIs should be used to register users in the Developer Portal, create applications, and subscribe to APIs. These APIs provide the necessary endpoints and functionality for Consumers to interact with the Developer Portal and manage their API usage.

References:

IBM API Connect: Consumer APIs

IBM API Connect: Using the Consumer APIs

When a developer selects " Secure using Client ID " in API Connect, the required header for executing the API is X-IBM-Client-Id . This header is used to authenticate the client and ensure that it has the necessary permissions to access the API.

References:

IBM API Connect: Securing APIs with Client IDs

IBM API Connect: API Security

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.

References:

IBM API Connect: API Connect CLI Reference

IBM API Connect: Managing Products with the CLI

In IBM API Connect v10.0.3, if a Catalog associated with the Developer Portal has two gateway services enabled , and each of these gateway services is associated with different analytics services , the Developer Portal will not display any analytics data. This is because IBM API Connect does not support combining or displaying analytics data from multiple analytics services in a single portal view.

Each gateway service would be linked to its own analytics service, and since the Developer Portal is designed to integrate with a single analytics service per Catalog, conflicting analytics configurations prevent the display of any analytics data. As a result, the system does not display any statistics like API calls, response times, or error rates in the Developer Portal when multiple analytics services are configured.

References:

IBM API Connect Documentation

IBM API Connect v10.0.3 - Now Available