You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: integration-tests/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Quick test use cases.
24
24
4. verify admin t3 channel port by exec into the admin pod and deploying webapp using the channel port for WLST
25
25
5. verify web app load balancing by accessing the webapp using loadBalancerWebPort
26
26
6. verify domain life cycle(destroy and create) should not any impact on Operator managing the domain and web app load balancing and admin external service
27
-
7. cluster scale up/down using Operator REST endpoint, webapp load balancing should adjust accordingly. (run.sh does scaling by editing the replicas in domain-custom-resource.yaml.)
27
+
7. cluster scale up/down using Operator REST endpoint, webapp load balancing should adjust accordingly.
28
28
8. Operator life cycle(destroy and create) should not impact the running domain
29
29
9. verify liveness probe by killing managed server 1 process 3 times to kick pod auto-restart
30
30
10. shutdown the domain by changing domain serverStartPolicy to NEVER
Copy file name to clipboardExpand all lines: kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/README.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,17 @@
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. The scripts also generate the domain YAML file, which can then be used to start the Kubernetes artifacts of the corresponding domain. Optionally, the scripts start up the domain, and WebLogic Server pods and services.
3
+
The sample scripts demonstrate the creation of a WebLogic domain home in a Docker image. If logHomeOnPV is enabled, then the log home resides 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 to start the Kubernetes artifacts of the corresponding domain. Optionally, the scripts start up the domain, and WebLogic Server pods and services.
4
4
5
5
## Prerequisites
6
6
7
+
Before you begin, read this guide, [Domain Resource](../../../../../site/domain-resource.md)
8
+
7
9
The following prerequisites must be handled prior to running the create domain script:
8
10
* The WDT sample requires that JAVA_HOME is set to a java JDK version 1.8 or greater
9
11
* Make sure the WebLogic operator is running.
10
12
* The operator requires WebLogic Server 12.2.1.3.0 with patch 28076014 applied. Refer to [Weblogic Docker images](../../../../../site/weblogic-docker-images.md) for details on how to create one. If a different `domainHomeImageBase` (see Configuration table below) is specified, the specified image needs to be built locally or pulled from a repository.
11
13
* Create a Kubernetes namespace for the domain unless the intention is to use the default namespace.
14
+
* If logHomeOnPV is enabled, create the Kubernetes persistent volume where the log home will be hosted, and the Kubernetes persistent volume claim for the domain in the same Kubernates namespace. For samples to create a PV and PVC, see [Create sample PV and PVC](../../create-weblogic-domain-pv-pvc/README.md).
12
15
* Create the Kubernetes secrets `username` and `password` of the admin account in the same Kubernetes namespace as the domain.
-u Username used in building the Docker image for WebLogic domain in image.
51
54
-p Password used in building the Docker image for WebLogic domain in image.
52
55
-e Also create the resources in the generated YAML files, optional.
56
+
-v Validate the existence of persistentVolumeClaim, optional.
53
57
-k Keep what has been previously cloned from https://github.com/oracle/docker-images.git, optional.
54
58
If not specified, this script will always remove existing project and clone again.
55
59
-h Help
@@ -99,9 +103,12 @@ The following parameters can be provided in the inputs file.
99
103
|`includeServerOutInPodLog`| Boolean indicating whether to include server .out to the pod's stdout. |`true`|
100
104
|`initialManagedServerReplicas`| Number of Managed Servers to initially start for the domain. |`2`|
101
105
|`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`|
106
+
|`logHomeOnPV`| Specifies whether the log home is stored on the persistent volume. |`false`|
107
+
|`logHome`| The in-pod name of the directory to store the domain, node manager, server logs, and server .out files in. If not specified, the value is derived from the `domainUID` as `/shared/logs/<domainUID>`. |`/shared/logs/domain1`|
102
108
|`managedServerNameBase`| Base string used to generate Managed Server names. |`managed-server`|
103
109
|`managedServerPort`| Port number for each Managed Server. |`8001`|
104
110
|`namespace`| Kubernetes namespace in which to create the domain. |`default`|
111
+
|`persistentVolumeClaimName`| Name of the persistent volume claim. If not specified, the value is derived from the `domainUID` as `<domainUID>-weblogic-sample-pvc`|`domain1-weblogic-sample-pvc`|
105
112
|`productionModeEnabled`| Boolean indicating if production mode is enabled for the domain. |`true`|
106
113
|`serverStartPolicy`| Determines which WebLogic Servers will be started up. Legal values are `NEVER`, `IF_NEEDED`, `ADMIN_ONLY`. |`IF_NEEDED`|
107
114
|`t3ChannelPort`| Port for the T3 channel of the NetworkAccessPoint. |`30012`|
0 commit comments