|
1 | 1 | # WebLogic sample domain home in Docker image
|
2 | 2 |
|
3 |
| -The sample scripts demonstrate the creation of a WebLogic domain home in a Docker image using one of the domain home in image samples in the [WebLogic Server Domain Docker image samples GitHub project](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples). The sample scripts provide an option to put the WebLogic domain log, server logs, server output files, and the Node Manager logs on an existing Kubernetes persistent volume (PV) and persistent volume claim (PVC). The scripts also generate the domain YAML file, which can then be used by the scripts or manually to start the Kubernetes artifacts of the corresponding domain, including the WebLogic Server pods and services. |
| 3 | +The sample scripts demonstrate the creation of a WebLogic domain home in a Docker image using one of the domain home in image samples in the [WebLogic Server Domain Docker image samples GitHub project](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples). The sample scripts have an option of putting the WebLogic domain log, server logs, server output files, and the node manager logs on an existing Kubernetes persistent volume (PV) and persistent volume claim (PVC). The scripts also generate the domain YAML file, which can then be used by the scripts or manually to start the Kubernetes artifacts of the corresponding domain, including the WebLogic Server pods and services. |
4 | 4 |
|
5 | 5 | ## Prerequisites
|
6 | 6 |
|
@@ -115,7 +115,7 @@ The following parameters can be provided in the inputs file.
|
115 | 115 | | `initialManagedServerReplicas` | Number of Managed Servers to initially start for the domain. | `2` |
|
116 | 116 | | `javaOptions` | Java options for starting the Administration and Managed Servers. A Java option can have references to one or more of the following pre-defined variables to obtain WebLogic domain information: `$(DOMAIN_NAME)`, `$(DOMAIN_HOME)`, `$(ADMIN_NAME)`, `$(ADMIN_PORT)`, and `$(SERVER_NAME)`. | `-Dweblogic.StdoutDebugEnabled=false` |
|
117 | 117 | | `logHomeOnPV` | Specifies whether the log home is stored on the persistent volume. If set to true, then you must specify the `logHome`, `persistentVolumeClaimName` and `domainPVMountPath` parameters.| `false` |
|
118 |
| -| `logHome` | The in-pod location for domain log, server logs, server out, and Node Manager log files. If not specified, the value is derived from the `domainUID` as `/shared/logs/<domainUID>`. This parameter is required if `logHomeOnPV` is true. Otherwise, it is ignored. | `/shared/logs/domain1` | |
| 118 | +| `logHome` | The in-pod location for domain log, server logs, server out, and node manager log files. If not specified, the value is derived from the `domainUID` as `/shared/logs/<domainUID>`. This parameter is required if `logHomeOnPV` is true. Otherwise, it is ignored. | `/shared/logs/domain1` | |
119 | 119 | | `managedServerNameBase` | Base string used to generate Managed Server names. | `managed-server` |
|
120 | 120 | | `managedServerPort` | Port number for each Managed Server. | `8001` |
|
121 | 121 | | `namespace` | Kubernetes namespace in which to create the domain. | `default` |
|
@@ -175,7 +175,7 @@ spec:
|
175 | 175 | includeServerOutInPodLog: true
|
176 | 176 | # Whether to enable log home
|
177 | 177 | # logHomeEnabled: false
|
178 |
| - # The in-pod location for domain log, server logs, server out, and Node Manager log files |
| 178 | + # The in-pod location for domain log, server logs, server out, and node manager log files |
179 | 179 | # logHome: /shared/logs/domain1
|
180 | 180 | # serverStartPolicy legal values are "NEVER", "IF_NEEDED", or "ADMIN_ONLY"
|
181 | 181 | # This determines which WebLogic Servers the operator will start up when it discovers this Domain
|
|
0 commit comments