with IBM Corp....an integrated development envir onment. Mobile devices The Maximo Anywher e mobile...

IBM Maximo AnywhereVersion 7 Release 6

Planning, installation, and deployment

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” on page 65.

This edition applies to version 7, release 6, modification 3 of IBM Maximo Anywhere and to all subsequent releasesand modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2013, 2017.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Planning to deploy MaximoAnywhere . . . . . . . . . . . . . . 1System requirements for Maximo Anywhere,MobileFirst Server, and MobileFirst Studio . . . . 1System architecture and components . . . . . . 3Deployment topologies . . . . . . . . . . . 6

Development environment. . . . . . . . . 7Single-server deployment of Maximo Anywhereand MobileFirst Server . . . . . . . . . . 8Multiple-server deployment of Maximo Anywhereand MobileFirst Server . . . . . . . . . . 9

Installation overview . . . . . . . . . . . 12Installation planning worksheet . . . . . . . 14Installation checklist for Maximo Anywhere . . . 15

Chapter 2. Installing the MaximoAnywhere components. . . . . . . . 19Installing the Maximo Asset Management requiredcomponents . . . . . . . . . . . . . . 19

Automatically updating the database andbuilding and deploying the EAR file . . . . . 20Manually updating the database and buildingand deploying the EAR file . . . . . . . . 20

Updating the database and building the EARfile . . . . . . . . . . . . . . . 20Deploying the EAR file on WebSphereApplication Server . . . . . . . . . . 20Deploying the EAR file on WebLogic Server 21

Installing MobileFirst Server . . . . . . . . . 21Installing MobileFirst Server by using theinstallation program . . . . . . . . . . 21Installing the MobileFirst Server AdministrationServices . . . . . . . . . . . . . . 23Setting the Java heap size on the JVM forWebSphere Application Server or WebSphereApplication Server Liberty . . . . . . . . 24

Preparing the Maximo Anywhere environment . . 24Installing the Android development tools . . . 25Installing the iOS development tools . . . . . 25Installing the Windows development tools . . . 27

Installing Maximo Anywhere . . . . . . . . 28Creating a MobileFirst runtime environment . . . 29Installing an integrated development environment 30Silent mode: Installing Maximo Anywhere . . . . 32

Recording a response file for silent installation . 32Installing the required components in silentmode . . . . . . . . . . . . . . . 32Installing Installation Manager in silent mode . . 33

Parameters for silent mode installation . . . 33Installing Maximo Anywhere in silent mode . . 34

Setting up Maximo Asset Management for MaximoAnywhere . . . . . . . . . . . . . . . 35

Adding users to the Maximo Anywhere securitygroups . . . . . . . . . . . . . . . 35

Maximo Anywhere security groups in MaximoAsset Management . . . . . . . . . . . 35Enabling Maximo Asset Managementapplications for maps and labor reporting . . . 37Maximo Asset Management system options thataffect mobile apps . . . . . . . . . . . 37

Chapter 3. Updating the MaximoAnywhere components. . . . . . . . 39Updating the required components . . . . . . 39Updating MobileFirst Server. . . . . . . . . 39Updating the Maximo Anywhere build environment 40Updating the MaximoAnywhere project inMobileFirst Studio . . . . . . . . . . . . 41What's new in application definitions in 7.6.3 . . . 42

Chapter 4. Installing help locally. . . . 43Installing help . . . . . . . . . . . . . 43IBM Knowledge Center configuration . . . . . 44Help components . . . . . . . . . . . . 45Maximo Asset Management documentation library 46

Chapter 5. Building and deployingMaximo Anywhere apps . . . . . . . 49Application deployment process for MaximoAnywhere apps . . . . . . . . . . . . . 49Deploying Maximo Anywhere apps to MobileFirstServer . . . . . . . . . . . . . . . . 51

Deploying apps from the command line toWebSphere Application Server . . . . . . . 51Deploying apps by using MobileFirst Studio . . 53Properties files . . . . . . . . . . . . 54Maximo Anywhere directory structure . . . . 56Configuring MySQL Database . . . . . . . 57

Adding digital signatures to Maximo Anywhereapps . . . . . . . . . . . . . . . . . 57Deploying apps to a secure server . . . . . . . 58Installing Maximo Anywhere apps on mobiledevices . . . . . . . . . . . . . . . . 58

Installing Maximo Anywhere apps on Windowsdevices . . . . . . . . . . . . . . . 59

Testing apps . . . . . . . . . . . . . . 60Setting up the Android emulator . . . . . . 61

Chapter 6. Uninstalling MaximoAnywhere, MobileFirst Server, andMobileFirst Studio . . . . . . . . . . 63

Notices . . . . . . . . . . . . . . 65Trademarks . . . . . . . . . . . . . . 67Terms and conditions for product documentation. . 67IBM Online Privacy Statement . . . . . . . . 68

© Copyright IBM Corp. 2013, 2017 iii

iv Planning, installation, and deployment

Chapter 1. Planning to deploy Maximo Anywhere

IBM® Maximo Anywhere must be deployed with selected IBM MobileFirstPlatform Foundation components to an enterprise system that includes OpenServices for Lifecycle Collaboration (OSLC) provider capabilities.

The installation of Maximo Anywhere involves deploying components that arespecific to Maximo Anywhere and other components that are specific toMobileFirst.

During the Maximo Anywhere installation, you must perform tasks that areoutlined in the IBM MobileFirst Platform Foundation version 7.1.0 IBM KnowledgeCenter. Before you install Maximo Anywhere, read the installation and deploymentinformation.

To access the documentation, you must have an internet connection.

System requirements for Maximo Anywhere, MobileFirst Server, andMobileFirst Studio

Your environment must meet all of the software and hardware requirements forMaximo Anywhere, MobileFirst Server, and MobileFirst Studio.

A complete list of hardware and software requirements for your product isavailable in the Maximo Anywhere information in the System Requirementssection of the Maximo® Asset Management wiki.

The MobileFirst system requirements are available in the IBM Support Portal.

You must have administrative user rights on all the computers that are used forthe Maximo Anywhere 7.6.3 installation.

Enterprise system

Tivoli®'s process automation engine is the enterprise platform for productssuch as IBM Maximo Asset Management, IBM TRIRIGA® ApplicationPlatform, and Maximo industry solutions. The process automation engineand the supporting middleware together comprise the enterprise system.

Maximo Anywhere 7.6.3 must be installed with Maximo AssetManagement version 7.6.2 or later.

Maximo Integration Framework is also required. If Maximo AssetManagement 7.6.2 is installed, the correct version of the IntegrationFramework might already be deployed. The installation program detectsthe required components if they are already installed.

The Maximo Integration Framework component includes OSLC objectstructures that the enterprise system requires to support MaximoAnywhere. With OSLC integration, the enterprise applications can sharedata with Maximo Anywhere.

You can verify that the required components are installed by logging intoMaximo Asset Management and selecting Help > System Information.

© Copyright IBM Corp. 2013, 2017 1

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/wl_welcome.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/wl_welcome.html

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Maximo%20Anywhere%20system%20requirements

http://www-01.ibm.com/support/docview.wss?uid=swg27024838

Maximo Anywhere supports IBM Maximo Spatial Asset Management7.5.0.1 or later versions to provide positioning information that determinesthe location of a work order on a map. Maximo Spatial Asset Managementis an optional component. If Maximo Spatial Asset Management is not inyour environment, positioning information is obtained by using non-linkedobjects.

Maximo Anywhere version 7.6.3

To configure, build, and deploy the Maximo Anywhere mobile apps, thefollowing prerequisite software must be installed.v The Oracle Java Development Kit (JDK) is a prerequisite for Android

and iOS development, and its subcomponent, the Java RuntimeEnvironment (JRE), is required to run MobileFirst Studio.

v The Android SDK is required to build the Maximo Anywhere apps forAndroid mobile devices.

v To install mobile apps on iOS devices, a set of Apple-registered accountsis required so that you can build the iOS apps in your environment. Ifyou are installing Maximo Anywhere on a Mac OS X computer, youmust install the iOS development tools first.

v Xcode IDE is required to build the Maximo Anywhere apps so that theycan be deployed on iOS mobile devices.

v Microsoft Visual Studio is required to build Maximo Anywhere apps sothat they can be deployed on Windows mobile devices.

v To set up an integrated development environment, you must installEclipse IDE for Java™ EE Developers and MobileFirst Studio.

v To preview the deployed applications in the MobileFirst Studio mobilebrowser simulater, you must install Google Chrome.

IBM MobileFirst® Platform Server 7.1.0

MobileFirst Server is required to deploy Maximo Anywhere in aproduction environment. Ensure that you have installed the latest interimfix.

You must deploy MobileFirst Server on a Windows, Linux, or AIX®

computer.

MobileFirst Server must be deployed to an application server. Theapplication server can be configured with a specific profile for MobileFirstServer.

If you plan to use Application Center to distribute Maximo Anywhere appsto iOS devices, you must configure the MobileFirst Server to listen throughSSL.

In a production environment, MobileFirst Server requires aproduction-grade database instance. You can configure an existing databaseserver for MobileFirst Server by creating a database instance or databaseschemas.

Application servers Databases

v IBM WebSphere® Application ServerLiberty

v IBM WebSphere Application Server

v Apache Tomcat

v IBM DB2®

v Oracle Database

v MySQL Database

2 Planning, installation, and deployment

For compatible products and versions, see the IBM MobileFirst PlatformFoundation 7.1.0 detailed system requirements.

Restrictions:

v MobileFirst Server is not supported on Mac OS X computers.v MobileFirst Server does not support Oracle WebLogic Server. If your enterprise

environment runs WebLogic Server, install IBM WebSphere Application ServerLiberty or Apache Tomcat to host MobileFirst Server.

v MobileFirst Server does not support Microsoft SQL Server. If your enterpriseenvironment runs SQL Server as the database, you must use MySQL Database,Oracle Databaseor IBM Db2 as the database platform for MobileFirst Server.

IBM MobileFirst Platform StudioYou must install Oracle JDK before you install MobileFirst Studio. TheOracle JDK includes the Java Runtime Environment (JRE), whichMobileFirst Studio requires to build the Maximo Anywhere applications.

To configure the mobile apps, install the required development tools incombination with MobileFirst Studio. For more information, see Installingan integrated development environment.

Mobile devices

The Maximo Anywhere mobile apps can be deployed to Android, iOS, orWindows mobile devices. In a development environment, you can also testthe apps in the MobileFirst Studio mobile browser simulator, the AndroidEmulator, or the iOS Simulator.

For a full list of operating systems and supported screen sizes, see theMaximo Anywhere system requirements.

System architecture and componentsMaximo Anywhere and MobileFirst form a mobile application platform thatintegrates with the Maximo Asset Management enterprise system. MaximoAnywhere provides the content that is required to build mobile apps for MaximoAsset Management. The MobileFirst components function as middleware byenabling integration with the enterprise system and by supporting the deploymentof apps to mobile devices.

Maximo Integration Framework is included in the Maximo Asset Management7.6.2 environment. This framework is required to enable the integration betweenMaximo Asset Management and external applications. The Integration Frameworkincludes the OSLC capabilities and service providers that are used by the MaximoAnywhere apps to retrieve and process enterprise data.

OSLC is installed on the Maximo Asset Management administrative workstation aspart of the Maximo Anywhere package.

The following figure shows the system architecture of Maximo Anywhere andhighlights the relationship with key components in Maximo Asset Managementand MobileFirst.

Table 1. Supported application servers and databases.

Chapter 1. Planning to deploy Maximo Anywhere 3




Application Center

MobileFirst server

Mobile device

Maximo Anywhere

app

Local data store

Build EAR file

Native appsConsole

Login

module

Adapter

Maximo enterprise

application

OSLC service

provider

DataInstall

Runtime environment

Build environment

Maximo Anywhere build server

Adapter

Maximo Anywhere project

App

Data

Build and deploy

Maximo

administrative

workstation

Maximo database

MobileFirst

database

MobileFirst

The following required components must be deployed to the Maximo AssetManagement environment to support the Maximo Anywhere apps:

Maximo Integration FrameworkThis framework is required to enable the integration between MaximoAsset Management and external applications. The Integration Frameworkincludes the OSLC capabilities and service providers that are used by theMaximo Anywhere apps to retrieve and process enterprise data. MaximoAsset Management 7.6.2 environments include the Integration Framework.

IBM OSLC Content package 7.6.0OSLC resources define the metadata for business objects of OSLC serviceproviders. The OSLC resources are used by the mobile apps to retrieve andprocess application data from the service providers in Maximo AssetManagement.

Maximo Anywhere Enablement 7.6.3The enablement package includes application files, license enablement files,and cron task automation. The enablement package also includes theAnywhere Administration application, which is deployed as part of theMaximoAnywhere project.

Figure 1. Maximo Anywhere system architecture and components


The following components are deployed when you implement Maximo Anywhere:

IBM Maximo AnywhereA collection of resources that are required for integration and deploymenton the MobileFirst platform. These resources include aMobileFirst-compatible project and an OSLC adapter. The OSLC adaptermanages communications between MobileFirst Server and the providerapplication, Maximo Asset Management. Before run time, the MaximoAnywhere project WAR, the applications, and the OSLC adapter must bedeployed to MobileFirst Server. The mobile apps can be configured, tested,and deployed to an emulator or a mobile device.

IBM MobileFirst Platform Server for MobileFirst Consumer EditionA runtime container for the OSLC adapter and server-based applicationcomponents. MobileFirst Server includes an administrative console and anapp store for publishing mobile apps within the organization. MobileFirstServer must be deployed to an application server. The same applicationserver can be used to deploy both Maximo Asset Management andMobileFirst Server.

Application CenterThe Application Center is an enterprise app store that you can use fordeploying the Maximo Anywhere apps to mobile devices in yourorganization. Application Center is automatically installed with MobileFirstServer. Application Center is composed of a server component, arepository, the Application Center console, and a mobile client app.v Server component:

The server component is a Java Enterprise application that must bedeployed in a web application server, such as WebSphere ApplicationServer.The server component consists of an administration console and amobile client. The mobile client installs the apps that are available to theclient component.Several services compose the Application Center server component, suchas a service that lists the available apps, and a service that delivers theapp binary files to the mobile device.

v Repository:The repository stores the apps that can be installed on mobile devices.The repository is a database that also stores information, such asfeedback about the apps, and the amount of storage that an app uses.

v Application Center console:The Application Center console is a web application that is used tomanage the repository. You must have system administrator privileges toaccess the Application Center console.

v Mobile client:The mobile client runs on mobile devices and is used to install the appsthat reside in the repository.

IBM MobileFirst Platform Studio for MobileFirst Consumer Edition (Optional)An Eclipse-based integrated development environment that can bedeployed with Maximo Anywhere.

MobileFirst Studio is installed as an Eclipse add-on by using a P2 Eclipseupdate. MobileFirst Studio is used to configure and test the MaximoAnywhere apps, and to manage the build and deployment process.


The following items are not included in the Maximo Anywhere product license.However, you can deploy these items to the Maximo Anywhere environment toextend and complement the capabilities that are available in the product itself.

Map servicesThe map view uses positioning data that is provided by Maximo AssetManagement. Maximo Asset Management can be configured to obtain thispositioning data from ArcGIS, an external geographic information system.You can also configure the map view to show a route and directionsbetween work order locations. To support this configuration, you musteither have permissions from the map service provider, Esri or you mustinstall and obtain a license for IBM Maximo Spatial Asset Management.

Mobile Device ManagementYou can deploy IBM MaaS360 Mobile Device Management with MaximoAnywhere to complement the mobile app management capabilities thatMobileFirst provides. IBM MaaS360 Mobile Device Management providesmobile device management capabilities, including security management,for your mobile organization.

Deployment topologiesA development environment is created by installing Maximo Anywhere andMobileFirst Studio on the same computer. A production environment is created byinstalling Maximo Anywhere and MobileFirst Server in a single-server ormultiple-server deployment.

You use a development environment to configure and test the Maximo Anywheremobile apps before they are deployed to the production server. A test instance or adevelopment instance of Maximo Asset Management is required, either on thesame computer or on a remote computer.

You can set up a pre-production test environment or a small-scale productionenvironment on a single server. A single-server deployment features MaximoAnywhere and MobileFirst Server installed on the same computer. Apre-production instance of Maximo Asset Management is also required, either onthe same computer or on a remote computer. The pre-production instance ofMaximo Asset Management must closely match the production environment sothat the application configurations can be tested before you move to a productionenvironment.

For medium and large enterprises, creating a production environment involvesinstalling the components on more than one computer. MobileFirst Server mustfirst be deployed to an application server. A production instance of Maximo AssetManagement must be available on a different computer than the MaximoAnywhere and MobileFirst components.

MobileFirst Studio is an optional integrated development environment. If you wantto use MobileFirst Studio to test, configure, and build the Maximo Anywhereapplications, you must install it on the same computer as the Maximo Anywherecomponent.

The Maximo Anywhere computer functions as a build server from which theapplication build and deployment processes are run.


Cluster environments

To introduce high availability and scalability to your Maximo Anywheredeployment, you can set up a MobileFirst Server cluster environment. TheMobileFirst cluster can be integrated with a basic or advanced enterprise systemtopology.

You can create a cluster either by setting up multiple application server hostcomputers or by using multiple Java virtual machines (JVMs) that share theMobileFirst Server database instance. Each node of a MobileFirst Server clusterrequires a separate copy of the MobileFirst web application archive (WAR) projectfile.

If you plan to set up a clustered environment, configure the cluster before youinstall MobileFirst Server and Maximo Anywhere.

Hardware-based or software-based load balancers regulate the data activity acrossmultiple web servers. For more information, see the clustering information in theIBM MobileFirst Platform Foundation 7.1.0 IBM Knowledge Center.Related information:Optimizing system performance

Clustering of MobileFirst Server

Development environmentA development environment can be used to configure, test, and build the MaximoAnywhere mobile apps before they are deployed to a production environment.

To create a development environment, you install MobileFirst Studio and MaximoAnywhere on a single computer. A test instance or a development instance ofMaximo Asset Management is also required, either on the same computer or on aremote computer.

Maximo Asset Management

MobileFirst Studio

Maximo Anywhere

Before you install MobileFirst Studio and Maximo Anywhere, you must install acollection of required components on the Maximo Asset Management computer.

MobileFirst Studio is an Eclipse-based integrated development environment. Youmust install MobileFirst Studio within an existing Eclipse client. Update yourEclipse environment by installing the development tools for the Android or iOSmobile platform.

Example: Creating an Android development environment

Dale is a system administrator who is responsible for implementing MaximoAnywhere in his enterprise. He wants to test and configure the Maximo Anywhereapps before he deploys them to the production environment. To do this, hedesignates one computer as a development environment.

Figure 2. A Maximo Anywhere development environment.


http://www-01.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mbs.doc/gp_sysperf/c_ctr_improve_sysperf.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.deploy.doc/admin/c_clustering.html

Before Dale begins, he prepares the enterprise system to support MaximoAnywhere.

He creates a test instance or a development instance of Maximo Asset Managementand backs up the system.

On the computer where Maximo Asset Management is installed, he installs theMaximo Asset Management required components.

If using Maximo Asset Management 7.6.2, he runs the Configuration Tool toupdate the database and rebuild and redeploy the Maximo EAR files.

On a designated development computer, Dale installs Oracle JDK, Android SDK,and Eclipse. He then installs MobileFirst Studio as a P2 Eclipse update.

Dale starts the launchpad and installs Maximo Anywhere. During the installation,he selects Embedded Server within MobileFirst Studio.

When the installation is complete, Dale can configure and test the MaximoAnywhere mobile apps. He can build the apps and deploy them to the AndroidEmulator.

Single-server deployment of Maximo Anywhere andMobileFirst Server

For small enterprises, a single-server deployment can be used for productionpurposes. Larger enterprises can use a single-server deployment as apre-production test environment.

To create a single-server deployment, you install MobileFirst Server and MaximoAnywhere on a single computer. A test instance or a production instance ofMaximo Asset Management is also required, either on the same computer or on aremote computer.

Maximo Asset Management

MobileFirst Server

Maximo Anywhere

You can configure an instance of WebSphere Application Server, WebSphereApplication Server Liberty, or Apache Tomcat for use with MobileFirst Server.

You can also configure an existing production database, such as Db2, OracleDatabase, or MySQL Database.

To configure the Maximo Anywhere applications for your organization, youmodify the properties files and the application definitions. You can build, deploy,and preview the mobile apps in the MobileFirst Operations Console. You can thendeploy the apps to the Application Center where mobile workers can downloadthem to a mobile device.

Figure 3. A single-server deployment of Maximo Anywhere and MobileFirst Server.


Example: Creating a single-server deployment

Ian is a system administrator who is responsible for implementing MaximoAnywhere in a small enterprise. He wants to create a small-scale productionenvironment.

Ian performs any necessary backup of the system and sets up a productioninstance of Maximo Asset Management.

He creates a production database instance on the Maximo database server.

He installs the required components on the computer where Maximo AssetManagement is installed.


On the same computer, he installs MobileFirst Server and uses the MobileFirstServer Configuration Tool to install the MobileFirst Server Administration Services.

Ian installs Maximo Anywhere and again uses the MobileFirst ServerConfiguration Tool to install the MobileFirst runtime environment.

When the configuration is complete, Ian can download the Maximo Anywhereapps from the Application Center and install them on a mobile device.

Multiple-server deployment of Maximo Anywhere andMobileFirst Server

A multiple-server deployment is suitable for medium and large enterprises and isdeployed by installing Maximo Anywhere and MobileFirst Server on separatecomputers. A production instance of Maximo Asset Management on a remotecomputer is also required.

If you use WebSphere Application Server as the enterprise application server, youcan create a new profile for MobileFirst Server. You must also create a databaseinstance or multiple database schemas on the enterprise database server.

The Maximo Anywhere build server is used to configure, build, and deploy theapps to MobileFirst Server. Mobile workers can then download the apps to theirmobile devices from the Application Center.

You can create a MobileFirst Server cluster and integrate it with a basic or anadvanced enterprise system topology. An enterprise system topology contains anOSLC provider cluster, which can consist of either multiple WebSphere ApplicationServer instances or multiple Oracle WebLogic Server instances.


Maximo Anywhere

apps

Firewall

Maximo Anywhere

build server

MobileFirst web server

load balancer

MobileFirst server

cluster

Application server

MobileFirst database

HTTP/HTTPS

HTTP/HTTPS

Web server load

balancer

OSLC provider

cluster

Application server

Maximo database

Enterprise system environment

The MobileFirst Server cluster supports only multiple instances of WebSphereApplication Server.

In an advanced enterprise system topology, you can isolate processes that requirethe use of an application server into separate clusters. For example, you can isolatethe user interface applications into one cluster and isolate cron tasks and reportingprocesses into other clusters.

The MobileFirst Server cluster and the OSLC provider cluster can be integrated inan advanced enterprise system topology.

Figure 4. A Maximo Anywhere multiple-server deployment (basic topology).


Maximo

Anywhere

apps

Firewall

Maximo Anywhere

build server

MobileFirst

web server load

balancer

MobileFirst

server cluster

Application

server

HTTP/HTTPS

HTTP/HTTPSWeb server load

balancer

Enterprise system

environment

MobileFirst

database

Maximo

database

Reporting

database

OSLC provider

cluster

Application

server

User interface

cluster

Application

server

Integration

cluster

Application

server

Cron

cluster

Application

server

Reporting

cluster

Application

server

HTTP/HTTPS

Maximo Asset

Management

applications

Example: Creating a multiple-server deployment

Ian is a system administrator who is responsible for implementing MaximoAnywhere in a production environment.

Before he begins, he creates a database instance or multiple database schemas onthe production database server. MobileFirst Server can be configured to share theexisting database server with the enterprise system.

Ian installs or identifies an application server for use with MobileFirst Server. Forexample, he installs WebSphere Application Server Liberty or creates a newinstance of WebSphere Application Server.

On the computer where Maximo Asset Management is installed, Ian starts thelaunchpad and installs the Maximo Asset Management required components.

Figure 5. A Maximo Anywhere multiple-server deployment (advanced topology).



On a designated host server computer, Ian starts the launchpad and installsMobileFirst Server. He starts the MobileFirst Server Configuration Tool and installsthe MobileFirst Server Administration Services.

On a separate computer, he starts the launchpad and installs Maximo Anywhere.During the installation, Ian specifies the host name of the MobileFirst Servercomputer.

When the installation is complete, Ian copies the MaximoAnywhere.war file from theMaximo Anywhere computer to the MobileFirst Server computer.

On the MobileFirst Server computer, Ian starts the MobileFirst ServerConfiguration Tool and adds a MobileFirst runtime environment.

When the configuration is complete, Ian can download the Maximo Anywhereapps from the Application Center and install them on a mobile device.Related tasks:Configuring the application serverRelated information:

Typical topologies of a MobileFirst instance

Clustering with MobileFirst Server

Installation overviewThe Maximo Anywhere installation involves preparing target computers andexisting middleware for installation, and installing key components for MaximoAnywhere and MobileFirst Server.

The Maximo Anywhere launchpad is a centralized interface where you can startthe installation programs. Maximo Anywhere and MobileFirst Server are installedby using IBM Installation Manager. Installation Manager is a tool that guides youthrough the installation of IBM products.

Before you install the product, you must extend the enterprise system to supportMaximo Anywhere.

Ensure that Maximo Asset Management 7.6.2 or later is installed.

On the Maximo Asset Management administrative workstation, start the MaximoAnywhere launchpad and install the required components to extend the enterprisesystem for Maximo Anywhere.

Before you install Maximo Anywhere and MobileFirst Server, ensure that yourenvironment contains an application server and a database instance.

If your enterprise environment runs IBM WebSphere Application Server, you cancreate a profile for MobileFirst Server.

A cluster is created by implementing multiple host servers or by configuringmultiple JVMs. If you want to set up a MobileFirst cluster, do so before you installMobileFirst Server and Maximo Anywhere.


http://www.ibm.com/support/knowledgecenter/SSLKT6_7.5.0.5/com.ibm.mbs.doc/gp_highavail/t_ctr_configure_app_server.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/admin/c_typical_topology_of_an_ibm_wor.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.deploy.doc/admin/c_clustering.html

You must prepare the Maximo Anywhere environment by installing developmenttools. MobileFirst Studio is an optional component and can be installed as part ofthe Eclipse integrated development environment (IDE) workbench. For Androidapp development, the Android SDK and the Oracle JDK are both required to buildthe mobile apps. For iOS app development, XCode and Apple developer profilesare required on a Mac OS X computer. For Windows app development, MicrosoftVisual Studio is required to build the mobile apps.

Administrative user rights are required to install all of the components that aredelivered with Maximo Anywhere version 7.6.3. You must have root userauthorization for UNIX and Linux systems.

Required components

Maximo Asset Management requires a set of components to be deployed beforeMaximo Anywhere is installed. The Maximo Asset Management requiredcomponents include OSLC object structures and licenses to enable a set of extraapplications in Maximo Asset Management. Maximo Integration Framework mustalso be installed. The Service Address application is used with the map feature andthe Crews and Crew Types applications are used for labor reporting. TheAnywhere Administration application allows you to administer the MaximoAnywhere mobile apps from one central location.

Maximo Anywhere, MobileFirst Server, and MobileFirst Studio

Before you install Maximo Anywhere and the MobileFirst components, you mustinstall prerequisite software and configure the database server.

In most production environments, MobileFirst Server is installed on a differentcomputer than Maximo Anywhere. You must deploy MobileFirst Server to anapplication server before you install Maximo Anywhere. You can installMobileFirst Studio and Maximo Anywhere on the same target computer andstreamline the configuration and testing of the mobile apps before they aredeployed.

Silent installation

A silent installation is useful for installing Maximo Anywhere and MobileFirstServer in the following scenarios:v You are installing the components on a group of computers that are configured

in the same way.v You are installing the components on a production server that is behind a

firewall. The use of remote desktop access software can be restricted byfirewalls, so system administrators can be prevented from using the launchpadto install the components.

v You are installing the components on a computer that cannot display an Eclipseuser interface.

Silent installation eliminates the need to use the graphical user interface (GUI) ofthe installation program to collect installation data. You can run a silent installationof Maximo Anywhere, MobileFirst Server, and Installation Manager from acommand line.


Silent installations that are conducted with Installation Manager are defined by anXML response file. The response file can be used to install, update, and uninstallproducts.

You can use the Installation Manager GUI to record installation preferences andactions in a response file. By default, a response file is not recorded, so you mustenable the recording by setting the record environment variable to true before youstart the launchpad.

Installation planning worksheetUse the planning worksheet to record the information that you need during theinstallation process, such as system settings, properties, and user names.

Variable Default value Example value Your value

Maximo Anywhereinstallation directory

Windows: C:\IBM\Anywhere

UNIX and Linux:opt/ibm/Anywhere

MobileFirst ServerAdministration protocol

On Windows: http

On Mac OS X: https

MobileFirst ServerAdministration host name

hostname.yourdomain.com or1.234.567.89 or localhost

MobileFirst ServerAdministration port(Stand-alone server)

9080

MobileFirst ServerAdministration port(Embedded server)

10080

MobileFirst ServerAdministration context root

wladmin

MobileFirst ServerAdministration runtimecontext root

MaximoAnywhere

MobileFirst ServerAdministration user name

MobileFirst ServerAdministration password

Application Center protocol On Windows: http

On Mac OS X: https

Application Center hostname

hostname.yourdomain.com or1.234.567.89 or localhost

Application Center port On Windows, UNIX, andLinux: 9080

On Mac OS X: none

Application Center contextroot

applicationcenter

Application Center username

appcenteradmin


Variable Default value Example value Your value

Application Centerpassword

Android platform directory C:\Users\Administrator\Downloads\android-sdk_r22.6.2-windows\android-sdk-windows\platforms\android-19

Oracle JDK directory Windows: C:\ProgramFiles\Java

UNIX and Linux:/usr/java

Maximo Server protocol http

Maximo Server host name hostname.yourdomain.com or1.234.567.89 or localhost

Maximo Server port 9080 or 80

Maximo Server context root maximo

Installation checklist for Maximo AnywhereYou can use the checklist to ensure that all installation steps completedsuccessfully. Print this topic and check each task as you complete it. To access thelinks, you must have an internet connection.

Preparing for installation

Done Task

Ensure that your environment meets all ofthe software and hardware requirements forMaximo Anywhere and IBM MobileFirstPlatform Foundation.

To build mobile apps for Windows devices,you must use a Windows computer. To buildmobile apps for iOS devices, you must use aMac OS X computer. Prepare your buildenvironment by installing the requireddevelopment tools for your chosen platform.

Print the installation planning worksheetand use it during the installation.

Installing IBM Maximo Anywhere

Done Task

On the computer where Maximo AssetManagement is installed, download theMaximo Anywhere product software fromIBM® Passport Advantage®.

Table 1. Variables and values for system settings, properties, and user names.

Table 1. Planning checklist.


Done Task

Install the Maximo Asset Managementrequired components.

Create or identify a database instance to usewith MobileFirst Server.

Install or identify an application server touse with MobileFirst Server.

On a designated server computer, installMobileFirst Server.

Install the MobileFirst Server AdministrationServices by using the MobileFirst ServerConfiguration Tool.

On the build computer, prepare the MaximoAnywhere build environment.

On the build computer, install MaximoAnywhere.

On the MobileFirst Server computer, add aMobileFirst runtime environment by usingthe configuration tool.

On the computer where Maximo Anywhereis installed, run the build all command. Ifyour computer is a Windows system, use thebuild.cmd file. If your computer is a UNIXor Linux system, use the build.sh file. Thisstep generates the distributable files for theMaximo Anywhere project and deploysthem to MobileFirst Server.

Install the Maximo Anywhere apps onmobile devices.

Optional: On the build computer, to createan integrated development environment,install MobileFirst Studio.

Configuring IBM Maximo Anywhere and Maximo AssetManagement

Done Task

Add users to the Maximo Anywheresecurity groups.

Enable Maximo Asset Managementapplications for maps and labor reporting.

Table 2. Installation checklist.


Done Task

Set up Maximo Asset Management toinclude the following data:

v Ensure that your user has an associatedlabor code.

v Ensure that your user has authorization toat least his own labor code.

v Ensure that your user has a default insertsite defined.

v Ensure that your user has a default timezone defined.

Verifying the installation

Done Task

Test the Maximo Anywhere apps on mobiledevices.

Table 3. Configuration checklist.

Table 4. Verification checklist.


Chapter 2. Installing the Maximo Anywhere components

After you plan your environment, you install Maximo Anywhere and MobileFirston one or more computers.

Before you begin

Ensure that Maximo Asset Management 7.6.2 or later is installed.

Download the Maximo Anywhere product software from IBM PassportAdvantage®.

About this task

Maximo Anywhere 7.6.3 includes the following compressed files:v Max_Anywhere_V763.zip

v MaxAny_763_MobileFirst_71.zip

You must extract the compressed files on multiple computers. The contents of theInstall folder in the MaxAny_763_MobileFirst_71.zip file must always be copiedinto the Install folder of the Max_Anywhere_V763 folder on the target system.

Installing the Maximo Asset Management required componentsYou extend Maximo Asset Management with components that include OSLC objectstructures and licenses that enable a set of applications.

About this task

Running the launchpad executable file as an administrator ensures that you havethe permissions to update the existing installation directory.

Procedure1. On the computer where Maximo Asset Management is installed, extract the

Max_Anywhere_V763.zip for your version to the Maximo Asset Managementinstallation directory.

2. Start the launchpad by right-clicking the launchpad file and selecting Run asadministrator. If your computer is a 64-bit system, use the launchpad64 file. Ifyour computer is a UNIX or Linux system, use the launchpad.sh file.

3. On the Install IBM Maximo Asset Management Required Components pane,click Install.

4. Complete the installation wizard.5. Deploy the product by updating the database and building and deploying the

Maximo EAR file. Allow the IBM Tivoli process automation engineconfiguration utility to start and select Update Database and Build andDeploy Application EAR Files to complete the configuration.

6. Verify that the required components are installed by logging in to MaximoAsset Management and selecting Help > System Information. Ensure that IBMMaximo Integration Framework is listed as one of the installed components.


What to do next

If you plan to install Maximo Anywhere and MobileFirst Server on differentcomputers, copy the installation images to the target computers.

Automatically updating the database and building anddeploying the EAR file

If you deferred the configuration step during installation, you can use theconfiguration wizard to deploy the product.

Before you begin

Ensure that the installation of the required components on the Maximo AssetManagement computer is complete.

Procedure1. Start the configuration wizard by double-clicking the ConfigUI file in the

install_home/ConfigTool directory.2. On the home screen of IBM Tivoli's process automation engine configuration

utility, select Update Database and Build and Deploy Application EAR Files.3. Complete the configuration wizard.

Manually updating the database and building and deployingthe EAR file

If you did not use the configuration wizard, you must manually update theMaximo database and build and deploy the EAR file. If your deployment usesOracle WebLogic Server, you are required to complete the manual steps.

Updating the database and building the EAR fileBefore you can deploy the product, you must update the Maximo database andbuild the Maximo EAR file.

Procedure1. Open a command prompt and change to the install_home\maximo\tools\

maximo directory.2. Run the following command:

updatedb

3. Change to the install_home\maximo\deployment directory and run thefollowing command:buildmaximoear

Deploying the EAR file on WebSphere Application ServerIf you did not use the configuration wizard, Maximo Asset Management includes acommand line tool, which you can use to manually deploy the EAR file.

Before you begin

Ensure that you updated the Maximo database and built the EAR file.

About this task

Maximo Asset Management includes a command line tool, which is located in theinstall_home\ConfigTool\scripts\ directory. Command-line configuration quickly


updates configuration values without using the configuration wizard. You can usethe command line tool to build and deploy the EAR file.

The EAR file is installed on WebSphere Application Server during the MaximoAsset Management installation.

Deploying the EAR file starts the application server.

Procedure1. Open a command prompt and change to the install_home\ConfigTool\

scripts\ directory.2. On Windows systems, run the following command:

reconfigurePae.bat -action updateApplication -deploymaximoear

On UNIX or Linux systems, run the following command:reconfigurePae.sh -action updateApplication -deploymaximoear

Deploying the EAR file on WebLogic ServerAfter you update the database and build the EAR file, you must deploy the EARfile from the WebLogic Server console.

About this task

To deploy the EAR file on WebLogic Server, follow the instructions in Deployingear files.

Installing MobileFirst ServerThe installation program automatically creates a database instance for theMobileFirst Server environment. It also configures the application server that youassign to MobileFirst Server.

Before you begin

Before you install MobileFirst Server, consider whether to use the automatedmethod or to create a database instance manually. By using the manual method,you can also create database schemas on a single instance. After the installation iscomplete, you must manually configure the application server to add the databasesthat you created.

For more information about planning the creation of databases, see the IBMMobileFirst Platform Foundation IBM Knowledge Center.

Restriction: MobileFirst Server is not supported on Mac OS X computers. If youwant to build and deploy apps for iOS devices, you must install MobileFirst Serveron a different operating system.

Installing MobileFirst Server by using the installation programIn a Maximo Anywhere deployment, MobileFirst Server includes three maincomponents: MobileFirst Server Administration Services, MobileFirst OperationsConsole, and Application Center. You must deploy MobileFirst Server to anapplication server.

Chapter 2. Installing the Maximo Anywhere components 21

http://www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mam.inswl.doc/install/t_tamit_deployingearfiles.html

http://www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mam.inswl.doc/install/t_tamit_deployingearfiles.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/install_config/c_wlserver_plan_install.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/install_config/c_wlserver_plan_install.html

Before you beginv Ensure that you installed the required components on the Maximo Asset

Management administrative workstation.v Ensure that your environment includes one of the application servers that

MobileFirst supports. For more information, see the system requirements forMaximo Anywhere, MobileFirst Server, and MobileFirst Studio. The installer forWebSphere Application Server Liberty is provided with MobileFirst.

v If you are using WebSphere Application Server in your enterprise environment,create a new profile for MobileFirst Server.

v To improve performance, set the Java heap size on the JVM for WebSphereApplication Server or WebSphere Application Server Liberty before you installMobileFirst Server.

About this task

To ensure that the launchpad program runs correctly, do not use any spaces in thedirectory path where the launchpad file is located.

Use the planning worksheet to collect the values that you enter, so that they can beused later in the installation.

During the installation, you might be required to exit the launchpad and restart thelaunchpad on a different computer.

When you start Installation Manager, you can check for the latest fix packs. YourIBM login credentials are required to access the fix pack download site.

Procedure1. On the computer where MobileFirst Server is installed, extract the

Max_Anywhere_V763.zip file and the MaxAny_763_MobileFirst_71.zip file. Copythe contents of the MaxAny_763_MobileFirst_71\Install folder into theMax_Anywhere_V763\Install folder.

2. Start the launchpad by right-clicking the launchpad file and selecting Run asadministrator. Running the executable file as an administrator ensures that youhave the permissions to update the existing installation directory. If yourcomputer is a 64-bit system, use the launchpad64 file. If your computer is aUNIX or Linux system, use the launchpad.sh file.

3. On the Install IBM MobileFirst Server pane, click Install.4. On the MobileFirst Information pane, select Stand-alone MobileFirst Server

and complete the installation wizard.

What to do next

In certain circumstances, you might be required to restart the application server.For more information, see Completing the installation.Related information:

Planning the creation of databases

Creating a profile for a WebSphere Application Server

Manually installing MobileFirst Server administration

Manually installing Application Center


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/admin/c_completing_the_installation.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/install_config/c_wlserver_plan_databases.html

http://www.ibm.com/support/knowledgecenter/SSRTLW_8.5.5/com.ibm.servertools.doc/topics/rcprofile.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/install_config/t_wlconsole_install_manual.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/appcenter/c_installation_manager.html

Installing the MobileFirst Server Administration ServicesAfter MobileFirst Server is installed, you must install and configure theAdministration Services by using the MobileFirst Server Configuration Tool.

Before you begin

Verify that the Application Center Console is installed by entering the ApplicationCenter URL in a web browser. The default URL is: http://localhost:9080/appcenterconsole/login.html.

About this task

Use the planning worksheet to collect the values that you enter, so that they can beused later in the installation.

Accept the default values that the MobileFirst Server Configuration Tool provides.

For more information about the tasks that can be completed by using theMobileFirst Server Configuration Tool, see the IBM MobileFirst PlatformFoundation 7.1.0 IBM Knowledge Center.

Procedure1. On the computer where MobileFirst Server is installed, start the Server

Configuration Tool.

Option Description

On Windows In the Start menu, right-click IBMMobileFirst Platform Server 7.1 > ServerConfiguration Tool and select Run asadministrator.

On Linux In the desktop menu, click IBM MobileFirstPlatform Server 7.1 > Server ConfigurationTool.

On Mac OS X In the Finder, browse to themf_server_home/shortcuts/ directory anddouble-click the configuration-tool.sh file.

2. Select Create a MobileFirst Server Configuration.3. Specify a name for the configuration and click OK. For example, enter Maximo

Anywhere.4. On the Configurations Details pane, make a record of the context root value for

the MobileFirst Administration Services and click Next. The default context rootvalue is /wladmin.

5. On the Console Settings pane, make a record of the context root value for theMobileFirst Operations Console. The context root value can be used to log in tothe MobileFirst Operations Console and administer the mobile apps afterMaximo Anywhere is installed. The default context root value is/worklightconsole.

6. In the Database Properties window, specify the database properties that youselected during the MobileFirst Server installation.

7. In the Application Server Choice window, specify the Application Centerproperties that you selected during the MobileFirst Server installation. Recordthe user name and password values in the planning worksheet. The user name


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/install_config/t_wlconsole_install.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/install_config/t_wlconsole_install.html

and password are required to access the MobileFirst Administrative Services aspart of the Maximo Anywhere installation. Click Save and Deploy.

8. Restart the application server.9. Verify that the MobileFirst Operations Console is installed by entering the

console URL in a web browser. The default URL is: http://localhost:9080/worklightconsole/login.html.

Setting the Java heap size on the JVM for WebSphereApplication Server or WebSphere Application Server Liberty

To improve the performance of the MobileFirst Server, you must increase the javaheap size that is used by the Java virtual machine (JVM). You can set the Java heapsize for the application server by modifying the jvm.options file.

About this task

You can also modify the Java heap size for other types of application server.

You specify the minimum and maximum Java heap sizes as follows:v Minimum Java heap: -Xms<value in MB>mv Maximum Java heap: -Xmx<value in MB>m

By default, the WebSphere Application Server and WebSphere Application ServerLiberty are configured with the following JVM settings:-Xms4m-Xmx488m

You can override the default values by modifying the values in the jvm.optionsfile in the installation directory.

Procedure1. Stop the server by running the following command:

websphere_home\bin\server stop

2. Browse to the websphere_home\usr\servers\defaultServer\type directory andopen the jvm.options file for editing.

3. Specify the following values to set the Java heap size:-Xms128m-Xmx512m

4. Save and close the jvm.options file.5. Start the server by running the following command:

websphere_home\bin\server start

Preparing the Maximo Anywhere environmentBefore you can build and deploy the Maximo Anywhere apps, you must installdevelopment tools that are specific to the mobile platform.

About this task

To build the mobile apps for iOS devices, a Mac OS X computer is required. Theorder of installation is different on Mac OS X computers. For more information, seethe technote Installing a Maximo Anywhere development environment on Mac OSX.




Procedure1. Prepare the computer for building the mobile apps:

Option Description

Android Install the Android development tools.

iOS Install the iOS development tools.

Windows Install the Windows development tools.

2. Install Maximo Anywhere.3. Create a MobileFirst runtime environment.4. Deploy the apps from the command line.5. Optional: Install an integrated development environment.

Installing the Android development toolsOracle JDK and Android SDK are required to build Android mobile apps.

Procedure1. Install Oracle JDK. For the current supported version, see the Maximo

Anywhere system requirements.2. Download the Java SE Development Kit for your operating system.3. Run the executable file and proceed through the installation program.4. To install the Android SDK, go to the Android developers' website and click to

see other download options.5. In the section with the SDK tools, download the SDK for your operating

system and extract the compressed file on your computer.6. Start the installation wizard.

Option Description

On Windows From the extracted directory, run the SDKManager.exe file.

On UNIX or Linux Open a terminal and navigate to theandroid_home/tools/ directory, then run thefollowing command:

android sdk

7. Under Tools, select Android SDK Tools Revision 22 or later and the latestAndroid SDK build tools. Also, select an Android package with an API of 14 orgreater and click Install Packages.

Installing the iOS development toolsA Mac OS X computer with Oracle JDK and Xcode installed is required to buildthe iOS mobile apps.

About this task

You use your Apple ID to enroll in a developer program. You can enroll in the iOSDeveloper Program as an individual or a company in which an individual is aone-person team.




http://developer.android.com/sdk/index.html

You can also enroll in the iOS Developer Enterprise Program as a company, whichauthorizes you to create proprietary in-house iOS apps. The procedure for settingup the iOS Developer Enterprise account might include extra steps.

The person who creates the team becomes the team agent who is the legal contactand administrator of the team and has all privileges and full access to MemberCenter and iTunes Connect. The team agent is required to complete steps 5-7. iOSdevelopers might require the assistance of the team agent to complete theprocedure.

You create provisioning profiles to manage the use of iOS apps that you develop.

A development provisioning profile regulates the development and testing of apps to aspecific number of devices. Development provisioning profiles for the apps mustcontain the IDs of the devices on which the app is installed. You can register moreiOS devices and add them to the provisioning profiles.

A distribution provisioning profile provides access to the app store from all of thedevices in your enterprise.

Procedure1. Install Oracle JDK. For the current supported version, see the Maximo

Anywhere system requirements.a. Download the Java SE Development Kit for your operating system.b. Run the executable file and complete the installation program.

2. Create an Apple ID by registering as an Apple developer in the AppleRegistration Center.

3. Download and install Xcode IDE, including the iOS SDK and Simulator, fromthe Mac App Store.

4. Add your Apple ID to Xcode.5. If you are the team agent, in Xcode create the certificate for the distribution

provisioning profile. Download the certificate to your local environment.6. Register the App IDs.

Create a unique ID for each app that you support. The app ID that youspecify must be unique: Apple does not allow duplicate app IDs.The following table contains examples of bundle IDs that can be specified forthe Maximo Anywhere apps. Replace the company_name value with yourcompany name.

App name Example bundle ID

Asset Audit com.company_name.maximoanywhere.AssetAudit

Asset Data Manager com.company_name.maximoanywhere.AssetDataManager

Inspection com.company_name.maximoanywhere.Inspection

Issues and Returns com.company_name.maximoanywhere.IssuesReturns

Physical Count com.company_name.maximoanywhere.PhysicalCount

Service Request com.company_name.maximoanywhere.ServiceRequest

Transfers and Receiving com.company_name.maximoanywhere.Transfers

Work Approval com.company_name.maximoanywhere.WorkApproval

Work Execution com.company_name.maximoanywhere.WorkExecution




https://developer.apple.com/programs/register/

https://developer.apple.com/programs/register/

http://www.apple.com/osx/apps/app-store.html

https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppStoreDistributionTutorial/AddingYourAccounttoXcode/AddingYourAccounttoXcode.html

https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html

https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingProfiles/MaintainingProfiles.html

To specify an identifier to represent a single app, click Explicit App ID andenter a unique ID for the app. Repeat this step for each app that you support.

7. From the maximoanywhere_home\MaximoAnywhere\apps\app_name directory, openthe application_descriptor.xml file and change the bundle ID strings tomatch the bundle IDs that you created.

8. To support command line builds of our app, you must create a distributionprovisioning profile. Ensure that you select the distribution certificate whencreating this provisioning profile.a. Create a distribution provisioning profile for each app by using Member

Center. When you generate a distribution provisioning profile, you are notrequired to provide IDs of the devices.

b. Download each app's provisioning profile to your Mac OS X computer.Every time that a provisioning profile is updated, you must download theprofile to the build server.

When you run the app build and deployment process, the provisioningprofiles are collected and stored in the iOS application archive file (IPA).

9. Run the following command:./build.sh all

10. Optional: To test the app on a local device using Xcode, you must register theDevice IDs for all of your test devices. You must also create a DeveloperProvisioning Profile for the app. While creating the provisioning profile,ensure that you select your developer certificate while creating the app andalso the Device IDs of your test devices.a. Create a developer certificate for a development provisioning profile.

Download the certificate and add it to the Keychain application.b. Register the Device IDs in Member Center. You can locate the unique

device identifier (UDID) by connecting your device to the Mac OS Xcomputer while Xcode or iTunes are running.

c. Download the developer provisioning profile to your Mac OS X computer.

Installing the Windows development toolsMicrosoft Visual Studio is required to build apps for Windows devices.

Before you beginv Ensure that your Windows computer is running a supported operating system.

For more information, see the System Requirements section of the Maximo AssetManagement wiki.

v Windows devices require Visual C++ redistributable packages, which must beinstalled if they are not already on the device. For more information, see VisualC++ Redistributable for Visual Studio 2012.

About this task

Visual Studio Community 2015 is the recommended version.

Restriction: Visual Studio Express for Web is not supported.

Procedure1. From the Visual Studio website, select a supported version of Visual Studio and

click Download.2. Run the vs_community.exe file.




http://support.apple.com/kb/PH7297



https://www.microsoft.com/en-us/download/details.aspx?id=30679

https://www.microsoft.com/en-us/download/details.aspx?id=30679

https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs.aspx

3. Complete the installation wizard.

Installing Maximo AnywhereInstall Maximo Anywhere on a designated build computer. You use the buildcomputer to build the mobile apps and deploy them to MobileFirst Server.

Before you beginv Ensure that the required enablement components are installed on the computer

where Maximo Asset Management is installed.v If you are installing a production environment, ensure that MobileFirst Server is

installed.

About this task

The Maximo Anywhere installation image contains the MaximoAnywhere projectand the mobile apps.

The production build computer must be continuously connected to the networkand undergo regular system backups.

To ensure that the launchpad program runs correctly, the directory path where thelaunchpad file is located must not contain any spaces. Running the launchpadexecutable file as an administrator ensures that you have the permissions to updatethe existing installation directory.

Restriction: The Maximo Anywhere launchpad program is not supported on MacOS X. To start the installation on Mac, you must start IBM Installation Managermanually.

Procedure1. On the computer where Maximo Anywhere is installed, extract the

Max_Anywhere_V763.zip file for your version. If you plan to install eitherMobileFirst Server or MobileFirst Studio as part of an integrated developmentenvironment, then also extract the MaxAny_763_MobileFirst_71.zip file.

2. Start the launchpad.

Option Description

Windows, Linux, or UNIX Right-click the launchpad file and select Runas administrator. If your computer is aWindows system, use the launchpad64.exefile. If your computer is a UNIX or Linuxsystem, use the launchpad.sh file.

Mac OS X 1. From the Maximo Anywhere installationimage, open the Install > IM folder andexpand the installer.macOS compressedfile.

2. Ensure that the path to the Userinstexecutable file does not contain anyspaces or parentheses. Double-click theUserinst executable file.

3. On the Install IBM Maximo Anywhere pane, click Install.


4. If you deployed MobileFirst Server to a stand-alone application server, selectStand-alone MobileFirst Server. If you are setting up an integrateddevelopment environment with MobileFirst Studio, select Embedded Serverwithin MobileFirst Studio and complete the installation wizard.

5. After the installation is complete, copy the MaximoAnywhere.war file to thecomputer where MobileFirst Server is installed.

Creating a MobileFirst runtime environmentAfter Maximo Anywhere is installed, you must set up and configure a MobileFirstruntime configuration by using the MobileFirst Server Configuration Tool.

Before you begin

Ensure that Maximo Anywhere is installed. If you installed Maximo Anywhere ona different computer than the MobileFirst Server computer, ensure that theMaximoAnywhere.war file is copied over.

About this task

Use the installation planning worksheet to record the values that you enter so thatthey can be used later in the installation.

Procedure1. On the computer where MobileFirst Server is installed, start the Server

Configuration Tool.

Option Description

On Windows In the Start menu, click IBM MobileFirstPlatform Server 7.1 > Server ConfigurationTool.

On Linux In the desktop menu, click IBM MobileFirstPlatform Server 7.1 > Server ConfigurationTool.

2. Select Add a MobileFirst runtime environment to a configuration and specifya name for the new runtime environment. For example, enter MaximoAnywhere.Use the scroll bar to see the MobileFirst project configuration.

3. On the MobileFirst runtime environment pane, browse to theMaximoAnywhere.war file that was generated on the Maximo Anywherecomputer. Specify the MobileFirst project context root and click Next. Thisvalue must match the runtime context root that you specified during theMaximo Anywhere installation.

4. Specify the database settings in the subsequent panes and click Save andDeploy. After the runtime configuration is saved, you can redeploy theMaximoAnywhere.war file at any time by selecting it in the MobileFirst ServerConfiguration Tool.

5. Restart MobileFirst Server.6. On the computer where Maximo Anywhere is installed, run the build all

command. If your computer is a Windows system, use the build.cmd file. Ifyour computer is a UNIX or Linux system, use the build.sh file. This stepgenerates the distributable files for the project and deploys them to MobileFirstServer.


Results

After the deployment is complete, the MaximoAnywhere project and apps areavailable in the MobileFirst Operations Console and the Application CenterConsole.

Installing an integrated development environmentYou can create an integrated development environment (IDE) by installing theEclipse IDE and MobileFirst Studio. You can use the IDE to develop, test, andconfigure mobile apps before you deploy them to MobileFirst Server or to mobiledevices.

Before you beginv Ensure that Maximo Anywhere is installed on the computer where you are

installing the IDE.v It is recommended that you install the IDE on a computer that is independent of

the server.v Depending on the mobile platform that you plan to develop apps for, ensure

that you installed the Android, iOS, or Windows development tools.v Oracle JDK is required to run Eclipse and to build apps for Android, iOS, and

Windows devices. For the current supported version, see the Maximo Anywheresystem requirements.

v To preview the apps in the MobileFirst Studio mobile browser simulator, installGoogle Chrome.

v To allow Eclipse to install the required plugins, ensure that your firewall istemporarily disabled.

v If you are installing an integrated development environment on a Mac OS Xcomputer, follow the instructions in this technote: Installing a MaximoAnywhere development environment on Mac OS X.

About this task

MobileFirst Studio is an Eclipse-based development environment that can be usedto configure the Maximo Anywhere apps. You install MobileFirst Studio from theEclipse integrated development environment (IDE) workbench. A set of platformdevelopment tools are also required to build and deploy the mobile apps.

You can use the mobile browser simulator, the Android Emulator, or the iOSSimulator to view and test the mobile apps.

You can customize the mobile apps when they are deployed. For more information,see Customizing Maximo Anywhere mobile apps.

Procedure1. Install Eclipse IDE:

a. Go to Eclipse IDE for Java EE Developers and download Eclipse IDE forJava EE Developers (Eclipse Kepler 2).

b. Extract the compressed folder and run the Eclipse application.2. Set up your Eclipse development environment:

a. Check whether the Eclipse JSDT plug-in is installed. The JavaScriptDevelopment Tool (JSDT) plug-in helps you navigate through the JavaScript code in Eclipse.






http://panchax.tivlab.austin.ibm.com:8207/help/topic/com.ibm.mbs.doc/config_apps/t_ctr_cust_apps.html

http://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/keplersr2

1) Select Help > About Eclipse > Installation Details and click the WTPicon (Eclipse Web Tools Platform).

2) In the About Eclipse Features window, browse the Feature Name list forEclipse JavaScript Development Tools.

b. If the JavaScript Development Tools plug-in is not already installed,complete the following steps:1) Select Help > Install New Software > Add.2) In the Add Repository window, specify the following URL in the

Location field: http://download.eclipse.org/webtools/repository/kepler.

3) In the Name field, specify Eclipse WTP.4) Select Web Tools Platform (WTP) 3.5.1 (or later) > JavaScript

Development Tools and install the plug-in.c. Set Google Chrome as the default web browser by selecting Window >

Preferences > General > Web Browser > Use external web browser. IfChrome is not available in the External web browsers window, click New,specify Chrome in the Name field and browse to the Chrome.exe file which isin the C:\Program Files (x86)\Google\Chrome\Application directory onWindows systems. Click OK to apply your changes. Alternatively, you canset your default web browser to Chrome.

3. Install MobileFirst Studio Consumer Edition:a. In Eclipse, select Help > Install New Software > Add.b. In the Add Repository window, click Archive.c. Browse to the MaxAny_763_MobileFirst_71/MobileFirstStudio.zip folder

and click Open > OK.d. On the Available Software pane, select IBM MobileFirst Platform Studio

Development Tools. The following items are selected for installation: IBMDojo Mobile Tools, IBM jQuery Mobile Tools, and IBM MobileFirst PlatformStudio.

e. Click Next > Next > Finish.f. Restart Eclipse to apply the changes.

4. Import the MaximoAnywhere project into MobileFirst Studio.a. In Eclipse, click File > Import > General, select Existing Projects into

Workspace and click Next.b. Click Select root directory and specify the path to \IBM\Anywhere.c. Select the MaximoAnywhere project and click Copy projects into workspace.

Click Finish.d. In the Project Explorer pane, expand all nodes. Right-click the

OSLCGenericAdapter folder and select Run As > Deploy MobileFirstAdapter.

e. Right-click the application folder and click Run As > Run on MobileFirstDevelopment Server.

f. To preview the app, right-click the application folder and click Run As >Preview.

5. To build apps for Android devices, install the Android Development Tools(ADT) plug-in:a. In Eclipse, select Help > Install New Software > Add.b. In the Add Repository window, specify the following URL in the Location

field: https://dl-ssl.google.com/android/eclipse/.c. In the Name field, specify Android Development Tools and click OK.


d. On the Available Software pane, click Select All > Next > Next > Finish.e. Restart Eclipse and specify a workspace directory.f. Open the Eclipse Preferences window and specify the Android SDK path.

Click Apply > OK to apply the changes.g. On the Welcome to Android Development pane, select Use existing SDKs

and browse to the SDK directory. Click OK > Next > Finish.

Silent mode: Installing Maximo AnywhereYou can run a silent installation of Maximo Anywhere, MobileFirst Server, andInstallation Manager from a command line. Silent installations that are conductedwith Installation Manager are defined by an XML response file.

Recording a response file for silent installationA response file collects data and records the selections that you make when youuse the Installation Manager. If you want to run a silent installation, you mustrecord the installation settings.

About this task

When you use the Installation Manager to install the components, an XMLresponse file can be recorded. The response file can be used for future silentinstallations of Maximo Anywhere and MobileFirst Server. Once your system is setup to record a response file, the response file is overwritten with each subsequentuse of the installation program.

To record a response file, set the record environment variable to true before youstart the launchpad. Alternatively, if you want to run the installation program froma command line, use the -record parameter.

Procedure1. Open a command line and run the set record=true command on Windows or

the export record=true command on UNIX or Linux.2. Start the Maximo Anywhere launchpad and proceed with the installation.3. Click Finish. A response file is generated in the user home directory. The

response file is marked with a time stamp, for example,tpaeInstallerRsp20130716105150.xml.

Installing the required components in silent modeIn a Maximo Asset Management 7.6.2 environment, you use Installation Managerto install the required components in silent mode.

About this task

The process automation engine executable file is called install.exe orinstall.bin. You reuse this file to install the Maximo Anywhere components.

Procedure

Maximo Asset Management version 7.6.2 or later:

1. Open the response file for editing and modify the values for your operatingsystem. Ensure that the value for the repository location is correct.


2. Change directory to the tools directory where Installation Manager wasinstalled and run the following command:imcl -input responsefilename -log logfilename -acceptLicense

Specify the path and name of the existing response file and log file that youwant to use. The -acceptLicense parameter is used to accept the licenseautomatically. For example, on Windows, run the following command:imcl -input C:\tmp\response_install_Anywhere_Enablement.xml-log C:\tmp\silent_install_log.xml -acceptLicense

Related information:

Silent installation properties

Installing Installation Manager in silent modeInstallation Manager is the tool that is used to install Maximo Anywhere andMobileFirst Server. Installation Manager can itself be installed in silent mode.

About this task

The Installation Manager folder includes the silent-install.ini initialization file,which contains default parameters and values that are required for silentinstallation. You can use the initialization file to set the values for the silentinstallation process. A range of parameters can be modified in thesilent-install.ini file.

Procedure1. Browse to the Install\IM folder of the Maximo Anywhere installation image

and copy the Installation Manager folder for your system to a local directory.For example, copy the installer.win64 if your computer is running aWindows 64-bit operating system.

2. Optional: To modify the installation parameters, edit the silent-install.inifile.

3. From a command line, change to the directory where you copied theInstallation Manager folder and run one of the following commands. Specifythe path and the name of the log file that you want to create:

Option Description

On Windows installc.exe –-launcher.inisilent-install.ini -loglogfilename-acceptLicense

On UNIX or Linux ./installc --launcher.inisilent-install.ini -loglogfilename-acceptLicense

For example, run the following command for Windows:installc.exe –-launcher.ini silent-install.ini -log C:\tmp\silent_install_log.xml -acceptLicense


Install Installation Manager silently

Parameters for silent mode installationYou can modify the silent-install.ini initialization file by updating theparameters for your environment.


http://www.ibm.com/support/knowledgecenter/SSPJLC_7.6.0/com.ibm.mam.inswas.doc/install/r_silentbsiproperties.html

http://pic.dhe.ibm.com/infocenter/install/v1r5/topic/com.ibm.silentinstall12.doc/topics/t_silent_installIM_IMinst.html

Parameter Description

-vm Specifies the Java launcher. In silent mode,always use java.exe on Windows, and javaon other operating systems.

-nosplash Suppresses the splash screen.

--launcher.suppressErrors Suppresses the JVM error dialog.

-silent Runs the Installation Manager program insilent mode.

-input Specifies that an XML response is used asthe input for the Installation Managerprogram.

-log Generates a log file that records the result ofthe silent installation. The log file is an XMLfile, for example, c:\mylogfile.xml or/root/mylogs/mylogfile.xml

Installing Maximo Anywhere in silent modeTo install in silent mode, a response file is required. You can generate a responsefile by completing a successful installation of Maximo Anywhere with theInstallation Manager. Alternatively, you can use a sample response file that isprovided in the Maximo Anywhere installation image.

Before you begin

Installation Manager must be installed on the target computer.

Copy a generated response file or a sample response file with the necessarychanges to the target computer. A sample response file is provided for youroperating system in the Max_Anywhere_V763\samples folder of the MaximoAnywhere compressed installation image.

For Windows installations, use the response_install_Maximo_Anywhere_Win.xmlresponse file.

For Mac OS X installations, use theresponse_install_Maximo_Anywhere_UnixMac.xml response file.

About this task

You can copy the Maximo Anywhere response file to multiple computers to runsilent installations.

You must ensure that all values in the response file are valid for the target system.

Procedure1. Open the response file for editing and modify the values for your operating

system. Ensure that the value for the repository location is correct.2. Change directory to the tools directory where Installation Manager was

installed and run the following command:imcl -input responsefilename -log logfilename -acceptLicense


Specify the path and name of the existing response file and log file that youwant to use. The -acceptLicense parameter is used to accept the licenseautomatically. For example, on Windows, run the following command:imcl -input C:\tmp\response_install_Maximo_Anywhere_Win.xml-log C:\tmp\silent_install_log.xml -acceptLicense

Setting up Maximo Asset Management for Maximo AnywhereYou must add users to the predefined Maximo Anywhere security groups andenable applications in Maximo Asset Management.

Adding users to the Maximo Anywhere security groupsWhen mobile workers manage records, they must have the authority to use theMaximo Anywhere mobile apps. You authorize access to the Maximo Anywhereapps by adding users to the predefined security groups in Maximo AssetManagement.

About this task

The user and group association are retrieved from Maximo Asset Managementduring authentication. If the user does not belong to the security group that isassociated with the app, login fails. For each app, this security control isimplemented in the application definition file. In this file, the requiredRoleattribute specifies the security group that is authorized to use the app.

By default, the Maximo Anywhere security groups do not include any users. Youmust add the relevant users, including predefined users such as MAXADMIN,before you deploy the associated apps.

Procedure1. In the Users application of Maximo Asset Management, create the user records.2. In the Security Groups application, select the Maximo Anywhere group to

which you want to add a user.3. If your user is in a MAXADMIN group, clear the independent flag for that

security group.4. From the Users tab, click New Row.5. Select a user. The associated user information populates the other fields.6. Save your changes.

What to do next

The Maximo Anywhere security groups do not include authorizations for specificsites, labor, storerooms, or GL components. You must create separate securitygroups to implement security controls for these items.

Users of the Maximo Anywhere Work Execution app must have a labor record. If auser does not have a labor record, login fails.

Maximo Anywhere security groups in Maximo AssetManagement

Maximo Asset Management includes predefined security groups for the MaximoAnywhere apps. You use these security groups to grant authorization to use the


http://www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mbs.doc/user/t_add_users.html

http://www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mbs.doc/securgroup/t_assign_sites_security_groups.html

Maximo Anywhere apps. The number of authorized users for each app mustcomply with the terms of the Maximo Anywhere product license.

App authorizations

The following security groups are included in the required components that aredeployed during installation to the Maximo Asset Management environment:

ANYWHERE_TECHNICIANGrants authorization to use the Maximo Anywhere Work Execution app.

ANYWHERE_APPROVERGrants authorization to use the Maximo Anywhere Work Approval app.

ANYWHERE_PHYSICAL_COUNTGrants authorization to use the Maximo Anywhere Physical Count app.

ANYWHERE_INSPECTORGrants authorization to use the Maximo Anywhere Inspection app.

ANYWHERE_ASSET_AUDITORGrants authorization to use the Maximo Anywhere Asset Audit app.

ANYWHERE_ASSET_MANAGERGrants authorization to use the Maximo Anywhere Asset Data Managerapp.

ANYWHERE_ISSUES_RETURNSGrants authorization to use the Maximo Anywhere Issues and Returns app.

ANYWHERE_SERVICE_REQUESTGrants authorization to use the Maximo Anywhere Service Request app.

ANYWHERE_TRANSFERSGrants authorization to use the Maximo Anywhere Transfers and Receivingapp.

These security groups are used to implement security at two levels:v Authorization to use the associated mobile app. This type of control is provided

by the app itself. Only users who belong to the associated security group can login to the app. If you remove a user from the associated security group,authorization is revoked the next time that the user logs in to the app throughthe server.

v Authorization to read, create, and update data for the OSLC resources that areused in the associated mobile app. This type of control is provided by theMaximo application that is registered with the object structure for the resource.The security group identifies the authorizing application for each object structureand specifies the application-level signature options that are required to providethe appropriate level of data access. Users who belong to the security groupautomatically have the appropriate level of access for all data operations in theassociated app.

By default, these security groups do not include any users. You must add therelevant users, including system users such as MAXADMIN, before you deploy theassociated apps.

The Maximo Anywhere security groups do not include authorizations for specificsites, labor, storerooms, or GL components. To ensure complete access to MaximoAnywhere, click the Sites tab and select Authorize group for all sites. Click theLabor tab and select Authorize group for all labor.


Product license compliance

The terms of your Maximo Anywhere license specify the number of users that areentitled to use each mobile app. To comply with the terms of your product license,the number of users in the Maximo Anywhere security groups must not exceed thenumber of users that are entitled to use the associated apps.

Enabling Maximo Asset Management applications for mapsand labor reporting

The Maximo Anywhere required components contain licenses for more MaximoAsset Management applications. You enable the Service Address application foruse with the map feature and the Crews and Crew Types applications are used forlabor reporting.

About this task

This procedure grants access to administrators to configure the features of theapplications.

Procedure1. In Maximo Asset Management, go to the Security Groups application and select

the group to which you want to grant access. For example, specify MAXADMIN.2. On the Applications tab, select Grant access for the applications that you want

to enable.3. Save the group.Related concepts:Map positioning information

Maximo Asset Management system options that affect mobileapps

The settings that you define in the Organizations application in Maximo AssetManagement apply to the relevant enterprise system applications and to theassociated mobile apps.

The options that affect the mobile apps are system-wide. You cannot define settingsthat are organization-specific or site-specific.

The following table specifies the options that affect the mobile apps. Configurableoptions are accessed from the Select Action menu in the Organizations applicationand are grouped by business object.

Option group Option description Example

Timer Options Automatically change thework order status fromApproved to In Progresswhen a user starts a labortimer.

If a work order is approved,the status automaticallychanges to In Progress whenyou start the timer.

Automatically change thework order status toComplete when a user stopsa labor timer.

When you stop the timer fora labor transaction, the statusof the work order changes toComplete.


http://panchax.tivlab.austin.ibm.com:8207/help/topic/com.ibm.mbs.doc/maps/c_tech_overview_maps.html

Option group Option description Example

Labor Options Future labor transactiontolerance in hours. A labortransaction is not valid if itincludes a future start orstop time that exceeds thespecified tolerance.

You can specify the numberof hours in the future thatlabor transactions can beentered. You might want toenter time for future labor ifyou know that you are goingto perform a task but wantto report the time now.

Edit Rules Work order edit settings.Some fields do not apply tothe mobile apps, and areexcluded from the mobileapps or are read-only in themobile apps.

For each work order status,you can specify the types ofdata that can be edited. Forexample, if a work order isin Approved status, you canspecify that the asset fieldcan be edited.

Time zones

When mobile workers use mobile apps, the time zone at the server might bedifferent from their time zones. With the Users application in Maximo AssetManagement, you must specify the time zone in the user record for each mobileworker. The mobile apps use this information to calculate the difference betweenthe server time and the device time.

For example, in labor transactions, the start and end times are adjusted andreported accurately based on the time zone that is set in your user record. Settingthe time zone is important for these types of transactions, especially if you want toreport hours for labor that is to be done in the future.


Chapter 3. Updating the Maximo Anywhere components

To update your environment to Maximo Anywhere 7.6.3, you must update thecomponents on one or more computers.

About this task

You can update to Maximo Anywhere 7.6.3 from the following versions:v Maximo Anywhere 7.6.2v Maximo Anywhere 7.6.2.1

Maximo Anywhere 7.6.3 includes the following compressed files:v Max_Anywhere_V763.zip

v MaxAny_763_MobileFirst_71.zip

You must extract the compressed files on multiple computers. The contents of theInstall folder in the MaxAny_763_MobileFirst_71.zip file must always be copiedinto the Install folder of the Max_Anywhere_V763 folder on the target system.

When you launch Installation Manager from the launchpad, Installation Managerupdates to the latest version and restarts. After the update is complete, you canbegin the update process from the launchpad.

Updating the required componentsYou must update the required components on the computer where Maximo AssetManagement is installed.

Procedure1. On the computer where Maximo Asset Management is installed, extract the

Max_Anywhere_V763.zip for your version to the Maximo Asset Managementinstallation directory.

2. Start the launchpad by right-clicking the launchpad file and selecting Run asadministrator. If your computer is a 64-bit system, use the launchpad64 file. Ifyour computer is a UNIX or Linux system, use the launchpad.sh file.

3. On the Install or Update IBM Maximo Asset Management RequiredComponents pane, click Install. The Installation Manager wizard starts.

4. On the Installation Manager home screen, click Update and complete theupdate wizard.

5. Deploy the product by updating the database and building and deploying theMaximo EAR file. Allow the IBM Tivoli process automation engineconfiguration utility to start and select Update Database and Build andDeploy Application EAR Files to complete the configuration.

Updating MobileFirst ServerYou can either update MobileFirst Server to version 7.1.0 or install MobileFirstServer 7.1.0 as a fresh instance on a new server.


About this task

For more information about the update process, see updating to MobileFirst ServerV7.1.0 in a production environment.

Procedure1. On the computer where MobileFirst Server is installed, extract the

Max_Anywhere_V763_for_Max7x.zip file for your version and theMaxAny_763_MobileFirst_71.zip file. Copy the contents of theMaxAny_763_MobileFirst_71\Install folder into theMax_Anywhere_V763_for_Max7x\Install folder.

2. Start the launchpad by right-clicking the launchpad64.exe file and selectingRun as administrator. If your computer is a Windows system, use thelaunchpad64.exe file. If your computer is a UNIX or Linux system, use thelaunchpad.sh file.

3. On the Install or Update IBM MobileFirst Server pane, click Install. TheInstallation Manager wizard starts.


Updating the Maximo Anywhere build environmentTo build and deploy the apps, you must update the computer where MaximoAnywhere is installed.

About this task

Running the executable file as an administrator ensures that you have thepermissions to update the existing installation directory.

Procedure1. On the computer where Maximo Anywhere is installed, extract the

Max_Anywhere_V763.zip file for your version. If you plan to update eitherMobileFirst Server or MobileFirst Studio, then also extract theMaxAny_763_MobileFirst_71.zip file.

2. Start the launchpad by right-clicking the launchpad64.exe file and selectingRun as administrator. If your computer is a Windows system, use thelaunchpad64.exe file. If your computer is a UNIX or Linux system, use thelaunchpad.sh file.

3. On the Install or Update IBM Maximo Anywhere pane, click Install. TheInstallation Manager wizard starts.


5. If an error occurs with the anywhere-rdfs-puller.xml file after MaximoAnywhere is updated, you can run the script manually. For more information,see Importing OSLC resources to Maximo Anywhere.a. If you had any custom timeouts in the OSLCGenericAdapter.xml file, these

are overwritten during the update. Ensure that the following properties areset to the correct values:<connectionTimeoutInMilliseconds>30000</connectionTimeoutInMilliseconds><socketTimeoutInMilliseconds>30000</socketTimeoutInMilliseconds>

b. If you added a lookup resource prior to updating to Maximo Anywhere7.6.3, ensure that a queryBase and a queryURI are specified or lookup data


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr_in_production_env.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr_in_production_env.html

http://panchax.tivlab.austin.ibm.com:8207/help/topic/com.ibm.mbs.doc/integration/t_import_resource_data.html

downloads will fail. For example, add the following queryBase to yourresource under the <attributes> section:<queryBases id="additionalstoreroom_queryBases"><queryBase id="additionalstoreroom_queryBase_getlocationstoreroom"name="getlocationstoreroom" queryUri="/oslc/os/oslcopersroom"/></queryBases>

Ensure that your queryUri matches the URI of your OSLC resource.6. Go to the maximoanywhere_home\Anywhere\MaximoAnywhere\apps\app_name

directory for each app and, in the app-feature.properties file, ensure that theproperties that you require are set to true.

7. Migrate the artifact configurations. You can find the original files in yourbacked up directory, for example in MaximoAnywhere_b4_7.6.3.a. Use a graphical file-comparison program to compare your modified 7.6.2

app.xml file to the 7.6.3 app.xml file.b. Copy any additional JavaScript or XML files that you created in the old

environment to the new environment.8. After the update is complete, copy the MaximoAnywhere.war file to the

computer where MobileFirst Server is installed.9. On the computer where MobileFirst Server is installed, start the Server

Configuration Tool and redeploy the MaximoAnywhere.war file.10. Restart MobileFirst Server.11. On the computer where Maximo Anywhere is installed, run the build all

command. If your computer is a Windows system, use the build.cmd file. Ifyour computer is a UNIX or Linux system, use the build.sh file.

Updating the MaximoAnywhere project in MobileFirst StudioThe method that you use to update the MaximoAnywhere project in MobileFirstStudio depends on the way that you imported the project when you installedMaximo Anywhere.

Before you begin

Ensure that you have updated Maximo Anywhere to version 7.6.3.

About this task

If your environment already includes MobileFirst Studio 7.1, you do not need tocomplete these steps.

The MaximoAnywhere project was set up by using one of the following options:v The Copy Projects into workspace check box was cleared in Eclipse. Eclipse

uses the files that are in the installation directory.v The Copy Projects into workspace check box was selected in Eclipse. Eclipse

uses copies of the MaximoAnywhere files, which are stored separately from theinstallation directory.

Procedure1. On the computer where Maximo Anywhere 7.6.3 and MobileFirst Studio is

installed, ensure that you have extracted the MaxAny_763_MobileFirst_71.zipfile.

Chapter 3. Updating the Maximo Anywhere components 41

2. If the Copy Projects into workspace check box was cleared in Eclipse, completethe following procedure:a. Start MobileFirst Studio, right-click the MaximoAnywhere project and click

Close.b. Start the launchpad and on the Install or Update IBM Maximo Anywhere

pane, click Install.c. In IBM Installation Manager, click Update and complete the update wizard.

Maximo Anywhere is updated to version 7.6.3.d. In MobileFirst Studio, update to version 7.1.0, but use the

MobileFirstStudio.zip file that is located in the MaxAny_763_MobileFirst_71folder. This step requires you to restart MobileFirst Studio.

e. After MobileFirst Studio 7.1.0 restarts, right-click the MaximoAnywhereproject and select Open Project.

3. If the Copy Projects into workspace check box was selected in Eclipse,complete the following procedure:a. Ensure that the MaximoAnywhere installation directory contains the most

recent file changes.b. Start the launchpad and on the Install or Update IBM Maximo Anywhere

pane, click Install.c. In IBM Installation Manager, click Update and complete the update wizard.

Maximo Anywhere is updated to version 7.6.3.d. Start MobileFirst Studio 6.3.0, right-click the MaximoAnywhere project, click

Delete and select Delete project contents on disk. This step removes theproject files and deletes the contents from the hard disk drive.

e. In MobileFirst Studio, update to version 7.1.0, but use theMobileFirstStudio.zip file that is provided in theMaxAny_763_MobileFirst_71 folder. This step requires you to restartMobileFirst Studio.

f. After MobileFirst Studio 7.1.0 restarts, import the MaximoAnywhere projectfrom the original installation directory.

What's new in application definitions in 7.6.3The application definition file (app.xml) contains new content in MaximoAnywhere 7.6.3. There are two new properties, fullScreeen and combinedViews.

The application definition files for each of the mobile apps are located in themaximoanywhere_home\ Anywhere\MaximoAnywhere\apps\app_name\artifactdirectory.

If the fullScreeen property is set to true for a view, this view is shown in fullscreen mode. All its child views, views that can be navigated to from the fullscreen view, are also shown as full screen. If the combinedViews property is set totrue for the IBM Maximo Anywhere Work Execution app, the first view is enabledfor split panes, and it is shown in the left pane. All other views, unless thefullScreeen property is set to true for a view, are shown in the right pane.


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.upgrade.doc/devenv/t_upgrade_studio.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.upgrade.doc/devenv/t_upgrade_studio.html

Chapter 4. Installing help locally

Product help for Maximo Anywhere is provided online in IBM Knowledge Center.If you want to install help locally, you can download IBM Knowledge Center andhelp packages from Fix Central.

Installing helpYou can download help packages from Fix Central that contain the samedocumentation packages that are available online in IBM Knowledge Center. Youadd the help packages and configuration files to a local installation of IBMKnowledge Center

Procedure1. To download a locally-installable version of IBM Knowledge Center and help

packages from Fix Central, follow the instructions at http://www-01.ibm.com/support/docview.wss?uid=swg24041962.

2. Extract the IBM Knowledge Center package to the location where you want toinstall it. The default installation location is C:\KnowledgeCenter. If you installIBM Knowledge Center to a different location, you must update the pathvalue in the taxonomy.properties file for each help package that you install.

3. Extract a help package to a temporary location. The extracted files include oneor more plugin folders, a properties file and a taxonomy file.

4. Copy all com.ibm.prod.doc plugin folders from the help package to theinstall_home/KnowledgeCenter/usr/content/KCXhtml directory.

5. Copy the properties file to the configuration directory, for example toinstall_home/KnowledgeCenter/usr/conf/SSLKT6_7.6.0.5.properties.

6. Open the taxonomy.properties file in a text editor and update the path value,if necessary, to point to the installed location. For example, change the valueof the Path property from C:/KnowledgeCenter/usr/content/KCXhtml toE:/IBM/SMP/KnowledgeCenter/usr/content/KCXhtml, where IBM KnowledgeCenter is installed at E:/IBM/SMP/KnowledgeCenter.

7. Replace the install_home/KnowledgeCenter/usr/taxonomy/KC_taxonomy.ditamap with the version of the KC_taxonomy.ditamap file that isincluded in the help package.

8. In the install_home/KnowledgeCenter/bin directory, click startKC.bat onWindows or startKC.sh on Linux or AIX to start IBM Knowledge Center.

9. In a browser, open http://install_home:port/kc to view the product help, forexample http://127.0.0.1:9090/kc.

10. In Maximo Anywhere, redirect the application help links to point to your localinstallation of IBM Knowledge Center:a. In the System Properties application, filter for mxe.help properties.b. Change the mxe.help.host and mxe.help.port properties to the host and

port values for your local installation of IBM Knowledge Center, such asthe default host value of 127.0.0.1 and default port value of 9090.

c. Change the mxe.help.path property value from /support/knowledgecenter/to /kc/.

d. Save the changes and click Live Refresh to update the values in theproduct database.




11. To stop IBM Knowledge Center, in the install_home/KnowledgeCenter/bindirectory, click stopKC.bat on Windows or stopKC.sh on Linux or AIX.

IBM Knowledge Center configurationIBM Knowledge Center requires minimal configuration to run help packages forIBM products in your local environment. You can also configure it to providedifferent content in separate instances of IBM Knowledge Center or to run existingEclipse help plugins in IBM Knowledge Center.

Changing the IBM Knowledge Center URL

If you install IBM Knowledge Center on your local computer, when you start theserver, the help is available in a browser at the default URL ofhttp://localhost:9090/kc. The host value changes, depending on where youinstall IBM Knowledge Center. If the default port is already in use, you can changethe port value in the kc_ant.properties file in the etc directory.

If you want to provide different help to different audiences or if you want to hosthelp for product versions that are not compatible with each other, you can installmultiple instances of IBM Knowledge Center on the same computer . You renamethe additional instances to unique directory names, such as KnowledgeCenter2 andKnowledgeCenter3, and you configure the kc_ant.properties file in the etcdirectory so that each instance runs on a different port.

Maintaining taxonomy files

Each product version in the IBM software catalog has a unique taxonomy valuethat forms part of the URL for the product help on www.ibm.com. For example,the taxonomy value for Maximo Asset Management, version 7.6.0.5, isSSLKT6_7.6.0.5, and the URL for the product welcome page ishttp://www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0.5/com.ibm.mam.doc/welcome.html. The taxonomy.properties file and the KC_taxonomy.ditamap filecontrol the taxonomy values in IBM Knowledge Center.

Each help package includes a taxonomy.properties file that is specific to the productversion. You must add this file to the usr/conf directory in IBM KnowledgeCenter. If you add help packages for multiple products to IBM Knowledge Center,the usr/conf directory must contain a separate taxonomy.properties file for eachhelp package.

The KC_taxonomy.ditamap file lists each product version in the IBM softwarecatalog, and the file is frequently updated as new products and new versions ofproducts are released. A basic version of the KC_taxonomy.ditamap file is providedas a placeholder in the usr/taxonomy directory in IBM Knowledge Center but itdoes not contain a comprehensive list of product taxonomy values. You mustreplace this placeholder file with the version of the KC_taxonomy.ditamap that isincluded in the help package.

When you add multiple help packages to IBM Knowledge Center, each helppackage includes a KC_taxonomy.ditamap file. Because of the dynamic nature of thisfile, the included KC_taxonomy.ditamap files might be at different versions. Alwaysuse the most recent version of the file because taxonomy values are added to thefile incrementally.


Troubleshooting

When you start IBM Knowledge Center after adding a new help package, indexand cache files are created to enable faster search and retrieval of help topics. If thenew help topics do not show in a browser, check if subdirectories were created forthe product version in the runtime/diskcache and runtime/index directories. Ifthese subdirectories were not created, check that the taxonomy.properties fileexists in the usr/conf directory and that it contains the correct path to the mainhelp plugin in the usr/content/KCXhtml directory. If the taxonomy.properties is inthe correct location and contains the correct path to the help plugin, it is likely thatyou forgot to add the latest version of the KC_taxonomy.ditamap to theusr/taxonomy directory.

After troubleshooting, before you start IBM Knowledge Center, you can delete theproduct version subdirectories in the runtime/diskcache and runtime/indexdirectories, to ensure that the content is fully refreshed.

Help componentsHelp components include a locally-installable version of IBM Knowledge Centerand help packages that contain content plugins for product versions. You candownload a locally-installable version of IBM Knowledge Center to deploy helppackages in your local environment.

IBM Knowledge CenterA standalone help system that includes a WebSphere Application ServerLiberty, version 8.5.5.x, embedded server. IBM Knowledge Center isdistributed to Maximo customers on https://www-933.ibm.com/support/fixcentral/. IBM Knowledge Center is available for Windows, Linux, orAIX platforms and you can run IBM Knowledge Center on a localcomputer, server, or read-only media.

After you extract the IBM Knowledge Center package, you add producthelp packages to it to deploy help in your local environment. You can useIBM Knowledge Center to host help packages for several products at thesame time, if the products are on compatible release versions. If you wantto host help packages that are not compatible with one another, you canrun additional instances of IBM Knowledge Center that you configure torun on different ports.

Help packagesContain the same documentation that is available on http://www.ibm.com/support/knowledgecenter and include one or more contentplugins that contain topics in their appropriate directories and thenavigation files that control the table of contents for the topics. Helppackages also include the following files that are required by IBMKnowledge Center:v A taxonomy.properties file contains the taxonomy value for the product

version and the path to the main toc.ditamap file for the plugin orplugins in the help package.

v The KC_taxonomy.ditamap file lists the taxonomy values for all productsin the IBM software catalog. A basic version of this file is included inIBM Knowledge Center but this version of the file is not up-to-date. TheKC_taxonomy.ditamap file that is included in the help package is thecurrent version of the file when the help package is created.

Chapter 4. Installing help locally 45

https://www-933.ibm.com/support/fixcentral/

https://www-933.ibm.com/support/fixcentral/

Help packages include instructions for where to add the plugins and theadditional files to IBM Knowledge Center.

IBM Knowledge Center versionsThe locally-installable versions of IBM Knowledge Center are based onIBM Knowledge Center, version 1.5. This version has a different look andfeel to IBM Knowledge Center, version 2.0, which is onhttp://www.ibm.com/support/knowledgecenter. The functionality issimilar but there are some differences in navigation and search. PDFcreation is not supported on the locally-installable version.

When a locally-installable IBM Knowledge Center, version 2.0, is available,it will be distributed to customers who want to update their local version.

Maximo Asset Management documentation libraryThe help packages in the documentation library mirror the product catalog andinstallation environment. Either the Maximo Asset Management help package orthe Maximo Asset Management Multitenancy help package must be installed in thesame IBM Knowledge Center environment where you install help packages forindustry solutions and add-on products.

The Maximo Asset Management and Maximo Asset Management Multitenancyhelp packages contain multiple plug-ins. Help packages for industry solutions andadd-on products contain one or more plug-ins. When a help package containsmultiple plug-ins, one plug-in acts as the navigation plug-in. A navigation plug-incontains the main toc.ditamap file that controls the table of contents for allplug-ins in the help package. The taxonomy.properties file that is included in thehelp package specifies the path to the main toc.ditamap file.

Maximo Asset Management and Maximo Asset Management Multitenancy helppackages include reuse plug-ins. These plug-ins contain topics only. Consumingplug-ins control the table of contents and metadata for the reused topics. Thecontent is used extensively by other help plug-ins and you must install reuseplug-ins in IBM Knowledge Center to provide coherent content and ensure thatlinks resolve.

Maximo Asset Management help package

This help package includes the following plug-ins:

com.ibm.mam.docNavigation plug-in, containing the welcome page and product overview,and help for planning, getting started, and managing financial processes.

com.ibm.mam.inswas.docHelp for installing Maximo Asset Management on WebSphere ApplicationServer.

com.ibm.mam.inswl.docHelp for installing Maximo Asset Management on Oracle WebLogic Server.

com.ibm.mbs.docReuse plug-in, containing help for administering Maximo AssetManagement, application design, workflow design, working withMigration Manager, implementing high availability, and application help.


com.ibm.mif.docReuse plug-in, containing help for integrating Maximo Asset Managementdata with external applications.

com.ibm.support.mbs.docReuse plug-in, containing troubleshooting and support information forMaximo Asset Management and for industry solutions and add-onproducts. Troubleshooting topics for industry solutions and add-onproducts are visible only if that help plug-in is installed in IBM KnowledgeCenter.

Maximo Asset Management Multitenancy help package

This help package contains a subset of the plug-ins in the Maximo AssetManagement help package and the content is aimed at tenants in a multitenancyenvironment. You cannot install Maximo Asset Management plug-ins and MaximoAsset Management Multitenancy plug-ins in the same instance of IBM KnowledgeCenter environment. If you want to support both libraries, you must configureseparate instances of IBM Knowledge Center to support them.

This help package includes the following plug-ins:

com.ibm.mt.docNavigation plug-in, containing the welcome page and product overview,and help topics for planning, getting started, and managing financialprocesses. Content also includes topics that are specific to a tenant in amultitenancy environment.

com.ibm.mbs.docReuse plug-in. Topics are filtered to exclude information that is notrelevant to tenants in a multitenancy environment.

com.ibm.mif.docReuse plug-in. Topics are filtered to exclude information that is notrelevant to tenants in a multitenancy environment.

Industry solution and add-on help packages

The help packages for industry solutions and add-on products are intended for usewith the associated version of the Maximo Asset Management help package. Youcan check which version of Maximo Asset Management or Maximo AssetManagement is a prerequisite for an industry solution or add-on product versionat https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Other%20Maximo%20products%20system%20requirements. You can install non-recommendedversions of help packages together but some links might not resolve or some of thefeatures that are described in topics might not be available to users.

Chapter 4. Installing help locally 47

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Other%20Maximo%20products%20system%20requirements



Chapter 5. Building and deploying Maximo Anywhere apps

Before mobile users can download Maximo Anywhere apps, the apps must be builtand deployed to MobileFirst Server. This process occurs automatically for theprovided Maximo Anywhere apps during the installation of Maximo Anywhere. Ifyou change the configuration of these apps and are not using the AnywhereAdministration application, you must manually build and deploy the apps.

Application deployment process for Maximo Anywhere appsMaximo Anywhere apps are generated in the build server and then deployed tothe runtime environment, which includes MobileFirst Server.

On the build server, you use the adapter and application files to generate thedeployable files. You then deploy the project and the deployable files into theruntime environment. From MobileFirst Studio or the operating system commandline, you run commands or tasks to deploy the apps to MobileFirst Server.

The following figure shows the relationship between the build server and theruntime environment. It also shows how the project and files are deployed to theMobileFirst Server so that the apps are available for download to a mobile device.

The build server contains both the adapter and the applications. When yougenerate deployable files, the WAR file, the ADAPTER file, the WLAPP file, andthe APK, IPA, or APPX file are created. When you deploy the project and these

Figure 1. How the project and files are deployed so that they are available for download.


files to the runtime environment, which includes MobileFirst Server, theapplications and adapter are available for download to a mobile device.

The deployable files are in either the maximoanywhere_home\Anywhere\MaximoAnywhere\bin directory or the maximoanywhere_home\Anywhere\MaximoAnywhere\apps\app_name\operating_system\native\bin directory:

WAR fileA web archive (WAR) file. Each Maximo Anywhere project includes twoWAR files. The WAR files are used to package distributable applicationfiles and related project resources and to deploy them to MobileFirstServer.

To support servlet version 3.0 and servlet version 2.4 application servers,there are two WAR files:v The MaximoAnywhere.war file for servlet version 3.0 application servers,

WebSphere Application Server 8, WebSphere Application Server 8.5,WebSphere Application Server Liberty, and Apache Tomcat

v The MaximoAnywhere2.4.war file for servlet version 2.4 application server:WebSphere Application Server 7

After you install Maximo Anywhere, both of these WAR files areautomatically updated with the host information. When you deploy eitherof the WAR files to the MobileFirst Server and run the build allcommand, the MaximoAnywhere.war file is updated with the MaximoAnywhere distributable application files and related project resources.

ADAPTER fileA MobileFirst adapter that is deployed to MobileFirst Server. This filecontains server code that does tasks such as retrieving data from a remotedatabase. Adapter code is accessed by MobileFirst applications through asimple invocation API.

WLAPP fileMetadata and web resources of a Maximo Anywhere app that is deployedto MobileFirst Server. MobileFirst Server uses this file to identify mobileapps.

APPX fileA Windows mobile binary file that is ready for deployment to a mobiledevice.

APK fileAn Android mobile binary file that is ready for deployment to a mobiledevice.

IPA fileAn iOS mobile binary file that is ready for deployment to a mobile device.

You can deploy apps from MobileFirst Studio or the operating system commandline.

MobileFirst StudioMobileFirst Studio includes the Mobile Browser Simulator for testing yourapps, but it does not include the Application Center for downloading yourapps.

WebSphere Application Server Liberty profile

A dynamic profile that restricts WebSphere Application Server to use onlythe features that are required by the applications that are deployed to the


server. This profile includes the Application Center for downloading appsto mobile devices. WebSphere Application Server Liberty does not supportclustered environments.

WebSphere Application Server full profile

The full profile supports clustered environments and advancedconfigurations. WebSphere Application Server includes Application Centerfor downloading apps to mobile devices.

If you deploy apps from MobileFirst Studio, you run the adapter and appsdeployment tasks. The adapter and apps are deployed to MobileFirst Server andavailable for download.

With MobileFirst Studio, the Application Center is not available. You test yourapps by using either the Run as > Android Application menu option for Androidapps or the Run as > Xcode project for iOS apps.

For Windows apps, you test your apps by using the Run as > Visual StudioProject menu option within Visual Studio Windows Simulator.

If you deploy apps from the operating system command line, you also deploy aWAR file to MobileFirst Server. This WAR file is created during the MaximoAnywhere installation process. You deploy the WAR file with the MobileFirstServer Configuration tool. This WAR file contains properties that control theMaximo Anywhere app features, such as timeout values. Whenever you change theproperties of the apps, you need to redeploy the WAR file.

After you deploy the WAR file by using the MobileFirst Server Configuration Tool,you run the build all-deploy command. After the apps and the WAR file aredeployed to the server, mobile users can download the apps from the ApplicationCenter to their mobile devices.Related reference:“Properties files” on page 54The process for building and deploying apps requires input from configurableproperties files that belong to the application.“Maximo Anywhere directory structure” on page 56The Maximo Anywhere directory contains the files that are required to generateMaximo Anywhere apps. This directory includes predefined content for generatingmobile apps that integrate with provider applications in the enterprise system. Theapplication deployment process also generates a set of files.

Deploying Maximo Anywhere apps to MobileFirst ServerApps must be deployed to the server before they can be downloaded to mobiledevices. You can deploy apps from MobileFirst Studio or the operating systemcommand line.

Deploying apps from the command line to WebSphereApplication Server

You can deploy apps from the command line for environments that do not includeIBM MobileFirst Platform Studio but that do include one of the IBM WebSphereApplication Server profiles.

Chapter 5. Building and deploying apps 51

Before you beginv Install Maximo Anywhere.v Add users to the Maximo Anywhere security groups.v If you plan to preview the deployed apps in the MobileFirst Operations Console,

Google Chrome must be installed on the IBM Maximo Anywhere build server.The preview function for the deployed apps does not support other webbrowsers. To avoid app login issues due to cached data, you can enable privatebrowsing in Google Chrome.

v The IBM MobileFirst Platform Server instance and the Application Centerconsole must be running.

v Verify that the MobileFirst Server properties and the Application Centerproperties are correct for your environment.

Procedure1. Deploy the distributable files to the MobileFirst Server:

a. On the Maximo Anywhere build server, in the maximoanywhere_home\Anywhere\MaximoAnywhere directory, open the build.properties file.

b. Choose one of the following options for building the apps:

Option Action

To build all applications Run the build all command. This command is build.cmd onMicrosoft Windows, and build.sh on UNIX and Linuxsystems. The .apk, .ipa, or .appx artifact file is generated andall distributable files for the Maximo Anywhere project aredeployed to MobileFirst Server.

To build only someapplications

Specify a comma-separated list of apps. The possible valuesare AssetDataManager, Inspection, IssuesReturns,PhysicalCount, ServiceRequest, WorkApproval, AssetAudit,Transfers, and WorkExecution. For example, to build anddeploy the IBM Maximo Anywhere Inspection app and theIBM Maximo Anywhere Service Request app, run thefollowing command: appsToBuild=Inspection,ServiceRequest.

2. Verify deployment of the Maximo Anywhere apps in the MobileFirstOperations Console. In Google Chrome, open the MobileFirst OperationsConsole and select Preview as common resources for any Maximo Anywhereapp.

What to do nextv Install the Application Center mobile client on an Android mobile device or an

iOS mobile device so that you can download the Maximo Anywhere apps.For apps that run on Windows devices, follow the instructions for installing aWindows Store application on a Windows device and follow the instructions forlicensing and installing the product keys.

v Add digital signatures to Maximo Anywhere apps.Related information:

Application Center setup information

Mobile client setup


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/t_installing_the_client_on_an_and_mob.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/t_installing_the_client_on_a_ios_mob.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/t_ac_install_wsapp_win_dev.html


https://msdn.microsoft.com/en-us/library/windows/apps/dn832613.aspx


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/r_preliminary_information.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/r_ac_prereqs_build_client.html

Deploying apps by using MobileFirst StudioMobileFirst Studio includes an embedded instance of MobileFirst Server, whichmeans that you do not need to deploy the WAR file. MobileFirst Studio alsoincludes the Mobile Browser Simulator for testing your apps.

Before you beginv Set up Maximo Asset Management for Maximo Anywhere.v If you plan to preview the deployed apps in the Mobile Browser Simulator,

Google Chrome must be installed in the development environment. The previewfunction for deployed apps does not support other web browsers.

Procedure1. In MobileFirst Studio, import the Maximo Anywhere project.

a. Right-click inside the Project Explorer, and select Import. From the Importwindow, select Existing Projects into Workspace and click Next.

b. Browse to the maximoanywhere_home folder, select the Anywhere\MaximoAnywhere folder, select Copy projects into workspace, and clickFinish.

2. For iOS devices, set the Ant file path or, for Android devices, set the Gradle filepath.a. From the Window menu, select Preferences. Expand Ant or Gradle and

then select Runtime.b. Select Ant Home Entry or Gradle Home Entry and click Ant Home or

Gradle Home.c. In the Browse for Folder window, expand maximoanywhere_home >

Anywhere > MaximoAnywhere > build > tools > ant and click OK.3. Add the build.xml file to the Ant or Gradle view. Select the build.xml file from

MaximoAnywhere and drag the build.xml file to the Ant or Gradle view.4. Expand the build.xml file in the Ant or Gradle view and double-click the all

task.5. From the Project Explorer, deploy the adapter.

a. Select MaximoAnywhere > Adapters and right-click OSLCGenericAdapter.b. Select Run As > Deploy MobileFirst Adapter.

6. Build and deploy the Maximo Anywhere Asset Audit app.a. Under MaximoAnywhere > apps, right-click AssetAudit.b. Select Run As > Run on MobileFirst Development Server.

7. Repeat step 6 for each of the following applications:v AssetDataManagerv Inspectionv IssuesReturnsv PhysicalCountv ServiceRequestv Transfersv WorkApprovalv WorkExecution

8. Verify the application deployment in MobileFirst Operations Console byright-clicking the app and selecting Run As > Preview.


9. Test your app on your mobile device, Android emulator, or iOS Simulator. Totest the app on the Android emulator, you must first set up the emulator. Totest the app on a mobile device, connect that device to your computer.

Device type Steps

Android 1. In the Project Explorer, select theAndroid project that is under the appthat you are testing and select Run as >Android Studio project.

2. Select Launch a new Android VirtualDevice for the Android emulator orLaunch a new Android Device for anAndroid mobile device.

iOS 1. Under MaximoAnywhere > apps >app_name > iphone, select Run as >Xcode project.

2. From the Xcode window, choose thesimulated device or mobile device onwhich you want to test the app, andclick the Play icon.

Windows 1. Open Microsoft Visual Studio.

2. From the menu bar, select FILE > Open> Project/Solution.

3. From the MaximoAnywhere/apps/application_name/windows/nativedirectory, select the *.jsproj file.

4. In Visual Studio, select the index.htmlfile, and then click Simulator to run thesimulator.

Related concepts:

Mobile browser simulator

iOS SimulatorRelated tasks:“Setting up the Android emulator” on page 61The Android emulator can show you what your Android apps look like and helpyou test app behavior.“Testing apps” on page 60After you deploy an app, you must verify that data is exchanged between theenterprise system database and the mobile application. You can use a mobiledevice, the Mobile Browser Simulator, an Android emulator, or the iOS Simulatorto test apps.

Properties filesThe process for building and deploying apps requires input from configurableproperties files that belong to the application.

You can configure the app by editing the configurable properties files, or, if it isenabled, the Anywhere Administration application. If you configure the app withthe Anywhere Administration application, those configuration changes haveprecedence over any configuration changes made to the configurable propertiesfiles.


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.dev.doc/wl_studio_tools/topics/cmbswl.html

https://developer.apple.com/library/prerelease/ios/documentation/IDEs/Conceptual/iOS_Simulator_Guide/

worklight.propertiesContains application configuration properties:v MobileFirst Server database connectionv MobileFirst Server securityv Map service provider authenticationv Heartbeat intervalv Timeout and wait timesv Log line limitv Authentication methodv Maximo contextv Download and upload of attachmentsv Size of attachmentsv Location of base directory for attachmentsv Tokensv Display lock times

build.properties

Contains information about the application definition location, the APIversion, and whether an app is deployed. The build.properties file alsocontains information about the OSLC adapter and the setting for enablingdata encryption.

This file contains the properties for online and offline builds, and also theproperty for enabling a Fix Central check for any updates. If thebuild.process=offline property is set, a connection failure does not breakthe build. If the build.process=online property is set, a connection failuredoes break the build. The default value for this property is online. Toenable a check on Fix Central to see if there is an available update, set thebuild.update.check.enabled= property to true.

This file also contains the properties for MobileFirst Server, the ApplicationCenter, and the WAR file. The build.properties file defines the instance ofMobileFirst Server to which the app is deployed.

During installation, the build.properties file is copied to themaximoanywhere_home\Anywhere\MaximoAnywhere directory and updatedwith values that are provided to the installer. If you change theenvironment after you install Maximo Anywhere, the build.properties fileis not automatically updated. You might need to update thebuild.properties file in the following situations:v If you change the enterprise server in your environment, you must

change the adapter.connection properties.v If you move the WAR file from its default location on the MobileFirst

Server computer, you must change the project.config.war.file.nameproperty in the build.properties file.

v If you decide to build only a certain subset of the app files, you mustchange the build.target property. The build target determines what tobuild. Setting this property to all builds and deploys all of the files.Setting this property to mobilefirst builds the WAR file, the adapterfile, and the WLAPP file, and deploys them to the MobileFirst Server.

app-feature.propertiesContains information about the settings for features that you can enableduring the build process:


v Maps are enabled with the map.enabled propertyv GPS is enabled with the gps.enabled propertyv Bar code scanning is enabled with the barcode.enabled propertyv Attachments are enabled with the attachments.enabled propertyv Push notifications are enabled with the pushnotification.enabled

propertyv Undo actions for work order transactions are enabled with the

custom.undo.process.enabled propertyv Split panes for the IBM Maximo Anywhere Work Execution app are

enabled with the splitpane.enabled property

Maximo Anywhere directory structureThe Maximo Anywhere directory contains the files that are required to generateMaximo Anywhere apps. This directory includes predefined content for generatingmobile apps that integrate with provider applications in the enterprise system. Theapplication deployment process also generates a set of files.

The Maximo Anywhere directory includes the application definition file and a setof properties files.

File Description Path

app.xml Defines the user interface,data elements, and associatedbusiness rules for an app

maximoanywhere_home\Anywhere\MaximoAnywhere\apps\app_name\artifact

worklight.properties Contains configurationparameters for apps

maximoanywhere_home\Anywhere\MaximoAnywhere\server\conf

build.properties Contains the variable aspectsof the build process anddefines the target server towhich an app is deployed

maximoanywhere_home\Anywhere\MaximoAnywhere

app-feature.properties Contains variable aspects ofthe build process

maximoanywhere_home\Anywhere\MaximoAnywhere\apps\app_name

MaximoAnywhere.war Packages distributableapplication files and relatedproject resources and deploysthem to MobileFirst Server.

maximoanywhere_home\Anywhere\MaximoAnywhere\bin

The application deployment process generates another set of files. These files arecreated after you run the build all command from the command line or you runthe adapter and apps deployment tasks in MobileFirst Studio.


OSLCGenericAdapter.adapter Contains server adapter code maximoanywhere_home\Anywhere\MaximoAnywhere\bin

application_name.wlapp Contains server artifacts maximoanywhere_home\Anywhere\MaximoAnywhere\bin

Table 1. The directory structure of the application file and the properties files.



application_name.apk

application_name.ipa

application_name.appx

Contains client artifacts maximoanywhere_home\Anywhere\MaximoAnywhere\bin

Configuring MySQL DatabaseExtra configuration might be required before you can load mobile app .apk files tothe MobileFirst Server when MySQL Database is used. With MySQL Database, the.apk file must not be bigger than 10% of the innodb_log_file_size value.

Procedure1. Stop the WebSphere Application Server.2. Stop the MySQL service.3. From the C:\ProgramData\MySQL\MySQL Server 5.6\ directory, open the my.ini

file for editing and update the innodb_log_file_size value. For example, if the.apk file is 37 MB, the innodb_log_file_size variable must have more than 370 MBplus the sum of all other variable length fields.

4. Start the MySQL service.5. Start WebSphere Application Server.

Adding digital signatures to Maximo Anywhere appsMaximo Anywhere apps must be digitally signed before they can be run on adevice, distributed for testing, or submitted to the store.

About this task

For apps that run on Android devices, follow the instructions in the Androiddocumentation for signing Android APK files.

For apps that run on iOS devices, follow the instructions in the iOS documentationfor maintaining your signing identities and certificates.

For apps that run on Windows devices, certificates must be installed on the devicesas trusted certificates. Maximo Anywhere provides default certificates, but thesecertificates are temporary and eventually must be replaced with a certificate thatyou create. The default certificates are in the windows\native directory on eachapp. Each certificate is named MaximoAnywhere_TemporaryKey.pfx. You can updatethe certificate at any time.

Procedure1. From the mobilefirst_install_dir/MobileFirst_Platform_Server/

ApplicationCenter/installer directory, download and extract theIBMApplicationCenterWindowsStore.zip file on your device.

2. Run IBMApplicationCenter.exe.3. Enter your product key. Microsoft product keys are required for sideloading

apps that are not published to Windows Store. The product keys must belicensed in Microsoft and installed on the mobile device operating system.

Table. 2 The directory structure of the generated files.


http://developer.android.com/tools/publishing/app-signing.html

https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingCertificates/MaintainingCertificates.html

4. If you do not want to use a default certificate, create your own *.pfx certificate.This process must be completed for each app individually:a. On your development workstation, open Visual Studio Tools and

double-click the *.jsproj file that is in the windows/native directory.b. From the Solution Explorer, double-click the package.appxmanifest file, and

then click the Packaging tab.c. In the Choose Certificate dialog box, select one of the options for including

a *.pfx certificate, and click Save. The certificate is copied to thewindows\native directory for the app.

5. Start the IBM MobileFirst Platform Application Center app, and connect to yourIBM MobileFirst Platform Server.

6. After your MobileFirst Server connects, download and install the MaximoAnywhere apps onto your device.


IBM MobileFirst application authenticity overview

Deploying apps to a secure serverThe Secure Socket Layer protocol ensures secure transactions between servers andclients. The MobileFirst platform supports SSL between MobileFirst Server and theenterprise server. In Maximo Anywhere, the enterprise server is the Maximo server.

To protect the communication between a MobileFirst Server and the enterprisesystem, configure SSL for MobileFirst adapters and back-end servers.

To protect the communication between the client apps and the MobileFirst Server,configure SSL.

Installing Maximo Anywhere apps on mobile devicesFor Android and iOS devices, you install the Maximo Anywhere applications usingthe Application Center console through an internet browser. For Windows devices,the Application Center mobile client must be installed before the apps can beinstalled.

The Application Center console is a web application for managing the repository ofmobile apps. The Application Center mobile client is a secure catalog of availableWindows mobile apps. You must log in to the Application Center to download themobile client to your devices.

If you are using MobileFirst Studio and you want to run on a connected mobiledevice, under MaximoAnywhere > apps, right-click the app and select Run As >Run on device.

For Android apps, follow the instructions in the MobileFirst documentation forinstalling the client on an Android mobile device.

For apps that run on Android devices, follow the instructions for building andrunning from the command line on the Android developers website.

For apps that run on iOS devices, follow the instructions in the MobileFirstdocumentation for installing the client on an iOS mobile device.


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.dev.doc/dev/c_ibm_worklight_app_authentication_overview.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/admin/t_configuring_SSL_WL_adapters_backend_servers_certificates.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.installconfig.doc/appcenter/c_ac_ssl_config.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/t_installing_the_client_on_an_and_mob.html

http://developer.android.com/tools/building/building-cmdline.html

http://developer.android.com/tools/building/building-cmdline.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/t_installing_the_client_on_a_ios_mob.html

For apps that run on Windows devices, follow the instructions for installing aWindows Store application on a Windows device and follow the instructions forlicensing and installing the product keys.Related concepts:

The Application Center mobile clientRelated tasks:

Adding an app to the Application CenterRelated information:

Specific platform requirements

Installing Maximo Anywhere apps on Windows devicesTo install the apps on Windows devices, you must install the Application Centermobile client. The Application Center mobile client is a secure catalog of availablemobile apps.

Before you begin

Ensure that you have installed the Windows development tools and the Visual C++redistributable packages are installed on the target Windows devices.

Import your certificate PFX file into the Trusted People store on each tablet.

For Windows 8.1 devices, run Powershell and accept the terms for the developerlicense.

For Windows 10 devices, from the Settings menu, enable sideloading of apps. Formore information, see sideloading apps in Windows 10.

About this task

You can install Maximo Anywhere mobile apps on Windows 8.1 (64-bit andexcluding RT) or Windows 10 devices.

Certificates are used to sign the apps. The certificates must be installed on themobile devices as trusted certificates. Maximo Anywhere provides defaultcertificates. The default certificates are in the windows\native directory for eachapp. Each certificate is called MaximoAnywhere_TemporaryKey.pfx. This certificate istemporary and must be replaced with your own certificate.

Procedure1. From the mobilefirst_install_dir/ApplicationCenter/installer directory,

download the IBMApplicationCenterWindowsStore.zip file to your Windowsdevice.

2. Extract the IBMApplicationCenterWindowsStore.zip file, and runIBMApplicationCenter.exe.

3. Enter the Microsoft Windows product key. Product keys are required forsideloading apps that are not published in the Windows Store. The productkeys must be licensed through Microsoft and installed on the mobile deviceoperating system. For more information, see sideloading Windows apps.

4. Replace the temporary certificate with your own certificate.a. In Visual Studio Tools, open the app by double-clicking the *.jsprojfile

that is in the windows\native directory.






http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/c_the_mobile_client.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/t_adding_a_mobile_application.html

http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.appadmin.doc/appcenter/r_ac_platform_reqs.html

https://technet.microsoft.com/en-us/itpro/windows/deploy/sideload-apps-in-windows-10

https://technet.microsoft.com/en-us/windows/jj874388.aspx

b. From Solution Explorer, select the package.appxmanifest file and click thePackaging tab.

c. In the Choose Certificate window, select one of the options for including a*.pfx certificate. The certificate is copied to the windows\native directory forthe app.

d. Click Save.e. Repeat this process for each Maximo Anywhere app.

5. Start the Application Center app on your device. The context isapplicationcenter.

6. Connect to your MobileFirst Server and download and install the MaximoAnywhere apps.

Testing appsAfter you deploy an app, you must verify that data is exchanged between theenterprise system database and the mobile application. You can use a mobiledevice, the Mobile Browser Simulator, an Android emulator, or the iOS Simulatorto test apps.

About this task

Mobile device

A mobile device is the most accurate way to test apps. To test your appson a mobile device, you install the Application Center client on the mobiledevice and download the apps that you want to test.


In the Mobile Browser Simulator of MobileFirst Studio, you can test yourapps on many different types of devices. The Mobile Browser Simulatorcontains settings that you can use to duplicate the look of your devices. Toview the apps in the Mobile Browser Simulator in MobileFirst Studio, youmust configure the web browser view to use Google Chrome as theexternal web browser.

Android emulator

To test your Android apps on your workstation rather than on a mobiledevice, you can use the emulator. The emulator is not as accurate arepresentation as a mobile device. The Android emulator requires that youdownload the APK file from the Application Center unless you areworking with MobileFirst Studio.

iOS Simulator

To test your iOS apps on your workstation instead of on a mobile device,you can use the iOS Simulator. The iOS Simulator is not as accurate arepresentation as a mobile device.

Visual Studio Windows Simulator

To test your Windows apps on your workstation instead of on a mobiledevice, you can use the Windows Simulator. The Windows Simulator is notas accurate a representation as a mobile device.

Procedure1. Log in to a Maximo Anywhere app and search for a known work order.


2. In a Maximo Asset Management application, such as Work Order Tracking, usethe same search criteria.

3. Compare the results to ensure that they are the same.Related concepts:


iOS Simulator

Visual Studio Windows Simulator

Setting up the Android emulatorThe Android emulator can show you what your Android apps look like and helpyou test app behavior.

Before you beginv Install the Oracle Java Development Kit.v Install the Android Software Development Kit.

If you are testing a new instance of a previously deployed application, clear thebrowser cache. In Google Chrome, go to Settings > Apps, and select the appwhose data you want to clear. Click Clear Data.

Procedure1. From the AndroidSDK\adt-bundle-windows-x86_64\eclipse directory, run the

SDK Manager.exe file.2. In the SDK Manager, select Tools > AVD Manager and click New.3. In the CPU/ABI field, select Intel Atm (x86).4. Select the Hardware keyboard present check box and the Display a skin with

hardware controls check box.5. For SD Card Size, enter 1 GB and click OK.6. Select your Android Virtual Device (AVD) and click Start.7. Install the Application Center mobile client on the emulator.

a. From a browser, enter the following URL: http://hostname:portnumber/appcenterconsole/installers.html where hostname is the address of theserver and portnumber is the number of the port where the ApplicationCenter is installed.

b. Enter your user name and password.c. Click IBM App Center and Install Now.d. On the Notification tab, select the downloaded APK file.e. At the prompt, scroll to the bottom of the window and click Install.

8. Start the Application Center and download the apps that you want to test onyour emulator.


http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.dev.doc/wl_studio_tools/topics/cmbswl.html

https://developer.apple.com/library/prerelease/ios/documentation/IDEs/Conceptual/iOS_Simulator_Guide/

https://msdn.microsoft.com/en-us/library/hh441475.aspx

Chapter 6. Uninstalling Maximo Anywhere, MobileFirst Server,and MobileFirst Studio

You use Installation Manager to uninstall Maximo Anywhere, the mobile apps, andMobileFirst Server. If MobileFirst Studio is installed, you uninstall it from theEclipse client.

Procedure1. To uninstall Maximo Anywhere, the mobile apps, and MobileFirst Server:

Option Description

On Windows 1. Click Start > All programs > IBMInstallation Manager.

2. Start the IBM Installation Managerprogram and click Uninstall.

3. Select the packages that you want touninstall and complete the wizard.

4. Manually remove any residual folders,for example, \Anywhere\MobileFirst_Platform_Server.

5. Restart the server.

On Mac OS X 1. In the /Users/administrator directory,open the file Maximo_install.location.

2. Record the IM_install_dir property. Forexample, /Users/administrator/IBM/anywhereinstall/eclipse=IM_install_dir.

3. Change directory to the IM_install_dirdirectory and start Installation Manager.

4. Select Uninstall and select the packagethat you want to uninstall.

5. Complete the uninstallation wizard.

2. To uninstall MobileFirst Studio:a. In Eclipse, click Help > About Eclipse > Installation Details.b. From the Installed Software tab, select the following items and complete the

wizard:v IBM Dojo Mobile Toolsv IBM jQuery Mobile Toolsv IBM MobileFirst Platform Studio

3. To remove the MaximoAnywhere project:a. In Eclipse, from the Project Explorer window, right-click the

MaximoAnywhere project.b. Select Delete.c. Select Delete project contents on disk and click OK.


Notices

This information was developed for products and services offered in the US. Thismaterial might be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

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 user's 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 Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

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 jurisdictions do not allow disclaimer ofexpress or implied warranties in certain transactions, therefore, this statement maynot apply to 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 websites are provided forconvenience only and do not in any manner serve as an endorsement of those


websites. The materials at those websites are not part of the materials for this IBMproduct and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide 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:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

The performance data and client examples cited are presented for illustrativepurposes only. Actual performance results may vary depending on specificconfigurations and operating conditions.

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.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

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 actual people or business enterprises is entirelycoincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. The sample


programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the followingterms and conditions.

Applicability

These terms and conditions are in addition to any terms of use for the IBMwebsite.

Personal use

You may reproduce these publications for your personal, noncommercial useprovided that all proprietary notices are preserved. You may not distribute, displayor make derivative work of these publications, or any portion thereof, without theexpress consent of IBM.

Commercial use

You may reproduce, distribute and display these publications solely within yourenterprise provided that all proprietary notices are preserved. You may not makederivative works of these publications, or reproduce, distribute or display thesepublications or any portion thereof outside your enterprise, without the expressconsent of IBM.

Rights

Except as expressly granted in this permission, no other permissions, licenses orrights are granted, either express or implied, to the publications or anyinformation, data, software or other intellectual property contained therein.

Notices 67

http://www.ibm.com/legal/us/en/copytrade.shtml

IBM reserves the right to withdraw the permissions granted herein whenever, in itsdiscretion, the use of the publications is detrimental to its interest or, asdetermined by IBM, the above instructions are not being properly followed.

You may not download, export or re-export this information except in fullcompliance with all applicable laws and regulations, including all United Statesexport laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESEPUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUTWARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDINGBUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY,NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy StatementIBM Software products, including software as service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

Depending upon the configurations deployed, this Software Offering may usesession and persistent cookies that collect each user’s name, user name, password,or other personally identifiable information for purposes of session management,authentication, single sign-on configuration or other usage tracking or functionalpurposes. These cookies can be disabled, but disabling them will also likelyeliminate the functionality they enable.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM's Online Privacy Statement at http://www.ibm.com/privacy/details in thesection entitled “Cookies, Web Beacons and Other Technologies” and the "IBMSoftware Products and Software-as-a-Service Privacy Statement" athttp://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details



Notices 69

IBM®

Printed in USA

with IBM Corp....an integrated development envir onment. Mobile devices The Maximo Anywher e mobile...

Documents

Transcript of with IBM Corp....an integrated development envir onment. Mobile devices The Maximo Anywher e mobile...