---
title: Next steps - Integrate PingIntelligence into your environment
description: After the installation is complete, refer the following topics based on the type of deployment.
component: pingintelligence
version: 5.1
page_id: pingintelligence:pingintelligence_production_deployment:pingintelligence_integrating_into_environment
canonical_url: https://docs.pingidentity.com/pingintelligence/5.1/pingintelligence_production_deployment/pingintelligence_integrating_into_environment.html
revdate: April 25, 2024
---

# Next steps - Integrate PingIntelligence into your environment

After the installation is complete, refer the following topics based on the type of deployment.

**Sideband configuration:**

After you have completed the deployment, integrate one of the following API gateways with PingIntelligence components and start sending the API traffic to your API gateway:

* [Akana API gateway sideband integration](../pingintelligence_integrations/pingintelligence_akana_integration.html)

* [Apigee integration](../pingintelligence_integrations/pingintelligence_apigee_integration.html)

* [AWS API gateway integration](../pingintelligence_integrations/pingintelligence_aws_integration.html)

* [Azure APIM sideband integration](../pingintelligence_integrations/pingintelligence_azure_apim.html)

* [Axway sideband integration](../pingintelligence_integrations/pingintelligence_axway_integration.html)

* [CA API gateway sideband integration](../pingintelligence_integrations/pingintelligence_ca_integration.html)

* [F5 BIG-IP integration](../pingintelligence_integrations/pingintelligence_f5_big_ip_integration.html)

* [IBM DataPower Gateway sideband integration](../pingintelligence_integrations/pingintelligence_ibm_datapower_integration.html)

* [Kong API gateway integration](../pingintelligence_integrations/pingintelligence_kong_integration.html)

* [MuleSoft sideband integration](../pingintelligence_integrations/pingintelligence_mulesoft_integration.html)

* [NGINX sideband integration](../pingintelligence_integrations/pingintelligence_nginx_integration.html)

* [NGINX Plus sideband integration](../pingintelligence_integrations/pingintelligence_nginx_plus_integration.html)

* [PingAccess sideband integration](../pingintelligence_integrations/pingintelligence_pa_integration.html)

* [PingFederate sideband integration](../pingintelligence_integrations/pingintelligence_pf_integration.html)

* [WSO2 integration](../pingintelligence_integrations/pingintelligence_wso2_integration.html)

**Inline configuration:** If you configured PingIntelligence ASE as [Inline ASE](../api_security_enforcer/pingintelligence_inline_ase.html), the next step is to add [API definitions to the PingIntelligence for APIs](../api_security_enforcer/pingintelligence_defining_api_json_configuration_inline.html) software. After this is complete, direct your API client to the IP address of the ASE software on port 80 or 443.

It is recommended to read the following topics (part of the admin guides) apart from reading the [ASE](../api_security_enforcer/pingintelligence_ase.html) and [ABS](../abs_ai_engine/pingintelligence_abs_ai_engine.html) Admin Guides:

* [ASE port information](../api_security_enforcer/pingintelligence_customizing_ase_ports.html)

* [API naming guidelines](../api_security_enforcer/pingintelligence_api_naming_guidelines.html)

* [Connect ASE and ABS](../api_security_enforcer/pingintelligence_abs_ai_based_security.html)

After you have added your APIs in ASE, the API model needs to be trained. The training of API model is completed in ABS. The following topics give a high level view, however it is a good practice to read the entire ABS Admin Guide.

* [Train your API model](../abs_ai_engine/pingintelligence_ai_engine_training.html)

* [Generate and view the REST API reports using Postman](../abs_ai_engine/pingintelligence_api_reports_using_postman.html): To access the ABS REST API reports you would require the following information:

  * IP address: IP address of ABS configured in the [`config/hosts`](pingintelligence_automated_deployment_downloading_package.html) file.

  * Port number: default value is 8080. It is configured in `abs-defaults.yml` file

  * API Name: Name of the API for which you want to generate REST API reports

  * Later and Earlier date: The date range for which you want to generate the reports

* View [Access PingIntelligence Dashboard](../pingintelligence_poc/pingintelligence_access_dashboard_docker_poc.html):

  Login to PingIntelligence Dashboard using the `ping_user` login ID and the password that you configured during PingIntelligence installation. For more information on password configuration, see [Change Dashboard default settings](pingintelligence_changing_dashboard_default_settings.html). The PingIntelligence for APIs Dashboard takes approximately one hour to start showing attack information.