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: site/manually-creating-domain.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Manually creating a WebLogic domain
2
2
3
-
**PLEASE NOTE** This page is a work in progress, we have some rough notes in here, we are working on writing better doc for how to set up this integration.
3
+
**PLEASE NOTE**: This page is a work in progress. We have some rough notes here and are working on writing better documentation for how to set up this procedure.
4
4
5
-
If creating the domain manually, using a WLST script for example, the domain must be configured to meet these requirements:
5
+
If you are creating the domain manually, for example, using a WLST script, the domain must be configured to meet these requirements:
6
6
7
7
* Domain directory should be in `/shared/domain`.
8
8
* Applications directory should be in `/shared/applications`.
@@ -11,11 +11,11 @@ If creating the domain manually, using a WLST script for example, the domain mus
11
11
12
12
## Use the scripts to create the sample YAML files
13
13
14
-
The `create-weblogic-domain.sh` script described in the previous section can be executed with the “-g” option, which will cause it to generate the YAML files but take no action at all against the Kubernetes environment. This is a useful way to create the sample YAML files needed to manually create a domain.
14
+
The `create-weblogic-domain.sh` script can be executed with the `-g` option, which will cause it to generate the YAML files but take no action at all against the Kubernetes environment. This is a useful way to create the sample YAML files needed to manually create a domain.
15
15
16
16
First, make a copy of `create-weblogic-domain-inputs.yaml` and customize it.
17
17
18
-
Next, choose and create a directory that generated operatorrelated files will be stored in, e.g. /path/to/weblogic-operator-output-directory
18
+
Next, choose and create a directory that generated operator-related files will be stored in, for example, `/path/to/weblogic-operator-output-directory`.
19
19
20
20
Then, execute the script, pointing it at your inputs file and output directory:
21
21
@@ -25,7 +25,7 @@ Then, execute the script, pointing it at your inputs file and output directory:
25
25
-o /path/to/weblogic-operator-output-directory
26
26
```
27
27
28
-
The following YAML files will be generated in the /path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID> directory:
28
+
The following YAML files will be generated in the `/path/to/weblogic-operator-output-directory/weblogic-domains/<domainUID>` directory:
29
29
30
30
*`weblogic-domain-pv.yaml` can be customized and used to create the persistent volume for this domain.
31
31
*`weblogic-domain-pvc.yaml` can be customized and used to create the persistent volume claim for this domain.
@@ -48,13 +48,13 @@ The file `weblogic-domain-pv.yaml` contains a template to create a persistent vo
48
48
* Persistent volume name
49
49
* Storage class name
50
50
* The amount of storage to allocate
51
-
* The physical location of the persistent volume (edit). Prior to creating the persistent volume you need to ensure this location exists and has read/write/execute permission set for the account that Kubernetes is running from.
51
+
* The physical location of the persistent volume (edit). Prior to creating the persistent volume, you need to ensure this location exists and has read/write/execute permissions set for the account that Kubernetes is running from.
52
52
* The access mode is Read/Write Many. You must use a provider that supports Read/Write Many.
53
53
* The contents of the volume are retained across restarts of the Kubernetes environment.
54
54
55
55
## Creating the persistent volume
56
56
57
-
To create the persistent volume issue the following command:
57
+
To create the persistent volume, issue the following command:
58
58
59
59
```
60
60
kubectl create –f weblogic-domain-pv.yaml
@@ -70,7 +70,7 @@ Replace `PV_NAME` with the name of the persistent volume.
70
70
71
71
## Preparing to create the persistent volume claim
72
72
73
-
The file `weblogic-domain-pvc.yaml` contains a template to claim a portion of the persistent volume storage. The customizable items are listed below:
73
+
The file,`weblogic-domain-pvc.yaml`, contains a template to claim a portion of the persistent volume storage. The customizable items are:
74
74
75
75
* Persistent volume claim name
76
76
* Namespace name
@@ -80,7 +80,7 @@ The file `weblogic-domain-pvc.yaml` contains a template to claim a portion of th
80
80
81
81
## Creating the persistent volume claim
82
82
83
-
To create the persistent volume claim issue the following command:
83
+
To create the persistent volume claim, issue the following command:
84
84
85
85
```
86
86
kubectl create –f weblogic-domain-pvc.yaml
@@ -96,7 +96,7 @@ Replace `PVC_NAME` with the name of the persistent volume claim.
96
96
97
97
## Preparing to create the domain custom resource
98
98
99
-
The file `domain-custom-resource.yaml` contains a template to create the domain custom resource. The customizable items are listed below:
99
+
The file,`domain-custom-resource.yaml`, contains a template to create the domain custom resource. The customizable items are:
0 commit comments