Architecture
Mid Tier architecture for Progressive Web Application
is capable of rendering a progressive web application (PWA) for a custom application. The following image represents the architecture of that involves a cross-launch from .
As part of the new architecture, the backend is used to leverage its generic and metadata-driven implementation, and the client-side rendering logic is changed to produce a user interface and experience that is similar to that of .
The core business logic and functional logic including Role Based Access Control (RBAC) exists in the application workflows. The ITSM data model also exists in the with the business logic in filters. and continue to work until the Progressive Web Application (PWA) technology completely replaces their functionality.
How PWA screens are viewed from
The following video shows some of the PWA screens in
You can enable opening of these PWA screens from by using the cross-launch settings configured in the Centralized Configuration. The following diagram illustrates how PWA screens are viewed from :
When a screen is available in PWA, screens are displayed from as described in the following steps, which illustrate the example of when a user views an incident ticket.
- The Incident screen is available as PWA, so is cross-launched from Smart IT so that the incident ticket can be viewed as PWA.
- The Incident screen is available as PWA, so the user is redirected to . The user views the incident and gets the incident details such as tasks and notes.
- sends the final response to the user.
The following list shows the information flow when a user accesses a screen that is available only in :
A. The request to view a screen is sent to the server because the interface is not available as PWA.
B. An authentication REST API call is sent to the server.
C. A user is logged in to .
D. displays the information to the user.
Default typeahead and chunk size values in the Progressive Web App screens
BMC Helix ITSMincludes revamped screens for work orders, incidents, people profiles, asset, problem investigation, known error, broadcast, task, and change that are delivered by using the Progressive Web Application (PWA) technology. The PWA technology converts the Mid Tier view to a modern view that is customizable and extensible. You can access the PWA screens from the BMC Helix ITSM Universal Client (UC).
By default, the BMC Helix ITSM screens are displayed. If your organization has opted for this feature, you can enable the PWA screens. For more information, seeDeveloping a Progressive Web Application.
Architecture for classic interfaces
View architecture for classic Smart IT
The following diagram illustrates the classic Smart IT architecture:
Tier | Description |
|---|---|
Data tier | Stores definitions and data for Smart IT. |
Server tier | Processes the data received from the Smart IT clients, and passes the data to the database server to be stored. |
Web tier | Serves as a repository for web applications. Displays the appropriate web page to an authorized user. |
Client tier | Enables different clients to access and interact with the Smart IT data. |
View architecture for classic Mid Tier
A database forms the underlying element of the BMC Helix ITSM architecture. AR System is on top of the database and processes all data that is entered by the BMC Helix ITSM applications. In addition, AR System is the workflow engine between the BMC Helix ITSM applications and the database. It also verifies that a user has permission to perform each action, thereby enforcing any access control defined in the applications.
In this capacity, AR System is the interface between the database and BMC Helix CMDB, which includes the Product Catalog and BMC Helix CMDB. CMDB stores information about the configuration items (CIs) in your IT environment and the relationships between them. CMDB makes this information available to the BMC Helix ITSM applications and their various shared application components, such as the Task Management.
AR Systemalso manages the following modules:
- The Approval Server is a self-contained, shared module where you can automate any approval or signature process. For more information about Approval Server, see Automatic request assignment.
- You use the Assignment Engine to automatically assign requests to individuals. For more information about Assignment Engine, see Automatic request assignment.
The relationships among the database, AR System, CMDB, shared application components, and the BMC Helix ITSM applications are shown in the following illustration.
Learn more