Skip to main content

​
Prerequisites

Before initiating the configuration, ensure you have the following credentials and connectivity in place:
  • Make sure that you have followed Get started with connectors.
  • OBPM Access: An active account in the Oracle Banking Payments Manager environment with FX rate access.
  • Network Connectivity: Confirmed routing between the OBPM environment and the Grand Central (GC) iPaaS.
  • Environment Details: The following environment variables are needed from OBPM to configure the connector:
KeyDescription
obpm.baseUrlThe base URL to access the OBPM environment
obpm.client_idOAuth client ID for authentication
obpm.client_secretOAuth client secret for authentication

​
Configuration guide

Follow these steps to initialize and authorize your OBPM Exchange Rate connector.

​
1. Establishing connectivity

Share the following details with the Grand Central team to establish secure connectivity between Grand Central and OBPM:
  • Environment Details: baseUrl and ipaddress of the OBPM application.
  • OAuth2 Credentials: client_id and client_secret for OAuth token generation.

​
2. Environment configuration

Define your environment variables in the gc-applications-live repository within the fx-rates-v0.values.yaml file.
KeyDescription
obpm.baseUrlTarget API endpoint for the OBPM gateway.
obpm.client_idOAuth client ID assigned by Oracle.
obpm.client_secretOAuth client secret assigned by Oracle.
obpm.fx.defaultCurrencyDefault base currency for rate lookups.
Below is a sample fx-rates-v0.values.yaml: 
# Sample OBPM exchange rate environment configuration
obpm.baseUrl: "https://api.obpm.sandbox.com"
obpm.client_id: "your_client_id"
obpm.client_secret: "your_client_secret"
obpm.fx.defaultCurrency: "USD"
Below is the path where the fx-rates-v0.values.yaml needs to be placed: 
├── iPaaS
└── azure/runtimes
    ├── dev
    └── test
        └── values
            ├── gc-obpm-fx
                └── fx-rates-v0.values.yaml

​
Testing your integration

To access the Exchange Rate Unified API, you must include your Grand Central subscription key in the request header. If you do not have a key, please contact the Grand Central Support Team to have one provisioned.
KeyValue
api-key<your_subscription_key>
Test the API using the Postman Collection.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Grand Central (GC) gateway cannot establish a handshake with the OBPM endpoint. This typically indicates an upstream service outage at Oracle or a network routing failure.Solution: Verify the operational status of the OBPM environment with Oracle. If the service is operational, contact GC Support.
Cause: The request to OBPM timed out before receiving a response. This may indicate high latency or an unresponsive endpoint.Solution: Verify the operational status of the OBPM environment. If the service is operational, contact GC Support.
Cause: The requested currency pair is not available in the OBPM FX rate feed.Solution: Verify that both currencies are supported by your OBPM configuration. Contact Oracle to add support for additional currency pairs if needed.
Cause: The client_id or client_secret provided during setup is incorrect.Solution: Re-verify your credentials with the Oracle portal and contact the GC team to update the connection.
Cause: The number of incoming requests has exceeded the defined threshold for your subscription tier.Solution: Review your application’s request patterns to identify unexpected spikes. Consider caching FX rates for short periods to reduce API calls.

​
Need more help?

Contact support

Reach out to the Grand Central team for assistance with environment setup or rate limit increases.