Diese Seite ist nur auf Englisch verfügbar.

System Architecture and Interfaces

Dependencies

Building Block View of Ticket Management
Component Ticket-Service

Technology

Purpose

  • Manage life cycle of deviations in form of tickets, including

    • Time-based escalation for tickets (due time exceeded)

    • Track history of ticket actions

  • Shadowing master data (devices, facilities) in database and consuming changes from MMPD

  • Manage solution groups

Interfaces

  • HTTP/HTTPS (REST)

  • MACMA for authentication and fetching Access Control List information

  • MDM for master data: devices and facilities

  • Portal for registration of views, widgets, context contributions

  • Deviation Processor for registration of TM as a reactor module to enable automatic ticket creation based on deviation

  • Notification Service for enabling email notification in case of ticket status changes

  • Relational DB for storage of data

  • RabbitMQ

    • incoming device master changes from MDM

    • outgoing ticket state changes

  • Websockets providing ticket-live-view

Network Connections Overview

Source Destination Protocol

Ticket Management Web UI

Ticket Management

https

Ticket Management

MACMA

https

Ticket Management

Master Data Management

https

Ticket Management

IAS Portal

https

Ticket Management

Deviation Processor

https

Ticket Management

Notification Service

https

Ticket Management

RabbitMQ

AMQP 0.9.1 with TLS

Ticket Management

RDBMS

TCP/IP with SSL

Deployment and Bootstrapping Process in Nexeed Industrial Application System

Deployment and Bootstrapping Process

First MACMA must be setup, that the modules can use the authentication of MACMA. After that all modules (TM, MDM, Deviation Processor, Notification Service, and Portal need to register at MACMA to get client credentials, which are needed to configure the module. After that the modules can be started. Then roles and resources of the modules can be registered at MACMA, that they are available afterwards. After successful startup, TM can register at Portal and checks the presence of TM and other module roles in MACMA, that they can be used by TM. If all roles are available, TM can call the endpoints of the modules to pull data from MDM, register as reactor module in Deviation Processor and call the Notification Service APIs to send direct messages, such as email notifications.

Deployment View for Cloud Deployment

DeploymentViewCloud

TM Namespace View for Cloud Deployment

TMNamespaceDeploymentView
Edit this pageDiese Seite bearbeiten

Feedback on this pageFeedback zu dieser Seite