Connect Bridge for Git to Endevor Web Services/MF Webhook through Zowe APIML
search cancel

Connect Bridge for Git to Endevor Web Services/MF Webhook through Zowe APIML

book

Article ID: 375246

calendar_today

Updated On:

Products

Endevor

Issue/Introduction

Is there any way to connect Bridge for Git to Endevor web services/webhook on the mainframe through the Zowe APIML?

Environment

Endevor V19

Bridge for Git 2.15.2

Resolution

Registering Endevor Web Services to the Zowe API Mediation Layer provides access to the Endevor REST API through the API Mediation Layer Gateway. For more information, check out Integrate REST API with the Zowe API Mediation Layer

It is not possible to integrate Bridge for Git (B4G) with API ML in terms of accessing B4G through API ML. B4G is not primarily a mainframe product, it does not provide a mainframe related API and B4G does not use mainframe credentials for login. 

It is not possible to integrate MF Webhook server with API ML. Webhook server does not expose any API to integrate, communication for webhook server is outbound from mainframe, not inbound to mainframe. 

 

Multiple method can be used to connect B4G to Endevor Web Services (EWS) that are APIML enabled:

  1. Connect to the EWS directly (if network configuration allows) - basically ignoring the fact that it is API ML enabled and continue working as before.
  2. Connect to EWS through API ML using password - just specify different Web Services URL when creating Endevor Connection in B4G.
  3. Connect to EWS through API ML using SSO token - the same as above, when creating new connection, specify 'Show advanced options' and 'Login method' as 'Log in with API Mediation Layer', this will allow using client certificate to login, mainframe password is not stored in the database using this method.
  4. Connect to EWS through API ML using personal access token -  the same as above, pecify 'Login method' as 'Log in with API Mediation Layer Personal Access Token', this one use different type of tokens. 

 

Note that additional Endevor/APIML configurations are required for using method 2,3,4 (enabling SSO/passtickets for Endevor, enable refresh endpoint for API ML, enable client certificate login for API ML, enable PATs for API ML).