Scenario Overview

Union Station is a major multimodal railway transportation hub. It is one of the busiest stations in the country and serves thousands of passengers a day. The train shed, platforms, and tracks are owned by GOGO transit, and they operate the station. Trains are owned by the companies named Quantis, ColTrain, and RailCo. To provide a digital ecosystem, all four companies are planning to develop their day to day business operations with ESB technology. These development ranges from providing different kinds of APIs to external/internal users, providing real time notifications, stream data processing, integrating with partners/external systems etc.

Scenario Overview

These tutorials will demonstrate how ESB technology can be used to cater to their different requirements.

Prerequisites

Docker and Docker compose need to be installed. Please refer https://docs.docker.com/compose/install/ for more information. Allocate a minimum of 4 CPU cores and 4GB Memory for Docker resources.

Requirements

  • ESB Experience : Intermediate
  • Technologies used :
    • MWARE ESB 4.1.0 or higher
    • ESB Micro Integrator
    • ESB Streaming Integrator
    • Sample backends and clients written in Spring boot and hosted in Tomcat
    • MySQL

Deployment

Scenario Deployment

A basic infrastructure has already been created for you to try out the scenarios. To run the setup please follow these steps.

  1. Clone https://github.com/wso2/samples-apim.
  2. Go to samples-apim/apim-tutorial.
  3. Start the setup using the command docker-compose up -d.
  4. You can view the logs using the command docker-compose logs -d.
  5. It might take 5-10 minutes for the setup to complete (if it is the first time, based on your download speed it might take longer).
  6. When you see the below log you can start working on the scenarios. 
    “==Data population completed==”

ESB Setup

The ESB setup consists of 3 tenants for Quantis, ColTrain, and RailCo and Gogo Transit uses the super tenant domain. Tenants, Users, and APIs will be created automatically when Docker compose starts.

Scenario Tenants

You can log in to the Publisher Portal and Developer Portal using each tenant's credentials.

Publisher portal: https://localhost:9443/publisher/ Developer portal: https://localhost:9443/devportal

The following default users are created. For the ease of use, every tenant has 3 common users (admin, apiprovider, devuser) for Admin, Publisher, and Developer Portal.

Admin Publisher Developer Portal
Quantis admin@quantis.com
  • apiprovider@quantis.com
  • andy@quantis.com
  • devuser@qunatis.com
  • bob@quantis.com
  • sindy@quantis.com
  • logan@quantis.com
ColTrain admin@coltrain.com
  • apiprovider@coltrain.com
  • bill@coltrain.com
  • devuser@coltrain.com
  • george@coltrain.com
RailCo admin@railco.com
  • apiprovider@railco.com
  • jill@railco.com
  • devuser@railco.com
  • tom@railco.com

(admin user password: admin , other user password : user123)

Micro Integrator and Streaming Integrator Setup

The Micro Integrator and Streaming Integrator containers that were created when you started the setup will contain the services and client .jar files that will be used throughout this tutorial.

Others

  • Apache Tomcat - This will host the services that will be used as backends, clients that will be used throughout the tutorial.
  • MySQL - This MySQL database will be used by Micro Integrator. An initial database will be created when the container spins up.

Scenarios

Top