This past quarter, our team has been invested in many new, exciting capabilities as part of our releases. One of these items has to do with the deployment flexibility of the IBM API Connect analytics subsystem.
We realize that enterprises often have pre-existing configurations of many useful analytics tools that allow them to have an overview of their organizationsâ€™ API usage and health. So in this scenario, the question often comes up: â€śWhy do we need to install all of the UI related microservices for the analytics subsystem?â€ť
This is a valid question. You should not have to download the UI related microservices if you are utilizing a 3rd party tool for analytics ingestion and/or visualization. As part of Version 2018.4.1.8, you can now opt out of having to install these Analytics microservices. What does this mean for your enterprise? Even lower minimum configuration requirements for your team to deploy API Connect!
We wanted to make this as simple as possible. This can be accomplished in two easy steps prior to API Connect installation:
Step 1: Create an extra-values file and enter relevant information about your Analytics offload tooling. These pieces of info will include your host and an index to point at.
Step 2: When running your installation commands, enter the following commands:
apicup subsys set analyt ingestion-only=true
apicup subsys set analyt extra-values-file=INSERT_NAME_OF_EXTRA_VALUES_FILE.yaml
Once you install your analytics subsystem, these settings will be reflected.
You can view additional documentation here:
- Kubernetes installation: https://www.ibm.com/support/knowledgecenter/en/SSMNED_2018/com.ibm.apic.install.doc/tapic_enable_ingest_only.html
- VMWare installation: https://www.ibm.com/support/knowledgecenter/en/SSMNED_2018/com.ibm.apic.install.doc/tapic_enable_ingest_only_vm.html
This capability applies to API Connect Version 2018.4.1.8 and later.Â