Requirements and limitations

This section provides information about the system requirements and limitations for deploying and running Oracle WebCenter Content domains with the WebLogic Kubernetes operator.

System requirements for Oracle WebCenter Content domains

For the current production release 21.1.2:

  • Oracle Linux 7 (UL6+) and Red Hat Enterprise Linux 7 (UL3+ only with standalone Kubernetes) are supported.
  • Kubernetes 1.14.8+, 1.15.7+, 1.16.0+, 1.17.0+, and 1.18.0+ (check with kubectl version).
  • Docker 18.09.1ce, 19.03.1 (check with docker version) or CRI-O 1.14.7 (check with crictl version | grep RuntimeVersion).
  • Flannel networking v0.12.0-amd64 or later (check with docker images | grep flannel).
  • Helm 3.4.1 (check with helm version --client --short).
  • Oracle WebLogic Kubernetes operator 3.1.1 (see operator releases page).
  • Oracle WebCenter Content 12.2.1.4 Docker image built using these steps.
  • You must have the cluster-admin role to install the operator. The operator does not need the cluster-admin role at runtime.
  • We do not currently support running Oracle WebCenter Content in non-Linux containers.
  • Additionally, see the Oracle WebCenter Content documentation for other requirements such as database version.

See here for resourse sizing information for Oracle WebCenter Content domains setup on Kubernetes cluster.

Limitations

Compared to running a WebLogic Server domain in Kubernetes using the operator, the following limitations currently exist for Oracle WebCenter Content domains:

  • In this release, Oracle WebCenter Content domains are supported using the domain on a persistent volume model only, where the domain home is located in a persistent volume (PV).
  • The “domain in image” and “model in image” models are not supported. Also, “WebLogic Deploy Tooling (WDT)” based deployments are currently not supported.
  • Only configured clusters are supported. Dynamic clusters are not supported for Oracle WebCenter Content domains. Note that you can still use all of the scaling features, but you need to define the maximum size of your cluster at domain creation time. Mixed clusters (configured servers targeted to a dynamic cluster) are not supported.
  • The WebLogic Logging Exporter currently supports WebLogic Server logs only. Other logs will not be sent to Elasticsearch. Note, however, that you can use a sidecar with a log handling tool like Logstash or Fluentd to get logs.
  • The WebLogic Monitoring Exporter currently supports WebLogic MBean trees only. Support for JRF and Oracle WebCenter Content MBeans is not available. Also, a metrics dashboard specific to Oracle WebCenter Content is not available. Instead, use the WebLogic Server dashboard to monitor the Oracle WebCenter Content server metrics in Grafana.
  • Some features such as multicast, multitenancy, production redeployment, and Node Manager (although it is used internally for the liveness probe and to start WebLogic Server instances) are not supported in this release.
  • Features such as Java Messaging Service whole server migration, consensus leasing, and maximum availability architecture (Oracle WebCenter Content setup) are not supported in this release.

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.