Sheyam Maximo 7 Installation Tips and Tricks

Maximo 7 Installation Tips and Trickshttp://www-306.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html
*
© 2009 IBM Corporation
http://www-306.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html
Overview
Fix Pack
Download middleware package(s)
Non IBM middleware components must be installed manually before Maximo installation
IBM Maximo Asset Management 7.1
Middleware installer enables
Do not configure Application Server Security during Maximo installation. Configure Application Server Security after the installation
*
If WebSphere - wasadmin
Create groups – MAXADMIN
MAXIMOUSERS (Active Directory)
Common functionality for Tivoli Process Automation Engine (TPAE)
Launchpad option – Maximo Asset Management
PSI provides a common deployment mechanism for Process Solutions
*
Deployment Engine
PSI is based around a common component called Autonomic Deployment Engine (DE) which defines an installable package format and provides a set of runtime services used to install those packages.
In order to be installed via PSI, an installable package must adhere to the DE Packaging structure
DE database contains information regarding products installed
Operating System
ISC, HIS, FPs, …)
Maximo Base Services
PSI For PMPs
Customers may optionally choose to re-use existing MW.
Base Services Installer (BSI)
Deploys Common packages
Deploys PSI Installer
Solution Packages
Exploiter teams builds PSI modular packages to package and deploy their solutions (“extensions”).
BSI
PSI
Supports s/w lifecycle (e.g. applying fixes)
MWI
Launchpad option – Enable Maximo Asset Management License for Usage
Use Middleware Installer for IBM middleware components (DB2, WebSphere, Tivoli Directory Server)
Remote access to all servers at the Administrator level
Local Administrator to server (not Domain user)
TPAE and Maximo must be installed on Windows
Disable Firewall
*
Follow through the screens to the Import Middleware Configuration Information dialog
Recommendation - Do not select Import middleware configuration information
*
TPAE (Base Services) Installation
Follow through the screens filling in the correct data to the Automate Database Configuration Information dialog
Select Automate – If only the database was created
Select Do not automate – If database, tablespaces, users, etc. were created
*
Follow through the screens filling in the correct data to the Automate WebSphere Configuration Information dialog, if using WebSphere
Select Automate – If MXServer and JMS Queues configuration has not been done
Select Do not automate – If MXServer and JMS Queues configuration has manually been done
Recommendation – Select Automate WebSphere configuration
Follow through the screens filling in the correct data to the Security dialog
Do not select Configure J2EE application security
*
Follow through the screens filling in the correct data to the Run Configuration Step dialog
Select Do not run the configuration step now
*
Follow through the screens filling in the correct data to the Summary dialog screens
Review the installation options and install
IBM Tivoli Software
Support Technical Exchange Web site http://www-306.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html
Taskrunner
Runs the configuration and creates the Maximo objects in the database
From Command Prompt – ibm\smp\scripts
taskrunner.bat CONTINUE STOPONERROR
*
Select from Launchpad
Follow through the screens filling in the correct data to the Package Options dialog
*
Build and deploy EAR
Build EAR files
Run buildmaximoear
Run buildhelpear
Deploy EAR files (WebSphere)
Expand Applications
Select both and click Uninstall
Click Install
Browse to location of the EAR files (ibm\smp\maximo\deployment\default)
Click Next
Click Next
Select all modules and select MXServer and webserver1 and click Apply
Click Next
Deploy EAR files (WebSphere)
Click Next
Click Finish
Repeat deploy process for Maximo Help EAR
Deploy EAR files (WebLogic)
Click Lock & Edit
Click Deployments
If the Maximo and Maximohelp applications are listed, select both and click Delete
Browse to location of the EAR files and select (ibm\smp\maximo\deployment\default)
Click Next
Select Install this deployment as an application and click Next
Click Finish
Updatedb
Stop the Maximo Application Server
From a command prompt change to ibm\smp\maximo\tools\maximo
Run updatedb
Add Java parameters to the MXServer Application Server (-Dsun.rmi.dgc.ackTimeout=10000 -Djava.net.preferIPv4Stack=true)
Document 1261874
Expand Servers and click Application Servers
Click MXServer
Click Process Definition
Post Installation
In Generic JVM Arguments field add the following 2 Java parameters:
-Dsun.rmi.dgc.ackTimeout=10000
-Djava.net.preferIPv4Stack=true
Click Apply
Expand System Administration
Click Console Preferences
Click Apply
Post Installation
If WebSphere on Windows - to create the node agent as a service
Document 1314060
WASService -add NodeAgent -serverName nodeagent -profilePath "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01" -wasHome "C:\IBM\WebSphere\AppServer" -logRoot "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent" -logFile "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent\startServer.log" -restart true
7.1.1.5 Fix Pack Installation
Follow through the screens filling in the correct data to the Run Configuration Step
Select Copy files now, and perform installation configuration later, manually
Select Deploy application files manually later
*
taskrunner.bat CONTINUE STOPONERROR
*
Backup database
ibm\smp\de_backups
Jservice.exe process
Backup/restore
Run setenv
IU UUID: 744662FEEC4911DB83140800200C9A66 Name: Common_PMP_IU Version: 7.1.1.5
IU UUID: 3D2FFFEAA4C34409A21320BD5593574A Name: MADT_Install_Files Version: 1.0.2
IU UUID: 0794CE26E761421987D484491844F7DF Name: LTA_WAR_Package_IU Version: 7.1.1.5
IU UUID: 5094F7205DF3550E4464171617007FD2 Name: WAS_SIU Version: 6.1.0.19
IU UUID: 4BCCD05B7D458FED08B91392544B685E Name: IBM Websphere Application Server Network Deployment Install Programs SIU Version: 6.1.0.19
IU UUID: DF6BF2DED35E0980B36D49E1171A0D99 Name: IBM HTTP Server SIU Version: 6.1.0.5
IU UUID: D35A73EDDD8043EA386474F121CB2603 Name: IBM HTTP Server Install Programs SIU Version: 6.1.0.5
IU UUID: DDCE934782398B3E81431666515AC8B5 Name: DE Extensions Interfaces CLI IU Version: 1.3.1.11
IU UUID: C37109911C8A11D98E1700061BDE7AEA Name: Deployment Engine IU Version: 1.3.1.11
IU UUID: 39BC4EED169A46BCBABE2CF84E9B92F4 Name: MAM71_PACKAGE_IU Version: 7.1.0
IU UUID: DF6BF2DED35E0980B36D49E1171A0D99 Name: IBM HTTP Server SIU Version: 6.1.0.19
IU UUID: D35A73EDDD8043EA386474F121CB2603 Name: IBM HTTP Server Install Programs SIU Version: 6.1.0.19
IU UUID: 443D6188FFFFBEEFBABEAB257CFFFFFF Name: CCMDB Log Trace Analyzer PM Language Support IU Version: 7.1.1
IU UUID: B8E7B73A663E0F93507CA938098FDAE6 Name: Web server plug-ins for WebSphere Application Server SIU Version: 6.1.0.5
IU UUID: 47BA266BABD09EF09132076D2A0A3DF5 Name: Web server plug-ins for WebSphere Application Server Install Programs SIU Version: 6.1.0.5
IU UUID: EF040FD1B664D07D11D8030760FC27DE Name: WAS Update Installer SIU Version: 6.1.0.19
IU UUID: A3E559B8B0FF56FEB3AADE0E071FF84A Name: WAS Update Installer Install Programs SIU Version: 6.1.0.19
IU UUID: 71A1FA732940473ADB80528125CB154B Name: IBM Rational Agent Controller SIU Version: 7.0.3.1
IU UUID: 58A64F8342F8CA7EA3B3DF8AB67DF8DB Name: IBM Rational Agent Controller Install Programs SIU Version: 7.0.3.1
IU UUID: B8E7B73A663E0F93507CA938098FDAE6 Name: Web server plug-ins for WebSphere Application Server SIU Version: 6.1.0.19
IU UUID: 47BA266BABD09EF09132076D2A0A3DF5 Name: Web server plug-ins for WebSphere Application Server Install Programs SIU Version: 6.1.0.19
IU RootIU UUID: 0E35A86B92424AE2B94CACB48CCFE623 Name: Common_PMP Version: 7.1.1.5
IU RootIU UUID: 14D0AD20636FA1A6CC8B6A47A70C53E7 Name: IBM Websphere Application Server Network Deployment Version: 6.1.0.19
IU RootIU UUID: 167210CE0B3E47D395F906A9C939E9DB Name: MADT_RootIU Version: 1.0.2
IU RootIU UUID: 24213C7D1B5E55A8EA2136D74D5A5519 Name: IBM HTTP Server Version: 6.1.0.19
IU RootIU UUID: 24213C7D1B5E55A8EA2136D74D5A5519 Name: IBM HTTP Server Version: 6.1.0.5
IU RootIU UUID: 56CB9E49C593486BBE0B140FC9796034 Name: LTA_WAR_Package Version: 7.1.1
IU RootIU UUID: 56CB9E49C593486BBE0B140FC9796034 Name: LTA_WAR_Package Version: 7.1.1.5
IU RootIU UUID: 70E41B7F4A204AB9B0131EB6E28E80AA Name: EAM711Package Version: 7.1
Feature (RootIU UUID: 0E35A86B92424AE2B94CACB48CCFE623 Name: Maximo Common PMP Language Support Feature)Feature Name:Maximo Common PMP Language
Run solutioninstaller –action showinstalled –type all
C:\ibm\SMP\bin>solutioninstaller -action showinstalled -type all
CTGIN0055I: The process solution installation client received the following command: "-action showinstalled -type all ".
CTGIN0054I: The command is correctly formed and will be sent to the process solution installation service.
CTGIN0059I: There are currently "5" installed process solution element packages that matched the specified criteria.
Name Version Solution Type Package Type Unique Identifier
=================================== ======= =============== ============ ===================================
Application Deployment Toolkit 1.0.2 Process Manager Product Full Update 167210CE0B3E47D395F906A9C939E9DB
base services Package 7.1.1 Process Manager Product Full Update 56CB9E49C593486BBE0B140FC9796034
base services Package 7.1.1.5 Process Manager Product Incremental Update 56CB9E49C593486BBE0B140FC9796034
IBM Tivoli Maximo Common PMP 7.1.1.5 Process Manager Product Full Update 0E35A86B92424AE2B94CACB48CCFE623
Maximo Asset Management 7.1 Package 7.1 Process Manager Product Base 70E41B7F4A204AB9B0131EB6E28E80AA
Deployment Engine
Backup DE
From command prompt change to c:\program files\ibm\common\acsi
Run setenv
Deployment Engine
Restore DE
From command prompt change to c:\program files\ibm\common\acsi
Run setenv
IBM Tivoli Software
Logs
C:\program files\ibm\common\acsi\logs\<userid>
de_trace.log
de_install.log
de_msg.log
ibm\smp\logs\CTGInstallTracenn.log
ibm\smp\logs\ CTGInstallMessagenn.log
ibm\websphere\appserver\profiles\<maximoprofile-name>\ logs\mxserver folder
SystemOut.log
SystemErr.log
Trace.log
ibm\smp\maximo\tools\maximo\log
Package-Specific Action Trace Logs (Maximo Admin Machine)
ibm\smp\solutions\logs\<package-name>
LogZipper
Concerns
Build number in file build711.name (ibm\smp\logs)
Build number 20080502D3 – 7.1.1 GA level (May 2008 release)
Build number 20080702D – 7.1.1 DCR 269 deliverable (not shipped by CCMDB, shipped by MAM and TAMIT, July 2008)
Build number of 20081023D – 7.1.1 Refresh #1 level (October 2008)
Build number of 20090306D2 – 7.1.1 Refresh #2 level (March 2009)
What’s new in Maximo Asset Management 7.1 document - 1380517
Concerns
Properties are stored in the Maximo database, and in ibm\smp\maximo\applications\maximo\properties\maximo.properties and ibm\smp\etc\install.properties
maximo.properties precedes database value
Properties and values in the maxprop and maxpropvalues tables
*
Concerns
System configuration properties not in the database if maxinst is run using an upgraded database
Cannot have multiple Maximo environments on one Maximo administrative machine and maintain them separately
Users and passwords used during the initial installation to be used for Fix Packs, Add-ons, etc.
Logs hard to read through and error messages difficult to understand
No uninstall process
Troubleshooting
Troubleshooting
PSI requires access to the maxprop and maxpropvalues tables to determine configuration settings required for package deployment
Properties are defined during the installation
If the PSI is unable to access these required properties, PSI fails immediately with the message CTGIN0210E
When encountering this error, perform the following checks:
Ensure that the Maximo Database is started and accessible from the Maximo Admin Workstation
*
Manually start the install
From a command prompt change to the location of the installer
Run
Or
Rename server (‘-’ can be used)
CTGIN2395E: User maximo already exists and password does not match
Issue with remote configuration enablement of the remote system
Exception thrown trying to get a copy of ConfigurationProperties object
ACUASI0110E File setupPSIEnv.bat with the path C:\IBM\SMP\bin\setupPSIEnv.bat does not exist.,
com.ibm.ac.common.hosts.CreationFailedException
Missing system configuration properties in the database
Ensure that the system configuration properties exist in the maxpropvalue table and contain the correct value
Document 1377418
CTGIN0143E: An action error occurred during the processing of a deployment operation. Action identifier: "Rebuild_Maximo_EAR". Action display name: "Maximo EAR Rebuild Script" or tools.jar not found building maximo.ear.
Create a lib folder under ibm\smp\maximo\tools\java
Copy tools.jar from ibm\smp\maximo\applications\maximo\lib folder
Paste the tools.jar into the ibm\smp\maximo\tools\java folder
Troubleshooting
Properties have gotten out of sync with actual configuration, so other product additions or fixpacks fail
Message: "CTGIN2233I WebSphere Node Agent Not Running" in the status bar of the installer. Node Agent is up and running
In the wsadmin.traceout there are messages indicating the credentials are no longer valid:
javax.management.JMRuntimeException: ADMN0022E: Access is denied for the getProcessType operation on Server MBean because of insufficient or empty credentials
0000000a AbstractShell A WASX7093I: Issuing message: "WASX7246E: Cannot establish "SOAP" connection to host "hostname.com" because of an authentication failure
In the CTGInstallTrace00.log also shows authentication errors:
Input Error: Can not find script file “C:\IBM\SMP\wasclient\sleep.vbs".
WASX7246E: Cannot establish "SOAP" connection to host "hostname.com" because of an authentication failure
FINE: ENTER^^S^CTGIN2233I: WebSphere NodeAgent is not Running.
*
com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndDEHealthAction handleInstall
FINE: NOTE ^** ERROR: Autonomic Deployment Engine installation/upgrade failure.Return code: 3
Failure: DE in use or general failure See the CCMDB si_inst.log and DE logs for additional information.
com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndDEHealthAction failInstall
FINE: ENTER^^n^ com.ibm.tivoli.ccmdb.install.foundation.ccmdb.FndDEHealthAction failInstall
FINE: NOTE ^Setting flags to opt-out of configuration due to DE installation failure.^n^
One DE return code is 3, which usually means DE is in use or can't be used
Check if the DE service is up and running (IBM ADE service)
Check if the DE directory has lock files that are holding onto the DE instance.
c:\program files\ibm\common\acsi folder, .lock and .lck files
Delete the lock files
DE Deployment Failures
Listiu command reports no output or a return code of 2
The Deployment Engine is not in a working state
Check the de_trace.log files to determine the exact nature of the failure
Cycle the DE service (IBM ADE Service)
Uninstall/install DE
Delete c:\program files\ibm\common\acsi folder, .lock and .lck files
From command prompt change to ibm\smp\de folder
Include Java in the path
Set path=c:\ibm\smp\jre\bin;%PATH%
Uninstall DE
Troubleshooting
Fix Pack Installs may fail with CTGRI00001E if maximo.properties file is not encrypted
ibm\smp\maximo\applications\maximo\properties
mxe.encrypted=true
encrypted password
From command prompt change to ibm\smp\maximo\tools\maximo
Run encryptproperties
ISC War Deployment Failures
The below exception is causing war file removal to fail. This may be caused by another process holding a lock to a file w/in the PortalLogTraceAnaylzer.war directory
java.io.IOException: CTGRI0009E C:\Program Files\IBM\WebSphere\AppServer\systemApps\isclite.ear\PortalLogTraceAnalyzer.war cannot be removed
Failure when trying to deploy using a userid that is not root, or doesn't have the right set of permissions. Most often evidenced by the installer hanging during the deployment of a .war file. Further investigation into the dmgr logs from ibm\websphere\appserver\profiles\ctgdmgr01\logs\dmgr and the wsadmin.traceout log from ibm\websphere\appserver\profiles\ctgdmgr01\logs shows:
00000049 AppBinaryProc E Exception from run: org.eclipse.jst.j2ee.commonarchivecore.internal.exception.SaveFailureException: IWAE0017E Unable to replace original archive: C:\IBM\WebSphere\AppServer\systemApps\isclite.ear\PortalLogTraceAnalyzer.war
*
Delete browser temp files and cookies
*
Search on Severe
Verify Deployment Engine status
1261874 - Parameters to improve Maximo performance using WebSphere
1314060 - Create Windows Service for Node Agent and Maximo Server in WebSphere
7014419 - Product Configuration Matrix
1262959 - Use CURSOR_SHARING=FORCE or SIMILAR for best performance
1263185 - CHAR length semantics are required for the AL32UTF8 character set
1315023 - CTGIN2149E: ... does not have DBA role granted - SQL Server
1394841 - Error when Restoring or Backing up the Deployment Engine
1395223 - Backing up and restoring the Deployment Engine database
1377301 - Maximo 7 Component and/or Fix Pack Installation Fails
1317674 - The installation exits unexpectedly
1366686 - Error: "DE database backup failed" During Maximo 7 Install
1319827 - Get error CTGIN2233I during base services install
1380393 - 7.1.1.0 license install failing on user wasadmin
1399355 - Middleware fails to install when hostname has underscore characters
1317135 - CTGIN2289E: The process manager package null install failed
1391499 - Maximo Asset Management Installer does not open from the Launch Pad
1327383 - 7.1.1.1 or 7.1.1.x Base Services installation missing prerequisites
1377418 - Maximo 7 Component and/or Fix Pack Installation Issue
1319341 - CTGRI0011E - An error occurred when accessing the remote registry
1318525 - Error CTGIN0143E occurs deploying the Maximo.ear file
1390265 - Encountering error CTGIN9035E while using the middleware installation program
1315640 - Base Services installation incorrectly requests TADDM Configuration location
1406016 - 7.1 Middleware install hangs, IE Enhanced Security Configuration error
1328888 - "Required Base Version Is Not Installed" Error
1366394 - Installation launchpad fails to start MWI on Linux
1366438 - LaunchPad.exe will not initialize on Windows
7015423 - Installing middleware
1321228 - Installing Tivoli Asset Management for IT and Maximo Asset Management on 64-bit systems
1389624 - CTGIN2395E: User maximo already exists and password does not match
1392272 - Updating environment data
1378193 - Update 7.1.1.4 hanging
1378147 - The launchpad for Maximo Asset Management industry solutions and add-on products does not start when using Windows Vista or Windows Server 2008
7014370 - Installation of Maximo 7.1 getting permission CTGIN9036E error
1405028 - 7.1.1.5 Installation Run Configuration Steps Options
1405034 - Start Center links do not work
IBM Tivoli Software
Future
Better troubleshooting and recovery
TPAE version will be 7.1.1.6
*
Questions?
Click on the hand icon on the icon toolbar at the top of your screen to indicate you have a question. We will assign you a microphone. You can activate the microphone by pressing the control key on your keyboard
Or type your question into the chat window of the web conferencing tool.
For general questions about the STE program or to request specific topics feel free to email:
[email protected]
Please visit the STE website for information on upcoming or past events:

Sheyam Maximo 7 Installation Tips and Tricks

Documents

Transcript of Sheyam Maximo 7 Installation Tips and Tricks