Before you begin
Make sure that IBM® ADDI Local
Analysis is configured and up and
running.
About this task
By using IBM ADDI Configuration Server, you can provide
configuration details of your ADDI Local Analysis container to allow
IBM
ADDI to connect to it.
Procedure
- Access , and go to
. The
ADDI Local Analysis settings page is
displayed.
- Enter the following information:
- Host
- Enter the hostname or the IP of the computer where the ADDI Local Analysis container is deployed.
- Server Port
- Enter the ADDI Local Analysis
API server port. By default, the ADDI Local Analysis
API server port is set to
4680
.
- Docker API Port (optional)
- Only fill in the Docker API Port
information if the ADDI Local Analysis container is running in a
remote environment to IBM ADDI. Enter the TCP port that was defined to enable remote connection to
Docker Engine API Server.
- Docker Container ID
- Enter your ADDI Local Analysis container ID.
- Authorization token
- Enter the authorization token value that you configured when starting ADDI Local Analysis server by using the wa-startup.sh script. The token value may contain any combination of 5
to 15 alphanumeric characters and special symbols except equal sign "=", hyphen
"-", or blank " ".
Note: The authorization token is reset each time you start ADDI Local Analysis servers and you need to make sure that this
configuration page is kept up to date with the latest authorization token value configured in ADDI Local Analysis.
If you change the
Host,
Server Port, or
Docker API Port (optional) fields on the
ADDI Local Analysis configuration page in
ADDI Dashboard, you need to restart the
IBM
ADDI WebSphere Liberty Profile
Windows service from the
Windows Services Panel to make those changes take
effect.
Note: Wait until the ADDI Local Analysis
Rest API Service is successfully restarted by verifying the
CWWKZ0001I: Application wazianalyze started in xxx seconds.
log message in the ...\wlp\usr\servers\ad_server\logs\messages.log file.
- Click Save.