Skip to content

Commit f93efcd

Browse files
rakillenrakillen
authored
JIRA WDT-347 - Reorganize server group configuration and other sections (#667)
1 parent 53ed38e commit f93efcd

File tree

7 files changed

+166
-196
lines changed

7 files changed

+166
-196
lines changed

‎README.md

Lines changed: 17 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
Many organizations are using WebLogic Server, with or without other Oracle Fusion Middleware components, to run their enterprise applications. As more and more organizations move toward Continuous Delivery of their applications, the importance of automated testing grows. Automating WebLogic Server domain creation and application deployment with hand-coded WLST scripts is challenging. After those scripts exist for a project, they must be maintained as the project evolves. The motivation for the Oracle WebLogic Server Deploy Tooling project is to remove the need for most users to write WLST scripts for routine domain creation and application deployment tasks. Instead, the project team can write a declarative, metadata model describing the domain and applications (with their dependent resources), and use one or more of the single-purpose tools provided that perform domain lifecycle operations based on the content of the model. The goal is to make it easy to stand up environments and perform domain lifecycle operations in a repeatable fashion based on a metadata model that can be treated as source and evolve as the project evolves.
44

55
## Table of Contents
6-
- [Features](#features-of-the-oracle-weblogic-server-deploy-tooling)
6+
- Features
77
- [Create Domain Tool](site/create.md)
88
- [Update Domain Tool](site/update.md)
99
- [Deploy Applications Tool](site/deploy.md)
@@ -14,74 +14,38 @@ Many organizations are using WebLogic Server, with or without other Oracle Fusio
1414
- [Prepare Model Tool](site/prepare.md)
1515
- [Extract Domain Resource Tool](site/kubernetes.md)
1616
- [Model Help Tool](site/model_help.md)
17-
- [The Model](#the-metadata-model)
17+
- The Model
1818
- [Top-Level Sections](#top-level-model-sections)
1919
- [Simple Example](#simple-example)
2020
- [Model Names](#model-names)
2121
- [Model Semantics](#model-semantics)
2222
- [Declaring Named MBeans to Delete](#declaring-named-mbeans-to-delete)
2323
- [Using Multiple Models](#using-multiple-models)
24-
- [Administration Server Configuration](site/admin_server.md)
25-
- [Model Security](site/security.md)
26-
- [Modeling Security Providers](site/security_providers.md)
27-
- [JRF Trust Service Identity Asserter](site/security_providers.md#trust-service-identity-asserter)
28-
- [Custom Security Providers](site/security_providers.md#custom-security-providers)
29-
- [Modeling WebLogic Users, Groups, and Roles](site/security_users_groups_roles.md)
30-
- [ODL Configuration](site/odl_configuration.md)
31-
- [Configuring Oracle HTTP Server (OHS)](site/ohs_configuration.md)
32-
- [Configuring Oracle WebLogic Server Kubernetes Operator](site/kubernetes.md)
33-
- [Model Samples](site/samples/samples.md)
3424
- [The Archive File](site/archive.md)
35-
- Configuration
36-
- [Custom Configuration](site/config/custom_configuration.md)
25+
- Model Use Cases
26+
- [Customizing the Administration Server](site/admin_server.md)
27+
- [Modeling a Configured Cluster](site/samples/configured_cluster.md)
28+
- [Modeling a JDBC Data Source](site/samples/jdbc.md)
29+
- [Modeling a Work Manager](site/samples/work_manager.md)
30+
- [Modeling Security Providers](site/security_providers.md)
31+
- [Modeling WebLogic Users, Groups, and Roles](site/security_users_groups_roles.md)
32+
- [Modeling ODL](site/odl_configuration.md)
33+
- [Modeling Oracle HTTP Server (OHS)](site/ohs_configuration.md)
34+
- [Targeting Server Groups](site/server_groups.md)
35+
- [Using WDT with Oracle WebLogic Server Kubernetes Operator](site/kubernetes.md)
36+
- Tool Configuration
3737
- [Model Filters](site/tool_filters.md)
3838
- [Type Definitions](site/type_def.md)
3939
- [Variable Injection](site/variable_injection.md)
40+
- [Custom Configuration](site/config/custom_configuration.md)
41+
- [Supported WLS Versions](site/wls_versions.md)
4042
- [Downloading and Installing](#downloading-and-installing-the-software)
4143
- [Developer Guide](site/developer/developer_guide.md)
4244
- [Known Issues](KnownIssues.md)
4345

4446
## Features of the Oracle WebLogic Server Deploy Tooling
4547

46-
The Oracle WebLogic Server Deploy Tooling is designed to support a wide range of WebLogic Server versions. This is possible because the underlying framework, upon which the tools are built, embeds a knowledge base that encodes information about WLST folders and attributes, making it possible for the tooling to know:
47-
48-
- The folder structures
49-
- Which folders are valid in the version of WLST being used
50-
- How to create folders
51-
- Which attributes a folder has in the version of WLST being used
52-
- The attribute data types and how to get/set their values (which isn't as easy as it might sound)
53-
- The differences between WLST online and WLST offline for working with folders and attributes
54-
55-
### Supported WebLogic Server Versions
56-
The following table specifies the supported WebLogic Server versions, along with the JDK versions, that must be used to run the WDT tool. You must set the `JAVA_HOME` environment variable to specify a JDK version different from the system default version.
57-
58-
To create a domain with the proper JDK (particularly if the `JAVA_HOME` is different from the one which will be used by the target domain), set the domain `JavaHome` attribute in the domain model.
59-
60-
Note that the WDT Encryption Model Tool used to encrypt and decrypt clear text passwords in the model and variable files, requires WDT to run with a minimum JDK version of 1.8.
61-
62-
| WebLogic Server Version | Tool JDK Version |
63-
|--------------------------|-------------------|
64-
| 10.3.6 | 1.7 |
65-
| 12.1.1 | 1.7, 1.8 |
66-
| 12.1.2 <sup>[1]</sup><sup>[2]</sup> | 1.7, 1.8 |
67-
| 12.1.3 | 1.7, 1.8 |
68-
| 12.2.1 <sup>[3]</sup> | 1.8 |
69-
| 12.2.1.1 <sup>[4]</sup> | 1.8 |
70-
| 12.2.1.2 | 1.8 |
71-
| 12.2.1.3 | 1.8 |
72-
| 12.2.1.4 <sup>[5]</sup> | 1.8 |
73-
| 14.1.1 | 1.8, 1.11 |
74-
75-
***1*** First release dynamic clusters are supported
76-
***2*** First release Coherence clusters are supported
77-
***3*** First release WLS roles are supported
78-
***4*** First release multitenancy is supported
79-
***5*** Last release multitenancy is supported
80-
81-
### Metadata model
82-
The metadata model, described in detail in the next section, is WebLogic Server version and WLST mode independent. As such, a metadata model written for an earlier version of WebLogic Server is designed to work with a newer version. There is no need to port your metadata model as part of the upgrade process. Of course, you may wish to add data to your metadata model to take advantage of new features in newer versions of WebLogic Server.
83-
84-
Currently, the project provides five single-purpose tools, all exposed as shell scripts (both Windows and UNIX scripts are provided):
48+
Currently, the project provides several single-purpose tools, all exposed as shell scripts (both Windows and UNIX scripts are provided):
8549

8650
- The [Create Domain Tool](site/create.md) (`createDomain`) understands how to create a domain and populate the domain with all resources and applications specified in the model.
8751
- The [Update Domain Tool](site/update.md) (`updateDomain`) understands how to update an existing domain and populate the domain with all resources and applications specified in the model, either in offline or online mode.

‎site/kubernetes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
## Configuring Oracle WebLogic Server Kubernetes Operator
1+
## Using WDT with Oracle WebLogic Server Kubernetes Operator
22

33
The Extract Domain Resource Tool can be used to create a domain resource file for use with the Oracle WebLogic Server Kubernetes Operator. This allows the domain configuration and the Kubernetes container configuration to be specified in a single model file.
44

‎site/samples/samples.md

Lines changed: 0 additions & 12 deletions
This file was deleted.

‎site/security.md

Lines changed: 0 additions & 7 deletions
This file was deleted.

‎site/server_groups.md

Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
### Targeting Server Groups
2+
3+
To create more complex domains with clusters of different types, it is necessary to control the targeting of server groups to managed servers. By default, all server groups in the domain type definition are targeted to all managed servers. To create a SOA domain with SOA and OSB clusters, simply add the OSB template and server group to the SOA domain definition, as shown below.
4+
5+
```json
6+
{
7+
"name": "SOA",
8+
"description": "SOA type domain definitions",
9+
"versions": {
10+
"12.2.1.3": "SOA_12213"
11+
},
12+
"definitions": {
13+
"SOA_12213": {
14+
"baseTemplate": "Basic WebLogic Server Domain",
15+
"extensionTemplates": [
16+
"Oracle SOA Suite",
17+
"Oracle Service Bus"
18+
],
19+
"serverGroupsToTarget": [ "JRF-MAN-SVR", "WSMPM-MAN-SVR", "SOA-MGD-SVRS", "OSB-MGD-SVRS-COMBINED" ],
20+
"dynamicClusterServerGroupsToTarget": [ "SOA-DYN-CLUSTER" ],
21+
"rcuSchemas": [ "STB", "WLS", "MDS", "IAU", "IAU_VIEWER", "IAU_APPEND", "OPSS", "UCSUMS", "SOAINFRA" ]
22+
}
23+
}
24+
}
25+
```
26+
27+
Then, use the `ServerGroupTargetingLimits` map in the `domainInfo` section to limit the targeting of the Web Services Manager, SOA, and OSB server groups to the `soa_cluster` or `osb_cluster`, as appropriate. In the example below, notice that the `JRF-MAN-SVR` server group is not listed; therefore, it will use the default targeting and be targeted to all managed servers. The value of each element in this section is a logical list of server and/or cluster names. As shown in the example, the value for each server group can be specified as a list, a comma-separated string, or a single-valued string. There is no semantic difference between listing a cluster's member server names versus using the cluster name; the example uses these simply to show what is possible.
28+
29+
```yaml
30+
domainInfo:
31+
AdminUserName: weblogic
32+
AdminPassword: welcome1
33+
ServerStartMode: prod
34+
ServerGroupTargetingLimits:
35+
'WSMPM-MAN-SVR': soa_cluster
36+
'SOA-MGD-SVRS': 'soa_server1,soa_server2'
37+
'OSB-MGD-SVRS-COMBINED': [ osb_server1, osb_server2 ]
38+
39+
topology:
40+
Name: soa_domain
41+
AdminServerName: AdminServer
42+
Cluster:
43+
soa_cluster:
44+
osb_cluster:
45+
Server:
46+
AdminServer:
47+
ListenAddress: myadmin.example.com
48+
ListenPort: 7001
49+
Machine: machine1
50+
SSL:
51+
Enabled: true
52+
ListenPort: 7002
53+
soa_server1:
54+
ListenAddress: managed1.example.com
55+
ListenPort: 8001
56+
Cluster: soa_cluster
57+
Machine: machine2
58+
SSL:
59+
Enabled: true
60+
ListenPort: 8002
61+
soa_server2:
62+
ListenAddress: managed2.example.com
63+
ListenPort: 8001
64+
Cluster: soa_cluster
65+
Machine: machine3
66+
SSL:
67+
Enabled: true
68+
ListenPort: 8002
69+
osb_server1:
70+
ListenAddress: managed1.example.com
71+
ListenPort: 9001
72+
Cluster: osb_cluster
73+
Machine: machine2
74+
SSL:
75+
Enabled: true
76+
ListenPort: 9002
77+
osb_server2:
78+
ListenAddress: managed2.example.com
79+
ListenPort: 9001
80+
Cluster: osb_cluster
81+
Machine: machine3
82+
SSL:
83+
Enabled: true
84+
ListenPort: 9002
85+
UnixMachine:
86+
machine1:
87+
NodeManager:
88+
ListenAddress: myadmin.example.com
89+
ListenPort: 5556
90+
machine2:
91+
NodeManager:
92+
ListenAddress: managed1.example.com
93+
ListenPort: 5556
94+
machine3:
95+
NodeManager:
96+
ListenAddress: managed2.example.com
97+
ListenPort: 5556
98+
SecurityConfiguration:
99+
NodeManagerUsername: weblogic
100+
NodeManagerPasswordEncrypted: welcome1
101+
```
102+
103+
#### Targeting Dynamic Cluster Server Groups
104+
Dynamic Cluster Server Groups are server groups that can be targeted to dynamic clusters. Dynamic clusters were added in WebLogic Server version 12.1.2. In WebLogic Server version 12.2.1.1, the ability to target a single dynamic server group to a dynamic cluster was added. In WebLogic Server Version 12.2.1.4, you now have the ability to target multiple dynamic server groups to a dynamic cluster.
105+
106+
To enable targeting of dynamic server groups to dynamic clusters, add the dynamicClusterServerGroupsToTarget entry with any dynamic server groups you wish to be targeted to the dynamic clusters in your model or domain. This list must only contain one dynamic server group if you are running a version of WebLogic Server earlier than 12.2.1.4.
107+
```json
108+
{
109+
"definitions": {
110+
"dynamicClusterServerGroupsToTarget" : [ "WSMPM-DYN-CLUSTER", "WSM-CACHE-DYN-CLUSTER" ]
111+
}
112+
}
113+
```
114+
If you wish to specify which dynamic server group to target to a dynamic server, add DynamicClusterServerGroupTargetingLimits to the domainInfo of your model. This entry can coexist with managed servers defined in ServerGroupTargetingLimits.
115+
```yaml
116+
domainInfo:
117+
AdminUserName: weblogic
118+
AdminPassword: welcome1
119+
ServerStartMode: prod
120+
DynamicClusterServerGroupTargetingLimits:
121+
'SOA-DYN-CLUSTER': 'soa_dynamic_cluster'
122+
```

0 commit comments

Comments
 (0)