Skip to main content
Follow the steps in Get started with connectors before proceeding. Oracle FLEXCUBE access: An active account in the Oracle FLEXCUBE production or test environment. Network connectivity: Verify that your network routes traffic between the Oracle FLEXCUBE environment and Banking OS Connectivity. For supported options, see Network connectivity. Environment details: You need the following environment details from Oracle FLEXCUBE:

​
Prepare the connector

Backbase deploys this connector. To share connectivity details and provide the environment details, follow these steps:
  1. Share connectivity details. Share connectivity details between Banking OS and Oracle FLEXCUBE as described in Network connectivity.
  2. Send environment details to Backbase. Send flexcube.baseUrl, flexcube.source, flexcube.ubsComp, flexcube.userId, and flexcube.branch to your Backbase support team.
For property names and defaults, see Reference.

​
Testing the connector

To use the Unified API, include your Banking OS subscription key in the request header. If you don’t have a key, contact your Backbase support team to request one. Test the API using the Postman collection.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Banking OS gateway cannot establish a handshake with the Oracle FLEXCUBE endpoint. This typically indicates an upstream service outage at Oracle or a network routing failure.Solution: Verify the operational status of the Oracle FLEXCUBE environment. Check Oracle’s status page or contact Oracle support.
Cause: The request to Oracle FLEXCUBE exceeded the configured timeout period. This may indicate performance issues at Oracle or network latency problems.Solution: Verify the operational status of the Oracle FLEXCUBE environment and check for any performance degradation.
Cause: The JMS URL for the Oracle FLEXCUBE notification system is incorrect or the queue is unreachable.Solution: Contact your Backbase support team to verify the jmsFlexCubeUrl configuration and the queue name.
Cause: The authentication credentials provided during setup are incorrect, expired, or the user lacks the required permissions in Oracle FLEXCUBE.Solution: Re-verify your credentials with your Oracle FLEXCUBE administrator, and ensure the user has the required permissions. Contact your Backbase support team to update the connection credentials if needed.
Cause: The number of incoming requests exceeds the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Banking OS and Oracle FLEXCUBE infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact your Backbase support team to request a higher rate limit.