Install > Install the Mobile Applications client > Install Service Manager Mobile Applications

Install Service Manager Mobile Applications

This section provides details about how to install Service ManagerMobile Applications to support your business processes.

Before you start

As the System Administrator, you must:

  • Have already installed Service Manager on a web accessible location.

  • Your web application server meets the requirements that are described in the Service Manager compatibility matrix. For details, refer to the Service Manager Support Matrix at Support Matrices.
  • Configure the JVM memory settings on the web application server as below:

    • Minimal setting: -Xms:1024m, -Xmx:1024m, -XX:PermSize=256m

    • Recommended setting: -Xms:1500m, -Xmx:1500m

  • Set JAVA_HOME to the location where the JDK was installed (for Tomcat only), or enable the profiles to use the version 7.0 SDK (for WAS 8.5.5 only).

    For example, use the following command on a 32-bit operation system:

    managesdk -enableProfileAll -sdkname 1.7_32 -enableServers

  • Review the browser requirements for smartphones.
  • Set up your Mobile Applications preferences.
  • Configure Service Manager.

Edit the configuration file in the war archive

To edit web.properties in webapp-x.xx.xxxx.war, follow these steps:

  1. Open webapp-x.xx.xxxx.war in an archive management program.
  2. Extract the web.properties file from the WEB-INF directory to your local system, and then open this file in a text editor.
  3. Set the Service Manager server and port parameters as follow to add your server connection information:

    Required parameters for Service Manager Mobile Applications client connection
    Parameter Default value Description
    endpoint http://localhost:13080/SM/ui

    Change localhost:13080 to your Service Manager server host name and port number.

    resourceRoot None

    This parameter is commented-out by default. You need to update this value only when the *.js image files and the *.css files are stored on another server.

    For example, if you moved the static files to another Apache server, change this value to resourceRoot=http://<host name of another Apache server>:8080/mobile/statics/.

    Tip

    • Optionally, you can also define the number of records that appear in every page of the List View by configuring the value in the recordlistcount parameter.
    • If FIPS (Federal Information Processing Standards) mode is enabled on the Service Manager side, you need to enable FIPS mode in the Mobility client. For details, see the following topics of the Service Manager Help Center:

      • Configure LW-SSO in the Mobility Client for FIPS mode
      • Configure FIPS mode in the Mobility Client

  4. Save the file and add the updated file back to the WEB-INF directory of the webapp-x.xx.xxxx.war archive.

Install Service Manager Mobile Applications

The Service ManagerMobile Applications contains a J2EE-compliant web application that runs on your web application server. Each web application server has its own method of deploying web applications. See your web application server documentation for specific instructions on deploying a web application.

Note For the specific versions of the application servers that are currently supported by the Service ManagerMobile Applications client, refer to the Service Manager Support Matrix at Support Matrices.

The following table provides a summary of deployment methods required.

Web application server Deployment method
Apache Tomcat Copy the webapp-x.xx.xxxx.war file to the <Tomcat>\webapps folder and start the web application server.
IBM Web Application Server Open the administration console and install the web application from the webapp-x.xx.xxxx.war file.

Note If you are planning to upgrade both platform and applications to version from Service Manager 9.34 or later 9.3x versions, the Mobile Applications will be upgraded to the latest version which supports both power user view and self-service user view.