Mms711 InstallMaximo mobile 7.1

Tivoli IBM Maximo Mobile Suite

Installation and Configuration Guide

Version 7.1.1

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 subsequentreleases 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 Contractwith IBM Corp.

ContentsChapter 1. Overview of the installationand configuration processes. . . . . . 1Mobile device requirements . . . . . . . . . 1

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

Chapter 3. Installing Maximo MobileSuite on the application server . . . . . 5

Chapter 4. Granting access rights tosecurity groups in the Maximo MobileSuite applications . . . . . . . . . . 7

Chapter 5. Authenticating users withapplication server security. . . . . . . 9

Chapter 6. Preparing to install MaximoMobile Suite on a mobile device . . . . 11Configuring the properties of a mobile device . . . 11Configuring files to access the application server . . 11Maximo Mobile Suite properties . . . . . . . 11Importing mobile application data . . . . . . . 13Translating Maximo Mobile Suite . . . . . . . 13Packaging application bundles . . . . . . . . 13

Chapter 7. Installation of mobile devicemiddleware . . . . . . . . . . . . . 15Installing middleware onto a mobile device . . . 15Installing middleware onto a personal computer . . 16

Chapter 8. Configuring the IBM MaximoMobile Suite . . . . . . . . . . . . 17Ensuring records are unique . . . . . . . . . 17

Sending status changes separately from records . . 17Creating asset statuses . . . . . . . . . . . 17Changing polling frequency . . . . . . . . . 18Removing transactions from inactive users . . . . 18Creating a profile for bar code scanning . . . . . 18Enabling bar code scanning on an Intermec mobiledevice . . . . . . . . . . . . . . . . 19

Adding a library to Intermec mobile devices . . 19Enabling bar code scanning on a Motorola Symbolmobile device. . . . . . . . . . . . . . 20

Adding a library to Motorola Symbol mobiledevices . . . . . . . . . . . . . . . 20

Chapter 9. Managing data for mobiledevices . . . . . . . . . . . . . . 23Limiting data sent to mobile devices . . . . . . 23Automatically downloading records onto a mobiledevice . . . . . . . . . . . . . . . . 23Counting records for a mobile device . . . . . . 23Analyzing data for a mobile device . . . . . . 24Removing supporting data from a mobile device . . 24

Chapter 10. Customizing . . . . . . . 25Configuring Maximo Mobile Suite applications formobile devices . . . . . . . . . . . . . 25

Application configuration planning . . . . . 25XML attributes in Maximo Mobile Suiteapplications . . . . . . . . . . . . . 26

Changing the screen layout . . . . . . . . . 27Creating additional copies of a Mobile application 28

Notices . . . . . . . . . . . . . . 29Trademarks . . . . . . . . . . . . . . 30

Index . . . . . . . . . . . . . . . 33

Copyright IBM Corp. 2007, 2009 iii

iv IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 1. Overview of the installation and configurationprocesses

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 touse an application. The configuration information about bar code scanning isprovided only for Motorola Symbol and Intermec mobile devices.

The following steps describe the complete process for installing and configuringMaximo Mobile Suite.1. Overview of the installation and configuration processes2. Preparing to install3. Installing Maximo Mobile Suite on the application server4. Application security5. Preparing to install on a mobile device6. Installing the middleware7. Configuring Maximo Mobile Suite8. Managing data for mobile devices9. Customizing

Mobile device requirementsEach mobile device must meet the following requirements to be able to run theapplication.v 128 MB of RAM minimumv Microsoft Windows Mobile 5.0 or 6.1v Microsoft ActiveSync 4.0 or laterv IBM Maximo Asset Management 7.1.1.6 or laterv An environment that supports HTTP protocol, such as LAN TCP/IP, WiFi,cellular, or satellite communications.

Copyright IBM Corp. 2007, 2009 1

2 IBM Maximo Mobile Suite 7.1.1: Installation and Configuration Guide

Chapter 2. Preparing to installFor the installation process to be successful, you must ensure that various system,device, and precautionary requirements are met. You must create a backup of thedatabase, update the database and stop the application server.

Procedure1. 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 applicationserver

You must install Maximo Mobile Suite on the application server after IBM MaximoAsset Management is installed. The Maximo Mobile Suite requires the separateinstallation of additional components.

Procedure1. 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 theMaximo Mobile Suite applications

To install the Maximo Mobile Suite, you must grant access rights to the MobileInstaller application, and to the user who is performing the installation. Otheraccess rights can be granted later during the configuration process because allusers must have access rights to an application.

Procedure1. 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. TheMobile Installer application must be granted read access rights for theinstallation process to be successful.

3. Save the updated profile. Log out for the changes to take effect.


Chapter 5. Authenticating users with application serversecurity

You can prevent unauthorized users from accessing confidential information byauthenticating users on a lightweight directory access protocol (LDAP) server fordatabase security.

Procedure1. 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 tags to uncomment the lines after the

and 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 aWebLogic application server) cron task to active.


Chapter 6. Preparing to install Maximo Mobile Suite on amobile device

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

Configuring the properties of a mobile deviceThe mobile.properties file is embedded into each application bundle. You mustenter information about the mobile device, the application server, and whichfeatures are used for each type of device in this file so that the mobile device cancommunicate with the application server after it is installed.

Procedure1. 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 serverYou must configure the properties files that are used to access the applicationserver. Configuring the mobiletools.properties file enables the files and packagesto communicate with the server. The .cmd files are the tools that are used in thepackaging and importing process.

Procedure1. 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 propertiesThe properties for Maximo Mobile Suite must be configured with specific values toenable communication to and from the application server.

Property Value to be entered

maximo.mobile.hostname The IP address or host name of theapplication server.

maximo.mobile.port The port number of the application server.

maximo.mobile.ssl Set this property to true if you are using aSecure Socket Layer (SSL) environment.Otherwise, leave the value as false.



maximo.mobile.username The user name of the person who isperforming the installation. This securitygroup for the user must already beconfigured in the Security Groups (Mobile)application.

maximo.mobile.password The password of the user who is performingthe installation.

maximo.mobile.contextname Do not change the default context locationvalue of \maximomobile\mobileservices

maximo.mobile.barcode To enable the device for bar code scanning,delete the // prefix before the name of themobile device manufacturer.

v SYMBOLv INTERMECv CUSTOM, for other devices, which requirefurther configuration.

maximo.mobile.rfid To enable the device for Radio FrequencyIdentification (RFID), delete the // prefixbefore the name of the mobile devicemanufacturer.

v SYMBOLv INTERMECv CUSTOM, for other devices, which are notready for immediate use and requirefurther configuration.

maximo.mobile.datafetchsize The maximum number of records to displayon the device. The default value is 1000.

maximo.mobile.snapshot To enable the mobile device to be shared bymultiple users, set the Save and Restoreproperty to true.This setting moves all data from a deviceonto the application server when a user logsoff the device. It uploads the data back ontothe device when the user logs back in.This setting allows for maximum memoryusage by the device without losing anydetails from a users session. The user canuse any device to log in because informationis stored on the application server and noton individual devices.

maximo.mobile.snapshot.chunksizekb The size, in KB, that data from a userssession is divided into for fastertransmission between the application serverand the mobile device.The size limit is imposed when the Save andRestore property is set to true and a userssession data has exceeded this limit. Thedefault limit is 1000 KB.For example, if a users session contains2000 KB of data to be uploaded to theapplication server, then the mobile devicesends two transmissions of 1000 KB each tothe application server.



maximo.mobile.refreshdata.numberrec The number of records to be downloaded byeach request when the user refreshes themobile device. You can adjust the number ofrecords that the mobile device retrievesaccording to the network latency. Thedefault record download value is 50.

Importing mobile application dataInformation that is critical to the installation and configuration process must beimported onto the application server.

Procedure1. Start the application server.2. In a command prompt, navigate to the maximo_root\mobiletools\maximo folder.3. Enter importall.cmd.

Translating Maximo Mobile SuiteIf the base language of your application server is not English, you can translate theMaximo 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 theimportall.cmd but before you run the packagemobile.cmd.

About this task

Maximo Mobile Suite does not support bidirectional languages.

Procedure1. In a command prompt, navigate to the maximo_root\mobiletools\maximo folder.2. Enter translatemobile.cmd.3. Restart the application server.

Packaging application bundlesThe packaging process creates mobile application bundles on the applicationserver. The bundles are uploaded to the application server to create profiles, whichrun the Maximo Mobile Suite applications.

Procedure1. In a command prompt, navigate to the maximo_root\mobiletools\maximo folder.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

Chapter 7. Installation of mobile device middlewareThe middleware installation process downloads the profile that is generated by thepackagemobile.cmd file, extracts it, and prepares it for use. The Maximo MobileSuite 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 MotorolaSymbol or Intermec devices, is different from the middleware that is installed onlarger mobile devices such as a personal computer notebook or tabletPC.

Mobile devices must be able to communicate with the application server so thatthe Maximo Mobile Suite can be downloaded to the device. You must install theJava virtual machine, IBM DB2 Everyplace database, and the Maximo MobileInstaller application.

Installing middleware onto a mobile deviceMobile workers can use Maximo Mobile Suite from mobile devices such as aMotorola Symbol or Intermec handheld devices. To install Maximo Mobile Suite onthe device, you must install the middleware to generate the profile for the mobiledevice.

Before you begin

You can map the Maximo folder in a client that has Microsoft ActiveSync installedon it that can connect to the devices. If you do not have access to a client computerwith support for Microsoft Active Sync, navigate to the maximo_root\mobiletools\maximo\ folder, and double-click the importinstallers.cmd file. Then you canaccess the Maximo Mobile Installer .cab files from a Web browser athttp://hostname:port/maximomobile/mobileinst/.

Procedure1. On the application server, navigate to the maximo_root\mobiletools\maximo

folder. Select the installation file for your device, depending on whether youare using Windows Mobile version 5 or 6, and whether your mobile device hasan 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 ontothe device.

3. On the mobile device, select Device as the location for the installation files, andclick Install.

4. Click OK.5. Select a profile to download and install the profile.6. Close the application for the changes to take effect.


Installing middleware onto a personal computerMobile workers can use Maximo Mobile Suite on personal computers such as anotebook, tabletPC, or desktop computer. To install Maximo Mobile Suite on thecomputer, you must install the middleware to generate the profile for thecomputer.

Procedure1. 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 editorfile.

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

5. Specify the host name, port, user name and password to connect to theapplication server.

6. Select a profile to download and install the profile.7. Close the application for the changes to take effect.


Chapter 8. Configuring the IBM Maximo Mobile SuiteYou configure Maximo Mobile Suite by changing settings on the application server.Configuring Maximo Mobile Suite ensures that the application server can properlyhandle data from mobile devices, facilitates communication between mobiledevices and the application server, enables bar code scanning, and optimizes datatransmission to mobile devices.

Ensuring records are uniqueA record that is created on a mobile device is not validated until it is uploaded tothe application server. The validation process checks to ensure that the attributethat is defined as its unique identifier does not exist on the Maximo database.

Procedure1. 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 theuniqueness of the record.

4. Save the record.

Sending status changes separately from recordsYou can define which statuses are sent to the application separately from workorder or ticket records. When mobile workers update the application server withstatus changes for work orders and tickets, they can continue to work on workorders and tickets stored on the mobile device.

Procedure1. 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 statusesWhen mobile workers are performing an audit, they might need to change thestatus of an asset to indicate that it is missing. You can create a status that worksthe same as an operating status, but which indicates that an asset cannot be found.

Procedure1. 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


3. Click OK.

Changing polling frequencyTransaction polling affects the rate at which the application server processestransactions from a mobile device. You can increase the speed at which informationis sent from a mobile device to the application server by increasing the rate atwhich 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. Bydefault, the cron task for transaction polling is set to run every minute. Eachpolling instance processes one transaction. To increase the efficiency of transactionprocessing, increase the polling instances to process several transactions at thesame time. Polling periods determine how often each polling instance runs.

Procedure1. 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 fivetransactions are processed every 2 minutes.

Removing transactions from inactive usersIf users do not connect with the application server from their mobile device after aspecified number of days, you can remove all the pending transactions betweenthe mobile device and the application server.

Procedure1. 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 scanningIf you are using bar code scanning, you must create a profile folder to contain thefiles that are needed for bar code scanning.

Procedure1. 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.


3. In the new profile folder, edit the profile.properties file by changing themaximo.mobile.profile.name=PDA attribute to the name given to the newprofile. For example, maximo.mobile.profile.name=SYMBOL.

4. In the common\appsetup folder, copy the mobile.properties file to thenew_profile\appsetup folder.

5. In the mobile.properties file, delete // to enable the required Intermec orMotorola Symbol bar code driver.

Enabling bar code scanning on an Intermec mobile deviceIf your organization uses Intermec mobile devices for bar code scanning, you mustdownload files from the Intermec Web site to enable the Intermec mobile devicesfor bar code scanning.

Procedure1. 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:\ProgramFiles\Intermec\DeveloperLibrary\Data CollectionResourceKit\Runtime\WCE420\PocketPC 2003\processortype: Armv4 or xScale\

JavaDataCollection.cab maximo_root\mobiletools\profiles\Intermec profilefolder\devicesetup

C:\ProgramFiles\Intermec\DeveloperLibrary\JAVALib\

DataCollection.jar maximo_root\mobiletools\profiles\Intermec profilefolder\devicesetup\Maximo\lib

C:\Windows itcscan.dll maximo_root\mobiletools\profiles\Intermec profilefolder\\devicesetup\J9\PPRO11\bin

5. Navigate to the maximo_root\mobiletools\maximo folder and double-click thepackagemobile.cmd file to upload the new bar code profile to the applicationserver.

6. On the mobile device, navigate to the Programs IBM Maximo Mobile folderand run the Mobile Installer application to update the device with the updatedprofile.

7. If you are using Windows Mobile 5 as an operating system, on the mobiledevice, navigate to the maximo_root folder, and then double-click theJavaCollection.cab file.

Adding a library to Intermec mobile devicesIf you are using Intermec mobile devices for bar code scanning, you need to editthe properties file for each application to add a library that handles bar codescanning for your device.

Chapter 8. Configuring the IBM Maximo Mobile Suite 19

Procedure1. 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 parametersjvm.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 parametersjvm.parameters="-Xjit:count=0" "-jcl:ppro11" "-classpath" "\maximo\lib\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 deviceIf your organization uses a Motorola Symbol mobile devices for bar code scanning,you must download files from the Motorola Web site to enable the Motorolamobile devices for bar code scanning.

Procedure1. 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\SymbolMobility Developer Kit forJava\v1.3\bin\

symbolclasses.jar maximo_root\mobiletools\profiles\Symbol profilefolder\devicesetup\Maximo\lib

C:\Program Files\SymbolMobility Developer Kit forJava\v1.3\bin\

symboljavaapi.dll maximo_root\mobiletools\profiles\Symbol profilefolder\devicesetup\Windows

6. Navigate to the maximo_root\mobiletools\maximo folder and double-click thepackagemobile.cmd file to upload the new bar code profile to the applicationserver.

7. On the mobile device, navigate to the Programs IBM Maximo Mobile folderand run the Mobile Installer application to update the device with the updatedprofile.

Adding a library to Motorola Symbol mobile devicesIf you are using Motorola Symbol mobile devices for bar code scanning, you needto edit the properties file for each application to add a library that handles barcode scanning for your device.


Procedure1. 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 parametersjvm.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 parametersjvm.parameters="-Xjit:count=0" "-jcl:ppro11" "-classpath" "\maximo\lib\db2ejdbc.jar;\maximo\lib\mobilepreboot.jar;maximo\lib\symbolclasses.jar"

4. Save the updated properties file.

Chapter 8. Configuring the IBM Maximo Mobile Suite 21

Chapter 9. Managing data for mobile devicesThe quantity of data that is sent to a mobile device affects how a mobile devicefunctions and how the device is used by on-site workers. You can filter data, countthe number of records, analyze data quantity, remove excess data, and enable ordisable automatic downloading of data to control the data volume sent to a device.

Limiting data sent to mobile devicesYou can create queries to filter the number of records that can be downloaded bymobile devices. The queries are created in the Mobile Data Manager application onthe application server. Creating simple SQL statements is preferred becausecomplex statements increase processing time.

Procedure1. 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 queriedfrom a mobile device. Repeat the process for all data groups and user groups inthe applications.

Automatically downloading records onto a mobile deviceWhen you create a query, you can configure a mobile device to automaticallydownload queried records. If this option is not enabled, the mobile device user canchoose to download the records upon the next refresh of the mobile device, whichallows the mobile device to perform other tasks.

Procedure1. 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 deviceAfter you create a query, you can see how many records the query will send to amobile device before the mobile device downloads them. If the record count ishigh, you can decide to remove records or create a more precise query.

Procedure1. 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.


Analyzing data for a mobile deviceAfter you create queries, you can analyze all the data from all the queries that ison a mobile device for a mobile user. The result of the analysis displays thenumber of records on a device for a user, categorized by data groups. If the recordcount is high, you can remove data to increase the speed of the mobile device.

Procedure1. 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 thesupporting data on the device. Analyzing the data may take several minutesbecause the data transfer to the mobile device is being simulated.

Removing supporting data from a mobile deviceYou can remove supporting data to reduce the quantity of data being sent tomobile devices. For example, you can remove the failure reports in work orderscoming from the Maximo Mobile Work Manager application. If you removesupporting data, the data is removed from all groups and users.

Procedure1. 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.


Chapter 10. CustomizingAfter configuration is complete, you can change the appearance and behavior ofthe user interface on a mobile device. Customizing is done by changing the XMLdefinition files for an application.

Configuring Maximo Mobile Suite applications for mobile devicesWhen you change the XML definition file for a Maximo Mobile Suite application,you change how information is displayed on a mobile device and how theinterface behaves. For example, you can change the name of a field or whether afield 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

Procedure1. 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 tag, the length of a field is 3.3. Save the XML definition file.

Application configuration planningSome attributes in the XML definition files have complex relationships. You mustdecide which value to give to the attributes when you configure the XMLdefinition files.

Validating values on a device or application server

Because mobile devices contain a limited amount of data, not all possible fieldvalues can be stored on the device. The system can verify whether a value that auser enters exists on the device or on the application server. The domain validationis configured in the domain and domainattribute attributes of the XML definitionfile of an application.

A user enters 11439 in the Asset field from a mobile device. This asset number ischecked to see if it exists on the mobile device. No error is created if the assetnumber does not exist on the device, but the domain and domainattributeattributes are defined in the definition file for the application.Asset number 11439 is verified on the application server after the mobile devicenext uploads data to it. Because this asset is stored on the application server, thetransaction involving asset 11439 can be completed.


Record creation during bar code scans

When you configure the XML definition files for bar code scanning, you mustconfigure the enablebarcode and insertonscan attributes, and the tag.The enablebarcode attribute has true and false values that enable the bar codescanning. The insertonscan attribute enables a record to be created when the tag is set to true.

After setting the enablebarcode attribute to true, you must enter one of thefollowing possible XML values for the insertonscan attribute to create a recordwhen the bar code on an item is scanned.

Table 1. Possible values for the insertonscan attributeAttribute Condition Action

notfound No record exists for the scanneditem

Prompts the mobile device user tocreate a record for the scanned item.

instant Whether or not a record exists fora scanned item

Automatically creates a record for thescanned item.

instantask Whether or not a record exists fora scanned item

Prompts the mobile device user tocreate a record for the scanned item.

The tag creates or displays the record after the insertonscan attributeactivates the system to create a record.

The following table lists the required attributes for the tag.

Table 2. Required attributes for the tagAttribute 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 thescanner.

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 tag for work orders in the mobilewo.xml definition file, you enter thefollowing code:

XML attributes in Maximo Mobile Suite applicationsAttributes control the display and behavior of an application. To configure anapplication, you add or change attributes in XML tags in the XML definition filefor the application.


Attributes that affect theappearance of a screen XML tag Attribute

Adding fields dataattribute

Changing field lengths size

Changing field labels label

Limiting maximumcharacters in a field

maxdatalength

Attributes that affect thebehavior of a screen XML tag Attribute

Adding all data from a datagroup to the Mobile DataManager application

usequeries= true

Downloading only datagroups defined in queries

queryrequired=trueIf queryrequired=false, allthe data for this data groupis downloaded.

Defining the display mode ofa table window

label= visible, invisible, orfixed

Enabling table windowscanning

enablebarcode= true

Filtering the number ofrecords retrieved by a mobiledevice during SQL queries

filtercondition

Setting a field as required displaymode= required

Setting a field as read-only inputmode= read-only

Validating a domain domaindomainattribute

Attributes that affectbarcode scanning XML tag Attribute

Creating records duringinventory scans

insertonscan= notfound,instant, or instantask

Enabling dynamic tablescanning

enablebcevent

Scanning event IDtype = view (default) ortype=insertevent

Setting default primary orsecondary columns

scantype= primary orsecondary

Changing the screen layoutIf a mobile user runs Maximo Mobile Suite on a standard computer instead of on amobile 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 blankspace.

Chapter 10. Customizing 27

Procedure1. 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

colspacing The value given to thisattribute determines thespace between columns on ascreen.

rowspacing The value given to thisattribute determines thespace between rows on ascreen.

3. Save the properties file.

Creating additional copies of a Mobile applicationRunning the cloneapp batch job duplicates the XML files of an application. You cancopy an application if you need it to look or behave in different ways within thesame environment.

Procedure1. 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.


NoticesThis 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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the users responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

U.S.A. IBM Corporation2Z4A/10111400 Burnet RoadAustin, 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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBMs future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol ( or ), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries. A current list of IBM trademarks is available onthe Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,and/or other countries.


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 ofMicrosoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marksof others.

Notices 31

IndexAapplication data

importing 13application server

installing Maximo Mobile Suite 5attributes

adding 27modifying 27

Bbar code scanning

adding a library 20, 21attributes 25creating a profile 18dependencies 25enabling 19, 20Intermec 20Intermec mobile device 19Motorola Symbol 21Motorola Symbol mobile device 20record creation 25

Ccloning

mobile applications 28configuration

overview 17cron tasks

polling frequency 18removing transactions 18

customizingoverview 25, 28

Ddomain validation

attributes 25dependencies 25

Iimporting

application data 13installation

packaging 11planning 3updates 3

Mmanaging data

analyzing 24counting records 23creating queries 23mobile device 23, 24removing data groups 24

Maximo databasebacking up 3updating 3

Maximo Mobileinstalling 5

Maximo Mobile Suiteproperties 11

middlewareinstalling 15installing on a mobile device 15installing on a personal computer 16overview 15

mobile applicationscloning 28

mobile devicecounting records 23download data 23Intermec 20managing data 23Motorola Symbol 21preparing to install 11properties 11requirements 1

Ppackaging

overview 13planning

overview 3polling frequency

cron tasks 18profile

bar code scanning 18properties

Maximo Mobile Suite 11

Qqueries

creating 23managing 23

Rrecord creation

bar code scanning 25records

creating unique records 17

Ssecurity

authenticating users 9granting access rights 7groups 7LDAP servers 9

setup processoverview 1

status changessending separately from records 17

statusescreating asset statuses 17

Ttransactions

processing 18queues 18removing 18

translatingMaximo Mobile Suite 13

Vvalues

validating 25

XXML definition files

configuring 25overview 25


Printed in USA

ContentsChapter 1. Overview of the installation and configuration processesMobile device requirements

Chapter 2. Preparing to installChapter 3. Installing Maximo Mobile Suite on the application serverChapter 4. Granting access rights to security groups in the Maximo Mobile Suite applicationsChapter 5. Authenticating users with application server securityChapter 6. Preparing to install Maximo Mobile Suite on a mobile deviceConfiguring the properties of a mobile deviceConfiguring files to access the application serverMaximo Mobile Suite propertiesImporting mobile application dataTranslating Maximo Mobile SuitePackaging application bundles

Chapter 7. Installation of mobile device middlewareInstalling middleware onto a mobile deviceInstalling middleware onto a personal computer

Chapter 8. Configuring the IBM Maximo Mobile SuiteEnsuring records are uniqueSending status changes separately from recordsCreating asset statusesChanging polling frequencyRemoving transactions from inactive usersCreating a profile for bar code scanningEnabling bar code scanning on an Intermec mobile deviceAdding a library to Intermec mobile devices

Enabling bar code scanning on a Motorola Symbol mobile deviceAdding a library to Motorola Symbol mobile devices

Chapter 9. Managing data for mobile devicesLimiting data sent to mobile devicesAutomatically downloading records onto a mobile deviceCounting records for a mobile deviceAnalyzing data for a mobile deviceRemoving supporting data from a mobile device

Chapter 10. CustomizingConfiguring Maximo Mobile Suite applications for mobile devicesApplication configuration planningXML attributes in Maximo Mobile Suite applications

Changing the screen layoutCreating additional copies of a Mobile application

NoticesTrademarks

IndexABCDIMPQRSTVX

Documents

Mms711 InstallMaximo mobile 7.1