Skip to content

Commit ff4623b

Browse files
committed
Catchup to rc2 changes
1 parent d9e6af9 commit ff4623b

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# WebLogic sample domain home in Docker image
22

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.
44

55
## Prerequisites
66

@@ -115,7 +115,7 @@ The following parameters can be provided in the inputs file.
115115
| `initialManagedServerReplicas` | Number of Managed Servers to initially start for the domain. | `2` |
116116
| `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` |
117117
| `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` |
119119
| `managedServerNameBase` | Base string used to generate Managed Server names. | `managed-server` |
120120
| `managedServerPort` | Port number for each Managed Server. | `8001` |
121121
| `namespace` | Kubernetes namespace in which to create the domain. | `default` |
@@ -175,7 +175,7 @@ spec:
175175
includeServerOutInPodLog: true
176176
# Whether to enable log home
177177
# 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
179179
# logHome: /shared/logs/domain1
180180
# serverStartPolicy legal values are "NEVER", "IF_NEEDED", or "ADMIN_ONLY"
181181
# This determines which WebLogic Servers the operator will start up when it discovers this Domain

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/create-domain-inputs.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ includeServerOutInPodLog: true
7777
# The default is false.
7878
logHomeOnPV: false
7979

80-
# The in-pod location for domain log, server logs, server out, and Node Manager log files
80+
# The in-pod location for domain log, server logs, server out, and node manager log files
8181
# If not specified, the value is derived from the domainUID as /shared/logs/<domainUID>
8282
# This parameter is required if 'logHomeOnPV' is true.
8383
# Otherwise, it is ignored.

kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ The following parameters can be provided in the inputs file.
8888
| `includeServerOutInPodLog` | Boolean indicating whether to include server .out to the pod's stdout. | `true` |
8989
| `initialManagedServerReplicas` | Number of Managed Servers to initially start for the domain. | `2` |
9090
| `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` |
91-
| `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>`. | `/shared/logs/domain1` |
91+
| `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>`. | `/shared/logs/domain1` |
9292
| `managedServerNameBase` | Base string used to generate Managed Server names. | `managed-server` |
9393
| `managedServerPort` | Port number for each Managed Server. | `8001` |
9494
| `namespace` | Kubernetes namespace in which to create the domain. | `default` |
@@ -148,7 +148,7 @@ spec:
148148
includeServerOutInPodLog: true
149149
# Whether to enable log home
150150
logHomeEnabled: true
151-
# The in-pod name location for domain log, server logs, server out, and Node Manager log files
151+
# The in-pod name location for domain log, server logs, server out, and node manager log files
152152
logHome: /shared/logs/domain1
153153
# serverStartPolicy legal values are "NEVER", "IF_NEEDED", or "ADMIN_ONLY"
154154
# This determines which WebLogic Servers the operator will start up when it discovers this Domain

kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/create-domain-inputs.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ weblogicCredentialsSecretName: domain1-weblogic-credentials
6363
# The default is true.
6464
includeServerOutInPodLog: true
6565

66-
# The in-pod location for domain log, server logs, server out, and Node Manager log files
66+
# The in-pod location for domain log, server logs, server out, and node manager log files
6767
# If not specified, the value is derived from the domainUID as /shared/logs/<domainUID>
6868
logHome: /shared/logs/domain1
6969

0 commit comments

Comments
 (0)