Pre-General Availability: 2026-03-13

Create an Instance

After you install Blockchain Platform Manager, you can create an instance of Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu.

Deploying the stack (or manually installing the distribution package) creates Blockchain Platform Manager, which you can use to provision, configure, and manage instances of Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu. Instance nodes run on a set of available Kubernetes worker nodes.

You use Blockchain Platform Manager to complete the following tasks:

• Create, start, stop, and delete instances of Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu.
• View details about all instances and activity records for all instances.
• Configure, activate, and use the LDAP service. You can use the built-in OpenLDAP service or your own LDAP server.
• Create and save user accounts.

Before You Begin

Review the Application Information page, which shows details about the Blockchain Platform Manager, Kubernetes cluster, and Terraform output.

• Note the ingress gateway IP address, which is used for Blockchain Platform Manager, and the ingress IP address for instance services, which is used by the service console and RPC gateway.
• Full job logs, including jump host details and Terraform logs, are available under Jobs.

To ensure proper host name resolution, add entries to your local etc/hosts or C:\Windows\System32\drivers\etc\hosts file for Blockchain Platform Manager and OpenLDAP fully-qualified domain names. For a production environment, use DNS and certificates instead of etc/hosts file mappings. Add entries similar to the following example, where the the ingress IP address is the ingress gateway IP address shown in the installation output.

<ingress-ip> controlplane.<domainname> openldap.<domainname> auth.<domainname> 

To create an instance:

1. Open Blockchain Platform Manager (https://controlplane.domainname/console/index.html)
   Your browser might warn you about a self-signed certificate.
2. Log in to Blockchain Platform Manager by using the obpadmin user name and the password that you provided during installation.
3. Activate and test the default OpenLDAP authentication server.
   1. Select Configuration, and then Authentication Servers.
   2. Select the Default authentication server, then select Save and Set active.
4. Add an instance administrative user to the system. Do not use the Oracle Blockchain Platform administrator account for routine tasks. Log out and then log back in as the new user.
   1. On the Authentication Servers tab of the Configuration page of Blockchain Platform Manager, click Add User.
   2. Once you've entered the user name and password, this user will be added to the LDAP server as an administrative user.
   3. You can now log out of Blockchain Platform Manager with your default admin user, and log in with this newly added instance administrative user to create an instance.

   Note:

   Once you've successfully logged into Blockchain Platform Manager with this user and provisioned an instance, you may want to disable the default admin user (obpadmin) for security reasons. This can be done from the Configuration page Platform Settings tab.
5. On the Instances page, click Create Instance to create an instance of the Besu network.
   The Besu Create Instance dialog is displayed.
6. Complete the following fields:

   Field	Description
   Instance Name	Enter a name for your Oracle Blockchain Platform instance. The service instance name: Must contain one or more characters. Must not exceed 15 characters. Must start with an ASCII letter: a to z. Must contain only lower case ASCII letters or numbers. Must not contain a hyphen. Must not contain any other special characters. Must be unique within the identity domain.
   Description	Optional. Enter a short description of the Oracle Blockchain Platform instance.
   Domain Name	Enter the domain name for the cluster that you specified when installing. This must contain only lower case ASCII letters. The hostnames generated for the Blockchain Instance services make use of the domain name and the instance name as parent domain and sub domain respectively.
   Role	Select Founder to create a complete blockchain environment. This instance becomes the founder organization and you can onboard new participants in the network later. Select Participant to create an instance that will join an existing blockchain network created elsewhere before this instance can be used.
   Configuration	Select a provisioning shape which meets the needs of your deployment. Only Enterprise is currently supported for Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu.
   Chain ID	(Founder instance only) Enter your Ethereum chain ID. The default is 1500. Provide a unique numeric identifier for this network avoiding common public IDs like 1, 137, 1337, or 56, to ensure transaction signatures are valid only on this specific Besu deployment and protected from replay attacks.
   Block Period	(Founder instance only) Minimum time (in seconds) between new block creation.
   Validator Node Count	(Founder instance only) Number of nodes responsible for validating and proposing blocks.
   BootNode Count	(Founder instance only) Number of nodes used for initial peer discovery.
   RPC Node Count	(Founder instance only) Number of nodes providing APIs for external communication.
   Rich History Oracle DB Profile	Currently not supported.
   Upload Genesis File	(Participant instance only) Upload the genesis metadata .zip file from the founder instance. Select Export Genesis Metadata from the founder instance Actions menu to download the genesis metadata file from the founder.

   The instance creation process runs, creating the pods for the nodes and services that make up the Besu network.
7. Once the instance is listed in the Up state, add the Hosts entries to your Hosts file.

   <ingress-ip> console.<instance-name>.<instance-domain-name> rpcproxy.<instance-name>.<instance-domain-name>