Skip to content
This repository has been archived by the owner on Jul 3, 2024. It is now read-only.

Latest commit

 

History

History
71 lines (42 loc) · 5.89 KB

README.md

File metadata and controls

71 lines (42 loc) · 5.89 KB
master Build Status Coverage Status
dev Build Status Coverage Status

Acme Freight ERP Quick Links

The Acme Freight Journey

Acme Freight Shipping is a fictional shipping and logistics company using the Logistics Wizard application framework to reimagine supply chain optimization systems for the 21st century.

Acme Freight uses an application, called Logistic Wizard to manage some of its assets. The application is composed of several microservices, including three Cloud Foundry applications and multiple OpenWhisk actions.

Acme Freight uses LoopBack, an open source Node.js framework, built for quickly creating and exposing APIs for new and existing applications and data. LoopBack enables Acme Freight to create an application that integrates with their existing ERP system, and API Connect allows them to expose data via a managed API.

For more on the Acme Freight journey and the technologies behind it, visit the Acme Freight journey website.

Acme Freight Tutorials

To start learning more about Acme Freight and the technology behind it, jump to one of the tutorials below.

Deploy Acme Freight

Rapidly Create APIs with the Node API Framework, LoopBack

Create APIs for OpenWhisk actions in just a few clicks

Acme Freight Architecture

The following projects are leveraged in the overall Acme Freight solution:

  • acme-freight-erp - defines the API used by Acme Freight to access data from an ERP system. It also provides a default implementation to be used as a simulator. The simulator is a Node.js application connected to a PostgreSQL database. Through its API, it manages users (supply chain managers and retail store managers), distribution centers, retail stores and shipments.

  • acme-freight-webui - provides a dashboard to view ongoing shipments and alerts. There is no log-in or user credentials per se to use the deployed applications. Instead a unique demo ID is assigned to any new user trying the application. Behind each demo ID, Acme Freight creates an isolated environment with a default set of business users, distribution centers, retail stores, shipments. Refer to the walkthrough to get a tour of the capabilities.

  • acme-freight-recommendation - makes shipment recommendations based on weather conditions. It is a set of Bluemix OpenWhisk to retrieve current weather conditions and given a weather event to generate new shipment recommendations. These recommendations could then be turned into real orders.

  • acme-freight-controller - acts as the main controller for interaction between the services. It receives requests from the user interface and routes them to the ERP or the weather recommendation module.

Acme Freight is forked and extended from the IBM Bluemix project, Logistics Wizard. Visit the Logistics Wizard project wiki for a detailed breakdown of the original Logicistics Wizard architecture and deployment strategy.

Overview

With the Acme Freight app, we focus on the planning and delivery of products from distribution centers to retail locations. Acme Freight's ERP service defines a subset of a full ERP system data model.

Acme Freight uses LoopBack to expose existing ERP data via an API and API Connect to secure and manage the API.

API Definition

The API and data models are defined in this Swagger 2.0 file. You can view this file in the Swagger Editor.

The API allows to:

  • log in and get access tokens;
  • get the list of Products, Distribution Centers, Retailers;
  • create, retrieve, update, delete Shipments.

The API defines the following roles:

  • supply chain manager - can view all data and manage Shipments
  • retail store manager - can view all data except Inventory and Suppliers