Release 3

Configuration Guide

IBM Maximo Mobile Applications
First Edition (November 2006)
This edition applies to Release 3 of IBM Maximo Mobile Applications and to all subsequent releases and
modifications until otherwise indicated in new editions.
Third-Party Technology: Certain Maximo products contain technology provided under license from third
parties, as noted in the following table:
Open Source: Maximo contains computer software obtained from the public domain, known as "Open Source"
ownership of which is attributed as follows: Portions 2002, Steve Souza (admin@jamonapi.com). Portions
2000-2004, Jason Hunter & Brett McLaughlin. Portions 2004-2005, The Apache Software Foundation
(http://www.apache.org/).
Copyright International Business Machines Corporation 2006. All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
IBM Product Third-Party Information
All Products Portions 1996-2003 Visual Mining, Inc. Visual Mining
NetCharts Server provided by Visual Mining, Inc. 1998-
2005 Centennial Software Limited.
IBM Maximo Portions 1995-2004 Actuate Corporation. Portions 2005
BEA Systems, Inc. BEA WebLogic Server provided by BEA
Systems, Inc.
Portions 1996-2005, i-net software GmbH. J-Integra for
COM v2.4. 2004 Intrinsyc Software International, Inc.
Maximo Discovery
MSDE Copyright Microsoft

Corporation.
IBM Maximo Enterprise Asset Navigator Portions 1993-2002 Snowbound Software Corporation.
RasterMaster Raster imaging technology provided by
Snowbound Software Corporation.
Portions 1991 Pegasus Imaging Corp.
IBM Maximo Mobile Portions 2005 DataMirror, Inc.
Portions 2000-2005 Zaval Creative Engineering Group.
IBM Maximo Mobile SE Portions 1996-2005 Syclo, LLC.
Note
Before using this information and the product it supports, read the information in Notices on page Notices-1.
Copyright IBM Corp. 2006 iii
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Chapter 1: Configuring the Maximo Mobile Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Adding/Removing Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Changing Field Lengths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Limiting the Number of Characters in a Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Changing Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Configuring a Table Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Adding/Removing Columns Within Table Window Selector Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Marking a Field as Being Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Marking a Field as Needing to Be Validated via a Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Changing the Frequency of the Server-Side Queue Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Changing How Often the Device Data in the Maximo Server Is Removed. . . . . . . . . . . . . . . . . . . . . . . . 1-5
Changing the Clock Setting to Accept Multiple Open Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Cloning a Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Adding/Removing Data Groups in the Security Groups Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Adjusting Queries Hard-Coded in the Mobile Screen XML Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Application Server Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Chapter 2: Implementing Your Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Importing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notices-1
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Contents
iv IBM Maximo Mobile Applications: Configuration Guide
Copyright IBM Corp. 2006 v
About This Guide
This section explains how this guide can help you to use IBM

Maximo

. It
also provides information about other IBM Corporation resources available to
you, such as additional documentation and support.
Audience
This guide provides configuration instructions for a system administrator,
network administrator, or other professional who modifies the IBM Maximo
Mobile applications after installation.
The guide enables you to configure the Maximo Mobile applications to suit the
specific needs and requirements of your company.
Related Documentation
For more information about Maximo Mobile applications, refer to the
following documentation:.
Support
IBM Maximo users with a valid Annual Customer Support Plan (ACSP) can
obtain product support online at Support Online: support.mro.com.
Support Online includes information about product releases, software
patches, and documentation updates. To find the most current version of a
document, refer to the Knowledge Base on this site.
Document Description
IBM Maximo Mobile Inventory
Manager Users Guide
Describes the Mobile Inventory
Manager application.
IBM Maximo Mobile Work Manager
Users Guide
Describes the Mobile Work Manager
application.
IBM Maximo Mobile Applications
Installation Guide
Provides instructions for installing the
Maximo Mobile applications,
including information on editing files
and packaging files for downloading on
mobile devices.
Support
vi IBM Maximo Mobile Applications: Configuration Guide
Copyright IBM Corp. 2006 1-1
This chapter describes various ways to configure the Maximo Mobile
applications to suit your specific needs and requirements.
Adding/Removing Fields
Each mobile application has a corresponding XML file. In Mobile Work
Manager, the file is named mobilewo.xml. The XML definitions can be found
in the <maximo_root>/mobiletools/maximo/metadata directory. These XML
definitions are hierarchical. At their highest level they are broken into two
parts: the <mobilembos> and the <mobilescreens> sections. The Mobile MBO
section contains parts relevant to the DB objects and definitions while the
Screen section is where the application's presentation is managed. Depending
on what you want to do, you may have to make changes to both sections (see
the example later in this section).
The best way to view, edit, and understand the structure of the XML
definitions is to use an XML editor such as Eclipse or XML Spy.
NOTE In addition, there are a few XML definitions that are used to control the
display of certain dialogs that are used within the respective mobile
application. These XML files can be found in the maximo/mobiletools/maximo/
metadata/system directory.
To remove a field, navigate the XML hierarchy to find the field, then either
comment it out or remove it entirely. To add a field, find the place where you
want to add the field, then add the appropriate tag. For example, if you
wanted to add the 'Work Order' (WONUM) field to a page you would add the
following:
<t ext box i d=" wodesct xt 1" dat aat t r i but e=" WONUM" ></ t ext box>
If the field has not yet been defined in the mobile mbo, you must do so at the
top of the XML definition. Using the same example of WONUM, you would
check to make sure the Work Order Number (WONUM) data attribute has
been added as shown below:
<mobi l emboat t r i but e name=" WONUM" mboat t r i but e=" WONUM"></
mobi l emboat t r i but e>
Configuring the Maximo
Mobile Applications
1
Changing Field Lengths
1-2 IBM Maximo Mobile Applications: Configuration Guide
Changing Field Lengths
Field lengths are designed to behave in the following way. We look at the
length as specified in the DB and if that length is between 1-5 we default the
physical width of the field to 5 capital B's. If the DB length is between 6-20 the
physical width of the field is dynamic and will display as X capital B's, where
X is the length specified in the DB. If the length in the DB is greater than 20,
the physical length of the field will be the equivalent of 20 capital B's. This can
be overridden on a field by field basis directly in the XML. As for the
maximum character width this is derived from the maximum character as set
in the DB. When a field is not bound (e.g. a non-persistent field) we are
defaulting the physical width to 15 capital B's. All of these ranges and widths
can also be adjusted by modifying the ui.properties file. The maximum
character length for all fields is set in DB Configuration.
To override a field width directly in XML, add this attribute to the <textbox>
tag like this:
<t ext box i d=" wodesct xt 1" dat aat t r i but e=" WONUM" si ze="3" ></ t ext box>
Limiting the Number of Characters in a Field
You can limit the number of characters a user can enter in a field even
though, in Database Configuration, the field is configured to hold more. For
example, a field might be configured in Database Configuration to hold a
maximum of 12 characters. You can limit the field to fewer characters by
adding an attribute to the <textbox> tag. The following example restricts the
field to allow 2 characters:
<t ext box i d=" wodesct xt 5" dat aat t r i but e=" WOPRI ORI TY"
maxdat al engt h=" 2" ></ t ext box>
You cannot expand the field to hold more characters than configured in the
database.
Changing Labels
By default, field labels come from the database. If you want to override the
database label, you must add the label attribute to the XML for the given field
label="XYZ123". In the example of the WONUM field, if nothing was changed
the on screen display would be 'Work Order', but if on a mobile device you
wanted to save space and shorten it to "WO No.", you would add the 'label'
attribute to the <textbox> tag in the following way:
<t ext box i d=" wodesct xt 1" dat aat t r i but e=" WONUM" l abel =" WO No. "></
t ext box>
Now follow the procedures in the chapter titled "Implementing your
Configuration Changes".
Configuring a Table Window
Configuring the Maximo Mobile Applications 1-3
Configuring a Table Window
Table Windows are first defined by the <table> tag and then by the
<tablecolumn> tags. Settings for the table itself such as the number of rows to
display or which QBE/Filter page to call are set within the <table> tag, while
defining which columns display, by default, and the names of those columns is
set within <tablecolumn> tags.
Mobile table windows have a unique feature that allows end-users, at
runtime, to select which columns are displayed. Columns which have the
attribute 'displaymode' set to 'visible' (e.g. displaymode="visible") will, by
default, display that column. However, if you want a column to be hidden from
the default view, but available for the user to display by selecting the column
selector icon, than within that <tablecolumn> tag the 'displaymode' must be
set to 'invisible (e.g. displaymode="invisible"). When 'displaymode' is set to
'fixed' that column will always display and is not configurable (i.e., a user
won't be able to hide it by unchecking it).
<t abl e i d=" wor esul t st bl " r owsper page=" 10" opaque=" t r ue"
t ool bar =" t abl et bar " f i l t er page=" wof i l t er "
r owst yl eevent =" set wor kl i st st yl e" >
<t abl ecol umn i d=" wor esul t s1" dat aat t r i but e="WONUM"
di spl aymode=" f i xed" >
<l i nk i d=" wor esul t s1L" event =" showpage" val ue=" womai n"
dat aat t r i but e=" WONUM" ></ l i nk>
</ t abl ecol umn>
<t abl ecol umn i d=" wor esul t s2" dat aat t r i but e="DESCRI PTI ON"
di spl aymode=" vi si bl e" / >
<t abl ecol umn i d=" wor esul t s3" dat aat t r i but e="STATUS"
di spl aymode=" i nvi si bl e" / >
</ t abl e>
Adding/Removing Columns Within Table Window
Selector Dialogs
Columns that have the their 'displaymode' set to either 'visible' or 'invisible'
will show up within the column selector list. Columns whose 'displaymode' is
set to 'fixed' will not show up in the column selector list.
Marking a Field as Being Required
Fields can be marked as being required on a mobile screen. However, it should
be noted that being required on the core has no influence on mobile. In other
words, if you want certain fields within your mobile applications to be
required you must explicitly define that. To set a field as being required
simply set the 'inputmode' attribute to 'required'. Once marked as such a red
asterisks will display next to that field.
<t ext box i d=" wodesct xt 5" dat aat t r i but e=" WOPRI ORI TY"
i nput mode=" r equi r ed"></ t ext box>
Marking a Field as Needing to Be Validated via a Domain
1-4 IBM Maximo Mobile Applications: Configuration Guide
NOTE If you want to mark a field as being read-only set the 'inputmode' to 'read-
only'.
Marking a Field as Needing to Be Validated via a Domain
Fields can be 'validated' on the device upon exiting a field by marking it so
within the XML. If we imagine the Asset field is set up accordingly, the
following will happen:
A user enters value 11439 in the Asset field. We look to see if this is a valid/
confirmed value in the Domain: Asset. In other words, we look to see if 11439
exists locally on the device. If it does, the user is all set and we move them on
to next field. If it does not, we display the following message dialog box.
This value cannot be validated locally. Would you like to:
Accept Value
Cancel & Clear
Lookup
'Accept Value' allows users to submit this value, 'Cancel & Clear' clears out
the value and puts the cursor back in field, and 'Lookup' takes the user to
Select Value page from which they can lookup locally or attempt to connect to
server.
In the XML definition, we will set for a given Text field whether or not we will
allow users to enter unconfirmed, potentially invalid values. If this
domainvaluerequired="true" the user will not be allowed to enter a value
which is not within the local domain. If this is so, the following message will
display:
This is not a valid value.
Cancel & Clear
Lookup
'Cancel & Clear' will clear out value and put cursor back in field, and 'Lookup'
will take user to Select Value page from which they can lookup locally or
attempt to connect to server
To set the fields as described above, you must find the corresponding field
within the respective XML definition and set three attributes:
( dat aat t r i but e=" WOASSET" domai n=" ASSET" domai nat t r i but e=" ASSETNUM"
domai nval uer equi r ed=" f al se" ) wi t hi n t he <t ext box> t ag.
<t ext box i d=" wodesct xt 4" dat aat t r i but e=" WOASSET" domai n=" ASSET"
domai nat t r i but e=" ASSETNUM" domai nval uer equi r ed=" f al se" ></ t ext box>
Changing the Frequency of the Server-Side Queue Polling
Configuring the Maximo Mobile Applications 1-5
Changing the Frequency of the Server-Side Queue Polling
Transactions sent to the core Maximo Server are placed in a server-side queue
named MOBILETXNQ. The frequency with which transactions are processed
from this queue is determined by cron tasks, which you can manage from the
Cron Task Setup application.
Maximo Mobile applications includes a cron task named MOBILETXN for
polling the transactions in MOBILETXNQ. It is set to run every minute. To
increase efficiency, you can set up multiple instances where each instance
picks up a different user's transactions, thereby processing the transactions in
parallel.
In addition, if the Maximo Server crashes or is killed, Maximo maintains a
Lock in the MOBILETXNLOCK table. Transactions will be maintained there
for a specified time after which the lock is cleared and the server attempts to
process the transactions again. The cron task that performs this lock is
MOBILETXNLOCKRELESASE and the parameter that specifies the time
interval is LOCKINTERVALINMINUTES. The default value is 10 minutes.
You can specify a different time interval as needed.
Changing How Often the Device Data in the Maximo
Server Is Removed
If, after a specified number of days, there are no transactions between a
mobile device and the Maximo Server, the transaction data is removed from
the server. A cron task named MOBILEDEVCLEANUP performs this data
removal. Its parameter, NOOFDAYS, specifies the number of days. The
default value is 10. There are some situations where you will need to increase
this value. For example, if device users go to remote locations for a long time,
such as 20 days on an offshore oil rig, then you must specify a value of 20 days
or more, as needed.
Changing the Clock Setting to Accept Multiple Open
Clocks
In the Mobile Work Manager application there is an implementation-wide
setting that allows mobile users to have multiple clocks running on a work
order or restricts it to a single a user to only allow them to have a single clock
running. This is controlled by a setting within the mobile.properties file found
in the Maximo > MobileDeployment directory.
maxi mo. mobi l e. mobi l ewo. mul t i pl et i mer s=t r ue
Cloning a Mobile Application
1-6 IBM Maximo Mobile Applications: Configuration Guide
Cloning a Mobile Application
Cloning a Maximo Mobile application follows a similar process to cloning a
core Maximo application. From a command prompt navigate to the Maximo >
MobileTools > Maximo directory and run the 'cloneapp' batch file by typing in
the following command:
cl oneapp APPYOURCLONI NG NEWAPPNAME
e.g. cloneapp MOBILEWO MOBILEWO1
Presuming everything works fine, you should get a 'CLONE SUCCESFUL'
message. There is a limitation of 10 characters on the length of the name of
the new application being created.
Adding/Removing Data Groups in the Security Groups
Application
The Data Groups that show up the Types of Data table window on the new
Mobile Data tab in the Security Groups application are derived from
<mobilembo> tags as specified in the first section of the corresponding
application's XML definition. In order for a Data Group to exist, and in turn
support a query for which such related data can be specified, the mbo must be
a top level object. If the mbo is a top level object, then setting the 'usequeries'
attribute within the <mobilembo> tag to 'true' will create that entry within
the table and allow queries to be set to manage this as a category of related
data.
<mobilembo name="ASSET" mboname="ASSET"
type="localworksetdownload" usequeries="true" multisitetype="SITE"
siteattribute="SITEID" description="Assets">
Adjusting Queries Hard-Coded in the Mobile Screen XML
Definitions
Certain pieces of metadata that are brought down to the device are controlled
directly within the XML definitions (i.e. mobilewo.xml). Within these XML
files there are two tags <mbofilter></mbofilter> and <mbodependentfilter></
mbodependentfilter> where this is set. For example, the extent of how many
supporting work orders are brought down with a given work order for its
associated asset is controlled by a sql query defined directly in the
mobilewo.xml within one of these tags. Where work order 1000 references
asset 11430, the number of work orders associated with asset 11430 would be
managed by such a sql query. In this instance, by default we will collect all
history work orders whose actual start date was within the last six months as
well as all non-history work orders (see below). To change this, one simply
needs to find the applicable tag and modify the sql statement within the
corresponding mobilewo.xml file.
Application Server Security
Configuring the Maximo Mobile Applications 1-7
<mbodependent f i l t er dependson=" ASSET" >
<mat ch mobi l emboat t r i but e=" ASSETNUM"
dependsonmobi l emboat t r i but e=" ASSETNUM" ></ mat ch>
<mat ch mobi l emboat t r i but e=" SI TEI D"
dependsonmobi l emboat t r i but e=" SI TEI D"></ mat ch>
<f i l t er condi t i on>
( hi st or yf l ag=0) or ( hi st or yf l ag=1 and ( act st ar t + 180) >= : sysdat e)
</ f i l t er condi t i on>
</ mbodependent f i l t er >
Other SQL statements may be housed within the <mbofilter></mbofilter>
Application Server Security
You can enable Maximo to use application server security to authenticate
users against an LDAP server. Refer to the IBM Maximo System
Administrators Guide for general information on how to set this up. If you set
up Maximo to use application server security and you install Maximo Mobile,
then additional steps are required.
To enable Maximo Mobile to use application server security:
1 Open the web.xml file in the following folder:
<maximo_root>applications\maximo\mobileweb\webmodule\WEB-INF
2 Set the useAppServerSecurity environment entry to true, as in the
following example:
<env-entry>
<description>Indicates whether to use Application Server security
or not</description>
<env-entry-name>useAppServerSecurity</env-entry-name>
<env-entry-value>true</env-entry-value>
3 In the same web.xml file, uncomment these lines:
<!--
<security-constraint>
<web-resource-collection>
<web-resource-name>MAXIMO Mobile resources</web-resource-
name>
<description>pages accessible by authorised users</description>
<url-pattern>*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<description>Roles that have access to MAXIMO Mobile</
description>
<role-name>maximouser</role-name>
</auth-constraint>
Application Server Security
1-8 IBM Maximo Mobile Applications: Configuration Guide
<user-data-constraint>
<description>data transmission gaurantee</description>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>MAXIMO Mobile Realm</realm-name>
</login-config>
-->
Copyright IBM Corp. 2006 2-1
After you make changes to the configuration of a mobile application (with the
exception of those configurations managed within the core Maximo Security
Groups (Mobile) application), you need to go through a deployment process
that includes importing, packaging, and then the final deployment of the
changes to the mobile device.
Importing
If you made changes to more than one Maximo Mobile application you will
need to run the importall command. However, this command uses the
mobiletools.properties file to connect to the MAXIMO Server and therefore
you must make sure you are pointing to the right server. The out-of-the-box
configuration assumes you are running on your local machine (i.e. localhost).
To run the importall command follow these steps.:
1 Ensure that the Maximo Application Server is running.
2 Go To Maximo > MobileTools > Maximo and open the file titled
mobiletools.properties. This file indicates where Maximo is running. We
assume it is running on your local machine (i.e. localhost).
3 Within the same directory Maximo > MobileTools > Maximo, run the
command file titled importall. This takes the XML definitions for all the
applications and puts them into the Maximo database. When the import is
successful you should get a 'BUILD SUCCESSFUL' message.
If you made changes to only one mobile application rather than running the
importall command you should run the importmetadata command. Like
the importall command, this uses the mobiletools.properties file to connect to
the MAXIMO server and therefore you must make sure you are pointing to
the right server. The out-of-the-box configuration assumes you are running on
your local machine (i.e. localhost).
1 Ensure that the Maximo Application Server is running.
2 Go To Maximo > MobileTools > Maximo and open the file titled
mobiletools.properties. This file indicates where Maximo is running. We
assume it is running on your machine (i.e. localhost).
3 Within the same directory Maximo > MobileTools > Maximo, run the batch
file titled importmetadata. However, before you do this make sure you
know the file location of the corresponding XML definition. From the
command window enter the following syntax:
Implementing Your
Configuration Changes
2
Packaging
2-2 IBM Maximo Mobile Applications: Configuration Guide
i mpor t met adat a <app xml f i l e l ocat i on>
As an example:
importmetadata c:\MAXIMO\mobiletools\maximo\metadatafiles\mobilewo.xml
This takes the XML definition and puts it into the Maximo database. When
the import is successful you should get a 'BUILD SUCCESSFUL' message.
Packaging
After a successful import you now need to package things up in order to create
application bundles which are used to run the applications on the mobile
device. Like the import process, depending on whether you are packaging up
one application or more than one application, the steps to follow will vary
slightly.
If you are working with a single application, make sure your mobile
applications are pointing to the correct server by going to Maximo >
MobileDeployment directory. You will see a couple of files. If your Maximo
Mobile application is running on a different server, which in the case of the
mobile applications it basically always is since it's running on a device, than
in the mobiledeoplyment.properties file you will have to point the device to
communicate to the appropriate server (e.g. localhost).
NOTE The other important file here is the mobile.properties file. This is where you
can enable a series of settings. Modifications to these property files ultimately
get included in the .jar which is the file that gets put on the mobile device in
order to run the application. What this means is that these properties must be
set up correctly; otherwise the mobile user won't be able to log in. The
properties settings you need to consider are maximo.mobile.hostname,
maximo.mobile.port, and maximo.mobile.ssl.
If you are packaging more the one application you will need to run the
packagemobile command by following these steps:
From a command prompt, navigate to the
<maximo_root>\mobiledeployment\packagemobile directory and run the
following command:
packagemobi l e
Presuming everything works fine, you should get a 'BUILD SUCCESSFUL'
message.
Executing this command creates a series of directories within the Maximo >
MobileDeployment folder, including one directory for each language you are
supporting. Within these folders you will find your .jar file (one for each
language) and it is these .jar files that will need to be transferred to the mobile
device(s).
If you are packaging just a single application you will need to run the
packagemobileapp command by following these steps:
Deployment
Implementing Your Configuration Changes 2-3
From a command prompt, navigate to the
<maximo_root>\mobiledeployment\packagemobile directory and run the
following command:
packagemobi l eapp <app name>
e.g. packagemobileapp mobilewo
Presuming everything works fine, you should get a 'BUILD SUCCESSFUL'
message.
Deployment
In order to run Mobile Work Manager or Mobile Inventory Manager you must
have IBM WebSphere

Everyplace

6.0 Environment / J9 Java Virtual

Machine (JVM) installed on your Microsoft

Powered Pocket PC device. There

are several ways to install and distribute files onto a mobile device, including
third-party software distribution tools and Microsoft ActiveSync

. The steps
outlined below assume you are using ActiveSync, but this does not mean that
other more efficient tools and/or processes do not exist. To transfer files, follow
these steps:
1 Connect your device to the cradle using ActiveSync 4.x.
2 Initiate a connection/partnership with your device.
3 Make sure the IBM WebSphere Everyplace 6.0 Environment / J9 Java
Virtual Machine (JVM) is installed in the device's <RootDirectory>/
Program Files folder. If it is not, be sure to copy and paste the entire J9
folder here.
If you already have .jars on the device you must follow these steps prior to
installing the new .jar file(s) on your device.
1 Connect your device to the cradle.
2 Initiate an ActiveSync connection/partnership with your device.
3 Via ActiveSync, navigate to the maximo/db folder on the device.
4 Delete all files in this directory.
Finally, you must take the .jar files that were created from the packaging
process and put them on your device.
1 Connect your device to the cradle.
2 Initiate an ActiveSync connection/partnership with your device.
3 Via ActiveSync, navigate to the maximo/lib folder on the device
4 Paste the .jar file(s) into the maximo/lib folder.
Deployment
2-4 IBM Maximo Mobile Applications: Configuration Guide
Copyright IBM Corp. 2006 Notices-1
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 user's
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:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, 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
Notices-2 IBM Maximo Mobile Applications: Configuration Guide
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.
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:
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 document 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 IBM's 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
AIX, IBM, IBM Corporation, the IBM logo, Tivoli, and WebSphere are
registered trademarks of the International Business Machines Corporation in
the United States, other countries, or both.
Intel, the Intel logo, and Pentium are registered trademarks of the Intel
Corporation in the United States, other countries, or both.
Microsoft, Windows, and Internet Explorer are registered trademarks of
Microsoft Corporation in the United States, other countries, or both.
Notices-3
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or
both.
Sun, Sun Microsystems, the Sun logo, and Solaris are trademarks of Sun
Microsystems, Inc.
Linux is a trademark of Linus Torvalds in the United States, other countries,
or both.
UNIX is a registered trademark of The Open Group in the United States and
other countries.
Other company, product, and service names may be trademarks or service
marks of others.
Notices-4 IBM Maximo Mobile Applications: Configuration Guide
Copyright IBM Corp. 2006 Index-1
A
application server
security 1-7
applications, See mobile applications
C
clocks
multiple or single on work orders 1-5
cloning mobile applications 1-6
columns in table windows
adding/removing 1-3
cron tasks
for changing frequency of server-side queue polling 1-5
for maintaining lock on mobile transactions 1-5
for removing transaction data after specified number of days
1-5
customer support i-v
D
data groups
adding/removing in Security Groups (Mobile) 1-6
F
fields
adding/removing 1-1
changing labels 1-2
changing length 1-2
limiting number of characters in 1-2
making required 1-3
requiring domain validation 1-4
I
importall command 2-1
importmetadata command 2-1
L
LDAP
configuring for 1-7
M
mobile applications
cloning 1-6
deployment 2-3
importing changes 2-1
packaging bundles to run on mobile devices 2-2
mobile.properties file 2-1, 2-2
O
online support i-v
P
packagemobile command 2-2
packagemobileapp command 2-2
packaging application bundles to run on mobile devices 2-2
Q
queries
adjusting in mobile screen XML definitions 1-6
S
security
application server 1-7
Security Groups (Mobile) application
adding/removing data groups 1-6
server-side queue polling
changing frequency 1-5
support, online i-v
Index
Index
Index-2 IBM Maximo Mobile Applications: Configuration Guide
T
table windows
adding/removing columns 1-3
configuring 1-3
transactions
frequency of server-side queue polling 1-5
maintaining lock 1-5
removing data after specified number of days of inactivity
1-5
X
XML definitions
adjusting hard coded queries in 1-6