| OPENSHIFT | |
 | OpenShift enabling the Image Registry route and pushing image. |
|
When installing OpenShift 4.3+ there is no default route created for the image registry. Therefore we are unable to load in images from outside of the cluster. |
|
|
|
|
| API CONNECT | |
 | Calling DB2's Rest interface from API Connect |
| Guest Post by Lars Fanebost | |
|
Lars Fanebost put together this awesome guide on calling DB2 from inside of API connect. This is taken from https://github.com/lfanebost/api-connect-exposing-db-data-pub/ |
|
|
|
|
| API CONNECT | |
|
| Custom Client ID and Client Secret values |
|
From API Connect V5 and onwards users have been able to customise the Client ID and Client Secret values on applications. But this is a rarely known gem. This article will explains the API calls required to do this. |
|
|
|
|
| API CONNECT | |
|
| Vanity URLs in APIConnect v2018 and onwards |
|
API Connect v2018 has the ability to configure vanity Urls for the API Endpoints . Vanity URLs allow the api developer/administrator to change how the endpoint is rendered in the API Connect Developer portal. This is useful if you wish to go via a CDN or there is a requirement for each catalog having a different URL subdomain. |
|
|
|
|
|
MQ | Enable TLS for ACE HTTPS calls |
| Guest Post by Mannie Kagan | |
|
When making calls from ACE to https endpoints the trust store must contain the certificate for the target endpoint. In ACE this is done by creating a secret and reference it in the help chart. This article provides instructions on how to do this. |
|
|
|
|
| API CONNECT | |
|
| User Defined Policies / Custom Policies in API Connect 2018 (MQ invoke Example) |
|
User Defined Policies (aka Custom Policies) allow a customer to provide a bespoke piece of function as a policy in the API Designer Pallet. In this example I will explain the different pieces that need to be constructed to build an MQ Invoke Policy. |
|
|
|
|
| API CONNECT | |
|
| DataPower Quorums with two DataPowers |
|
Ways to handle the DataPower quorum when there is only enough Licenses for two DataPowers. THIS HAS BEEN UPDATED - https://chrisphillips-cminion.github.io/apiconnect/2022/10/19/APIC-DataPowerQuorum2Node0.html |
|
|
|
|
| API CONNECT | |
|
| Chatbot with Twilio via API Connect |
|
Chatbots have been a current fashionable project to work on right now. An API Gateway is critical to help take the load off the main business application as well as providing a way to implement multiple Chatbot intermediaries without rewriting the business logic.
|
|
|
|
|
| API CONNECT | |
|
| API Connect - Switching the DataPower Peering Primary |
|
In the event that a DataPower quorum is lost the remaining DataPowers can be forced into a working quorum. |
|
|
|
|
| API CONNECT | |
|
| API Connect - Deploying Components to specific Nodes |
|
API Connect has four components, there is a requirement to deploy the DataPower Gateway to their own worker nodes in Kubernetes. |
|
|
|
|
|
| ABOUT | APICONNECT | API | DATAPOWER | OPENSHIFT | EVENTSTREAMS | INTEGRATION | DAY2-OPS | ACE |
