Planning, Installation, and Deployment

IBM Maximo Anywhere Version 7 Release 5.2

Planning, installation, and deployment

IBM Note Before using this information and the product it supports, read the information in “Notices” on page 51.

This edition applies to version 7, release 5, modification 2 of IBM Maximo Anywhere and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 2013, 2015. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents

Chapter 1. Planning to deploy Maximo Adding users to the Maximo Anywhere security Anywhere ...... 1 groups ...... 32 System architecture and components ...... 1 Maximo Anywhere security groups in Maximo System requirements for Maximo Anywhere, Asset Management ...... 33 MobileFirst Server, and MobileFirst Studio .... 4 Enabling Maximo Asset Management Deployment topologies ...... 6 applications for maps and labor reporting ... 34 Development environment...... 7 Maximo Asset Management system options that Single-server deployment of Maximo Anywhere affect mobile apps ...... 34 and MobileFirst Server ...... 8 Upgrading Maximo Anywhere ...... 35 Multiple-server deployment of Maximo File location changes in version 7.5.2 ..... 36 Anywhere and MobileFirst Server ...... 10 Application definition changes in version 7.5.2 . 36 Installation overview ...... 12 Installation planning worksheet ...... 14 Chapter 3. Building and deploying Installation checklist for Maximo Anywhere ... 15 Maximo Anywhere apps ...... 39 Application deployment process for Maximo Chapter 2. Installing the Maximo Anywhere apps ...... 39 Anywhere components...... 17 Deploying Maximo Anywhere apps to MobileFirst Installing the Maximo Asset Management required Server ...... 41 components ...... 17 Deploying apps from the command line to Installing MobileFirst Server ...... 17 WebSphere Application Server ...... 41 Setting the Java heap size on the JVM for Deploying apps by using MobileFirst Studio .. 42 WebSphere Application Server or WebSphere Properties files ...... 44 Application Server Liberty ...... 18 Maximo Anywhere directory structure .... 45 Installing MobileFirst Server by using the Adding digital signatures to Maximo Anywhere installation program ...... 18 apps...... 46 Installing the MobileFirst Server Administration Deploying apps to a secure server ...... 46 Services ...... 19 Installing Maximo Anywhere apps on mobile Preparing the Maximo Anywhere environment .. 21 devices ...... 46 Installing the Android development tools ... 21 Testing apps ...... 47 Installing the iOS development tools ..... 23 Setting up the Android emulator ...... 48 Installing Maximo Anywhere ...... 25 Creating a MobileFirst runtime environment ... 26 Chapter 4. Uninstalling Maximo Installing an integrated development environment 27 Anywhere, MobileFirst Server, and Silent mode: Installing Maximo Anywhere .... 28 MobileFirst Studio ...... 49 Recording a response file for silent installation . 28 Installing the required components in silent Notices ...... 51 mode ...... 29 Privacy Policy Considerations ...... 52 Installing Installation Manager in silent mode .. 30 Trademarks ...... 53 Parameters for silent mode installation ... 30 Installing Maximo Anywhere in silent mode .. 31 Setting up Maximo Asset Management for Maximo Anywhere ...... 32

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

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

During the Maximo Anywhere installation, you must perform tasks that are outlined in the IBM MobileFirst Platform Foundation version 6.3.0 IBM Knowledge Center (www.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/ wl_welcome.html). Before you install Maximo Anywhere, read the installation and deployment information.

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

System architecture and components Maximo Anywhere and MobileFirst form a mobile application platform that integrates with the Maximo® Asset Management enterprise system. Maximo Anywhere provides the content that is required to build mobile apps for Maximo Asset Management. The MobileFirst components function as middleware by enabling integration with the enterprise system and by supporting the deployment of apps to mobile devices.

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

The following figure shows the system architecture of Maximo Anywhere and highlights the relationship with key components in Maximo Asset Management and MobileFirst.

Maximo Anywhere build server

Maximo Maximo Anywhere project administrative workstation App Adapter

Build EAR file Build and deploy

Runtime environment

Maximo enterprise application MobileFirst server

OSLC service MobileFirst Application Center provider Login Console Data module Native apps

Adapter

Maximo database

Data Install

MobileFirst Mobile device database

Maximo Anywhere app

Local data store

Figure 1. Maximo Anywhere system architecture and components

The following required components must be deployed to the Maximo Asset Management environment to support the Maximo Anywhere apps: Maximo Integration Framework 7.5.1.2 This framework is required to enable the integration between Maximo Asset Management and external applications. The Integration Framework includes the OSLC capabilities and service providers that are used by the Maximo Anywhere apps to retrieve and process enterprise data. For Maximo Asset Management 7.5 environments, the Integration Framework is installed with the required components package. Maximo Asset Management 7.6 environments include the Integration Framework. IBM OSLC Content package 7.5.2.0 OSLC resources define the metadata for business objects of OSLC service providers. The OSLC resources are used by the mobile apps to retrieve and process application data from the service providers in Maximo Asset Management. Maximo Anywhere Enablement 7.5.2 The enablement package includes application files, license enablement, and

2 Planning, installation, and deployment cron task automation. The enablement package also includes the Anywhere Administration application, which is deployed as part of the MaximoAnywhere project.

The following components are deployed when you implement Maximo Anywhere: IBM Maximo Anywhere A collection of resources that are required for integration and deployment on the MobileFirst platform. These resources include a MobileFirst-compatible project and an OSLC adapter. The OSLC adapter manages communications between MobileFirst Server and the provider application, Maximo Asset Management. Before run time, the Maximo Anywhere project WAR, the applications, and the OSLC adapter must be deployed 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 Edition A runtime container for the OSLC adapter and server-based application components. MobileFirst Server includes an administrative console and an app store for publishing mobile apps within the organization. MobileFirst Server must be deployed to an application server. The same application server can be used to deploy both Maximo Asset Management and MobileFirst Server. Application Center The Application Center is an enterprise app store that you can use for deploying the Maximo Anywhere apps to mobile devices in your organization. Application Center is automatically installed with MobileFirst Server. Application Center is composed of a server component, a repository, the Application Center console, and a mobile client app. v Server component: The server component is a Java™ Enterprise application that must be deployed in a web application server, such as WebSphere® Application Server. The server component consists of an administration console and a mobile client. The mobile client installs the apps that are available to the client component. Several services compose the Application Center server component, such as a service that lists the available apps, and a service that delivers the app 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 as feedback 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 to manage the repository. You must have system administrator privileges to access the Application Center console. v Mobile client: The mobile client runs on mobile devices and is used to install the apps that reside in the repository. IBM MobileFirst Platform Studio for MobileFirst Consumer Edition (Optional) An Eclipse-based integrated development environment that can be deployed with Maximo Anywhere.

Chapter 1. Planning to deploy Maximo Anywhere 3 MobileFirst Studio is installed as an Eclipse add-on by using a P2 Eclipse update. MobileFirst Studio is used to configure and test the Maximo Anywhere 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 to extend and complement the capabilities that are available in the product itself. Map services The map view in the Maximo Anywhere Work Execution app uses positioning data that is provided by Maximo Asset Management. Maximo Asset Management can be configured to obtain this positioning data from ArcGIS, an external geographic information system. You can also configure the map view to show a route and directions between work order locations. To support this configuration, you must have permissions from the map service provider, Esri. Mobile Device Management You can deploy IBM MaaS360 Mobile Device Management with Maximo Anywhere to complement the mobile app management capabilities that MobileFirst provides. IBM MaaS360 Mobile Device Management provides mobile device management capabilities, including security management, for your mobile organization.

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

A complete list of hardware and software requirements for your product is available in the Maximo Anywhere information in the System Requirements section of the Maximo Asset Management wiki (www.ibm.com/developerworks/ community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset %20Management/page/Maximo%20Anywhere%20system%20requirements).

The MobileFirst system requirements are available in the IBM Support Portal (www.ibm.com/support/docview.wss?uid=swg27024838).

Administrative user rights are required for all computers that are used for the Maximo Anywhere 7.5.2 installation. Enterprise system Tivoli®'s process automation engine is the enterprise platform for products such as IBM Maximo Asset Management, IBM TRIRIGA® Application Platform, and Maximo industry solutions. The process automation engine and the supporting middleware together comprise the enterprise system. Maximo Anywhere 7.5.2 must be installed with Maximo Asset Management 7.5.0.6 or later, or version 7.6. Maximo Integration Framework version 7.5.1.2 is also required and is included as an iFix for Maximo Asset Management 7.5.0.6 or later versions. If Maximo Asset Management 7.6 is installed, the correct version of the Integration Framework might already be deployed. The installation program detects the required components if they are already installed.

4 Planning, installation, and deployment The Maximo Integration Framework component includes OSLC object structures that the enterprise system requires to support Maximo Anywhere. With OSLC integration, the enterprise applications can share data with Maximo Anywhere. You can verify that the required components are installed by logging into Maximo Asset Management and selecting Help > System Information. Maximo Anywhere supports IBM Maximo Spatial Asset Management 7.5.0.1 to provide positioning information that determines the location of a work order on a map. Maximo Spatial Asset Management is an optional component. If Maximo Spatial Asset Management is not in your environment, positioning information is obtained by using non-linked objects. Maximo Anywhere version 7.5.2 To configure, build, and deploy the Maximo Anywhere mobile apps, the following prerequisite software must be installed. v The Oracle Java Development Kit (JDK) is a prerequisite for Android development, and its subcomponent, the Java Runtime Environment (JRE), is required to run MobileFirst Studio. v The Android SDK is required to build the Maximo Anywhere apps for Android mobile devices. v To install mobile apps on iOS devices, a set of Apple-registered accounts is required so that you can build the iOS apps in your environment. If you are installing Maximo Anywhere on a Mac OS X computer, you must install the iOS development tools first. v Xcode IDE is required to build the Maximo Anywhere apps so that they can be deployed on iOS mobile devices. v To set up an integrated development environment, you must install Eclipse IDE for Java EE Developers and MobileFirst Studio. v To preview the deployed applications in the MobileFirst Studio mobile browser simulater, you must install Google Chrome. IBM MobileFirst Platform Server 6.3.0 MobileFirst Server is required to deploy Maximo Anywhere in a production environment. You must deploy MobileFirst Server on a Windows, Linux, or AIX® computer. MobileFirst Server must be deployed to an application server. The application server can be configured with a specific profile for MobileFirst Server. For iOS devices that are operating at version 7.1 or later, you must configure the application server to use SSL security. In a production environment, MobileFirst Server requires a production-grade database instance. You can configure an existing database server for MobileFirst Server by creating a database instance or database schemas.

Application servers v IBM WebSphere Application Server Liberty v IBM WebSphere Application Server v Apache Tomcat

Chapter 1. Planning to deploy Maximo Anywhere 5 Databases v Apache Derby. Included in the installation image. Apache Derby is supplied for evaluation and testing purposes only and is not a production-grade database. v IBM DB2® v Oracle Database v MySQL Database

Table 1: Supported application servers and databases.

For compatible products and versions, see the IBM MobileFirst Platform Foundation 6.3.0 detailed system requirements (www.ibm.com/support/ docview.wss?uid=swg27024838).

Restrictions: v The Mac OS X operating system does not support MobileFirst Server. You can install MobileFirst Studio on a Mac OS X development environment, but you must deploy MobileFirst Server to a computer with a different operating system. v MobileFirst Server does not support Oracle WebLogic Server. If your enterprise environment runs WebLogic Server, install one of the supported application servers to host MobileFirst Server. v MobileFirst Server does not support Microsoft SQL Server. v IBM WebSphere Application Server and IBM WebSphere Application Server Liberty do not support MySQL Database. IBM MobileFirst Platform Studio You must install Oracle JDK before you install MobileFirst Studio. The Oracle JDK includes the Java Runtime Environment (JRE), which MobileFirst Studio requires to build the Maximo Anywhere applications. To configure the mobile apps, install the required development tools in combination with MobileFirst Studio. For more information, see Installing an integrated development environment. Mobile devices The Maximo Anywhere mobile apps can be deployed to Android or iOS mobile devices. In a development environment, you can also test the apps in the MobileFirst Studio mobile browser simulator, the Android Emulator, or the iOS Simulator. For a full list of operating systems and supported screen sizes, see the Maximo Anywhere system requirements (www.ibm.com/developerworks/ community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset %20Management/page/Maximo%20Anywhere%20system %20requirements).

Deployment topologies A development environment is created by installing Maximo Anywhere and MobileFirst Studio on the same computer. A production environment is created by installing Maximo Anywhere and MobileFirst Server in a single-server or multiple-server deployment.

6 Planning, installation, and deployment You use a development environment to configure and test the Maximo Anywhere mobile apps before they are deployed to the production server. A test instance or a development instance of Maximo Asset Management is required, either on the same computer or on a remote computer.

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

For medium and large enterprises, creating a production environment involves installing the components on more than one computer. MobileFirst Server must first be deployed to an application server. A production instance of Maximo Asset Management must be available on a different computer than the Maximo Anywhere and MobileFirst components.

MobileFirst Studio is an optional integrated development environment. If you want to use MobileFirst Studio to test, configure, and build the Maximo Anywhere applications, you must install it on the same computer as the Maximo Anywhere component.

The Maximo Anywhere computer functions as a build server from which the application build and deployment processes are run. Cluster environments

To introduce high availability and scalability to your Maximo Anywhere deployment, you can set up a MobileFirst Server cluster environment. The MobileFirst cluster can be integrated with a basic or advanced enterprise system topology.

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

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

Hardware-based or software-based load balancers regulate the data activity across multiple web servers. For more information, see the clustering information in the IBM MobileFirst Platform Foundation 6.3.0 IBM Knowledge Center. Related information: Optimizing system performance Clustering of MobileFirst Server Development environment A development environment can be used to configure, test, and build the Maximo Anywhere mobile apps before they are deployed to a production environment.

Chapter 1. Planning to deploy Maximo Anywhere 7 To create a development environment, you install MobileFirst Studio and Maximo Anywhere on a single computer. A test instance or a development instance of Maximo Asset Management is also required, either on the same computer or on a remote computer.

Maximo Asset Management

MobileFirst Studio Maximo Anywhere

Figure 2. A Maximo Anywhere development environment

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

MobileFirst Studio is an Eclipse-based integrated development environment. You must install MobileFirst Studio within an existing Eclipse client. Update your Eclipse environment by installing the development tools for the Android or iOS mobile platform. Example: Creating an Android development environment

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

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

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

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

If using Maximo Asset Management 7.6, he runs the Configuration Tool to update 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 Maximo Anywhere mobile apps. He can build the apps and deploy them to the Android Emulator. Single-server deployment of Maximo Anywhere and MobileFirst Server For small enterprises, a single-server deployment can be used for production purposes. Larger enterprises can use a single-server deployment as a pre-production test environment.

8 Planning, installation, and deployment To create a single-server deployment, you install MobileFirst Server and Maximo Anywhere on a single computer. A test instance or a production instance of Maximo Asset Management is also required, either on the same computer or on a remote computer.

Maximo Asset Management

MobileFirst Server Maximo Anywhere

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

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

You can also configure an existing production database, such as DB2, Oracle Database, or MySQL Database. MobileFirst Server includes a test database, Apache Derby.

To configure the Maximo Anywhere applications for your organization, you modify the properties files and the application definitions. You can build, deploy, and preview the mobile apps in the MobileFirst Operations Console. You can then deploy the apps to the Application Center where mobile workers can download them to a mobile device. Example: Creating a single-server deployment

Ian is a system administrator who is responsible for implementing Maximo Anywhere in a small enterprise. He wants to create a small-scale production environment.

Ian performs any necessary backup of the system and sets up a production instance 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 Asset Management is installed.

If using Maximo Asset Management 7.6, he runs the Configuration Tool to update the database and rebuild and redeploy the Maximo EAR files.

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

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

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

Chapter 1. Planning to deploy Maximo Anywhere 9 Multiple-server deployment of Maximo Anywhere and MobileFirst Server A multiple-server deployment is suitable for medium and large enterprises and is deployed by installing Maximo Anywhere and MobileFirst Server on separate computers. A production instance of Maximo Asset Management on a remote computer is also required.

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

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

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

HTTP/HTTPS MobileFirst web server load balancer

Maximo Anywhere apps

MobileFirst server MobileFirst database cluster

Application server Maximo Anywhere build server

HTTP/HTTPS Enterprise system environment

Web server load balancer

OSLC provider Maximo database cluster

Application server Firewall

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

The MobileFirst Server cluster supports only multiple instances of WebSphere Application Server.

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

10 Planning, installation, and deployment The MobileFirst Server cluster and the OSLC provider cluster can be integrated in an advanced enterprise system topology.

HTTP/HTTPS MobileFirst MobileFirst MobileFirst web server load server cluster database balancer

Maximo Application Anywhere server apps

Maximo Anywhere build server

Enterprise system environment OSLC provider cluster

Application server

User interface cluster

Application server Maximo database Integration cluster

Application server

HTTP/HTTPS Web server load HTTP/HTTPS balancer

Maximo Asset Cron Management cluster applications Application server Reporting database Reporting cluster

Application Firewall server

Figure 5. A Maximo Anywhere multiple-server deployment (advanced topology) Example: Creating a multiple-server deployment

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

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

Ian installs or identifies an application server for use with MobileFirst Server. For example, he installs WebSphere Application Server Liberty or creates a new instance of WebSphere Application Server.

Chapter 1. Planning to deploy Maximo Anywhere 11 On the computer where Maximo Asset Management is installed, Ian starts the launchpad and installs the Maximo Asset Management required components.

If using Maximo Asset Management 7.6, he runs the Configuration Tool to update the database and rebuild and redeploy the Maximo EAR files.

On a designated host server computer, Ian starts the launchpad and installs MobileFirst Server. He starts the MobileFirst Server Configuration Tool and installs the 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 Server computer.

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

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

When the configuration is complete, Ian can download the Maximo Anywhere apps from the Application Center and install them on a mobile device. Related tasks: Configuring the application server Related information: Typical topologies of an IBM Worklight instance Clustering with Worklight Server

Installation overview The Maximo Anywhere installation involves preparing target computers and existing middleware for installation, and installing key components for Maximo Anywhere and MobileFirst Server.

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

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

Ensure that Maximo Asset Management 7.5.0.6 or later, or version 7.6 is installed.

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

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

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

12 Planning, installation, and deployment A cluster is created by implementing multiple host servers or by configuring multiple JVMs. If you want to set up a MobileFirst cluster, do so before you install MobileFirst Server and Maximo Anywhere.

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

Administrative user rights are required to install all of the components that are delivered with Maximo Anywhere version 7.5.2. You must have root user authorization for UNIX and Linux systems. Required components

Maximo Asset Management requires a set of components to be deployed before Maximo Anywhere is installed. The Maximo Asset Management required components include OSLC object structures and licenses to enable a set of extra applications in Maximo Asset Management. Maximo Integration Framework must also be installed. The Service Address application is used with the map feature and the Crews and Crew Types applications are used for labor reporting. The Anywhere Administration application allows you to administer the Maximo Anywhere mobile apps from one central location. Maximo Anywhere, MobileFirst Server, and MobileFirst Studio

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

In most production environments, MobileFirst Server is installed on a different computer than Maximo Anywhere. You must deploy MobileFirst Server to an application server before you install Maximo Anywhere. You can install MobileFirst Studio and Maximo Anywhere on the same target computer and streamline the configuration and testing of the mobile apps before they are deployed. Silent installation

A silent installation is useful for installing Maximo Anywhere and MobileFirst Server 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 by firewalls, so system administrators can be prevented from using the launchpad to install the components. v You are installing the components on a computer that cannot display an Eclipse user interface.

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

Chapter 1. Planning to deploy Maximo Anywhere 13 Silent installations that are conducted with Installation Manager are defined by an XML response file. The response file can be used to install, update, and uninstall products.

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

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

Variable Default value Example value Your value Maximo Anywhere Windows: C:\IBM\Anywhere installation directory UNIX and Linux: opt/ibm/Anywhere MobileFirst Server On Windows: http Administration protocol On Mac OS X: https MobileFirst Server hostname.yourdomain.com or Administration host name 1.234.567.89 or localhost MobileFirst Server 9080 Administration port (Stand-alone server) MobileFirst Server 10080 Administration port (Embedded server) MobileFirst Server wladmin Administration context root MobileFirst Server MaximoAnywhere Administration runtime context root MobileFirst Server Administration user name MobileFirst Server Administration password Application Center protocol On Windows: http

On Mac OS X: https Application Center host hostname.yourdomain.com or name 1.234.567.89 or localhost Application Center port On Windows, UNIX, and Linux: 9080

On Mac OS X: none Application Center context applicationcenter root Application Center user appcenteradmin name

14 Planning, installation, and deployment Variable Default value Example value Your value Application Center password Android platform directory C:\Users\Administrator\ Downloads\android- sdk_r22.6.2-windows\ android-sdk-windows\ platforms\android-19 Oracle JDK directory Windows: C:\Program Files\Java

UNIX and Linux:/usr/java Maximo Server protocol http Maximo Server host name hostname.yourdomain.com or 1.234.567.89 or localhost Maximo Server port Maximo Server context root maximo

Related reference: Installation program log files

Installation checklist for Maximo Anywhere You can use the checklist to ensure that all installation steps completed successfully. Print this topic and check each task as you complete it. Preparing for installation

Done Task Ensure that your environment meets all of the software and hardware requirements for Maximo Anywhere and IBM MobileFirst Platform Foundation. Print the installation planning worksheet and use it during the installation.

Installing IBM Maximo Anywhere

Done Task On the computer where Maximo Asset Management 7.5.0.6 or 7.6 is installed, download the Maximo Anywhere product software from IBM® Passport Advantage® and install the Maximo Asset Management required components. Create or identify a database instance to use with MobileFirst Server. Install or identify an application server to use with MobileFirst Server. On a designated server computer, install MobileFirst Server.

Chapter 1. Planning to deploy Maximo Anywhere 15 Done Task Install the MobileFirst Server Administration Services by using the configuration tool. On a designated build computer, prepare the Maximo Anywhere environment. On the build computer, install Maximo Anywhere. On the MobileFirst Server computer, add a MobileFirst runtime environment by using the configuration tool. 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. If your computer is a UNIX or Linux system, use the build.sh file. This step generates the distributable files for the Maximo Anywhere project and deploys them to MobileFirst Server. Install the Maximo Anywhere apps on mobile devices. Optional: To create an integrated development environment, install MobileFirst Studio on the computer where Maximo Anywhere is installed.

Configuring IBM Maximo Anywhere and Maximo Asset Management

Done Task Add users to the Maximo Anywhere security groups. Enable Maximo Asset Management applications for maps and labor reporting. Set up Maximo Asset Management to include the following data: v Ensure that your user has an associated labor code. v Ensure that your user has authorization to at least his own labor code. v Ensure that your user has a default insert site defined. v Ensure that your user has a default time zone defined.

Verifying the installation

Done Task Test the Maximo Anywhere apps on mobile devices.

16 Planning, installation, and deployment Chapter 2. Installing the Maximo Anywhere components

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

Installing the Maximo Asset Management required components You extend Maximo Asset Management with components that include OSLC object structures and licenses that enable a set of applications. Before you begin

Install Maximo Asset Management 7.5.0.6 or later, or version 7.6. Procedure 1. On the computer where Maximo Asset Management is installed, download the Maximo Anywhere product software from IBM Passport Advantage® and extract the installation image to a local directory. 2. Start the launchpad by double-clicking the launchpad file. If your computer is a 64-bit system, use the launchpad64 file. 3. On the Install IBM Maximo Asset Management Required Components pane, click Install. If you are using Maximo Asset Management 7.5.0.6 or later, you must select the installation directory first. 4. Complete the installation wizard. 5. If you are using 7.6 Maximo Asset Management, complete the configuration wizard. If you are using Maximo Asset Management 7.5.0.6 or later, change to the tpae_home\maximo\tools\maximo directory and run updatedb. Then, build and deploy the Maximo EAR files. 6. Verify that the required components are installed by logging in to Maximo Asset Management and selecting Help > System Information. Ensure that IBM Maximo Integration Framework 7.5.1.2 or later is listed as one of the installed components. What to do next

If you plan to install Maximo Anywhere and MobileFirst Server on different computers, copy the installation image to the target computers. Related information: Building and deploying EAR files for basic configurations

Installing MobileFirst Server The installation program automatically creates a database instance for the MobileFirst Server environment. It also configures the application server that you assign to MobileFirst Server. Before you begin

Before you install MobileFirst Server, consider whether to use the automated method or to create a database instance manually. By using the manual method,

For more information about planning the creation of databases, see the IBM MobileFirst Platform Foundation IBM Knowledge Center (www.ibm.com/support/ knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.installconfig.doc/ install_config/c_wlserver_plan_install.html). Setting the Java heap size on the JVM for WebSphere Application Server or WebSphere Application Server Liberty To improve the performance of the MobileFirst Server, you must increase the java heap size that is used by the Java virtual machine (JVM). You can set the Java heap size 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: -Xmsm v Maximum Java heap: -Xmxm

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

You can override the default values by modifying the values in the jvm.options file in the installation directory. Procedure 1. Stop the server by running the following command: websphere_home\bin\server stop 2. Browse to the websphere_home\usr\servers\defaultServer\type directory and open 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 Installing MobileFirst Server by using the installation program In a Maximo Anywhere deployment, MobileFirst Server includes three main components: MobileFirst Server Administration Services, MobileFirst Operations Console, and Application Center. You must deploy MobileFirst Server to an application server. Before you begin v Ensure that you installed the required components on the Maximo Asset Management administrative workstation.

18 Planning, installation, and deployment v The installer for WebSphere Application Server Liberty is provided with MobileFirst. v Ensure that your environment includes one of the application servers that MobileFirst supports. For more information, see the system requirements for Maximo Anywhere, MobileFirst Server, and MobileFirst Studio. 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 WebSphere Application Server or WebSphere Application Server Liberty before you install MobileFirst Server. About this task

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

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

When you start Installation Manager, you can check for the latest fix packs. Your IBM login credentials are required to access the fix pack download site. Procedure 1. Start the launchpad by double-clicking the launchpad file. If your computer is a Windows system, use the launchpad64.exe file. If your computer is a UNIX or Linux system, use the launchpad.sh file. 2. On the Install IBM MobileFirst Server pane, click Install. 3. 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 (www.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/ com.ibm.worklight.installconfig.doc/admin/c_completing_the_installation.html). Related tasks: “Setting the Java heap size on the JVM for WebSphere Application Server or WebSphere Application Server Liberty” on page 18 To improve the performance of the MobileFirst Server, you must increase the java heap size that is used by the Java virtual machine (JVM). You can set the Java heap size for the application server by modifying the jvm.options file. Related information: Planning the creation of databases Creating a profile for a WebSphere Application Server Manually installing MobileFirst Server administration Manually installing Application Center Installing the MobileFirst Server Administration Services After MobileFirst Server is installed, you must install and configure the Administration Services by using the MobileFirst Server Configuration Tool.

Chapter 2. Installing the Maximo Anywhere components 19 Before you begin

Verify that the Application Center Console is installed by entering the Application Center 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 be used later in the installation.

For more information about the tasks that can be completed by using the MobileFirst Server Configuration Tool, see the IBM MobileFirst Platform Foundation 6.3.0 IBM Knowledge Center (www.ibm.com/support/ knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.installconfig.doc/ install_config/t_wlconsole_install.html). Procedure 1. On the computer where MobileFirst Server is installed, start the Server Configuration Tool.

Option Description On Windows In the Start menu, click IBM MobileFirst Platform Server 6.3 > Server Configuration Tool. On Linux In the desktop menu, click IBM MobileFirst Platform Server 6.3 > Server Configuration Tool. On Mac OS X In the Finder, browse to the mf_server_home/shortcuts/ directory and double-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 MFAnywhereConfig. 4. On the Configurations Details pane, record the context root value for the MobileFirst Administration Services in the planning worksheet. Click Next. The default context root value is /wladmin. 5. On the Console Settings pane, record the context root value for the MobileFirst Operations Console in the planning worksheet. The context root value can be used to log in to the MobileFirst Operations Console and administer the Maximo Anywhere apps after Maximo Anywhere is installed. The default context root value is /worklightconsole. 6. In the Database Properties window, specify the database properties that you selected during the MobileFirst Server installation. 7. In the Application Server Choice window, specify the Application Center properties that you selected during the MobileFirst Server installation. Record the user name and password values in the planning worksheet. The user name and password are required to access the MobileFirst Administrative Services as part 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.

20 Planning, installation, and deployment Preparing the Maximo Anywhere environment Before you can build and deploy the Maximo Anywhere apps, you must set up the computer on which Maximo Anywhere is installed. About this task

To build the apps for iOS mobile devices, a Mac OS X computer with specific software is required. Procedure 1. Prepare the environment for building the mobile apps:

Android Install the Android development tools. iOS Install the iOS development tools.

2. Optional: Install an integrated development environment. Installing the Android development tools Oracle JDK and Android SDK are required to build Android mobile apps. Procedure 1. Install Oracle JDK version 7.0. a. From the Oracle Java SE downloads page (www.oracle.com/technetwork/ java/javase/downloads/jdk7-downloads-1880260.html), download the Java SE Development Kit for your operating system. b. Run the executable file and proceed through the installation program. c. Set the JAVA_HOME environment variable and specify the path to the directory where the JDK was installed:

Chapter 2. Installing the Maximo Anywhere components 21 Windows 1. Go to your computer's Advanced System Settings. 2. On the Advanced tab, click Environment Variables. 3. Under System Variables, click New. 4. Specify JAVA_HOME as the variable name and enter the path to the JDK installation directory as the variable value. Environment variable values cannot be separated by a space. If the Java installation directory contains a space in the path name, specify the shortened path name. For example, on Windows operating systems, enter C:\Progra~1\Java\jdk1.7.0_55 5. Close all open windows. 6. Verify that the JAVA_HOME system environment variable is defined by opening a new command prompt and running the following command: SET JAVA_HOME

A value is returned such as: JAVA_HOME=C:\Progra~1\Java\jdk1.7.x

Linux or UNIX 1. At a command line, run the following command: vi ~/.bash_profile 2. Set the variables by running the following command and replacing the java_path variable with the Java path that you specified: export JAVA_HOME=java_path export PATH=$JAVA_HOME/bin:$PATH 3. Save and close the .bash profile, and run the following command to apply the changes: source ~/.bash_profile 4. Verify that the JAVA_HOME system environment variable is defined by opening a new command line and running the following command: echo $JAVA_HOME

2. Install the Android SDK: a. Go to the Android developers' website (developer.android.com/sdk/ index.html) and click Other Download Options. b. In the SDK Tools Only section, download the SDK for your operating system and extract the compressed file on your computer. c. Start the installation wizard.

22 Planning, installation, and deployment On Windows: From the extracted directory, run the SDK Manager.exe file. On Linux or OS X: Open a terminal and navigate to the android_home/tools/ directory, then run the following command: android sdk

d. Under Tools, select Android SDK Tools Revision 22 or later and the latest Android SDK build tools. Also select an Android package with an API of 19 or greater and click Install Packages. 3. Optional: Install an integrated development environment. 4. If you installed Eclipse in step 3, 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. Installing the iOS development tools For iOS app development, you use your Apple ID to enroll in a developer program. About this task

You can enroll in the iOS Developer Program as an individual or a company where an individual is considered a one-person team.

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

The person who creates the team becomes the team agent; the legal contact and administrator of the team who has all privileges and full access to Member Center and iTunes Connect. The team agent is required to complete steps 5-7. iOS developers might require the assistance of the team agent to complete the procedure.

You create provisioning profiles to manage the use of iOS apps that you develop. You can create a development provisioning profile or a distribution provisioning profile

A development provisioning profile regulates the development and testing of apps to a specific number of devices. Development provisioning profiles for the apps must contain the IDs of the devices on which the app is installed. You can register more iOS devices and add them to the provisioning profiles.

An app store distribution provisioning profile provides access to the apps on all devices in your enterprise. However, Maximo Anywhere supports only one global

Chapter 2. Installing the Maximo Anywhere components 23 app ID for an app store distribution provisioning profile. Procedure 1. Install Oracle JDK version 7.0. a. From the Oracle Java SE downloads page (www.oracle.com/technetwork/ java/javase/downloads/jdk7-downloads-1880260.html), download the Java SE Development Kit for your operating system. b. Run the executable file and proceed through the installation program. c. Set the JAVA_HOME environment variable and specify the path to the directory where the JDK was installed by running cmd>vi ~/.bash_profile and adding the following line to your ~/.bash_profile: export JAVA_HOME=`/usr/libexec/java_home -v 1.7` 2. Create an Apple ID by registering as an Apple developer in the Apple Registration Center (developer.apple.com/programs/register/). 3. Download and install Xcode IDE, including the iOS SDK and Simulator, from the Mac App Store (www.apple.com/osx/apps/app-store.html). 4. Add your Apple ID to Xcode (developer.apple.com/library/ios/ documentation/IDEs/Conceptual/AppStoreDistributionTutorial/ AddingYourAccounttoXcode/AddingYourAccounttoXcode.html). 5. In Xcode, create the certificate (developer.apple.com/library/ios/ documentation/IDEs/Conceptual/AppDistributionGuide/ MaintainingCertificates/MaintainingCertificates.html) for the provisioning profile. v Create a developer certificate for a development provisioning profile. Download the certificate and add it to the Keychain application (support.apple.com/kb/PH7297). v Create a distribution certificate for a distribution provisioning profile. Download the certificate to your local environment. 6. Register the App IDs (developer.apple.com/library/ios/documentation/IDEs/ Conceptual/AppDistributionGuide/MaintainingProfiles/ MaintainingProfiles.html). You must register the App IDs as wildcards. When you create the App IDs, select Wildcard App ID and enter the bundle ID.

Type of provisioning profile Wildcard App ID Development provisioning profile The bundle ID for WorkExecution is com.WorkExecution*.

The bundle ID for WorkApproval is com.WorkApproval*. App store distribution provisioning profile Maximo Anywhere supports only one global app ID for an app store distribution provisioning profile.

The bundle ID is com*.

7. Register the Device IDs in Member Center (developer.apple.com/library/ios/ documentation/IDEs/Conceptual/AppDistributionGuide/MaintainingProfiles/ MaintainingProfiles.html). You can locate the unique device identifier (UDID) by connecting your device to the Mac OS X computer while Xcode or iTunes are running. 8. Create the provisioning profile for each app by using Member Center.

24 Planning, installation, and deployment Type of provisioning profile Action Development provisioning profile As the developer, generate the provisioning profiles and then download the profiles to your Mac OS X computer. Open each provisioning profile in XCode. The provisioning profiles are added to the system library at the following location: ~/Library/MobileDevice/Provisioning Profiles". App store distribution provisioning profile When you generate the provisioning profile, you are not required to provide IDs of the devices. Download the profile to your Mac OS X computer and add the profile identifier to the build.properties file.

You must download the provisioning profile to the build server every time the profile is updated. When you run the app build and deployment process, the provisioning profiles are collected and stored in the iOS application archive file (IPA).

Installing Maximo Anywhere The Maximo Anywhere component contains the project and the mobile apps. Before you begin v Ensure that the required 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

During the installation, you must provide details about the type of server that is used in the deployment.

Restriction: The Maximo Anywhere launchpad program is not supported on Mac OS X. Procedure 1. Start the launchpad.

Option Description Windows, Linux, or UNIX Double-click the launchpad file. If your computer is a Windows system, use the launchpad64.exe file. If your computer is a UNIX or Linux system, use the launchpad.sh file.

Mac OS X 1. From the Maximo Anywhere installation image, open the Install > IM folder and expand the installer.macOS compressed file. 2. Ensure that the path to the Userinst executable file does not contain any spaces or parentheses. Double-click the Userinst executable file.

Chapter 2. Installing the Maximo Anywhere components 25 2. On the Install IBM Maximo Anywhere pane, click Install. 3. If you deployed MobileFirst Server to a stand-alone application server, select Stand-alone MobileFirst Server. If you are setting up an integrated development environment with MobileFirst Studio, select Embedded Server within MobileFirst Studio and complete the installation wizard. 4. If you installed MobileFirst Server on a different computer, copy the MaximoAnywhere.war file to the MobileFirst Server computer.

Creating a MobileFirst runtime environment After Maximo Anywhere is installed, you must set up and configure a MobileFirst runtime configuration by using the MobileFirst Server Configuration Tool. About this task

Use the installation planning worksheet to record the values that you enter so that they can be used later in the installation. Procedure 1. On the computer where MobileFirst Server is installed, start the Server Configuration Tool.

Option Description On Windows In the Start menu, click IBM MobileFirst Platform Server 6.3 > Server Configuration Tool. On Linux or UNIX In the desktop menu, click IBM MobileFirst Platform Server 6.3 > Server Configuration Tool. On Mac OS X In the Finder, browse to the mf_server_home/shortcuts/ directory and double-click the configuration-tool.sh file.

2. Select Add a MobileFirst runtime environment to a configuration and specify a 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 the MaximoAnywhere.war file that was generated on the Maximo Anywhere computer. Specify the MobileFirst project context root and click Next. This value must match the runtime context root that you specified during the Maximo Anywhere installation. 4. Specify the database settings in the subsequent panes and click Save and Deploy. After the runtime configuration is saved, you can redeploy the MaximoAnywhere.war file at any time by selecting it in the MobileFirst Server Configuration 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. If your computer is a UNIX or Linux system, use the build.sh file. This step generates the distributable files for the project and deploys them to MobileFirst Server.

26 Planning, installation, and deployment Results

After the deployment is complete, the MaximoAnywhere project and apps are available in the MobileFirst Operations Console and the Application Center Console.

Installing an integrated development environment To create a development environment, you must install a set of development tools on the build computer. You can use an integrated development environment to test and configure mobile apps before you deploy them to mobile devices. Before you begin v Prepare the Maximo Anywhere environment. v To preview the apps in the MobileFirst Studio mobile browser simulator, install Google Chrome. About this task

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

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

You can customize the mobile apps when they are deployed. For more information, see the Configuring Maximo Anywhere mobile apps section of the IBM Knowledge Center. Procedure 1. Install Eclipse IDE: a. Go to www.eclipse.org/downloads/packages/eclipse-ide-java-ee- developers/keplersr1 and download Eclipse IDE for Java EE Developers version 4.3.2 (Kepler) for your operating system. b. Extract the compressed folder and run the Eclipse application to install the software. 2. Set up your Eclipse development environment: a. Check whether the Eclipse JSDT plug-in is installed. The JavaScript Development Tool (JSDT) plug-in helps you navigate through the Java Script code in Eclipse. 1) Select Help > About Eclipse and click Eclipse Web Tools Platform (WTP) 2) Browse for Eclipse JavaScript Development Tools in the About Eclipse Features window. 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.

Chapter 2. Installing the Maximo Anywhere components 27 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. Select the Chrome check box and click OK to apply your changes. 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 MobileFirstStudio.zip file in the Install directory of the Maximo Anywhere installation image and click Open > OK. d. On the Available Software pane, select IBM Worklight Studio Development Tools and click Next > Next > Finish. e. 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 Worklight Adapter. e. Right-click the application folder and click Run As > Run on Worklight Development Server. f. To preview the app, right-click the application folder and click Run As > Preview.

Silent mode: Installing Maximo Anywhere You can run a silent installation of Maximo Anywhere, MobileFirst Server, and Installation Manager from a command line. Silent installations that are conducted with Installation Manager are defined by an XML response file. Recording a response file for silent installation A response file collects data and records the selections that you make when you use the Installation Manager. If you want to run a silent installation, you must record the installation settings. About this task

When you use the Installation Manager to install the components, an XML response file can be recorded. The response file can be used for future silent installations of Maximo Anywhere and MobileFirst Server. Once your system is set up to record a response file, the response file is overwritten with each subsequent use of the installation program.

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

28 Planning, installation, and deployment Procedure 1. Open a command line and run the following command:

On Windows set record=true On UNIX or Linux export record=true

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 mode For Maximo Asset Management 7.5.0.6 or later, the required components can be installed silently by running an executable file on the computer where Maximo Asset Management is installed. In a Maximo Asset Management 7.6 environment, you use Installation Manager to install the required components in silent mode. About this task

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

Maximo Asset Management version 7.5.0.6 or later: 1. From the Install directory of the Maximo Anywhere installation image, copy the Payload.zip folder to the directory where the install.exe or install.bin is stored. The default directory is C:\IBM\SMP\madt on Windows or /opt/IBM/SMP/madt on UNIX or Linux systems. 2. From the samples folder of the Maximo Anywhere installation image, copy the response_install_Anywhere_Enablement.xml file to a local directory. 3. Verify that the response file contains the Maximo Asset Management installation directory. The default value is C:\\IBM\\SMP on Windows or /opt/IBM/SMP on UNIX and Linux. 4. Change to the directory where the installation executable file is stored and run the following command:

Windows install.exe -f response file path and name

For example, run the following command: install.exe -f C:\temp\ response_install_Anywhere_Enablement.xml UNIX or Linux ./install.bin -f response file path and name

For example, run the following command: ./install.bin -f /temp/ response_install_Anywhere_Enablement.xml

Maximo Asset Management version 7.6 or later: 5. Open the response file for editing and modify the values for your operating system. Ensure that the value for the repository location is correct.

Chapter 2. Installing the Maximo Anywhere components 29 6. Change directory to the tools directory where Installation Manager was installed and run the following command: imcl -silent -input responsefilename -log logfilename -acceptLicense

Specify the path and name of the existing response file and log file that you want to use. The -acceptLicense parameter is used to accept the license automatically. For example, on Windows, run the following command: imcl -silent -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 mode Installation Manager is the tool that is used to install Maximo Anywhere and MobileFirst 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 silent installation. You can use the initialization file to set the values for the silent installation process. A range of parameters can be modified in the silent-install.ini file. Procedure 1. 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 a Windows 64-bit operating system. 2. Optional: To modify the installation parameters, edit the silent-install.ini file. 3. From a command line, change to the directory where you copied the Installation Manager folder and run one of the following commands. Specify the path and the name of the log file that you want to create:

Windows installc.exe –-launcher.ini silent-install.ini -log logfilename-acceptLicense UNIX or Linux ./installc --launcher.ini silent-install.ini -log logfilename-acceptLicense

For example, run the following command for Windows: installc.exe –-launcher.ini silent-install.ini -log C:\tmp\ silent_install_log.xml -acceptLicense Related information: Install Installation Manager silently Parameters for silent mode installation You can modify the silent-install.ini initialization file by updating the parameters for your environment.

30 Planning, installation, and deployment Parameter Description -vm Specifies the Java launcher. In silent mode, always use java.exe on Windows, and java on other operating systems. -nosplash Suppresses the splash screen. --launcher.suppressErrors Suppresses the JVM error dialog. -silent Runs the Installation Manager program in silent mode. -input Specifies that an XML response is used as the input for the Installation Manager program. -log Generates a log file that records the result of the silent installation. The log file is an XML file, for example, c:\mylogfile.xml or /root/mylogs/mylogfile.xml

Installing Maximo Anywhere in silent mode You can generate a response file by completing a successful installation of Maximo Anywhere with the Installation Manager. Alternatively, you can use a sample response file that is provided in the samples directory of the Maximo Anywhere compressed folder. Before you begin

Installation Manager must be installed on the target computer.

Copy a generated response file or a sample response file with the necessary changes to the target computer.

A sample response file is provided for your operating system in the samples folder of the Maximo Anywhere installation image.

For Windows installations, use the response_install_Maximo_Anywhere_Win.xml response file.

For Mac OS X installations, use the response_install_Maximo_Anywhere_UnixMac.xml response file. About this task

You can copy the Maximo Anywhere response file to multiple computers to run silent installations. However, ensure that all values in the response file are valid for the target system. Procedure 1. 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 -silent -input responsefilename -log logfilename -acceptLicense

Chapter 2. Installing the Maximo Anywhere components 31 Specify the path and name of the existing response file and log file that you want to use. The -acceptLicense parameter is used to accept the license automatically. For example, on Windows, run the following command: imcl -silent -input C:\tmp\response_install_Maximo_Anywhere_Win.xml -log C:\tmp\silent_install_log.xml -acceptLicense

Setting up Maximo Asset Management for Maximo Anywhere You must add users to the predefined Maximo Anywhere security groups and enable applications in Maximo Asset Management. Adding users to the Maximo Anywhere security groups When mobile workers manage records, they must have the authority to use the Maximo Anywhere mobile apps. You authorize access to the Maximo Anywhere apps by adding users to the predefined security groups in Maximo Asset Management. About this task

The user and group association are retrieved from Maximo Asset Management during authentication. If the user does not belong to the security group that is associated with the app, login fails. For each app, this security control is implemented in the application definition file. In this file, the requiredRole attribute specifies the security group that is authorized to use the app.

By default, the Maximo Anywhere security groups do not include any users. You must add the relevant users, including predefined users such as MAXADMIN, before you deploy the associated apps. Procedure 1. In the Users application of Maximo Asset Management, create the user records (www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mbs.doc/ user/t_add_users.html). 2. In the Security Groups application, select the Maximo Anywhere group (www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mbs.doc/ securgroup/t_assign_sites_security_groups.html) 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 specific sites, labor, storerooms, or GL components. You must create separate security groups to implement security controls for these items.

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

32 Planning, installation, and deployment Maximo Anywhere security groups in Maximo Asset Management Maximo Asset Management includes predefined security groups for the Maximo Anywhere apps. You use these security groups to grant authorization to use the Maximo Anywhere apps. The number of authorized users for each app must comply with the terms of the Maximo Anywhere product license. App authorizations

The following security groups are included in the required components that are deployed during installation to the Maximo Asset Management environment: ANYWHERE_TECHNICIAN Grants authorization to use the Maximo Anywhere Work Execution app. ANYWHERE_APPROVER Grants authorization to use the Maximo Anywhere Work Approval app. ANYWHERE_PHYSICAL_COUNT Grants authorization to use the Maximo Anywhere Physical Count app. ANYWHERE_INSPECTOR Grants authorization to use the Maximo Anywhere Inspection app.

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 log in 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 through the server. v Authorization to read, create, and update data for the OSLC resources that are used in the associated mobile app. This type of control is provided by the Maximo application that is registered with the object structure for the resource. The security group identifies the authorizing application for each object structure and specifies the application-level signature options that are required to provide the appropriate level of data access. Users who belong to the security group automatically have the appropriate level of access for all data operations in the associated app.

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

The terms of your Maximo Anywhere license specify the number of users that are entitled 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 the number of users that are entitled to use the associated apps.

Chapter 2. Installing the Maximo Anywhere components 33 Enabling Maximo Asset Management applications for maps and labor reporting The Maximo Anywhere required components contain licenses for more Maximo Asset Management applications. You enable the Service Address application for use with the map feature and the Crews and Crew Types applications are used for labor reporting. About this task

This procedure grants access to administrators to configure the features of the applications. Procedure 1. 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 mobile apps The settings that you define in the Organizations application in Maximo Asset Management apply to the relevant enterprise system applications and to the associated mobile apps.

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

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

Option group Option description Example Timer Options Automatically change the If a work order is approved, work order status from the status automatically Approved to In Progress changes to In Progress when when a user starts a labor you start the timer. timer. Automatically change the When you stop the timer for work order status to a labor transaction, the status Complete when a user stops of the work order changes to a labor timer. Complete. Labor Options Future labor transaction You can specify the number tolerance in hours. A labor of hours in the future that transaction is not valid if it labor transactions can be includes a future start or entered. You might want to stop time that exceeds the enter time for future labor if specified tolerance. you know that you are going to perform a task but want to report the time now.

34 Planning, installation, and deployment Option group Option description Example Edit Rules Work order edit settings. For each work order status, Some fields do not apply to you can specify the types of the mobile apps, and are data that can be edited. For excluded from the mobile example, if a work order is apps or are read-only in the in Approved status, you can mobile apps. specify that the asset field can be edited.

Time zones

When mobile workers use mobile apps, the time zone at the server might be different from their time zones. With the Users application in Maximo Asset Management, you must specify the time zone in the user record for each mobile worker. The mobile apps use this information to calculate the difference between the server time and the device time.

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

Upgrading Maximo Anywhere To upgrade Maximo Anywhere to version 7.5.2 you must upgrade the server, upgrade the development environment, and migrate the artifact configurations. If you configured any build properties, you must re-enable them during the upgrade. Procedure 1. Upgrade the servers. a. On the computer where Maximo Asset Management is installed, apply the latest updates or fixes. b. Upgrade MobileFirst Server (www.ibm.com/support/knowledgecenter/ SSHS8R_6.3.0/com.ibm.worklight.upgrade.doc/devenv/ c_upgrade_to_srvr_in_production_env.html). c. Install the new version of the Maximo Anywhere project. Upgrading the existing project is not supported. d. Test your environment by deploying Maximo Anywhere apps to MobileFirst Server. 2. Upgrade the development environment. a. Upgrade MobileFirst Studio (www.ibm.com/support/knowledgecenter/ SSHS8R_6.3.0/com.ibm.worklight.upgrade.doc/devenv/ t_upgrade_studio.html). b. Migrate your project to the updated version of MobileFirst Studio (www.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/ com.ibm.worklight.upgrade.doc/devenv/ c_upgrading_to_wl_studio_v610_migrating_projects.html). 3. Migrate the artifact configurations. a. Back up the new Maximo Anywhere version 7.5.2 app.xml file that you are about to modify. b. Use a graphical file-comparison program to compare your modified 7.5.1 app.xml file to the 7.5.2 app.xml file.

Chapter 2. Installing the Maximo Anywhere components 35 c. In the build.properties file and the worklight.properties file, ensure that the options that you want enabled are set to true. d. Copy any additional JavaScript or XML files that you created in the old environment to the new environment. File location changes in version 7.5.2 In this release, the structure of the project directory for Maximo Anywhere is simplified.

The properties for GPS, maps, and connection settings have moved from the build.properties file to the new app-feature.properties file. However, any settings that are still in the build.properties file override any settings in the app-feature.properties file.

The following table shows the location of files.

File Version 7.5.1 Version 7.5.2 app.xml maximoanywhere_home\ maximoanywhere_home\ AnywhereWorkManager\apps\ MaximoAnywhere\apps\ app_name\artifact app_name\artifact worklight.properties maximoanywhere_home\ maximoanywhere_home\ AnywhereWorkManager\ MaximoAnywhere\server\conf server\conf build.properties maximoanywhere_home\ maximoanywhere_home\ AnywhereWorkManager MaximoAnywhere MaximoAnywhere.war maximoanywhere_home\ maximoanywhere_home\ AnywhereWorkManager\ MaximoAnywhere\bin bin(worklight.war) OSLCGenericAdapter.adapter maximoanywhere_home\ maximoanywhere_home\ AnywhereWorkManager\bin MaximoAnywhere\bin application_name.wlapp maximoanywhere_home\ maximoanywhere_home\ AnywhereWorkManager\bin MaximoAnywhere\bin application_name.apk maximoanywhere_home\ maximoanywhere_home\ application_name.ipa AnywhereWorkManager\bin MaximoAnywhere\bin

Additionally, you can place your customized files in the following directories:

File File path Image files that are specific to an app maximoanywhere_home\MaximoAnywhere\apps\ application_name\common\images\mdpi .css files that are specific to an app maximoanywhere_home\MaximoAnywhere\apps\ application_name\common\css JavaScript business logic files maximoanywhere_home\MaximoAnywhere\apps\ application_name\common\js OSLC Resource Description Framework maximoanywhere_home\MaximoAnywhere\oslc- (RDF) files docs\resources\rdf\oslc

Application definition changes in version 7.5.2 The following updates apply to the application definition file (app.xml) in this release.

36 Planning, installation, and deployment The application definition files for the apps are in the maximoanywhere_home\ MaximoAnywhere\apps\app_name\artifact directory. ID generation tool

The id attribute is now a required attribute for each new app.xml artifact. A new tool is available that dynamically generates and adds unique IDs to your app.xml when you merge app.xml changes into the 7.5.2 app.xml file. To run the ID generator tool, change to the /MaximoAnywhere directory and run the following command: ant -f artifact-id-generator.xml

Advanced Features

The following features are now available and can be used with the Anywhere Administration application: v Editable widgets can now be used inside elements. v The cssClass attribute can be set on elements. v The hideEmpty attribute can be set on elements to remove them from view if they are empty. v The showreqattribute attribute can be set on elements to show a required indicator. v The visibleButtonCount attribute can be set on