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: kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/README.md
+14-8Lines changed: 14 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,11 @@ The sample scripts demonstrate the creation of a WebLogic domain home in a Docke
5
5
## Prerequisites
6
6
7
7
The following prerequisites must be handled prior to running the create domain script:
8
+
* The WDT sample requires that JAVA_HOME is set to a java JDK version 1.8 or greater
8
9
* Make sure the WebLogic operator is running.
9
-
* 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.
10
+
* 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.
10
11
* Create a Kubernetes namespace for the domain unless the intention is to use the default namespace.
11
12
* Create the Kubernetes secrets `username` and `password` of the admin account in the same Kubernetes namespace as the domain.
12
-
* Build the Oracle WebLogic image `oracle/weblogic:12.2.1.3-developer`. Refer to [Oracle WebLogic Server on Docker](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/dockerfiles/12.2.1.3). If a different `baseImage` (see Configuration table below) is specified, the specified image needs to be built locally or pulled from a repository.
13
13
14
14
## Use the script to create a domain
15
15
@@ -31,8 +31,13 @@ The script will perform the following steps:
31
31
* Replace the built-in user name and password in the `properties/docker-build/domain_security.properties` file with the `username` and `password` that are supplied on the command line using the `-u` and `-p` options. These credentials need to match the WebLogic domain admin credentials in the secret that is specified via the `weblogicCredentialsSecretName` property in the `create-domain-inputs.yaml` file.
32
32
* Build a Docker image based on the Docker sample, [Example Image with a WebLogic Server Domain using the Oracle WebLogic Deploy Tooling (WDT)](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-domain-home-in-image-wdt) and [Example Image with a WebLogic Server Domain using WLST](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-domain-home-in-image). It will create a sample WebLogic Server domain in the Docker image. Also, you can run the Docker sample, [Example Image with a WebLogic Server Domain](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-domain-home-in-image), manually with the generated `domain.properties` to create a domain home image. **Note**: Oracle recommends keeping the domain home image private in the local repository.
33
33
* Create a Kubernetes domain YAML file, `domain.yaml`, in the directory that is created above. This YAML file can be used to create the Kubernetes resource using the `kubectl create -f` or `kubectl apply -f` command.
As a convenience, using the `-e` option, the script can optionally create the domain object, which in turn results in the creation of the corresponding WebLogic Server pods and services. This option should only be used in a single node Kubernetes cluster.
34
39
35
-
As a convenience, using the `-e` option, the script can optionally create the domain object, which in turn results in the creation of the corresponding WebLogic Server pods and services.
40
+
For a multi-node Kubernetes cluster, make sure that the generated image is available on all nodes before creating the domain resource using the kubectl apply -f command.
36
41
37
42
The usage of the create script is as follows:
38
43
@@ -71,15 +76,15 @@ The following parameters can be provided in the inputs file.
71
76
|`adminPort`| Port number for the Administration Server inside the Kubernetes cluster. |`7001`|
72
77
|`adminNodePort`| Port number of the Administration Server outside the Kubernetes cluster. |`30701`|
73
78
|`adminServerName`| Name of the Administration Server. |`admin-server`|
74
-
|`baseImage`| The image that is used to build the domain-home-in-image Docker image. If not specified, use the built-in base image `oracle/weblogic:12.2.1.3-developer`. The image specified here needs to be built locally or pulled from a repository before the `create-domain.sh` script is executed. |`oracle/weblogic:12.2.1.3-developer`|
75
79
|`clusterName`| Name of the WebLogic cluster instance to generate for the domain. |`cluster-1`|
76
80
|`clusterType`| Type of the WebLogic Cluster. Legal values are `CONFIGURED` or `DYNAMIC`. |`DYNAMIC`|
77
-
|`configuredManagedServerCount`| Number of Managed Server instances to generate for the domain. |`2`|
81
+
|`configuredManagedServerCount`| Number of Managed Server instances to generate for the domain. |`5`|
82
+
|`domainHomeImageBase`| Base WebLogic binary image used to build the WebLogic domain image. 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 before the `create-domain.sh` script is executed. ||
83
+
|`domainHomeImageBuildPath`| Location of the WebLogic "domain home in image" Docker image in `https://github.com/oracle/docker-images.git` project. If not specified, use "./docker-images/OracleWebLogic/samples/12213-domain-home-in-image-wdt". Another possible value is "./docker-images/OracleWebLogic/samples/12213-domain-home-in-image" which uses WLST scripts, instead of WDT, to generate the domain configuration. |`./docker-images/OracleWebLogic/samples/12213-domain-home-in-image-wdt`|
78
84
|`domainUID`| Unique ID that will be used to identify this particular domain. Used as the name of the generated WebLogic domain as well as the name of the Kubernetes domain resource. This ID must be unique across all domains in a Kubernetes cluster. This ID cannot contain any character that is not valid in a Kubernetes service name. |`domain1`|
79
85
|`exposeAdminNodePort`| Boolean indicating if the Administration Server is exposed outside of the Kubernetes cluster. |`false`|
80
86
|`exposeAdminT3Channel`| Boolean indicating if the T3 administrative channel is exposed outside the Kubernetes cluster. |`false`|
81
-
|`image`| WebLogic Docker image that the domain resource will use. If not specified, the value is the name of the generated Docker image. |`12213-domain-home-in-image-wdt`|
82
-
|`imagePath`| The relative directory of the WebLogic domain home in image Docker image in `https://github.com/oracle/docker-images.git` project under the `docker-images/OracleWebLogic/samples` directory. |`12213-domain-home-in-image-wdt`|
87
+
|`image`| WebLogic Docker image that the domain resource will pull if needed. You only need to specify this if you are going to push the generated image from the local Docker repository to another Docker repository. If not specified, the sample uses the internally generated image name, either "domain-home-in-image:latest" or "domain-home-in-image-wdt:latest". ||
83
88
|`imagePullPolicy`| WebLogic Docker image pull policy. Legal values are "IfNotPresent", "Always", or "Never" |`IfNotPresent`|
84
89
|`imagePullSecretName`| Name of the Kubernetes secret to access the Docker Store to pull the WebLogic Server Docker image. The presence of the secret will be validated when this parameter is specified ||
85
90
|`includeServerOutInPodLog`| Boolean indicating whether to include server .out to the pod's stdout. |`true`|
@@ -89,7 +94,7 @@ The following parameters can be provided in the inputs file.
89
94
|`managedServerPort`| Port number for each Managed Server. |`8001`|
90
95
|`namespace`| Kubernetes namespace in which to create the domain. |`default`|
91
96
|`productionModeEnabled`| Boolean indicating if production mode is enabled for the domain. |`true`|
92
-
|`serverStartPolicy`| Determines which WebLogic Servers will be started up. Legal values are `NEVER`, `ALWAYS`, `IF_NEEDED`, `ADMIN_ONLY`. |`IF_NEEDED`|
97
+
|`serverStartPolicy`| Determines which WebLogic Servers will be started up. Legal values are `NEVER`, `IF_NEEDED`, `ADMIN_ONLY`. |`IF_NEEDED`|
93
98
|`t3ChannelPort`| Port for the T3 channel of the NetworkAccessPoint. |`30012`|
94
99
|`t3PublicAddress`| Public address for the T3 channel. |`kubernetes`|
95
100
|`weblogicCredentialsSecretName`| Name of the Kubernetes secret for the Administration Server's username and password. |`domain1-weblogic-credentials`|
0 commit comments