Create the Instance for the Deposit Token Application

After you configure the rich history database profile, you create the instance for the application.

Do not complete the following steps until you have configured the rich history database profile.

1. In Blockchain Platform Manager, Select Instances, then select Create Instance.
2. Enter the required settings, including archive node count, member node count, and smart contract governance mode.
3. For Rich History DB Profile, select the profile that you created, which must be an Oracle Database profile, not an Internal DB profile.
   For more information about creating an instance, see Create an Instance in Administering Oracle Blockchain Platform Enterprise Edition for Besu.
4. To verify that rich history data is available, after the instance is created, deploy and initialize the deposit token application. For more information, see One-Click Application Deployment.
5. Run representative transactions, such as account creation, so that indexed rich history data is generated.
   The ORDS Script uses the exact table prefix before the following rich history tables.

   <BESU_TABLE_PREFIX>_more
   <BESU_TABLE_PREFIX>_store_state
   <BESU_TABLE_PREFIX>_store_hist

   For example, if the tables are named obpBesu_centralbank_123_more, obpBesu_centralbank_123_store_state, and obpBesu_centralbank_123_store_hist, set the following prefix. Use the exact database object prefix, including case. Do not supply a view name, a table suffix such as _more, or a fabricated deployment label.

   BESU_TABLE_PREFIX="obpBesu_centralbank_123"

You can now prepare and run the ORDS script.