Mms711 InstallMaximo Mobile 7.1

Tivoli IBM Maximo Mobile Suite
Version 7.1.1
Installation and Configuration Guide
Note
Before using this information and the product it supports, read the information in Notices on page 29.
This edition applies to version 7, release 1, modification 1 of IBM Maximo Mobile Suite and to all subsequent
releases and modifications until otherwise indicated in new editions.
Copyright International Business Machines Corporation 2007, 2009.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Chapter 1. Overview of the installation
and configuration processes . . . . . . 1
Mobile device requirements .
. 1
Chapter 2. Preparing to install . . . . . 3

Chapter 3. Installing Maximo Mobile
Suite on the application server . . . . . 5
Chapter 4. Granting access rights to
security groups in the Maximo Mobile
Suite applications . . . . . . . . . . 7
Chapter 5. Authenticating users with
application server security. . . . . . . 9
Chapter 6. Preparing to install Maximo
Mobile Suite on a mobile device . . . . 11
Configuring the properties of a mobile device .
Configuring files to access the application server
Maximo Mobile Suite properties . . . . .
Importing mobile application data . . . . .
Translating Maximo Mobile Suite . . . . .
Packaging application bundles . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
11
11
11
13
13
13
Chapter 7. Installation of mobile device

middleware . . . . . . . . . . . . . 15
Installing middleware onto a mobile device . .
Installing middleware onto a personal computer .
. 15
. 16
Chapter 8. Configuring the IBM Maximo

Mobile Suite . . . . . . . . . . . . 17
Ensuring records are unique .
Copyright IBM Corp. 2007, 2009
. 17
Sending status changes separately from records .

Creating asset statuses . . . . . . . . . .
Changing polling frequency . . . . . . . .
Removing transactions from inactive users . . .
Creating a profile for bar code scanning . . . .
Enabling bar code scanning on an Intermec mobile
device . . . . . . . . . . . . . . .
Adding a library to Intermec mobile devices .
Enabling bar code scanning on a Motorola Symbol
mobile device. . . . . . . . . . . . .
Adding a library to Motorola Symbol mobile
devices . . . . . . . . . . . . . .
.
.
.
.
.
17
17
18
18
18
. 19
. 19
. 20
. 20
Chapter 9. Managing data for mobile

devices . . . . . . . . . . . . . . 23
Limiting data sent to mobile devices . . . . .
Automatically downloading records onto a mobile
device . . . . . . . . . . . . . . .
Counting records for a mobile device . . . . .
Analyzing data for a mobile device . . . . .
Removing supporting data from a mobile device .
. 23
.
.
.
.
23
23
24
24
Chapter 10. Customizing . . . . . . . 25

Configuring Maximo Mobile Suite applications for
mobile devices . . . . . . . . . . . .
Application configuration planning . . . .
XML attributes in Maximo Mobile Suite
applications . . . . . . . . . . . .
Changing the screen layout . . . . . . . .
Creating additional copies of a Mobile application
. 25
. 25
. 26
. 27
28
Notices . . . . . . . . . . . . . . 29
Trademarks .
. 30
Index . . . . . . . . . . . . . . . 33
iii
iv
IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide
Chapter 1. Overview of the installation and configuration

processes
You must complete installation and configuration tasks to set up the IBM
Maximo Mobile Suite. The process includes the tasks that you need to complete to
use an application. The configuration information about bar code scanning is
provided only for Motorola Symbol and Intermec mobile devices.
The following steps describe the complete process for installing and configuring
Maximo Mobile Suite.
1. Overview of the installation and configuration processes
2. Preparing to install
3. Installing Maximo Mobile Suite on the application server
4. Application security
5. Preparing to install on a mobile device
6. Installing the middleware
7. Configuring Maximo Mobile Suite
8. Managing data for mobile devices
9. Customizing
Mobile device requirements

Each mobile device must meet the following requirements to be able to run the
application.
v
v
v
v
128 MB of RAM minimum

Microsoft Windows Mobile 5.0 or 6.1
Microsoft ActiveSync 4.0 or later
IBM Maximo Asset Management 7.1.1.6 or later
v An environment that supports HTTP protocol, such as LAN TCP/IP, WiFi,

cellular, or satellite communications.
Chapter 2. Preparing to install

For the installation process to be successful, you must ensure that various system,
device, and precautionary requirements are met. You must create a backup of the
database, update the database and stop the application server.
Procedure
1. Ensure that you are running the required version of IBM Maximo Asset
Management.
a. In a command prompt, navigate to the maximo_root\applications\maximo
directory.
b. Enter version.bat to view the product, configuration, and fix pack levels.
2. Create a backup of your maximo_root folder and database.
3. Install any updates to the Maximo database.
a. On the application server, go to the Database Configuration application.
b. If required updates are listed, select the Apply Configuration Changes
from the Select Action menu.
4. Stop the application server.
Chapter 3. Installing Maximo Mobile Suite on the application

server
You must install Maximo Mobile Suite on the application server after IBM Maximo
Asset Management is installed. The Maximo Mobile Suite requires the separate
installation of additional components.
Procedure
1. Open the installation launchpad by double-clicking the launchpad.exe file,
which is on the product DVD.
2. From the launchpad, select Install the Product.
3. Select the name of the application that you are installing.
4. Complete the installation wizard, and then click Done.
5. In the Middleware Login Information window, click the WebSphere Admin tab
and enter the password for the WebSphere Application Server manager.
6. Click the WebSphere Remote tab and enter the password for the Remote
Administrator user.
7. Complete the wizard, and then click Done.
Chapter 4. Granting access rights to security groups in the

Maximo Mobile Suite applications
To install the Maximo Mobile Suite, you must grant access rights to the Mobile
Installer application, and to the user who is performing the installation. Other
access rights can be granted later during the configuration process because all
users must have access rights to an application.
Procedure
1. In the Security Groups (Mobile) application on the application server, enter the
name of the security group that is responsible for installation.
2. On the Applications tab, click the Mobile tab, then select the access rights for
the application to which you are granting the security group access rights. The
Mobile Installer application must be granted read access rights for the
installation process to be successful.
3. Save the updated profile. Log out for the changes to take effect.
Chapter 5. Authenticating users with application server

security
You can prevent unauthorized users from accessing confidential information by
authenticating users on a lightweight directory access protocol (LDAP) server for
database security.
Procedure
1. In the maximo_root\applications\maximo\mobileweb\webmodule\WEB-INF
directory, open the web.xml file.
2. Set the useAppServerSecurity attribute to true.
3. Delete the opening <!- - and closing - - > tags to uncomment the lines after the
<login-config> and <security-constraint> tags.
4. Rebuild the .ear file and deploy it to the application server.
5. Synchronize the users and groups from LDAP into the system by setting the
VMMSYNC (for a WebSphere application server) or LDAPSYNC (for a
WebLogic application server) cron task to active.
10
Chapter 6. Preparing to install Maximo Mobile Suite on a

mobile device
Before you install Maximo Mobile Suite on a mobile device, you must prepare the
files that are responsible for running the applications on mobile devices. To prepare
the files for installation, you must configure the properties files to enable
communication to and from the application server, and run command files to
bundle the data into a profile.
Configuring the properties of a mobile device

The mobile.properties file is embedded into each application bundle. You must
enter information about the mobile device, the application server, and which
features are used for each type of device in this file so that the mobile device can
communicate with the application server after it is installed.
Procedure
1. In the maximo_root\mobiletools\profiles\common\appsetup folder, right-click
the mobile.properties file and open it with a text editor.
2. Enter the property values for Maximo Mobile Suite.
3. Save your configuration.
Configuring files to access the application server

You must configure the properties files that are used to access the application
server. Configuring the mobiletools.properties file enables the files and packages
to communicate with the server. The .cmd files are the tools that are used in the
packaging and importing process.
Procedure
1. On the application server, navigate to the maximo_root\mobiletools folder.
2. Right-click the mobiletools.properties file and open it with a text editor.
3. Configure the properties for the host name, port, SLL, user name and
password.
4. Save the file.
Maximo Mobile Suite properties

The properties for Maximo Mobile Suite must be configured with specific values to
enable communication to and from the application server.
Property
Value to be entered
maximo.mobile.hostname
The IP address or host name of the

application server.
maximo.mobile.port
The port number of the application server.
maximo.mobile.ssl
Set this property to true if you are using a

Secure Socket Layer (SSL) environment.
Otherwise, leave the value as false.
11
Property
Value to be entered
maximo.mobile.username
The user name of the person who is

performing the installation. This security
group for the user must already be
configured in the Security Groups (Mobile)
application.
maximo.mobile.password
The password of the user who is performing

the installation.
maximo.mobile.contextname
Do not change the default context location

value of \maximomobile\mobileservices
maximo.mobile.barcode
To enable the device for bar code scanning,

delete the // prefix before the name of the
mobile device manufacturer.
v SYMBOL
v INTERMEC
v CUSTOM, for other devices, which require
further configuration.
maximo.mobile.rfid
To enable the device for Radio Frequency

Identification (RFID), delete the // prefix
before the name of the mobile device
manufacturer.
v SYMBOL
v INTERMEC
v CUSTOM, for other devices, which are not
ready for immediate use and require
further configuration.
12
maximo.mobile.datafetchsize
The maximum number of records to display

on the device. The default value is 1000.
maximo.mobile.snapshot
To enable the mobile device to be shared by

multiple users, set the Save and Restore
property to true.
This setting moves all data from a device
onto the application server when a user logs
off the device. It uploads the data back onto
the device when the user logs back in.
This setting allows for maximum memory
usage by the device without losing any
details from a users session. The user can
use any device to log in because information
is stored on the application server and not
on individual devices.
maximo.mobile.snapshot.chunksizekb
The size, in KB, that data from a users

session is divided into for faster
transmission between the application server
and the mobile device.
The size limit is imposed when the Save and
Restore property is set to true and a users
session data has exceeded this limit. The
default limit is 1000 KB.
For example, if a users session contains
2000 KB of data to be uploaded to the
application server, then the mobile device
sends two transmissions of 1000 KB each to
the application server.
Property
Value to be entered
maximo.mobile.refreshdata.numberrec
The number of records to be downloaded by

each request when the user refreshes the
mobile device. You can adjust the number of
records that the mobile device retrieves
according to the network latency. The
default record download value is 50.
Importing mobile application data

Information that is critical to the installation and configuration process must be
imported onto the application server.
Procedure
1. Start the application server.
2. In a command prompt, navigate to the maximo_root\mobiletools\maximo folder.
3. Enter importall.cmd.
Translating Maximo Mobile Suite

If the base language of your application server is not English, you can translate the
Maximo Mobile Suite interface into the same language as your application server.
Before you begin

If you are translating Maximo Mobile Suite, it must be done after you run the
importall.cmd but before you run the packagemobile.cmd.
About this task

Maximo Mobile Suite does not support bidirectional languages.
Procedure
2. Enter translatemobile.cmd.
3. Restart the application server.
Packaging application bundles

The packaging process creates mobile application bundles on the application
server. The bundles are uploaded to the application server to create profiles, which
run the Maximo Mobile Suite applications.
Procedure
2. Enter packagemobile.cmd and wait for the Build Successful message.
3. Exit the command window and close the application server for your changes to
take effect.
Chapter 6. Preparing to install Maximo Mobile Suite on a mobile device
13
14
Chapter 7. Installation of mobile device middleware

The middleware installation process downloads the profile that is generated by the
packagemobile.cmd file, extracts it, and prepares it for use. The Maximo Mobile
Suite application folder is copied onto the mobile device.
How you install middleware depends on what type of mobile device is being used.
The middleware that is installed on handheld mobile devices, such as Motorola
Symbol or Intermec devices, is different from the middleware that is installed on
larger mobile devices such as a personal computer notebook or tabletPC.
Mobile devices must be able to communicate with the application server so that
the Maximo Mobile Suite can be downloaded to the device. You must install the
Java virtual machine, IBM DB2 Everyplace database, and the Maximo Mobile
Installer application.
Installing middleware onto a mobile device

Mobile workers can use Maximo Mobile Suite from mobile devices such as a
Motorola Symbol or Intermec handheld devices. To install Maximo Mobile Suite on
the device, you must install the middleware to generate the profile for the mobile
device.
Before you begin

You can map the Maximo folder in a client that has Microsoft ActiveSync installed
on it that can connect to the devices. If you do not have access to a client computer
with support for Microsoft Active Sync, navigate to the maximo_root\mobiletools\
maximo\ folder, and double-click the importinstallers.cmd file. Then you can
access the Maximo Mobile Installer .cab files from a Web browser at
http://hostname:port/maximomobile/mobileinst/.
Procedure
1. On the application server, navigate to the maximo_root\mobiletools\maximo
folder. Select the installation file for your device, depending on whether you
are using Windows Mobile version 5 or 6, and whether your mobile device has
an Xscale or ArmV4T processor.
2. Connect the mobile device to Microsoft ActiveSync. On the application server,
select the CEAppMgr.cmd file. Wait for the files to be automatically copied onto
the device.
3. On the mobile device, select Device as the location for the installation files, and
click Install.
4. Click OK.
5. Select a profile to download and install the profile.
6. Close the application for the changes to take effect.
15
Installing middleware onto a personal computer

Mobile workers can use Maximo Mobile Suite on personal computers such as a
notebook, tabletPC, or desktop computer. To install Maximo Mobile Suite on the
computer, you must install the middleware to generate the profile for the
computer.
Procedure
From the source_root\mobiletools\devicesetup\DESKTOP directory, copy the
IBM_maximo_Mobile folder onto the personal computer for mobile workers.
2. Right-click the setEnv.cmd file, and open it with a text editor.
3. Edit the JAVA_HOME environment variable by inserting the path to the folder
where the JRE folder is installed on the personal computer. Save the text editor
file.
1.
4. Double-click the Mobile_Installer.cmd file to start the Mobile Installer

application.
5. Specify the host name, port, user name and password to connect to the
application server.
6. Select a profile to download and install the profile.
7. Close the application for the changes to take effect.
16
Chapter 8. Configuring the IBM Maximo Mobile Suite

You configure Maximo Mobile Suite by changing settings on the application server.
Configuring Maximo Mobile Suite ensures that the application server can properly
handle data from mobile devices, facilitates communication between mobile
devices and the application server, enables bar code scanning, and optimizes data
transmission to mobile devices.
Ensuring records are unique

A record that is created on a mobile device is not validated until it is uploaded to
the application server. The validation process checks to ensure that the attribute
that is defined as its unique identifier does not exist on the Maximo database.
Procedure
1. From the Mobile Data Manager application, specify the group for whom record
duplication is prevented.
2. Select Select Action Asset Manager Options.
3. Specify the attribute that uniquely defines the asset. For example, the
SERIALNUM attribute uses the serial number of an asset to validate the
uniqueness of the record.
4. Save the record.
Sending status changes separately from records

You can define which statuses are sent to the application separately from work
order or ticket records. When mobile workers update the application server with
status changes for work orders and tickets, they can continue to work on work
orders and tickets stored on the mobile device.
Procedure
1. From the Mobile Data Manager application, specify the group for which you
want to allow independent status changes.
2. Select Select Action Mobile Work Manager Options Status Changes.
3. Specify for which work orders or tickets a mobile worker can send an
independent status change to the application server.
4. Click OK.
Creating asset statuses

When mobile workers are performing an audit, they might need to change the
status of an asset to indicate that it is missing. You can create a status that works
the same as an operating status, but which indicates that an asset cannot be found.
Procedure
1. In the Domains application, open the LOCASSETSTATUS domain.
2. Create a new synonym domain with the following values:
Internal Value
Value
Description
OPERATING
MISSING
Asset missing
17
3. Click OK.
Changing polling frequency

Transaction polling affects the rate at which the application server processes
transactions from a mobile device. You can increase the speed at which information
is sent from a mobile device to the application server by increasing the rate at
which the application server queue is polled for transactions.
About this task

Cron tasks are jobs that are set to run automatically and on a fixed schedule. By
default, the cron task for transaction polling is set to run every minute. Each
polling instance processes one transaction. To increase the efficiency of transaction
processing, increase the polling instances to process several transactions at the
same time. Polling periods determine how often each polling instance runs.
Procedure
1. In the Cron Task Setup application, retrieve the MOBILETXN cron task and
click the Polling Frequency tab.
2. In the Instances field, enter the number of polling instances to run at the same
time. The default value is 1 polling instance per polling period.
3. Specify the number of minutes between each polling instance. The default
value is 1 minute.
Example
A polling instance value of 5 with a polling period value of 2 means that five
transactions are processed every 2 minutes.
Removing transactions from inactive users

If users do not connect with the application server from their mobile device after a
specified number of days, you can remove all the pending transactions between
the mobile device and the application server.
Procedure
1. In the Cron Task Setup application, retrieve the MOBILEDEVCLEANUP cron
task.
2. In the NOOFDAYS parameter, enter the number of days after which
transactions are removed from mobile devices. The default value is 10 days.
3. Save the cron task.
Creating a profile for bar code scanning

If you are using bar code scanning, you must create a profile folder to contain the
files that are needed for bar code scanning.
Procedure
1. Navigate to the maximo_root\mobiletools\profiles\pda folder.
2. In the Profiles folder, copy the pda folder and rename it Intermec, Symbol, or
Custom if you are not using Intermec or Motorola Symbol mobile devices.
18
3. In the new profile folder, edit the profile.properties file by changing the
maximo.mobile.profile.name=PDA attribute to the name given to the new
profile. For example, maximo.mobile.profile.name=SYMBOL.
4. In the common\appsetup folder, copy the mobile.properties file to the
new_profile\appsetup folder.
5. In the mobile.properties file, delete // to enable the required Intermec or
Motorola Symbol bar code driver.
Enabling bar code scanning on an Intermec mobile device

If your organization uses Intermec mobile devices for bar code scanning, you must
download files from the Intermec Web site to enable the Intermec mobile devices
for bar code scanning.
Procedure
1. Go to the Intermec Supply Chain Management Web site at www.intermec.com.
2. Download the IDL Resource Kit - Data Collection and install it in your
C:\Program Files directory.
3. Open Microsoft ActiveSync and navigate to the Tools\Explore Pocket PC
folder.
4. Copy the files in the following table to the specified locations.
Source location
Name of file
Target location
C:\Program
Files\Intermec\Developer
Library\Data Collection
Resource
Kit\Runtime\WCE420\
PocketPC 2003\processor
type: Armv4 or xScale\
JavaDataCollection.cab
maximo_root\mobiletools\
profiles\Intermec profile
folder\devicesetup
C:\Program
Files\Intermec\Developer
Library\JAVALib\
DataCollection.jar
folder\devicesetup\Maximo\
lib
C:\Windows
itcscan.dll
folder\\devicesetup\J9\
PPRO11\bin
5. Navigate to the maximo_root\mobiletools\maximo folder and double-click the

packagemobile.cmd file to upload the new bar code profile to the application
server.
6. On the mobile device, navigate to the Programs IBM Maximo Mobile folder
and run the Mobile Installer application to update the device with the updated
profile.
7. If you are using Windows Mobile 5 as an operating system, on the mobile
device, navigate to the maximo_root folder, and then double-click the
JavaCollection.cab file.
Adding a library to Intermec mobile devices

If you are using Intermec mobile devices for bar code scanning, you need to edit
the properties file for each application to add a library that handles bar code
scanning for your device.
19
Procedure
1. Navigate to the maximo_root\mobiletools\profiles\pda\devicesetup\Maximo\
lib directory.
2. Right-click the properties file for each application to open it with a text editor.
3. At the end of the text file, enter \maximo\lib\DataCollection.jar. Before you
update the properties file, it contains the following data:
# App parameters
jvm.parameters="-Xjit:count=0" "-jcl:ppro11" "-classpath" "\maximo\lib\
db2ejdbc.jar;\maximo\lib\mobilepreboot.jar;"
After you edit the properties file, it contains the following data:
# App parameters
db2ejdbc.jar;\maximo\lib\mobilepreboot.jar;maximo\lib\DataCollection.jar"
4. Save the updated properties file.
Enabling bar code scanning on a Motorola Symbol mobile device

If your organization uses a Motorola Symbol mobile devices for bar code scanning,
you must download files from the Motorola Web site to enable the Motorola
mobile devices for bar code scanning.
Procedure
1. Go to the Motorola Symbol Support Central Web site at support.symbol.com.
2. Search for the Symbol Mobility Developer Kit for Java and download the latest
version that is compatible with your device.
3. Install the developer kit in your C:\Program Files\Symbol Mobility Developer
Kit for Java\ directory.
4. Open Microsoft ActiveSync and navigate to the Tools\Explore Pocket PC
folder.
5. Copy the files in the following table to the specified locations.
Source location
Name of file
Target location
C:\Program Files\Symbol
Mobility Developer Kit for
Java\v1.3\bin\
symbolclasses.jar
profiles\Symbol profile
folder\devicesetup\Maximo\
lib
C:\Program Files\Symbol
Mobility Developer Kit for
Java\v1.3\bin\
symboljavaapi.dll
profiles\Symbol profile
folder\devicesetup\Windows
6. Navigate to the maximo_root\mobiletools\maximo folder and double-click the

packagemobile.cmd file to upload the new bar code profile to the application
server.
7. On the mobile device, navigate to the Programs IBM Maximo Mobile folder
and run the Mobile Installer application to update the device with the updated
profile.
Adding a library to Motorola Symbol mobile devices

If you are using Motorola Symbol mobile devices for bar code scanning, you need
to edit the properties file for each application to add a library that handles bar
code scanning for your device.
20
Procedure
1. Navigate to the maximo_root\mobiletools\profiles\pda\devicesetup\Maximo\
lib directory.
2. Right-click the properties file for the application to open it with a text editor.
3. At the end of the text file, enter \maximo\lib\symbolclasses.jar. Before you
edit the properties file, it contains the following data:
# App parameters
db2ejdbc.jar;\maximo\lib\mobilepreboot.jar;"
After you edit the properties file, it contains the following data:
# App parameters
db2ejdbc.jar;\maximo\lib\mobilepreboot.jar;maximo\lib\symbolclasses.jar"
4. Save the updated properties file.
21
22
Chapter 9. Managing data for mobile devices

The quantity of data that is sent to a mobile device affects how a mobile device
functions and how the device is used by on-site workers. You can filter data, count
the number of records, analyze data quantity, remove excess data, and enable or
disable automatic downloading of data to control the data volume sent to a device.
Limiting data sent to mobile devices

You can create queries to filter the number of records that can be downloaded by
mobile devices. The queries are created in the Mobile Data Manager application on
the application server. Creating simple SQL statements is preferred because
complex statements increase processing time.
Procedure
1. In the Mobile Data Manager application, enter the name of the user group for
which you want to limit the available records on the mobile device.
2. Select an application, and then select a data group.
3. Create a query for each data group. For example, you can create a query for
assets so that only assets that are active for 180 days or fewer can be queried
from a mobile device. Repeat the process for all data groups and user groups in
the applications.
Automatically downloading records onto a mobile device

When you create a query, you can configure a mobile device to automatically
download queried records. If this option is not enabled, the mobile device user can
choose to download the records upon the next refresh of the mobile device, which
allows the mobile device to perform other tasks.
Procedure
1. In the Mobile Data Manager module on the application server, create a query
for a user group in an application.
2. Before you save the query, select Download by Default from the query creation
screen.
3. Save the query.
Counting records for a mobile device

After you create a query, you can see how many records the query will send to a
mobile device before the mobile device downloads them. If the record count is
high, you can decide to remove records or create a more precise query.
Procedure
1. In the Mobile Data Manager application on the application server, create a
query for a user group in an application.
2. Before you save the query, click Count Records from the query creation screen.
3. Enter the user name of the user for whom you want to count the records from
the query being sent to a mobile device.
4. Click OK.
23
Analyzing data for a mobile device

After you create queries, you can analyze all the data from all the queries that is
on a mobile device for a mobile user. The result of the analysis displays the
number of records on a device for a user, categorized by data groups. If the record
count is high, you can remove data to increase the speed of the mobile device.
Procedure
1. After the queries are created in the Mobile Data Manager application on the
application server, select the Select Action menu.
2. Select Analyze Mobile Data.
3. Select an application, then enter a user name to analyze.
4. Select Full Refresh or Work List Refresh. A full refresh displays all the data on
a mobile device, and a work list refresh displays the work list items and the
supporting data on the device. Analyzing the data may take several minutes
because the data transfer to the mobile device is being simulated.
Removing supporting data from a mobile device

You can remove supporting data to reduce the quantity of data being sent to
mobile devices. For example, you can remove the failure reports in work orders
coming from the Maximo Mobile Work Manager application. If you remove
supporting data, the data is removed from all groups and users.
Procedure
1. After the queries are created in the Mobile Data Manager application on the
application server, click the Select Action menu.
2. Select Supporting Data.
3. Select an application, and then select a data group. The supporting data is
listed.
4. To remove the supporting data from all groups and users, clear the Download
check box of the data group name of the supporting data.
5. Save your changes.
24
Chapter 10. Customizing

After configuration is complete, you can change the appearance and behavior of
the user interface on a mobile device. Customizing is done by changing the XML
definition files for an application.
Configuring Maximo Mobile Suite applications for mobile devices

When you change the XML definition file for a Maximo Mobile Suite application,
you change how information is displayed on a mobile device and how the
interface behaves. For example, you can change the name of a field or whether a
field is mandatory.
About this task

The XML definition files are in the maximo_root\mobiletools\maximo\
metadatafiles directory.
Application name
XML definition file name
IBM Maximo Mobile Work Manager
mobilewo.xml
IBM Maximo Mobile Inventory Manager
mobileinv.xml
IBM Maximo Mobile Asset Manager
mobileam.xml
Procedure
1. Open the XML definition file for the application that you want to configure.
2. Add or change the attribute for the XML tag. For example, by adding the
size=3 attribute to the <textbox> tag, the length of a field is 3.
3. Save the XML definition file.
Application configuration planning

Some attributes in the XML definition files have complex relationships. You must
decide which value to give to the attributes when you configure the XML
definition files.
Validating values on a device or application server

Because mobile devices contain a limited amount of data, not all possible field
values can be stored on the device. The system can verify whether a value that a
user enters exists on the device or on the application server. The domain validation
is configured in the domain and domainattribute attributes of the XML definition
file of an application.
A user enters 11439 in the Asset field from a mobile device. This asset number is
checked to see if it exists on the mobile device. No error is created if the asset
number does not exist on the device, but the domain and domainattribute
attributes are defined in the definition file for the application.
Asset number 11439 is verified on the application server after the mobile device
next uploads data to it. Because this asset is stored on the application server, the
transaction involving asset 11439 can be completed.
25
Record creation during bar code scans

When you configure the XML definition files for bar code scanning, you must
configure the enablebarcode and insertonscan attributes, and the <scanevent> tag.
The enablebarcode attribute has true and false values that enable the bar code
scanning. The insertonscan attribute enables a record to be created when the
<scanevent> tag is set to true.
After setting the enablebarcode attribute to true, you must enter one of the
following possible XML values for the insertonscan attribute to create a record
when the bar code on an item is scanned.
Table 1. Possible values for the insertonscan attribute
Attribute
Condition
Action
notfound
No record exists for the scanned

item
Prompts the mobile device user to

create a record for the scanned item.
instant
Whether or not a record exists for

a scanned item
Automatically creates a record for the

scanned item.
instantask
Whether or not a record exists for

a scanned item
Prompts the mobile device user to

create a record for the scanned item.
The <scanevent> tag creates or displays the record after the insertonscan attribute
activates the system to create a record.
The following table lists the required attributes for the <scanevent> tag.
Table 2. Required attributes for the <scanevent> tag
Attribute
Description
ID
Identifies the control with a unique identifier.
type
view: Displays the record if one exists. (Default value).

insert: Creates a record.
event
The name of the event that handles the information that is read from the
scanner.
targetid
The name of the page that the scan event loads.
value
Supplementary information that is sent to the current event, if required.
Example
You are configuring the XML definition file for Maximo Mobile Work Manager,
and want the table for work orders to be configured for bar code scanning. In the
<table> tag for work orders in the mobilewo.xml definition file, you enter the
following code:
<table id="woresultstbl" rowsperpage="9" toolbar="tabletbar" filterpage="wofilter"
rowstyleevent="setworkliststyle" enablebarcode="true" insertonscan="notfound">
<scanevent id="woresultstbl_scan" type="view" event="gotoworklistmainpage"/>
XML attributes in Maximo Mobile Suite applications

Attributes control the display and behavior of an application. To configure an
application, you add or change attributes in XML tags in the XML definition file
for the application.
26
Attributes that affect the

appearance of a screen
XML tag
Attribute
Adding fields
<textbox>
dataattribute
Changing field lengths
<textbox>
size
Changing field labels
<textbox>
label
Limiting maximum
characters in a field
<textbox>
maxdatalength
XML tag
Attribute
Adding all data from a data

group to the Mobile Data
Manager application
<mobilembo>
usequeries= true
Downloading only data

groups defined in queries
<mobilembo>
queryrequired=true
If queryrequired=false, all
the data for this data group
is downloaded.
Attributes that affect the

behavior of a screen
Defining the display mode of <tablecolumn>

a table window
label= visible, invisible, or

fixed
Enabling table window

scanning
enablebarcode= true
<table>
Filtering the number of

<mbodependentfilter>
records retrieved by a mobile
device during SQL queries
filtercondition
Setting a field as required
<textbox>
displaymode= required
Setting a field as read-only
<textbox>
inputmode= read-only
Validating a domain
<textbox>
domain
domainattribute
Attributes that affect

barcode scanning
XML tag
Attribute
Creating records during

inventory scans
<table>
insertonscan= notfound,
instant, or instantask
Enabling dynamic table

scanning
<table>
enablebcevent
Scanning event
<scanevent>
ID
type = view (default) or
type=insert
event
Setting default primary or

secondary columns
<tablecolumn>
scantype= primary or
secondary
Changing the screen layout

If a mobile user runs Maximo Mobile Suite on a standard computer instead of on a
mobile device, the default screen layout does not use all the available screen space.
You can change the layout of columns and rows in a window to use the blank
space.
Chapter 10. Customizing
27
Procedure
1. Navigate to the maximo_root\mobiletools\maximo folder. Right-click the
properties file and open it with a text editor.
2. Change the following attributes:
XML tag
Attribute
Action
<sectionrow>
colspacing
The value given to this

attribute determines the
space between columns on a
screen.
<section>
rowspacing
The value given to this

attribute determines the
space between rows on a
screen.
3. Save the properties file.
Creating additional copies of a Mobile application

Running the cloneapp batch job duplicates the XML files of an application. You can
copy an application if you need it to look or behave in different ways within the
same environment.
Procedure
1. Open a command prompt and navigate to the maximo_root\mobiletools\maximo
directory.
2. Enter cloneapp appname clonename. For example, to duplicate the Mobile Work
Management application, enter cloneapp mobilewo mobilewo1.
3. Click OK when the Clone Successful message is displayed.
28
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the users responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
29
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
U.S.A. IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBMs future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol ( or ), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common
law trademarks in other countries. A current list of IBM trademarks is available on
the Web at Copyright and trademark information at www.ibm.com/legal/
copytrade.shtml
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.
30
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks
of others.
Notices
31
32
Index
A
application data
importing 13
application server
installing Maximo Mobile Suite
attributes
adding 27
modifying 27
B
bar code scanning
adding a library 20, 21
attributes 25
creating a profile 18
dependencies 25
enabling 19, 20
Intermec 20
Intermec mobile device 19
Motorola Symbol 21
Motorola Symbol mobile device
record creation 25
20
Maximo database
backing up 3
updating 3
Maximo Mobile
installing 5
Maximo Mobile Suite
properties 11
middleware
installing 15
installing on a mobile device 15
installing on a personal computer
overview 15
mobile applications
cloning 28
mobile device
counting records 23
download data 23
Intermec 20
managing data 23
Motorola Symbol 21
preparing to install 11
properties 11
requirements 1
cloning
mobile applications 28
configuration
overview 17
cron tasks
polling frequency 18
removing transactions 18
customizing
overview 25, 28
packaging
overview 13
planning
overview 3
polling frequency
cron tasks 18
profile
bar code scanning 18
properties
Maximo Mobile Suite 11
17
T
16
transactions
processing 18
queues 18
removing 18
translating
Maximo Mobile Suite
13
V
values
validating
25
X
XML definition files
configuring 25
overview 25
domain validation
attributes 25
dependencies 25
queries
creating 23
managing 23
I
importing
application data
installation
packaging 11
planning 3
updates 3
status changes
sending separately from records
statuses
creating asset statuses 17
R
record creation
bar code scanning 25
records
creating unique records
13
M
managing data
analyzing 24
counting records 23
creating queries 23
mobile device 23, 24
removing data groups
17
24
security
authenticating users 9
granting access rights 7
groups 7
LDAP servers 9
setup process
overview 1
33
34

Printed in USA

Mms711 InstallMaximo Mobile 7.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mms711 InstallMaximo Mobile 7.1

Uploaded by

Copyright:

Available Formats

Tivoli IBM Maximo Mobile Suite

Installation and Configuration Guide

Chapter 2. Preparing to install . . . . . 3

Chapter 7. Installation of mobile device

Chapter 8. Configuring the IBM Maximo

Copyright IBM Corp. 2007, 2009

Sending status changes separately from records .

Chapter 9. Managing data for mobile

Chapter 10. Customizing . . . . . . . 25

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 1. Overview of the installation and configuration

Mobile device requirements

128 MB of RAM minimum

v An environment that supports HTTP protocol, such as LAN TCP/IP, WiFi,

Copyright IBM Corp. 2007, 2009

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 2. Preparing to install

Copyright IBM Corp. 2007, 2009

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 3. Installing Maximo Mobile Suite on the application

Copyright IBM Corp. 2007, 2009

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 4. Granting access rights to security groups in the

Copyright IBM Corp. 2007, 2009

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 5. Authenticating users with application server

Copyright IBM Corp. 2007, 2009

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 6. Preparing to install Maximo Mobile Suite on a

Configuring the properties of a mobile device

Configuring files to access the application server

Maximo Mobile Suite properties

The IP address or host name of the

The port number of the application server.

Set this property to true if you are using a

Copyright IBM Corp. 2007, 2009

The user name of the person who is

The password of the user who is performing

Do not change the default context location

To enable the device for bar code scanning,

To enable the device for Radio Frequency

The maximum number of records to display

To enable the mobile device to be shared by

The size, in KB, that data from a users

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

The number of records to be downloaded by

Importing mobile application data

Translating Maximo Mobile Suite

Before you begin

About this task

Packaging application bundles

Chapter 6. Preparing to install Maximo Mobile Suite on a mobile device

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 7. Installation of mobile device middleware

Installing middleware onto a mobile device

Before you begin

Copyright IBM Corp. 2007, 2009

Installing middleware onto a personal computer

4. Double-click the Mobile_Installer.cmd file to start the Mobile Installer

IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 8. Configuring the IBM Maximo Mobile Suite

Ensuring records are unique

Sending status changes separately from records