Maximo Upgrade

April 2016

1

• Maximo Upgrade• Why Upgrade• Upgrade Requirements• Upgrade Planning• Upgrade Process Overview• Upgrade Process Notes• Upgrade Notes

• Maximo 7.6 Installation and Configuration• Maximo 7.6 Installation and Configuration• Industry Solutions an Add-ons• Maximo 7.5 to 7.6 Upgrade• Notes

Agenda

2

Why Upgrade – Maximo 7.5 Expanded Footprint

Asset Management

Work Management

Materials Management

Purchasing

Locations

• Repair Facilities

Asset

Asset Templates

Failure Codes

Linear Assets

• Visual Control

Condition Monitoring

Meters

Meter Groups

Request for Quotation

Receiving

Receiving Inspections

Shipment Receiving

Purchase Requisitions

•Invoices

• Invoice Reversals

Purchase Orders

• Revisioning

• Receipt Tolerance

Desktop Requisitions

Item Master

Storerooms

Inventory

•Inventory Usage

•LIFO/FIFO Costing

• Consignment

• Transfer via

Shipment

• Default Costing

Condition Codes

Stocked Tools

Service Items

Job Plans

• Revisioning

Work Order Tracking

•Assignment Tab

•Hard/Soft Reservations

•Repair Facilities

Safety

Quick Reporting

Labor/Crafts

Tools

Preventive Maintenance

• PM Forecasting

Master PM

Assignment Manager

Contract Management

Purchase Contracts

Master Contracts

Warranty Contracts

Lease/Rental Contracts

Labor Rate Contracts

•Premium Pay Rates

Payment Schedules

Service Management

Service Groups

SLA Management

Change Management

•Incidents

•Problems

•Changes

•Releases

•Solutions

3

Why Upgrade – Maximo 7.5 Expanded Footprint

KPIs / Reporting/ Ad-hoc Reporting / Cognos Integration

Enhanced Workflow – Event Driven, Context-based / Escalation Manager

Security/Administration/Configuration – Automation Scripts, Migration Manager

Integration/Web Services – Import & Export direct from applications

4

Why Upgrade – IBM Maximo Asset Management 7.6

Expanded capabilities to support business intelligence

Intuitive navigation for users

Increased Serviceability

• Focus on User Experience – new look and feel, expanded start center configuration options

• Analytical insights through Reporting, KPI’s and Dashboards improved performance, increased user access and better tools to monitor the health of your business

• Functional Enhancements improved crew management and service addresses to support maps

• Technology Improvements – expanded install and platform support

• Built-in Mobility Capabilities – through Everyplace

5

• New middleware servers/VMs• Newer Oses supported

– AIX 7.1– Windows Server 2012– RHEL 6.0– RHEL 7.0– SUSE Linux Enterprise Server 11

• New Admin workstation• Windows, Linux, and AIX admin workstation support

– Windows Server 2012 (x86 64 bit)– RHEL 6.0 (x86-64, zSeries 64 bit, PowerPC)– RHEL 7.0 (x86-64, zSeries 64 bit, PowerPC)– AIX 7.1 (IBM System p® 64 bit)– SUSE Linux Enterprise Server 11 (x86 65 bit)

Why Upgrade

6

• New middleware versions (minimum versions)

• WebSphere 8.5.5 / WebLogic 12c

• Oracle 11g R2

• DB2 10.1

• SQL Server 2012

Why Upgrade

7

Upgrade Requirements

8

Upgrade Requirements

� Upgrade paths and relative complexity

� Note:– Current path

• 7.1.1.13 to 7.5.0.9 to 7.6.0.3

Maximo

4.11 to

5.2

Maximo

5.2 to 6.2

6.5.1.1

Upgrade

Utilities

Required

Maximo

6.2.8 to

7.1.1.13

Maximo

7.1.1.13

to 7.5.0.9

Maximo

7.5.0.9 to

7.6.0.3

9

• Maximo 6.2 to 7.6• Maximo 6.2, please note that Maximo 6.2.8 is the prerequisite/minimum version and patch you

need to have applied prior to upgrading to 7.1.

To upgrade from 6.2 to 7.6, you will follow this process:

– Apply Maximo 6.2.8 Fix Pack– Install 7.1 which includes the 6-7 upgrade program– Apply Maximo Base Services 7.1.1.13 Fix Pack – Upgrade v6 to 7.1.1.13– Install 7.5 which includes the 7.1-7.5 upgrade program– Apply Maximo 7.5.0.9 Fix Pack– Upgrade v7.1 to 7.5.0.9– Install 7.6 which includes the 7.5-7.1 upgrade program– Apply Maximo 7.6.0.3 Feature Pack– Upgrade v7.5 to 7.6.0.3

Upgrade Requirements

10

• Data Size and Archiving• More Data = Longer Upgrade• Improves App Performance

• Integration Points• Identify Integration Points in Existing System• Evaluate each integration to determine requirement• Document change requirements from existing to new

• Customizations• Evaluate new product functionality to determine if it now addresses the custom requirement• Customization work is work done outside the configuration framework provided with the

product

• Java Class Extensions• Custom Workflow• Code or content added

Upgrade Planning

11

• Time Requirements• Deadline for Go Live

• Downtime Restrictions

• When do you need to be on the new release?

• How long does the database upgrade take?

• How long will it take to upgrade integrations?

• How long will it take to upgrade customizations?

• How long will reports take?

• Technological / Reporting Requirements

• User Training• Administrative Users• TPAE, Security, Crons, Escalation, Workflow, Performance Monitoring & Tuning• General Users• Reporting• Focus Group Users

• Call Centers• Accounting• Management

Upgrade Planning

12

Upgrade Planning

• Reporting Requirements

• Reporting Server Changes– No Actuate Integration

– No Crystal Integration

13

• Overview• Apply Maximo 6.2.8 fix pack

• Complete Maximo 7.1 pre-upgrade tasks

• Install Maximo 7.1

• Apply Maximo Base Services fix pack 7.1.1.13

• Run industry solution and/or add-on installation programs

• Apply industry solution and/or add-on fix packs

• Run Maximo 7.1.1.13 upgrade utilities

– Integrity Checker

– Validation

– Upgrade Program

– Updatedb

Upgrade Process Overview

14

• Overview (cont.)

• Complete Maximo 7.5 pre-upgrade tasks

• Run the Maximo 7.5 product installation program to upgrade from 7.1 to 7.5

– Point to 7.1.1.13 folder

– Defer database update and application deployment

• Apply Maximo 7.5.0.9 fix pack

• Run industry solution and/or add-on installation programs

• Apply industry solution and/or add-on fix packs

• Run the product installation program to perform database update operations

Upgrade Process Overview

15

• Overview (cont.)

• Complete Maximo 7.6 pre-upgrade tasks

• Run the Maximo 7.6 product installation program

• Apply Maximo 7.6.0.3 feature pack

• Run industry solution and/or add-on installation programs

• Apply industry solution and/or add-on fix packs

• Run the configuration tool to perform database update operations

Upgrade Process Overview

16

• Overview (cont.)

• Complete post-upgrade tasks

– Migrate customizations

• After ALL products are installed on the 7.6 admin workstation

• Move the custom Java code to the 7.6 tree and compile using a JDK 1.7 compiler

• Move the compiled Java code into the appropriate folders on the 7.6 installed admin workstation

• If there were changes applied to in any existing JSP, XML, HTML, CSS or Java Script files pages

» Identify the differences from the old source tree and re-apply the changes accordingly into the new files that were laid down by

the 7.6 installation.

– Analyze reports

– Review integrations

Upgrade Process Overview

17

• Maximo 6 – 7.1 Upgrade

• From the Maximo 7.1.1.13 folders run

– Upgradeui Utility

• Integrity Checker – report and repair mode, source meta-data integrity

• Validation – source versus target meta-data integrity

• Upgrade – transforms database to version 7 structure

– Updatedb

• Transforms database to 7.1.1.13 fix pack

• Note: Integrity Checker

– You may be asked to run Database Configuration for your database:

• Only run the Database Configuration from Maximo 6.2.8

Upgrade Process

18

• Maximo 6 – 7.1 Upgrade

• Add new tables and columns, using Metadoc

• Process Callouts for tables, logically sequenced

• Delete obsolete tables and columns, using Metadoc

• Metadoc defines database differences

• Industry Solutions create Metadocs and Callouts

• Industry Solutions recognized by maxvars

Upgrade Process

19

• Maximo 7.1.1.13 – 7.5.0.9 Upgrade

• Database is upgraded via updatedb utility invoked automatically by the

installer

– Only after ALL products are installed at 7.5 level

– Option is available to have it done only after admin workstation is upgraded (defer

updatedb)

• If not automated by the installer, you must run the following manually

– Updatedb

– If languages other than English are deployed: run Tdtoolkit for each PMP installed

– Build and deploy the EAR file(s)

Upgrade Process

20

• Maximo 7.1.1.13 – 7.5.0.9 Upgrade• Validate integrity of current Maximo 7.1 database

– Run Maximo 7.1 Integrity Checker and fix all errors

• If required, upgrade/install middleware components and Operating Systems

– Patch or upgrade Operating System

– Upgrade database server

– Upgrade LDAP/directory server

– Upgrade WebLogic

– Deploy WebSphere v7• Install a fresh instance of WebSphere v7

• Use WebSphere v7 migration tool to migrate existing WebSphere 6.1 configuration

• If manual WebSphere configuration, apply recommended performance settings

Upgrade Process

21

• Upgrade Maximo 7.1 to 7.5

• Maximo folder is renamed to pre_75_maximo

• If just Maximo is deployed:

– The upgrade, updatedb, and EAR deployment can be done automatically during the installation at one time

• If multiple products:

– Defer database update and application deployment

• Install add-ons and/or Industry Solutions

• Launch 7.5 install and select database update and application deployment

• Validate integrity of Maximo 7.5 database

• Run Maximo 7.5 Integrity Checker

Upgrade Process

22

• Maximo 7.1.1.13 – 7.5.0.9 Upgrade

• Product upgrade can be done as 2 ‘manual’ steps

– Apply the 7.5 files on the administrative workstation

– Manually run updatedb, tdtoolkit, and build and deploy the EAR files

• Note: In a multi product installation, 7.5 version of all products must be installed first. Only after all products are at 7.5, then updatedb and EAR deployment can be invoked by the 7.5 installer

Upgrade Process

23

• Maximo 7.5.0.9 – 7.6.0.3 Upgrade

• Database is upgraded via updatedb utility invoked by the configuration tool

– Only after ALL products are installed in 7.6 environment that exist in 7.5

environment

• If not automated by the tool, you must run the following manually

– Updatedb

– If languages other than English are deployed: run Tdtoolkit for each component

installed

– Build and deploy the EAR file(s)

Upgrade Process

24

• Maximo 7.5.0.9 – 7.6.0.3 Upgrade• Validate integrity of current Maximo 7.5 database

– Run Maximo 7.5 Integrity Checker and fix all errors

• If required, upgrade/install middleware components and Operating Systems

– Patch or upgrade Operating System

– Upgrade database server

– Upgrade LDAP/directory server

– Upgrade WebLogic

– Deploy WebSphere v8.5.5• Install a fresh instance of WebSphere v8.5.5

• Configure via the configuration tool

• If manual WebSphere configuration, apply recommended performance settings

Upgrade Process

25

• Upgrade Maximo 7.5 to 7.6• New installation of Maximo 7.6• If just Maximo is deployed:

– The upgrade, updatedb, and EAR deployment can be done by the configuration tool immediately after the installation

• If multiple products and/or customizations: – Do not run configuration tool right after installation

• Install add-ons and/or Industry Solutions

• Migrate customizations

• Launch 7.6 configuration tool and upgrade the database and application deployment

• Validate integrity of Maximo 7.6 database• Run Maximo 7.6 Integrity Checker

Upgrade Process

26

• Note: In a multi product installation, all products must be installed first. Only after all products are installed, then updatedb and EAR deployment can be invoked by the 7.6 configuration tool

Upgrade Process

27

• Maximo 7.5.0.9 – 7.6.0.3 Upgrade

• Run install validation

• Review upgraded screens

• Review custom table domains and crossover domains

• Regenerate request pages for reports

• Update database statistics

Upgrade Process

28

• Supported by upgrade• All data• Any configurations done with the Maximo configuration tools• Data model• User interface and presentation layer• Workflow processes• Data validations and defaults• Integration definitions• Escalations

• Not supported by upgrade• Database schema or objects changed outside of Maximo database configuration• Database objects created (i.e. stored procedures, triggers, views, synonyms)• Custom extensions of Maximo code• Moving from one database platform to another

Upgrade Process Notes

29

• Maximo 7.5 Industry Solutions and Add-ons installed to Maximo 7.6

• If no 7.6 version available

• On Windows admin workstations – run existing launchpad

• On Linux/AIX – run command line install

– solutionInstaller or solutionInstallerGUI

• After installation, configuration tool is used to configure industry solutions and add-ons

Upgrade Process Notes

30

• End of Support of Maximo 6.2.x was September 2013• End of Support of Maximo 7.1.x was April 2015• Must be at 7.1.1.13 to upgrade to 7.5.0.9

• Will be 2 release streams• 7.5.0.10 Fix Pack • 7.6.0.5 Feature Pack

• All products must be at 7.5/7.6• Cannot upgrade one product to 7.5 and others at 7.1

• Maximo 7.5/7.6 upgrade - No upgrade utilities like in previous upgrades• No upgradeui• No 7.5/7.6 Integrity Checker success before upgrading• No Validation success before upgrading• No upgrade program

• Maximo 7.5/7.6 upgrade - Database upgrade done via updatedb

Upgrade Notes

31

• There are 2 installations and packages

• Non Multitenancy

• Multitenancy – DB2 only

• Cannot remove multitenacy

• No upgrade from Maximo 7.5 to Maximo 7.6 Multitenancy

• Windows, Linux, and AIX admin workstation support

• Windows Server 2012 (x86 64 bits)

• RHEL 6.0 (x86-64, zSeries 64bit, PowerPC)

• RHEL 7.0 (x86-64, zSeries 64bit, PowerPC)

• AIX 7.1 (IBM System p® 64-bits)

• SUSE Linux Enterprise Server 11 (x86 64-bits)

Upgrade Notes

32

• Perform upgrade is a test environment first

• Backup the database many times during the process

• Disable custom triggers

• If you have Mobile, delete user data

Upgrade Notes

33

• Installation Manager

• Common technology for installation, delivery and management of the product release lifecycle

• Installs, upgrades and uninstalls

• New releases, fix packs

• Customer entitlement, downloads and validation checks

• Simplification of the installation for Maximo, its components, and IBM

middleware

• Maximo-based products and components packaged as Installation Manager packages

Maximo 7.6 Installation

34

• Installation and Configuration operations done separately

• Install uses IBM Installation Manager

• Configuration is done as post-install steps, by specific tooling

• Launchpad offers users install choices to be performed

• Single install technology

• IM is launched with Offerings for required middleware and product

• Configuration tool is launched at the end of the IM Offerings installs

• Allows configuration/reconfiguration to run multiple times

• Uses same interface for initial product configuration and configuration updates

• Allows manual configuration after an automated install

• Configuration tool can be launched from the launchpad

Maximo 7.6 Installation

35

• Launchpad

• Guide you through planning and deployment tasks

Maximo 7.6 Installation

36

• Installation Manager

• Lays downs files

• Keeps metadata of what

is installed

Maximo 7.6 Installation

37

• Searches and downloads latest

version of fixes and patches

• Checks and downloads latest

level of software packages

• Feature packs and interim

fixes can be downloaded at

install time

• Does customer entitlement for

fixes and updates of products

• At the end of the install you can

launch the configuration tool

Maximo 7.6 Installation

38

• Configuration and Deploy

• Environment deployment and

configuration

• Deployment maintenance and

administrative tasks

Maximo 7.6 Installation

39

• Post install tool used for configuration

• Enhanced user input validation

• Self-help troubleshooting

• Definition and (re)configuration of deployment

• Initial settings for middleware, Maximo, industry solutions and add-ons

• Add languages, password changes, database updates, application server security

settings, etc

• Support provided via GUI and Command Line Interface (CLI)

Maximo 7.6 Deployment Configuration Tool

40

Maximo 7.6 Deployment Configuration Tool

41

• Number of panels has been reduced

• Contextual help• Flyover help

• Embedded help on panels

• Additional page level help

• Contextual feedback• Field level – immediate feedback when information is incorrect

• Page level – validation on page when you attempt to proceed

• Full validation – deep validation when you attempt to deploy

• Error messages display in the console window

• Error indicators with flyover on fields

• Status indicators in navigation tree

Maximo 7.6 Deployment Configuration Tool

42

Maximo 7.6 Deployment Configuration ToolMost functions are handled using a wizard interface

Console area with progress and error

messages

Navigation tree to indicate where you are in the process with

status indicators

Navigation buttons

Field indicators to more quickly find

problems

Navigation tree also allows direct access navigation to other

pages

43

• Middleware Configuration

• Initial configuration of WebSphere

• Used to be done by the middleware installer

• Creates necessary profiles, start options and sets the administrative security mode

• Automated configuration of clusters

– Both horizontal and vertical

• No longer need separate initial configuration for DB2, all necessary configuration can

be done when configuring the deployment

Maximo 7.6 Deployment Configuration Tool

44

Maximo 7.6 Deployment Configuration Tool

Option for cluster

configuration

45

• Once all configuration

information has been entered the deployment options are presented

Maximo 7.6 Deployment Configuration Tool

46

• Maximo 7.5 Industry Solutions

and Add-ons installed to Maximo 7.6

• If no 7.6 version available

• On Windows admin

workstations – run existing

launchpad

• On Linux/AIX – run

command line install

– solutionInstaller or solutionInstallerGUI

Maximo 7.6 Industry Solutions and Add-ons

47

• After installation, configuration

tool is used to configure industry solutions and add-ons

Maximo 7.6 Industry Solutions and Add-ons

48

Maximo 7.5 to 7.6 Upgrade

Do not Do not configure a

database

49

• There are 2 installations and packages

• Non Multitenancy

• Multitenancy – DB2 only

• Cannot remove multitenacy

• No upgrade from Maximo 7.5 to Maximo 7.6 Multitenancy

• Java 1.7

• Java version 1.6.0 SR4 FP1

• Java version 1.7 is required for the application server

• WebSphere ND v8.5.5.3

• DB2 10.5.0.4

Maximo 7.6 Installation and Upgrade Notes

50

• Maximo Knowledge Center• http://www-01.ibm.com/support/knowledgecenter/SSLKT6/sslkt6_welcome.html

• Maximo 7.6 What’s New• http://www-

01.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mam.doc_7.6.0/overview/c_ctr_wn_mam_7.6.html

• System Requirements• https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Max

imo%20Asset%20Management/page/Version%207.6• Upgrade Resources

• https://www-304.ibm.com/support/docview.wss?uid=swg21266217• Upgrade Frequently Asked Questions

• https://www-304.ibm.com/support/docview.wss?uid=swg21368150• Upgrade Requirements Matrix

• https://www-304.ibm.com/support/docview.wss?uid=swg21440174• Maximo Wiki

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

• Maximo 7.6 Resources• http://www-01.ibm.com/support/docview.wss?uid=swg21692646

Resources

51

• Enterprise Adapter Upgrade Considerations• https://www-

304.ibm.com/support/docview.wss?q1=upgrade&rs=3214&uid=swg21306367&context=SSLKT6&cs=utf-8&lang=en&loc=en_US

• WebSphere Settings• https://www-304.ibm.com/support/docview.wss?uid=swg21498645

• Maximo 7.5 Packaging• https://www-304.ibm.com/support/docview.wss?uid=swg21498420

• Maximo 7.6 Packaging• http://www-01.ibm.com/support/docview.wss?uid=swg24038431

• Configuration Maxtrix• https://www.ibm.com/developerworks/community/groups/service/html/communityview?co

mmunityUuid=a9ba1efe-b731-4317-9724-a181d6155e3a#fullpageWidgetId=W5f281fe58c09_49c7_9fa4_e094f86b7e98&file=97d773e7-2177-4c0a-8b6b-170374718f9e

• Pre-Req Checker• https://www-304.ibm.com/support/docview.wss?uid=swg21498097

• Maximo Support Landing Page• http://www-01.ibm.com/support/docview.wss?uid=swg21418666

Resources

Thank You