Hi Pablo,
don't think there is a documentation out on how to best setup this containerized/integration server yet.
We create one "base integration container " which we clone for each specific 'integration - ORG' we need.
Especially with the usage of API Keys (which are ORG specific) it gets some more complexity but this can be handled in the config files.. so the API key secrets specific for the Org get used, ....
------------------------------
--------------------------------
Kris Caron
---------------------------------
------------------------------
Original Message:
Sent: Wed May 06, 2020 03:08 AM
From: PABLO ROBERTO GARCIA
Subject: Integration server configuration for different organizations
About the deployment of the integration server based on containers.
Is there any specific document explaining the process?... They only place I saw it was at:
ibmresilient/resilient-circuits-docker| GitHub | remove preview |
 | | ibmresilient/resilient-circuits-docker | | This repository is a community submission detailing how you can use Docker to containerize an integration for Resilient Circuits. Integrations used with resilient_circuits are Python packages which are typically installed before use and Circuits itself is also a Python package. | | View this on GitHub > |
|
|
About multiple org with MSSP you requires to deploy as many as circuits you need based on the number of the org. If you have 10 child-orgs you have to run 10 process with 10 app.config files, this can be run on single user for testing, separate users, separate boxes, containers..., a few options are available and I believe it depends on the customer requirement. About the automation every child-org and the integration server will take their jobs to run the automation... Any doubt or clarification on that?
------------------------------
PABLO ROBERTO GARCIA
Original Message:
Sent: Tue May 05, 2020 05:14 AM
From: Kris Caron
Subject: Integration server configuration for different organizations
Hi Jasmine,
We resolved this issue by moving our Integration server to Kubernetes - Docker containerized solution.
This allows us to run multiple Integration servers next to each other.
It's not just a copy paste of the infrastructure to Kubernetes:
- We put each micro integration in a separate Container, so it's easy to do proper packaging, monitoring, redeploy new code.
- Each container = a mini integration server which Circuits running
- We spin-off a copy of the containers if we need to serve a second (or more) Organization. This is the case on our Development and Acceptance Appliances.
For us this is certainly the way to go, much more flexible than running the Integration server as one VM which one controller=Circuits.
------------------------------
Kris Caron
Original Message:
Sent: Fri May 01, 2020 06:20 AM
From: Jasmine
Subject: Integration server configuration for different organizations
Hi,
1- What is the Integration server configuration if there are two or more organizations with different actions / functions.
2-What is the Integration server configuration if there are two or more organizations with different actions / functions if we had mssp licence?
Any document or advice would be appreciated.
Best
------------------------------
Jasmine
------------------------------