Skip to content

Commit 690d584

Browse files
committed
Merge branch 'docs-3.3.0' into 'main'
Doc updates for 3.3.0 See merge request weblogic-cloud/weblogic-deploy-tooling!1520
2 parents 6564e3d + feb9a1a commit 690d584

File tree

6 files changed

+154
-38
lines changed

6 files changed

+154
-38
lines changed

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

Lines changed: 9 additions & 5 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 = 83
4+
weight = 82
55
pre = "<b> </b>"
66
+++
77

88

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

1919
#### Other Changes
20-
- #1514 - Added the ability to disable the RCU drop schema step when running Create Domain with `-run_rcu`.
20+
- #1517 - Added a `postCreateRcuSchemasScript` element to the typedef file definitions to accommodate extra
21+
schema patching work required for Oracle Identity Governance domain creation.
22+
- #1519 - Added `rcu_admin_user` field to the `domainInfo:/RCUDbInfo` section to replace `rcu_db_user`, which is now
23+
deprecated and will be removed in a future release. This field is optional and will default to the appropriate
24+
admin user name: `admin` when using an ATP database and `SYS` otherwise.
2125

2226
#### Bug Fixes
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.
27+
- #1518 - Fixed an issue when using an ATP database as the RCU schema repository that was causing
28+
`config/fmwconfig/jps-config.xml` to contain a clear text password after JRF domain creation.
2529

2630
#### Known Issues
2731
None
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
+++
2+
title = "Release Notes 3.2.6"
3+
date = 2019-02-22T15:27:38-05:00
4+
weight = 83
5+
pre = "<b> </b>"
6+
+++
7+
8+
9+
### Changes in Release 3.2.6
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+
- #1514 - Added the ability to disable the RCU drop schema step when running Create Domain with `-run_rcu`.
21+
22+
#### Bug Fixes
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.
25+
26+
#### Known Issues
27+
None
28+
29+
See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

documentation/3.0/content/userguide/database/connect-db.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -82,9 +82,9 @@ domainInfo:
8282
RCUDbInfo:
8383
databaseType : 'ATP'
8484
rcu_prefix : DEV
85+
rcu_admin_user : admin
8586
rcu_admin_password: <database admin password is required only when you specify -run_rcu flag>
8687
rcu_schema_password : <RCU schema password>
87-
rcu_db_user : admin
8888
tns.alias : <tns alias name. e.g. dbname_tp>
8989
javax.net.ssl.keyStorePassword : <atp wallet password when generating the wallet from Oracle Cloud Console>
9090
javax.net.ssl.trustStorePassword : <atp wallet password when generating the wallet from Oracle Cloud Console>
@@ -115,9 +115,9 @@ domainInfo:
115115
databaseType : 'ATP'
116116
rcu_prefix : DEV
117117
rcu_db_conn_string: <required URL string for use with -run_rcu>
118+
rcu_admin_user : admin
118119
rcu_admin_password: <database admin password is required only when you specify -run_rcu flag>
119120
rcu_schema_password : <RCU schema password>
120-
rcu_db_user : admin
121121
tns.alias : my_atp_db_medium
122122
javax.net.ssl.keyStorePassword : wlsdeploy/dbWallets/rcu/keystore.jks
123123
javax.net.ssl.trustStorePassword : wlsdeploy/dbWallets/rcu/truststore.jks
@@ -211,12 +211,12 @@ For a typical database, use the following example:
211211
domainInfo:
212212
RCUDbInfo:
213213
rcu_prefix : DEV
214-
# Optional rcu_db_user for creating RCU schema if -run_rcu flag is specified. Default user is SYS if not specified.
214+
# Optional rcu_admin_user for creating RCU schema if -run_rcu flag is specified. Default user is SYS if not specified.
215215
# This user must have SYSDBA privilege and this is the equivalent of -dbUser in the RCU utility.
216-
rcu_db_user: superuser
217-
rcu_schema_password : <rcu schema password, will be prompted if not specified>
216+
rcu_admin_user: superuser
218217
rcu_admin_password : <database admin password is required only when you specify -run_rcu flag, will be prompted
219-
if not specified>
218+
if not specified>
219+
rcu_schema_password : <rcu schema password, will be prompted if not specified>
220220
rcu_db_conn_string : dbhost:1521/pdborcl
221221
```
222222

documentation/3.0/content/userguide/limitations/limitations.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,3 +61,25 @@ discovered model to use the same user and group store so that there is no need t
6161
new user and group store is desired, these external stores natively provide export and import mechanisms for moving
6262
users and groups. If this is not an option, then the user will need to hand-edit the discovered model file to add any
6363
users and groups not created by default.
64+
65+
#### JRF Domain configuration files containing clear text password
66+
67+
**ISSUE**: After a JRF domain is created, the `jps-config.xml` and `jps-config-jse.xml` files contain clear text password for the key store.
68+
69+
**ACTION**: You will need to create a key store using Oracle Wallet and change the key store provider priority in the JVM. See Oracle Support Doc ID 2215283.1 for details.
70+
If you are creating a JRF domain using Oracle Autonomous Transaction Database, you can use the SSO key stores instead of JKS key stores,
71+
the generated `jps-config.xml` and `jps-config-jse.xml` files will then use the SSO key stores without any clear text password.
72+
73+
```yaml
74+
domainInfo:
75+
RCUDbInfo:
76+
databaseType : ATP
77+
rcu_prefix : FMW
78+
rcu_schema_password : '...'
79+
rcu_admin_password: '...'
80+
rcu_db_user : admin
81+
tns.alias : myatp_tp
82+
javax.net.ssl.keyStoreType: SSO
83+
javax.net.ssl.trustStoreType: SSO
84+
```
85+

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

Lines changed: 33 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,9 @@ weight: 2
66
---
77

88

9-
WebLogic Deploy Tooling has an extensible domain type system. The three built-in domain types (`WLS`, `RestrictedJRF`, and `JRF`) are defined in JSON files of the same name in the `WLSDEPLOY_HOME/lib/typedefs` directory. For example, the `JRF` domain type is defined in the `WLSDEPLOY_HOME/lib/typedefs/JRF.json` file with similar content, as shown below.
9+
WebLogic Deploy Tooling has an extensible domain type system. The three built-in domain types (`WLS`, `RestrictedJRF`,
10+
and `JRF`) are defined in JSON files of the same name in the `WLSDEPLOY_HOME/lib/typedefs` directory. For example,
11+
the `JRF` domain type is defined in the `WLSDEPLOY_HOME/lib/typedefs/JRF.json` file with similar content, as shown below.
1012

1113
```json
1214
{
@@ -82,13 +84,17 @@ weight: 2
8284
}
8385
```
8486

85-
This file tells the Create Domain Tool which templates to use to create the domain, which server groups to target, and even which RCU schemas to create, all based on the installed version of WebLogic Server.
87+
This file tells the Create Domain Tool which templates to use to create the domain, which server groups to target, and
88+
even which RCU schemas to create, all based on the installed version of WebLogic Server.
8689

87-
New domain types can be defined by creating a new JSON file with the same structure in the `WLSDEPLOY_HOME/lib/typedefs` directory.
90+
New domain types can be defined by creating a new JSON file with the same structure in the
91+
`WLSDEPLOY_HOME/lib/typedefs` directory.
8892

89-
Another option is to create this file in the [Custom configuration]({{< relref "/userguide/tools-config/custom_config.md" >}}) directory `$WDT_CUSTOM_CONFIG/typedefs`.
93+
Another option is to create this file in the
94+
[Custom configuration]({{< relref "/userguide/tools-config/custom_config.md" >}}) directory `$WDT_CUSTOM_CONFIG/typedefs`.
9095

91-
For example, to define a `SOA` domain type for 12.2.1.3, add the `typedefs/SOA.json` file with similar content, as shown below.
96+
For example, to define a `SOA` domain type for 12.2.1.3, add the `typedefs/SOA.json` file with similar content,
97+
as shown below.
9298

9399
```json
94100
{
@@ -110,13 +116,21 @@ weight: 2
110116
}
111117
```
112118

113-
After the new domain `typedef` file exists, simply specify the new domain type name to the `createDomain` script, being sure to reference an Oracle Home with the required components installed. For pre-12.2.1 versions, the `-wlst_path` argument must be used to point to the product home where the appropriate WLST shell script exists; for example, for SOA 12.1.3, add `-wlst_path <ORACLE_HOME>/soa` so that the tool uses the WLST shell script with the proper environment for SOA domains. In 12.2.1 and later, this is no longer necessary because the WLST shell script in the standard `<ORACLE_HOME>oracle_common/common/bin` directory will automatically load all components in the Oracle Home. Using the new domain type, simply run the following command to run RCU and create the SOA domain with all of its resources and applications deployed.
119+
After the new domain `typedef` file exists, simply specify the new domain type name to the `createDomain` script,
120+
being sure to reference an Oracle Home with the required components installed. For pre-12.2.1 versions, the
121+
`-wlst_path` argument must be used to point to the product home where the appropriate WLST shell script exists; for
122+
example, for SOA 12.1.3, add `-wlst_path <ORACLE_HOME>/soa` so that the tool uses the WLST shell script with the
123+
proper environment for SOA domains. In 12.2.1 and later, this is no longer necessary because the WLST shell script
124+
in the standard `<ORACLE_HOME>oracle_common/common/bin` directory will automatically load all components in the
125+
Oracle Home. Using the new domain type, simply run the following command to run RCU and create the SOA domain with
126+
all of its resources and applications deployed.
114127

115-
weblogic-deploy\bin\createDomain.cmd -oracle_home d:\SOA12213 -domain_type SOA -domain_parent d:\demo\domains -model_file DemoDomain.yaml -archive_file DemoDomain.zip -variable_file DemoDomain.properties -run_rcu -rcu_db mydb.example.com:1539/PDBORCL -rcu_prefix DEMO [-rcu_db_user SYS]
128+
weblogic-deploy\bin\createDomain.cmd -oracle_home d:\SOA12213 -domain_type SOA -domain_parent d:\demo\domains -model_file DemoDomain.yaml -archive_file DemoDomain.zip -variable_file DemoDomain.properties -run_rcu
116129

117130
#### Custom extension templates
118131

119-
The `customExtensionTemplates` attribute can be used to specify custom extension templates to be applied to the domain. These should be specified as absolute file paths, and can use tokens.
132+
The `customExtensionTemplates` attribute can be used to specify custom extension templates to be applied to the domain.
133+
These should be specified as absolute file paths, and can use tokens.
120134

121135
```json
122136
{
@@ -140,11 +154,13 @@ weight: 2
140154
}
141155
```
142156

143-
If there are any server groups in the custom template that should be targeted to managed servers, they should be specified in the `serverGroupsToTarget` attribute, similar to `MY_MAN_SVR` in the example above.
157+
If there are any server groups in the custom template that should be targeted to managed servers, they should be
158+
specified in the `serverGroupsToTarget` attribute, similar to `MY_MAN_SVR` in the example above.
144159

145160
#### Using compact profile
146161

147-
The `topologyProfile` field can be used to create a domain using a specific profile for each of the templates. This partial example will apply the compact profile for each of the specified templates.
162+
The `topologyProfile` field can be used to create a domain using a specific profile for each of the templates. This
163+
partial example will apply the compact profile for each of the specified templates.
148164
```json
149165
{
150166
"copyright": "Copyright (c) 2022, Oracle Corporation and/or its affiliates. All rights reserved.",
@@ -155,13 +171,17 @@ weight: 2
155171
...
156172
}
157173
```
158-
WebLogic Deploy Tooling provides the `JRF-Compact.json` type definition file that can be used to create a JRF domain using the compact profile.
174+
WebLogic Deploy Tooling provides the `JRF-Compact.json` type definition file that can be used to create a JRF domain
175+
using the compact profile.
159176

160177
#### Targeting in earlier WebLogic Server versions
161178

162-
Templates in WebLogic Server versions prior to 12.2.1 may require the use of the `applyJRF` WLST command to correctly target resources to the correct clusters and servers. The default behavior for WebLogic Deploy Tooling is to invoke `applyJRF` only when the `extensionTemplates` list includes JRF templates.
179+
Templates in WebLogic Server versions prior to 12.2.1 may require the use of the `applyJRF` WLST command to correctly
180+
target resources to the correct clusters and servers. The default behavior for WebLogic Deploy Tooling is to invoke
181+
`applyJRF` only when the `extensionTemplates` list includes JRF templates.
163182

164-
A custom type definition file can require `applyJRF` to be invoked after the templates are added. This is done by setting the `targeting` attribute to `APPLY_JRF`, as in this example:
183+
A custom type definition file can require `applyJRF` to be invoked after the templates are added. This is done by
184+
setting the `targeting` attribute to `APPLY_JRF`, as in this example:
165185

166186
```json
167187
{

0 commit comments

Comments
 (0)