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
- Place the resulting `ace-11.0.0.5_with_IT12345.tar.gz` file in the `deps` folder and when building using the `build-arg` to specify the name of the file: `--build-arg ACE_INSTALL=ace-11.0.0.5_with_IT12345.tar.gz`
33
-
33
+
34
34
### Using App Connect Enterprise for Developers
35
35
36
36
Get [ACE for Developers edition](https://www.ibm.com/marketing/iwm/iwm/web/pick.do?source=swg-wmbfd). Then place it in the `deps` folder as mentioned above.
@@ -69,7 +69,7 @@ Then set the build argument `ACE_INSTALL` to the name of the ACE file placed in
69
69
70
70
Follow the instructions above for building an image with App Connect Enterprise Only.
71
71
72
-
Add the MQ Client libraries to your existing image by running `cd ubi && docker build -t ace-mqclient --build-arg BASE_IMAGE=<AceOnlyImageTag> --file Dockerfile.mqclient .`
72
+
Add the MQ Client libraries to your existing image by running `docker build -t ace-mqclient --build-arg BASE_IMAGE=<AceOnlyImageTag> --file ubi/Dockerfile.mqclient .`
73
73
74
74
`<AceOnlyImageTag>` is the tag of the image you want to add the client libs to i.e. ace-only. You can supply a customer URL for the MQ binaries by setting the argument MQ_URL
75
75
@@ -83,6 +83,7 @@ In order to use the image, it is necessary to accept the terms of the IBM App Co
83
83
84
84
This chart requires a SecurityContextConstraints to be bound to the target namespace prior to installation. To meet this requirement there may be cluster scoped as well as namespace scoped pre and post actions that need to occur.
85
85
86
+
86
87
#### Running an ACE Only Integration Server
87
88
88
89
The predefined SecurityContextConstraints name: [`ibm-anyuid-scc`](https://ibm.biz/cpkspec-scc) has been verified for this chart when creating an ACE & MQ integration server, if your target namespace is bound to this SecurityContextConstraints resource you can proceed to install the chart.
@@ -192,7 +193,7 @@ You can mount the following file structure at `/home/aceuser/initial-config`. Mi
192
193
- 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`
193
194
- You can place multiple files, each with a different file name/alias.
194
195
- `/home/aceuser/initial-config/webusers`
195
-
- 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:
196
+
- 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:
196
197
```
197
198
# Lines starting with a "#" are ignored
198
199
# Each line should specify the <adminUser> <password>, separated by a single space
@@ -202,7 +203,7 @@ You can mount the following file structure at `/home/aceuser/initial-config`. Mi
202
203
admin1 password1
203
204
admin2 password2
204
205
```
205
-
- 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:
206
+
- 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:
206
207
```
207
208
# Lines starting with a "#" are ignored
208
209
# Each line should specify the <adminUser> <password>, separated by a single space
@@ -221,6 +222,10 @@ You can mount the following file structure at `/home/aceuser/initial-config`. Mi
221
222
- A json file called 'agentp.json' containing configuration information for the agent connectivity, this will be copied into the appropriate iibswitch directory
222
223
- `/home/aceuser/initial-config/extensions`
223
224
- A zip file called `extensions.zip` will be extracted into the directory `/home/aceuser/ace-server/extensions`. This allows you to place extra files into a directory you can then reference in, for example, the server.conf.yaml
225
+
- `/home/aceuser/initial-config/ssl`
226
+
- A pem file called 'ca.crt' will be extracted into the directory `/home/aceuser/ace-server/ssl`
227
+
- A pem file called 'tls.key' will be extracted into the directory `/home/aceuser/ace-server/ssl`
228
+
- A pem file called 'tls.cert' will be extracted into the directory `/home/aceuser/ace-server/ssl`
0 commit comments