Connector Designer deployment architecture

Connector Designer is a web application that allows users to create connectors.

Connector Designer and i2 Analyze are designed to run on separate servers. You must deploy Connector Designer on a separate server from the i2 Analyze deployment. A load balancer, running in a container, is used to route traffic to the i2 Analyze deployment and to Connector Designer.

When a connector is created and deployed using Connector Designer, the connector is run in a container and communicates with i2 Analyze by using the load balancer.

When you install Connector Designer, the required certificates and certificate stores are created. When a user deploys a connector from Connector Designer, it is deployed with the required certificates and certificate stores.

When a user deploys a connector from Connector Designer, the connector is deployed with the required certificates and certificate stores to communicate with i2 Analyze via the load balancer.

Note: Connector Designer is not supported on the same server as i2 Analyze. If you install Connector Designer on the same server as i2 Analyze, it can cause issues with your i2 Analyze deployment.

The following diagram shows the deployment architecture when Connector Designer is deployed alongside an existing i2 Analyze deployment.

Network

The following diagram shows the network architecture of Connector Designer:


Connector Designer network architecture

When you deploy Connector Designer, you must provide the URLs of the Liberty servers in your i2 Analyze deployment. The load balancer uses these URLs to route traffic to the i2 Analyze deployment. If you already have a load balancer in your deployment, configure load balancer that is deployed as part of Connector Designer to point to your existing load balancer.

Security

The following diagram shows the security architecture of Connector Designer:


Connector Designer security architecture

Connector Designer uses TLS to communicate and JWT tokens to authenticate users.