...

1. Log in to the Web Console (default username: admin, default password: adminuser).

2. Define the main type of monitored transactions and preferred theme (this will determine the default type and theme for all users):

   1. Choose DataPower Gateway services if the main type of monitored transactions is DataPower services (e.g.: WSP, MPGW).

   2. Choose API Connect APIs if the main type of monitored transactions are API-Connect APIs.

3. Read the End User License Agreement, and if acceptable, accept it.

4. Once logged in, check system status.

5. Change the default password.

Adding and Configuring Monitored Devices

1. Make sure to Prepare your Monitored Devices.

2. Follow Adding Monitored Gateways.

3. Configure the monitored devices to send data to DPOD by following Configuring Monitored Gateways.

4. If you are using DPOD to monitor API-Connect APIs, and the API-Connect Analytics subsystem is installed, you may configure it to offload data to DPOD to see payload and headers, and to enjoy Expert Mode dashboards.

Security and Roles

1. Log in to the Admin Console (default username: admin, default password: adminuser) and change the default password.

2. Complete the LDAP configuration steps.
   The built-in local repository of users, groups and roles is only for POCs and demo usage. To better comply with more strict security requirements it is advised to leave the Local User Registry Management disabled in System Parameters (it is disabled by default). When disabled, DPOD will not allow to add or edit any users, roles or groups, and will display a relevant error message.

3. Create Custom Roles for users or groups to restrict the permissions each user has in the system.
   For example, allow the development team of a certain group of APIs to see transactions of their own APIs, while preventing access to other teams' APIs.

4. Secure the installation by replacing self signed certificate of the web console and limiting admin dashboard to specific IP addresses.

...