IBM Maximo for Service Providers

Version 7 Release 5.3

Installation Guide


 Note
Before using this information and the product it supports, read the information in Notices on page 11.

Compilation date: July 2014

This edition applies to version 7, release 5, modification 3 of IBM Maximo for Service Providers and to all
subsequent releases and modifications until otherwise indicated in new editions.
Copyright IBM Corporation 2008, 2014.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Installing Maximo for Service Providers 1 Deploying the EAR files on WebSphere Application
Updating environment data . . . . . . . . . 1 Server . . . . . . . . . . . . . . . . 7
Updating database properties. . . . . . . . 2 Command syntax for deploying EAR files on
Updating installation properties . . . . . . . 3 WebSphere Application Server . . . . . . . . 8
Updating the WebSphere Application Server Ensuring that the PLUSPQUOTECRONTASK cron
Network Deployment host name . . . . . . 3 task has finished running . . . . . . . . . . 8
Preparing for the installation . . . . . . . . . 4
Running the installation program . . . . . . . 4 Notices . . . . . . . . . . . . . . 11
Building EAR files . . . . . . . . . . . . 6 Trademarks . . . . . . . . . . . . . . 12
Deploying the EAR files on WebLogic Server . . . 6

Copyright IBM Corp. 2008, 2014 iii

iv Installation Guide
Installing Maximo for Service Providers
The installation of IBM Maximo for Service Providers Version 7.5.3 involves
installing the product, deploying the Enterprise Application Archive (EAR) files,
and configuring the software. You start the installation programs from the
launchpad.

Before you begin

IBM Maximo Asset Management Version 7.5 must be installed on the same
Windows administrative workstation where you install Maximo for Service
Providers Version 7.5.3, and in the same language as Maximo for Service Providers
Version 7.5.3. Ensure that you have installed the Maximo Asset Management
Version 7.5.0.5 or later fixpack.

Additionally, before you install Maximo for Service Providers Version 7.5.3, you
must update the Maximo database during the Maximo Asset Management
installation.

For information about installing Maximo Asset Management, see the

installation information for the product.

For information about upgrading, see the Upgrade Guide, IBM Maximo Products V7.1

to V7.5 on the Maximo Upgrade Resources web site.

About this task

You must install Maximo for Service Providers on a Microsoft Windows

administrative workstation. The Maximo for Service Providers EAR files are built
on the Windows workstation and later deployed to the application server.

Procedure
1. If you are upgrading to Maximo for Service Providers Version 7.5.3 from an
earlier version of Maximo for Service Providers (Version 7.1, 7.1.1, 7.1.1.1,
7.1.1.2, 7.1.2, 7.5, 7.5.1, 7.5.1.1, 7.5.1.2, or 7.5.2), update your environment data.
2. Prepare to install.
3. Install Maximo for Service Providers.
4. If you use Oracle WebLogic Server, deploy the EAR files.
5. For IBM WebSphere Application Server environments: The EAR files were
installed during the IBM Maximo Asset Management installation. If this task
was deferred during the Maximo Asset Management installation, rebuild and
deploy the EAR files.

Updating environment data

When you install a fix pack or upgrade an existing installation, the installation
program uses values that are recorded from the previous deployment. If anything
in your environment changed since the original deployment, you must record
these changes in properties files before you can install Maximo for Service
Providers.

Copyright IBM Corp. 2008, 2014 1

 About this task

If you made environmental changes to any of the systems in the original

deployment, such as changing a host name or updating a password, the changes
must be recorded. To record the environmental changes, you update the
install.properties and maximo.properties files on the administrative system.

When the product installation program runs an upgrade task, it attempts to use
values in the install.properties file and the maximo.properties file. During the
upgrade process, if the user name or password for a system is not updated, the
installation program uses the credentials in the properties files. If the installation
program cannot log on to a system with the credentials found in the properties
files, you are prompted to supply the correct information. Updated values are
written to the appropriate property file.

Updating credential information in property files has one exception: database

connection and credential information must always be current before you attempt
an upgrade operation. Database connection information and credential information
are stored in the maximo.properties file. Any changes to this information from the
time of the original deployment must be manually recorded in the
maximo.properties file before you begin an upgrade from version 7.1, 7.1.1, 7.1.1.1,
7.1.1.2, 7.1.2 , 7.5, 7.5.1, 7.5.1.1, 7.5.1.2, or 7.5.2 to version 7.5.3.

When you change the property value of the IBM WebSphere Application Server
Network Deployment host name (WAS.DeploymentManagerHostName) in the
install.properties file, you must also update a property for the WebSphere
Application Server Network Deployment thin client in the thinwasadmin.bat file
and then run that file.

For information about upgrading, see the Upgrade Guide, IBM Maximo Products V7.1
to V7.5 on the Maximo Upgrade Resources web site.

Updating database properties

Before you can upgrade your version of Maximo for Service Providers, you must
record any database changes that have been made in your environment since the
original deployment. You update the database properties in the maximo.properties
file.

Procedure
1. Change to the product_home\maximo\applications\maximo\properties
directory. The default location is C:\IBM\SMP\maximo\applications\maximo\
properties.
2. Make a copy of the maximo.properties file, and rename the file.
3. Delete the maximo.properties file.
4. Change to the product_home\etc directory.
5. Back up the maximo.properties_orig file. Save this backup copy permanently.
6. Rename the unencrypted maximo.properties_orig file to maximo.properties.
7. Copy the maximo.properties file to the product_home\maximo\applications\
maximo\properties\ directory.
8. Edit the maximo.properties file and update the credential or connection
information for the database server.
9. Save the maximo.properties file.

2 Installation Guide
 10. Run the encryptproperties.bat file in the product_home\maximo\tools\
maximo\ directory on the file to encrypt it.

What to do next

Update the installation properties in the install.properties file.

Updating installation properties

Before you can upgrade your version of Maximo for Service Providers, you must
record any installation program properties changes that have been made in your
environment since the original deployment. You update the installation properties
in the install.properties file.

Before you begin

Update the database properties in the maximo.properties file, as described in the

previous topic.

Procedure
1. Change to the product_home\etc directory.
2. Edit the install.properties file. Do not change encrypted properties that are
prefixed by [enc]. You are prompted for updated values during the update
operation. These values are written to the install.properties file.
3. Save the file.

What to do next

If you use WebSphere Application Server, you must update the WebSphere
Application Server Network Deployment host name.

Updating the WebSphere Application Server Network

Deployment host name
Before you can upgrade your version of Maximo for Service Providers, you must
update the WebSphere Application Server Network Deployment host name that
was used in the previous deployment.

Before you begin

Update the installation properties in the install.properties file, as described in
the previous topic.

Procedure
1. Update the WAS.DeploymentManagerHostName value in the install.properties
file.
2. Edit the C:\IBM\SMP\WASClient\thinwasadmin.bat file.
3. Update the following line with the new, fully qualified host name of the
WebSphere Application Server Network Deployment server: set
wsadminHost=-Dcom.ibm.ws.scripting.host=fully_qualified_host_name.
4. Run the thinwasadmin.bat file with these values: thinwasadmin.bat -domain
manager user name -password.
5. When prompted, indicate that you do want to download the truststore file.

Installing Maximo for Service Providers 3

Preparing for the installation
Before you install Maximo for Service Providers, you must complete tasks on the
middleware servers and on your administrative workstation.

Before you begin

The installation program requires access to the middleware servers that are
installed with Maximo Asset Management to complete the installation. You need
the administrative user IDs and passwords for the middleware servers.

About this task

When you install Maximo for Service Providers, you modify the configuration and
content of your application server, database server, and directory server. These
servers are referred to as the middleware servers.

Procedure
1. Install IBM Maximo Asset Management 7.5 with the 7.5.0.5 or later fixpack, on
the same administrative workstation where you install Maximo for Service
Providers, and in the same language as Maximo for Service Providers. Be sure
to update the Maximo database during the Maximo Asset Management
installation.
2. Back up the middleware servers and the administrative workstation.
3. Prepare the application server.

Application server What to do

WebSphere Application Server
WebLogic Server
Ensure that the middleware servers are
started. The installation program connects
to the middleware servers by using the
middleware login information that you
specify during the product installation.
Ensure that the application server
(MAXIMOSERVER) is stopped. If the
application server is running, stop the
server and wait a few minutes before you
start the installation program. If the
application server is not stopped, the
installation process stops.

4. If you run the installation program in a double-byte language or an Eastern

European language, set the workstation regional settings to that language. You
can reset your regional settings after you complete the installation.

Running the installation program

You can start the installation program for Maximo for Service Providers from the
launchpad.

About this task

You access the product software either from IBM Passport Advantage or from the
product DVD if you requested one. To download your product from IBM Passport
Advantage, follow the instructions in the download document.

4 Installation Guide
The launchpad is automatically started when you run the product DVD. If the
Windows autorun feature is disabled, you can start the launchpad by running the
launchpad.exe program from the root directory of the product DVD.

If you run 64-bit applications, use launchpad64.exe.

Procedure
1. Start the launchpad.
2. Select a language for the installation program, and click OK.
3. Click Install from the menu of options.
4. From the drop-down menu, select the installation path for Maximo Asset
Management.
5. Click IBM Maximo for Service Providers.
6. Follow the steps in the installation program.
7. If the Package Options window opens, ensure that the check box to defer
updating the Maximo database is cleared, and the checkbox to defer
redeploying the Maximo applications is cleared. If you are installing
additional products, you can choose to defer the Maximo application
redeployment option. If the package options were specified during the
Maximo Asset Management installation, the Package Options window might
not open.
8. Continue the installation program until the Pre-Install Summary window
opens. If the system check passes successfully, no error messages appear
under System Check Messages.
9. If any error messages are shown, make a note of the message identifiers, and
stop the installation.
10. When the installation is complete, from the Package Successfully Deployed
window, click Done.
11. Optional: If you deferred running the updatedb command and are running it
manually, you must run the following command afterwards:
tools/maximo/internal/runscriptfile -cserviceprovider -fProductEnabler
to add the authorizations for the Service Provider cloned applications.
Attention: This command must always be run after updatedb is run.

What to do next

Download and install the latest hot fix to ensure that you have the most current
build with all recent fixes. The latest hot fixes are on the IBM Support Portal
for Maximo for Service Providers.

Review any existing release notes for this product at Release Notes for
Maximo for Service Providers 7.5.3.

Additionally, perform the following steps:

v To check the results of the language package installation, review the language
package installation log file, TDToolkitdate-time.log, in the Maximo_home\maximo\
tools\maximo\log directory.
v If you use WebLogic Server, deploy the EAR files.
v If you use WebSphere Application Server, the installation is complete. You can
start Maximo for Service Providers. However, if your environment requires you

Installing Maximo for Service Providers 5

 to deploy the EAR files manually, or this task was deferred during the
installation, rebuild and deploy the EAR files.

If you are upgrading from Maximo for Service Providers version 7.1, 7.1.1, 7.1.1.1,
7.1.1.2, 7.1.2, 7.5, 7.5.1, 7.5.1.1, 7.5.1.2, or 7.5.2 to version 7.5.3, you must not
perform any billing processes until you have ensured that the
PLUSPQUOTECRONTASK cron task has finished running.

Review and complete the tasks that are described in the configuration
information for the product.

Building EAR files

If you deferred running the updatedb command when you ran the installation
program, or if you are manually running the updatedb command, build and deploy
the EAR files.

About this task

To manually build the EAR files, complete the following steps:

Procedure
1. To build the EAR file, run the command, install_home\maximo\deployment\
buildmaximoear.cmd
2. To build the help system EAR file, run the command, install_home\maximo\
deployment\buildmxiehsear.cmd

What to do next

Next, redeploy the EAR files.

Deploying the EAR files on WebLogic Server

If you use WebLogic Server, after you install Maximo for Service Providers, you
must deploy the EAR files from the WebLogic Server console. Deploying the EAR
files starts the application server.

Before you begin

v The EAR files must be deployed after the Maximo database is updated. The
Maximo database is updated as part of the installation process. However, if you
manually update the database (by running the updatedb command), make sure
that you do so before you deploy the EAR files.
v On a Windows operating system: If the MAXIMOSERVER server is not running,
start it from a command prompt.
v On a UNIX operating system: Ensure that the WebLogic Server daemon is
running.

To view the WebLogic Server console, you must have a Java Virtual Machine
installed.

6 Installation Guide
 Procedure
1. Change to the mydomain directory.

Operating system Location

Windows From a command prompt, change the path
to drive:\Oracle_installation_location\
user_projects\domain\mydomain
UNIX Open a command prompt, and change the
path to /home/mxadmin/oracle/
user_projects/domains/mydomain

2. Start WebLogic Server.

Operating system Command

Windows startWebLogic.cmd
UNIX ./startWebLogic.sh

3. Type the WebLogic Server user name and password.

4. Start the MAXIMOSERVER administration console by typing the following
address in the address bar of your browser: http://hostname:7001/console.
5. Log on to the WebLogic Server console.
6. Follow the instructions in the WebLogic Server console help to deploy the
maximo.ear file and the maximoiehs.ear file.

Results

The installation is complete. You can start Maximo for Service Providers.

Deploying the EAR files on WebSphere Application Server

You can manually deploy Maximo for Service Providers EAR files on WebSphere
Application Server. You perform this task if your organization has application
deployment restrictions that require that you deploy application files manually.

About this task

The EAR files are installed on WebSphere Application Server during the Maximo
Asset Management installation. If the deployment of the EAR files was deferred
during the Maximo Asset Management installation, you can deploy the EAR files
manually.

Procedure
1. Deploy the Maximo EAR file:
PRODUCT_HOME\jacl\solutions\DeployApplication.[bat|sh] WASAdminUserName
WASAdminPassword "MAXIMO" WASNodeName WASApplicationServerName
"PRODUCT_HOME\maximo\deployment\default\maximo.ear" WASVirtualHost
WASWebServerName
2. Deploy the Maximo help system EAR file:
PRODUCT_HOME\jacl\solutions\DeployApplication.[bat|sh] WASAdminUserName
WASAdminPassword "MAXIMOIEHS" WASNodeName WASApplicationServerName
"PRODUCT_HOME\maximo\deployment\default\maximoiehs.ear" WASVirtualHost
WASWebServerName
Related reference:

Installing Maximo for Service Providers 7

 Command syntax for deploying EAR files on WebSphere Application Server
You use parameters in the command syntax when you manually deploy the EAR
files on WebSphere Application Server.

Command syntax for deploying EAR files on WebSphere Application

Server
You use parameters in the command syntax when you manually deploy the EAR
files on WebSphere Application Server.

Syntax of the commands to deploy EAR files

The syntax of the commands for deploying the EAR files includes the following
parameters.

Parameters
WASAdminUserName
A WebSphere Application Server Network Deployment account with
deployment privileges.
WASAdminPassword
The password of the user who is specified in the WASAdminUserName
parameter.
WASNodeName
The name of the WebSphere Application Server Network Deployment node.
WASApplicationServerName
The name of the WebSphere Application Server Network Deployment
application server.
WASVirtualHost
The name of the WebSphere Application Server Network Deployment virtual
host.
WASWebServerName
The name of the WebSphere Application Server Network Deployment web
server.
Related tasks:
Deploying the EAR files on WebSphere Application Server on page 7
You can manually deploy Maximo for Service Providers EAR files on WebSphere
Application Server. You perform this task if your organization has application
deployment restrictions that require that you deploy application files manually.

Ensuring that the PLUSPQUOTECRONTASK cron task has finished

running
If you are upgrading from Service Provider version 7.1, 7.1.1, 7.1.1.1, 7.1.1.2, 7.1.2,
7.5, 7.5.1, 7.5.1.1, or 7.5.2 to version 7.5.3, you must not perform any billing
processes until you have ensured that the PLUSPQUOTECRONTASK cron task has
finished running.

8 Installation Guide
About this task

This cron task is necessary because the database was extended. The record that
contains the work order pricing totals was expanded to include a field to hold a
price total for those work orders that have quotes, minimum pricing, or included
pricing that was specified at the work-order level. These work orders do not have
price totals for labor, services, tools, materials, or fees.

Procedure
1. Log in to Maximo for Service Providers.
2. In the Cron Task Setup application, select the PLUSPQUOTECRONTASK cron
task.
3. Check for the cron task instance PLUSPQUOTE. If the PLUSPQUOTE instance
is there, then the cron task has not finished running yet. Wait until it is finished
before starting any billing processes. If the PLUSPQUOTE instance is not there,
then the cron task has run successfully and you can begin your billing
processes.

What to do next

Complete the tasks that are described in the configuration information for the
product.

Installing Maximo for Service Providers 9

10 Installation Guide
Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

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

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

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

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

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

Copyright IBM Corp. 2008, 2014 11

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

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

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Information concerning non-IBM products was obtained from the suppliers of

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

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

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International 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 and
trademark information at www.ibm.com/legal/copytrade.shtml.

12 Installation Guide
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft

Corporation in the United States, other countries, or both.

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

Notices 13
14 Installation Guide



Printed in USA