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
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ The script will perform the following steps:
42
42
* Create a properties file, `domain.properties`, in the directory that is created above. This properties file will be used to create a sample WebLogic Server domain.
43
43
* Clone the WebLogic docker-images project into the current directory using `git clone https://github.com/oracle/docker-images.git`.
44
44
* 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.
45
-
* 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.
45
+
* Build a Docker image based on the Docker sample, [Example Image with a WebLogic Server Domain using the Oracle WebLogic Scripting Tooling (WLST)](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-domain-home-in-image) or[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). It will create a sample WebLogic Server domain in the Docker image. **Note**: Oracle recommends keeping the domain home image private in the local repository.
46
46
* Create a tag that refers to the generated Docker image.
47
47
* 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.
48
48
```
@@ -101,10 +101,9 @@ The following parameters can be provided in the inputs file.
101
101
|`adminNodePort`| Port number of the Administration Server outside the Kubernetes cluster. |`30701`|
102
102
|`adminServerName`| Name of the Administration Server. |`admin-server`|
103
103
|`clusterName`| Name of the WebLogic cluster instance to generate for the domain. |`cluster-1`|
104
-
|`clusterType`| Type of the WebLogic Cluster. Legal values are `CONFIGURED` or `DYNAMIC`. |`DYNAMIC`|
105
104
|`configuredManagedServerCount`| Number of Managed Server instances to generate for the domain. |`5`|
106
-
|`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. ||
107
-
|`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`|
105
+
|`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` is specified, the specified image needs to be built locally or pulled from a repository before the `create-domain.sh` script is executed. ||
106
+
|`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". Another possible value is "./docker-images/OracleWebLogic/samples/12213-domain-home-in-image-wdt" which uses WDT, instead of WLST, to generate the domain configuration. |`./docker-images/OracleWebLogic/samples/12213-domain-home-in-image`|
108
107
|`domainPVMountPath`| Mount path of the domain persistent volume. |`/shared`|
109
108
|`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`|
110
109
|`exposeAdminNodePort`| Boolean indicating if the Administration Server is exposed outside of the Kubernetes cluster. |`false`|
@@ -161,7 +160,7 @@ spec:
161
160
# If the domain home is in the image
162
161
domainHomeInImage: true
163
162
# The Operator currently does not support other images
164
-
image: "12213-domain-home-in-image:latest"
163
+
image: "domain-home-in-image:latest"
165
164
# imagePullPolicy defaults to "Never"
166
165
imagePullPolicy: "Never"
167
166
# Identify which Secret contains the WebLogic Admin credentials (note that there is an example of
Copy file name to clipboardExpand all lines: kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/README.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,6 @@ The following parameters can be provided in the inputs file.
73
73
|`adminNodePort`| Port number of the Administration Server outside the Kubernetes cluster. |`30701`|
74
74
|`adminServerName`| Name of the Administration Server. |`admin-server`|
75
75
|`clusterName`| Name of the WebLogic cluster instance to generate for the domain. |`cluster-1`|
76
-
|`clusterType`| Type of the WebLogic Cluster. Legal values are `CONFIGURED` or `DYNAMIC`. |`DYNAMIC`|
77
76
|`configuredManagedServerCount`| Number of Managed Server instances to generate for the domain. |`5`|
78
77
|`createDomainFilesDir`| Directory to get all the create domain scripts and supporting files, including the script that is specified by the `createDomainScriptName` property. By default, this directory is set to the relative path `wlst`, and the create script will use the built-in WLST offline scripts in the `wlst` directory to create the WebLogic domain. It can also be set to the relative path `wdt`, and then the built-in WDT scripts will be used instead. An absolute path is also supported to point to an arbitrary directory in the file system. |`wlst`|
79
78
|`createDomainScriptsMountPath`| Mount path of the directory where the create domain scripts are located inside the pod. |`/u01/weblogic`|
0 commit comments