of 73 /73
Maximo Upgrade and Maximo Upgrade and Maximo 7.6 Installation o 7.6 Installation Darlene Nerden June 2017

Maximo Upgrade and Maximo Upgrade and Maximo 7.6 ... - IBM

  • Author
    others

  • View
    17

  • Download
    5

Embed Size (px)

Text of Maximo Upgrade and Maximo Upgrade and Maximo 7.6 ... - IBM

PowerPoint PresentationMaximo Upgrade and Maximo Upgrade and Maximo 7.6 Installation o 7.6 Installation Darlene Nerden
June 2017
• Maximo Upgrade
• Why Upgrade
• Upgrade Requirements
• Upgrade Planning
• Industry Solutions an Add-ons
• Notes 2 6/21/2017
Asset
Management
Work
Management
Materials
Enhanced Workflow – Event Driven, Context-based / Escalation Manager
Security/Administration/Configuration – Automation Scripts, Migration Manager
Integration/Web Services – Import & Export direct from applications
5 6/21/2017
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
addresses to support maps
• Built-in Mobility Capabilities – through Everyplace
•With continuous delivery new Work Centers will
be made available that work in conjunction with 7.6
•Target key user types and processes
Business Analyst Work Center
Supervisor Work Center
Enables supervisors to optimize the flow of their team's work
Technician Work Center
Manage all assignments that are assigned to you by your supervisor
Service Request Work Center
Create and view SRs
Why Upgrade – Maximo 7.6 Work Centers Offering Perceptive, Stateless, Responsive applications for a more intuitive user experience.
Role Based IntuitiveInteractiveData Driven
• Windows Server 2012
• 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) 7 6/21/2017
Why Upgrade
• WebSphere 8.5.5 / WebLogic 12c
Maximo 4.11 to
• 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
• Apply Maximo 7.5.0.11 Fix Pack
• Upgrade v7.1 to 7.5.0.11
• Apply Maximo 7.6.0.8 Feature Pack
• Upgrade v7.5 to 7.6.0.812 6/21/2017
Upgrade Requirements
Upgrade Planning
13 6/21/2017
• 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
• 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
• General Users
• Install Maximo 7.1
• Run Maximo 7.1.1.13 upgrade utilities
• Integrity Checker
• 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
• Apply Maximo 7.5.0.11 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
20 6/21/2017
• Run the Maximo 7.6 product installation program
• Apply Maximo 7.6.0.8 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
21 6/21/2017
• 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
22 6/21/2017
• Upgradeui Utility
• Validation – source versus target meta-data integrity
• Upgrade – transforms database to version 7 structure
• Updatedb
• Note: Integrity Checker
• You may be asked to run Database Configuration for your database:
• Only run the Database Configuration from Maximo 6.2.8
24 6/21/2017
Upgrade Process
• Process Callouts for tables, logically sequenced
• Delete obsolete tables and columns, using Metadoc
• Metadoc defines database differences
• Industry Solutions recognized by maxvars
25 6/21/2017
Upgrade Process
• Maximo 7.1.1.13 – 7.5.0.11 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)
26 6/21/2017
Upgrade Process
• 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:
• Install add-ons and/or Industry Solutions
• Launch 7.5 install and select database update and application
deployment
• Run Maximo 7.5 Integrity Checker
27 6/21/2017
Upgrade Process
• 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
28 6/21/2017
Upgrade Process
• Maximo 7.5.0.11 – 7.6.0.8 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)
29 6/21/2017
Upgrade Process
• 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
• Configure via the configuration tool
• If manual WebSphere configuration, apply recommended performance settings
30 6/21/2017
Upgrade Process
• 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
• Run Maximo 7.6 Integrity Checker
31 6/21/2017
Upgrade Process
• 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
32 6/21/2017
Upgrade Process
• Regenerate request pages for reports
• Update database statistics
• Data model
• Workflow processes
• 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
35 6/21/2017
• 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
36 6/21/2017
• Must be at 7.1.1.13 to upgrade to 7.5.0.11
• Will be 1 release stream
• 7.6.0.9 Feature Pack
• 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, 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
38 6/21/2017
Upgrade Notes
• Non 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)
39 6/21/2017
Upgrade Notes
• Backup the database many times during the process
• Disable custom triggers
40 6/21/2017
Upgrade Notes
• Common technology for installation, delivery and management of the product release lifecycle
• Installs, upgrades and uninstalls
• New releases, fix packs
• Simplification of the installation for Maximo, its components, and IBM middleware
• Maximo-based products and components packaged as Installation Manager packages
42 6/21/2017
• 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
43 6/21/2017
44 6/21/2017
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
46 6/21/2017
47 6/21/2017
• Update database option
• Updatedb and Updatedb Lite options
49 6/21/2017
50 6/21/2017
• Enhanced user input validation
• 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)
51 6/21/2017
52 6/21/2017
• Number of panels has been reduced
• Contextual help
• Flyover help
• 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
53 6/21/2017
54 6/21/2017
Maximo 7.6 Deployment Configuration Tool Most 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
problems
pages
• 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
55 6/21/2017
56 6/21/2017
Option for cluster
entered the deployment options are
presented
Maximo 7.6 Industry Solutions and Add-ons
58 6/21/2017
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
60 6/21/2017
Maximo 7.5 to 7.6 Upgrade
61 6/21/2017
62 6/21/2017
Do not configure a
63 6/21/2017
• Non Multitenancy
• Java 1.7
• Java version 1.7 is required for the application server
• WebSphere ND v8.5.5.3
• Released May 19, 2017
• Data Set Designer function (7.6.0.6)
• Create data sets quickly and without the involvement of IT personnel
• For Work Centers
• Supervisor Work Center (7.6.0.5)
• Inspection Work Centers (7.6.0.8)
• New Workflow Designer (7.6.0.6)
• Import building model data in the Construction-Operations Building information exchange (COBie) format into Maximo
• Manage BIM Viewer
• License Usage Monitoring application (7.6.0.6)
• Monitor your usage of licenses
• Time Zone Rules application (7.6.0.8)
• Specify time zone rules to identify the local date and time when records are created for a process
• Budget Monitoring application (7.6.0.8)
• Create budget records to monitor transactions in a financial period
• New REST APIs (7.6.0.8) 66 6/21/2017
Maximo 7.6.0.8
• JRE 1.8.0_66 (7.6.0.4)
• Firefox 45 (7.6.0.5)
• WebSphere Settings
• http://www-01.ibm.com/support/docview.wss?uid=swg24038431 • Configuration Maxtrix
• https://www-01.ibm.com/support/docview.wss?uid=swg27049624
• http://www-01.ibm.com/support/docview.wss?uid=swg22004316
72 6/21/2017