Skip to content

Commit efecf8d

Browse files
committed
Issue #144 - Incorporated changes from review
1 parent 365df6e commit efecf8d

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

README.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -223,9 +223,19 @@ One of the primary goals of the WebLogic Deploy Tooling is to support a sparse m
223223

224224
### Declaring Named MBeans to Delete
225225

226-
With WebLogic Deploy Tooling release 1.3.0, you can specify named items in the model to be deleted using the Create Domain, Update Domain, and Deploy Applications Tools. Named items are those that have multiple instances that are distinguished by user-provided names, such as managed servers, data sources, and security realms. Items to be deleted are prepended with an exclamation point (!) in the model.
226+
With WebLogic Deploy Tooling release 1.3.0, you can specify named items in the model to be deleted using the Create Domain, Update Domain, and Deploy Applications Tools. Named items are those that have multiple instances that are distinguished by user-provided names, such as managed servers, data sources, and security realms. Items to be deleted are prepended with an exclamation point (!) in the model.
227227

228-
This feature can be used to remove items that were created by WebLogic Server templates. For example, the basic template creates a default security realm called ```myrealm```. If a user chooses to declare a custom realm, ```myrealm``` is no longer needed. In this example, ```myrealm``` will be deleted, and the custom realm ```newrealm``` will be created, and declared as the default realm:
228+
In this example, the managed server ```obsoleteServer``` will be deleted, and ```newServer``` will be created:
229+
230+
```yaml
231+
Server:
232+
!obsoleteServer:
233+
newServer:
234+
ListenAddress: 127.0.0.1
235+
ListenPort: 9005
236+
```
237+
238+
This feature can also remove items that were created by WebLogic Server templates. For example, the basic template creates a default security realm called ```myrealm```. If a user chooses to declare a custom realm, ```myrealm``` is no longer needed. In this example, ```myrealm``` will be deleted, and the custom realm ```newrealm``` will be created, and declared as the default realm:
229239

230240
```yaml
231241
SecurityConfiguration:
@@ -241,16 +251,6 @@ This feature does not apply to named security providers within a realm. These it
241251

242252
This feature cannot be use to un-deploy applications or remove libraries.
243253

244-
This feature can also be used for simple updates to domain configuration. In this example, the managed server ```obsoleteServer``` will be deleted, and ```newServer``` will be created:
245-
246-
```yaml
247-
Server:
248-
!obsoleteServer:
249-
newServer:
250-
ListenAddress: 127.0.0.1
251-
ListenPort: 9005
252-
```
253-
254254
### Using Multiple Models
255255

256256
The Create Domain, Update Domain, Deploy Applications, and Validate Model Tools allow the specification of multiple models on the command line. For example:

0 commit comments

Comments
 (0)