Home United States dc3 United States software in english pdf How to Move IBM App Connect Enterprise to Containers: Part 2(b)

How to Move IBM App Connect Enterprise to Containers: Part 2(b)

249
0
SHARE

Following on from the previous scenarios in this series, we now explain how to deploy a simple flow onto Red Hat OpenShift using the IBM App Connect Dashboard.
Join the DZone community and get the full member experience. In Scenario 2a we introduced the App Connect ‘operator’. This works as a sort of digital assistant to help us look after App Connect containers. In that scenario, we used the operator to deploy a container via the Kubernetes command line. In this scenario, we’re going to do exactly the same deployment but instead through a user interface known as the App Connect Dashboard. The App Connect Dashboard is a user interface that provides a simplified way to deploy BAR files within App Connect containers and administer them once live. Some of the facilities it provides are: Note that we described both ‘operators’ and ‘configurations’ in Scenario 2a should you need to go back and refresh your understanding of them. Clearly, the dashboard provides some powerful convenience features, but it does require some additional installation steps, configuration, and slightly increases the footprint on your installation. This is why we have made it optional, since some will prefer to use just the command line option. The Dashboard code is actually part of the operator that we installed in Scenario 2a, so if you have not done that yet, install the App Connect Operator. To keep the footprint light, the operator does not automatically install an instance of the App Connect Dashboard, so you’ll need to do that next. Before you create the App Connect Dashboard instance, you must decide what type of storage to use for uploaded or imported BAR files. The following storage types can be used to allocate storage for the ACE Dashboard content server. For our simple scenario, an ephemeral storage type will work just fine and will be the quickest/simplest to install. However, note that if you want to change to a different storage type later, you will need to re-install the dashboard. You can create an App Connect Dashboard instance from the IBM Cloud Pak for Integration Platform Navigator, the Red Hat OpenShift web console or CLI, or the CLI for a Kubernetes environment. The steps to create an instance of the dashboard and information on each of the storage types are here. You can launch the dashboard user interface from the OpenShift console, or from the IBM Automation Hub (previously known as Platform Navigator) if you have installed IBM Cloud Pak for Integration. The dashboard home page (shown below) has different tiles that tell you how many integration applications are currently deployed, how many integration servers are running, as well as a tile to create a new integration server. Note that if you did Scenario 2a, then you should be able to see the integration server you deployed previously using the CLI. This is because we set createDashboardUsers: true in the integration server definition file. Finally, we are ready to begin our deployment of the simple flow. First, verify the status of your application by looking at the pod log: As you would have noticed, we deployed two replicas of the Integration Server for high availability purposes. The Integration Server tile on the ACE dashboard displays the number of replicas currently configured and running. You can verify it via the command line too by running the following command: Identify the public endpoint (routes) for the HTTP service. The HOST/PORT entry as highlighted above forms the external base URL for invoking the webservice. From the pod logs, we saw that the deployed HTTPEcho service is listening on service endpoint ‘/Echo’. So the complete URL to invoke the service would be: http://simple-echo-app-http-ace-demo.apps.cp4i-2021-demo.cp.fyre.ibm.com/Echo Now test the message flow by invoking the service URL using the browser as shown below. If you see the Echo response above, then you have managed to call your deployed flow. Performing and administering deployments using the dashboard, performs exactly the same actions on the underlying Kubernetes platform as you would have done if using the command line. You can swap between the command line and user interface as you please, using whichever is the most effective for the job at hand. Acknowledgment and thanks to Kim Clark for providing valuable inputs to this article. Published at DZone with permission of Amar Shah. See the original article here. Opinions expressed by DZone contributors are their own.