Application Transformer for VMware Tanzu discovers the WebLogic Server (WLS) domain to retrieve domain metadata and application artifacts (*.war, *.ear files). WebLogic containerization is supported for Linux VMs only.

Containerization builds an OCI image from discovered artifacts and produces a deployment file you can use to deploy in the TKG cluster or any Kubernetes cluster. Building of image uses Oracle’s WIT (WebLogic Image Tool).

Note: The current version of Application Transformer for VMware Tanzu does not support following features:
  • Complete server migration
  • Consensus leasing
  • Node Manager (However it is used internally for the liveness probe, and to start WebLogic Server instances)
  • Multicast
  • Multitenancy
  • Production redeployment
  • Mixed clusters (configured servers targeted to a dynamic cluster) For up-to-date information about the features of WebLogic Server that are supported in Kubernetes environments, see My Oracle Support Doc ID 2349228.1.

Prerequisites

Procedure

  1. Modify the model file, Validate and Save > Continue.
  2. Refer the current versions of WebLogic server, JDK and select the desired versions for image.
  3. Select a source registry to pull the base image, which can be embedded harbor registry, enterprise harbor registry or docker registry.
  4. Select the Base OS for image.
    • By default, oraclelinux:7-slim is populated, which you can change.
    • Recommended operating systems are Oracle Linux and RHEL with valid tags. RHEL images require Redhat subscription credentials.
  5. Click Continue.
  6. Apply Patches.
    If you have selected the WebLogic 12.2.1.3.0 version, you see a warning message and requires you to select a My Oracle Support Account to proceed further.

    If patches are required, you can add as comma separated list in the Apply Patches screen.

  7. Select the destination registry and provide a proper image tag in the <repository>/<image>:<tag> format to push the image and artifacts and then, click Continue.
  8. Review the selections and click CONFIRM to trigger the Build Image task.

Results

  • An alert pops-up showing the status of the operation. Build Image Task can be tracked in the Tasks page. Click on the task within the task bar to view the logs associated with the build process.
  • After successful completion of image build and push, component details are updated with OCI image tag and artifact tag. Artifacts zip can be downloaded and contains all discovered artifacts from the domain and generated template deployment yaml file which needs to be edited to replace FIX-ME details before deploying.

What to do next