Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content
  • Monitoring TIBCO BusinessWorks? Container Edition applications with TIBCO Hawk® Container Edition


    Manoj Chaurasia

    Table of Contents

    TIBCO Hawk® Container Edition 1.0.0. is a lightweight, low-footprint, containerized TIBCO Hawk Agent along with other separate TIBCO Hawk components such as Cluster Manager, and TIBCO Hawk Console. TIBCO Hawk Container Edition helps you carry the same Hawk monitoring and management experience from the enterprise world to the container world. There is no fundamental change in the TIBCO Hawk architecture in the container edition; concepts like TIBCO Hawk Domain, Agent, Microagent, RuleBase, Alerts, Schedules, auto-discovery, AMI, and console APIs are still the same.

    There is a significant improvement in the configuration of these components; no more .cfg files - now configuration via environment variables, via yml files is supported. And of course, the TIBCO Hawk components are deployed as (Docker) Containers. There are new microagents in the Container Edition for monitoring Docker infrastructure.

    Advantages of using TIBCO Hawk Container Edition:

    • Rules and Alerts - You can create rules based on your monitoring criteria and configure alerts to notify you in case of a criteria breach. You can take further action and invoke external triggers and actions based on the alert.

    • Invoke and subscribe - You can view monitoring data for your applications by invoking or subscribing to various microagent methods.

    • Monitor Docker infrastructure - You can monitor the underlying docker infrastructure using TIBCO Hawk Container Edition. This way you can gather stats about docker host/s and get insights into not only your containerized applications but the hosts as well.

    • Forward Docker Container logs to TIBCO LogLogic Log Management Intelligence (LMI) - With the built-in LMI microagent, you can now send container logs and TIBCO Hawk alerts to a LogLogic LMI appliance. This requires minimal configurations and log publishing can be started/stopped on demand!

    Note:

    • TIBCO Hawk Container Edition 1.0.0 supports only Docker.

    • TIBCO Hawk Container Edition 1.0.0 supports only TCP transport (no RV/ EMS transport support in the container world). This means it is mandatory to start the TIBCO Hawk Cluster Manager Container (daemon) to initialize the TCP transport-based TIBCO Hawk Domain.

    The TIBCO Hawk Microagent for TIBCO BusinessWorks? Container Edition software provides methods to perform the following tasks:

    • Retrieve the TIBCO BusinessWorks Container Edition application node and application details.

    • Retrieve details of processes in the deployed TIBCO BusinessWorks Container Edition applications.

    • Collect various statistics for processes and their activities.

    • Asynchronously subscribe to retrieve information on TIBCO BusinessWorks Container Edition process, activity, and transition events from the event bus.

    • Create rules and alerts based on the TIBCO BusinessWorks Container Edition application monitoring criteria

    In order to monitor the TIBCO BusinessWorks Container Edition applications running in Docker containers, we need to instrument the TIBCO BusinessWorks Container Edition Container with TIBCO Hawk Microagent for TIBCO BusinessWorks Container Edition.

    Deployment Architecture

    Only one TIBCO Hawk Agent needs to be set up on a Docker Host. To set up TIBCO Hawk Domain with TCP transport, we need to set up Hawk ClusterManager on any one of the Docker Hosts.

    TIBCO Hawk Agents on each of the Docker hosts will join the Cluster Manager to form the TIBCO Hawk Domain.

    One or more TIBCO BusinessWorks containers instrumented with TIBCO Hawk Microagent will connect with the TIBCO Hawk Agent on that Docker host.

    Note: Each individual TIBCO BusinessWorks container will need to be instrumented with the TIBCO Hawk microagent for TIBCO BusinessWorks Container Edition.

    Finally, install TIBCO Hawk Console on any one of the Docker Hosts to get UI Console to author Rulebases and deploy to TIBCO Hawk Agents.

    screen_shot_2018-05-29_at_10_24.31_am.png.2f3f49afc34eb2e3bdd9076a07dee6f1.png

    Diagram 1: Typical deployment scenario for monitoring TIBCO BusinessWorks ;Container Edition applications using TIBCO Hawk Container Edition

    The diagram above shows a typical TIBCO Hawk Domain consisting of TIBCO Hawk Agent, Cluster Manager, Hawk Console, and TIBCO BusinessWorks containers instrumented with TIBCO Hawk Microagent. Note that there can be multiple TIBCO BusinessWorks containers on the same Docker Host, but they all connect to a single TIBCO Hawk Agent container on that host.

    Downloading the Components

    Please ensure that you have the necessary licenses before you download these components.

    1. TIBCO Hawk Agent and TIBCO Hawk Cluster Manager for Container Edition: Download "TIBCO Hawk - Container Edition Software (v 1.0.0)" - available as a component under TIBCO Hawk 6.0.0 on eDelivery.
    2. TIBCO Hawk Microagent for TIBCO BusinessWorks Container Edition: Download ?TIBCO Hawk Microagent for TIBCO BusinessWorks Container Edition (v 1.0.0)? - available as a component under TIBCO Hawk 6.0.0 on eDelivery.
    3. TIBCO Hawk Console: Download ?TIBCO Hawk® Console for Docker - Community Edition" from https://tap.tibco.com/storefront/trialware/tibco-hawk-console-for-docker...

    Creating Docker images for TIBCO Hawk Components

    Refer to https://docs.tibco.com/pub/hkce/1.0.0/doc/html/GUID-C51B12F3-4C9F-4FC0-9... to create the Docker images for TIBCO Hawk Agent, TIBCO Hawk Cluster Manager, and TIBCO Hawk Console.

    Instrumenting TIBCO BusinessWorks Container Edition Docker Container with TIBCO Hawk Microagent

    Download the zip file for TIBCO Hawk Microagent for TIBCO BusinessWorks Container Edition (v 1.0.0) from eDelivery. Extract the zip file to get the jar files:

    • com.tibco.hawk.microagent.bwce_<version>.jar
    • com.tibco.hawk.tcp.ami_<version>.jar

    Create a Dockerfile to copy the required JAR files of TIBCO Hawk Microagent for TIBCO BusinessWorks Container Edition to the TIBCO BusinessWorks Container Edition add-ons directory, optionally also copy the TIBCO BusinessWorks Container Edition application ear file.

    Create a Docker image for instrumented TIBCO BusinessWorks container from this Dockerfile.

    Refer to: https://docs.tibco.com/emp/hkbwce/1.0.0/doc/html/GUID-416E25B7-1AA8-4DAC... for more details.

    Quick Test:

    Run all Components in Standalone Mode

    Once we have all the required Docker containers, viz.

    • TIBCO Hawk Agent
    • TIBCO Hawk Cluster Manager
    • TIBCO BusinessWorks Container Edition instrumented with TIBCO Hawk Microagent with application
    • TIBCO Hawk Console

    we can quickly test using Docker Compose, running all the containers in standalone mode on a single Docker Host. Here is a sample docker-compose.yml file which has all 4 components:

     

     

     version: '3' services:   hawkclustermanager:     image: hkce_clustermanager:1.0.0    ports:      - '2561:2561'    environment:      tcp_daemon_url: hawkclustermanager:2561      tcp_self_url: hawkclustermanager:2561      hawk_domain: tcpdomain   hawkagent:     image: hkce_agent:1.0.0    depends_on:      - "hawkclustermanager"    ports:      - '2551:2551'      - '2571:2571'    volumes:      - /var/run/docker.sock:/var/run/docker.sock    environment:      tcp_daemon_url: hawkclustermanager:2561      tcp_self_url: hawkagent:2551      hawk_domain: tcpdomain      ami_tcp_session: hawkagent:2571      DOCKER_HOST: unix:///var/run/docker.sock      auto_config_dir: /tibco.home/hkce/1.0/autoconfig/      hma_plugin_dir: /tibco.home/hkce/1.0/plugin/      LMI_HOST: <LMI_URL>   bwcewithhawk:     image: bwce_233_hk:latest    depends_on:      - "hawkagent"    ports:      - '2555:2555'    environment:        tcp_self_url: bwcewithhawk:2555        ami_agent_url: hawkagent:2571   hawkconsole:     image: hkce_console:1.0.0    depends_on:      - "bwcewithhawkadapter"    environment:      tcp_daemon_url: hawkclustermanager:2561      tcp_self_url: hawkconsole:2551      hawk_domain: tcpdomain    ports:      - '2589:2589'      - '8083:8083' 

     

    Docker compose will run all the components, create the network, and create the domain to which the TIBCO Hawk Agent and Console join.

    Go to http://<host>/8083/HawkConsole (username/ password: admin/admin) to login to the TIBCO Hawk Console. Drill Down to the Domain and Agent and navigate to ?BWCEHawkMicroagent-containerID? micro agent to see all the methods to monitor the TIBCO BusinessWorks Container Edition application.

    Here is the list of all methods exposed by TIBCO Hawk Microagent for TIBCO BusinessWorks Container Edition for monitoring the TIBCO BusinessWorks Container Edition application, process, and activities: You can invoke/ subscribe or create RuleBases to monitor the TIBCO BusinessWorks Container Edition process and activities.

    Running TIBCO Hawk Container Edition with TIBCO BusinessWorks Container Edition on Kubernetes cluster, TIBCO Hawk Container Edition 1.0.0. supports PaaS deployments using the most popular Kubernetes platform. Refer to: https://docs.tibco.com/pub/hkce/1.0.0/doc/html/GUID-EF1F3786-C7B1-4C2F-B...


    User Feedback

    Recommended Comments

    There are no comments to display.


×
×
  • Create New...