Skip to content

minor edits #237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 1, 2018
Merged

minor edits #237

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions site/starting-domain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Starting a WebLogic domain

Startup of the domain is controlled by settings in the domain custom resource. The domain creation job, if used, will have created a domain custom resource YAML file. If the domain was created manually, this YAML file will also need to be created manually.
Startup of the domain is controlled by settings in the domain custom resource. If used, the domain creation job will have created a domain custom resource YAML file. If the domain was created manually, this YAML file will also need to be created manually.

An example of the domain custom resource YAML file is shown below:

Expand Down Expand Up @@ -96,10 +96,10 @@ The operator determines which servers to start using the following logic:
* If `startupControl` is set to `SPECIFIED`, then:

* The Administration Server will be started.
* Each server listed in a `serverStartup` section will be brought up to state that is specified in the `desiredState` in that section, `RUNNING` or `ADMIN`.
* For each cluster listed in a `clusterStartup` section, a number of servers in that cluster equal to the `replicas` setting will be brought up to state that is specified in the `desiredState` in that section, `RUNNING` or `ADMIN`. If `replicas` is not specified in `clusterStartup`, then the top-level `replicas` field in the domain custom resource will be used instead.
* Each server listed in a `serverStartup` section will be brought up to the state that is specified in the `desiredState` in that section, `RUNNING` or `ADMIN`.
* For each cluster listed in a `clusterStartup` section, a number of servers in that cluster, equal to the `replicas` setting, will be brought up to the state that is specified in the `desiredState` in that section, `RUNNING` or `ADMIN`. If `replicas` is not specified in `clusterStartup`, then the top-level `replicas` field in the domain custom resource will be used instead.

* If `startupControl` is set to `AUTO`, then:

* The operator will perform as if `startupControl` were set to `SPECIFIED`.
* For all clusters that do not have a `clusterStartup` section, a number of servers in that cluster equal to the top-level `replicas` setting will be brought up to `RUNNING` state.
* For all clusters that do not have a `clusterStartup` section, the number of servers in that cluster equal to the top-level `replicas` setting, will be brought up to the `RUNNING` state.