IBM Integration Bus on Cloud delivers a fully managed IBM Integration Bus environment that helps your business to start projects quickly and easily. With IBM Integration Bus on Cloud (IIBoC) you can deploy integration solutions to the cloud without the need to acquire and maintain an IT infrastructure. The IIBoC service has just released an improved way of seeing how your integrations are behaving in near real-time. This new feature, described below, lets you view the IIBoC system log entries in a Logmet Kibana dashboard, hosted in IBM Bluemix.
IBM Integration Bus on Cloud lets you upload and run Broker Archive files (BAR files). These contain IIB artifacts that you have developed such as applications, message flows and message models. The service uses Docker containers to host the IIB runtime message flows, and since IIBoC was first released it has been possible to download individual log files for running integrations. However, using this new Logmet capability you can now view your IBM Integration Bus on Cloud integration logs alongside your Integration Bus software logs which could be running on-prem, in the cloud, in docker containers etc. In fact you can also view logs in a single dashboard alongside other IBM products such as WebSphere Application Server, WAS Liberty or MQ for example.
When you log in to IIBoC from your web browser, you can now create a new Policy. A Policy holds configuration information which can be used to influence the behaviour of IIBoC integrations. Policies of different types hold different kinds of configuration information. For example a Kafka Policy defines the credentials needed to access a Kafka broker from your integrations. This blog entry discusses a Logmet Policy which contains credentials for pushing logs to the Logmet service in Bluemix. The following video demonstrates how to configure this new feature, then further down below we also provide detailed instructions to get you quickly up and running with this new feature:
Configuration in 3 Easy Steps
1. Retrieve your Bluemix logging configuration details:
IIBoC requires a Bluemix Logging token in order to be authorised to send data in to the Bluemix Logmet service. You also need a Bluemix space identifier which tells IIBoC how to locate your Logmet service instance. You can retrieve both of these pieces of information using a simple cURL request to the Logmet login URL. Issue the following cURL request:
curl -k -XPOST -d “user=<BLUEMIX_USER>&passwd=<BLUEMIX_PASSWORD>&space=<BLUEMIX_SPACE>&organization=<BLUEMIX_ORGANIZATION>” <BLUEMIX_LOGIN_URL>
curl -k -XPOST -d “firstname.lastname@example.orgemail@example.com” https://logmet.ng.bluemix.net/login
The response message will have this structure:
“access_token”: ” …”,
“account_id”: ” … “,
“logging_token”: ” …”,
You will need the values for logging_token and space_id. For more information, on the above commands please consult the IIB Knowledge Center.
2. Create an IIBoC Policy:
In the IIBoC user interface in your web browser, create a Policy of type “Logmet” and specify:
- A policy name
- Logmet host to send the logs to
- Bluemix space identifier which you retrieved in step 1.
- Bluemix logging token which you retrieved in step 1.
3. Attach the policy to your IIBoC integration:
Note that an IIBoC integration must be stopped in order for you to attach a policy to it, start the integration and follow the Kibana dashboard link to go view your logs in Logmet!
Logs are uploaded to Logmet on a 60 second interval so there may be a short delay before they are visible in your Kibana dashboard. For further information on submitting logs from IBM Integration Bus please refer to Martin Boag’s post Exploiting Bluemix and Logmet Kibana Dashboards with IBM Integration Bus version 10.0.0.7. A simple IBM Integration Bus Dashboard template is supplied with an IIB installation in the samples directory. You can read more about this topic by following this link.