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.

BMC Remedy ITSM - Mobility Service Desk deployment considerations

This page provides general information deployment considerations for  the BMC Remedy ITSM - Mobility server.

BMC Remedy ITSM - Mobility web server

BMC Remedy ITSM - Mobility server uses Apache Tomcat 6 or 7, installed with the BMC Remedy ITSM - Mobility server or leveraging an existing BMC Remedy Tomcat server

VMware

BMC Remedy ITSM - Mobility server can run on a VMware image

BMC Remedy ITSM - Mobility server database

BMC Remedy ITSM - Mobility server does not have database of its own. All settings and parameters are saved on the Admin server database.

Port access

The BMC Remedy ITSM - Mobility server must have one port open for the BMC Remedy ITSM - Mobility: Service Desk Incident Management application to gain access.

The Administrator sets the default port at installation time and can the modify the port later. The port is HTTP(s).

BMC Remedy ITSM - Mobility server performance and scalability

Multiple BMC Remedy ITSM - Mobility servers cannot be load-balanced from a mobile application perspective. There must be session-based persistence between the BMC Remedy ITSM - Mobility Incident Management application and the BMC Remedy ITSM - Mobility server that cannot be achieved through a simple load-balanced configuration.

Five hundred concurrent users can access one BMC Remedy ITSM - Mobility server.

For this release, the BMC Remedy ITSM - Mobility server can connect to only one BMC Remedy server. Multi-tenancy is not supported in this release.

 

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