Integrate Jarvis Analytics

The following requirements should be met in order to use API Portal with your external Jarvis service:
Prerequisites
The following requirements should be met in order to use API Portal with your external Jarvis service:
  • API Portal and Jarvis cannot be run on the same server.
  • The following ports will be used by API Portal to talk to the Jarvis instance: 8443, 9443, 39443.
  • The Jarvis domain name should be resolvable by your API Portal instance.
    Editing the hosts file of the Portal machine is not a viable solution since the hosts file is not respected by Docker. The network should be set up such that the domain is resolvable.
Enable Integration
If you have been using Jarvis from version 4.2.x, the variable PORTAL_ENABLE_ANALYTICS in your existing portal.conf is no longer used. Replace this variable with the variables shown next.
To enable Portal integration with external Jarvis service:
  1. Navigate to 
    /conf/portal.conf
    .
  2. Add the following information:
    PORTAL_JARVIS_DOMAIN=address.broadcom.net PORTAL_JARVIS_CERT=certs/jarvis.crt PORTAL_JARVIS_DATA_RETENTION_DAYS=100
If you enable Jarvis integration after creating a tenant, the Analytics dashboard page may be shown as blank for that tenant until you hit your first APIs.