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: README.md
+38-8Lines changed: 38 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,25 +199,55 @@ You can mount the following file structure at `/home/aceuser/initial-config`. Mi
199
199
- The truststore file that will be created for these files needs a password. You must set a truststore password using the environment variable `ACE_TRUSTSTORE_PASSWORD`
200
200
- You can place multiple files, each with a different file name/alias.
201
201
- `/home/aceuser/initial-config/webusers`
202
-
- A text file called either `admin-users.txt` or `operator-users.txt`. It contains a list of users to be created as admin/operator users using the command `mqsiwebuseradmin`. These users will have READ, WRITE and EXECUTE access on the Integration Server. The file has the following format:
202
+
- A text file called `admin-users.txt`. It contains a list of users to be created as `admin` users using the command `mqsiwebuseradmin`. These users will have READ, WRITE and EXECUTE access on the Integration Server. The file has the following format:
203
203
```
204
204
# Lines starting with a "#" are ignored
205
-
# Each line should specify the <adminUser> <password>, separated by a single space
205
+
# Each line should specify the <user> <password>, separated by a single space
206
206
# Each user will have "READ", "WRITE" and "EXECUTE" access on the integration server
- A text file called `viewer-users.txt`, `editor-users.txt`, `audit-users.txt` . It contains a list of users to be created as viewer/editor/auditor users using the command `mqsiwebuseradmin`. These users will have READ access on the Integration Server. The file has the following format:
212
+
- A text file called `operator-users.txt`. It contains a list of users to be created as `operator` users using the command `mqsiwebuseradmin`. These users will have READ and EXECUTE access on the Integration Server. The file has the following format:
213
213
```
214
214
# Lines starting with a "#" are ignored
215
-
# Each line should specify the <adminUser> <password>, separated by a single space
215
+
# Each line should specify the <user> <password>, separated by a single space
216
+
# Each user will have "READ" and "EXECUTE" access on the integration server
- A text file called `editor-users.txt`. It contains a list of users to be created as `editor` users using the command `mqsiwebuseradmin`. These users will have READ and WRITE access on the Integration Server. The file has the following format:
223
+
```
224
+
# Lines starting with a "#" are ignored
225
+
# Each line should specify the <user> <password>, separated by a single space
226
+
# Each user will have "READ" and "WRITE" access on the integration server
- A text file called `audit-users.txt`. It contains a list of users to be created as `audit` users using the command `mqsiwebuseradmin`. These users will have READ access on the Integration Server. The file has the following format:
233
+
```
234
+
# Lines starting with a "#" are ignored
235
+
# Each line should specify the <user> <password>, separated by a single space
216
236
# Each user will have "READ" access on the integration server
- A text file called `viewer-users.txt`. It contains a list of users to be created as `viewer` users using the command `mqsiwebuseradmin`. These users will have READ access on the Integration Server. The file has the following format:
243
+
```
244
+
# Lines starting with a "#" are ignored
245
+
# Each line should specify the <user> <password>, separated by a single space
246
+
# Each user will have "READ" access on the integration server
- A text file called `config.mqsc`. It contains a list of mqsc commands which will be processed on start by `runmqsc` command. Further details can be found in the [MQ Knowledge Center](https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.ibm.mq.adm.doc/q020670_.htm)
0 commit comments