Last updated on FEBRUARY 01, 2022
Oracle WebCenter Portal – Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Oracle has certified the deployment of WebCenter Portal 18.104.22.168.0 domains running on Kubernetes.
Kubernetes, Oracle Linux host operating system versions and kernel versions that have been certified are described below.
The WC Portal on Kubernetes certification includes and requires using the Flannel network fabric in Kubernetes.
Oracle may certify other network fabrics in the future.
You can find more information here:
- For details on all the specific certified configurations, consult Oracle certification information listed at the following URL. WebCenter Portal specific exceptions will be listed in this document.
Redhat Openshift and OKE (Oracle Kubernetes Engine) are currently not certified for Oracle WebCenter Portal container deployment.
For details on configuring the environment see:
Here is the patch information to download a pre-built container image from My Oracle Support:
|Patch 33762020||ORACLE FUSION MIDDLEWARE 12C WEBCENTER PORTAL 22.214.171.124 WCP IMAGE with jdk8u321, OL 7-slim, AND WebCenter Portal Bundle Patch 126.96.36.199.201126|
Quick Start Deployment ON-PREMISE:https://oracle.github.io/fmw-kubernetes/wcportal-domains/appendix/quickstart-deployment-on-prem/
Certified and supported WebCenter Portal configurations and features
Oracle has certified and supported the following WebCenter Portal configurations and features:
- Running one or more WebCenter Portal domains in a Kubernetes cluster.
- Single or multiple node Kubernetes clusters.
- WebCenter Portal Clustered Managed Servers in WCP domain with domain home configuration in persistent volume.
- Load balancing HTTP requests using Nginx, Træfik, Voyager (HAProxy) Ingress controllers, Apache HTTP Server in Kubernetes clusters.
- Scale Oracle WebCenter Portal domains by starting and stopping Managed Servers on demand.
- Integration with Prometheus monitoring using the WebLogic Monitoring Exporter.
- RMI communication from outside/inside the Kubernetes cluster.
- Patching WebCenter Portal domain.
- WebLogic Server Kubernetes Operator.
In this certification of WebCenter Portal on Kubernetes, there are the following limitations:
- In this release, Oracle WebCenter Portal 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 Portal 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.
- In this release, WebCenter Portal domains are not configured with Portlet server.
On next release portlet server will be added.
- 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 Portal MBeans is not available.
Also, a metrics dashboard specific to Oracle WebCenter Portal is not available.
Instead, use the WebLogic Server dashboard to monitor the Oracle WebCenter Portal server metrics in Grafana.
- Some features such as multicast, multitenancy, production redeployment, and Node Manager (although it is used internally for the livenes probe and to start WebLogic Server instances) are not supported in this release.
Oracle Support will assist customers running Oracle WebCenter Portal in certified containers on other Kubernetes platforms (e.g Kubernetes not on Oracle Linux) in the following manner:
- If a problem is a known Oracle issue, Oracle Support will recommend the appropriate known solution.
- If the problem is not a known Oracle issue, Oracle Support will provide support in the following fashion:
- a) Oracle Support will attempt to reproduce the problem outside the container and Kubernetes, directly on a certified Host OS, unless Oracle Support believes the problem is related to use of container or Kubernetes.
- b) If the problem cannot be reproduced as outlined in (2.a), then Oracle Support will attempt to reproduce the problem on a certified container, certified Kubernetes, and certified Flannel network.
- c) If the problem cannot be reproduced as outlined in (2.b) and the customer continues to require support for their problem, Oracle will request that the customer reproduce the problem on a certified container, certified Kubernetes, certified Flannel network fabric, or directly on a certified Host OS.
- d) If the problem cannot be reproduced in either of these environments, Oracle Support will assume the problem is caused by differences between the certified Kubernetes platform, and the Kubernetes platform being used by the customer.
- e) If the problem is a network communication issue Oracle Support will assume the problem is caused by the network fabric being used by the customer. Oracle Support will refer the customer to the non-certified Kubernetes platform or the network vendor for support.
Note:2593367.1 – Common Queries On Oracle WebLogic Server Kubernetes Operator
To view full details, sign in with your My Oracle Support account.
Don’t have a My Oracle Support account? Click to get started!
In this Document
|Certified and supported WebCenter Portal configurations and features|