Skip to content

Commit 53ed38e

Browse files
Document the boot.properties behavior in the README (#666)
* Document the boot.properties behavior in the README * Update create.md
1 parent 30d32e9 commit 53ed38e

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

site/create.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,3 +30,24 @@ If the model or variables file contains encrypted passwords, add the `-use_encry
3030
### Using Multiple Models
3131

3232
The Create Domain Tool supports the use of multiple models, as described in [Using Multiple Models](../README.md#using-multiple-models).
33+
34+
### Development Domain and `boot.properties`
35+
36+
When creating a development domain, WDT provides the convenience of making a `boot.properties` file for each of the servers in the domain. The `boot.properties` file will contain encrypted values of the Administration Server user name and password. When the Administration Server or Managed Server is started, WebLogic Server will bypass the prompt for credentials, and instead use the credentials from the `boot.properties` file.
37+
38+
A domain is in production mode if the `ServerStartMode` option is set to `prod` or the domain `ProductionModeEnabled` is set to `true`. The default value for both of these attributes is development mode.
39+
40+
The `boot.properties` file is stored in the domain home on the machine where WDT runs. It is stored for each server as `<domain_home>/servers/<server_name>/security/boot.properties`.
41+
42+
The following is a model example with both attributes explicitly set to development mode.
43+
44+
```yaml
45+
domainInfo:
46+
AdminUserName: weblogic
47+
AdminPassword: welcome1
48+
ServerStartMode: dev
49+
topology:
50+
Name: "my-domain"
51+
AdminServerName: "admin-server"
52+
ProductionModeEnabled: false
53+
```

0 commit comments

Comments
 (0)