This version of the documentation supports the 3.2 version of BMC Digital Workplace Basic. Click here to view the documentation for the current version.

Architecture for BMC MyIT OnDemand

The application employs a standard three-tier architecture: client, application server, and database. (Clients include smartphones, tablets, laptops, and desktops.) The BMC MyIT and BMC Remedy with Smart IT OnDemand infrastructure is installed on a shared server as shown in the following figure.

BMC MyIT and BMC Remedy with Smart IT are two different entities that are tightly integrated. BMC MyIT shares the same installer, social engine, databases, and server with BMC Smart IT.They have separate mobile apps and universal clients that connect to the same server. 

BMC MyIT and BMC Remedy with Smart IT deployment with BMC Remedy OnDemand

BMC MyIT integrates with different service request providers, service availability providers, and so on. The BMC MyIT server is an integration point for the BMC MyIT application. The application can expose aspects of other IT applications through the UI, or it can use other applications to aid or enhance core BMC MyIT functionality.

Out of the box, BMC MyIT supports only one product in each category, for example, BMC Service Request Management for submitting service desk requests and BMC Knowledge Management for knowledge search. To integrate other products, you must use adapters. MyIT has a provider abstraction layer for each type to enable this, as described in the following section.

Server architecture

The following diagram shows the server architecture.

serverarch

Note

The configuration data store and operational data store are logically separated for software-as-a-service multi-tenancy. For an on-premise, single-tenant installation, these data stores can be co-located in the same database. The data stores are SQL-based, and BMC MyIT supports multiple vendors.

The data access layer uses EclipseLink. In the diagram, green represents generic framework code, and blue represents business logic that is specific to certain features. The adapters have a green border to represent the common interface they implement for the business function of that type of provider.

The architecture of the social component can stand alone to present a social API to all BMC products in a “social cloud.” Some tips to remember are:

  • Integrations that the social component makes to outside systems are based on a REST architecture.
  • Other products interact with the social cloud by calling the social cloud API. The social cloud code does not have adapters to integrate with other BMC systems and conform to their APIs. In that sense, the social cloud is a service, not a client. For integrations to other social platforms or systems external to BMC that are needed for core social functionality, the social cloud code adapts to and uses those interfaces (which should be compatible with REST).
  • Storage uses a Mongo database.
  • The data access layer uses Mongoose object relational mapping (ORM).

BMC MyIT mobile applications

A native mobile app for BMC MyIT, which you can distribute to your users as described in Deploying BMC MyIT to your users. If you are investigating BMC MyIT, you can download a mobile client that connects to our trial environment from the following locations:

For more information about device compatibility, see System requirements.

For more information about deploying a custom-branded app to your users, see Deploying BMC MyIT to your users.

 

Was this page helpful? Yes No Submitting... Thank you

Comments