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: documentation/3.0/content/userguide/tools-config/tool_prop.md
+24-13Lines changed: 24 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -10,18 +10,29 @@ weight: 4
10
10
11
11
If a property is removed from the file, or a property value is incorrectly formatted, a `WARNING` message is logged and an internal default value used instead of the missing or bad value.
|`connect.timeout`| The number of milliseconds that WLST waits for the online `connect` command to complete. A value of 0 means the operation will not timeout. |
16
-
|`activate.timeout`| The number of milliseconds that WLST waits for the activation of configuration changes to complete. A value of -1 means the operation will not timeout. |
17
-
|`deploy.timeout`| The number of milliseconds that WLST waits for the undeployment process to complete. A value of 0 means the operation will not timeout. |
18
-
|`redeploy.timeout`| The number of milliseconds that WLST waits for the redeployment process to complete. A value of 0 means the operation will not timeout. |
19
-
|`start.application.timeout`| The number of milliseconds that WLST waits for the start application process to complete. A value of 0 means the operation will not timeout. |
20
-
|`stop.application.timeout`| The number of milliseconds that WLST waits for the stop application process to complete. A value of 0 means the operation will not timeout. |
21
-
|`set.server.groups.timeout`| Specifies the amount of time the set server groups connection can be inactive before the connection times out. |
22
-
|`wlst.edit.lock.acquire.timeout`| Specifies the amount of time in milliseconds the WLST online `startEdit` command will wait trying to acquire the edit lock before it times out. |
23
-
|`wlst.edit.lock.release.timeout`| Specifies the amount of time in milliseconds the WLST online `startEdit` command will wait for the edit lock to be released before releasing it automatically. |
24
-
|`wlst.edit.lock.exclusive`| Specifies whether the edit lock acquired by `startEdit` should be exclusive or shared (default is shared). |
|`connect.timeout`| The number of milliseconds that WLST waits for the online `connect` command to complete. A value of 0 means the operation will not timeout. |
16
+
|`activate.timeout`| The number of milliseconds that WLST waits for the activation of configuration changes to complete. A value of -1 means the operation will not timeout. |
17
+
|`deploy.timeout`| The number of milliseconds that WLST waits for the undeployment process to complete. A value of 0 means the operation will not timeout. |
18
+
|`redeploy.timeout`| The number of milliseconds that WLST waits for the redeployment process to complete. A value of 0 means the operation will not timeout. |
19
+
|`undeploy.timeout`| The number of milliseconds that WLST waits for the undeployment process to complete. A value of 0 means the operation will not timeout. |
20
+
|`start.application.timeout`| The number of milliseconds that WLST waits for the start application process to complete. A value of 0 means the operation will not timeout. |
21
+
|`stop.application.timeout`| The number of milliseconds that WLST waits for the stop application process to complete. A value of 0 means the operation will not timeout. |
22
+
|`set.server.groups.timeout`| Specifies the amount of time the set server groups connection can be inactive before the connection times out. |
23
+
|`wlst.edit.lock.acquire.timeout`| Specifies the amount of time in milliseconds the WLST online `startEdit` command will wait trying to acquire the edit lock before it times out. |
24
+
|`wlst.edit.lock.release.timeout`| Specifies the amount of time in milliseconds the WLST online `startEdit` command will wait for the edit lock to be released before releasing it automatically. |
25
+
|`wlst.edit.lock.exclusive`| Specifies whether the edit lock acquired by `startEdit` should be exclusive or shared (default is shared). |
26
+
|`yaml.max.file.size`| The maximum size of the YAML model file that the WDT SnakeYAML parser will allow. The default value of '0' uses the SnakeYAML default setting of 3145728 (i.e., 3 MB). |
27
+
|`use.deprecation.exit.code`| Whether deprecation messages should cause WDT tools to exit with a non-zero exit code (default is false). |
28
+
|`disable.rcu.drop.schema`| Whether the RCU drop step should be skipped when running Create Domain with the `-run_rco` switch (default is false). |
25
29
26
30
You can override the value of a single property using a Java System property with the name `wdt.config.<tool-property-name>`.
27
-
For example, adding `-Dwdt.config.connect.timeout=5000` will set the effective `connect.timeout` property to 5000 milliseconds, regardless of what the value in the tool.properties file might be.
31
+
For example, adding `-Dwdt.config.connect.timeout=5000` will set the effective `connect.timeout` property to 5000 milliseconds, regardless of what the value in the tool.properties file might be. To pass
32
+
one or more of these properties to a WDT shell script (e.g., `createDomain.sh`), simply set the WLSDEPLOY_PROPERTIES environment variable prior to calling the shell script. For example:
0 commit comments