Skip to content

Commit 3e8185c

Browse files
authored
Merge pull request #227 from oracle/RMmanualcreatedomain
minor edits
2 parents 88840b6 + b4302b8 commit 3e8185c

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

site/manually-creating-domain.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
# Manually creating a WebLogic domain
22

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

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:
66

77
* Domain directory should be in `/shared/domain`.
88
* 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
1111

1212
## Use the scripts to create the sample YAML files
1313

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

1616
First, make a copy of `create-weblogic-domain-inputs.yaml` and customize it.
1717

18-
Next, choose and create a directory that generated operator related 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`.
1919

2020
Then, execute the script, pointing it at your inputs file and output directory:
2121

@@ -25,7 +25,7 @@ Then, execute the script, pointing it at your inputs file and output directory:
2525
-o /path/to/weblogic-operator-output-directory
2626
```
2727

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:
2929

3030
* `weblogic-domain-pv.yaml` can be customized and used to create the persistent volume for this domain.
3131
* `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
4848
* Persistent volume name
4949
* Storage class name
5050
* 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.
5252
* The access mode is Read/Write Many. You must use a provider that supports Read/Write Many.
5353
* The contents of the volume are retained across restarts of the Kubernetes environment.
5454

5555
## Creating the persistent volume
5656

57-
To create the persistent volume issue the following command:
57+
To create the persistent volume, issue the following command:
5858

5959
```
6060
kubectl create –f weblogic-domain-pv.yaml
@@ -70,7 +70,7 @@ Replace `PV_NAME` with the name of the persistent volume.
7070

7171
## Preparing to create the persistent volume claim
7272

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:
7474

7575
* Persistent volume claim name
7676
* Namespace name
@@ -80,7 +80,7 @@ The file `weblogic-domain-pvc.yaml` contains a template to claim a portion of th
8080

8181
## Creating the persistent volume claim
8282

83-
To create the persistent volume claim issue the following command:
83+
To create the persistent volume claim, issue the following command:
8484

8585
```
8686
kubectl create –f weblogic-domain-pvc.yaml
@@ -96,7 +96,7 @@ Replace `PVC_NAME` with the name of the persistent volume claim.
9696

9797
## Preparing to create the domain custom resource
9898

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:
100100

101101
* Domain name
102102
* Namespace name

0 commit comments

Comments
 (0)