Get started

Follow the steps in Get started with connectors before proceeding.

​

Prerequisites

• An active FusionFabric.cloud tenant (sandbox or production) with API subscriptions for the retail banking packs used by your journeys.
• Network connectivity between FFDC or Essence and Grand Central iPaaS. For more information, see Network connectivity.
• OAuth2 client credentials (client-id, client-secret) and a token URL from your FFDC app registration.

​

OAuth credentials (SOPS)

The following table lists SOPS secrets for FFDC client credentials. Set finastra.oauth.tokenUrl in the connector values.yaml file, not in SOPS. Test and development gc-finastra values files omit these SOPS secret names. The connectors forward Authorization and Ocp-Apim-Subscription-Key when the gateway uses subscription-key forwarding.

---

​

Configure the connector

To configure the Finastra Essence connectors, follow these steps:

1. Configure outbound connectivity to api.fusionfabric.cloud (or your regional FFDC or Essence host). For more information, see Network connectivity.
2. Configure Finastra authentication. Use OAuth2 client credentials against your FFDC token URL. Store finastra-client-id and finastra-client-secret in SOPS. For more information, see How to create SOPS.
3. Configure the environment in gc-applications-live. Configure connectors under values/gc-finastra/. Use these connector artifacts and values files:
   • gc-finastra-party-connector: party-v2.values.yaml for party operations
   • gc-finastra-deposit-connector: deposit-v0.values.yaml for deposit accounts
   • gc-finastra-deposit-transaction-connector: deposit-transaction-v0.values.yaml for deposit transactions
   For the full property list for each connector, including defaults and descriptions, see Reference.
4. Set the property keys the connectors read. Set finastra.base.url and the Essence path properties listed in Reference. Confirm values against your environment values.yaml file. Don’t copy sandbox paths into production without validation. For example:
   # gc-applications-live/runtimes/<env>/values/gc-finastra/party-v2.values.yaml
   connector:
     existingSecretName: finastra   # SOPS: finastra-client-id, finastra-client-secret
     properties:
       # finastra.oauth.tokenUrl: https://api.fusionfabric.cloud/login/v1/sandbox/oidc/token
       finastra.party.path: /bfweb/retail/v1/party
       finastra.party-search.path: /bfweb/retail/v1/party/partysearch
     traits:
       knativeservice:
         minScale: 0
       logging:
         level: INFO
   
   # deposit-v0.values.yaml
   connector:
     properties:
       finastra.create-casa.path: /bfweb/retail/v1/accounts/currentsavings
       finastra.get-casa.path: /bfweb/retail/v1/accounts/currentsavings
       finastra.get-account-details.path: /bfweb/retail/v1/accounts/account-details
       finastra.get-fd.path: /bfweb/retail/v1/accounts/fixeddeposits
       finastra.get-account.path: /bfweb/retail/v1/accounts
       finastra.casa.deposit-types: CURRENT_ACCOUNT,SAVINGS_ACCOUNT
   

​

Testing

The following table lists the header you need for API testing. Use X-Request-ID on party and deposit calls for correlation. Test the API using the Postman collection.

​

Troubleshooting

The following table lists common symptoms and what to check.

​

Next steps

• Overview: use cases and operation tables
• Reference: configuration properties and error mapping