Java™ analysis prerequisites
Starting with IBM® Application Discovery and Delivery Intelligence for IBM Z® (IBM ADDI) 6.0.2, the advanced Java analysis capabilities that integrate IBM ADDI and IBM ADDI Local Analysis are introduced. If you obtain IBM ADDI as part of the IBM ADDI bundle, you get access to both IBM ADDI and IBM ADDI Local Analysis.
Prerequisites:
-
Make sure that the IBM ADDI Local Analysis container is deployed. For more information, see Deploying the ADDI Local Analysis container.Note: Ensure that you deploy a IBM ADDI Local Analysis version that is compatible with corresponding IBM ADDI version. Otherwise, the integration between IBM ADDI and IBM ADDI Local Analysis will not work. Refer to the following table that shows the compatibility between IBM ADDI and IBM ADDI Local Analysis.If you need to upgrade your IBM ADDI Local Analysis to a later version, back up your project data first as described in Backing up project data and then check the instructions in Migrating to a newer version .
Table 1. Compatibility between IBM ADDI and IBM ADDI Local Analysis IBM ADDI Version IBM ADDI Local Analysis Version IBM Wazi Analyze Version 6.1.4 2025.1.0 Not applicable 6.1.3 Not applicable 2023.2.0 or later 6.1.2 Not applicable 2023.2 6.1.1 Not applicable 2.0.0.4 and 2.2.0 6.1.0 Not applicable 2.0.0.2 6.0.2 Not applicable 1.4.0 When you deploy the IBM ADDI Local Analysis container, the source folder where Java projects will be stored needs to be mapped to the /home/wazi/data folder within the IBM ADDI Local Analysis container and the port 4680 and 5000 need to be exposed. For example, to deploy the IBM ADDI Local Analysis container by using Docker or Podman, you can run the following commands:
Docker:
Podman:docker run -v <IBM_AD_Java_Projects_Path>:/home/wazi/data -it -p 5000:5000 -p 4680:4680 --name ADDI_LOCAL addilocal:2025.1.0
podman run -v <IBM_AD_Java_Projects_Path>/home/wazi/data -it -p 5000:5000 -p 4680:4680 --name ADDI_LOCAL addilocal:2025.1.0
Note: Starting with IBM ADDI Local Analysis 2.0.0.3, the home directory was changed from /home/wazianalyze/data to /home/wazi/data.Important:- For Java Analysis, the destination of the mounting point should always be
/home/wazi/data
. If you already have an existing IBM ADDI Local Analysis container created for a different purpose and has a different mounting point destination, it cannot be used with IBM ADDI. In this case, you need to create a new container with the correct mapping described above. - On Linux, when a local folder is mapped to the data folder within the IBM ADDI Local
Analysis container, the owner of the data folder inside the
IBM ADDI Local
Analysis container is updated to the root user or the
user who owns the local folder. To revert it back to the IBM ADDI Local
Analysis user within the IBM ADDI Local
Analysis container, complete the following steps:
- Open the IBM ADDI Local Analysis docker container CLI window.
- Change the ownership of data folder back to the IBM ADDI Local
Analysis user by running the following
command:
sudo chown wazi:wazi data
- Enter
sudo user password
. By default, the password is same as the usernamewazi
. - The ownership of data folder should now be updated.
When you copy source files into the project folder, you also need to change the ownership of the source files because by default those source files would be owned by the user adding them. After you copy the source files, you need to complete the following steps to change the owner of the source files to the IBM ADDI Local Analysis user:- Open the IBM ADDI Local Analysis docker container CLI window.
- Go to the /home/wazi/data/<project-id>/source/ directory.
- Change the ownership of source files back to the IBM ADDI Local
Analysis user by running the following
command:
sudo chown -R wazi:wazi *
- Enter
sudo user password
. By default, the password is same as the usernamewazi
. - The ownership of source files within /home/wazi/data/<project-id>/source/ folder should now be updated.
- For Java Analysis, the destination of the mounting point should always be
- Make sure that IBM ADDI Local Analysis Server is up and running. For more information on how to start or stop IBM ADDI Local Analysis Server, see Starting up and shutting down the server.
Configuration options for consideration
You can choose to either configure IBM ADDI Local
Analysis locally
or remotely to IBM
ADDI:
- To configure IBM ADDI Local
Analysis locally to IBM
ADDI when IBM ADDI Local
Analysis Docker Container is running on the same machine where IBM
ADDI Servers and Services are running, complete the following step:
- Make sure that Docker API Port on the IBM ADDI Local Analysis configuration page in IBM ADDI Dashboard is left empty. For more information, see Configuring ADDI Local Analysis.
- To configure IBM ADDI Local
Analysis remotely to IBM
ADDI when IBM ADDI Local
Analysis Docker Container is running on a different machine from where IBM
ADDI Servers and Services are running, complete the following step:
- Configuring Docker Engine for remote access with TLS. The configured TCP port should be added to Docker API Port field in IBM ADDI Local Analysis configuration page in AD Dashboard. For more information, see Configuring ADDI Local Analysis.