content_image/983242.jpg
5. Copy the certificate, including the lines -----BEGIN CERTIFICATE-----  and ----END CERTIFICATE-----  and paste it to both files: truststore-Cert-mykey.crt  and keystore-mykey.crt 

6. Run generateSecret.sh. 

./generateSecrets.sh my-kafka-secret icp4i 

## Deploy the BAR file 

Perform the following to deploy the BAR files: 

1. On the IBM App Connect dashboard, navigate to the Servers tab and click Add server . 

2. Select BAR file and click Continue . 

3. Copy the Content URL to the clipboard and click Configure release . 

4. Helm chart opens. Click Configure . 

5. Along with all usual configurations, ensure that you enter the secret name as defined previously in the step for generating secrets for accessing Event Streams. In our case, secret name is my-kafka-secret as shown in Figure 7-103. 

<img src='content_image/983242.jpg'>

6. On successful deploy of helm release, verify the connectivity with Kafka broker by processing the message through IBM App Connect integration flow. 

## 7.9 Splitting an integration across on-premises and cloud 

This section discusses available features in IBM App Connect that enables hybrid Integration between Cloud and on-premises deployments. 

## 7.9.1 Overview 

When you are building your hybrid or multicloud infrastructure, you must make an important architectural decision about splitting your integrations between these environments. IBM App Connect makes this possible with callable flows. A message flow can call another flow directly, both deployed on different platforms or environments, or indeed between on-premises and cloud. 

A message flow can complete many different actions, if those actions are computation-intensive, you can split them from the main flow and complete them somewhere else. Callable flows also facilitate reuse because they can be called by multiple message flows. You can split your flows between different applications in the same integration server, or between different integrations servers, which can also be in different integration nodes. Callable flows must be in applications. You cannot deploy in libraries or integration projects. 

In a hybrid integration scenario, some parts of a message flow might logically belong in a specific location. For example, if your flow queries an on-premises database, performance is better if that part of the flow remains on-premises. But if part of your flow queries a website multiple times, performance might be improved by running that part of the flow in the cloud. 

