One-Click Deploy the Wholesale CBDC Application

One-click deployment prepares the required back end services and supplies the application configuration.

One-click deployment provisions and connects the following application components.

  • Besu wholesale CBDC smart contract and deployment metadata, which provides the token operations and contract details that are used by the application.
  • Besu wrapper API, which provides the application API for contract and account operations.
  • Rich history database objects and scripts, which store transaction and operation history.
  • Wholesale CBDC ORDS deployment and configuration, which exposes history and related back end services.
  • Wholesale CBDC web application and service configuration, which connects the UI to the deployed back end services.

One-click deployment also prepopulates the Setup page with service endpoints, contract addresses, UWaaS and wallet settings, OIDC or LDAP settings, ORDS settings, and the packaged default customizations. Users do not need to enter these back end or identity provider values again. Only the wholesale CBDC token ID is required on the Setup page. Optional user-facing customizations can also be changed there.

Before you begin, you need the following information.

  • The target Oracle Blockchain Platform instance where the wholesale CBDC application will be deployed.
  • The wholesale CBDC token ID, to connect the application to the deployed token contract.
  • Bootstrap user details that were supplied during when the smart contract was initialized, which identify the first central bank administrator and provide initial administrative access.
  • Optionally, display name, logo, currency, organization, or role label changes, which control the interface that users see after setup.

Complete the following steps for one-click deployment

  1. Start the wholesale CBDC one-click deployment in Blockchain Platform Manager for the selected instance.
  2. Wait until the smart contract, wrapper API, rich history, ORDS, and application components report a successful or ready state. This confirms that the application dependencies are available.
  3. Open the application URL. The /setup page is displayed because deployment has completed the back end setup but the application configuration is not complete yet.
  4. Enter the wholesale CBDC token ID and review the prefilled values. Do not replace back end values unless you are making an actual change to the deployment.
  5. Optionally, change the user-facing customization values, and then select Apply Changes. This validates the required fields, saves the token ID and customization values, combines them with the prefilled deployment configuration, and applies the resulting configuration to the application.

After you select Apply Changes, wait for the configuration update or redeployment to complete. The application then returns to the sign-in page. The central bank administrator and financial institution administrator can sign in without a CBDC account if their selected wallet already has the matching Token Admin or Org Admin Besu contract role. Every persona still needs an eligible wallet; other personas also need an active CBDC account. One-click deployment does not create users, wallets, or CBDC accounts.