Skip to content

Commit a21febe

Browse files
committed
Merge branch 'docs-release-3.2.6' into 'main'
Adding doc updates for Release 3.2.6 See merge request weblogic-cloud/weblogic-deploy-tooling!1515
2 parents 7c382e9 + aeeeae9 commit a21febe

File tree

3 files changed

+62
-22
lines changed

3 files changed

+62
-22
lines changed

documentation/3.0/content/release-notes/_index.md

Lines changed: 5 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
+++
22
title = "Release Notes"
33
date = 2019-02-22T15:27:38-05:00
4-
weight = 84
4+
weight = 83
55
pre = "<b> </b>"
66
+++
77

88

9-
### Changes in Release 3.2.5
9+
### Changes in Release 3.2.6
1010
- [Major New Features](#major-new-features)
1111
- [Other Changes](#other-changes)
1212
- [Bugs Fixes](#bug-fixes)
@@ -17,15 +17,11 @@ pre = "<b> </b>"
1717
None
1818

1919
#### Other Changes
20-
None
20+
- #1514 - Added the ability to disable the RCU drop schema step when running Create Domain with `-run_rcu`.
2121

2222
#### Bug Fixes
23-
#1506 - Fixed an issue with online discovery of the JMS `ErrorDestination` attribute (GitHub #1494).
24-
#1507 - Added documentation for the WDT Discover Domain tool's limitation regarding users and groups in the `DefaultAuthenticator` (GitHub #1493).
25-
#1508 - Fixed an issue with Update Domain that was causing the Oracle JDBC driver to throw `FileNotFoundException`
26-
when using a JRF domain with an ATP database.
27-
#1509 - Fixed an issue with online discovery of custom security providers that caused the implementation class name to
28-
be added to the model instead of the interface class name (GitHub #1495).
23+
- #1511 - Fixed an error message to make it more helpful.
24+
- #1513 - Fixed issues with sparse RCU Data Source template merging when creating JRF domains.
2925

3026
#### Known Issues
3127
None
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
+++
2+
title = "Release Notes 3.2.5"
3+
date = 2019-02-22T15:27:38-05:00
4+
weight = 84
5+
pre = "<b> </b>"
6+
+++
7+
8+
9+
### Changes in Release 3.2.5
10+
- [Major New Features](#major-new-features)
11+
- [Other Changes](#other-changes)
12+
- [Bugs Fixes](#bug-fixes)
13+
- [Known Issues](#known-issues)
14+
15+
16+
#### Major New Features
17+
None
18+
19+
#### Other Changes
20+
None
21+
22+
#### Bug Fixes
23+
#1506 - Fixed an issue with online discovery of the JMS `ErrorDestination` attribute (GitHub #1494).
24+
#1507 - Added documentation for the WDT Discover Domain tool's limitation regarding users and groups in the `DefaultAuthenticator` (GitHub #1493).
25+
#1508 - Fixed an issue with Update Domain that was causing the Oracle JDBC driver to throw `FileNotFoundException`
26+
when using a JRF domain with an ATP database.
27+
#1509 - Fixed an issue with online discovery of custom security providers that caused the implementation class name to
28+
be added to the model instead of the interface class name (GitHub #1495).
29+
30+
#### Known Issues
31+
None
32+
33+
See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

documentation/3.0/content/userguide/tools-config/tool_prop.md

Lines changed: 24 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,18 +10,29 @@ weight: 4
1010

1111
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.
1212

13-
| Property | Description |
14-
|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
15-
| `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). |
13+
| Property | Description |
14+
|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
15+
| `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). |
2529

2630
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:
33+
34+
```shell
35+
WLSDEPLOY_PROPERTIES="-Dwdt.config.connect.timeout=5000 -Dwdt.config.disable.rcu.drop.schema=true"
36+
export WLSDEPLOY_PROPERTIES
37+
$WLSDEPLOY_HOME/bin/createDomain.sh ...
38+
```

0 commit comments

Comments
 (0)