Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Deployment architecture

This section provides information about the deployment architecture for BMC Remedy ITSM - Mobility: Service Desk. 

Deployment types

The following diagram illustrates a BMC Remedy ITSM - Mobility: Service Desk for deployment of On Premise with DMZ deployment:

Deployment Diagram - On Premise with DMZ.jpg

This describes deployment on dedicated VMs for Mobility. This deployment is recommended, because it provides better performance and reduces dependency and downtime in case either Mid Tier or Mobility have to be rebooted.

The following diagram illustrates a BMC Remedy ITSM - Mobility: Service Desk for a Mobility server with Mid Tier deployment:

Deployment Diagram - Mobility Server with Midtier.jpg

This describes deployment on the same VM as Mid Tier .This provides cost savings by consolidation on single VM. However, this may negatively impact performance when the number of end user connections is greater than 250.

Communication

Two types of communication activities occur:

  • Data—The BMC Mobility server and AR System server communicate by using the BMC Remedy AR System Java API. You can specify a TCP port for this communication when you install the BMC Mobility server, and you can modify the port later, if needed.
  • Notifications—Escalations on the AR System server trigger the web services on the BMC Mobility server. Web service messages are then delivered to the BMC Mobility server through the BMC Mobility for Remedy ITSM plug-ins. Web services are on the same port on which Apache Tomcat is listening. For more information, see Port-requirements.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Remedy ITSM - Mobility: Service Desk 7.6.07