IBM AD Web Services Prerequisites

• 64-bit AdoptOpenJDK 8/11/13 HotSpot
• 64-bit Java 8/11 Oracle
• 64-bit Java 8 IBM

• Microsoft SQL Server

  Microsoft SQL Server 2014/2016/2017/2019/2022 is installed and configured (accessible, if it is installed on a different machine). For more information, see Microsoft SQL Server Configurations at the end of this topic.

• Db2® for LUW (Linux®, UNIX, and Windows)
  If you use Db2 for LUW (Linux, UNIX, and Windows), IBM AD Dashboard will automatically create the Audit database for you if the prerequisites are met. For more information, see Prerequisite software for automatically creating the Db2 for LUW databases.

  Note: If the Audit database cannot be created automatically, you might want to check the instructions in Preparing repository using scripts for Db2 for LUW projects to troubleshoot and manually create the database.
• Db2 for z/OS®

  If you use Db2 for z/OS, you must manually create the Audit database before you run the IBM AD Configuration Wizard or define a relational database server against Db2 for z/OS. To create the Audit database, complete the following steps:

  1. Run the following SQL clauses to create the Audit database, tables, and indexes.

  --#SET TERMINATOR ;
  
  CREATE DATABASE EZAUDIT
  --STOGROUP CUSTOM_STOGROUP_NAME
  CCSID UNICODE ;
  
  SET CURRENT SCHEMA = 'EZAUDIT';
  CREATE TABLE APPLICATIONS (
       ID          INTEGER NOT NULL,
       DESCRIPTION VARCHAR(255),
       NAME        VARCHAR(255),
       CONSTRAINT APPLICATIONS_PK PRIMARY KEY(ID)
  ) IN DATABASE EZAUDIT;
  CREATE TABLE EVENTS (
       ID                INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 1, INCREMENT BY 1),
       APPLICATION_ID    INTEGER,
       DATE              TIMESTAMP,
       INSTANCE_ID       VARCHAR(255),
       IP                VARCHAR(255),
       OPERATION_NAME    VARCHAR(255),
       OPERATION_TYPE_ID INTEGER,
       PROJECT_NAME      VARCHAR(255),
       USER_NAME         VARCHAR(255),
       CONSTRAINT EVENTS_PK PRIMARY KEY(ID)
  ) IN DATABASE EZAUDIT;
  CREATE TABLE EVENTS_ARCHIVED (
       ID                INTEGER GENERATED BY DEFAULT AS IDENTITY (START WITH 1, INCREMENT BY 1),
       APPLICATION_ID    INTEGER,
       DATE              TIMESTAMP,
       INSTANCE_ID       VARCHAR(255),
       IP                VARCHAR(255),
       OPERATION_NAME    VARCHAR(255),
       OPERATION_TYPE_ID INTEGER,
       PROJECT_NAME      VARCHAR(255),
       USER_NAME         VARCHAR(255),
       CONSTRAINT EVENTS_ARCHIVED_PK PRIMARY KEY(ID)
  ) IN DATABASE EZAUDIT;
  CREATE TABLE EVENTS_INFO (
       EVENT_ID   INTEGER NOT NULL,
       INFO_VALUE VARCHAR(255),
       INFO_KEY   VARCHAR(255) NOT NULL,
       CONSTRAINT EVENTS_INFO_PK PRIMARY KEY(EVENT_ID, INFO_KEY)
  ) IN DATABASE EZAUDIT;
  CREATE TABLE EVENTS_INFO_ARCHIVED (
       EVENT_ARCHIVED_ID INTEGER NOT NULL,
       INFO_VALUE        VARCHAR(255),
       INFO_KEY          VARCHAR(255) NOT NULL,
       CONSTRAINT EVENTS_INFO_ARCHIVED_PK PRIMARY KEY(EVENT_ARCHIVED_ID, INFO_KEY)
  ) IN DATABASE EZAUDIT;
  CREATE TABLE NOTIFICATIONS (
       ID             BIGINT GENERATED BY DEFAULT AS IDENTITY (START WITH 1, INCREMENT BY 1),
       CREATED        TIMESTAMP NOT NULL,
       MESSAGE_KEY    VARCHAR(255),
       MESSAGE_VALUES VARCHAR(255),
       SOURCE         VARCHAR(36) NOT NULL,
       TITLE          VARCHAR(255) NOT NULL,
       TYPE           INTEGER,
       CONSTRAINT NOTIFICATIONS_PK PRIMARY KEY(ID)
  ) IN DATABASE EZAUDIT;
  CREATE TABLE USAGE_DETAIL (
       ID         BIGINT GENERATED BY DEFAULT AS IDENTITY (START WITH 1, INCREMENT BY 1),
       END_TIME   TIMESTAMP,
       LOG_TIME   TIMESTAMP,
       START_TIME TIMESTAMP,
       SUBTYPE    VARCHAR(255),
       TYPE       VARCHAR(255),
       VALUE      BIGINT,
       CONSTRAINT USAGE_DETAIL_PK PRIMARY KEY(ID)
  ) IN DATABASE EZAUDIT;
  CREATE TABLE USER_PROFILE (
       ID        BIGINT GENERATED BY DEFAULT AS IDENTITY (START WITH 1, INCREMENT BY 1),
       LAST_SEEN TIMESTAMP NOT NULL,
       USERNAME  VARCHAR(255) NOT NULL,
       CONSTRAINT USER_PROFILE_PK PRIMARY KEY(ID),
       CONSTRAINT USER_PROFILE_USERNAME_UNQ UNIQUE (USERNAME)
  ) IN DATABASE EZAUDIT;
  CREATE TABLE USERS (
       ID        BIGINT GENERATED BY DEFAULT AS IDENTITY (START WITH 1, INCREMENT BY 1),
       CREATED   TIMESTAMP NOT NULL,
       LICENSE_TYPE    INTEGER,
       USERNAME  VARCHAR(255) NOT NULL,
       CONSTRAINT USERS_PK PRIMARY KEY(ID),
       CONSTRAINT USERS_USERNAME_UNQ UNIQUE (USERNAME)
  ) IN DATABASE EZAUDIT;
  CREATE INDEX IN_SOURCE_CREATED ON NOTIFICATIONS (CREATED, SOURCE, ID);
  ALTER TABLE EVENTS_INFO ADD CONSTRAINT EVENTS_INFO_EVENTS_FK FOREIGN KEY (EVENT_ID)
  REFERENCES EVENTS
  ENFORCED;
  ALTER TABLE EVENTS_INFO_ARCHIVED ADD CONSTRAINT EVENTS_INFO_ARCHIVED_EVENTS_ARCHIVED_FK FOREIGN KEY (EVENT_ARCHIVED_ID)
  REFERENCES EVENTS_ARCHIVED
  ENFORCED;

  2. Copy the db2jcc_license_cisuz.jar file from your Db2 into the <IBM ADDI Installation Folder>/IBM AD Web Services/wlp/usr/shared/config/lib/global directory.

9080 and 9443 are the default ports that are used by the IBM Application Discovery WebSphere® Liberty Profile Service. Make sure that both ports are open, unused, and not blocked by your firewall. If the default ports are not available, you can check the troubleshooting tips at the end of this topic.

Starting with IBM AD V5.1.0.7, you don't need to perform the pre-configurations of IBM WAS Liberty Web Server and the pre-configurations of SQL database for IBM AD Audit. Audit database is created automatically for Microsoft SQL Server users.