Create a Domain

After you create a stack, use the Jenkins job to create a domain for Oracle WebLogic Server for OKE.

When you create a domain with the create domain job, a new domain that has a basic configuration with no custom applications or libraries, called the primordial domain, is created. This domain contains the base WebLogic Server image that has the WebLogic installer, JDK installer, and WebLogic patches for Oracle WebLogic Server for OKE.

To know about the primordial domain, see Mutate the Domain Layer in WebLogic Kubernetes Operator documentation.

To create a domain, you must create a domain as a component, register the component, and register the application.

Create a Domain as a Component

Before you create a domain as component, ensure that all the prerequisites are completed. See Prerequisites to Create a Domain.

Perform the following tasks:

Configure WebLogic Server

Specify the parameters required to configure a WebLogic server on a container cluster.

  1. Sign in to the Jenkins console for your stack. See Access the Jenkins Console.
  2. On the Dashboard page, click create domain as component.
  3. Click Build with Parameters.
  4. For Domain_Name, specify a WebLogic name.
  5. For WebLogic_Version, select a version of Oracle WebLogic Server.

    The available versions are 12.2.1.4.0, 14.1.1.0.0 running on JDK 8, and 14.1.1.0.0 running on JDK 11.

  6. Optional: Select the required base image from the Base_Image list.

    The images are displayed based on the Weblogic Server version. For example, if you select 12.2.1.4.0, 12.2.1.4 images are displayed, and if you select 14.1.1.0.0, 14.1.1.0.0_jdk8 and 14.1.1.0.0_jdk11 images are displayed.

    Note:

    For 14.1.1.0.0., make sure that the base image you select should have the same WebLogic Server and JDK version as in step 5.

    The custom base images and uploaded images are also listed in the Base_Image list. See Create a Custom Base Image.

  7. Enter a user name for the WebLogic Server administrator.
  8. Enter the password for the WebLogic Server administrator.
  9. Select the number of running managed servers in the domain you want to create. You can specify up to nine manged servers.

    The number of running managed servers is also the number of WebLogic Server pods in the Kubernetes cluster. Each managed server runs in a separate pod in the Kubernetes cluster. Managed servers are members of a WebLogic Server cluster.

Configure the Registry

Specify the credentials to access container images in the Oracle Cloud Infrastructure Registry(OCIR).

Note:

If you want to use another user credentials, other than the one specified when creating a stack, then specify the credentials that Oracle WebLogic Server for OKE must use to access container images in the Oracle Cloud Infrastructure Registry (OCIR).
  1. In the Registry_Username field, enter a user name that Kubernetes uses to access the image in the registry.

    The registry user name format is tenancy_namespace/<username>. If your tenancy is federated with Oracle Identity Cloud Service, then the registry user name format is tenancy_namespace/oracleidentitycloudservice/<username>.

    You can choose either to include the tenancy_namespace or remove the tenancy_namespace in the user name format. For example, you can either use tenancy_namespace/<username> or <username>.

    Note:

    If you choose to include tenancy_namespace in the user format, ensure that you use the correct namespace for your tenancy.
  2. In the Registry_Authentication_Token field, enter the OCID of the secret for the auth token generated for the registry user.

For information about how to create a container registry, see Overview of Registry in the Oracle Cloud Infrastructure documentation.

Configure the Domain

In the Provision with JRF section, keep the default selection for Domain_Type as Non_JRF.

Run the Pipeline Job

Click Build to run the Pipeline job.

After the job is successful, you can access the WebLogic Console. See Access the WebLogic Console.

Register a Component

Use the Jenkins job to specify the Verrazzano WebLogic component to register for the WebLogic domain.

  1. Sign in to the Jenkins console for your stack. See Access the Jenkins Console.
  2. On the Dashboard page, click register component.
  3. Click Build with Parameters.
  4. From Component_Names, select the Verrazzano component to register.
  5. Click Build to run the Pipeline job.

Create an Application Configuration

Use this job to select a component, which allows to generate the basic application configuration with an IngressTrait and a MetricsTrait.

Perform the following tasks:

  1. Sign in to the Jenkins console for your stack. See Access the Jenkins Console.
  2. On the Dashboard page, click create application configuration.
  3. Click Build with Parameters.
  4. For Component_Name, select the Verrazzano component for which you want to create the application configuration.
  5. Click Build to run the Pipeline job.

Register an Application

Use the Jenkins job to deploy the Verrazzano application to a Verrazzano system.

See About Verrazzano WebLogic Components and Application Configuration.

You can use one of the following sources to specify the location of the application configuration file:
  • Application Name - The Verrazzano application to register.

  • File Upload - Uploads the file from the local system.

  • Object Storage - Uses the pre-authenticated URL on the Object Storage.

  • Shared File System - Uses the path of the shared file storage.

    The NFS shared file system path is mounted on /u01/shared location on the administration host.

In the job you should select either an application or provide a custom application yaml.

  1. Sign in to the Jenkins console for your stack. See Access the Jenkins Console.
  2. On the Dashboard page, click register application.
  3. Click Build with Parameters.
  4. Select either one of the following:
    • Select the application from the Application_Name list.
    • Select the source of the application configuration file from the Application_Source list.

    Note:

    • If both the application name and a custom application yaml is provided, the application name selection is ignored.
    • For the Application_Source option, if the files are larger than one MB, then use the Object Storage or Shared File System option.
  5. If you have select the Application_Source option:

    For Application_Source_Location, either browse to select the zip file, specify the http pre-authenticated URL, or specify the path of the configuration Yaml file on the shared file system.

  6. Click Build to run the Pipeline job.