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: integration-tests/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ externalRestEnabled: true
98
98
javaLoggingLevel: FINE
99
99
```
100
100
101
-
src/integration-tests/resources/domainonpvwlst.yaml - See "Input Yaml to the test". For all the properties that are not defined here, the default values in the sample inputs are used while generating inputs yaml.
101
+
src/integration-tests/resources/domainonpvwlst.yaml - See [Input Yaml to the test](#input-yaml-to-the-test). For all the properties that are not defined here, the default values in the sample inputs are used while generating inputs yaml.
102
102
103
103
```
104
104
adminServerName: admin-server
@@ -126,7 +126,7 @@ The input yaml file(for example, domainonpvwlst.yaml) to the java test is used t
126
126
- custom attributes that are used to provide more flexibility for creating the domain.
127
127
128
128
Below are the load balancer attributes:
129
-
- loadBalancer: value can be TRAEFIK or VOYAGER, default is TRAEFIK
129
+
- loadBalancer: value can be `TRAEFIK` or `VOYAGER`, default is `TRAEFIK`
130
130
- loadBalancerWebPort: web port for the load balancer
131
131
- ingressPerDomain: create ingress per domain or one ingress for all domains in multiple domain configuration, default is true.
Copy file name to clipboardExpand all lines: integration-tests/USECASES.MD
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,22 +2,22 @@
2
2
3
3
Java integration tests cover the below use cases:
4
4
5
-
Quick test Configuration & Use Cases -
5
+
## Quick test Configuration & Use Cases -
6
6
7
7
|||
8
8
| --- | --- |
9
9
| Operator Configuration | operator1 deployed in `weblogic-operator1` namespace and manages domains in `default` and `test1` namespaces |
10
10
| Domain Configuration | Domain on PV using WLST, Traefik load balancer |
11
11
12
-
Basic Use Cases
12
+
**Basic Use Cases**
13
13
14
14
1. Create operator `operator1` which manages `default` and `test1` namespaces, verify it's deployed successfully, pods created, operator ready and verify external REST service, if configured.
15
15
2. Create domain `domain1` in `default` namespace and verify the pods, services are created and servers are in ready state.
16
16
3. Verify the admin external service by accessing the admin REST endpoint with `nodeport` in URL.
17
17
4. Verify admin t3 channel port by exec into the admin pod and deploying webapp using the channel port for WLST.
18
18
5. Verify web app load balancing by accessing the webapp using `loadBalancerWebPort`.
19
19
20
-
Advanced Use Cases
20
+
**Advanced Use Cases**
21
21
22
22
6. Verify domain life cycle (destroy and create) should not have any impact on operator managing the domain and web app load balancing and admin external service.
23
23
7. Cluster scale up/down using operator REST endpoint, webapp load balancing should adjust accordingly.
@@ -29,7 +29,7 @@ Also the below use cases are covered for Quick test:
29
29
10. Shutdown the domain by changing domain `serverStartPolicy` to `NEVER`.
30
30
31
31
32
-
Full test Configuration & Use Cases - Runs Quick test Configuration & Use cases and the below
32
+
## Full test Configuration & Use Cases - Runs Quick test Configuration & Use cases and the below
33
33
34
34
|||
35
35
| --- | --- |
@@ -74,9 +74,7 @@ Basic Use Cases described above are verified in all the domain configurations. A
74
74
| Server pods restarted by changing includeServerOutInPodLog | Verify admin and managed server pods being restarted by property change: includeServerOutInPodLog: true --> includeServerOutInPodLog: false |
75
75
| Server pods restarted by changing logHomeEnable | Verify admin and managed server pods being restarted by property change: logHomeEnabled: true --> logHomeEnabled: false |
76
76
77
-
Configuration Overrides Usecases
78
-
79
-
| Override | Usecase |
77
+
| Overrides | Usecase |
80
78
| --- | --- |
81
79
| Configuration override | Override the administration server properties `connect-timeout`, `max-message-size`, `restart-max`, `debug-server-life-cycle` and `debug-jmx-core` debug flags. Also T3Channel public address using Kubernetes secret. The override is verified by JMX client connecting to the serverConfig MBean tree and the values are checked against the expected values. The test client connects to the overridden T3 public address and port to connect to the MBean servers |
82
80
| JDBC Resource Override | Override JDBC connection pool properties; `initialCapacity`, `maxCapacity`, `test-connections-on-reserve`, `connection-harvest-max-count`, `inactive-connection-timeout-seconds`. Override the JDBC driver parameters like data source `URL`, `DB``user` and `password` using kubernetes secret. The test verifies the overridden functionality datasource `URL`, `user`, `password` by getting the data source connection and running DDL statement it is connected to. |
0 commit comments