API Connect

Hi Team,

We trying to build API Connect v10 user defined Policy in that we used the Gateway Script Code.

We need to capture automatically Backend URL for that there is no context variable to get it, so we plan to use "service-metadata" for "var://service/URL-out".

and 

How to check the transaction flow there is no MPG's and we can enable the probe for services only.

Please solve my problem.

------------------------------
Ramesh Vankayala
------------------------------

Hello Ramesh, 

Apologies that this has taken so long to get an answer for. 

I went on and found the following documentation that might be helpful for you. Here is the link to it.

I think that the issue might come from the fact that The GatewayScript does not work with ice-metadata module, as the documentation states below:

:The GatewayScript assembly action can use all objects and modules that are supported by the traditional DataPower GatewayScript processing except for the following modules.

• fs module
• mgmt module
• policy module
• policy-utility module
• service-metadata module"
  
  I hope that this helps. 

------------------------------
Gabriel Marte Blanco
Austin TX
------------------------------

Original Message:
Sent: Wed August 10, 2022 11:18 AM
From: Ramesh Vankayala
Subject: In API Connect "service-metadata" code is not working and How to enable Probe there is no mpg

Hi Team,

We trying to build API Connect v10 user defined Policy in that we used the Gateway Script Code.

We need to capture automatically Backend URL for that there is no context variable to get it, so we plan to use "service-metadata" for "var://service/URL-out".

and 

How to check the transaction flow there is no MPG's and we can enable the probe for services only.

Please solve my problem.

------------------------------
Ramesh Vankayala
------------------------------

Hi Ramesh,

This had somehow missed my radar as well, my apologies.  The API Gateway Service doesn't have a request/response rule like a Multi-Protocol Gateway Service does, but only a single assembly rule. In a MPGW, "var://service/URL-out" references the url that is coming out of the end of the request rule, so it really would not apply to an API Gateway Service, which has only an invoke policy that sends request to the desired target-url (ie, no native proxy policy).  Exactly what is your requirement? Are you needing to know the url of the last invoke policy that was executed?

Regards,

Steve

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------

Original Message:
Sent: Wed August 10, 2022 11:18 AM
From: Ramesh Vankayala
Subject: In API Connect "service-metadata" code is not working and How to enable Probe there is no mpg

Hi Team,

We trying to build API Connect v10 user defined Policy in that we used the Gateway Script Code.

We need to capture automatically Backend URL for that there is no context variable to get it, so we plan to use "service-metadata" for "var://service/URL-out".

and 

How to check the transaction flow there is no MPG's and we can enable the probe for services only.

Please solve my problem.

------------------------------
Ramesh Vankayala
------------------------------

Hi Steve Linn,

--> Yes, We needing to know the URL of the last invoke policy, currently we store and get from APIC properties.

--> Can Graphql support v10 v5Compatable Gateway?, we getting gateway incompatible error!



------------------------------
Ramesh Vankayala
------------------------------

Original Message:
Sent: Tue October 18, 2022 12:01 PM
From: Steve Linn
Subject: In API Connect "service-metadata" code is not working and How to enable Probe there is no mpg

Hi Ramesh,

This had somehow missed my radar as well, my apologies.  The API Gateway Service doesn't have a request/response rule like a Multi-Protocol Gateway Service does, but only a single assembly rule. In a MPGW, "var://service/URL-out" references the url that is coming out of the end of the request rule, so it really would not apply to an API Gateway Service, which has only an invoke policy that sends request to the desired target-url (ie, no native proxy policy).  Exactly what is your requirement? Are you needing to know the url of the last invoke policy that was executed?

Regards,

Steve

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM

Original Message:
Sent: Wed August 10, 2022 11:18 AM
From: Ramesh Vankayala
Subject: In API Connect "service-metadata" code is not working and How to enable Probe there is no mpg

Hi Team,

We trying to build API Connect v10 user defined Policy in that we used the Gateway Script Code.

We need to capture automatically Backend URL for that there is no context variable to get it, so we plan to use "service-metadata" for "var://service/URL-out".

and 

How to check the transaction flow there is no MPG's and we can enable the probe for services only.

Please solve my problem.

------------------------------
Ramesh Vankayala
------------------------------

Hi Ramesh,

> Last url from invoke policy - This is not stored in the context for later retrieval.  Your approach of pulling the url from APIC properties or having a set variable policy that would set your own context variable to what the subsequent invoke policy's target url would be are the only approaches I can think of.  You'd need to submit a request for enhancement to have this url stored in the context for programmatic retrieval in a subsequent policy.  Use https://integration-development.ideas.ibm.com/?project=DPGWY (may require you to register first)

> Graphql support in v5c gateway - This is not supported.

Regards,

Steve

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------

Original Message:
Sent: Tue October 25, 2022 06:07 AM
From: Ramesh Vankayala
Subject: In API Connect "service-metadata" code is not working and How to enable Probe there is no mpg

Hi Steve Linn,

--> Yes, We needing to know the URL of the last invoke policy, currently we store and get from APIC properties.

--> Can Graphql support v10 v5Compatable Gateway?, we getting gateway incompatible error!



------------------------------
Ramesh Vankayala

Original Message:
Sent: Tue October 18, 2022 12:01 PM
From: Steve Linn
Subject: In API Connect "service-metadata" code is not working and How to enable Probe there is no mpg

Hi Ramesh,

This had somehow missed my radar as well, my apologies.  The API Gateway Service doesn't have a request/response rule like a Multi-Protocol Gateway Service does, but only a single assembly rule. In a MPGW, "var://service/URL-out" references the url that is coming out of the end of the request rule, so it really would not apply to an API Gateway Service, which has only an invoke policy that sends request to the desired target-url (ie, no native proxy policy).  Exactly what is your requirement? Are you needing to know the url of the last invoke policy that was executed?

Regards,

Steve

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM

Original Message:
Sent: Wed August 10, 2022 11:18 AM
From: Ramesh Vankayala
Subject: In API Connect "service-metadata" code is not working and How to enable Probe there is no mpg

Hi Team,

We trying to build API Connect v10 user defined Policy in that we used the Gateway Script Code.

We need to capture automatically Backend URL for that there is no context variable to get it, so we plan to use "service-metadata" for "var://service/URL-out".

and 

How to check the transaction flow there is no MPG's and we can enable the probe for services only.

Please solve my problem.

------------------------------
Ramesh Vankayala
------------------------------

Hi Ramesh,

Sorry as I missed part 2 of your question:

> How to check the transaction flow there is no MPG's and we can enable the probe for services only.

The API Gateway has a DataPower object named API Probe Settings that you can simply enable.  You can then use the Test tab of your API to send a sample request, and if the apim-debug HTTP header has a value of true, you should be able to follow a trace of the API's assembly flow and see the API Gateway context at the beginning of each policy that is to be executed.

Regards,

Steve

------------------------------
Steve Linn
Senior Consulting I/T Specialist
IBM
------------------------------

Original Message:
Sent: Wed August 10, 2022 11:18 AM
From: Ramesh Vankayala
Subject: In API Connect "service-metadata" code is not working and How to enable Probe there is no mpg

Hi Team,

We trying to build API Connect v10 user defined Policy in that we used the Gateway Script Code.

We need to capture automatically Backend URL for that there is no context variable to get it, so we plan to use "service-metadata" for "var://service/URL-out".

and 

How to check the transaction flow there is no MPG's and we can enable the probe for services only.

Please solve my problem.

------------------------------
Ramesh Vankayala
------------------------------