1. Administering Oracle Blockchain Platform
  2. Install Your Oracle Blockchain Platform Instance

3 Install Your Oracle Blockchain Platform Instance

Topics

Deploy Your Virtual Machine

Load Oracle Blockchain Platform Enterprise Edition on your Virtual Machine Hosting Software

  1. Download the blockchain package; it consists of an OVA image called obpee_19_3_4.ova.
  2. Import the VM into your virtual machine hosting software. For example on Oracle VirtualBox, complete the following steps. For information about using VMWare ESXi, see Load Oracle Blockchain Platform Enterprise Edition on VMWare ESXi.
    1. Select File then Import Appliance, and browse to the directory where the OVA has been extracted.
    2. On the Appliance settings page, you may check Reinitialize the MAC address of all network cards if you plan on running more than 1 VM in your setup. You can create multiple VMs by either importing the appliance multiple times, or cloning the VM immediately after it's imported. Click Import.
  3. After a few minutes, the VM will be displayed in the list of machines in VirtualBox Manager. Right-click on the VM and select Settings:
    1. Under System on the Motherboard tab, select Hardware Clock in UTC Time to ensure the guest VM and the host's clocks are consistent in terms of timezones.
    2. Under Network on the Adapter tab connected to the network you want the VM to be on, ensure Enable Network Adapter is selected, and select Bridged Adapter.

The VM is now ready to be used.

Load Oracle Blockchain Platform Enterprise Edition on VMWare ESXi

  1. In the VMWare ESXi navigator, select the Virtual Machines page, and then click Create / Register VM.
  2. Under Select creation type, select Deploy a virtual machine from an OVF or OVA file and then click Next.
  3. Enter a name for the virtual machine and select the blockchain package (OVA file) that you downloaded and then click Next.
  4. Accept the default values and click Next for the remaining pages.
  5. Click Finish, and then wait for the VM to be provisioned.
  6. Once the VM is running, open a console to the VM and log in using the default user name oracle and the default password Welcome1. You'll be prompted to change the password. After you change the password, log in again using the new password.
  7. To enable DHCP to obtain an IP address, use the sudo command to change to the root account and then complete the following steps:
    1. Copy the file /etc/sysconfig/network-scripts/ifcfg-enp0s3 to a new file in the same directory called ifcfg-ens160.
    2. Edit the ifcfg-ens160 file to change the adapter name from enp0s3 to ens160.
    3. Power off the VM.
    4. Change the network adapter type from E1000 to VMXNET 3.
  8. Power on the VM.

The VM is now ready to be used.

Expand the Available Space for the Ledger

Because the ledger and logs for Oracle Blockchain Platform are persistent, you need to expand the root volume to ensure you don't run out of space.

  1. Add a hard disk for the SCSI controller. In VirtualBox click Settings then select Storage. Add a new hard disk. The recommended file type is VHD (Virtual Hard Disk); select either fixed or extensible mode.
  2. Create the logical volume partition: sudo fdisk -c -u /dev/sdb
    Enter the following subcommands sequentially: 
    n Create new partition Press 
p Choose primary partition use p
1 Choose 1 for the primary partition
after this press return key twice for max allocation
t Change the type
8e Change the partition type to Linux LVM
p Print the partition
w write the changes
  3. Create the new physical volume: sudo pvcreate /dev/sdb1
  4. Restart the system.
  5. Verify the physical volume: 
    sudo pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 vg00 lvm2 a-- 96.66g <25.41g
/dev/sdb1 lvm2 ¿ <200.00g <200.00g
  6. Add /dev/sdb1 to vg00 to extend the size to get more space for expanding the logical volume: sudo vgextend vg00 /dev/sdb1
  7. Check the size of the volume group: 
    sudo vgs
VG #PV #LV #SN Attr VSize VFree
vg00 2 5 0 wz-n <296.66g 225.40g
    In this example, 225.4 GB are free.
  8. After extending, resize the file system: sudo resize2fs /dev/vg00/root\
  9. Check the logical volume: 
    /dev/vg00/root
df -h
/dev/mapper/vg00-root 194G 18G 169G 10% /

Start Oracle Blockchain Platform

Once your network and sytem settings are configured, start the VM by selecting it and clicking Start. It should start within a minute.

Once the VM has started, hit the Enter key to get a login prompt.

Update Your Docker Root CA Certificate

The Docker root CA certificates included with Oracle Blockchain Platform Enterprise Edition must be updated on each of the Oracle Blockchain Platform Enterprise Edition virtual machines.

To update your certificates:
  1. On one of your Oracle Blockchain Platform Enterprise Edition VMs, create a folder /u01/renewCerts/docker-certs.
  2. Go to this folder and run the following commands to generate new certificates:
    openssl genrsa -aes256 -passout pass:example -out rootCA.key 4096 
openssl req -x509 -new -nodes -key rootCA.key -sha256 -days 3650 -out rootCA.crt -subj "/C=US/ST=CA/L=RedwoodShores/O=Oracle/OU=/CN=oracle.com" -passin pass:example
    The above commands will generate:
    • rootCA.crt
    • rootCA.key
    in /u01/renewCerts/docker-certs. These files will be used to update all VMs of all your Blockchain Platform instances.
  3. Check the ownership of the two files. It should be set as root:root. If not, change the ownership.
  4. Copy the rootCA.crt and rootCA.key files generated in step 2 to all the Oracle Blockchain Platform Enterprise Edition VMs of all instances, in a folder under /u01.
    For consistency, you can create a folder path /u01/renewCerts/docker-certs on each of the VMs and copy the files to this folder.
  5. For each of the Oracle Blockchain Platform Enterprise Edition VMs of all instances do the following:
    1. Backup the existing root CA certificate files to /u01/renewCerts/:
      cp /etc/docker/ssl/rootCA.crt /u01/renewCerts/rootCA-orig.crt
cp /etc/docker/ssl/rootCA.key /u01/renewCerts/rootCA-orig.key
    2. Copy the newly generated rootCA.crt and rootCA.key to /etc/docker/ssl.
    3. Verify that the files rootCA.crt and rootCA.key in/etc/docker/ssl are the new files.
    4. Restart the VM.

      Note:

      The same rootCA.crt and rootCA.key files generated in step 2 must be copied to each Oracle Blockchain Platform Enterprise Edition VM.

Log on to Oracle Blockchain Platform for the First Time

After you've deployed and started Oracle Blockchain Platform Enterprise Edition on your VM hosting software, you can log on to Blockchain Platform Manager to create an instance.

You can directly log on to the Platform Manager by using the URL:
https://<hostname of your VM>:7443/console/index.html
The initial user name is obpadmin and the password is welcome1. This user is only meant for performing initial configuration and does not have instance creation privileges.

In order to use the internal LDAP server, the admin password must first be changed. Blockchain Platform Manager will not allow you to use an internal LDAP configuration with the default password.

Set the Blockchain Platform Manager Name

On the Configuration page Platform Settings tab of Blockchain Platform Manager, you can set a name for the Platform Manager.

Note:

Once the name for the Platform Manager has been set, any users added to the LDAP server will be associated with this name. If you change the name after adding users, those users will lose access to Blockchain Platform Manager and any Oracle Blockchain Platform instances.

Set the Notification and Console Idle Timeouts

On the Configuration page Platform Settings tab of Blockchain Platform Manager, you can set the timeouts for notifications and the console.
  • Console Idle Timeout: in minutes, how long the console can be idle before it logs out the current user.
  • Notification Timeout: in seconds, how long notifications will remain visible on the browser. Select -1 if you want notifications to remain visible until you close them.