Customizing the BMC Remedy ITSM 7.6.05 - Mobility server configuration

This topic provides information about customizing the BMC Remedy ITSM - Mobility server configuration.

You can configure the following settings in the BMC Remedy ITSM 7.6.05 - Mobility server:

• Data source query
• Connection properties
• Log levels and log file location
• BMC Remedy ITSM - Mobility server port
• Size of query results for incidents and worklog data

Data source query

The data source query is defined in the mobility_server_configure.xml file.

The following data sources are configured for the Incident Management mobile application:

• Incident
• Worklog
• Person
• SupportGroup

The data sources contain the data for the Incident Management mobile application. Each data source has at least one query configured. For example, the following query is used to retrieve Incident date:

Each query has a name, and the name is referenced by the Incident Management mobile application when downloading data from the data source. In addition, the Incident Management mobile application provides values to query variables. Variables are marked by a colon (:). For example:

The qualification is similar to the BMC Remedy Action Request System qualification, which uses single quotes for fields and the dollar sign for BMC Remedy AR System keywords. The only difference is that the data source query contains variables in the qualification.

You can modify queries by adding or removing query segments. Also, you can reuse existing query variables in a new segment, but you cannot introduce new query variables.

Connection properties

Connection properties specify the AR System server name, port, and Application Service password.

Passwords are in encrypted format, and you can change a password by using the following URL:

http://<mobilityServer-host>:<tomcat_port>/MobilityServer/admin

Log levels and log location

The BMC Remedy ITSM - Mobility server logging configuration is in the log4j-config.xml file.

You can change the following log levels to control the amount of information that is logged:

• Error
• Warn
• Info
• Debug

The log level is identified in the following tag:

If you set the log level to debug, for example, in the log4j-config.xml file, all levels above and including debug in the hierarchy, which includes info, warn, and error, are logged and can be output to a .txt file. If you set log level to info in the log4j-config.xml file, all levels above and including info in the hierarchy, which includes warn and error, are logged and can be output to a .txt file.

You can change the log file name or path by using the following XML tag:

BMC Remedy ITSM - Mobility server port

The BMC Remedy ITSM - Mobility server uses Http protocol and listens on port 80. You can change the default port by configuring the NIO AMF Http endpoint in the services-config.xml file.

1. Go to the C:/Program Files/BMC Software/Mobility/MobilityServer/WEB-INF/flex directory.
2. Open the services-config.xml file in a text editor.
3. Find the channel-definition id= mobility-nio-amf line in the XML file.

4. Change the endpoint port to 80:

   <endpoint url="http://{server.name}:80/nioamf
   

5. Restart the BMC Remedy ITSM - Mobility server.

   Note

   The Apache Tomcat web server must be restarted for the new BMC Remedy ITSM - Mobility server port to take effective. It takes about 50 seconds to start Tomcat, so be sure to wait enough time before reconnecting.

Size of query results for incidents and worklog data

You can configure the size attribute in the mobility_server_configure.xml file to adjust the maximum amount of incident or worklog data that is downloaded to a device. The minimum size of a query is 200 records.