Skip to main content

Prerequisites

  • Helm chart connector artifacts published to the enterprise artifactory at repo.backbase.com.
  • Access to gc-<customer>-applications-live and gc-devhub-<customer>-applications-live.
  • Create the required secrets with connector properties in the Kubernetes key vaults.

Requests to submit

Submit a request to establish Private Link connectivity between the Enterprise Backbase Platform (EBP) and the Grand Central (GC) platform with the BaaS team. EBP can use the Private Link connection by defining a hostAlias on the connecting integration service.
Contact your BaaS team representative for the Private Link connectivity setup steps and configuration details.

Deploy GC connectors

  • Create the required runtimes in the gc-<customer>-applications-live project in the GitHub organization provisioned for your project.
  • Deploy the required Secrets Operations (SOPS) secrets under runtimes/[env]/secrets. This includes OAuth client credentials, username/password, mTLS certificates, and similar items.
Contact your BaaS team representative for instructions on creating SOPS secrets and using them in connectors.

Deploy Azure API Management (APIM) components

  • Deploy APIM components through Argo CD. These configurations use Helm charts in YAML files for deployment.
  • The supported components are APIs, Named Values, Policy Fragments, Backends, Credential Managers, Products, and Subscriptions.
  • Argo CD automatically syncs and deploys the configurations as specified.
The version numbers in the following samples are illustrative. Check your shared Azure Container Registry (ACR) for the versions available in your environment.

1. Deploy unified APIs

Under main/runtimes/dev/apim/apis, add the following YAML configurations. For example, if you need to set up deposit and payment GC specs in the Azure APIM APIs: Add deposit-api.yaml:
Add payment-api.yaml:

2. Deploy API version sets

Add apiversionsets.values.yaml:

3. Deploy connector backends

Add backend.values.yaml under main/runtimes/dev/apim:

4. Deploy product policy fragments

Add policyfragments.values.yaml under main/runtimes/dev/apim:

5. Deploy products

Add products.values.yaml under main/runtimes/dev/apim:

6. Deploy subscriptions

Add subscription.values.yaml under main/runtimes/dev/apim:

7. Deploy connector values

Deploy the connector configurations under the values folder of the runtime. This includes secret names, connector configurations such as vendor system base URL, security token type, connection parameters, and similar items. Add deposit-v0.values.yaml under main/runtimes/dev/values/gc-flexcube:
Add payment-v0.values.yaml under main/runtimes/dev/values/gc-alacriti:

8. Deploy connectors

Deploy the GC connectors using the configuration under the apps folder. This configuration downloads the connector Helm charts from the enterprise shared repository at gcshared671.azurecr.io/charts. Add main/runtimes/dev/apps/gc-flexcube.yaml to deploy the GC managed connectors and the wiremock services for the mocked responses:

9. Deploy Istio configurations (optional)

Deploy Istio configurations for secure outgoing connectivity from Kubernetes. The setup uses the Istio egress gateway with all necessary components such as serviceEntries, virtualServices, destinationRules, and similar items. Add values.yaml under main/runtimes/dev/istio:

Deploy Sync Hub components

  • (Optional) Deploy the required platform components such as Sync Hub configurations for Azure Service Bus (ASB) topic, subscriptions, and similar items.
After you deploy all components, retrieve the Azure APIM subscription key for the product you created through the Argo CD deployments from the Azure portal.

Manage feature flags and custom configuration properties

Add feature flags

  • Configure the feature flags as required by the connectors in the runtime’s values configuration. Based on the implementation of the feature, the connector can handle the flow.

Add or modify data fields

  • Override the GC transformation mappings under the specific values resource of that API for any data mapping required for a specific integration API.

Add custom fields

  • Add any custom fields (additions) that you need in the same values resource-transformation mappings.
The following example shows deposit API custom field additions for the Flexcube deposit connector, including custom fields such as OFFSACC and PERCENTAGE.
In both cases, add the entire transformation resource file (included in managed connectors) along with the new, modified, or custom data mapping fields.

Test the connectors

Use Postman to test the GC APIs by passing the APIM product subscription key as the api-key header value. GC unified API Web Application Firewall (WAF) endpoint base URL: api.[runtime].[customer].gcservices.io Argo CD: https://argo.[runtime].[customer].gcservices.io/