With v4.3 of the Portal, Jarvis should be configured as an externalized service. We might be integrating with multiple independent Gateway clusters from the Portal so that all the APIs can be consumed from one place. In terms of setting up Jarvis for such a requirement, can you please confirm if a single instance of Jarvis would be enough. The documentation states that :
"Jarvis must be run and installed on a different server to that of CA API Developer Portal. As each Jarvis service is set up to correspond to a Portal tenant, you will need to scale up as needed, i.e. set up multiple Jarvis instances, if you are running multiple Portal tenants in different environments and/or time zones."
Does the Portal tenant here refer to a Gateway cluster ? If yes, how would multiple Jarvis instances integrate with the Portal instance. Please clarify.
Each Portal instance needs is own Jarvis instance , if the portal has multiple tenants it still needs
one Jarvis for this portal .
The tenant gateways connect to the portal and the analytics container connects to the external Jarvis .
You can not use one Jarvis and connect multiple portals to it .