Maximo Upgrade and Maximo Installation

Maximo Upgrade and Maximo 7.6.1 Installation
October Darlene Nerden

Agenda Maximo Upgrade Maximo 7.6.1 Installation and Configuration
Why Upgrade Upgrade Requirements Upgrade Planning Upgrade Process Overview Upgrade Notes Maximo Installation and Configuration Maximo Upgrade Notes

Why Upgrade

Continuing to deliver on the value of EAM

New Integrations and Applications from 7.6.0 Feature Packs

Modernizing the Maximo User Experience with Work Centers

Example: Very visual role-based work centers

Work Supervisor Work Center 7.6.1 Improvements

Work Execution Work Center 7.6.1 Improvements

Integration to IBM Equipment Maintenance Assistant from Work Technician

Service Requests 7.6.1 Improvements

Work Supervisor – Service Request Administration

Inspections – New Work Centers

Inspections – Roadmap

Fresh New Look to Maximo – new IOT18 skin

Updated KPI colors

Responsive UI in IOT18

New Icons for IOT18

IOT18 Skin

Maximo is GDPR Ready

Cognos 11 Analytics Entitlement in Maximo 7.6.1

Cognos 11 has been updated with new, modern interface

Cognos 11 – Mobile Applications

Technical investment to reduce total cost of ownership

Maximo 7.6.1 – Technical Enhancements

Maximo 7.6.1 moves to Java 8 (JDK 1.8)

Why Upgrade New middleware servers/VMs Newer OSes supported AIX 7.1
Windows Server 2012 R2, 2016 RHEL 7.0, 7.2

Why Upgrade New Admin workstation
Windows, Linux, and AIX admin workstation support Windows Server 2016 RHEL 7 AIX 7.1

Why Upgrade New middleware versions (minimum versions)
WebSphere , / WebLogic Oracle 11g R2, 12c DB (runs on support), 11.1 SQL Server 2014, 2016

Upgrade Requirements

6.5.1.1 Upgrade Utilities Required
Upgrade Requirements Upgrade paths and relative complexity Maximo 4.11 to 5.2 Maximo 5.2 to 6.2 Maximo 6.2.8 to Maximo to Maximo to 7.6.1 Maximo 7.6.0.x to 7.6.1 Note: Current paths to to 7.6.1 or 7.6.0.x to 7.6.1 Upgrade Utilities Required

Upgrade Requirements Maximo 6.2 to 7.6
Maximo 6.2, please note that Maximo 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.1, you will follow this process: Apply Maximo fix pack Install 7.1 which includes the 6-7 upgrade program Apply Maximo Base Services fix pack Upgrade v6 to Install 7.5 which includes the upgrade program

Upgrade Requirements To upgrade from 6.2 to 7.6, you will follow this process (cont.): Apply Maximo fix pack Upgrade v7.1 to Install which includes the upgrade program Upgrade v7.5 to 7.6.1

Upgrade Planning

Upgrade Planning Data size and archiving Integration Points
More data = longer upgrade Improves application performance Integration Points Identify integration points in existing system Evaluate each integration to determine requirement Document change requirements from existing to new

Upgrade Planning 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 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

Upgrade Planning User training Administrative users
TPAE, security, crons, escalations, Workflow, performance monitoring and tuning General users Reporting Focus groups users Call centers Accounting Management

Reporting Reporting Requirements Reporting Server Changes

Maximo Analytic Tools

Upgrade Process Overview (from pre 7.6.0)

Upgrade Process Overview
Apply Maximo fix pack Complete Maximo 7.1 pre-upgrade tasks Install Maximo 7.1 Apply Maximo Base Services fix pack Run industry solution and/or add-on installation programs Apply industry solution and/or add-on fix packs Run Maximo upgrade utilities Integrity Checker, Validation, Upgrade Program, Updatedb

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 folder Defer database update and application deployment Apply Maximo 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

Overview (cont.) Complete Maximo pre-upgrade tasks Run the Maximo product installation program Run industry solution and/or add-on installation program Apply industry solution and/or add-on fix packs Run the configuration tool to perform database update operations

Overview (cont.) Complete post-upgrade tasks Migrate customizations After all products are installed on the admin workstation Move the custom Java code to the tree and compile using a JDK 1.8 compiler Move the compiled Java code in the appropriate folders on the installed admin workstation

Overview (cont.) Complete post-upgrade tasks Migrate customizations (cont.) If there were changes applied to 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 installation Analyze reports Review integrations Run Maximo integrity checker

Upgrade Process Overview (from 7.6.0)

Industry solution and/or add-ons should be installed at fix pack level Complete Maximo pre-upgrade tasks Run the Maximo product installation program Run industry solution and/or add-on installation program Apply industry solution and/or add-on fix packs Run the configuration tool to perform database update operations

Overview (cont.) Complete post-upgrade tasks Migrate customizations After all products are installed on the admin workstation Move the custom Java code to the tree and compile using a JDK 1.8 compiler Move the compiled Java code in the appropriate folders on the installed admin workstation

Overview (cont.) Complete post-upgrade tasks Migrate customizations (cont.) If there were changes applied to 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 installation Analyze reports Review integrations Run Maximo integrity checker

Upgrade Process (from pre 7.6.0)

Upgrade Process Maximo 6 – 7.1 Upgrade
From the Maximo 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 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 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 Maximo 7.1.1.13 – 7.5.0.11 Upgrade
Database is upgraded via updated 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 Maximo 7.1 to 7.5 Upgrade
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

Upgrade Process 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 Maximo 7.1.1.13 – 7.5.0.11 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 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 Maximo 7.5.0.11 – 7.6.1 Upgrade
Database is upgraded via updatedb utility invoked by the configuration tool Only after ALL products are installed in 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)

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

If required, upgrade/install middleware components and Operating Systems (cont.) Deploy WebSphere 9.0 Install a fresh instance of WebSphere 9.0 Configure via the configuration tool If manual WebSphere configuration, apply recommended performance settings

New installation of Maximo 7.6.1 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 to do database update Install add-ons and/or industry solutions

Upgrade Process Migrate customizations
Launch configuration tool and upgrade the database and application deployment Validate integrity of Maximo database Run Maximo Integrity Checker 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 configuration tool

Upgrade Process Maximo 7.5.0.11 – 7.6.1 Upgrade Run install validation
Review upgraded screens Review custom table domains and crossover domains Regenerate request pages for reports Update database statistics Perform post upgrade tasks

Upgrade Process (from 7.6.0)

Upgrade Process Maximo 7.6.0.x – 7.6.1 Upgrade
Database is upgraded via updatedb utility invoked by the configuration tool Only after ALL products are installed in environment that exist in 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)

Validate integrity of current Maximo database Run Maximo 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

If required, upgrade/install middleware components and Operating Systems (cont.) Deploy WebSphere 9.0 Install a fresh instance of WebSphere 9.0 Configure via the configuration tool If manual WebSphere configuration, apply recommended performance settings

New installation of Maximo 7.6.1 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 to do database update Install add-ons and/or industry solutions

Upgrade Process Migrate customizations
Launch configuration tool and upgrade the database and application deployment Validate integrity of Maximo database Run Maximo Integrity Checker 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 configuration tool

Upgrade Process Maximo 7.6.0.x – 7.6.1 Upgrade Run install validation
Review upgraded screens Review custom table domains and crossover domains Regenerate request pages for reports Update database statistics Perform post upgrade tasks

Upgrade Process Notes

Upgrade Process Notes 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

Upgrade Process Notes 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 Notes End of Support of Maximo 6.2.x was September 2013
End of Support of Maximo 7.1.x was April 2015 End of Support of Maximo 7.5.x is April 2018 Must be at to upgrade to Maximo and x can upgrade to Maximo 7.6.1 Maximo x to upgrade is much less complex than a Maximo to upgrade Minimal changes from Maximo to that impact an upgrade Uses the same report engine, integration code and database structure Will be 2 release streams fix pack feature pack

Upgrade Notes All products must be at 7.6.x version
Cannot upgrade one product to 7.6 and others at 7.5 Maximo 7.5/7.6 upgrade – No upgrade utilities like in previous versions No upgradeui, 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 There are 2 installations and packages
Non Multitenancy Multitenancy – DB2 only Cannot remove multitenancy No upgrade from Maximo 7.5 to Maximo 7.6 Multitenancy Windows, Linux, and AIX admin workstation support Perform upgrade in a test environment first Backup the database many times during the process Disable custom triggers

Upgrade Notes

Maximo Installation

Maximo 7.6.1 Installation 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 Installation Installation and configuration operations done separately Install uses IBM Installation Manager (IM) 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

Maximo Installation 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.1 Installation Launchpad Guide you through planning
and deployment tasks

Maximo 7.6.1 Installation Installation Manager Lays down files
Keeps metadata of what is installed

Maximo Installation 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 Installation

Maximo 7.6.1 Installation Configuration and deploy
Environment deployment and configuration Deployment maintenance and administrative tasks Upgrade option

Maximo 7.6.1 Installation Configuration and Deploy
Configuration of WebSphere

Environment deployment and configuration Deployment maintenance and administrative tasks Upgrade option

Configuration of Maximo

Environment configuration Updatedb and updatedblite

Maximo 7.6.1 Deployment Configuration Tool

Maximo 7.6.1 Deployment Configuration Tool
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, updates, application server security settings, etc. Support provided via GUI and command line interface (CLI)

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 if incorrect Page level – validation of 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

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

Option for cluster configuration

Once all configuration information has been entered the deployment options are presented

Maximo Upgrade Notes

Do not configure a database
Maximo Upgrade Do not configure a database

Maximo 7.6.1 Installation and Upgrade Notes
Must be at to upgrade to Maximo and x can upgrade to Maximo 7.6.1 Maximo x to upgrade is much less complex than a Maximo to upgrade Minimal changes from Maximo to that impact an upgrade Uses the same report engine, integration code and database structure Will be 2 release streams fix pack feature pack

Maximo 7.6.1 Installation and Upgrade Notes
All products must be at 7.6.x version Cannot upgrade one product to 7.6 and others at 7.5 There are 2 installations and packages Non Multitenancy Multitenancy – DB2 only Cannot remove multitenancy No upgrade from Maximo 7.5 to Maximo 7.6 Multitenancy Java 1.8 WebSphere ND v , DB2 11.1

Resources

Resources Maximo Knowledge Center Maximo Upgrade Wiki
mam.doc/welcome.htmlSystem Requirements Maximo Upgrade Wiki wiki/IBM%20Maximo%20Asset%20Management/page/Version% Upgr ade Resources Maximo Upgrade Resources Upgrade Frequently Asked Questions

Resources Upgrade Requirements Matrix Maximo Wiki
Maximo Wiki wiki/IBM%20Maximo%20Asset%20Management Enterprise Adapter Upgrade Considerations 304.ibm.com/support/docview.wss?q1=upgrade&rs=3214&uid=swg &context=SSLKT6&cs=utf-8&lang=en&loc=en_US Configuration Matrix mmunityview?communityUuid=a9ba1efe-b a181d6155e3a#fullpageWidgetId=W5f281fe58c09_49c7_9fa4_e094f86b7e9 8&file=97d773e c0a-8b6b f9e

Resources Maximo 7.5 Packaging Maximo 7.6 Packaging
Maximo 7.6 Packaging Maximo Packaging New in Maximo 7.6.1 mam.doc/overview/c_new_in_7.6.1.html What’s New What_s_new_in_Maximo_Asset_Management_7_6_1?lang=en

Resources Maximo Support Landing Page Upgrading to Maximo 7.6.1
Upgrading to Maximo 7.6.1 a181d6155e3a/entry/Upgrading_to_Maximo_7_6_1_from_Maximo_7_6_0_x?l ang=en_us Maximo 7.5 End of Support Announcement (EOS) Support Lifecycle IoT Support YouTube Videos a181d6155e3a/entry/Maximo_YouTube_videos_are_now_available_on_the _new_IBM_IoT_Support_channel?lang=en

Thank You

Maximo Upgrade and Maximo Installation

Similar presentations

Presentation on theme: "Maximo Upgrade and Maximo Installation"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Maximo Upgrade and Maximo Installation

Similar presentations

Presentation on theme: "Maximo Upgrade and Maximo Installation"— Presentation transcript:

Similar presentations

About project

Feedback