Skip to main content

Maximo Installation : Pre Requisite Checker Tool


Saludos Amigos !

Today we are going to take a look at pretty essential time & effort saving Pre Requisite technique related with IBM Maximo installation.
As we know that IBM Maximo is a unique product which need multiple components in technology stack for installation. Generally with IBM Maximo version 75 and 76 , binaries can be divided into 2 parts -

MAM- Maximo Asset Management Binaries - these binaries consist base product files , tools required to apply add -on etc.
MWI- Middleware Installer Binaries- these binaries consist following components whose version varies as per compatibility with MAM versions-
     Application Server - IBM Web Sphere , Oracle Web Logic
     Web Server- IBM HTTPS Server 
     Database Server - IBM DB2 , Oracle , Sql Server
     Directory Server - IBM Tivoli Directory Server

In order to install all these products we need different servers and infrastructure components as per compatibility matrix given by IBM. In order to ensure that we are using correct infrastructure and other technology stack components , Pre requisite check should be done  before start installation of Maximo to avoid errors & failures during installation process due to infrastructure incompatibility.  

To do this tpae_req_check.bat should be used in Maximo 75 and Maximo 76.  This file can be found at following locations -
Maximo 75 Location: .\Maximo Launch Pad\Install\MWI\SystemRequirements

Maximo 76 Location: .\Maximo Launch Pad\SystemRequirements

Go to locations given above in respective version of installers and run tpae_req_check.bat as shown below. Once it'll start , provide input to check what kind of component you want to install on this machine- 

Once started utility will ask different details like Port# for DB2 , Drive to install different Web sphere etc  in this machine.  Provide the values as shown in screen shot below-

Once done , Tivoli Pre-requisite scanner will launch and provide details of different components as after checking machine configuration. 
Before proceed installation all checks should be PASS to ensure 100% hardware compatibility with Maximo Installer.  
Tool will display multiple properties after check and its results. All properties details of this tool result can be find out at link - 
http://www-01.ibm.com/support/knowledgecenter/SSLKT6_7.6.0/com.ibm.mam.inswas.doc/install/t_programmaticallyverifyingprereqs.html






Comments

  1. Wonderful bloggers like yourself who would positively reply encouraged me to be more open and engaging in commenting. So know it's helpful..
    Asset Management Software
    Asset Management System
    Asset Management and Maintenance Software
    Asset Management Solutions
    Fixed Asset Management Software

    ReplyDelete
  2. Thanks for sharing such a valuable information.. Great post.
    Banak Paving, we are paving stone specialist. We have installed hundreds of driveways and love the creativity it allows. If you have a special project in mind paving stones may just be the way to go.
    Concrete Paving Winnipeg
    Pads installation Winnipeg

    ReplyDelete

Post a Comment

Popular posts from this blog

Maximo OSLC Integration with External System- Get data in JSON format

Greetings! If you have noticed recent version of Maximo, couple new application in Integration module has been added which are OSLC Resources and OSLC Provider.These modules gives us ability to integrate with external system in JSON. OSLC is an open community that creates specifications for the integration of products and/or tools.  IBM is a leading contributor to this community and many software products within the IBM Software Group are implementing OSLC in order to enable cross-product integrations. An OSLC integration requires 2 players-  1. OSLC Consumer application 2. OSLC Provider application.   An OSLC provider application makes containers of associated resources(data) available for integration through service providers. Consumer applications then use these service providers to query resources and to create, update, and delete resource data.  The consumer application sends a query to the service provider for resource data. The service provider provides a link

Power of Maximo Formulas - Build logic w/o Custom Java code or Automation Script

Greetings! Maximo 7.6 has lot of additional capabilities added in Tivoli Automation Engine as compared to older versions of Maximo which aim to allow users to make change in applications for small requirements without actually going to customization route. Automation scripts is one of such tool given for users and technical developers to change the behavior of Maximo in case where functionalities can't be changed only via use of configuration. If we have a requirement to populate some field on basis of other fields , we can easily do that with automation script but in order to do that you still need to have knowledge of Jython or Javascript to write the logic. Maximo formula is one the tool given by IBM which can be used for such business requirements and user can make changes to Maximo logic via configuration without getting into difficulties of coding. Formulas are available from Maximo version 7603. With release of Maximo version 7606, there has been addition of new capabil

Call publish channel w/o enabling Event Listener in Maximo

Greetings! Generally if we have to send data to external system via MIF, we create Publish Channel and enable Event Listener on publish channel. Once event listener is enabled, Maximo listens for event and send data to end point via publish channel for each Save of related MBO . But t here are many scenarios where we need to send data to external system using publish channel on specific event and not for every save. In order  to send to external system on specific event, for example - sent data to Ariba when PO status in Maximo is changed to APPR, we can use automation script or java code to call publish channel on the go. Below code can be used in automation script - server = MXServer.getMXServer() userInfo = mbo.getUserInfo() whereClause = <CONDITION> server.lookup("MIC").exportData("<Publish Channel Name>", "<External System Name>", whereClause, userInfo, 1000) Via Java class - MXServer server = MXServer.getMXServer();