Remove QSEoK examples and references since no longer valid after 1.62…

….67. (#119)

* Remove QSEoK examples and references since no longer valid after 1.62.67
* Rename QSEfW to QSEoW

docs/example-qsefw-header.md → docs/example-qseow-header.md

@@ -1,14 +1,14 @@
-# Example: Running against QSEfW with header authentication
+# Example: Running against QSEoW with header authentication
 
-This step-by-step example shows how to set up and run a randomworker scenario against a Qlik Sense® Enterprise for Windows (QSEfW) deployment with header authentication enabled.
+This step-by-step example shows how to set up and run a randomworker scenario against a Qlik Sense® Enterprise for Windows (QSEoW) deployment with header authentication enabled.
 
-**Note:** Header authentication can be set up in different ways. The settings used in this example may not be valid for all QSEfW deployments.
+**Note:** Header authentication can be set up in different ways. The settings used in this example may not be valid for all QSEoW deployments.
 
 ## Requirements
 
 The following is required for this procedure:
 
-* A QSEfW deployment
+* A QSEoW deployment
 * A server with Gopherciser installed (referred to as the "load client")
 
 ## Creating suitable access rules with enough tokens
@@ -19,9 +19,9 @@ First, create access rules that allow allocation of licenses to the virtual user
 
 <summary>Example</summary>
 
-In this example, a login access rule is used to allocate licenses to the virtual users created by Gopherciser. The rule allows users from a specific user directory ("anydir") to access the QSEfW deployment.
+In this example, a login access rule is used to allocate licenses to the virtual users created by Gopherciser. The rule allows users from a specific user directory ("anydir") to access the QSEoW deployment.
 
-Do the following in the QSEfW deployment:
+Do the following in the QSEoW deployment:
 
 1. Open the Qlik® Management Console (QMC).
 2. Go to **License management** > **Login access rules** > **Create new**.
@@ -46,7 +46,7 @@ The next step is to create a virtual proxy to handle the authentication, session
 
 <summary>Example</summary>
 
-Do the following in the QSEfW deployment:
+Do the following in the QSEoW deployment:
 
 1. Open the QMC.
 2. Go to **Proxies**.
@@ -73,7 +73,7 @@ For information on how to create a virtual proxy, see the [Qlik help](https://he
 
 ## Importing and publishing the test apps
 
-Import the test apps to the QSEfW deployment. Make sure to publish the apps, so that they are available to all users.
+Import the test apps to the QSEoW deployment. Make sure to publish the apps, so that they are available to all users.
 
 For information on how to publish apps, see the [Qlik help](https://help.qlik.com/en-US/sense/Subsystems/ManagementConsole/Content/Sense_QMC/publish-apps.htm).
 
@@ -90,14 +90,14 @@ Do the following on the load client:
 1. Install a plug-in that allows modification of http headers in the web browser (for example, "ModHeader" for the Google Chrome browser).
 2. Enter the header name ("X-Qlik-User-header" in this example) in the **Header name** field in the browser plug-in.
 3. Enter the name of the user ("anyuser" in this example) in the **Header value** field in the browser plug-in.
-4. Go to the hub of the QSEfW deployment using the following URI (using "vp" as `<virtualproxyprefix>` in this example): `<hostname>/<virtualproxyprefix>/hub/`
+4. Go to the hub of the QSEoW deployment using the following URI (using "vp" as `<virtualproxyprefix>` in this example): `<hostname>/<virtualproxyprefix>/hub/`
 5. If you can access the hub and the username entered in the **Header value** field is displayed, the virtual proxy with header authentication works.
 
 </details>
 
 ## Modifying the sample test script
 
-The sample test script is available here: [General randomworker example with header authentication](./examples/random-qsefw-header.json)
+The sample test script is available here: [General randomworker example with header authentication](examples/random-qseow-header.json)
 
 <details>
 
@@ -106,8 +106,8 @@ The sample test script is available here: [General randomworker example with hea
 Do the following on the load client:
 
 1. Download the sample test script.
-2. Modify the following fields to match the QSEfW setup configured above:
-   * `connectionSettings.server`: The hostname of the QSEfW deployment.
+2. Modify the following fields to match the QSEoW setup configured above:
+   * `connectionSettings.server`: The hostname of the QSEoW deployment.
    * `connectionSettings.virtualproxy`: The prefix for the virtual proxy that handles the virtual users ("vp" in this example).
    * `connectionSettings.headers`: The name of the http header that identifies users ("X-Qlik-User-header" in this example).
    * `loginSettings.settings.directory`: The name of the user directory ("anydir" in this example). The directory name is used by the login access rule to allocate licenses.
@@ -130,7 +130,7 @@ Do the following on the load client:
 2. Execute the following command (the actual command differs depending on platform - the example below is based on Linux Bash):
 
 ```
-./gopherciser execute -c random-qsefw-header.json
+./gopherciser execute -c random-qseow-header.json
 ```
 
 </details>

docs/examples.md

@@ -1,11 +1,10 @@
 # Example scenarios
 
-The following list contains example scenarios for various targets such as Qlik Sense® Enterprise for Windows (QSEfW) and Qlik Sense Enterprise on Kubernetes (QSEoK) deployments. 
+The following list contains example scenarios for Qlik Sense® Enterprise on Windows (QSEoW) deployments. 
 
 ---
 
-- [Running against QSEfW with header authentication](./example-qsefw-header.md)
-- [Running against QSEfW with JWT authentication](./random-qsefw.md)
-- [Running against QSEoK with JWT authentication](./random-qseok.md)
+- [Running against QSEoW with header authentication](./example-qseow-header.md)
+- [Running against QSEoW with JWT authentication](./random-qseow.md)
 
 ---

docs/examples/random-qsefw-header.json → docs/examples/random-qseow-header.json

@@ -4,7 +4,7 @@
 		"logs": {
 			"traffic": true,
 			"debug": false,
-			"filename": "logs/random-qsefw-header.tsv"
+			"filename": "logs/random-qseow-header.tsv"
 		}
 	},
 	"scheduler": {