IBM Business Analytics Proven Practices: Revival Procedure for Predictive Maintenance and Quality Solution

Product(s): IBM Predictive Maintenance and Quality; Area of Interest: Business Analytics

A description of the steps to revive the IBM Predictive Maintenance and Quality Solution environment after an outage.

Sudarshan Tirumani Narayanan, Install and Build Engineer, IBM

Sudarshan Narayanan is a Senior Install and Build Engineer in IBM PMQ team (BA). He has worked on various installer and build technologies for different products with in IBM. He has an overall 9 years of experience. He played a key role in the design and development of IBM Predictive Maintenance and Quality Installer.



Sunil Gajula, Install Engineer, IBM

Sunil Gajula is an Install Engineer in IBM PMQ team (BA). He has worked on various installer technologies. He has an overall 6 years of experience and holds an M C A Degree in Computer Science stream.



28 January 2014

Also available in Russian

Introduction

Purpose of Document

The IBM Predictive Maintenance and Quality Solution resides over a five node inter-communicated architecture with the operating system being Red Hat Enterprise Linux 6.3. The IBM Predictive Maintenance and Quality Solution involves a plethora of strongly interlinked products which becomes a daunting task to revive them all to the right state after an outage. This document describes the steps to revive the IBM Predictive Maintenance and Quality Solution environment after an outage.

Applicability

This document applies to IBM Predictive Maintenance and Quality version 1.0.

Assumptions

The reader should have basic Linux skills and needs to be knowledgeable of the install locations and IP addresses of each node.


Overview

Getting the IBM Predictive Maintenance and Quality (PMQ) environment back to the right state involves several steps and procedures that will be walked through in detail below. Each section will describe the process for starting each node to retain its integrity.


Revival of Data Node (PMQ Database Node)

The Data Node is the first node in the IBM Predictive Maintenance and Quality product which needs to be enabled before any other node.

Please follow the following steps to properly start the Data Node.

  1. Connect to the Data Node and sign on as a root user to achieve a command line for the upcoming commands. This can be done using tools such as PuTTY.
  2. On the command line, type in the following command to switch the user from root to the DB2 Instance User, which is db2inst1.
    su – db2inst1
  3. Once the control has passed to the DB2 Instance User, issue the following command to load DB2.
    db2
  4. After DB2 starts it will leave the focus on a DB2 command line. Using DB2 commands, verify the four required databases are running. These databases are as follows:
    • IBMPMQ (PMQ Specific Database)
    • SPSSDB (Analytics Specific Database)
    • MDMDB (Master Data Management Specific Database)
    • COG102CS (Cognos Specific Database)
    To start the databases, issue the following four commands:
    activate database IBMPMQ
    activate database SPSSDB
    activate database COG102CS
    activate database MDMDB

    After the commands have been issued, use the list command to ensure the 4 databases have been started as follows:
    list active databases

    If successful, all four databases will be running and listed along with the path to each database.

After starting the four databases with the above steps the Data Node is enabled and ready.


Revival of BI Node (PMQ Business Intelligence Node)

The second node in the IBM Predictive Maintenance and Quality product which needs to be enabled is the Business Intelligence (BI) Node. The IBM Cognos BI server has been deployed over an IBM WebSphere server and an HTTP server which both need to be started.

Please follow the following steps to properly start the BI Node servers. All directory listings are default installation locations and the syntax should be adjusted as appropriate if non-default locations were chosen.

  1. Connect to the BI Node and sign on as a root user to achieve a command line for the upcoming commands. This can be done using tools such as PuTTY.
  2. First item to start is the HTTP server. Start the HTTP server with the following commands:
    cd /opt/IBM/HTTPServer/bin/
    apachectl -k start –f /opt/IBM/HTTPServer/conf/httpd.conf
  3. Next we start IBM WebSphere which will deploy the IBM Cognos applications using the following commands. The start of WebSphere can take several minutes to complete but when finished the message “Server Server1 open for e-business” will be displayed.
    cd /opt/IBM/WebSphere/AppServer/profiles/COGNOSProfile/bin
    ./startServer.sh server1
  4. After the command prompt is returned the IBM Cognos BI Dispatcher will continue to initialize and it could take up to 10 minutes to start the IBM Cognos BI Server. After waiting a few minutes, open a browser and navigate to the IBM Cognos BI URL at http://<CognosBINodeIPAddress>/ibmcognos/.

With a successful connection to the IBM Cognos BI URL the BI Node is enabled and running.


Revival of ESB Node (PMQ Enterprise Service Bus Node)

The third node the IBM Predictive Maintenance and Quality product which needs to enabled is the Enterprise Service Bus (ESB) Node.

What follows are the steps to get the ESB node of PMQ enabled. All directory listings are default installation locations and the syntax should be adjusted as appropriate if non-default locations were chosen.

  1. Connect to the ESB Node and sign on as a root user to achieve a command line for the upcoming commands. This can be done using tools such as PuTTY.
  2. On the command line, enter the following command to switch the user from root to the mqm user. All the activity in the ESB node must be done by the mqm user and not by the root user.
    su – mqm
  3. Under the mqm profile start pmqbroker and pmqmanager using the following commands:
    cd /opt/ibm/mqsi/8.0.0.1/bin
    ./mqsilist pmqbroker
  4. To verify the services have all started properly, run the following command and verify the results:
    ./mqsilist pmqbroker –e pmqgroup

    You should see the following messages:
    BIP1275I: Application ‘PMQEventLoad’ on execution group ‘pmqgroup’ is running.
    BIP1275I: Application ‘PMQIntegration’ on execution group ‘pmqgroup’ is running.
    BIP1275I: Application ‘PMQMasterDataLoad’ on execution group ‘pmqgroup’ is running.
    BIP1275I: Application ‘PMQMaximoIntegration’ on execution group ‘pmqgroup’ is running.
    BIP1275I: Application ‘OnboardingFileData’ on execution group ‘pmqgroup’ is running.
    BIP8071I:  Successful command completion.

With a successful message returned the ESB Node is enabled and running.


Revival of Analytic Node (PMQ Analytics Node)

The fourth node in the IBM Predictive Maintenance and Quality product which needs to be enabled is the Analytic Node which contains the IBM SPSS products Collaboration and Deployment Services (C&DS), Modeler and Statistics.

What follows are the steps to get the Analytic Node of PMQ enabled. All directory listings are default installation locations and the syntax should be adjusted as appropriate if non-default locations were chosen.

  1. Connect to the Analytic Node and sign on as a root user to achieve a command line for the following commands. This can be done using tools such as PuTTY.
  2. To launch Collaboration and Deployment Services (C&DS), start the server using the following commands:
    cd /opt/IBM/WebSphere/AppServer/profiles/SPSSProfile/bin
    ./startServer.sh server1
  3. After the message “Server Server1 is open for e-business” and the command prompt is returned, start the Modeler server using the following commands:
    cd /usr/IBM/SPSS/ModelerServer/15.0/
    ./modelersvr.sh start
  4. After the command prompt is returned and a successful start message is displayed, start the Statistics server using the following commands:
    cd /opt/IBM/SPSS/StatisticsServer21/bin
    ./start_statistics_server –d
  5. After the command prompt is returned check whether the Statistics server process is running, using the following command:
    ps –ef | grep statisticsd

    Review the output, if the server is running it will appear as the first process in the list and the Statistics Server is now ready to accept connections from end users.
  6. After confirmation that the Statistic Server is running, open a browser and navigate to the C&DS URL at http://<AnalyticsNodeIP>:9080/config. Upon the display of the Decision Management login screen, the Analytics Node is enabled and running.

Revival of MDM Node (PMQ Master Data Management Node)

The final node in the IBM Predictive Maintenance and Quality product which needs to be enabled is the Master Data Management (MDM) Node.

The below are the steps to get the MDM node enabled. All directory listings are default installation locations and the syntax should be adjusted as appropriate if non-default locations were chosen.

  1. Connect to the MDM node and sign on as a root user to achieve a command line for the upcoming commands. This can be done using tools such as PuTTY.
  2. Once logged in navigate to the IBM WebSphere application directory containing the MDM server and start the server using the following commands.
    cd /opt/IBM/WebSphere/AppServer/profiles/MDMProfile/bin
    ./startServer.sh server1
  3. Once the WebSphere is started and the “Server Server1 open for e-business” message is returned, navigate to the Master Data Management installation location and start the MDM Server by issuing the following commands.
    cd /opt/IBM/MDMPIM/bin/go/
    ./start_local_rmlogs.sh
  4. Starting the MDM Server will take several minutes as it starts seven different services. When the command line prompt is returned, open an Internet Explorer browser version 8 or higher and navigate to the MDM URL at http://<MDMNodeIPAddress>:7507/utils/enterLogin.jsp. When the login screen appears in the browser the MDM Node is enabled and running.

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Big data and analytics on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Big data and analytics
ArticleID=961453
ArticleTitle=IBM Business Analytics Proven Practices: Revival Procedure for Predictive Maintenance and Quality Solution
publish-date=01282014