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
@@ -159,15 +158,8 @@ To install AIDA, run the following procedure:
159
158
``./AIDA.sh build-start``
160
159
161
160
Accept the product license when prompted.
162
-
163
-
8. AIDA is now up and running. Configure the first server to be monitored by running the command
164
-
165
-
``./AIDA.sh add-credentials``
166
-
167
-
This command starts a guided configuration of the server.
168
-
For details, see [Managing Workload Automation server credentials](#managing-workload-automation-server-credentials).
169
161
170
-
9. If Keycloak is included in your AIDA deployment, you can connect AIDA user interface at the following link
162
+
8. If Keycloak is included in your AIDA deployment, you can connect AIDA user interface at the following link
171
163
172
164
``https://aida-ip:aida-port/``
173
165
@@ -177,40 +169,6 @@ To install AIDA, run the following procedure:
177
169
**Note**: The **common.env** environment file contains all the environment variables. For details, see [Configuration parameters](#configuration-parameters).
178
170
After AIDA installation, if you want to modify the configuration parameters, edit the common.env file and then run the command: ./AIDA.sh restart.
179
171
180
-
## Managing Workload Automation server credentials
181
-
You can manage the credentials needed to connect to a Workload Automation server using AIDA.sh script.
182
-
With a single AIDA instance you can monitor hybrid environments with a mix of HCL Workload Automation for distributed and z/OS systems.
183
-
184
-
**Limitations:**
185
-
With AIDA.sh script you can add, update, and delete credentials. You cannot list credentials since this function is not currently available.
186
-
187
-
To **add new credentials**, run the following steps:
188
-
1. From [docker_deployment_dir], run the following command
189
-
190
-
``./AIDA.sh add-credentials``.
191
-
192
-
A guided configuration procedure will start.
193
-
2. Follow the guided procedure and answer the prompts to add your credentials, specify the engine type (if HCL Workload Automation for distributed systems or HCL Workload Automation for Z) and, for HCL Workload Automation for Z only, also the engine name.
194
-
195
-
**Note:** If you are connecting HCL Workload Automation for distributed systems, you must use the Engine credentials.
196
-
If you are connecting HCL Workload Automation for Z, you must use the Dynamic Workload Console credentials instead.
197
-
198
-
To **update existing credentials**, run the following steps:
199
-
1. From [docker_deployment_dir], run the following command
200
-
201
-
``./AIDA.sh update-credentials``.
202
-
203
-
A guided configuration procedure will start.
204
-
2. Follow the guided procedure and answer the prompts to add your credentials, specify the engine type (if HCL Workload Automation for distributed systems or HCL Workload Automation for Z) and, for HCL Workload Automation for Z only, also the engine name.
205
-
206
-
207
-
To **delete existing credentials**, run the following steps:
208
-
1. From [docker_deployment_dir], run the following command
209
-
210
-
``./AIDA.sh delete-credentials``.
211
-
212
-
A guided configuration procedure will start.
213
-
2. Follow the guided procedure and answer the prompts to delete your credentials.
214
172
215
173
216
174
## Updating AIDA installation
@@ -275,12 +233,6 @@ For the command usage, run
275
233
276
234
``down-volumes`` Removes AIDA's containers and volumes
277
235
278
-
``add-credentials`` Lets you add credentials to connect to a HCL Workload Automation engine
279
-
280
-
``update-credentials`` Lets you update previously added credentials
281
-
282
-
``delete-credentials`` Lets you delete previously added credentials
283
-
284
236
``set-custom-port`` Sets a custom port to access AIDA (default value is 9432)
285
237
286
238
@@ -330,12 +282,13 @@ The following tables list the configurable parameters of each service in the com
|SMTP_SERVER|The smtp server. Example: smtp-mail.outlook.com | Y (if you want to receive anomaly notification by email) | | |
334
-
|SMTP_PORT|The port of the smtp server | Y (if you want to receive anomaly notification by email)| | |
335
-
|SENDER_MAILID| The email account of the alert sender | Y (if you want to receive anomaly notification by email) | | |
336
-
|SENDER_MAILPWD|The email password of the alert sender | Y (if you want to receive anomaly notification by email)| | |
337
-
|RECIPIENT_MAILIDS|The list of recipient emails. Example: `jack@gmail.com,jessie@live.com` | Y (if you want to receive anomaly notification by email) | | |
285
+
|SMTP_SERVER|The smtp server. Example: smtp-mail.outlook.com | Y (if you want to receive anomaly notification by email) | | smtp.server.com |
286
+
|SMTP_PORT|The port of the smtp server | Y (if you want to receive anomaly notification by email)| | 587 |
287
+
|SENDER_MAILID| The email account of the alert sender | Y (if you want to receive anomaly notification by email) | | smtp@server.com |
288
+
|SENDER_MAILPWD|The email password of the alert sender | Y (if you want to receive anomaly notification by email)| | smtpPassword |
289
+
|RECIPIENT_MAILIDS|The list of recipient emails. Example: `jack@gmail.com,jessie@live.com` | Y (if you want to receive anomaly notification by email) | | test1@email.com,test2@email.com |
338
290
|HOST_IP|AIDA Host IP address and Port. Example: 10.14.32.141:9432| Y (if you want to receive anomaly notification by email) | | |
291
+
|EXTERNAL_HOSTNAME=|AIDA Hostname to resolve vulnerabilities| | | |
339
292
340
293
341
294
@@ -387,6 +340,7 @@ The following tables list the configurable parameters of each service in the com
0 commit comments