web enabled: false

ibm-messaging · Jul 14, 2022 · b2362b9 · b2362b9
1 parent f5ba493
commit b2362b9
Show file tree

Hide file tree

Showing 18 changed files with 33 additions and 29 deletions.
diff --git a/01-tls/README.md b/01-tls/README.md
@@ -294,7 +294,7 @@ spec:
           name: qmgr
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example
@@ -366,6 +366,15 @@ The above points to the configmap with MQSC statements we created earlier. The M
 
 Setting the environment variable `MQSNOAUT=yes` disables user authentication (clients don't have to provide userid and password when connecting, and user authority to access resources is not checked). In CP4I, non-production queue managers have this setting by default.
 
+* MQ Web Console:
+
+```
+  web:
+    enabled: false
+```
+
+In Cloud Pak for Integration, the MQ Web Console is accessed from Platform Navigator. We are using the minimum configuration needed to run a queue manager, so are setting this to `enabled: false`. If you enable this setting to use the MQ Web Console, you must install the Cloud Pak for Integration operator and create an instance of Platform Navigator. 
+
 * Queue manager key and certificate:
 
 ```

diff --git a/01-tls/deploy-qm1-qmgr.sh b/01-tls/deploy-qm1-qmgr.sh
@@ -94,7 +94,7 @@ spec:
           name: qmgr
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/02-mtls/README.md b/02-mtls/README.md
@@ -319,7 +319,7 @@ spec:
           name: qmgr
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/02-mtls/deploy-qm2-qmgr.sh b/02-mtls/deploy-qm2-qmgr.sh
@@ -113,7 +113,7 @@ spec:
           name: qmgr
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/03-auth/README.md b/03-auth/README.md
@@ -279,7 +279,7 @@ spec:
         type: ephemeral
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/03-auth/deploy-qm3-qmgr.sh b/03-auth/deploy-qm3-qmgr.sh
@@ -119,7 +119,7 @@ spec:
         type: ephemeral
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/04-app2/README.md b/04-app2/README.md
@@ -350,7 +350,7 @@ spec:
         type: ephemeral
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/04-app2/deploy-qm4-qmgr.sh b/04-app2/deploy-qm4-qmgr.sh
@@ -155,7 +155,7 @@ spec:
         type: ephemeral
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/05-pvc/README.md b/05-pvc/README.md
@@ -332,7 +332,7 @@ spec:
         enabled: false
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/05-pvc/deploy-qm5-qmgr.sh b/05-pvc/deploy-qm5-qmgr.sh
@@ -164,7 +164,7 @@ spec:
         enabled: false
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/06-native-ha/README.md b/06-native-ha/README.md
@@ -339,7 +339,7 @@ spec:
         enabled: false
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/06-native-ha/deploy-qm6-qmgr.sh b/06-native-ha/deploy-qm6-qmgr.sh
@@ -164,7 +164,7 @@ spec:
         enabled: false
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/07-mqx/README.md b/07-mqx/README.md
@@ -267,7 +267,7 @@ spec:
         type: ephemeral
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/07-mqx/deploy-qm7-qmgr.sh b/07-mqx/deploy-qm7-qmgr.sh
@@ -129,7 +129,7 @@ spec:
         type: ephemeral
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/08-jms/README.md b/08-jms/README.md
@@ -262,7 +262,7 @@ spec:
         type: ephemeral
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/08-jms/deploy-qm8-qmgr.sh b/08-jms/deploy-qm8-qmgr.sh
@@ -108,7 +108,7 @@ spec:
         type: ephemeral
   version: 9.2.4.0-r1
   web:
-    enabled: true
+    enabled: false
   pki:
     keys:
       - name: example

diff --git a/09-rest-basic/README.md b/09-rest-basic/README.md
@@ -306,27 +306,24 @@ There are similarities and differences between this queue manager and, for examp
 
 * Both queue managers give permission to a user, `app1`, to connect to the queue manager and put to/get from Q1. On `qm3`, the clients connect to a Server Connection channel, and authenticate by presenting a TLS certificate. On this queue manager, the client authenticates with userid and password, presented in a basic HTTP header.
 
-* On all previous queue examples, the queue manager was created with:
+* Same as on all previous examples, the queue manager was created with:
 ```
   web:
-    enabled: true
+    enabled: false
 ```
 
-With this setting, Console and REST access to the queue manager is provided by the IBM Nginx service in CP4I (Service: `ibm-nginx-svc`, Route: `cpd`).
+With this setting, there is no MQ Web Console.
 
-On this queue manager, we have:
+On this queue manager, we add:
 ```
         - env:
             - name: MQ_ENABLE_EMBEDDED_WEB_SERVER
               value: 'true'
           ports:
             - containerPort: 9443
               protocol: TCP
-...
-  web:
-    enabled: false
 ```
-REST clients access an embedded Web Server in the container. This server listens on port 9443 (see above, where we create a service for this) and provides Console and REST support. Below we'll see how to access the MQ Console on this queue manager.
+REST clients access an embedded Web Server in the container. This server listens on port 9443 (see above, where we create a service for this) and provides MQ Web Console and REST support. Below we'll see how to access the MQ Web Console on this queue manager.
 
 * Configuration file (`mqwebuser.xml`)
 

diff --git a/README.md b/README.md
@@ -52,7 +52,7 @@ To run these examples, you need:
 
 * For the MQ REST API: `curl` (if not present, download it from https://curl.se/download.html).
 
-* The CP4I and MQ Operators installed on OpenShift.
+* The MQ Operator installed on OpenShift.
 
 These examples were tested on MacOS and Red Hat Linux (RHEL8), with CP4I running on [IBM Cloud](https://cloud.ibm.com).
 
@@ -69,7 +69,7 @@ I haven't tested this extensively on Windows, but most commands shown here shoul
 
 # Instructions
 
-Before running these examples, open a terminal and login to the OpenShift cluster where you installed Cloud Pak for integration and the MQ Operator.
+Before running these examples, open a terminal and login to the OpenShift cluster where you installed the MQ Operator.
 
 To implement the examples, follow the `README.md` found on each folder. Copy/paste the commands shown to a terminal session.
 
@@ -91,14 +91,12 @@ Instead of performing copy/paste of individual commands, you can run the scripts
 
 # Assumptions
 
-* You installed the **Cloud Pak for Integration** and **MQ** Operators in an OpenShift project / Kubernetes namespace called `cp4i`. If that is not the case, perform these global changes:
+* You installed the MQ Operator in an OpenShift project / Kubernetes namespace called `cp4i`. If that is not the case, perform these global changes:
 
   * Change all instances of `-n cp4i` to `-n <your namespace>`
 
   * Change all instances of `Namespace:		cp4i` to `Namespace:		<your namespace>`
 
-* You created an instance of **Platform Navigator**. This is necessary because these examples create queue managers with the Web Server enabled.
-
 * These examples were tested on [IBM Cloud](https://cloud.ibm.com). On other clouds:
 
   * Change all instances of `ibmc-block-gold` to a storage class that provides block storage.