Install on OCI

The Oracle Backend for Spring Boot and Microservices can be installed from OCI Marketplace.

Note: Oracle Backend for Spring Boot and Microservices can also be installed on-premises or in other clouds.

  1. Access the Oracle Cloud Infrastructure Marketplace listing

    Open the OCI Marketplace listing, as shown in the image below:

    OCI Marketplace listing OCI Marketplace listing

    Click on the Get App button.

  2. Log into your Oracle Cloud Infrastructure account

    You will be taken to a Sign-In page. Choose they type of account you have and click on the Sign In button. If you did not create an account in the Get Started lab, you can do so now using the Sign Up button.

    Sign In page Sign In page

    Sign in to your account as you normally do, using Single Sign-On or Direct Sign-In.

  3. Choose the region and compartment

    In the next screen you can choose the region using the pull down in the top right hand corner, and then choose the compartment you want to install into.

    Install screen Install screen

    Review the terms and restrictions, and then click on the checkbox to accept them. Then, click on Launch Stack,

    Note: This Live module is tested with version 1.2.0. Earlier versions do not contain all features used in this Live Lab.

  4. Review the Create Stack page

    Review the details on the Create Stack page. You may wish to update the Name or add tags. When you are ready, click on Next.

    Create stack screen Create stack screen

  5. In the Backend as A Service Section, fill in the following configuration variables as needed and select Next:

    • Compartment : Select the compartment where you want to install Oracle Backend for Spring Boot and Microservices.
    • Application Name (optional) : A random pet name that will be used as the application name if left empty.
    • Edition : Select COMMUNITY Edition. Standard edition will give more options for the installation but those are not required or used in this LiveLab.
    • Existing Authorization Token : Leave blank.

    Backend as A Service Backend as A Service

  6. If you check the checkbox Set Administrator Passwords in the Administrator Passwords section you have the option to fill in the following passwords (if not they are autogenerated):

    • APISIX Administrator Password (optional) : Leave blank to auto-generate.
    • Grafana Administrator Password (optional) : Leave blank to auto-generate.
    • ORACTL Administrator Password (optional) : Leave blank to auto-generate. This is the password for the obaas-admin user.
    • ORACTL User Password (optional) : Leave blank to auto-generate. This is the password for the obaas-user user.

    Passwords Passwords

  7. In the Kubernetes Cluster Options. fill in the following for the OKE Clusters Options:

    • Public API Endpoint? : For the Live Lba you must check the checkbox Public API Endpoint
    • API Endpoint Access Control : Enter the CIDR block you want to give access to the Control Plane API. Leave the default value 0.0.0.0/0.
    • Node Pool Workers : The number of Kubernetes worker nodes (virtual machines) attached to the OKE cluster. Leave the default value of 3.
    • Node Pool Worker Shape : The shape of the node pool workers. Leave the default Shape value.
    • Node Workers OCPU : The initial number of Oracle Compute Units (OCPUs) for the node pool workers. Leave the default value of 2.

    NOTE: Oracle recommends that you set Control Plane Access Control to be as restrictive as possible

    Public Control Plane Public Control Plane

  8. In the Load Balancers Options section, leave the default values.

    • Enable Public Load Balancer : This option allows access to the load balancer from the internet (public IP). If not selected, access can only be from a private VCN.
    • Public Load Balancer Access Control : Enter the CIDR block you want to give access to the Load Balancer. Default (and not recommended) is 0.0.0.0/0.
    • Public Load Balancer Ports Exposed : The ports exposed from the load balancer.
    • Minimum bandwidth : The minimum bandwidth that the load balancer can achieve.
    • Maximum bandwidth : The maximum bandwidth that the load balancer can achieve.

    NOTE: Oracle recommends that you set Public Load Balancer Access Control to be as restrictive as possible.

    Load Balancer Load Balancer

  9. In the Database Options section, leave the default values.

    • Autonomous Database Compute Model : Choose either ECPU (default) or OCPU compute model for the ADB. Leave the default value of ECPU
    • Autonomous Database Network Access : Choose the Autonomous Database network access. Leave the default value of SECURE_ACCESS
    • ADB Access Control : Comma separated list of CIDR blocks from which the ADB can be accessed. This only applies if SECURE_ACCESS was chosen. Leave default value of 0.0.0.0/0.
    • Autonomous Database ECPU Core Count : Choose how many ECPU cores will be elastically allocated. Leave default value of 2.
    • Allow Autonomous Database OCPU Auto Scaling : Enable auto-scaling for the ADB ECPU core count (x3 ADB ECPU). Leave the default value of un-checked.
    • Autonomous Database Data Storage Size : Choose ADB Database Data Storage Size in gigabytes. Leave the default value of 20GB.
    • Autonomous Database License Model : The Autonomous Database license model. Leave the default value of LICENSE_INCLUDED.
    • Create an Object Storage Bucket for ADB? : Leave the default value of un-checked.

    NOTE: Oracle recommends that you restrict by IP or CIDR addresses to be as restrictive as possible.

    Database Options Database Options

  10. Click Next to review your choices.

  11. Complete the Review page

    Review the details on the Review page. Check the box next to Run Apply. When you are ready, click on Create.

    Review screen Review screen

  12. Review the apply screen

    The stack will now be applied. On the Apply screen (see below) you can monitor the progress of the installation in the Logs box. The installation should take about 30 minutes to complete. This includes the time needed to create your Oracle Autonomous Database instance, your Oracle Container Engine for Kubernetes cluster and install the various components of the stack into the Kubernetes cluster.

    Stack apply screen Stack apply screen

    Note: While you are waiting for the installation to complete is a great time to start setting up your development environment (see the next lab). You can come back here where you are done to check the installation completed successfully.