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/limitations/limitations.md
+22Lines changed: 22 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -61,3 +61,25 @@ discovered model to use the same user and group store so that there is no need t
61
61
new user and group store is desired, these external stores natively provide export and import mechanisms for moving
62
62
users and groups. If this is not an option, then the user will need to hand-edit the discovered model file to add any
63
63
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.
Copy file name to clipboardExpand all lines: documentation/3.0/content/userguide/tools-config/domain_def.md
+33-13Lines changed: 33 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,9 @@ weight: 2
6
6
---
7
7
8
8
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.
10
12
11
13
```json
12
14
{
@@ -82,13 +84,17 @@ weight: 2
82
84
}
83
85
```
84
86
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.
86
89
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.
88
92
89
-
Another option is to create this file in the [Custom configuration]({{< relref "/userguide/tools-config/custom_config.md" >}}) directory `$WDT_CUSTOM_CONFIG/typedefs`.
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.
92
98
93
99
```json
94
100
{
@@ -110,13 +116,21 @@ weight: 2
110
116
}
111
117
```
112
118
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
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.
120
134
121
135
```json
122
136
{
@@ -140,11 +154,13 @@ weight: 2
140
154
}
141
155
```
142
156
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.
144
159
145
160
#### Using compact profile
146
161
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.
148
164
```json
149
165
{
150
166
"copyright": "Copyright (c) 2022, Oracle Corporation and/or its affiliates. All rights reserved.",
@@ -155,13 +171,17 @@ weight: 2
155
171
...
156
172
}
157
173
```
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.
159
176
160
177
#### Targeting in earlier WebLogic Server versions
161
178
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.
163
182
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:
0 commit comments