Introduction IBM Predictive Maintenance and Quality uses data from multiple sources to give you the information that you need to make informed operational, maintenance, repair, or component replacement decisions. IBM Predictive Maintenance and Quality provides you with operational intelligence data, which enables you to perform the following tasks:Understand, monitor, predict, and control product and process variability.Perform in-depth root cause failure analysis.Identify incorrect operating practices.Enhance equipment and process diagnostics capabilities.It also provides you with asset performance management capabilities that help you to achieve these goals:Have forward visibility into equipment and process performance.Increase asset uptime.Identify safety issues.Identify improper maintenance procedures.Optimize maintenance intervals and procedures. AudienceThis document is intended to help users install Predictive Maintenance and Quality. Finding information To find documentation on the web, including all translated documentation, access IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter). Accessibility features Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products. Some of the components included in the IBM Predictive Maintenance and Quality solution have accessibility features. For more information, see Accessibility features Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products. . IBM Predictive Maintenance and Quality HTML documentation has accessibility features. PDF documents are supplemental and, as such, include no added accessibility features. Forward-looking statements This documentation describes the current functionality of the product. References to items that are not currently available may be included. No implication of any future availability should be inferred. Any such references are not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of features or functionality remain at the sole discretion of IBM.

Introduction

IBM® Predictive Maintenance and Quality uses data from multiple sources to give you the information that you need to make informed operational, maintenance, repair, or component replacement decisions.

IBM Predictive Maintenance and Quality provides you with operational intelligence data, which enables you to perform the following tasks:

Understand, monitor, predict, and control product and process variability.

Perform in-depth root cause failure analysis.

Identify incorrect operating practices.

Enhance equipment and process diagnostics capabilities.

It also provides you with asset performance management capabilities that help you to achieve these goals:

Have forward visibility into equipment and process performance.

Increase asset uptime.

Identify safety issues.

Identify improper maintenance procedures.

Optimize maintenance intervals and procedures.

Audience

This document is intended to help users install Predictive Maintenance and Quality.

Finding information

To find documentation on the web, including all translated documentation, access IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter).

Accessibility features

Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products. Some of the components included in the IBM Predictive Maintenance and Quality solution have accessibility features. For more information, see Accessibility features.

IBM Predictive Maintenance and Quality HTML documentation has accessibility features. PDF documents are supplemental and, as such, include no added accessibility features.

Forward-looking statements

This documentation describes the current functionality of the product. References to items that are not currently available may be included. No implication of any future availability should be inferred. Any such references are not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of features or functionality remain at the sole discretion of IBM.

What's new in version 2.5.2The following new features are available in IBM Predictive Maintenance and Quality 2.5.2. Solution installerA new solution installer is available for installations on 64-bit Red Hat Enterprise Linux Server Edition version 6 (x86_64 with update 5, 6, or 7) operating systems. The solution installer provides a new user interface for flexible deployment topology creation. This installer provides a simplified set of prerequisite libraries for loading the installer. It also includes pre-built templates and other enhancements that help ensure a smooth Predictive Maintenance and Quality custom or silent installation into an enterprise environment. For more information, see the following topics: Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution. Install the Predictive Maintenance and Quality server artifactsThe server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.Other updatesIBM Predictive Maintenance and Quality 2.5.2 also includes recent supporting program updates and fixes available at the time of release.

What's new in version 2.5.2

The following new features are available in IBM® Predictive Maintenance and Quality 2.5.2.

Solution installer

A new solution installer is available for installations on 64-bit Red Hat Enterprise Linux Server Edition version 6 (x86_64 with update 5, 6, or 7) operating systems. The solution installer provides a new user interface for flexible deployment topology creation. This installer provides a simplified set of prerequisite libraries for loading the installer. It also includes pre-built templates and other enhancements that help ensure a smooth Predictive Maintenance and Quality custom or silent installation into an enterprise environment.

For more information, see the following topics:

Install the Predictive Maintenance and Quality servers

Install the Predictive Maintenance and Quality server artifacts

Other updates

IBM Predictive Maintenance and Quality 2.5.2 also includes recent supporting program updates and fixes available at the time of release.

Predictive Maintenance and QualityWith IBM Predictive Maintenance and Quality, you can monitor, analyze, and report on information that is gathered from devices. In addition, recommendations for actions can be generated by Predictive Maintenance and Quality.IBM Predictive Maintenance and Quality is an integrated solution that you can use to perform the following tasks:Predict the failure of an instrumented asset so that you can prevent costly unexpected downtime. Make adjustments to predictive maintenance schedules and tasks to reduce repair costs and minimize downtime.Quickly mine maintenance logs to determine the most effective repair procedures and maintenance cycles. Identify the root cause of asset failure faster so that you can take corrective actions.Identify quality and reliability issues definitively and in a timely way.Instrumented assets generate data such as device ID, timestamp, temperature, and status code. This data can be collected and used with maintenance records and other data in models that predict when an asset is likely to fail.Examples of instrumented assets are manufacturing equipment, mining equipment, drilling equipment, farming equipment, security equipment, cars, trucks, trains, helicopters, engines, cranes, oil platforms, and wind turbines.For example, an oil refinery is a system that combines thousands of interlocking pieces. It is critical that such a system is able to work safely and efficiently. You can use IBM Predictive Maintenance and Quality to monitor and track the lifecycle of each piece of the refinery, such as each pipe, pump, compressor, valve, furnace, turbine, tank, heat exchange unit, and boiler. Reports give you the information to ensure that you have the necessary parts available and can schedule repairs during periods of inactivity.Predictive maintenanceIn predictive maintenance, you look for patterns in the usage and environmental information for equipment that correlate with failures that take place. This information is used to create predictive models to score incoming new data. You can predict the likelihood of failure. Scores are generated from this information that give you an indication of the health of the piece of equipment. In addition, key performance indicators (KPIs) are collected, which are used for reporting. KPIs help you to identify assets that do not conform to normal patterns of behavior. You can define rules to generate recommendations when a piece of equipment is identified as having a high probability of failure. Recommendations can be fed into other systems so that people are alerted to them automatically.Predictive quality in manufacturingPast operations data, environmental data, and historical defect data can be used to identify the causes of elevated defect rates. This information is used in predictive models, so that when incoming data is fed into the models, you can predict the likely defect rates. The predicted values are then used for analysis and reporting and to drive recommendations such as modification to inspection patterns, or recalibration of machinery. Scoring can be done on a near real-time basis. Predictive Maintenance and Quality can also detect quality and reliability problems faster than traditional techniques.Single-server installationIn a single-server IBM Predictive Maintenance and Quality installation, the components for each node are installed to the same computer. Each node is configured to run on a separate WebSphere Application Server profile.Multiple-server installationIn a multiple-server installation, each IBM Predictive Maintenance and Quality node provides a specific function for the solution. Each node must be installed on a separate computer or on a separate virtual machine image from other nodes.High-availability installationYou can choose to copy the installation programs for all of the IBM Predictive Maintenance and Quality component programs to a computer, and then manually install the components individually.

Predictive Maintenance and Quality

With IBM® Predictive Maintenance and Quality, you can monitor, analyze, and report on information that is gathered from devices. In addition, recommendations for actions can be generated by Predictive Maintenance and Quality.

IBM Predictive Maintenance and Quality is an integrated solution that you can use to perform the following tasks:

Predict the failure of an instrumented asset so that you can prevent costly unexpected downtime.

Make adjustments to predictive maintenance schedules and tasks to reduce repair costs and minimize downtime.

Quickly mine maintenance logs to determine the most effective repair procedures and maintenance cycles.

Identify the root cause of asset failure faster so that you can take corrective actions.

Identify quality and reliability issues definitively and in a timely way.

Instrumented assets generate data such as device ID, timestamp, temperature, and status code. This data can be collected and used with maintenance records and other data in models that predict when an asset is likely to fail.

Examples of instrumented assets are manufacturing equipment, mining equipment, drilling equipment, farming equipment, security equipment, cars, trucks, trains, helicopters, engines, cranes, oil platforms, and wind turbines.

For example, an oil refinery is a system that combines thousands of interlocking pieces. It is critical that such a system is able to work safely and efficiently. You can use IBM Predictive Maintenance and Quality to monitor and track the lifecycle of each piece of the refinery, such as each pipe, pump, compressor, valve, furnace, turbine, tank, heat exchange unit, and boiler. Reports give you the information to ensure that you have the necessary parts available and can schedule repairs during periods of inactivity.

Predictive maintenance

In predictive maintenance, you look for patterns in the usage and environmental information for equipment that correlate with failures that take place. This information is used to create predictive models to score incoming new data. You can predict the likelihood of failure. Scores are generated from this information that give you an indication of the health of the piece of equipment. In addition, key performance indicators (KPIs) are collected, which are used for reporting. KPIs help you to identify assets that do not conform to normal patterns of behavior. You can define rules to generate recommendations when a piece of equipment is identified as having a high probability of failure. Recommendations can be fed into other systems so that people are alerted to them automatically.

Predictive quality in manufacturing

Past operations data, environmental data, and historical defect data can be used to identify the causes of elevated defect rates. This information is used in predictive models, so that when incoming data is fed into the models, you can predict the likely defect rates. The predicted values are then used for analysis and reporting and to drive recommendations such as modification to inspection patterns, or recalibration of machinery. Scoring can be done on a near real-time basis.

Predictive Maintenance and Quality can also detect quality and reliability problems faster than traditional techniques.

Single-server installation
In a single-server IBM Predictive Maintenance and Quality installation, the components for each node are installed to the same computer. Each node is configured to run on a separate WebSphere® Application Server profile.

Multiple-server installation
In a multiple-server installation, each IBM Predictive Maintenance and Quality node provides a specific function for the solution. Each node must be installed on a separate computer or on a separate virtual machine image from other nodes.

High-availability installation
You can choose to copy the installation programs for all of the IBM Predictive Maintenance and Quality component programs to a computer, and then manually install the components individually.

Single-server installationIn a single-server IBM Predictive Maintenance and Quality installation, the components for each node are installed to the same computer. Each node is configured to run on a separate WebSphere Application Server profile.For example, the Business Intelligence (BI) node is installed to a WebSphere Application Server profile named CUSTOMProfile that is using port number 9080. The Predictive Analytics node components are installed to a WebSphere Application Server profile named CNDSProfile that is using port number 9082. Each profile runs on the same WebSphere Application Server instance.The following table lists the port numbers for each WebSphere Application Server instance:Port numbers for WebSphere Application ServersComponentAdmin portSSL admin portApplication portBusiness Intelligence (BI) node906090409080IBM SPSS614181MDM624282A single-server installation should be used only for a test or demonstration environment.Predictive Maintenance and QualityWith IBM Predictive Maintenance and Quality, you can monitor, analyze, and report on information that is gathered from devices. In addition, recommendations for actions can be generated by Predictive Maintenance and Quality.

Single-server installation

In a single-server IBM® Predictive Maintenance and Quality installation, the components for each node are installed to the same computer. Each node is configured to run on a separate WebSphere® Application Server profile.

For example, the Business Intelligence (BI) node is installed to a WebSphere Application Server profile named CUSTOMProfile that is using port number 9080. The Predictive Analytics node components are installed to a WebSphere Application Server profile named CNDSProfile that is using port number 9082. Each profile runs on the same WebSphere Application Server instance.

The following table lists the port numbers for each WebSphere Application Server instance:

Table 1. Port numbers for WebSphere Application Servers

Component | Admin port | SSL admin port | Application port
Business Intelligence (BI) node | 9060 | 9040 | 9080
IBM SPSS | 61 | 41 | 81
MDM | 62 | 42 | 82

Important: A single-server installation should be used only for a test or demonstration environment.

Parent topic: Predictive Maintenance and Quality

Multiple-server installationIn a multiple-server installation, each IBM Predictive Maintenance and Quality node provides a specific function for the solution. Each node must be installed on a separate computer or on a separate virtual machine image from other nodes.The following diagram shows the nodes in a multiple-server architecture.Predictive Maintenance and Quality nodesPredictive Maintenance and Quality nodesPredictive Analytics nodeThe Analytics node provides predictive scores and offers recommendations.This node has the following software installed:IBM WebSphere Network DeploymentIBM SPSS Collaboration and Deployment ServicesIBM SPSS Modeler ServerIBM SPSS Modeler Solution PublisherIBM SPSS Modeler Server PremiumIBM SPSS Data Access PackIBM SPSS Modeler Collaboration and Deployment Services AdapterIBM SPSS Decision ManagementIBM SPSS Statistics ServerIBM SPSS Statistics Collaboration and Deployment Services AdapterIBM DB2 Client (not installed for Oracle Database server installation type)Business Intelligence (BI) nodeThe BI node provides dashboards and reports.This node has the following software installed:IBM WebSphere Network DeploymentIBM HTTP ServerIBM Cognos Business IntelligenceIBM DB2 Client Integration Bus nodeThe Integration Bus node processes events, updates the content for IBM Cognos Business Intelligence, and triggers predictive scoring and decision management. It also loads master data into the solution.This node has the following software installed:IBM WebSphere MQIBM Integration BusIBM Integration ExplorerIBM Integration Bus ODBC Database ExtenderIBM DB2 ClientMaster Data Management (MDM) nodeThe MDM node manages the master data for the solution. The master data includes the set of devices that supply events to the solution and their locations. It also includes metadata that is used to determine how events are processed by the solution.This node has the following software installed:IBM WebSphere Network DeploymentIBM InfoSphere Master Data Management Collaboration EditionIBM DB2 Client The MDM node is an optional node for either an Express Deployment or a Custom Deployment. If you install the MDM node, the Deployment Wizard does not show all of the details for the MDM node in the progress messages. For example, the MDM node dos not appear during the IBM DB2 Server Runtime Client deployment task. Progress messages for the MDM node are shown only during the Master Data Management deployment task.Data nodeThe data node provides the database server that contains the databases that are used by other products in the solution. The database acts as an event store and holds calculated key performance indicators (KPIs) and profiles. It also contains supporting master data for the solution.This node has the following software installed:IBM DB2 Enterprise Server Edition If you choose to use your own Oracle Database server for your Predictive Maintenance and Quality data and reports, then your deployment does not need a separate data node computer. IBM DB2 Enterprise Server Edition is installed on the Analytics node and is used for the MDM, SPSS, and IBM Cognos content store databases. Predictive Maintenance and QualityWith IBM Predictive Maintenance and Quality, you can monitor, analyze, and report on information that is gathered from devices. In addition, recommendations for actions can be generated by Predictive Maintenance and Quality.

Multiple-server installation

In a multiple-server installation, each IBM® Predictive Maintenance and Quality node provides a specific function for the solution. Each node must be installed on a separate computer or on a separate virtual machine image from other nodes.

The following diagram shows the nodes in a multiple-server architecture.

Figure 1. Predictive Maintenance and Quality nodes

Predictive Analytics node

The Analytics node provides predictive scores and offers recommendations.

This node has the following software installed:

IBM WebSphere® Network Deployment

IBM SPSS® Collaboration and Deployment Services

IBM SPSS Modeler Server

IBM SPSS Modeler Solution Publisher

IBM SPSS Modeler Server Premium

IBM SPSS Data Access Pack

IBM SPSS Modeler Collaboration and Deployment Services Adapter

IBM SPSS Decision Management

IBM SPSS Statistics Server

IBM SPSS Statistics Collaboration and Deployment Services Adapter

IBM DB2® Client (not installed for Oracle Database server installation type)

Business Intelligence (BI) node

The BI node provides dashboards and reports.

This node has the following software installed:

IBM WebSphere Network Deployment

IBM HTTP Server

IBM Cognos® Business Intelligence

IBM DB2 Client

Integration Bus node

The Integration Bus node processes events, updates the content for IBM Cognos Business Intelligence, and triggers predictive scoring and decision management. It also loads master data into the solution.

This node has the following software installed:

IBM WebSphere MQ

IBM Integration Bus

IBM Integration Explorer

IBM Integration Bus ODBC Database Extender

IBM DB2 Client

Master Data Management (MDM) node

The MDM node manages the master data for the solution. The master data includes the set of devices that supply events to the solution and their locations. It also includes metadata that is used to determine how events are processed by the solution.

This node has the following software installed:

IBM WebSphere Network Deployment

IBM InfoSphere® Master Data Management Collaboration Edition

IBM DB2 Client

The MDM node is an optional node for either an Express Deployment or a Custom Deployment.

If you install the MDM node, the Deployment Wizard does not show all of the details for the MDM node in the progress messages. For example, the MDM node dos not appear during the IBM DB2 Server Runtime Client deployment task. Progress messages for the MDM node are shown only during the Master Data Management deployment task.

Data node

The data node provides the database server that contains the databases that are used by other products in the solution. The database acts as an event store and holds calculated key performance indicators (KPIs) and profiles. It also contains supporting master data for the solution.

This node has the following software installed:

IBM DB2 Enterprise Server Edition

If you choose to use your own Oracle Database server for your Predictive Maintenance and Quality data and reports, then your deployment does not need a separate data node computer. IBM DB2 Enterprise Server Edition is installed on the Analytics node and is used for the MDM, SPSS, and IBM Cognos content store databases.

Parent topic: Predictive Maintenance and Quality

High-availability installationYou can choose to copy the installation programs for all of the IBM Predictive Maintenance and Quality component programs to a computer, and then manually install the components individually.This option does not install the programs or configure them. The installation and configuration must be done manually. Use this option to deploy Predictive Maintenance and Quality if you have specific configuration requirements that are not available from the single-server or multiple-server options in the Predictive Maintenance and Quality solution installer. For information on how to install the individual components, refer to the component product documentation. Predictive Maintenance and QualityWith IBM Predictive Maintenance and Quality, you can monitor, analyze, and report on information that is gathered from devices. In addition, recommendations for actions can be generated by Predictive Maintenance and Quality.

High-availability installation

You can choose to copy the installation programs for all of the IBM® Predictive Maintenance and Quality component programs to a computer, and then manually install the components individually.

This option does not install the programs or configure them. The installation and configuration must be done manually. Use this option to deploy Predictive Maintenance and Quality if you have specific configuration requirements that are not available from the single-server or multiple-server options in the Predictive Maintenance and Quality solution installer. For information on how to install the individual components, refer to the component product documentation.

Parent topic: Predictive Maintenance and Quality

Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.You must also install additional prerequisite software on some computers, including the Business Intelligence (BI) node , the Master Data Management (MDM) node, and the Integration Bus node computers.The computers or virtual machines that you use for Predictive Maintenance and Quality nodes must not have any of the included software already installed.Critical installation and configuration issuesTo review a list of critical installation and configuration issues for IBM Predictive Maintenance and Quality version 2.5.2 as of the date of release, see the document titled Critical installation and configuration issues for IBM Predictive Maintenance and Quality version 2.5.2 (www.ibm.com/support/docview.wss?uid=swg21975691). Supported operating systems and hardware requirementsReview the minimum hardware and operating system requirements before you install IBM Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation.Adding each node computer to the hosts fileTo ensure that each IBM Predictive Maintenance and Quality node computer can communicate properly, you must add all node computers to the hosts file on each node computer.Installing Java on the Predictive Analytics node computerYou must install a Java Runtime Environment (JRE) on the computer you use as the IBM Predictive Maintenance and Quality Analytics node.Installing Python and PyXML on the Predictive Analytics node computer (optional)If you want to use Python, then you must install Python and PyXML on the computer you use as the IBM Predictive Maintenance and Quality Analytics node.Installing R software on the Predictive Analytics node computer (optional)If you want to use R, you must install R and Essentials for R software on the computer you use as the IBM Predictive Maintenance and Quality Analytics node.Install Perl on the MDM node computerYou must install a version of Perl on the Master Data Management (MDM) node computer for IBM Predictive Maintenance and Quality.Setting ulimit values on nodes where WebSphere Application Server is to be installedBefore you install IBM Predictive Maintenance and Quality, you must ensure that you have appropriate ulimit values on each node where WebSphere Application Server is to be installed.Creating directories for the solution installerYou must create a directory on each computer on which you install an IBM Predictive Maintenance and Quality component.Mounting the USB hard disk driveThe installation files for IBM Predictive Maintenance and Quality are provided on a universal serial bus (USB) hard disk drive. You can run the installation from the USB or you can copy the files to your computer before you start the installation. Before you do either, you must mount the USB hard disk drive.Update the services file for IBM DB2 portsYou must update the /etc/services file before and after you install IBM Predictive Maintenance and Quality.

Prerequisites and installation preparation

Before you install IBM® Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

You must also install additional prerequisite software on some computers, including the Business Intelligence (BI) node , the Master Data Management (MDM) node, and the Integration Bus node computers.

Important: The computers or virtual machines that you use for Predictive Maintenance and Quality nodes must not have any of the included software already installed.

Critical installation and configuration issues

To review a list of critical installation and configuration issues for IBM Predictive Maintenance and Quality version 2.5.2 as of the date of release, see the document titled Critical installation and configuration issues for IBM Predictive Maintenance and Quality version 2.5.2 (www.ibm.com/support/docview.wss?uid=swg21975691).

Supported operating systems and hardware requirements
Review the minimum hardware and operating system requirements before you install IBM Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation.

Adding each node computer to the hosts file
To ensure that each IBM Predictive Maintenance and Quality node computer can communicate properly, you must add all node computers to the hosts file on each node computer.

Installing Java on the Predictive Analytics node computer
You must install a Java™ Runtime Environment (JRE) on the computer you use as the IBM Predictive Maintenance and Quality Analytics node.

Installing Python and PyXML on the Predictive Analytics node computer (optional)
If you want to use Python, then you must install Python and PyXML on the computer you use as the IBM Predictive Maintenance and Quality Analytics node.

Installing R software on the Predictive Analytics node computer (optional)
If you want to use R, you must install R and Essentials for R software on the computer you use as the IBM Predictive Maintenance and Quality Analytics node.

Install Perl on the MDM node computer
You must install a version of Perl on the Master Data Management (MDM) node computer for IBM Predictive Maintenance and Quality.

Setting ulimit values on nodes where WebSphere Application Server is to be installed
Before you install IBM Predictive Maintenance and Quality, you must ensure that you have appropriate ulimit values on each node where WebSphere Application Server is to be installed.

Creating directories for the solution installer
You must create a directory on each computer on which you install an IBM Predictive Maintenance and Quality component.

Mounting the USB hard disk drive
The installation files for IBM Predictive Maintenance and Quality are provided on a universal serial bus (USB) hard disk drive. You can run the installation from the USB or you can copy the files to your computer before you start the installation. Before you do either, you must mount the USB hard disk drive.

Update the services file for IBM DB2 ports
You must update the /etc/services file before and after you install IBM Predictive Maintenance and Quality.

Supported operating systems and hardware requirementsReview the minimum hardware and operating system requirements before you install IBM Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation. For an up-to-date list of environments that are supported by Predictive Maintenance and Quality, see the IBM Software Product Compatibility Reports (www.ibm.com/support/docview.wss?uid=swg27041626).Server computers The Predictive Maintenance and Quality server components must be installed on computers that are running the 64-bit Red Hat Enterprise Linux Server Edition version 6.5, 6.6, or 6.7 (x86_64) operating system. Hardware requirements for a multiple server environmentAt a minimum, each computer or virtual machine that hosts a Predictive Maintenance and Quality server component, or node, must have the following hardware requirements: 4 processors8 GB of RAM500 GB of hard disk space The computer from which you run the installation must have sufficient disk space that is allotted to the / directory. For the computer where you are running the installation, the minimum recommended disk space for the / directory is 150 GB. Each node computer should have a minimum of 100 GB of disk space that is allocated to the / directory. If you are installing from the universal serial bus (USB) hard disk drive, you must have 300 GB of disk space allocated to the / directory. If you are expecting to store large volumes of data, you might need to increase your disk size. Each node must be installed on a separate computer or on a separate virtual machine image. The home directory on the database node must have a minimum of 30 GB. The temporary location of the solution installer is /var/chef/cache. To accommodate the solution installer files, there must be a minimum of 100 GB on /var.Hardware requirements for a single-server environmentAt a minimum, the computer or virtual machine on which you install Predictive Maintenance and Quality must have the following hardware requirements: 4 processors8 GB of RAM500 GB of hard disk space The computer from which you run the installation must have sufficient disk space that is allotted to the / directory. For the computer where you are running the installation, the minimum recommended disk space for the / directory is 400 GB. A single-server installation should be used only for a test or demonstration environment.User requirementsYou must have root or sudo access to all of the computers on which you install a Predictive Maintenance and Quality node, including the computer from which you run the installation. Installation directory requirementsThe file paths that you specify in the solution installer must not include your user home directory. For example, if you are a sudo user called sample, your home directory is /home/sample. Do not include this path in the file paths that you specify when you are configuring the nodes in solution installer.Oracle Database To use Oracle Database for your Predictive Maintenance and Quality data and reports, instead of IBM DB2, ensure that you have completed the following requirements: Install Oracle Database 12cInstall and configure Oracle Database 12c Release 1 (12.1.0.2.0) Enterprise Edition for Microsoft Windows (x64). Ensure that it is available in your network and that you can connect to it.Install Oracle Database ClientInstall Oracle Database Client on the computer that you will use as the BI node. When you install Oracle Database Client, select the Java 6 option.Client computers The Predictive Maintenance and Quality client components must be installed on computers that run Microsoft Windows 7 or Microsoft Windows 8 operating systems. At a minimum, the computer where you run the Deployment Wizard for the client components must have the following hardware requirements: 2 processors4 GB of RAM200 GB of hard disk space Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.Modifying the sudoers file for the user who runs the installationTo run the IBM Predictive Maintenance and Quality installation you must be either root user or have sudo permission on each node computer.Installing required operating system packages for all nodesSpecific operating system packages must be installed on each computer or virtual machine where you install an IBM Predictive Maintenance and Quality node.Installing required operating system packages on the BI node computerSpecific operating system packages must be installed on the Linux operating system computer or virtual machine where you install the Business Intelligence (BI) node node.Installing required operating system packages on the Integration Bus node computerSpecific operating system packages must be installed on the Linux operating system computer or virtual machine where you install the IBM Predictive Maintenance and Quality Integration Bus node node.Additional prerequisites for the sudo userThere are additional prerequisites if you use the sudo user to install IBM Predictive Maintenance and Quality.

Supported operating systems and hardware requirements

Review the minimum hardware and operating system requirements before you install IBM® Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation.

For an up-to-date list of environments that are supported by Predictive Maintenance and Quality, see the IBM Software Product Compatibility Reports (www.ibm.com/support/docview.wss?uid=swg27041626).

Server computers

The Predictive Maintenance and Quality server components must be installed on computers that are running the 64-bit Red Hat Enterprise Linux Server Edition version 6.5, 6.6, or 6.7 (x86_64) operating system.

Hardware requirements for a multiple server environment

At a minimum, each computer or virtual machine that hosts a Predictive Maintenance and Quality server component, or node, must have the following hardware requirements:

4 processors

8 GB of RAM

500 GB of hard disk space

The computer from which you run the installation must have sufficient disk space that is allotted to the / directory. For the computer where you are running the installation, the minimum recommended disk space for the / directory is 150 GB. Each node computer should have a minimum of 100 GB of disk space that is allocated to the / directory.

Important: If you are installing from the universal serial bus (USB) hard disk drive, you must have 300 GB of disk space allocated to the / directory.

If you are expecting to store large volumes of data, you might need to increase your disk size.

Each node must be installed on a separate computer or on a separate virtual machine image.

The home directory on the database node must have a minimum of 30 GB.

The temporary location of the solution installer is /var/chef/cache. To accommodate the solution installer files, there must be a minimum of 100 GB on /var.

Hardware requirements for a single-server environment

At a minimum, the computer or virtual machine on which you install Predictive Maintenance and Quality must have the following hardware requirements:

4 processors

8 GB of RAM

500 GB of hard disk space

The computer from which you run the installation must have sufficient disk space that is allotted to the / directory. For the computer where you are running the installation, the minimum recommended disk space for the / directory is 400 GB.

Important: A single-server installation should be used only for a test or demonstration environment.

User requirements

You must have root or sudo access to all of the computers on which you install a Predictive Maintenance and Quality node, including the computer from which you run the installation.

Installation directory requirements

The file paths that you specify in the solution installer must not include your user home directory. For example, if you are a sudo user called "sample", your home directory is /home/sample. Do not include this path in the file paths that you specify when you are configuring the nodes in solution installer.

Oracle Database

To use Oracle Database for your Predictive Maintenance and Quality data and reports, instead of IBM DB2®, ensure that you have completed the following requirements:

Install Oracle Database 12c

Install and configure Oracle Database 12c Release 1 (12.1.0.2.0) Enterprise Edition for Microsoft Windows (x64). Ensure that it is available in your network and that you can connect to it.

Install Oracle Database Client

Install Oracle Database Client on the computer that you will use as the BI node. When you install Oracle Database Client, select the Java™ 6 option.

Client computers

The Predictive Maintenance and Quality client components must be installed on computers that run Microsoft Windows 7 or Microsoft Windows 8 operating systems.

At a minimum, the computer where you run the Deployment Wizard for the client components must have the following hardware requirements:

2 processors

4 GB of RAM

200 GB of hard disk space

Modifying the sudoers file for the user who runs the installation
To run the IBM Predictive Maintenance and Quality installation you must be either root user or have sudo permission on each node computer.

Installing required operating system packages for all nodes
Specific operating system packages must be installed on each computer or virtual machine where you install an IBM Predictive Maintenance and Quality node.

Installing required operating system packages on the BI node computer
Specific operating system packages must be installed on the Linux operating system computer or virtual machine where you install the Business Intelligence (BI) node node.

Installing required operating system packages on the Integration Bus node computer
Specific operating system packages must be installed on the Linux operating system computer or virtual machine where you install the IBM Predictive Maintenance and Quality Integration Bus node node.

Additional prerequisites for the sudo user
There are additional prerequisites if you use the sudo user to install IBM Predictive Maintenance and Quality.

Parent topic: Prerequisites and installation preparation

Modifying the sudoers file for the user who runs the installationThis topic has been updated as per Sudarshan's SI document.To run the IBM Predictive Maintenance and Quality installation you must be either root user or have sudo permission on each node computer.To install with sudo user permissions, you must also add the user to the sudoers file.Log in as root user.Enter the following command to open the sudoers file for editing:visudo -f /etc/sudoersAt the end of the file, add the following line for your user:username ALL=(ALL) ALLPress the Esc key, and enter :wq to save and close the file.Repeat these steps on each computer on which you install a Predictive Maintenance and Quality node.Supported operating systems and hardware requirementsReview the minimum hardware and operating system requirements before you install IBM Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation.

Modifying the sudoers file for the user who runs the installation

To run the IBM® Predictive Maintenance and Quality installation you must be either root user or have sudo permission on each node computer.

To install with sudo user permissions, you must also add the user to the sudoers file.

Procedure

Log in as root user.

Enter the following command to open the sudoers file for editing:

visudo -f /etc/sudoers

At the end of the file, add the following line for your user:

username ALL=(ALL) ALL

Press the Esc key, and enter :wq to save and close the file.

Repeat these steps on each computer on which you install a Predictive Maintenance and Quality node.

Parent topic: Supported operating systems and hardware requirements

Installing required operating system packages for all nodesThis topic has been updated with content from Sudarshan's SI document. Also resolves defect 27738. Note nfs.utils is required for the artifacts installation but you can install it at the same time as the other rpms. (Sunil).Specific operating system packages must be installed on each computer or virtual machine where you install an IBM Predictive Maintenance and Quality node.Ensure that the following packages are installed on every node in your deployment. These are the minimum versions required:compat-libstdc++-33-3.2.3-69.el6.i686.rpmcompat-libstdc++-33-3.2.3-69.el6.x86_64.rpmpam-1.1.1-20.el6.i686.rpmnfs.utils.rpmYou can download the packages from a site such as pkgs.org or rpm.pbone.net.Log on to the computer as the root user or as a user with sudo permissions.Type the following command to verify that an operating system package is installed:rpm -qi full_package_nameFor example, to verify that compat-libstdc++-33-3.2.3-69.el6.i686.rpm is installed, type rpm -qi compat-libstdc++-33-3.2.3-69.el6.i686.You might have to use sudo to run the command successfully.For example, enter sudo rpm -qi full_package_name.Install any package that is not already installed.You must download any missing package, and then install the downloaded package by typing the following command:rpm -ihv full_package_name.rpmFor example, to install compat-libstdc++-33-3.2.3-69.el6.i686.rpm, type rpm -ihv compat-libstdc++-33-3.2.3-69.el6.i686.rpm. To install pam-1.1.1-20.el6.i686.rpm, use the following command: rpm -ihv -force pam-1.1.1-20.el6.i686.rpm.rpm.Repeat these steps on each computer on which you install a Predictive Maintenance and Quality node.If you have yum repositories configured for your Linux operating system computers, you can use the following command to install all of the prerequisite RPMs: yum -y install --setopt=protected_multilib=false compat-libstdc++.i686 compat-libstdc++Supported operating systems and hardware requirementsReview the minimum hardware and operating system requirements before you install IBM Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation.

Installing required operating system packages for all nodes

Specific operating system packages must be installed on each computer or virtual machine where you install an IBM® Predictive Maintenance and Quality node.

Ensure that the following packages are installed on every node in your deployment. These are the minimum versions required:

compat-libstdc++-33-3.2.3-69.el6.i686.rpm

compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm

pam-1.1.1-20.el6.i686.rpm

nfs.utils.rpm

You can download the packages from a site such as pkgs.org or rpm.pbone.net.

Procedure

Log on to the computer as the root user or as a user with sudo permissions.

Type the following command to verify that an operating system package is installed:

rpm -qi full_package_name

For example, to verify that compat-libstdc++-33-3.2.3-69.el6.i686.rpm is installed, type rpm -qi compat-libstdc++-33-3.2.3-69.el6.i686.

Note: You might have to use sudo to run the command successfully.

For example, enter sudo rpm -qi full_package_name.

Install any package that is not already installed.

You must download any missing package, and then install the downloaded package by typing the following command:

rpm -ihv full_package_name.rpm

For example, to install compat-libstdc++-33-3.2.3-69.el6.i686.rpm, type rpm -ihv compat-libstdc++-33-3.2.3-69.el6.i686.rpm.

To install pam-1.1.1-20.el6.i686.rpm, use the following command: rpm -ihv -force pam-1.1.1-20.el6.i686.rpm.rpm.

Repeat these steps on each computer on which you install a Predictive Maintenance and Quality node.

If you have yum repositories configured for your Linux operating system computers, you can use the following command to install all of the prerequisite RPMs:

yum -y install --setopt=protected_multilib=false compat-libstdc++.i686 compat-libstdc++

Parent topic: Supported operating systems and hardware requirements

Installing required operating system packages on the BI node computerThis topic has been updated with content from Sudarshan's SI document. The content of this topic resolves defect 27315.Specific operating system packages must be installed on the Linux operating system computer or virtual machine where you install the Business Intelligence (BI) node node. For a complete list of software requirements for IBM Cognos Business Intelligence, see the Cognos Business Intelligence 10.2.2 Supported Software Environments page (www.ibm.com/support/docview.wss?uid=swg27042164).You must ensure that the following 32-bit packages are installed. These are the minimum versions required:openmotif-2.3.3-4.el6.i686.rpmlibgcc-4.8.3-9.el7.i686.rpmlibselinux-2.0.94-5.3.el6.i686.rpmcracklib-2.8.16-4.el6.i686.rpmdb4-4.7.25-17.el6.i686.rpmaudit-libs-2.2-2.el6.i686.rpmpam-1.1.1-13.el6.i686.rpmlibXtst-1.0.99.2-3.el6.i686.rpmapr-util-1.3.9-3.el6_0.1.i686.rpmYou can download the packages from a site such as pkgs.org or rpm.pbone.net.Log on to the BI node computer as the root user or as a user with sudo permissions.Type the following command to verify that an operating system package is installed:rpm -qi package_nameFor example, to verify that libselinux is installed and what version you have, type rpm -qi libselinux.You might have to use sudo to run the command successfully.For example, enter sudo rpm -qi full_package_name.Install any package that is not already installed.You must download any missing package, and then install the downloaded package by typing the following command:rpm -ihv full_package_name.rpmSudarshan's document doesn't list the version of pam required. Verify the version listed below. For example, to install libselinux-2.0.94-5.3.el6.i686.rpm, type rpm -ihv libselinux-2.0.94-5.3.el6.i686.rpm.If you have yum repositories configured for your Linux operating system computers, you can use the following command to install all of the prerequisite RPMs: yum -y install --setopt=protected_multilib=false libselinux.i686 cracklib.i686 db4.i686 audit-libs.i686 pam.i686 openmotif openmotif.i686 libgcc.i686 libXtst.i686 apr-util.i686 If you can't get the pam library downloaded, then download the library on to the RHEL environment, and use the following command to install it: rpm –ihv –force pam library name.Supported operating systems and hardware requirementsReview the minimum hardware and operating system requirements before you install IBM Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation.

Installing required operating system packages on the BI node computer

Specific operating system packages must be installed on the Linux operating system computer or virtual machine where you install the Business Intelligence (BI) node node.

For a complete list of software requirements for IBM® Cognos® Business Intelligence, see the Cognos Business Intelligence 10.2.2 Supported Software Environments page (www.ibm.com/support/docview.wss?uid=swg27042164).

You must ensure that the following 32-bit packages are installed. These are the minimum versions required:

openmotif-2.3.3-4.el6.i686.rpm

libgcc-4.8.3-9.el7.i686.rpm

libselinux-2.0.94-5.3.el6.i686.rpm

cracklib-2.8.16-4.el6.i686.rpm

db4-4.7.25-17.el6.i686.rpm

audit-libs-2.2-2.el6.i686.rpm

pam-1.1.1-13.el6.i686.rpm

libXtst-1.0.99.2-3.el6.i686.rpm

apr-util-1.3.9-3.el6_0.1.i686.rpm

You can download the packages from a site such as pkgs.org or rpm.pbone.net.

Procedure

Log on to the BI node computer as the root user or as a user with sudo permissions.

Type the following command to verify that an operating system package is installed:

rpm -qi package_name

For example, to verify that libselinux is installed and what version you have, type rpm -qi libselinux.

Note: You might have to use sudo to run the command successfully.

For example, enter sudo rpm -qi full_package_name.

Install any package that is not already installed.

You must download any missing package, and then install the downloaded package by typing the following command:

rpm -ihv full_package_name.rpm

For example, to install libselinux-2.0.94-5.3.el6.i686.rpm, type rpm -ihv libselinux-2.0.94-5.3.el6.i686.rpm.

Tip: If you have yum repositories configured for your Linux operating system computers, you can use the following command to install all of the prerequisite RPMs:

yum -y install --setopt=protected_multilib=false libselinux.i686 cracklib.i686 db4.i686 audit-libs.i686 pam.i686 openmotif openmotif.i686 libgcc.i686 libXtst.i686 apr-util.i686

If you can't get the pam library downloaded, then download the library on to the RHEL environment, and use the following command to install it: rpm –ihv –force pam library name.

Parent topic: Supported operating systems and hardware requirements

Installing required operating system packages on the Integration Bus node computerThis topic has been updated with content from Sudarshan's SI document. The content of this topic resolves defect 27315.Specific operating system packages must be installed on the Linux operating system computer or virtual machine where you install the IBM Predictive Maintenance and Quality Integration Bus node node.Ensure that the following 32-bit or 64-bit packages are installed. These are the minimum versions required:gtk2-2.24.23-6.el6.i686.rpmlibXtst-1.0.99.2-3.el6.i686.rpmglibc-2.12-1.80.el6.i686.rpmlibgcc-4.8.3-9.el7.i686.rpmwebkitgtk-1.4.3-9.el6.i686.rpmwebkitgtk-1.4.3-9.el6.x86_64.rpmYou can download the packages from a site such as pkgs.org or rpm.pbone.net.Log on to the computer as the root user or as a user with sudo permissions.Type the following command to verify that an operating system package is installed:rpm -qi package_nameFor example, to verify that gtk2 is installed and what version you have, type rpm -qi gtk2.You might have to use sudo to run the command successfully.For example, enter sudo rpm -qi full_package_name.Install any package that is not already installed.You must download any missing package, and then install the downloaded package by typing the following command:rpm -ihv full_package_name.rpmFor example, to install gtk2-2.24.23-6.el6.i686, type rpm -ihv gtk2-2.24.23-6.el6.i686.rpm.If you have yum repositories configured for your Linux operating system computers, you can use the following command to install all of the prerequisite RPMs: yum -y install --setopt=protected_multilib=false gtk2.i686 libXtst.i686 glibc.i686 libgcc.i686 webkitgtk.i686 webkitgtkSupported operating systems and hardware requirementsReview the minimum hardware and operating system requirements before you install IBM Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation.

Installing required operating system packages on the Integration Bus node computer

Specific operating system packages must be installed on the Linux operating system computer or virtual machine where you install the IBM® Predictive Maintenance and Quality Integration Bus node node.

Ensure that the following 32-bit or 64-bit packages are installed. These are the minimum versions required:

gtk2-2.24.23-6.el6.i686.rpm

libXtst-1.0.99.2-3.el6.i686.rpm

glibc-2.12-1.80.el6.i686.rpm

libgcc-4.8.3-9.el7.i686.rpm

webkitgtk-1.4.3-9.el6.i686.rpm

webkitgtk-1.4.3-9.el6.x86_64.rpm

You can download the packages from a site such as pkgs.org or rpm.pbone.net.

Procedure

Log on to the computer as the root user or as a user with sudo permissions.

Type the following command to verify that an operating system package is installed:

rpm -qi package_name

For example, to verify that gtk2 is installed and what version you have, type rpm -qi gtk2.

Note: You might have to use sudo to run the command successfully.

For example, enter sudo rpm -qi full_package_name.

Install any package that is not already installed.

You must download any missing package, and then install the downloaded package by typing the following command:

rpm -ihv full_package_name.rpm

For example, to install gtk2-2.24.23-6.el6.i686, type rpm -ihv gtk2-2.24.23-6.el6.i686.rpm.

Tip: If you have yum repositories configured for your Linux operating system computers, you can use the following command to install all of the prerequisite RPMs:

yum -y install --setopt=protected_multilib=false gtk2.i686 libXtst.i686 glibc.i686 libgcc.i686 webkitgtk.i686 webkitgtk

Parent topic: Supported operating systems and hardware requirements

Additional prerequisites for the sudo user There are additional prerequisites if you use the sudo user to install IBM Predictive Maintenance and Quality. Operating system group Create an operating system group with the same name as the sudo user who installs Predictive Maintenance and Quality. For example, if SVC_PMQAdmin is a sudo user doing the installation, then you must create an operating system with name SVC_PMQAdmin. Use the command sudo groupadd SVC_PMQAdmin. A group is also created for the new user. If the group does not exist, create one using the same syntax.Supported operating systems and hardware requirementsReview the minimum hardware and operating system requirements before you install IBM Predictive Maintenance and Quality. The requirements apply for all computers or virtual machines that you use for the installation.

Additional prerequisites for the sudo user

There are additional prerequisites if you use the sudo user to install IBM® Predictive Maintenance and Quality.

Operating system group

Create an operating system group with the same name as the sudo user who installs Predictive Maintenance and Quality. For example, if SVC_PMQAdmin is a sudo user doing the installation, then you must create an operating system with name SVC_PMQAdmin. Use the command sudo groupadd SVC_PMQAdmin. A group is also created for the new user. If the group does not exist, create one using the same syntax.

Parent topic: Supported operating systems and hardware requirements

Adding each node computer to the hosts fileTo ensure that each IBM Predictive Maintenance and Quality node computer can communicate properly, you must add all node computers to the hosts file on each node computer.For example, the hosts file on the data node computer must include the Predictive Analytics node, the Business Intelligence (BI) node, the Master Data Management (MDM) node, and the Integration Bus node computers.On each node computer, open the /etc/hosts file.Ensure that each node computer is listed in the file.For example, ensure that your hosts file contains values such as the following values:127.0.0.1 localhost.localdomain localhost ##.##.##.## analytics_node_name.domain.com analytics_node_name ##.##.##.## bi_node_name.domain.com bi_node_name ##.##.##.## data_node_name.domain.com data_node_name ##.##.##.## integrationbus_node_name.domain.com integrationbus_node_name ##.##.##.## mdm_node_name.domain.com mdm_node_nameSave and close the file.Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Adding each node computer to the hosts file

To ensure that each IBM® Predictive Maintenance and Quality node computer can communicate properly, you must add all node computers to the hosts file on each node computer.

For example, the hosts file on the data node computer must include the Predictive Analytics node, the Business Intelligence (BI) node, the Master Data Management (MDM) node, and the Integration Bus node computers.

Procedure

On each node computer, open the /etc/hosts file.

Ensure that each node computer is listed in the file. For example, ensure that your hosts file contains values such as the following values:

127.0.0.1	localhost.localdomain	localhost
##.##.##.##  analytics_node_name.domain.com  analytics_node_name
##.##.##.##  bi_node_name.domain.com  bi_node_name
##.##.##.##  data_node_name.domain.com  data_node_name
##.##.##.##  integrationbus_node_name.domain.com  integrationbus_node_name
##.##.##.##  mdm_node_name.domain.com  mdm_node_name

Save and close the file.

Parent topic: Prerequisites and installation preparation

Installing Java on the Predictive Analytics node computerYou must install a Java Runtime Environment (JRE) on the computer you use as the IBM Predictive Maintenance and Quality Analytics node.You must install Java version 1.7 or later on the Analytics node computer.Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Installing Java on the Predictive Analytics node computer

You must install a Java™ Runtime Environment (JRE) on the computer you use as the IBM® Predictive Maintenance and Quality Analytics node.

You must install Java version 1.7 or later on the Analytics node computer.

Parent topic: Prerequisites and installation preparation

Installing Python and PyXML on the Predictive Analytics node computer (optional)If you want to use Python, then you must install Python and PyXML on the computer you use as the IBM Predictive Maintenance and Quality Analytics node. Install Python version 2.7.1 or later and PyXML version 0.8.4.Log in to the Analytics node computer as the root user or as a user with sudo permissions.Download and install Python version 2.7.1. You can download the installer from the Python web site (https://www.python.org/download/releases/2.7.1).Download and install PyXML version 0.8.4. You can download the installer from the PyXML web site (https://pypi.python.org/pypi/PyXML/0.8.4).Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Installing Python and PyXML on the Predictive Analytics node computer (optional)

If you want to use Python, then you must install Python and PyXML on the computer you use as the IBM® Predictive Maintenance and Quality Analytics node.

Install Python version 2.7.1 or later and PyXML version 0.8.4.

Procedure

Log in to the Analytics node computer as the root user or as a user with sudo permissions.

Download and install Python version 2.7.1. You can download the installer from the Python web site (https://www.python.org/download/releases/2.7.1).

Download and install PyXML version 0.8.4. You can download the installer from the PyXML web site (https://pypi.python.org/pypi/PyXML/0.8.4).

Parent topic: Prerequisites and installation preparation

Installing R software on the Predictive Analytics node computer (optional)If you want to use R, you must install R and Essentials for R software on the computer you use as the IBM Predictive Maintenance and Quality Analytics node. For more information about R and Essentials for R software for IBM SPSS, see the IBM SPSS documentation (https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/We70df3195ec8_4f95_9773_42e448fa9029/page/Downloads%20for%20IBM%C2%AE%20SPSS%C2%AE%20Statistics).Log in to the Analytics node computer as the root user or as a user with sudo permissions.Download and install R software. You can download the installer from The Comprehensive R Archive Network website (http://cran.r-project.org).Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Installing R software on the Predictive Analytics node computer (optional)

If you want to use R, you must install R and Essentials for R software on the computer you use as the IBM® Predictive Maintenance and Quality Analytics node.

For more information about R and Essentials for R software for IBM SPSS®, see the IBM SPSS documentation (https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/We70df3195ec8_4f95_9773_42e448fa9029/page/Downloads%20for%20IBM%C2%AE%20SPSS%C2%AE%20Statistics).

Procedure

Log in to the Analytics node computer as the root user or as a user with sudo permissions.

Download and install R software. You can download the installer from The Comprehensive R Archive Network website (http://cran.r-project.org).

Parent topic: Prerequisites and installation preparation

Install Perl on the MDM node computerYou must install a version of Perl on the Master Data Management (MDM) node computer for IBM Predictive Maintenance and Quality.You can use the Perl in /usr or you can download and install a commercially distributed Perl such as ActiveState ActivePerl. You must install a minimum version of 5.10.For more information about installing Perl for IBM InfoSphere Master Data Management, see the MDM documentation (www.ibm.com/support/knowledgecenter/SSWSR9_11.4.0/com.ibm.pim.ins.doc/pim_tsk_installingperl.html?cp=SSWSR9_11.4.0%2F1-2-0-1).Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Install Perl on the MDM node computer

You must install a version of Perl on the Master Data Management (MDM) node computer for IBM® Predictive Maintenance and Quality.

You can use the Perl in /usr or you can download and install a commercially distributed Perl such as ActiveState ActivePerl. You must install a minimum version of 5.10.

For more information about installing Perl for IBM InfoSphere Master Data Management, see the MDM documentation (www.ibm.com/support/knowledgecenter/SSWSR9_11.4.0/com.ibm.pim.ins.doc/pim_tsk_installingperl.html?cp=SSWSR9_11.4.0%2F1-2-0-1).

Parent topic: Prerequisites and installation preparation

Setting ulimit values on nodes where WebSphere Application Server is to be installedBefore you install IBM Predictive Maintenance and Quality, you must ensure that you have appropriate ulimit values on each node where WebSphere Application Server is to be installed.You must set ulimit values on the Business Intelligence (BI) node, Predictive Analytics node, and the MDM node.Log in to the Business Intelligence (BI) node computer as the root user or as a user with sudo permissions.Go to the /etc/security directory.Open the limits.conf file for editing.Add the following lines to the file:@root soft nofile 10000 @root hard nofile 16384 * soft nofile 10000 * hard nofile 16384Save and close the file.Restart the computer for the changes to take effect.Log in to the Predictive Analytics node computer as the root user or as a user with sudo permissions.Go to the /etc/security directory.Open the limits.conf file for editing.Add the following lines to the file:@root soft nofile 10000 @root hard nofile 16384 * soft nofile 10000 * hard nofile 16384Save and close the file.Restart the computer for the changes to take effect.Log in to the Master Data Management (MDM) node computer as the root user or as a user with sudo permissions.Go to the /etc/security directory.Open the limits.conf file for editing.Add the following lines to the file:@root soft nofile 10000 @root hard nofile 16384 * soft nofile 10000 * hard nofile 16384Save and close the file.Restart the computer for the changes to take effect.Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Setting ulimit values on nodes where WebSphere Application Server is to be installed

Before you install IBM® Predictive Maintenance and Quality, you must ensure that you have appropriate ulimit values on each node where WebSphere Application Server is to be installed.

About this task

You must set ulimit values on the Business Intelligence (BI) node, Predictive Analytics node, and the MDM node.

Procedure

Log in to the Business Intelligence (BI) node computer as the root user or as a user with sudo permissions.

Go to the /etc/security directory.

Open the limits.conf file for editing.

Add the following lines to the file:

@root soft nofile 10000
@root hard nofile 16384
* soft nofile 10000
* hard nofile 16384

Save and close the file.

Restart the computer for the changes to take effect.

Log in to the Predictive Analytics node computer as the root user or as a user with sudo permissions.

Go to the /etc/security directory.

Open the limits.conf file for editing.

Add the following lines to the file:

@root soft nofile 10000
@root hard nofile 16384
* soft nofile 10000
* hard nofile 16384

Save and close the file.

Restart the computer for the changes to take effect.

Log in to the Master Data Management (MDM) node computer as the root user or as a user with sudo permissions.

Go to the /etc/security directory.

Open the limits.conf file for editing.

Add the following lines to the file:

@root soft nofile 10000
@root hard nofile 16384
* soft nofile 10000
* hard nofile 16384

Save and close the file.

Restart the computer for the changes to take effect.

Parent topic: Prerequisites and installation preparation

Creating directories for the solution installerYou must create a directory on each computer on which you install an IBM Predictive Maintenance and Quality component. The solution installer uses the /opt/IBM directory to copy license files and other files. This directory must exist on each node computer and on the computer on which you run the solution installer before you run the installation.Create an /opt/IBM directory on each computer on which you are going to install an IBM Predictive Maintenance and Quality component.Create an /opt/IBM directory on the computer on which you are going to run the solution installer.Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Creating directories for the solution installer

You must create a directory on each computer on which you install an IBM® Predictive Maintenance and Quality component.

The solution installer uses the /opt/IBM directory to copy license files and other files. This directory must exist on each node computer and on the computer on which you run the solution installer before you run the installation.

Procedure

Create an /opt/IBM directory on each computer on which you are going to install an IBM Predictive Maintenance and Quality component.

Create an /opt/IBM directory on the computer on which you are going to run the solution installer.

Parent topic: Prerequisites and installation preparation

Mounting the USB hard disk driveThe installation files for IBM Predictive Maintenance and Quality are provided on a universal serial bus (USB) hard disk drive. You can run the installation from the USB or you can copy the files to your computer before you start the installation. Before you do either, you must mount the USB hard disk drive.For more information about mounting USB hard disk drives, see the Red Hat Customer Portal (https://access.redhat.com/home).Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Mounting the USB hard disk drive

The installation files for IBM® Predictive Maintenance and Quality are provided on a universal serial bus (USB) hard disk drive. You can run the installation from the USB or you can copy the files to your computer before you start the installation. Before you do either, you must mount the USB hard disk drive.

For more information about mounting USB hard disk drives, see the Red Hat Customer Portal (https://access.redhat.com/home).

Parent topic: Prerequisites and installation preparation

Update the services file for IBM DB2 portsYou must update the /etc/services file before and after you install IBM Predictive Maintenance and Quality.Fast Communications Manager (FCM) is a feature of IBM DB2 that handles communications between database partition servers. When you install the instance-owning database server on the primary computer, DB2 reserves a port range according to the specified number of logical database partition servers that are participating in the partitioned database environment. The default range is four ports in the range 60000-60003.DB2 installation on data node fails if these port ranges are allocated to different services. Therefore, you must comment out the service entries that use this port range in the /etc/services file until the Predictive Maintenance and Quality installation is complete.After the installation of Predictive Maintenance and Quality, replace the port range 60000-60003 entries in /etc/services file with any other available port ranges (the ports must be sequentially numbered). Uncomment the original service that uses the port range 60000-60003.For more information about the port range, see Verifying port range availability on participating computers (Linux and UNIX) (www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/t0011777.html).Prerequisites and installation preparationBefore you install IBM Predictive Maintenance and Quality, ensure that the computers that you use meet the minimum requirements for operating systems, prerequisite software, processing, and disk space.

Update the services file for IBM DB2 ports

You must update the /etc/services file before and after you install IBM® Predictive Maintenance and Quality.

Fast Communications Manager (FCM) is a feature of IBM DB2 that handles communications between database partition servers. When you install the instance-owning database server on the primary computer, DB2 reserves a port range according to the specified number of logical database partition servers that are participating in the partitioned database environment. The default range is four ports in the range 60000-60003.

DB2 installation on data node fails if these port ranges are allocated to different services. Therefore, you must comment out the service entries that use this port range in the /etc/services file until the Predictive Maintenance and Quality installation is complete.

After the installation of Predictive Maintenance and Quality, replace the port range 60000-60003 entries in /etc/services file with any other available port ranges (the ports must be sequentially numbered). Uncomment the original service that uses the port range 60000-60003.

For more information about the port range, see Verifying port range availability on participating computers (Linux and UNIX) (www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.qb.server.doc/doc/t0011777.html).

Parent topic: Prerequisites and installation preparation

Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution. The solution installer runs on a Red Hat Enterprise Linux version 6 (x86_64 with update 5, 6, or 7) operating system. It has a web interface that you use to define, validate, and install your environment. You define your environment by identifying node computers, and dragging the component programs onto the nodes. The solution installer provides guidance for where you can add components and you can use it to validate the environment that you define. The operating system for the computer where you run the solution installer must be set to use English as the language. The solution installer does not run on other languages. The client computers must also be using English as the language.Installation processWith the IBM Predictive Maintenance and Quality server solution installer you can select the individual computers on which each solution node is to be installed and enter configuration information for each software component.Downloading and decompressing the installation filesYou must download the IBM Predictive Maintenance and Quality solution from IBM Passport Advantage, and then decompress the files to run the solution installer.Opening firewall ports for the solution installerYou can run the firewall.sh script to open the ports that are required on the computer on which you are running the IBM Predictive Maintenance and Quality solution installer.Starting the server solution installerYou run the server solution installer on a Red Hat Enterprise Linux operating system. Use the server solution installer to define the servers in the IBM Predictive Maintenance and Quality environment. After the solution installer is running, you access the solution installer interface from another computer by using a web browser and start defining your environment. Using the solution installerYou use the solution installer to define your IBM Predictive Maintenance and Quality environment you want to install.Using a predefined configurationThe solution installer contains predefined configurations for the most common IBM Predictive Maintenance and Quality environments. Use these predefined configurations to simplify your deployment work.Starting the installationThe solution installer installs the component products on each node computer. Before you start the installation, you can validate the configuration.Computer firewall settings to run the server componentsEach IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.Updating the .bashrc file on the MDM node computerIf you installed a Master Data Management (MDM) node with your IBM Predictive Maintenance and Quality environment, you must update the .bashrc file on the MDM node computer. Test the installationAfter the installation of the IBM Predictive Maintenance and Quality server components is complete, you must perform some additional configuration tasks and then test the installation.

Install the Predictive Maintenance and Quality servers

You use the solution installer to deploy the component programs on the servers that make up the solution.

The solution installer runs on a Linux version 6 (x86_64 with update 5, 6, or 7) operating system. It has a web interface that you use to define, validate, and install your environment.

You define your environment by identifying node computers, and dragging the component programs onto the nodes. The solution installer provides guidance for where you can add components and you can use it to validate the environment that you define.

Important: The operating system for the computer where you run the solution installer must be set to use English as the language. The solution installer does not run on other languages. The client computers must also be using English as the language.

Installation process
With the IBM® Predictive Maintenance and Quality server solution installer you can select the individual computers on which each solution node is to be installed and enter configuration information for each software component.

Downloading and decompressing the installation files
You must download the IBM Predictive Maintenance and Quality solution from IBM Passport Advantage, and then decompress the files to run the solution installer.

Opening firewall ports for the solution installer
You can run the firewall.sh script to open the ports that are required on the computer on which you are running the IBM Predictive Maintenance and Quality solution installer.

Starting the server solution installer
You run the server solution installer on a Red Hat Enterprise Linux operating system. Use the server solution installer to define the servers in the IBM Predictive Maintenance and Quality environment. After the solution installer is running, you access the solution installer interface from another computer by using a web browser and start defining your environment.

Using the solution installer
You use the solution installer to define your IBM Predictive Maintenance and Quality environment you want to install.

Using a predefined configuration
The solution installer contains predefined configurations for the most common IBM Predictive Maintenance and Quality environments. Use these predefined configurations to simplify your deployment work.

Starting the installation
The solution installer installs the component products on each node computer. Before you start the installation, you can validate the configuration.

Computer firewall settings to run the server components
Each IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.

Updating the .bashrc file on the MDM node computer
If you installed a Master Data Management (MDM) node with your IBM Predictive Maintenance and Quality environment, you must update the .bashrc file on the MDM node computer.

Test the installation
After the installation of the IBM Predictive Maintenance and Quality server components is complete, you must perform some additional configuration tasks and then test the installation.

Installation processWith the IBM Predictive Maintenance and Quality server solution installer you can select the individual computers on which each solution node is to be installed and enter configuration information for each software component.The diagram shows the installation process being run from one server, the staging server, and the IBM Predictive Maintenance and Quality components are being installed to different computers in a multiple server deployment. The deplscen1.svg needs to be updated to show solution installer instead of deployment wizard.IBM Predictive Maintenance and Quality multiple server installation processPredictive Maintenance and Quality installation processIn the diagram, the staging server represents the computer from which you run the solution installer. In your installation, the staging server can also be used as a node computer. If you use a separate computer as the staging server, that computer must also use the same operating system as the other computers on which you install a node. It must also have the same prerequisites.If you are installing Predictive Maintenance and Quality on a single server, you can install the components to the same computer where you are running the installation.Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution.

Installation process

With the IBM® Predictive Maintenance and Quality server solution installer you can select the individual computers on which each solution node is to be installed and enter configuration information for each software component.

The diagram shows the installation process being run from one server, the staging server, and the IBM Predictive Maintenance and Quality components are being installed to different computers in a multiple server deployment.

Figure 2. IBM Predictive Maintenance and Quality multiple server installation process

In the diagram, the staging server represents the computer from which you run the solution installer. In your installation, the staging server can also be used as a node computer. If you use a separate computer as the staging server, that computer must also use the same operating system as the other computers on which you install a node. It must also have the same prerequisites.

If you are installing Predictive Maintenance and Quality on a single server, you can install the components to the same computer where you are running the installation.

Parent topic: Install the Predictive Maintenance and Quality servers

Downloading and decompressing the installation filesThis topic has been updated with the pmq 2.5.2 installation file names (in c_inst_pmq_names.dita), provided by Ria. Need Sudarshan (or someone) to verify them.You must download the IBM Predictive Maintenance and Quality solution from IBM Passport Advantage, and then decompress the files to run the solution installer. For more information about the files that you must download, see Downloading Predictive Maintenance and Quality 2.5.2 (www.ibm.com/support/docview.wss?uid=swg24041606).Access the IBM Passport Advantage web site.If you receive an error, try using a different web browser to access Passport Advantage.Sign in and navigate to the software downloads page.Find the eImages for IBM Predictive Maintenance and Quality.Download an eImage by selecting the check box beside the name. Download all eImages for IBM Predictive Maintenance and Quality.When the download is complete, a Download Complete message is displayed. The location of the downloaded files are displayed in the message window.You may want to copy the files to another directory for safekeeping. Make note of the directory of this directory because you will refer to it again when you install the artifacts and the client components. Decompress the eImage files.Decompress the sol_installer_1.0.2_l86-64_en.tar.gz file.The file is decompressed to a directory that is named PMQ_2.5.2_linux. You must copy the server tar.gz files into the PMQ_2.5.2_linux directory.Copy the other tar.gz files to the PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Software directory.The tar.gz files that you need are pm_q_svr_2.5.2_1_l86-64_en.tar.gz, pm_q_svr_2.5.2_2_l86-64_en.tar.gz, and pm_q_svr_2.5.2_3_l86-64_en.tar.gz.You can manually decompress the files, or run the PMQ2.5.2_UncompressTarball.sh script to decompress the files.To run the script, enter sh PMQ2.5.2_UncompressTarball.sh. To manually decompress the files, enter tar xvf filesname.tar.gz.Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution.

Downloading and decompressing the installation files

You must download the IBM® Predictive Maintenance and Quality solution from IBM Passport Advantage, and then decompress the files to run the solution installer.

For more information about the files that you must download, see Downloading Predictive Maintenance and Quality 2.5.2 (www.ibm.com/support/docview.wss?uid=swg24041606).

Procedure

Access the IBM Passport Advantage® web site.

Tip: If you receive an error, try using a different web browser to access Passport Advantage.

Sign in and navigate to the software downloads page.

Find the eImages for IBM Predictive Maintenance and Quality.

Download an eImage by selecting the check box beside the name. Download all eImages for IBM Predictive Maintenance and Quality. When the download is complete, a Download Complete message is displayed. The location of the downloaded files are displayed in the message window.

You may want to copy the files to another directory for safekeeping. Make note of the directory of this directory because you will refer to it again when you install the artifacts and the client components.

Decompress the eImage files.

Decompress the sol_installer_1.0.2_l86-64_en.tar.gz file.

The file is decompressed to a directory that is named PMQ_2.5.2_linux. You must copy the server tar.gz files into the PMQ_2.5.2_linux directory.

Copy the other tar.gz files to the PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Software directory.

The tar.gz files that you need are pm_q_svr_2.5.2_1_l86-64_en.tar.gz, pm_q_svr_2.5.2_2_l86-64_en.tar.gz, and pm_q_svr_2.5.2_3_l86-64_en.tar.gz.

You can manually decompress the files, or run the PMQ2.5.2_UncompressTarball.sh script to decompress the files.

To run the script, enter sh PMQ2.5.2_UncompressTarball.sh.

To manually decompress the files, enter tar xvf filesname.tar.gz.

Parent topic: Install the Predictive Maintenance and Quality servers

Opening firewall ports for the solution installerUpdates for 2.5.2 complete. You can run the firewall.sh script to open the ports that are required on the computer on which you are running the IBM Predictive Maintenance and Quality solution installer. You must also open ports on the target, or client, computers on which you are installing a IBM Predictive Maintenance and Quality node. You can use the client_firewall.sh script to open the required ports. The firewall.sh script opens the following ports on the solution installer computer: 8080 incoming443 incoming9683 incoming22 outgoing On the target, or client computers, the client_firewall.sh script opens the following ports: 8080 outgoing443 incoming9683 outgoing22 incomingLog on to the computer that contains the solution installer node as the root user or as a user with sudo permissions.Back up your existing firewall settings by typing the following command: /etc/init.d/iptables save.Go to the directory where you decompressed the solution installer files, and run the firewall script by typing the following command: sh firewall.sh if you are the root user or sudo sh firewall.sh if you are a user with sudo permissions.For example, go to the PMQ_2.5.2_linux/SolutionInstaller directory.Copy the client_firewall.sh file onto each computer on which you are going to install an IBM Predictive Maintenance and Quality node.Log on to each computer on which you are going to install an IBM Predictive Maintenance and Quality node as the root user or as a user with sudo permissions.Back up your existing firewall settings by typing the following command: /etc/init.d/iptables save.Go to the directory where you copied the client_firewall.sh file, and run the script by typing the following command: sh client_firewall.sh.Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution.

Opening firewall ports for the solution installer

You can run the firewall.sh script to open the ports that are required on the computer on which you are running the IBM® Predictive Maintenance and Quality solution installer.

You must also open ports on the target, or client, computers on which you are installing a IBM Predictive Maintenance and Quality node. You can use the client_firewall.sh script to open the required ports.

The firewall.sh script opens the following ports on the solution installer computer:

8080 incoming

443 incoming

9683 incoming

22 outgoing

On the target, or client computers, the client_firewall.sh script opens the following ports:

8080 outgoing

443 incoming

9683 outgoing

22 incoming

Procedure

Log on to the computer that contains the solution installer node as the root user or as a user with sudo permissions.

Back up your existing firewall settings by typing the following command: /etc/init.d/iptables save.

Go to the directory where you decompressed the solution installer files, and run the firewall script by typing the following command: sh firewall.sh if you are the root user or sudo sh firewall.sh if you are a user with sudo permissions. For example, go to the PMQ_2.5.2_linux/SolutionInstaller directory.

Copy the client_firewall.sh file onto each computer on which you are going to install an IBM Predictive Maintenance and Quality node.

Log on to each computer on which you are going to install an IBM Predictive Maintenance and Quality node as the root user or as a user with sudo permissions.

Back up your existing firewall settings by typing the following command: /etc/init.d/iptables save.

Go to the directory where you copied the client_firewall.sh file, and run the script by typing the following command: sh client_firewall.sh.

Parent topic: Install the Predictive Maintenance and Quality servers

Starting the server solution installerUpdates complete.You run the server solution installer on a Red Hat Enterprise Linux operating system. Use the server solution installer to define the servers in the IBM Predictive Maintenance and Quality environment. After the solution installer is running, you access the solution installer interface from another computer by using a web browser and start defining your environment. In this task, you must have access to a computer that is separate from the computer that contains the installation files. This computer has the following requirements: Has a monitor with a screen resolution that is greater than 1024 by 760.The operating system uses English. Has Google Chrome 47, or later, or Mozilla Firefox 38 or later installed on it. The language of the installed web browser language must be English. The installation files must be in a directory for which you have execute permissions. Log on to the computer where you decompressed the installation files as the root user or as a user with sudo permissions.Go to the PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Software directory where you decompressed the solution installer files.If you are the root user, enter the following command: sh setup.sh. If you are a user with sudo permissions, enter the following command: sudo sh setup.sh.Open a web browser on another computer, and go to the solution installer URL: https://servername:8080/UI/index.html.Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer.Now you can access the solution installer from any computer in a Firefox or Chrome web browser.Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution.

Starting the server solution installer

You run the server solution installer on a Red Hat Enterprise Linux operating system. Use the server solution installer to define the servers in the IBM® Predictive Maintenance and Quality environment. After the solution installer is running, you access the solution installer interface from another computer by using a web browser and start defining your environment.

Before you begin

In this task, you must have access to a computer that is separate from the computer that contains the installation files. This computer has the following requirements:

Has a monitor with a screen resolution that is greater than 1024 by 760.

The operating system uses English.

Has Google Chrome 47, or later, or Mozilla Firefox 38 or later installed on it. The language of the installed web browser language must be English.

The installation files must be in a directory for which you have execute permissions.

Procedure

Log on to the computer where you decompressed the installation files as the root user or as a user with sudo permissions.

Go to the PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Software directory where you decompressed the solution installer files.

If you are the root user, enter the following command: sh setup.sh. If you are a user with sudo permissions, enter the following command: sudo sh setup.sh.

Open a web browser on another computer, and go to the solution installer URL: https://servername:8080/UI/index.html.

Important: Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer.

Results

Now you can access the solution installer from any computer in a Firefox or Chrome web browser.

Parent topic: Install the Predictive Maintenance and Quality servers

Using the solution installerUpdates from Sudarshan complete for pmq 2.5.2You use the solution installer to define your IBM Predictive Maintenance and Quality environment you want to install. You define the environment by identifying node computers and adding the software that you want installed on each node. You create an installation configuration for your solution by dragging nodes onto a canvas and then dragging components into the nodes. You can save your configurations. For more information, see Saving and opening configurationsYou can save IBM Predictive Maintenance and Quality configurations and open existing configurations in the solution installer.. You can also load predefined configurations. For more information, see Using a predefined configurationThe solution installer contains predefined configurations for the most common IBM Predictive Maintenance and Quality environments. Use these predefined configurations to simplify your deployment work.. The solution installer runs on Google Chrome 44 or later or Mozilla Firefox 38 or later. It does not run on Internet Explorer. For more information about supported software, see the IBM Software Product Compatibility Reports (www.ibm.com/support/docview.wss?uid=swg27041626).Open the solution installer in a web browser.After the solution installer is running, you can access the URL from any computer from a Firefox or Chrome web browser. The URL is https://servername:8080/UI/index.html, where servername is the name of the computer where you ran the solution installer. Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer. Ensure that you are using an English language web browser to access the solution installer URL.On the license information page, click Accept.Declining the license allows you to uninstall the solution installer and remove all of the files from the solution installer directory.Select New Configuration, and click OK.From the Mandatory Software List pane, drag a Node object onto the Configuration Editor pane. If you are installing IBM Predictive Maintenance and Quality on four nodes, you must drag four Node objects onto the Configuration Editor pane.A visual representation of an empty node is displayed.In the Property Editor pane, select the node object, and enter the following information.Enter a name for the node in Name, and press the Enter key.For example, enter BI node.Enter the server name in Host Name, and press the Enter key.Unless you are using a single node configuration, ensure that the host names or IP addresses are for different computers. Do not use the same computer for more than one Node object.Enter the user who has access to install the components in User Name, and press the Enter key.For example, enter root or a user with sudo permissions.Enter the user's password in User Password, and press the Enter key.Repeat these steps for each node object that you add.If you are installing IBM Predictive Maintenance and Quality on four nodes, you must repeat these steps for each of the four node objects.You must enter any mandatory information for nodes and other objects as indicated. Ensure that you review all of the properties to ensure that the values, both mandatory and optional, are valid. Ensure that you press the Enter key after you type a value for a property.From the Mandatory Software List pane, create your environment by dragging each object onto the appropriate node in the Configuration Editor pane.Valid drop zones are indicated in the Configuration Editor pane. Some restrictions are built into the placement of the objects. For example, if you are adding IBM Cognos BI Server to a node, then you must already have WebSphere Application Server on that node, and the IBM Cognos BI Server object must be placed within the WebSphere Application Server object. Image shows the BI node with the required components. Example environments are provided in the predefined configurations that are included with the installation files. For more information, see Using a predefined configurationThe solution installer contains predefined configurations for the most common IBM Predictive Maintenance and Quality environments. Use these predefined configurations to simplify your deployment work.. If you add the IBM DB2 Data Server Runtime Client component to the same node as the IBM DB2 Enterprise Server component, the IBM DB2 Data Server Runtime Client component will not be installed.After you add an object, select it, and modify any values in the Property Editor pane.When you add WebSphere Application Server to a node, you must provide the following information: WebSphere Install Directory is the location where WebSphere Application Server is to be installed.WebSphere Application Port is the port number that you want to use for WebSphere Application Server.WAS Profile Admin User Name is the administrator user's user name for WebSphere Application Server.WAS Profile Admin Password is the password for the administrator user. Image shows the required configuration properties for the WebSphere Application Server component.Ensure that you press the Enter key after you type a value for a property.From the Optional Software List, drag the objects to the node on which you want the installation files copied. The optional software is not installed by the solution installer. You must install the software manually. The installation files are copied to the node you drag them to.Unless you change the default path, the optional software installation files are copied to the /opt/IBM/OptSoftware directory on the node computer.As you build your environment, click Validate to identify errors or incomplete information.After all nodes are defined and each node is validated, click Run.After you click the Run button, do not close the browser window until the installation completes. If you close the browser, you cannot re-initiate the session.However, the installation does proceed even with the browser closed. But you cannot monitor the progress.If the browser window closes, do the following steps:Do nothing until enough time elapses to allow the installation to complete. Allow the installation at least 2 hours to complete.Open a new browser window, and open the solution installer again.Re-create the configuration that you used or open the saved session that you used. You must ensure that all of the values that you entered in the fields are the same as the configuration that you used when the browser window closed.Rerun the installation. The solution installer verifies that all of the components are installed.After the solution installer completes, verify that the components are working. For more information, see Test the installationAfter the installation of the IBM Predictive Maintenance and Quality server components is complete, you must perform some additional configuration tasks and then test the installation.. If you click Validate before all the mandatory content is added, a message indicates that the node is not valid. For example, if you validate the BI Node before you add the IBM DB2 Data Server Runtime Client component, then a message indicates that the node is not yet valid.Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution. Configuration properties for the server componentsYou must provide some configuration properties for each of the mandatory software components.Saving and opening configurationsYou can save IBM Predictive Maintenance and Quality configurations and open existing configurations in the solution installer.

Using the solution installer

You use the solution installer to define your IBM® Predictive Maintenance and Quality environment you want to install.

You define the environment by identifying node computers and adding the software that you want installed on each node. You create an installation configuration for your solution by dragging nodes onto a canvas and then dragging components into the nodes.

You can save your configurations. For more information, see Saving and opening configurations.

You can also load predefined configurations. For more information, see Using a predefined configuration.

Important: The solution installer runs on Google Chrome 44 or later or Mozilla Firefox 38 or later. It does not run on Internet Explorer.

For more information about supported software, see the IBM Software Product Compatibility Reports (www.ibm.com/support/docview.wss?uid=swg27041626).

Procedure

Open the solution installer in a web browser.

After the solution installer is running, you can access the URL from any computer from a Firefox or Chrome web browser.

The URL is https://servername:8080/UI/index.html, where servername is the name of the computer where you ran the solution installer.

Important: Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer.

Ensure that you are using an English language web browser to access the solution installer URL.

On the license information page, click Accept.

CAUTION:

Declining the license allows you to uninstall the solution installer and remove all of the files from the solution installer directory.

Select New Configuration, and click OK.

From the Mandatory Software List pane, drag a Node object onto the Configuration Editor pane.

If you are installing IBM Predictive Maintenance and Quality on four nodes, you must drag four Node objects onto the Configuration Editor pane.

A visual representation of an empty node is displayed.

In the Property Editor pane, select the node object, and enter the following information.

Enter a name for the node in Name, and press the Enter key. For example, enter BI node.

Enter the server name in Host Name, and press the Enter key.

Important: Unless you are using a single node configuration, ensure that the host names or IP addresses are for different computers. Do not use the same computer for more than one Node object.

Enter the user who has access to install the components in User Name, and press the Enter key. For example, enter root or a user with sudo permissions.

Enter the user's password in User Password, and press the Enter key.

Repeat these steps for each node object that you add. If you are installing IBM Predictive Maintenance and Quality on four nodes, you must repeat these steps for each of the four node objects.

Important: You must enter any mandatory information for nodes and other objects as indicated. Ensure that you review all of the properties to ensure that the values, both mandatory and optional, are valid.

Ensure that you press the Enter key after you type a value for a property.

From the Mandatory Software List pane, create your environment by dragging each object onto the appropriate node in the Configuration Editor pane.

Tip: Valid drop zones are indicated in the Configuration Editor pane.

Some restrictions are built into the placement of the objects. For example, if you are adding IBM Cognos BI Server to a node, then you must already have WebSphere Application Server on that node, and the IBM Cognos BI Server object must be placed within the WebSphere Application Server object.

Tip: Example environments are provided in the predefined configurations that are included with the installation files. For more information, see Using a predefined configuration.

Note: If you add the IBM DB2 Data Server Runtime Client component to the same node as the IBM DB2 Enterprise Server component, the IBM DB2 Data Server Runtime Client component will not be installed.

After you add an object, select it, and modify any values in the Property Editor pane.

When you add WebSphere® Application Server to a node, you must provide the following information:

WebSphere Install Directory is the location where WebSphere Application Server is to be installed.

WebSphere Application Port is the port number that you want to use for WebSphere Application Server.

WAS Profile Admin User Name is the administrator user's user name for WebSphere Application Server.

WAS Profile Admin Password is the password for the administrator user.

Important: Ensure that you press the Enter key after you type a value for a property.

From the Optional Software List, drag the objects to the node on which you want the installation files copied. The optional software is not installed by the solution installer. You must install the software manually. The installation files are copied to the node you drag them to.

Unless you change the default path, the optional software installation files are copied to the /opt/IBM/OptSoftware directory on the node computer.

As you build your environment, click Validate to identify errors or incomplete information.

After all nodes are defined and each node is validated, click Run.

Important: After you click the Run button, do not close the browser window until the installation completes. If you close the browser, you cannot re-initiate the session.

However, the installation does proceed even with the browser closed. But you cannot monitor the progress.

If the browser window closes, do the following steps:

Do nothing until enough time elapses to allow the installation to complete. Allow the installation at least 2 hours to complete.

Open a new browser window, and open the solution installer again.

Re-create the configuration that you used or open the saved session that you used. You must ensure that all of the values that you entered in the fields are the same as the configuration that you used when the browser window closed.

Rerun the installation. The solution installer verifies that all of the components are installed.

After the solution installer completes, verify that the components are working. For more information, see Test the installation.

Tip: If you click Validate before all the mandatory content is added, a message indicates that the node is not valid. For example, if you validate the BI Node before you add the IBM DB2 Data Server Runtime Client component, then a message indicates that the node is not yet valid.

Configuration properties for the server components
You must provide some configuration properties for each of the mandatory software components.

Saving and opening configurations
You can save IBM Predictive Maintenance and Quality configurations and open existing configurations in the solution installer.

Parent topic: Install the Predictive Maintenance and Quality servers

Configuration properties for the server componentsYou must provide some configuration properties for each of the mandatory software components. If you select any components from the Optional Software List, you must provide a deployment location for the installation files. You must manually install any item that you select from the Optional Software List.IBM DB2 Enterprise Server properties DB2 Server Install DirectoryThe location where IBM DB2 is to be installed on the data node computer.Default: /opt/ibm/db2/V10.5DB2 Database Port NumberThe port number that is used by IBM DB2.Default: 50000DB2 Server Admin User NameThe user ID that runs the administration server.Default: dasusr1This user must not exist on the computer.DB2 Server Admin PasswordThe password for the user ID that runs the administration server.The password cannot contain more than 8 characters and it must be lowercase.DB2 Server Admin Home DirectoryThe home directory for the user ID that runs the administration server. This directory is on the data node computer's file system.Default: /home/dasusr1DB2 Instance Owner User NameThe user ID that controls the DB2 processes and owns the directories that are used by the database instance.Default: db2inst1This user must not exist on the computer.DB2 Instance Owner PasswordThe password for the DB2 instance owner user.The password cannot contain more than 8 characters and it must be lowercase.DB2 Instance Owner Home DirectoryThe home directory for the DB2 instance owner user. This directory is on the data node computer's file system.Default: /home/db2inst1DB2 Fenced User NameThe user ID that can run user-defined functions and store procedures.Default: db2fenc1This user must not exist on the computer.DB2 Fenced User PasswordThe password for the DB2 fenced user.The password cannot contain more than 8 characters and it must be lowercase.DB2 Fenced User Home DirectoryThe home directory for the DB2 fenced user.Default: /home/db2fenc1Database: SPSS properties SPSS Database NameThe SPSS database that is used by the components that are installed on the Predictive Analytics node computer.This component must be contained within IBM DB2 Enterprise Server.Default: SPSSDBDatabase: BI Content Manager properties Content Manager Database NameThe IBM Cognos content store database.This component must be contained within IBM DB2 Enterprise Server.Default: COG102CSIBM DB2 Data Server Runtime Client properties The IBM DB2 Data Server Runtime Client component must be installed on each node, except for the data node computer. If you are doing a multi node deployment, make sure all of the values in the IBM DB2 Data Server Runtime Client are the same on all the nodes. If you add the IBM DB2 Data Server Runtime Client component to the same node as the IBM DB2 Enterprise Server component, the IBM DB2 Data Server Runtime Client component will not be installed. DB2 RTC Install DirectoryThe location where the IBM DB2 client is to be installed.Default: /opt/ibm/db2/V10.5DB2 RTC Instance User NameThe user ID for the DB2 client.Default: db2inst1This user must not exist on the computer.DB2 RTC Instance PasswordThe password for the DB2 client instance owner user.DB2 Client Instance Home DirectoryThe home directory for the DB2 client instance owner user.Default: /home/db2inst1WebSphere Application Server properties WebSphere Application Server must be installed on the nodes where you install IBM Cognos Business Intelligence and IBM SPSS Collaboration and Deployment Services Server. WebSphere Install DirectoryThe location where the WebSphere Application Server is to be installed.Default: /opt/IBM/WebSphere/AppServerWebSphere Application PortThe HTTP port number that is used by the WebSphere Application Server profile.Default: 9080WAS Profile Admin User NameThe administrative user name for the WebSphere Application Server profile.WAS Profile Admin PasswordThe password for the administrative user.IBM HTTP Server properties IBM HTTP Server must be installed on the computer where you install IBM Cognos Business Intelligence. HTTP Server Install DirectoryThe location where IBM HTTP Server is to be installed.Default: /opt/IBM/HTTPServerHTTP Server Port Number The port number that is used by HTTP Server.Default: 81IBM Cognos BI Server IBM Cognos BI Server must be contained within WebSphere Application Server in the Configuration Editor. IBM Cognos BI Server Install DirectoryThe location where IBM Cognos BI is to be installed.Default: /opt/ibm/cognos/c10_64IBM SPSS Modeler Server properties SPSS Modeler Server Install DirectoryThe location where IBM SPSS Modeler Server is to be installed.Default: /opt/IBM/SPSS/ModelerServer/17.0IBM SPSS Statistics Server properties SPSS Statistics Server Install DirectoryThe location where IBM SPSS Statistics Server is to be installed.Default: /opt/IBM/SPSS/StatisticsServer23IBM SPSS Data Access Pack properties SPSS Data Access Pack Install DirectoryThe location where IBM SPSS Data Access Pack is to be installed.Default: /root/SDAP711IBM SPSS C&DS Server (including ADM) properties IBM SPSS C&DS Server (including ADM) must be contained within WebSphere Application Server in the Configuration Editor. SPSS C&DS Server Install DirectoryThe location where IBM SPSS Collaboration and Deployment Services Server and Analytic Decision Management are to be installed.Default: /opt/IBM/SPSS/Deployment/7.0/ServerSPSS C&DS Server Admin User NameThe IBM SPSS Collaboration and Deployment Services administrative user.Default: adminSPSS C&DS Server Admin PasswordThe password for the IBM SPSS Collaboration and Deployment Services administrative user.Default: adminWebSphere MQ properties WebSphere MQ Home DirectoryThe WebSphere MQ home directory.Default: /homeChange the home directory only if the home directory location in the useradd file on the Linux System has been modified. WebSphere MQ Account User NameThe WebSphere MQ user.Default: mqmuser WebSphere MQ Account PasswordThe WebSphere MQ user account password.IBM Integration Bus properties IBM Integration Bus must be contained within WebSphere MQ in the Configuration Editor. Integration Bus Install DirectoryThe location where IBM Integration Bus is to be installed.Default: /opt/IBMODBC Data Extender Install DirectoryIBM Integration Bus ODBC Data Extender install location.Default: /opt/IBM/IE01/2.0.1Integration Bus Explorer Install DirectoryIBM Integration Bus Explorer install location.Default: /opt/IBM/IBExplorerIBM Analytical Foundation properties In the Configuration Editor, IBM Analytical Foundation must be inside the WebSphere MQ component. Analytical Foundation Shared Classes DirectoryIBM Analytical Foundation install location.Default: /var/mqsi/shared-classesIBM Integration Bus Manufacturing Pack properties In the Configuration Editor, IBM Integration Bus Manufacturing Pack must be inside the WebSphere MQ component. Destination DirectoryIBM Integration Bus Manufacturing Pack files location.Default: /opt/IBM/IIBManufactPack/IBM Master Data Management properties In the Configuration Editor, IBM Master Data Management must be inside the WebSphere Application Server component. MDM Install DirectoryIBM Master Data Management Server install location.Default: opt/IBM/MDMPerl Installation DirectoryUse the system perl directory.Default: MDM Application Server NameThe Master Data Management Application Server name used in WebSphere Application Server.Default: mdmsvrMDM WAS SOAP Port Number The Master Data Management Application Server SOAP port number.Default: 8880For a single node topology, use port number 8882. If IBM Master Data Management Server is installed on a WebSphere Application Server with multiple web applications, ensure you use the correct port number. Using the solution installerYou use the solution installer to define your IBM Predictive Maintenance and Quality environment you want to install.

Configuration properties for the server components

You must provide some configuration properties for each of the mandatory software components.

If you select any components from the Optional Software List, you must provide a deployment location for the installation files. You must manually install any item that you select from the Optional Software List.

IBM DB2 Enterprise Server properties

DB2 Server Install Directory

The location where IBM® DB2® is to be installed on the data node computer.

Default: /opt/ibm/db2/V10.5

DB2 Database Port Number

The port number that is used by IBM DB2.

Default: 50000

DB2 Server Admin User Name

The user ID that runs the administration server.

Default: dasusr1

This user must not exist on the computer.

DB2 Server Admin Password

The password for the user ID that runs the administration server.

The password cannot contain more than 8 characters and it must be lowercase.

DB2 Server Admin Home Directory

The home directory for the user ID that runs the administration server. This directory is on the data node computer's file system.

Default: /home/dasusr1

DB2 Instance Owner User Name

The user ID that controls the DB2 processes and owns the directories that are used by the database instance.

Default: db2inst1

This user must not exist on the computer.

DB2 Instance Owner Password

The password for the DB2 instance owner user.

The password cannot contain more than 8 characters and it must be lowercase.

DB2 Instance Owner Home Directory

The home directory for the DB2 instance owner user. This directory is on the data node computer's file system.

Default: /home/db2inst1

DB2 Fenced User Name

The user ID that can run user-defined functions and store procedures.

Default: db2fenc1

This user must not exist on the computer.

DB2 Fenced User Password

The password for the DB2 fenced user.

The password cannot contain more than 8 characters and it must be lowercase.

DB2 Fenced User Home Directory

The home directory for the DB2 fenced user.

Default: /home/db2fenc1

Database: SPSS properties

SPSS Database Name

The SPSS® database that is used by the components that are installed on the Predictive Analytics node computer.

This component must be contained within IBM DB2 Enterprise Server.

Default: SPSSDB

Database: BI Content Manager properties

Content Manager Database Name

The IBM Cognos® content store database.

This component must be contained within IBM DB2 Enterprise Server.

Default: COG102CS

IBM DB2 Data Server Runtime Client properties

The IBM DB2 Data Server Runtime Client component must be installed on each node, except for the data node computer.

If you are doing a multi node deployment, make sure all of the values in the IBM DB2 Data Server Runtime Client are the same on all the nodes.

Note: If you add the IBM DB2 Data Server Runtime Client component to the same node as the IBM DB2 Enterprise Server component, the IBM DB2 Data Server Runtime Client component will not be installed.

DB2 RTC Install Directory

The location where the IBM DB2 client is to be installed.

Default: /opt/ibm/db2/V10.5

DB2 RTC Instance User Name

The user ID for the DB2 client.

Default: db2inst1

This user must not exist on the computer.

DB2 RTC Instance Password

The password for the DB2 client instance owner user.

DB2 Client Instance Home Directory

The home directory for the DB2 client instance owner user.

Default: /home/db2inst1

WebSphere Application Server properties

WebSphere Application Server must be installed on the nodes where you install IBM Cognos Business Intelligence and IBM SPSS Collaboration and Deployment Services Server.

WebSphere Install Directory

The location where the WebSphere® Application Server is to be installed.

Default: /opt/IBM/WebSphere/AppServer

WebSphere Application Port

The HTTP port number that is used by the WebSphere Application Server profile.

Default: 9080

WAS Profile Admin User Name

The administrative user name for the WebSphere Application Server profile.

WAS Profile Admin Password

The password for the administrative user.

IBM HTTP Server properties

IBM HTTP Server must be installed on the computer where you install IBM Cognos Business Intelligence.

HTTP Server Install Directory

The location where IBM HTTP Server is to be installed.

Default: /opt/IBM/HTTPServer

HTTP Server Port Number

The port number that is used by HTTP Server.

Default: 81

IBM Cognos BI Server

IBM Cognos BI Server must be contained within WebSphere Application Server in the Configuration Editor.

IBM Cognos BI Server Install Directory

The location where IBM Cognos BI is to be installed.

Default: /opt/ibm/cognos/c10_64

IBM SPSS Modeler Server properties

SPSS Modeler Server Install Directory

The location where IBM SPSS Modeler Server is to be installed.

Default: /opt/IBM/SPSS/ModelerServer/17.0

IBM SPSS Statistics Server properties

SPSS Statistics Server Install Directory

The location where IBM SPSS Statistics Server is to be installed.

Default: /opt/IBM/SPSS/StatisticsServer23

IBM SPSS Data Access Pack properties

SPSS Data Access Pack Install Directory

The location where IBM SPSS Data Access Pack is to be installed.

Default: /root/SDAP711

IBM SPSS C&DS Server (including ADM) properties

IBM SPSS C&DS Server (including ADM) must be contained within WebSphere Application Server in the Configuration Editor.

SPSS C&DS Server Install Directory

The location where IBM SPSS Collaboration and Deployment Services Server and Analytic Decision Management are to be installed.

Default: /opt/IBM/SPSS/Deployment/7.0/Server

SPSS C&DS Server Admin User Name

The IBM SPSS Collaboration and Deployment Services administrative user.

Default: admin

SPSS C&DS Server Admin Password

The password for the IBM SPSS Collaboration and Deployment Services administrative user.

Default: admin

WebSphere MQ properties

WebSphere MQ Home Directory

The WebSphere MQ home directory.

Default: /home

Change the home directory only if the home directory location in the useradd file on the Linux System has been modified.

WebSphere MQ Account User Name

The WebSphere MQ user.

Default: mqmuser

WebSphere MQ Account Password

The WebSphere MQ user account password.

IBM Integration Bus properties

IBM Integration Bus must be contained within WebSphere MQ in the Configuration Editor.

Integration Bus Install Directory

The location where IBM Integration Bus is to be installed.

Default: /opt/IBM

ODBC Data Extender Install Directory

IBM Integration Bus ODBC Data Extender install location.

Default: /opt/IBM/IE01/2.0.1

Integration Bus Explorer Install Directory

IBM Integration Bus Explorer install location.

Default: /opt/IBM/IBExplorer

IBM Analytical Foundation properties

In the Configuration Editor, IBM Analytical Foundation must be inside the WebSphere MQ component.

Analytical Foundation Shared Classes Directory

IBM Analytical Foundation install location.

Default: /var/mqsi/shared-classes

IBM Integration Bus Manufacturing Pack properties

In the Configuration Editor, IBM Integration Bus Manufacturing Pack must be inside the WebSphere MQ component.

Destination Directory

IBM Integration Bus Manufacturing Pack files location.

Default: /opt/IBM/IIBManufactPack/

IBM Master Data Management properties

In the Configuration Editor, IBM Master Data Management must be inside the WebSphere Application Server component.

MDM Install Directory

IBM Master Data Management Server install location.

Default: opt/IBM/MDM

Perl Installation Directory

Use the system perl directory.

Default:

MDM Application Server Name

The Master Data Management Application Server name used in WebSphere Application Server.

Default: mdmsvr

MDM WAS SOAP Port Number

The Master Data Management Application Server SOAP port number.

Default: 8880

For a single node topology, use port number 8882. If IBM Master Data Management Server is installed on a WebSphere Application Server with multiple web applications, ensure you use the correct port number.

Parent topic: Using the solution installer

Saving and opening configurationsYou can save IBM Predictive Maintenance and Quality configurations and open existing configurations in the solution installer.To save a configuration:In the solution installer, define your configuration.Enter a name in the Save Configuration box, and click the Save Configuration icon Save Configuration icon.To open a saved configuration:Click Open, and browse to the saved configuration file, and click Open.Using the solution installerYou use the solution installer to define your IBM Predictive Maintenance and Quality environment you want to install.

Saving and opening configurations

You can save IBM® Predictive Maintenance and Quality configurations and open existing configurations in the solution installer.

Procedure

To save a configuration:

In the solution installer, define your configuration.

Enter a name in the Save Configuration box, and click the Save Configuration icon Save Configuration icon.

To open a saved configuration:

Click Open, and browse to the saved configuration file, and click Open.

Parent topic: Using the solution installer

Using a predefined configurationThe solution installer contains predefined configurations for the most common IBM Predictive Maintenance and Quality environments. Use these predefined configurations to simplify your deployment work.The following predefined configurations are available:PMQ Single Node ConfigurationAll of the IBM Predictive Maintenance and Quality components are installed on a single computer with IBM DB2 Enterprise Server. A single-node configuration is intended for a demonstration or testing environment. It should not be used for a production environment. A single node configuration contains the following components: PMQ Three Node for OracleAn IBM Predictive Maintenance and Quality environment on three nodes: a Business Intelligence node, an Analytics node, an Integration Bus node, all connected to an existing Oracle database. A three node configuration for Oracle contains the following components: PMQ Four Node ConfigurationA typical IBM Predictive Maintenance and Quality environment on four nodes: a data node with IBM DB2 Enterprise Server, a Business Intelligence node, an Analytics node, and an Integration Bus node. A four node configuration contains the following components: PMQ Five Node ConfigurationAn environment on five nodes, where IBM SPSS Collaboration and Deployment Services is installed on its own node rather than on the Analytics node computer as in the PMQ 4 Node Configuration. A five node configuration contains the following components: Open the solution installer in a web browser.After the solution installer is running, you can access the URL from any computer from a Firefox or Chrome web browser. The URL is https://servername:8080/UI/index.html, where servername is the name of the computer where you ran the solution installer. Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer. Ensure that you are using an English language web browser to access the solution installer URL.Select Predefined Configurations, and click OK.Select the configuration that you want to install, and click OK.The configuration is displayed in the Configuration Editor pane. Icons appear on each component where configuration information is required. For example, where you must provide user names or passwords. Image shows required configuration properties. Ensure that you change the server names to an actual server in your environment. Default values are provided.To add Master Data Management to a three node configuration, perform the following additional steps:Drag a Master Data Management component onto the BI Node, inside the WebSphere Application Server container. Drag a Master Data Management Database component onto the IBM DB2 Enterprise Server container.Change the MDM SOAP port number property to 8881.Ensure all of the properties are valid for your environment for each of the components and the nodes in the configuration.Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution.

Using a predefined configuration

The solution installer contains predefined configurations for the most common IBM® Predictive Maintenance and Quality environments. Use these predefined configurations to simplify your deployment work.

About this task

The following predefined configurations are available:

PMQ Single Node Configuration

All of the IBM Predictive Maintenance and Quality components are installed on a single computer with IBM DB2 Enterprise Server.

Note: A single-node configuration is intended for a demonstration or testing environment. It should not be used for a production environment.

A single node configuration contains the following components:

PMQ Three Node for Oracle

An IBM Predictive Maintenance and Quality environment on three nodes: a Business Intelligence node, an Analytics node, an Integration Bus node, all connected to an existing Oracle database.

A three node configuration for Oracle contains the following components:

PMQ Four Node Configuration

A typical IBM Predictive Maintenance and Quality environment on four nodes: a data node with IBM DB2 Enterprise Server, a Business Intelligence node, an Analytics node, and an Integration Bus node.

A four node configuration contains the following components:

PMQ Five Node Configuration

An environment on five nodes, where IBM SPSS Collaboration and Deployment Services is installed on its own node rather than on the Analytics node computer as in the PMQ 4 Node Configuration.

A five node configuration contains the following components:

Procedure

Open the solution installer in a web browser.

After the solution installer is running, you can access the URL from any computer from a Firefox or Chrome web browser.

The URL is https://servername:8080/UI/index.html, where servername is the name of the computer where you ran the solution installer.

Important: Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer.

Ensure that you are using an English language web browser to access the solution installer URL.

Select Predefined Configurations, and click OK.

Select the configuration that you want to install, and click OK.

The configuration is displayed in the Configuration Editor pane.

Icons appear on each component where configuration information is required. For example, where you must provide user names or passwords.

Important: Ensure that you change the server names to an actual server in your environment. Default values are provided.

To add Master Data Management to a three node configuration, perform the following additional steps:

Drag a Master Data Management component onto the BI Node, inside the WebSphere Application Server container.

Drag a Master Data Management Database component onto the IBM DB2 Enterprise Server container.

Change the MDM SOAP port number property to 8881.

Ensure all of the properties are valid for your environment for each of the components and the nodes in the configuration.

Parent topic: Install the Predictive Maintenance and Quality servers

Starting the installationThe solution installer installs the component products on each node computer. Before you start the installation, you can validate the configuration.In the solution installer, open the configuration that you want to install.Click Validate.If errors or messages about missing information are displayed, you must correct the error or provide the information before you can run the installation.Click Run.Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution.

Starting the installation

The solution installer installs the component products on each node computer. Before you start the installation, you can validate the configuration.

Procedure

In the solution installer, open the configuration that you want to install.

Click Validate. If errors or messages about missing information are displayed, you must correct the error or provide the information before you can run the installation.

Click Run.

Parent topic: Install the Predictive Maintenance and Quality servers

Computer firewall settings to run the server componentsEach IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.For information about IBM SPSS Modeler port numbers, see How many ports are utilized when a Modeler Client connects to Modeler Server? (www.ibm.com/support/docview.wss?uid=swg21488421).Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution. Configuring firewall settings for a single server installationOn the computer on which you install the IBM Predictive Maintenance and Quality nodes, you must open specific ports.Configuring firewall settings for the Analytics node computerYou must ensure that certain ports are open on the Predictive Analytics node computer for IBM Predictive Maintenance and Quality.Configuring firewall settings for the BI node computerYou must ensure that certain ports are open on the Business Intelligence (BI) node computer for IBM Predictive Maintenance and Quality.Configuring firewall settings for the Integration Bus node computerYou must ensure that certain ports are open on the Integration Bus node computer for IBM Predictive Maintenance and Quality.Configuring firewall settings for the data node computerYou must ensure that certain ports are open on the IBM Predictive Maintenance and Quality data node computer.Configuring firewall settings for the MDM node computerYou must ensure that certain ports are open on the Master Data Management (MDM) node computer for IBM Predictive Maintenance and Quality.

Computer firewall settings to run the server components

Each IBM® Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.

For information about IBM SPSS Modeler port numbers, see How many ports are utilized when a Modeler Client connects to Modeler Server? (www.ibm.com/support/docview.wss?uid=swg21488421).

Configuring firewall settings for a single server installation
On the computer on which you install the IBM Predictive Maintenance and Quality nodes, you must open specific ports.

Configuring firewall settings for the Analytics node computer
You must ensure that certain ports are open on the Predictive Analytics node computer for IBM Predictive Maintenance and Quality.

Configuring firewall settings for the BI node computer
You must ensure that certain ports are open on the Business Intelligence (BI) node computer for IBM Predictive Maintenance and Quality.

Configuring firewall settings for the Integration Bus node computer
You must ensure that certain ports are open on the Integration Bus node computer for IBM Predictive Maintenance and Quality.

Configuring firewall settings for the data node computer
You must ensure that certain ports are open on the IBM Predictive Maintenance and Quality data node computer.

Configuring firewall settings for the MDM node computer
You must ensure that certain ports are open on the Master Data Management (MDM) node computer for IBM Predictive Maintenance and Quality.

Parent topic: Install the Predictive Maintenance and Quality servers

Configuring firewall settings for a single server installationOn the computer on which you install the IBM Predictive Maintenance and Quality nodes, you must open specific ports.Log on to the computer as the root user or as a user with sudo permissions.Back up the existing firewall settings by typing the following command:/etc/init.d/iptables saveAdd rules for the ports with the following commands:iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 45088 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 58313 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 28054 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 3022 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport tungsten-https -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport glrpc -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport corbaloc -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 59356 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9043 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9044 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9060 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9061 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9080 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9081 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9362 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport vrace -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9663 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport http -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport <http_port> -j ACCEPTiptables -I where <http_port> is the HTTP Server Port Number. The default is 81. INPUT -m state --state NEW -m tcp -p tcp --dport boks -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_clntd -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_servm -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_servc -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport ibm-mqseries -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport ibm-db2 -j ACCEPTiptables -I INPUT -m state --state NEW -m tcp -p tcp --dport db2c_db2inst1 -j ACCEPTType the following command to save the firewall settings:/etc/init.d/iptables saveType the following command to restart the firewall./etc/init.d/iptables restartVerify that your changes have been applied with the following command:iptables -LThe ports appear in the list.Computer firewall settings to run the server componentsEach IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.

Configuring firewall settings for a single server installation

On the computer on which you install the IBM® Predictive Maintenance and Quality nodes, you must open specific ports.

Procedure

Log on to the computer as the root user or as a user with sudo permissions.

Back up the existing firewall settings by typing the following command:

/etc/init.d/iptables save

Add rules for the ports with the following commands:

iptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 45088 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 58313 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 28054 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 3022 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport tungsten-https -j
      ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport glrpc -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport corbaloc -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 59356 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 9043 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 9044 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 9060 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 9061 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 9080 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 9081 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 9362 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport vrace -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport 9663 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport http -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport <http_port> -j ACCEPTiptables -I
where <http_port> is the HTTP Server Port Number. The default is 81.
        INPUT -m state --state NEW -m tcp -p tcp --dport boks -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport boks_clntd -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport boks_servm -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport boks_servc -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport ibm-mqseries -j
      ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport ibm-db2 -j ACCEPTiptables -I
        INPUT -m state --state NEW -m tcp -p tcp --dport db2c_db2inst1 -j
      ACCEPT

Type the following command to save the firewall settings:

/etc/init.d/iptables save

Type the following command to restart the firewall.

/etc/init.d/iptables restart

Verify that your changes have been applied with the following command:

iptables -L

The ports appear in the list.

Parent topic: Computer firewall settings to run the server components

Configuring firewall settings for the Analytics node computerYou must ensure that certain ports are open on the Predictive Analytics node computer for IBM Predictive Maintenance and Quality.The following ports must be open:4508858313280543022tungsten-httpsglrpccorbaloc59356904390609080Log in to the Analytics node computer as the root user or as a user with sudo permissions.Back up the existing firewall settings by typing the following command:/etc/init.d/iptables saveAdd rules for the ports with the following commands:iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 45088 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 58313 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 28054 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 3022 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport tungsten-https -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport glrpc -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport corbaloc -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 59356 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9043 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9060 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9080 -j ACCEPTType the following command to save the firewall settings:/etc/init.d/iptables saveType the following command to restart the firewall./etc/init.d/iptables restartVerify that your changes have been applied with the following command:iptables -LThe ports appear in the list.Computer firewall settings to run the server componentsEach IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.

Configuring firewall settings for the Analytics node computer

You must ensure that certain ports are open on the Predictive Analytics node computer for IBM® Predictive Maintenance and Quality.

The following ports must be open:

45088

58313

28054

3022

tungsten-https

glrpc

corbaloc

59356

9043

9060

9080

Procedure

Log in to the Analytics node computer as the root user or as a user with sudo permissions.

Back up the existing firewall settings by typing the following command:

/etc/init.d/iptables save

Add rules for the ports with the following commands:

iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 45088 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 58313 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 28054 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 3022 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport tungsten-https -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport glrpc -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport corbaloc -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 59356 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9043 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9060 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9080 -j ACCEPT

Type the following command to save the firewall settings:

/etc/init.d/iptables save

Type the following command to restart the firewall.

/etc/init.d/iptables restart

Verify that your changes have been applied with the following command:

iptables -L

The ports appear in the list.

Parent topic: Computer firewall settings to run the server components

Configuring firewall settings for the BI node computerYou must ensure that certain ports are open on the Business Intelligence (BI) node computer for IBM Predictive Maintenance and Quality.The following ports must be open:9362vrace9663corbaloc9043glrpchttptungsten-https90609080Log in to the BI node computer as the root user or as a user with sudo permissions.Back up the existing firewall settings by typing the following command:/etc/init.d/iptables saveAdd rules for the ports with the following commands:iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9362 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport vrace -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9663 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport corbaloc -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9043 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport glrpc -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport http -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport tungsten-https -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9060 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9080 -j ACCEPTType the following command to save the firewall settings:/etc/init.d/iptables saveType the following command to restart the firewall./etc/init.d/iptables restartVerify that your changes have been applied with the following command:iptables -LThe ports appear in the list.Computer firewall settings to run the server componentsEach IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.

Configuring firewall settings for the BI node computer

You must ensure that certain ports are open on the Business Intelligence (BI) node computer for IBM® Predictive Maintenance and Quality.

The following ports must be open:

9362

vrace

9663

corbaloc

9043

glrpc

http

tungsten-https

9060

9080

Procedure

Log in to the BI node computer as the root user or as a user with sudo permissions.

Back up the existing firewall settings by typing the following command:

/etc/init.d/iptables save

Add rules for the ports with the following commands:

iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9362 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport vrace -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9663 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport corbaloc -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9043 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport glrpc -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport http -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport tungsten-https -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9060 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9080 -j ACCEPT

Type the following command to save the firewall settings:

/etc/init.d/iptables save

Type the following command to restart the firewall.

/etc/init.d/iptables restart

Verify that your changes have been applied with the following command:

iptables -L

The ports appear in the list.

Parent topic: Computer firewall settings to run the server components

Configuring firewall settings for the Integration Bus node computerYou must ensure that certain ports are open on the Integration Bus node computer for IBM Predictive Maintenance and Quality.The following ports must be open:boksboks_clntdboks_servmboks_servcibm-mqseriesLog in to the Integration Bus node computer as the root user or as a user with sudo permissions.Back up the existing firewall settings by typing the following command:/etc/init.d/iptables saveAdd rules for the ports with the following commands:iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_clntd -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_servm -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_servc -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport ibm-mqseries -j ACCEPTType the following command to save your firewall settings:/etc/init.d/iptables saveType the following command to restart your firewall./etc/init.d/iptables restartVerify that your changes have been applied with the following command:iptables -LThe ports appear in the list.Computer firewall settings to run the server componentsEach IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.

Configuring firewall settings for the Integration Bus node computer

You must ensure that certain ports are open on the Integration Bus node computer for IBM® Predictive Maintenance and Quality.

The following ports must be open:

boks

boks_clntd

boks_servm

boks_servc

ibm-mqseries

Procedure

Log in to the Integration Bus node computer as the root user or as a user with sudo permissions.

Back up the existing firewall settings by typing the following command:

/etc/init.d/iptables save

Add rules for the ports with the following commands:

iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_clntd -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_servm -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport boks_servc -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport ibm-mqseries -j ACCEPT

Type the following command to save your firewall settings:

/etc/init.d/iptables save

Type the following command to restart your firewall.

/etc/init.d/iptables restart

Verify that your changes have been applied with the following command:

iptables -L

The ports appear in the list.

Parent topic: Computer firewall settings to run the server components

Configuring firewall settings for the data node computerYou must ensure that certain ports are open on the IBM Predictive Maintenance and Quality data node computer.The following ports must be open: ibm-db2db2c_db2inst150001Log in to the data node computer as the root user or as a user with sudo permissions.Back up the existing firewall settings by typing the following command:/etc/init.d/iptables saveAdd rules for the port with the following commands:iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport ibm-db2 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport db2c_db2inst1 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 50001 -j ACCEPTType the following command to save the firewall settings:/etc/init.d/iptables saveType the following command to restart the firewall./etc/init.d/iptables restartVerify that your changes have been applied with the following command:iptables -LThe ports appear in the list.Computer firewall settings to run the server componentsEach IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.

Configuring firewall settings for the data node computer

You must ensure that certain ports are open on the IBM® Predictive Maintenance and Quality data node computer.

About this task

The following ports must be open:

ibm-db2

db2c_db2inst1

50001

Procedure

Log in to the data node computer as the root user or as a user with sudo permissions.

Back up the existing firewall settings by typing the following command:

/etc/init.d/iptables save

Add rules for the port with the following commands:

iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport ibm-db2 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport db2c_db2inst1 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 50001 -j ACCEPT

Type the following command to save the firewall settings:

/etc/init.d/iptables save

Type the following command to restart the firewall.

/etc/init.d/iptables restart

Verify that your changes have been applied with the following command:

iptables -L

The ports appear in the list.

Parent topic: Computer firewall settings to run the server components

Configuring firewall settings for the MDM node computerYou must ensure that certain ports are open on the Master Data Management (MDM) node computer for IBM Predictive Maintenance and Quality.The following ports must be open:tungsten-https504989634963357537498885334341950605734342040187netstewardcorbalocglrpc44152438303918890437507492988881cddbp-alt407525051235086bacula-dirjetdirect5505232970commplex-link372539060Log in to the MDM node computer as the root user or as a user with sudo permissions.Back up the existing firewall settings by typing the following command:/etc/init.d/iptables saveAdd rules for the ports with the following commands:iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport tungsten-https -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 50498 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9634 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9633 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 57537 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 49888 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 53343 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 41950 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 60573 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 43420 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 40187 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport netsteward -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport corbaloc -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport glrpc -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 44152 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 43830 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 39188 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9043 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 7507 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 49298 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 8881 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport cddbp-alt -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 40752 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 50512 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 35086 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport bacula-dir -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport jetdirect -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 55052 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 32970 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport commplex-link -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 37253 -j ACCEPT iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9060 -j ACCEPTType the following command to save the firewall settings:/etc/init.d/iptables saveType the following command to restart the firewall./etc/init.d/iptables restartVerify that your changes have been applied with the following command:iptables -LThe ports appear in the list.Computer firewall settings to run the server componentsEach IBM Predictive Maintenance and Quality node computer requires certain ports to be opened for the server components to operate in a multi-computer solution, and you must configure your firewall settings for each specific node.

Configuring firewall settings for the MDM node computer

You must ensure that certain ports are open on the Master Data Management (MDM) node computer for IBM® Predictive Maintenance and Quality.

The following ports must be open:

tungsten-https

50498

9634

9633

57537

49888

53343

41950

60573

43420

40187

netsteward

corbaloc

glrpc

44152

43830

39188

9043

7507

49298

8881

cddbp-alt

40752

50512

35086

bacula-dir

jetdirect

55052

32970

commplex-link

37253

9060

Procedure

Log in to the MDM node computer as the root user or as a user with sudo permissions.

Back up the existing firewall settings by typing the following command:

/etc/init.d/iptables save

Add rules for the ports with the following commands:

iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport tungsten-https -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 50498 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9634 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9633 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 57537 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 49888 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 53343 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 41950 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 60573 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 43420 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 40187 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport netsteward -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport corbaloc -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport glrpc -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 44152 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 43830 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 39188 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9043 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 7507 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 49298 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 8881 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport cddbp-alt -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 40752 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 50512 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 35086 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport bacula-dir -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport jetdirect -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 55052 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 32970 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport commplex-link -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 37253 -j ACCEPT
iptables -I INPUT -m state --state NEW -m tcp -p tcp --dport 9060 -j ACCEPT

Type the following command to save the firewall settings:

/etc/init.d/iptables save

Type the following command to restart the firewall.

/etc/init.d/iptables restart

Verify that your changes have been applied with the following command:

iptables -L

The ports appear in the list.

Parent topic: Computer firewall settings to run the server components

Updating the .bashrc file on the MDM node computerIf you installed a Master Data Management (MDM) node with your IBM Predictive Maintenance and Quality environment, you must update the .bashrc file on the MDM node computer. Log on to the MDM node computer as the root user.Open the .bashrc file in a text editor.For example, enter vi ~/.bashrc in a terminal window.Go to the line that starts with export PATH=.Add the following text to the end of that line::$PATHSave and close the file.Source the file by entering the following command: . ~/.bashrcInstall the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution.

Updating the .bashrc file on the MDM node computer

If you installed a Master Data Management (MDM) node with your IBM® Predictive Maintenance and Quality environment, you must update the .bashrc file on the MDM node computer.

Procedure

Log on to the MDM node computer as the root user.

Open the .bashrc file in a text editor. For example, enter vi ~/.bashrc in a terminal window.

Go to the line that starts with export PATH=.

Add the following text to the end of that line:

:$PATH

Save and close the file.

Source the file by entering the following command: . ~/.bashrc

Parent topic: Install the Predictive Maintenance and Quality servers

Test the installationAfter the installation of the IBM Predictive Maintenance and Quality server components is complete, you must perform some additional configuration tasks and then test the installation.Install the Predictive Maintenance and Quality serversYou use the solution installer to deploy the component programs on the servers that make up the solution. Testing the database installation and configurationYou can test the database installation and configuration by logging in to the IBM Predictive Maintenance and Quality data node computer and listing the databases on the server. You can also list the databases available on each node computer where the IBM DB2 client was installed.Testing Cognos Business IntelligenceVerify that you can access the IBM Business Intelligence portal.

Test the installation

After the installation of the IBM® Predictive Maintenance and Quality server components is complete, you must perform some additional configuration tasks and then test the installation.

Testing the database installation and configuration
You can test the database installation and configuration by logging in to the IBM Predictive Maintenance and Quality data node computer and listing the databases on the server. You can also list the databases available on each node computer where the IBM DB2® client was installed.

Testing Cognos Business Intelligence
Verify that you can access the IBM Business Intelligence portal.

Parent topic: Install the Predictive Maintenance and Quality servers

Testing the database installation and configurationYou can test the database installation and configuration by logging in to the IBM Predictive Maintenance and Quality data node computer and listing the databases on the server. You can also list the databases available on each node computer where the IBM DB2 client was installed.Log on to the data node computer.Open a terminal window, and change to the database instance owner user.For example, su - db2inst1.Enter the following command to list the databases on the computer:db2 list database directoryThe following databases are listed:COG102CSSPSSDBMDMDB (optional)Test the installationAfter the installation of the IBM Predictive Maintenance and Quality server components is complete, you must perform some additional configuration tasks and then test the installation.

Testing the database installation and configuration

You can test the database installation and configuration by logging in to the IBM® Predictive Maintenance and Quality data node computer and listing the databases on the server. You can also list the databases available on each node computer where the IBM DB2® client was installed.

Procedure

Log on to the data node computer.

Open a terminal window, and change to the database instance owner user. For example, su - db2inst1.

Enter the following command to list the databases on the computer:

db2 list database directory

The following databases are listed:

COG102CS

SPSSDB

MDMDB (optional)

Parent topic: Test the installation

Testing Cognos Business IntelligenceVerify that you can access the IBM Business Intelligence portal. Make sure the IBM Predictive Maintenance and Quality solution services are running.Open a web browser and enter the following URL: http://servername:81/ibmcognos/ where servername is the name of IP address of the computer where the Predictive Maintenance and Quality server components are installed.If you changed the default port number to 80 for IBM HTTP Server, you can exclude the port number from the URL.Test the installationAfter the installation of the IBM Predictive Maintenance and Quality server components is complete, you must perform some additional configuration tasks and then test the installation.

Testing Cognos Business Intelligence

Verify that you can access the IBM® Business Intelligence portal.

Before you begin

Make sure the IBM Predictive Maintenance and Quality solution services are running.

Procedure

Open a web browser and enter the following URL: http://servername:81/ibmcognos/ where servername is the name of IP address of the computer where the Predictive Maintenance and Quality server components are installed.

If you changed the default port number to 80 for IBM HTTP Server, you can exclude the port number from the URL.

Parent topic: Test the installation

Install the Predictive Maintenance and Quality server artifactsThis topic has been updated for 2.5.2.The server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.Before you can install the server artifacts, you must uninstall the solution installer that you used to install the servers. You must do the following things on the computer that currently contains the solution installer: Uninstall the solution installerInstall system files that are required for the artifact solution installerInstall the artifact solution installerUse the artifact solution installer to install and configure Predictive Maintenance and Quality artifactsFinish configuring the server componentsUninstalling the server solution installer Before you can install the IBM Predictive Maintenance and Quality server artifacts, you must uninstall the server solution installer and then install the artifact solution installer.Installing and starting the artifact solution installerUse the artifact solution installer to install the artifacts on the IBM Predictive Maintenance and Quality servers. You access the artifact solution installer interface from another computer by using a web browser. Configuring parameters for the artifact installationUse the solution installer to select and configure the artifacts in your solution. Complete the configuration of the server componentsAfter you have installed the IBM Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.Configuring the Analytics nodeYou must install and configure IBM SPSS Collaboration and Deployment Services Deployment Manager on the Analytics node.Updating database credentials and changing table namesIf you specified a user ID other than the default for the IBM Cognos content store database, then you must update the credentials for the jobs in Deployment Manager. Exporting solution and orchestration definitionsUse the export utility PMQExportUtility to export the solution and orchestration XML files to the Foundation Web UI application.

Install the Predictive Maintenance and Quality server artifacts

The server artifacts include report content and workflows for IBM® Predictive Maintenance and Quality.

Before you can install the server artifacts, you must uninstall the solution installer that you used to install the servers.

You must do the following things on the computer that currently contains the solution installer:

Uninstall the solution installer

Install system files that are required for the artifact solution installer

Install the artifact solution installer

Use the artifact solution installer to install and configure Predictive Maintenance and Quality artifacts

Finish configuring the server components

Uninstalling the server solution installer
Before you can install the IBM Predictive Maintenance and Quality server artifacts, you must uninstall the server solution installer and then install the artifact solution installer.

Installing and starting the artifact solution installer
Use the artifact solution installer to install the artifacts on the IBM Predictive Maintenance and Quality servers. You access the artifact solution installer interface from another computer by using a web browser.

Configuring parameters for the artifact installation
Use the solution installer to select and configure the artifacts in your solution.

Complete the configuration of the server components
After you have installed the IBM Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.

Configuring the Analytics node
You must install and configure IBM SPSS® Collaboration and Deployment Services Deployment Manager on the Analytics node.

Updating database credentials and changing table names
If you specified a user ID other than the default for the IBM Cognos content store database, then you must update the credentials for the jobs in Deployment Manager.

Exporting solution and orchestration definitions
Use the export utility PMQExportUtility to export the solution and orchestration XML files to the Foundation Web UI application.

Uninstalling the server solution installerThis is a variation of the same topic that's in PCI 1.1. Copied and modified it for PMQ 2.5.2. This topic also resolves defect 27518. Before you can install the IBM Predictive Maintenance and Quality server artifacts, you must uninstall the server solution installer and then install the artifact solution installer. When you uninstall the server solution installer, the processes that are used by the solution installer are stopped and removed from your computer. All of the files in the solution installer directory are also removed. This includes the IBM Predictive Maintenance and Quality server component and server artifact installation files that you copied into the solution installer directory. If you want to save those files, you must copy them to another directory before you uninstall the solution installer. Also, you can run a script on each node computer where you installed an IBM Predictive Maintenance and Quality component to remove the server solution installer processes. Ensure that you copy the cleanupClient.sh file before you uninstall the server solution installer. Uninstalling the server solution installer does not uninstall the IBM Predictive Maintenance and Quality component applications. If you want to uninstall those components, you must use each component's uninstallation programs.To remove the server solution installer processes on the client node computers, do the following steps on each client node computer:From the installation computer, copy the PMQ_2.5.2_linux/SolutionInstaller/cleanupClient.sh file onto each computer on which you installed an IBM Predictive Maintenance and Quality component.On the client node computer, go to the directory where you copied the cleanupClient.sh file.Enter the following command: sh cleanupClient.sh.To remove the server solution installer from the installation computer, do the following steps:Go to the PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Software directory.Enter the following command: sh cleanup.sh.Restart the installation computer. Start the Predictive Maintenance and Quality services. For information about how to start the services see, Start solution servicesYou must start the IBM Predictive Maintenance and Quality node services in a specific order..Install the artifact solution installer. Install the Predictive Maintenance and Quality server artifactsThe server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.

Uninstalling the server solution installer

Before you can install the IBM® Predictive Maintenance and Quality server artifacts, you must uninstall the server solution installer and then install the artifact solution installer.

When you uninstall the server solution installer, the processes that are used by the solution installer are stopped and removed from your computer. All of the files in the solution installer directory are also removed. This includes the IBM Predictive Maintenance and Quality server component and server artifact installation files that you copied into the solution installer directory. If you want to save those files, you must copy them to another directory before you uninstall the solution installer.

Also, you can run a script on each node computer where you installed an IBM Predictive Maintenance and Quality component to remove the server solution installer processes. Ensure that you copy the cleanupClient.sh file before you uninstall the server solution installer.

Note: Uninstalling the server solution installer does not uninstall the IBM Predictive Maintenance and Quality component applications. If you want to uninstall those components, you must use each component's uninstallation programs.

Procedure

To remove the server solution installer processes on the client node computers, do the following steps on each client node computer:

From the installation computer, copy the PMQ_2.5.2_linux/SolutionInstaller/cleanupClient.sh file onto each computer on which you installed an IBM Predictive Maintenance and Quality component.

On the client node computer, go to the directory where you copied the cleanupClient.sh file.

Enter the following command: sh cleanupClient.sh.

To remove the server solution installer from the installation computer, do the following steps:

Go to the PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Software directory.

Enter the following command: sh cleanup.sh.

Restart the installation computer.

Start the Predictive Maintenance and Quality services. For information about how to start the services see, Start solution services.

What to do next

Install the artifact solution installer.

Parent topic: Install the Predictive Maintenance and Quality server artifacts

Installing and starting the artifact solution installerUse the artifact solution installer to install the artifacts on the IBM Predictive Maintenance and Quality servers. You access the artifact solution installer interface from another computer by using a web browser. You must have access to a computer that is separate from the computer that contains the installation files. This computer has the following requirements: Has a monitor with a screen resolution that is greater than 1024 by 760.The operating system uses English. Has Google Chrome 47, or later, or Mozilla Firefox 38 or later installed on it. The language of the installed web browser language must be English. You must know the location of the pm_q_artfcts_2.5.2_l86-64_en.tar.gz file that you downloaded from Passport Advantage in Downloading and decompressing the installation filesYou must download the IBM Predictive Maintenance and Quality solution from IBM Passport Advantage, and then decompress the files to run the solution installer.. The pm_q_artfcts_2.5.2_l86-64_en.tar.gz file must be in a directory for which you have execute permissions. Log on to the computer as the root user or as a user with sudo permissions.Go to the directory that contains pm_q_artfcts_2.5.2_l86-64_en.tar.gz and decompress it by typing the following command: tar xvf filesname.tar.gzIf you are the root user, enter the following command: sh setup.sh. If you are a user with sudo permissions, enter the following command: sudo sh setup.sh.After the artifact solution installer starts, open a web browser on another computer, and go to the solution installer URL: https://servername:8080/UI/index.html. Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer.Install the Predictive Maintenance and Quality server artifactsThe server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.

Installing and starting the artifact solution installer

Use the artifact solution installer to install the artifacts on the IBM® Predictive Maintenance and Quality servers. You access the artifact solution installer interface from another computer by using a web browser.

Before you begin

You must have access to a computer that is separate from the computer that contains the installation files. This computer has the following requirements:

Has a monitor with a screen resolution that is greater than 1024 by 760.

The operating system uses English.

Has Google Chrome 47, or later, or Mozilla Firefox 38 or later installed on it. The language of the installed web browser language must be English.

You must know the location of the pm_q_artfcts_2.5.2_l86-64_en.tar.gz file that you downloaded from Passport Advantage® in Downloading and decompressing the installation files.

The pm_q_artfcts_2.5.2_l86-64_en.tar.gz file must be in a directory for which you have execute permissions.

Procedure

Log on to the computer as the root user or as a user with sudo permissions.

Go to the directory that contains pm_q_artfcts_2.5.2_l86-64_en.tar.gz and decompress it by typing the following command:

tar xvf filesname.tar.gz

If you are the root user, enter the following command: sh setup.sh. If you are a user with sudo permissions, enter the following command: sudo sh setup.sh.

After the artifact solution installer starts, open a web browser on another computer, and go to the solution installer URL: https://servername:8080/UI/index.html.

Important: Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer.

Parent topic: Install the Predictive Maintenance and Quality server artifacts

Configuring parameters for the artifact installationUpdated with content provided by Sunil. Word doc called PMQ_2_5_2_Server_Artifacts. Use the solution installer to select and configure the artifacts in your solution. Use the information in the following tables to configure parameters for the artifacts. The Property Editor displays some default values for each component. You can accept the default values or change them to suit your environment. Parameters for IBM DB2FieldDefault or example valueDescriptionData Deployment Location/opt/IBM/PMQ/DataThe location where the server artifacts are to be copied on the data node computer.DB2 Instance Home/home/db2inst1The home directory of the database instance owner.DB Database Instance User Namedb2inst1The user ID for the IBM Cognos content store database.DB Database Instance PasswordThis field does not have a default value. The password for the database instance owner user. Integration bus parameters for IBM DB2FieldDefault or example valueDescriptionInstall location of IIB/opt/IBM/IIBThe location where IBM Integration Bus is installed. This directory is on the Integration Bus node computer's file system.DB2 Client install Location/opt/ibm/db2/v10.5The IP address of the Analytics nodecomputer.Analytics Node IPThere is no default for this field.The IP address of the Predictive Analytics node computer.Analytics Node HTTP Transport Port9080The WebSphere Application Server port number that is used on the Analytics node computer.DB2 Port Number50000The port number that is used by the IBM DB2 server on the data node computer.Database Node IPThere is no default for this field. The IP address of the data node computer.DB2 UsernameDb2inst1The user ID that controls the database processes and owns the directories that are used by the database instance.Message Queue Usernamemqmuser User ID created by installing the message queue.DB2 Database Server Instance PasswordThere is no default for this field. Password of DB2 Username. Business Intelligence parameters for IBM DB2FieldDefault or example valueDescriptionBusiness Intelligence Deployment Location/opt/IBM/PMQ/Business_IntelligenceThe location where the server artifacts are to be installed on the BI node computer.Cognos Install Location/opt/ibm/cognos/c10_64The location where IBM Cognos BI is installed. This directory is on the BI node computer's file system.WebSphere Install Location/opt/IBM/WebSphere/AppServerThe location where WebSphere is installed. This directory is on the BI node computer's file system.DB2 Instance Home Directory/home/db2inst1The home directory of the database instance owner.DB2 Client Install Location/opt/ibm/db2/v10.5The location where the DB2 client is installed on the BI node computer.Cognos BI Dispatcher URIhttp://localhost:9080/p2pd/servlet/dispatchThe URL to the IBM Cognos BI dispatcher, where bi_node_name is the name or IP address of the BI node computer.DB2 Instance User Namedb2inst1The user ID for the IBM Cognos content store database. DB2 Instance PasswordThere is no default value for this field.Password for the database instance owner user. DB2 Database Port Number50000The port number for the DB2 server.Database Node IPThere is no default value for this field.The IP address of the Analytics node computer.Integration Bus Node IPThere is no default value for this field.The IP address of the Integration Bus node computer.WebSphere Application Server PMQUI Profile Administrative UsernameadminThe administrative user name for the WebSphere Application Server profile that is used for the dashboard application.WebSphere Application Server PMQUI Profile Administrative PasswordThere is no default value for this field.The password for the administrative user for the WebSphere Application Server profile that is used for the dashboard application.WebSphere Application Server Cognos Profile Administrative UsernameadminThe administrative user name for the WebSphere Application Server profile that is used for IBM Cognos Business Intelligence.WebSphere Application Server Cognos Profile Administrative PasswordThere is no default value for this field.The password for the administrative user for the WebSphere Application Server profile that is used for IBM Cognos Business Intelligence.Business Intelligence Node IPThere is no default value for this field.The IP address of the Business Intelligence node. Analytics parameters for IBM DB2FieldDefault or example valueDescriptionAnalytics Deployment Location/opt/IBM/PMQ/AnalyticsThe location where the server artifacts are to be installed on the Analytics node computer.SPSS Modeler Server Install Location/opt/IBM/SPSS/ModelerServer/17.0The location where the Modeler Server is installed.SPSS Data Pack Installation Location/root/SDAP71The directory where the IBM SPSS Data Access Pack is installed. This directory is on the Analytics node computer.SPSS CNDS Install Location/opt/IBM/SPSS/Deployment/7.0/ServerThe location where IBM SPSS Collaboration and Deployment Services is installed. This location is on the Analytics node computer.Integration Bus Node IPThere is no default value for this field.The IP address of the Integration Bus node computer.Database Node IPThere is no default value for this field.The IP address of the data node computer.Database Usernamedb2inst1The user ID for the IBM Cognos content store database.Database PasswordThere is no default value for this field.The password for the database instance owner user.Database Port50000The port number for the database server. Parameters for Master Data ManagementFieldDefault or example valueDescriptionMaster Data Deployment Location/opt/IBM/PMQ/Master_DataThe location where the server artifacts are to be copied on the Master Data Management (MDM) node computer. Oracle Database parameters FieldDefault or example valueDescriptionData Deployment Location/opt/IBM/PMQ/DataThe location where the server artifacts are to be installed on the data node computer.Oracle Install Location/home/oracle/app/oracle/product/12.1.0/dbhome_1The user ID that controls the database processes and owns the directories that are used by the database instance.Oracle Installed User Account Home Directory/home/oracleThe password for the database instance owner user. Ensure that you use the same password that you provided during the server installation.Oracle Port1521The port number used to install Oracle.Enter the Oracle Login DB UsernameOracleOracle installed username.Enter Sys PasswordThere is no default value for this field.Sys password used when you installed Oracle.Enter System PasswordThere is no default value for this field.Current system password.pmqsch user passwordDefault user ID for accessing the IBMPMQ database. Oracle Installed HostnameThere is no default value for this field.Host name of the computer that has Oracle installed. Integration bus parameters for Oracle DatabaseFieldDefault or example valueDescriptionInstall Location of IIB/opt/ibm/mqsi/9.0.0.2The location where IBM Integration Bus is installed. This directory is on the Integration Bus node computer's file system.Message Queue UsernamemqmuserUser ID created by installing the message queue.Analytics Node IPThere is no default for this field. The IP address of the Analytics nodecomputer.Analytics Node HTTP Transport Port9080The WebSphere Application Server port number that is used on the Analytics node computer.Database Port Number1521The port number for the Oracle Database server.Database Node IPThere is no default for this field. The IP address of the data node computer.Database UsernamepmqschThe user ID that controls the database processes and owns the directories that are used by the database instance.Database PasswordThere is no default for this field. The user ID that controls the database processes and owns the directories that are used by the database instance. Business Intelligence parameters for Oracle DatabaseFieldDefault or example valueDescriptionBusiness Intelligence Deployment LocationSunil: is there a dateandtime on the directory name?/opt/IBM/PMQ/BIdateandtimeThe location where the server artifacts are to be installed on the BI node computer. The artifacts are deployed to the location in a directory with a date and time stamp.Cognos Install Location/opt/ibm/cognos/c10_64The location where IBM Cognos BI is installed. This directory is on the BI node computer's file system.WebSphere Install Location/opt/IBM/WebSphere/AppServerThe location where WebSphere is installed. This directory is on the BI node computer's file system.Oracle Client Install Location/home/oracle/app/oracle/product/12.1.0/client_1The location where the Oracle Database client is installed on the BI node computer.Cognos BI Dispatcher URIhttp://localhost:9080/p2pd/servlet/dispatchThe URL to the IBM Cognos BI dispatcher, where bi_node_name is the name or IP address of the BI node computer. Database User NamepmqschThe user ID for the IBM Cognos content store database. Database PasswordThere is no default value for this field.The password for the database instance owner user. Database Port Number1521The port number for the Oracle Database server.Database Node IPThere is no default value for this field.The IP address of the Analytics node computer.Integration Bus Node IPThere is no default value for this field.The IP address of the Integration Bus node computer.WebSphere Application Server PMQUI Profile Administrative UsernameadminThe administrative user name for the WebSphere Application Server profile that is used for the dashboard application.WebSphere Application Server PMQUI Profile Administrative PasswordThere is no default value for this field.The password for the administrative user for the WebSphere Application Server profile that is used for the dashboard application.WebSphere Application Server Cognos Profile Administrative UsernameadminThe administrative user name for the WebSphere Application Server profile that is used for IBM Cognos Business Intelligence.WebSphere Application Server Cognos Profile Administrative PasswordThere is no default value for this field.The password for the administrative user for the WebSphere Application Server profile that is used for IBM Cognos Business Intelligence.Business Intelligence Node IPThere is no default value for this field.The IP address of the Business Intelligence node. Analytics parameters for Oracle DatabaseFieldDefault or example valueDescriptionAnalytics Deployment Location/opt/IBM/PMQ/AnalyticsThe location where the server artifacts are to be installed on the Analytics node computer.SPSS Modeler Server Install Location/opt/IBM/SPSS/ModelerServer/17.0The location where the Modeler Server is installed.SPSS Data Pack Installation Location/root/SDAP711The directory where the IBM SPSS Data Access Pack is installed. This directory is on the Analytics node computer.SPSS CNDS Install Location/opt/IBM/SPSS/Deployment/7.0/ServerThe location where IBM SPSS Collaboration and Deployment Services is installed. This location is on the Analytics node computer.Integration Bus Node IPThere is no default value for this field.The IP address of the Integration Bus node computer.Database Node IPThere is no default value for this field.The IP address of the data node computer.Database UsernamepmqschThe user ID for the IBM Cognos content store database.Database PasswordThere is no default value for this field.The password for the database instance owner user.Database Port Number1521The port number for the database server. Parameters for Master Data ManagementFieldDefault or example valueDescriptionMaster Data Deployment Location/opt/IBM/PMQ/Master_DataThe location where the server artifacts are to be copied on the Master Data Management (MDM) node computer.Open the solution installer in a web browser.After the solution installer is running, you can access the URL from any computer from a Firefox or Chrome web browser. The URL is https://servername:8080/UI/index.html, where servername is the name of the computer where you ran the solution installer. Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer. Ensure that you are using an English language web browser to access the solution installer URL.On the license information page, click Accept.Declining the license allows you to uninstall the solution installer and remove all of the files from the solution installer directory.Select New Configuration and click OK.From the Mandatory Software List pane, drag a Node object onto the Configuration Editor pane. A visual representation of an empty node is displayed.In the Property Editor pane, select the node object, and enter the following information.Enter a name for the node in Name, and press the Enter key.Enter the server name in Host Name, and press the Enter key.Unless you are using a single node configuration, ensure that the host names or IP addresses are for different computers. Do not use the same computer for more than one Node object.Enter the user who has access to install the components in User Name, and press the Enter key.For example, enter root or a user with sudo permissions.Enter the user's password in User Password, and press the Enter key.From the Optional Software List, drag an artifact on to the node.For the artifact, enter or verify the mandatory values in the Property Editor. Ensure that you review all of the properties to ensure that the values, both mandatory and optional, are valid. After you type a value for a property, press the Enter key. For the data node, select and configure either the IBM DB2 artifacts or the Oracle artifacts. After all nodes are defined click Run.After you click the Run button, do not close the browser window until the installation completes. If you close the browser, you cannot re-initiate the session.The installation continues even if you close the browser.If the browser window closes, do the following steps:Do nothing until enough time elapses to allow the installation to complete. Allow the installation at least 2 hours to complete.Open a new browser window, and open the solution installer again.Re-create the configuration that you used or open the saved session that you used. You must ensure that all of the values that you entered in the fields are the same as the configuration that you used when the browser window closed.Rerun the installation. The solution installer verifies that all of the components are installed.After the solution installer completes, verify that the components are working. For more information, see Test the installationAfter the installation of the IBM Predictive Maintenance and Quality server components is complete, you must perform some additional configuration tasks and then test the installation.. Do not use the Validate button when you are configuring artifacts. Install the Predictive Maintenance and Quality server artifactsThe server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.

Configuring parameters for the artifact installation

Use the solution installer to select and configure the artifacts in your solution.

About this task

Use the information in the following tables to configure parameters for the artifacts. The Property Editor displays some default values for each component. You can accept the default values or change them to suit your environment.

Table 2. Parameters for IBM DB2

Field
Default or example value
Description

Data Deployment Location

/opt/IBM/PMQ/Data

The location where the server artifacts are to be copied on the data node computer.

DB2 Instance Home

/home/db2inst1

The home directory of the database instance owner.

DB Database Instance User Name

db2inst1

The user ID for the IBM Cognos content store database.

DB Database Instance Password

This field does not have a default value.

The password for the database instance owner user.

Table 3. Integration bus parameters for IBM DB2

Field
Default or example value
Description

Install location of IIB

/opt/IBM/IIB

The location where IBM Integration Bus is installed. This directory is on the Integration Bus node computer's file system.

DB2 Client install Location

/opt/ibm/db2/v10.5

The IP address of the Analytics nodecomputer.

Analytics Node IP
There is no default for this field.
The IP address of the Predictive Analytics node computer.

Analytics Node HTTP Transport Port

9080

The WebSphere® Application Server port number that is used on the Analytics node computer.

DB2 Port Number
50000
The port number that is used by the IBM DB2 server on the data node computer.

Database Node IP

There is no default for this field.

The IP address of the data node computer.

DB2 Username

Db2inst1

The user ID that controls the database processes and owns the directories that are used by the database instance.

Message Queue Username

mqmuser

User ID created by installing the message queue.

DB2 Database Server Instance Password

There is no default for this field.

Password of DB2 Username.

Table 4. Business Intelligence parameters for IBM DB2

Field
Default or example value
Description

Business Intelligence Deployment Location

/opt/IBM/PMQ/Business_Intelligence

The location where the server artifacts are to be installed on the BI node computer.

Cognos Install Location

/opt/ibm/cognos/c10_64

The location where IBM® Cognos® BI is installed. This directory is on the BI node computer's file system.

WebSphere Install Location

/opt/IBM/WebSphere/AppServer

The location where WebSphere is installed. This directory is on the BI node computer's file system.

DB2 Instance Home Directory
/home/db2inst1
The home directory of the database instance owner.

DB2 Client Install Location

/opt/ibm/db2/v10.5

The location where the DB2 client is installed on the BI node computer.

Cognos BI Dispatcher URI

http://localhost:9080/p2pd/servlet/dispatch

The URL to the IBM Cognos BI dispatcher, where bi_node_name is the name or IP address of the BI node computer.

DB2 Instance User Name

db2inst1

The user ID for the IBM Cognos content store database.

DB2 Instance Password

There is no default value for this field.

Password for the database instance owner user.

DB2 Database Port Number

50000

The port number for the DB2 server.

Database Node IP

There is no default value for this field.

The IP address of the Analytics node computer.

Integration Bus Node IP

There is no default value for this field.

The IP address of the Integration Bus node computer.

WebSphere Application Server PMQUI Profile Administrative Username

admin

The administrative user name for the WebSphere Application Server profile that is used for the dashboard application.

WebSphere Application Server PMQUI Profile Administrative Password

There is no default value for this field.

The password for the administrative user for the WebSphere Application Server profile that is used for the dashboard application.

WebSphere Application Server Cognos Profile Administrative Username

admin

The administrative user name for the WebSphere Application Server profile that is used for IBM Cognos Business Intelligence.

WebSphere Application Server Cognos Profile Administrative Password

There is no default value for this field.

The password for the administrative user for the WebSphere Application Server profile that is used for IBM Cognos Business Intelligence.

Business Intelligence Node IP
There is no default value for this field.
The IP address of the Business Intelligence node.

Table 5. Analytics parameters for IBM DB2

Field
Default or example value
Description

Analytics Deployment Location

/opt/IBM/PMQ/Analytics

The location where the server artifacts are to be installed on the Analytics node computer.

SPSS Modeler Server Install Location

/opt/IBM/SPSS/ModelerServer/17.0

The location where the Modeler Server is installed.

SPSS Data Pack Installation Location

/root/SDAP71

The directory where the IBM SPSS Data Access Pack is installed. This directory is on the Analytics node computer.

SPSS CNDS Install Location

/opt/IBM/SPSS/Deployment/7.0/Server

The location where IBM SPSS® Collaboration and Deployment Services is installed. This location is on the Analytics node computer.

Integration Bus Node IP

There is no default value for this field.

The IP address of the Integration Bus node computer.

Database Node IP

There is no default value for this field.

The IP address of the data node computer.

Database Username

db2inst1

The user ID for the IBM Cognos content store database.

Database Password

There is no default value for this field.

The password for the database instance owner user.

Database Port

50000

The port number for the database server.

Table 6. Parameters for Master Data Management

Field
Default or example value
Description

Master Data Deployment Location

/opt/IBM/PMQ/Master_Data

The location where the server artifacts are to be copied on the Master Data Management (MDM) node computer.

Table 7. Oracle Database parameters

Field
Default or example value
Description

Data Deployment Location

/opt/IBM/PMQ/Data

The location where the server artifacts are to be installed on the data node computer.

Oracle Install Location

/home/oracle/app/oracle/product/12.1.0/dbhome_1

The user ID that controls the database processes and owns the directories that are used by the database instance.

Oracle Installed User Account Home Directory

/home/oracle

The password for the database instance owner user.

Note: Ensure that you use the same password that you provided during the server installation.

Oracle Port
1521
The port number used to install Oracle.

Enter the Oracle Login DB Username
Oracle
Oracle installed username.

Enter Sys Password
There is no default value for this field.
Sys password used when you installed Oracle.

Enter System Password
There is no default value for this field.
Current system password.

pmqsch user password

Default user ID for accessing the IBMPMQ database.

Oracle Installed Hostname
There is no default value for this field.
Host name of the computer that has Oracle installed.

Table 8. Integration bus parameters for Oracle Database

Field
Default or example value
Description

Install Location of IIB

/opt/ibm/mqsi/9.0.0.2

The location where IBM Integration Bus is installed. This directory is on the Integration Bus node computer's file system.

Message Queue Username

mqmuser

User ID created by installing the message queue.

Analytics Node IP

There is no default for this field.

The IP address of the Analytics nodecomputer.

Analytics Node HTTP Transport Port

9080

The WebSphere Application Server port number that is used on the Analytics node computer.

Database Port Number
1521
The port number for the Oracle Database server.

Database Node IP

There is no default for this field.

The IP address of the data node computer.

Database Username

pmqsch

The user ID that controls the database processes and owns the directories that are used by the database instance.

Database Password

There is no default for this field.

The user ID that controls the database processes and owns the directories that are used by the database instance.

Table 9. Business Intelligence parameters for Oracle Database

Field
Default or example value
Description

Business Intelligence Deployment Location

/opt/IBM/PMQ/BIdateandtime

The location where the server artifacts are to be installed on the BI node computer.

The artifacts are deployed to the location in a directory with a date and time stamp.

Cognos Install Location

/opt/ibm/cognos/c10_64

The location where IBM Cognos BI is installed. This directory is on the BI node computer's file system.

WebSphere Install Location

/opt/IBM/WebSphere/AppServer

The location where WebSphere is installed. This directory is on the BI node computer's file system.

Oracle Client Install Location

/home/oracle/app/oracle/product/12.1.0/client_1

The location where the Oracle Database client is installed on the BI node computer.

Cognos BI Dispatcher URI

http://localhost:9080/p2pd/servlet/dispatch

The URL to the IBM Cognos BI dispatcher, where bi_node_name is the name or IP address of the BI node computer.

Database User Name

pmqsch

The user ID for the IBM Cognos content store database.

Database Password

There is no default value for this field.

The password for the database instance owner user.

Database Port Number

1521

The port number for the Oracle Database server.

Database Node IP

There is no default value for this field.

The IP address of the Analytics node computer.

Integration Bus Node IP

There is no default value for this field.

The IP address of the Integration Bus node computer.

WebSphere Application Server PMQUI Profile Administrative Username

admin

The administrative user name for the WebSphere Application Server profile that is used for the dashboard application.

WebSphere Application Server PMQUI Profile Administrative Password

There is no default value for this field.

The password for the administrative user for the WebSphere Application Server profile that is used for the dashboard application.

WebSphere Application Server Cognos Profile Administrative Username

admin

The administrative user name for the WebSphere Application Server profile that is used for IBM Cognos Business Intelligence.

WebSphere Application Server Cognos Profile Administrative Password

There is no default value for this field.

The password for the administrative user for the WebSphere Application Server profile that is used for IBM Cognos Business Intelligence.

Business Intelligence Node IP

There is no default value for this field.

The IP address of the Business Intelligence node.

Table 10. Analytics parameters for Oracle Database

Field
Default or example value
Description

Analytics Deployment Location

/opt/IBM/PMQ/Analytics

The location where the server artifacts are to be installed on the Analytics node computer.

SPSS Modeler Server Install Location

/opt/IBM/SPSS/ModelerServer/17.0

The location where the Modeler Server is installed.

SPSS Data Pack Installation Location

/root/SDAP711

The directory where the IBM SPSS Data Access Pack is installed. This directory is on the Analytics node computer.

SPSS CNDS Install Location

/opt/IBM/SPSS/Deployment/7.0/Server

The location where IBM SPSS Collaboration and Deployment Services is installed. This location is on the Analytics node computer.

Integration Bus Node IP

There is no default value for this field.

The IP address of the Integration Bus node computer.

Database Node IP

There is no default value for this field.

The IP address of the data node computer.

Database Username

pmqsch

The user ID for the IBM Cognos content store database.

Database Password

There is no default value for this field.

The password for the database instance owner user.

Database Port Number

1521

The port number for the database server.

Table 11. Parameters for Master Data Management

Field
Default or example value
Description

Master Data Deployment Location

/opt/IBM/PMQ/Master_Data

The location where the server artifacts are to be copied on the Master Data Management (MDM) node computer.

Procedure

Open the solution installer in a web browser.

After the solution installer is running, you can access the URL from any computer from a Firefox or Chrome web browser.

The URL is https://servername:8080/UI/index.html, where servername is the name of the computer where you ran the solution installer.

Important: Do not use a web browser on the computer on which you are running the solution installer or any computer on which a Predictive Maintenance and Quality component is being installed. You must use a web browser on another computer.

Ensure that you are using an English language web browser to access the solution installer URL.

On the license information page, click Accept.

CAUTION:

Declining the license allows you to uninstall the solution installer and remove all of the files from the solution installer directory.

Select New Configuration and click OK.

From the Mandatory Software List pane, drag a Node object onto the Configuration Editor pane.

A visual representation of an empty node is displayed.

In the Property Editor pane, select the node object, and enter the following information.

Enter a name for the node in Name, and press the Enter key.

Enter the server name in Host Name, and press the Enter key.

Important: Unless you are using a single node configuration, ensure that the host names or IP addresses are for different computers. Do not use the same computer for more than one Node object.

Enter the user who has access to install the components in User Name, and press the Enter key. For example, enter root or a user with sudo permissions.

Enter the user's password in User Password, and press the Enter key.

From the Optional Software List, drag an artifact on to the node.

For the artifact, enter or verify the mandatory values in the Property Editor.

Important: Ensure that you review all of the properties to ensure that the values, both mandatory and optional, are valid.

After you type a value for a property, press the Enter key.

For the data node, select and configure either the IBM DB2 artifacts or the Oracle artifacts.

After all nodes are defined click Run.

Important: After you click the Run button, do not close the browser window until the installation completes. If you close the browser, you cannot re-initiate the session.

The installation continues even if you close the browser.

If the browser window closes, do the following steps:

Do nothing until enough time elapses to allow the installation to complete. Allow the installation at least 2 hours to complete.

Open a new browser window, and open the solution installer again.

Re-create the configuration that you used or open the saved session that you used. You must ensure that all of the values that you entered in the fields are the same as the configuration that you used when the browser window closed.

Rerun the installation. The solution installer verifies that all of the components are installed.

After the solution installer completes, verify that the components are working. For more information, see Test the installation.

Note: Do not use the Validate button when you are configuring artifacts.

Parent topic: Install the Predictive Maintenance and Quality server artifacts

Complete the configuration of the server componentsAfter you have installed the IBM Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.Install the Predictive Maintenance and Quality server artifactsThe server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.Verifying the configuration of IBM SPSS Collaboration and Deployment ServicesTo complete the configuration of IBM SPSS Collaboration and Deployment Services Server, you must verify the URL Prefix value for your environment.Configuring the MDM nodeTo configure the Master Data Management (MDM) node, you must log in to the MDM administration console and import content files.Configure the Integration Bus node componentsTo configure the Integration Bus node components, you must enable remote access for the queue manager.Enabling IBM Maximo Asset Management integrationTo enable IBM Maximo Asset Management integration with IBM Predictive Maintenance and Quality, you must manually modify configuration files and deploy the PMQMaximoIntegration.bar file.Starting the Predictive Maintenance and Quality dashboard applicationThe Predictive Maintenance and Quality dashboard application provides a single interface where users can access IBM Cognos Business Intelligence reports, access the IBM Analytics Solutions Foundation, and view live profile values for a particular resource.

Complete the configuration of the server components

After you have installed the IBM® Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.

Verifying the configuration of IBM SPSS Collaboration and Deployment Services
To complete the configuration of IBM SPSS® Collaboration and Deployment Services Server, you must verify the URL Prefix value for your environment.

Configuring the MDM node
To configure the Master Data Management (MDM) node, you must log in to the MDM administration console and import content files.

Configure the Integration Bus node components
To configure the Integration Bus node components, you must enable remote access for the queue manager.

Enabling IBM Maximo Asset Management integration
To enable IBM Maximo® Asset Management integration with IBM Predictive Maintenance and Quality, you must manually modify configuration files and deploy the PMQMaximoIntegration.bar file.

Starting the Predictive Maintenance and Quality dashboard application
The Predictive Maintenance and Quality dashboard application provides a single interface where users can access IBM Cognos® Business Intelligence reports, access the IBM Analytics Solutions Foundation, and view live profile values for a particular resource.

Parent topic: Install the Predictive Maintenance and Quality server artifacts

Verifying the configuration of IBM SPSS Collaboration and Deployment ServicesTo complete the configuration of IBM SPSS Collaboration and Deployment Services Server, you must verify the URL Prefix value for your environment.Open a web browser.In the address bar, type the address for the Collaboration and Deployment administration console.The address is http://analytics_node_name:9080/config, where analytics_node_name is the name or IP address for the Predictive Analytics node computer. If you are using a single node installation of Predictive Maintenance and Quality, the port number is 9082. For example, the address is http://analytics_node_name:9082/config.Enter the Login name and Password for the administrator user, and click Login.The default Login name is admin, and the default Password is admin.On the Configuration panel, under Setup, click URL Prefix.In the URL Prefix box, verify that the address is http://analytics_node_name:9080, where analytics_node_name is the name or IP address of the Analytics node computer.If the value is correct, you do not have to complete the remaining steps in this task.If the value is not correct, enter the name or IP address of the Analytics node computer, and click Set.Open the WebSphere Administrative Console in your web browser.The address is http://analytics_node_name:9060/ibm/console, where analytics_node_name is the name or IP address for the Analytics node computer. 9060 is the default port number for the WebSphere Administrative Console.Enter admin for both the User ID and Password, and click Log in.Under ApplicationsApplication TypesWebSphere Enterprise Applications, select IBM_SPSS_Collaboration_and_Deployment_Services_7.0, and click Stop.Select IBM_SPSS_Collaboration_and_Deployment_Services_7.0, and click Start to restart the application and apply the changes.Complete the configuration of the server componentsAfter you have installed the IBM Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.

Verifying the configuration of IBM SPSS Collaboration and Deployment Services

To complete the configuration of IBM® SPSS® Collaboration and Deployment Services Server, you must verify the URL Prefix value for your environment.

Procedure

Open a web browser.

In the address bar, type the address for the Collaboration and Deployment administration console.

The address is http://analytics_node_name:9080/config, where analytics_node_name is the name or IP address for the Predictive Analytics node computer.

Important: If you are using a single node installation of Predictive Maintenance and Quality, the port number is 9082. For example, the address is http://analytics_node_name:9082/config.

Enter the Login name and Password for the administrator user, and click Login.

The default Login name is admin, and the default Password is admin.

On the Configuration panel, under Setup, click URL Prefix.

In the URL Prefix box, verify that the address is http://analytics_node_name:9080, where analytics_node_name is the name or IP address of the Analytics node computer.

If the value is correct, you do not have to complete the remaining steps in this task.

If the value is not correct, enter the name or IP address of the Analytics node computer, and click Set.

Open the WebSphere® Administrative Console in your web browser.

The address is http://analytics_node_name:9060/ibm/console, where analytics_node_name is the name or IP address for the Analytics node computer. 9060 is the default port number for the WebSphere Administrative Console.

Enter admin for both the User ID and Password, and click Log in.

Under Applications > Application Types > WebSphere Enterprise Applications, select IBM_SPSS_Collaboration_and_Deployment_Services_7.0, and click Stop.

Select IBM_SPSS_Collaboration_and_Deployment_Services_7.0, and click Start to restart the application and apply the changes.

Parent topic: Complete the configuration of the server components

Configuring the MDM nodeTo configure the Master Data Management (MDM) node, you must log in to the MDM administration console and import content files.The content files are installed onto the MDM node computer by the Server Artifact installer. You must copy the content files from the MDM node to a computer where you have Microsoft Internet Explorer installed.Copy the MDM node contents to your Microsoft Windows-based computer with an FTP client or by using a shared directory.The contents files are installed to /opt/IBM/PMQ by default on the MDM node computer. The contents file is named IBMPMQ.zip.In Microsoft Internet Explorer, go to the MDM administration console.The address is http://mdm_node_name:7507/utils/enterLogin.jsp, where mdm_node_name is the name or IP address of the MDM node computer.In User name, enter Admin.These values are case-sensitive.In the Password box, enter trinitron.In the Company box, enter IBMPMQ.Click Login.Click System AdministratorImport Environment.In the Import Company Environment box, browse to and select the IBMPMQ.zip file that you copied.Click Import.Log out, and log back in to the MDM administration console to ensure that the import was completed.Complete the configuration of the server componentsAfter you have installed the IBM Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.

Configuring the MDM node

To configure the Master Data Management (MDM) node, you must log in to the MDM administration console and import content files.

The content files are installed onto the MDM node computer by the Server Artifact installer. You must copy the content files from the MDM node to a computer where you have Microsoft Internet Explorer installed.

Procedure

Copy the MDM node contents to your Microsoft Windows-based computer with an FTP client or by using a shared directory.

The contents files are installed to /opt/IBM/PMQ by default on the MDM node computer. The contents file is named IBMPMQ.zip.

In Microsoft Internet Explorer, go to the MDM administration console.

The address is http://mdm_node_name:7507/utils/enterLogin.jsp, where mdm_node_name is the name or IP address of the MDM node computer.

In User name, enter Admin.

Note: These values are case-sensitive.

In the Password box, enter trinitron.

In the Company box, enter IBMPMQ.

Click Login.

Click System Administrator > Import Environment.

In the Import Company Environment box, browse to and select the IBMPMQ.zip file that you copied.

Click Import.

Log out, and log back in to the MDM administration console to ensure that the import was completed.

Parent topic: Complete the configuration of the server components

Configure the Integration Bus node componentsTo configure the Integration Bus node components, you must enable remote access for the queue manager.Complete the configuration of the server componentsAfter you have installed the IBM Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.Enabling remote access for the queue managerFor IBM Predictive Maintenance and Quality, you must start the queue manager command line processor to enable remote access to the queue manager.

Configure the Integration Bus node components

To configure the Integration Bus node components, you must enable remote access for the queue manager.

Enabling remote access for the queue manager
For IBM Predictive Maintenance and Quality, you must start the queue manager command line processor to enable remote access to the queue manager.

Parent topic: Complete the configuration of the server components

Enabling remote access for the queue managerFor IBM Predictive Maintenance and Quality, you must start the queue manager command line processor to enable remote access to the queue manager.In a terminal window, go to the installation_location/mqsi/9.0.0.2/bin directory.For example, if you installed to the default location, go to the /opt/ibm/mqsi/9.0.0.2/bin directory.Change to the mqm user.For example, su mqm.Enter the following command to load the profile that is needed for the mqm user, and press Enter:. ~/.bash_profileAs the mqm user, enter the following command to start the queue manager:runmqsc queue_manager_nameFor example, to use the default queue manager named pmqmanager, enter:runmqsc pmqmanagerEnter the following lines, and press Enter after each line:START LISTENERALTER QMGR CHLAUTH(ENABLED)SET CHLAUTH(SYSTEM.BKR.CONFIG) TYPE(ADDRESSMAP) ADDRESS('*')  MCAUSER('mqm')SET CHLAUTH(SYSTEM.BKR.CONFIG) TYPE(BLOCKUSER) USERLIST('*NOACCESS')ENDThe ADDRESS('*') value in the command allows connections from any IP address. Consider restricting the access to a single computer. For more information about these values, see the WebSphere MQ documentation.Configure the Integration Bus node componentsTo configure the Integration Bus node components, you must enable remote access for the queue manager.

Enabling remote access for the queue manager

For IBM® Predictive Maintenance and Quality, you must start the queue manager command line processor to enable remote access to the queue manager.

Procedure

In a terminal window, go to the installation_location/mqsi/9.0.0.2/bin directory. For example, if you installed to the default location, go to the /opt/ibm/mqsi/9.0.0.2/bin directory.

Change to the mqm user. For example, su mqm.

Enter the following command to load the profile that is needed for the mqm user, and press Enter:

. ~/.bash_profile

As the mqm user, enter the following command to start the queue manager:

runmqsc queue_manager_name

For example, to use the default queue manager named pmqmanager, enter:

runmqsc pmqmanager

Enter the following lines, and press Enter after each line:

START LISTENER

ALTER QMGR CHLAUTH(ENABLED)

SET CHLAUTH(SYSTEM.BKR.CONFIG) TYPE(ADDRESSMAP) ADDRESS('*')  MCAUSER('mqm')

SET CHLAUTH(SYSTEM.BKR.CONFIG) TYPE(BLOCKUSER) USERLIST('*NOACCESS')

END

Important: The ADDRESS('*') value in the command allows connections from any IP address. Consider restricting the access to a single computer. For more information about these values, see the WebSphere® MQ documentation.

Parent topic: Configure the Integration Bus node components

Enabling IBM Maximo Asset Management integrationTo enable IBM Maximo Asset Management integration with IBM Predictive Maintenance and Quality, you must manually modify configuration files and deploy the PMQMaximoIntegration.bar file.Log on to the Integration Bus node computer as the mqm user.Go to the /var/mqsi/shared-classes/orchestrations directory.To enable IBM Maximo work order creation:Open PMQ_orchestration_definition_measurement.xml in a text editor.Uncomment the second service_invocation_configuration element in the service adapter section.Save and close the file.To enable IBM Maximo work order updating:Open PMQ_orchestration_definition_maintenance.xml in a text editor.Uncomment the last step element in the file.Save and close the file.Restart the pmqbroker.Go to the /opt/ibm/mqsi/9.0.0.2/bin directory.Enter the following command to stop the broker:./mqsistop pmqbrokerEnter the following command to restart the broker:./mqsistart pmqbrokerSet the URL for IBM Maximo.Go to the /var/PMQ/MQSIFileInput/properties directory.Open the PMQMaximoIntegration.properties file in a text editor.Enter the IP address of the IBM Maximo host computer in the webServiceURL.For example, change localhost to the IBM Maximo host IP address.Save and close the file.Update the PMQMaximoIntegration.bar file.Go to the /opt/ibm/mqsi/9.0.0.2/bin directory.Enter the following command:./mqsiapplybaroverride -b /var/PMQ/MQSIFileInput/server/PMQMaximoIntegration.bar -k PMQMaximoIntegration -p /var/PMQ/MQSIFileInput/properties/PMQMaximoIntegration.propertiesDeploy the PMQMaximoIntegration.bar file.Go to the /opt/ibm/mqsi/9.0.0.2/bin directory.Enter the following command:./mqsideploy pmqbroker -e pmqgroup1 -a /var/PMQ/MQSIFileInput/server/PMQMaximoIntegration.barComplete the configuration of the server componentsAfter you have installed the IBM Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.

Enabling IBM Maximo Asset Management integration

To enable IBM® Maximo® Asset Management integration with IBM Predictive Maintenance and Quality, you must manually modify configuration files and deploy the PMQMaximoIntegration.bar file.

Procedure

Log on to the Integration Bus node computer as the mqm user.

Go to the /var/mqsi/shared-classes/orchestrations directory.

To enable IBM Maximo work order creation:

Open PMQ_orchestration_definition_measurement.xml in a text editor.

Uncomment the second service_invocation_configuration element in the service adapter section.

Save and close the file.

To enable IBM Maximo work order updating:

Open PMQ_orchestration_definition_maintenance.xml in a text editor.

Uncomment the last step element in the file.

Save and close the file.

Restart the pmqbroker.

Go to the /opt/ibm/mqsi/9.0.0.2/bin directory.

Enter the following command to stop the broker:

./mqsistop pmqbroker

Enter the following command to restart the broker:

./mqsistart pmqbroker

Set the URL for IBM Maximo.

Go to the /var/PMQ/MQSIFileInput/properties directory.

Open the PMQMaximoIntegration.properties file in a text editor.

Enter the IP address of the IBM Maximo host computer in the webServiceURL. For example, change localhost to the IBM Maximo host IP address.

Save and close the file.

Update the PMQMaximoIntegration.bar file.

Go to the /opt/ibm/mqsi/9.0.0.2/bin directory.

Enter the following command:

./mqsiapplybaroverride -b /var/PMQ/MQSIFileInput/server/PMQMaximoIntegration.bar -k PMQMaximoIntegration -p /var/PMQ/MQSIFileInput/properties/PMQMaximoIntegration.properties

Deploy the PMQMaximoIntegration.bar file.

Go to the /opt/ibm/mqsi/9.0.0.2/bin directory.

Enter the following command:

./mqsideploy pmqbroker -e pmqgroup1 -a /var/PMQ/MQSIFileInput/server/PMQMaximoIntegration.bar

Parent topic: Complete the configuration of the server components

Starting the Predictive Maintenance and Quality dashboard applicationThe Predictive Maintenance and Quality dashboard application provides a single interface where users can access IBM Cognos Business Intelligence reports, access the IBM Analytics Solutions Foundation, and view live profile values for a particular resource.The Predictive Maintenance and Quality dashboard application contains the following tabs:DashboardCreate and manage dashboards.ReportsAccess the IBM Cognos Business Intelligence reports.FoundationConfigure Predictive Maintenance and Quality. This tab is visible to users in the Administrator group only. For the Predictive Maintenance and Quality dashboard application to work properly, master data must be loaded into Predictive Maintenance and Quality. For more information about master data, see the IBM Predictive Maintenance and Quality Solution Guide.Access the Predictive Maintenance and Quality dashboard application by typing the following URL:http://bi_node_name:port_number/PMQDashboard/pmqui bi_node_name is the name or IP address for the BI node computer. Complete the configuration of the server componentsAfter you have installed the IBM Predictive Maintenance and Quality server artifacts, you can complete the configuration of the server components.

Starting the Predictive Maintenance and Quality dashboard application

The Predictive Maintenance and Quality dashboard application provides a single interface where users can access IBM® Cognos® Business Intelligence reports, access the IBM Analytics Solutions Foundation, and view live profile values for a particular resource.

About this task

The Predictive Maintenance and Quality dashboard application contains the following tabs:

Dashboard

Create and manage dashboards.

Reports

Access the IBM Cognos Business Intelligence reports.

Foundation

Configure Predictive Maintenance and Quality. This tab is visible to users in the Administrator group only.

For the Predictive Maintenance and Quality dashboard application to work properly, master data must be loaded into Predictive Maintenance and Quality. For more information about master data, see the IBM Predictive Maintenance and Quality Solution Guide.

Procedure

Access the Predictive Maintenance and Quality dashboard application by typing the following URL:

http://bi_node_name:port_number/PMQDashboard/pmqui

bi_node_name is the name or IP address for the BI node computer.

Parent topic: Complete the configuration of the server components

Configuring the Analytics nodeYou must install and configure IBM SPSS Collaboration and Deployment Services Deployment Manager on the Analytics node.Install IBM SPSS Collaboration and Deployment Services Deployment Manager on the Predictive Analytics node.See Installing IBM SPSS Collaboration and Deployment Services Deployment ManagerYou must install IBM SPSS Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality..Add a content server connection. See Adding a content server connection for IBM SPSS Collaboration and Deployment ServicesYou must add a connection to your IBM SPSS Collaboration and Deployment Services repository in the IBM SPSS Collaboration and Deployment Services Deployment Manager client..Import the resource definitions. See Importing the resource definitions into IBM SPSS Collaboration and Deployment ServicesPredictive Maintenance and Quality resource definitions include credential definitions, data source definitions, message domains, promotion policies, server definitions, and server cluster specifications. These resources are required for running jobs..Add server and resource definitions. See Adding server and resource definitions to IBM SPSS Collaboration and Deployment ServicesYou must add server and resource definitions in Deployment Manager..Perform Updating database credentials and changing table namesIf you specified a user ID other than the default for the IBM Cognos content store database, then you must update the credentials for the jobs in Deployment Manager. Install the Predictive Maintenance and Quality server artifactsThe server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.

Configuring the Analytics node

You must install and configure IBM® SPSS® Collaboration and Deployment Services Deployment Manager on the Analytics node.

Procedure

Install IBM SPSS Collaboration and Deployment Services Deployment Manager on the Predictive Analytics node. See Installing IBM SPSS Collaboration and Deployment Services Deployment Manager.

Add a content server connection. See Adding a content server connection for IBM SPSS Collaboration and Deployment Services.

Import the resource definitions. See Importing the resource definitions into IBM SPSS Collaboration and Deployment Services.

Add server and resource definitions. See Adding server and resource definitions to IBM SPSS Collaboration and Deployment Services.

Perform Updating database credentials and changing table names

Parent topic: Install the Predictive Maintenance and Quality server artifacts

Updating database credentials and changing table namesIf you specified a user ID other than the default for the IBM Cognos content store database, then you must update the credentials for the jobs in Deployment Manager. Start Deployment Manager and select the Context Explorer tab.Expand the Content Repository folder. Right-click a job and select Open.Select a stream on the job and click the ODBC Data Sources tab.To change a database table name:Click an entry under ODBC DSN and click the ellipsis.Select either Use ODBC DSN or Create New ODBC.Change the table name or create a new one and then save the job.To update database credentials:Click an entry under Credentials and click the ellipsis.Select either Use Existing Credential or Create New Credential. Change the credentials or create a new one and then save the job.Install the Predictive Maintenance and Quality server artifactsThe server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.

Updating database credentials and changing table names

If you specified a user ID other than the default for the IBM Cognos content store database, then you must update the credentials for the jobs in Deployment Manager.

Procedure

Start Deployment Manager and select the Context Explorer tab.

Expand the Content Repository folder.

Right-click a job and select Open.

Select a stream on the job and click the ODBC Data Sources tab.

To change a database table name:

Click an entry under ODBC DSN and click the ellipsis.

Select either Use ODBC DSN or Create New ODBC.

Change the table name or create a new one and then save the job.

To update database credentials:

Click an entry under Credentials and click the ellipsis.

Select either Use Existing Credential or Create New Credential.

Change the credentials or create a new one and then save the job.

Parent topic: Install the Predictive Maintenance and Quality server artifacts

Exporting solution and orchestration definitionsUse the export utility PMQExportUtility to export the solution and orchestration XML files to the Foundation Web UI application. PMQExportUtility is at /opt/IBM/PMQ/BIdateandtimestamp/PMQExportUtility. Create a directory named /root/migrate_files on the BI node and put the solution XML files to be migrated into this directory. Create a directory named /root/migrate_files/orchestrations on the BI node and put the orchestration XML files to be migrated into this directory.Update the pmq_export.properties file to connect to the report database and IBM WebSphere Application Server.The following code shows examples for Oracle Database and IBM DB2. #-------------------------------------------# #Properties for data source #-------------------------------------------# #Example For Oracle: oracle.jdbc.OracleDriver #Example For DB2: com.ibm.db2.jcc.DB2Driverpmq_migration_jdbc_driver= com.ibm.db2.jcc.DB2Driver #Example For Oracle: <path>/ojdbc7.jar #Example For DB2: <path>/db2jcc4.jarpmq_migration_jdbc_driver_path= /opt/ibm/db2/V10.5/java/db2jcc4.jar #Example For Oracle: jdbc:oracle:thin:@<dbHost>:<dbPort>/<dbName> #Example For DB2: jdbc:db2://<dbHost>:<dbPort>/<dbName>:currentSchema=<dbCurentSchema>; pmq_migration_jdbc_url=jdbc:db2://9.120.120.120:50000/IBMPMQ:currentSchema=PMQSCH; pmq_migration_jdbc_username=db2inst1pmq_migration_jdbc_password=db2inst1 #-------------------------------------------# #Properties for WebSphere Application Server #-------------------------------------------# pmq_migration_was_root=/opt/IBM/WebSphere/AppServer pmq_migration_was_profile_name=PMQUIProfile pmq_migration_was_server_name=server1Run the following commands to migrate and export the foundation configuration content to the Foundation Web UI application.chmod 744 pmq_export.sh .pmq_export.shYou can access the foundation configuration files from http://host:port/PMQDashboard/pmqui.Install the Predictive Maintenance and Quality server artifactsThe server artifacts include report content and workflows for IBM Predictive Maintenance and Quality.

Exporting solution and orchestration definitions

Use the export utility PMQExportUtility to export the solution and orchestration XML files to the Foundation Web UI application.

About this task

PMQExportUtility is at /opt/IBM/PMQ/BIdateandtimestamp/PMQExportUtility.

Procedure

Create a directory named /root/migrate_files on the BI node and put the solution XML files to be migrated into this directory.

Create a directory named /root/migrate_files/orchestrations on the BI node and put the orchestration XML files to be migrated into this directory.

Update the pmq_export.properties file to connect to the report database and IBM® WebSphere® Application Server.

The following code shows examples for Oracle Database and IBM DB2®.

#-------------------------------------------#
#Properties for data source
#-------------------------------------------#
#Example For Oracle: oracle.jdbc.OracleDriver
#Example For DB2: com.ibm.db2.jcc.DB2Driverpmq_migration_jdbc_driver=
com.ibm.db2.jcc.DB2Driver
#Example For Oracle: <path>/ojdbc7.jar
#Example For DB2: <path>/db2jcc4.jarpmq_migration_jdbc_driver_path=
/opt/ibm/db2/V10.5/java/db2jcc4.jar
#Example For Oracle: jdbc:oracle:thin:@<dbHost>:<dbPort>/<dbName>
#Example For DB2:
jdbc:db2://<dbHost>:<dbPort>/<dbName>:currentSchema=<dbCurentSchema>;
pmq_migration_jdbc_url=jdbc:db2://9.120.120.120:50000/IBMPMQ:currentSchema=PMQSCH;
pmq_migration_jdbc_username=db2inst1pmq_migration_jdbc_password=db2inst1
#-------------------------------------------#
#Properties for WebSphere Application Server
#-------------------------------------------#
pmq_migration_was_root=/opt/IBM/WebSphere/AppServer
pmq_migration_was_profile_name=PMQUIProfile
pmq_migration_was_server_name=server1

Run the following commands to migrate and export the foundation configuration content to the Foundation Web UI application.

chmod 744 pmq_export.sh
.pmq_export.sh

Results

You can access the foundation configuration files from http://host:port/PMQDashboard/pmqui.

Parent topic: Install the Predictive Maintenance and Quality server artifacts

Artifact installation for a deployment that contains Oracle DatabaseFor an Oracle Database installation, you must configure IBM Predictive Maintenance and Quality to access the Oracle Database that contains your Predictive Maintenance and Quality data and reports.PrerequisitesBefore you install the artifacts to support Oracle Database, you must perform some tasks on the Predictive Maintenance and Quality nodes.Configuring Cognos Business IntelligenceYou must configure Cognos Business Intelligence on the BI node to point to your Oracle Database server.Configuring the PMQ UI serverYou must configure the PMQ UI to point to your Oracle Database.Configuring PMQExportUtilityYou must update pmq_export.properties so that you can use PMQExportUtility for Oracle Database.

Artifact installation for a deployment that contains Oracle Database

For an Oracle Database installation, you must configure IBM® Predictive Maintenance and Quality to access the Oracle Database that contains your Predictive Maintenance and Quality data and reports.

Prerequisites
Before you install the artifacts to support Oracle Database, you must perform some tasks on the Predictive Maintenance and Quality nodes.

Configuring Cognos Business Intelligence
You must configure Cognos® Business Intelligence on the BI node to point to your Oracle Database server.

Configuring the PMQ UI server
You must configure the PMQ UI to point to your Oracle Database.

Configuring PMQExportUtility
You must update pmq_export.properties so that you can use PMQExportUtility for Oracle Database.

PrerequisitesBefore you install the artifacts to support Oracle Database, you must perform some tasks on the Predictive Maintenance and Quality nodes.You must have Oracle Database 12c Release 1 (12.1.0.2.0) Enterprise Edition for Microsoft Windows (x64) installed and configured. Ensure that it is available in your network and that you can connect to it.Perform the following tasks on the Business Intelligence (BI) node:Install Oracle 12.1.0 32 bit client with an Installation Type of Runtime.Copy ojdbc6.jar and ojdbc7.jar files from oracle_home/jdbc/lib to cognos_home/webapps/p2pd/web-inf/lib.Artifact installation for a deployment that contains Oracle DatabaseFor an Oracle Database installation, you must configure IBM Predictive Maintenance and Quality to access the Oracle Database that contains your Predictive Maintenance and Quality data and reports.Installing the JDBC driverYou must install the Oracle JDBC driver on the Integration Bus node.

Prerequisites

Before you install the artifacts to support Oracle Database, you must perform some tasks on the Predictive Maintenance and Quality nodes.

You must have Oracle Database 12c Release 1 (12.1.0.2.0) Enterprise Edition for Microsoft Windows (x64) installed and configured. Ensure that it is available in your network and that you can connect to it.

Perform the following tasks on the Business Intelligence (BI) node:

Install Oracle 12.1.0 32 bit client with an Installation Type of Runtime.

Copy ojdbc6.jar and ojdbc7.jar files from oracle_home/jdbc/lib to cognos_home/webapps/p2pd/web-inf/lib.

Installing the JDBC driver
You must install the Oracle JDBC driver on the Integration Bus node.

Parent topic: Artifact installation for a deployment that contains Oracle Database

Installing the JDBC driver You must install the Oracle JDBC driver on the Integration Bus node.Log on to the Integration Bus node computer as the mqm user. Type the following command:mkdir -p /var/PMQ/JDBC_jar/Copy the Oracle JDBCojdbc7.jar file to /var/PMQ/JDBC_jar/Use the mqm ID and 755 permissions. The ojdbc7.jar file is available from the Oracle web site or your Oracle installation location.PrerequisitesBefore you install the artifacts to support Oracle Database, you must perform some tasks on the Predictive Maintenance and Quality nodes.

Installing the JDBC driver

You must install the Oracle JDBC driver on the Integration Bus node.

Procedure

Log on to the Integration Bus node computer as the mqm user.

Type the following command:

mkdir -p /var/PMQ/JDBC_jar/

Copy the Oracle JDBCojdbc7.jar file to /var/PMQ/JDBC_jar/ Use the mqm ID and 755 permissions. The ojdbc7.jar file is available from the Oracle web site or your Oracle installation location.

Parent topic: Prerequisites

Configuring Cognos Business IntelligenceYou must configure Cognos Business Intelligence on the BI node to point to your Oracle Database server.Open a web browser.Enter the address for the WebSphere Admin Console on the BI node computer.The address is: http://bi_node_name:9060/ibm/console where bi_node_name is the name or IP address for the BI node computer.Enter admin for both the User ID and Password, and click Log in.Expand ServersServer1Process definitionEnvironment Entries.Add the following resources:ResourcesNameValueLD_LIBRARY_PATH/opt/ibm/cognos/c10_64/bin64:/home/oracle/app/oracle/product/12.1.0/client_1/bin/:/home/oracle/app/oracle/product/12.1.0/client_1/lib/ORACLE_HOME/home/oracle/app/oracle/product/12.1.0/client_1TNS_ADMIN/home/oracle/app/oracle/product/12.1.0/client_1/network/admin/Click Apply and click Save.Artifact installation for a deployment that contains Oracle DatabaseFor an Oracle Database installation, you must configure IBM Predictive Maintenance and Quality to access the Oracle Database that contains your Predictive Maintenance and Quality data and reports.

Configuring Cognos Business Intelligence

You must configure Cognos® Business Intelligence on the BI node to point to your Oracle Database server.

Procedure

Open a web browser.

Enter the address for the WebSphere® Admin Console on the BI node computer.

The address is: http://bi_node_name:9060/ibm/console where bi_node_name is the name or IP address for the BI node computer.

Enter admin for both the User ID and Password, and click Log in.

Expand Servers > Server1 > Process definition > Environment Entries.

Add the following resources:

Table 12. Resources

Name | Value
LD_LIBRARY_PATH | /opt/ibm/cognos/c10_64/bin64:/home/oracle/app/oracle/product/12.1.0/client_1/bin/:/home/oracle/app/oracle/product/12.1.0/client_1/lib/
ORACLE_HOME | /home/oracle/app/oracle/product/12.1.0/client_1
TNS_ADMIN | /home/oracle/app/oracle/product/12.1.0/client_1/network/admin/

Click Apply and click Save.

Parent topic: Artifact installation for a deployment that contains Oracle Database

Configuring the PMQ UI serverYou must configure the PMQ UI to point to your Oracle Database.In a web browser, open the WebSphere Administrative Console.The address is http://bi_node_name:9060/ibm/console, where bi_node_name is the name or IP address for the BI node computer. 9060 is the default port number for the WebSphere Administrative Console. Enter admin for both the User ID and Password, and click Log in.Select ResourcesData sources and click New.Enter a value in the Data source name field, enter dbc/tenx in the JNDI name field, and click Next. Click Create new JDBC provider and click Next.Select values for the following fields and then click Next:Database valuesField nameValueDatabase typeOracleProvider_typeOracle JDBC driverImplementation typeXA data sourceEnter the database driver class path information and click Next. The ojdbc7.jar file must be in the path that you enter. Enter the following URL for the data source and click Next.jdbc:oracle:thin:@DB_IP_Address:DB_PORT_NUMBER:IBMPMQContact your database administrator for the values for DB_IP_Address and DB_PORT_NUMBER.Click Next to temporarily ignore the security alias setup.You'll configure the security settings later in this procedure.Click Finish and save your changes. The PMQ UI data source displays in the Data sources window.Click the PMQ UI data source name and then click JAAS - J2C authentication data. Click New, type values for Alias, User ID, and Password that are used to connect to Oracle Database and then click OK.Go back to the Data sources window and click the PMQ UI data source name. Scroll down to the Security settings section.Select the authentication values that you entered in the JAAS - J2C authentication data window and click OK.Select these values for all fields except Mapping-configuration alias.Save the configuration.Click Test connection to validate the connection to the data source.Artifact installation for a deployment that contains Oracle DatabaseFor an Oracle Database installation, you must configure IBM Predictive Maintenance and Quality to access the Oracle Database that contains your Predictive Maintenance and Quality data and reports.

Configuring the PMQ UI server

You must configure the PMQ UI to point to your Oracle Database.

Procedure

In a web browser, open the WebSphere® Administrative Console. The address is http://bi_node_name:9060/ibm/console, where bi_node_name is the name or IP address for the BI node computer. 9060 is the default port number for the WebSphere Administrative Console.

Enter admin for both the User ID and Password, and click Log in.

Select Resources > Data sources and click New.

Enter a value in the Data source name field, enter dbc/tenx in the JNDI name field, and click Next.

Click Create new JDBC provider and click Next.

Select values for the following fields and then click Next:

Table 13. Database values

Field name | Value
Database type | Oracle
Provider_type | Oracle JDBC driver
Implementation type | XA data source

Enter the database driver class path information and click Next.

The ojdbc7.jar file must be in the path that you enter.

Enter the following URL for the data source and click Next.

jdbc:oracle:thin:@DB_IP_Address:DB_PORT_NUMBER:IBMPMQ

Contact your database administrator for the values for DB_IP_Address and DB_PORT_NUMBER.

Click Next to temporarily ignore the security alias setup. You'll configure the security settings later in this procedure.

Click Finish and save your changes. The PMQ UI data source displays in the Data sources window.

Click the PMQ UI data source name and then click JAAS - J2C authentication data.

Click New, type values for Alias, User ID, and Password that are used to connect to Oracle Database and then click OK.

Go back to the Data sources window and click the PMQ UI data source name.

Scroll down to the Security settings section.

Select the authentication values that you entered in the JAAS - J2C authentication data window and click OK. Select these values for all fields except Mapping-configuration alias.

Save the configuration.

Click Test connection to validate the connection to the data source.

Parent topic: Artifact installation for a deployment that contains Oracle Database

Configuring PMQExportUtilityYou must update pmq_export.properties so that you can use PMQExportUtility for Oracle Database. Open the pmq_export.properties file and make the following changes to it: Update the JDBC driver value.pmq_migration_jdbc_driver=oracle.jdbc.OracleDriverUpdate the JDBC driver path value.pmq_migration_jdbc_driver_path=./lib/ojdbc7.jarCopy the ojdbc7.jar into the /lib folder of PMQExportUtility.Update the JDBC URL value to point to the location of the Oracle Database. pmq_migration_jdbc_url=jdbc:oracle:thin:@dbHost:dbPort/IBMPMQContact your database administrator for the values of dbHost and dbPort.Update the JDBC user name and password values with Oracle Database credentials. pmq_migration_jdbc_username=pmqsch pmq_migration_jdbc_password=<schema_password>Artifact installation for a deployment that contains Oracle DatabaseFor an Oracle Database installation, you must configure IBM Predictive Maintenance and Quality to access the Oracle Database that contains your Predictive Maintenance and Quality data and reports.

Configuring PMQExportUtility

You must update pmq_export.properties so that you can use PMQExportUtility for Oracle Database.

Procedure

Open the pmq_export.properties file and make the following changes to it:

Update the JDBC driver value. pmq_migration_jdbc_driver=oracle.jdbc.OracleDriver

Update the JDBC driver path value. pmq_migration_jdbc_driver_path=./lib/ojdbc7.jar

Copy the ojdbc7.jar into the /lib folder of PMQExportUtility.

Update the JDBC URL value to point to the location of the Oracle Database. pmq_migration_jdbc_url=jdbc:oracle:thin:@dbHost:dbPort/IBMPMQ

Contact your database administrator for the values of dbHost and dbPort.

Update the JDBC user name and password values with Oracle Database credentials.

pmq_migration_jdbc_username=pmqsch
pmq_migration_jdbc_password=<schema_password>

Parent topic: Artifact installation for a deployment that contains Oracle Database

Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.The client components must be installed on computers running the Microsoft Windows 7 or Microsoft Windows 8 32 or 64-bit operating system.Install the client components only after you successfully install the server components.Client componentsClient components for IBM Predictive Maintenance and Quality are available to be installed.Starting the Deployment Wizard for the client componentsUse the IBM Predictive Maintenance and Quality Launchpad to start the Deployment Wizard.Changing the temporary location for installation filesThe Deployment Wizard uses a temporary directory for installation source files. You must ensure that you are using a location that has adequate disk space for the installation source files. If you do not have enough disk space in the default location, you can change the location.Installing the client componentsUse the IBM Predictive Maintenance and Quality Deployment Wizard to copy the client installation files to your computer. You must run each installation program individually after the client installation files are copied to your computer.Installing IBM SPSS Collaboration and Deployment Services Deployment ManagerYou must install IBM SPSS Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.Installation of the Integration Bus clientsFor IBM Predictive Maintenance and Quality, you must install MQ Explorer, Integration Toolkit, and Integration Explorer.Installing Framework Manager for IBM Predictive Maintenance and QualityInstall IBM Cognos Framework Manager to create or edit models and publish packages for IBM Cognos Business Intelligence.Copying the license files to each client computerAfter you install the IBM Predictive Maintenance and Quality client components, you must copy the swidtag file and license folder from where you installed the artifacts to the computers on which you install an IBM Predictive Maintenance and Quality client.

Client component installation

There are several client components that are included with IBM® Predictive Maintenance and Quality. You can install the components as you require.

Important: The client components must be installed on computers running the Microsoft Windows 7 or Microsoft Windows 8 32 or 64-bit operating system.

Important: Install the client components only after you successfully install the server components.

Client components
Client components for IBM Predictive Maintenance and Quality are available to be installed.

Starting the Deployment Wizard for the client components
Use the IBM Predictive Maintenance and Quality Launchpad to start the Deployment Wizard.

Changing the temporary location for installation files
The Deployment Wizard uses a temporary directory for installation source files. You must ensure that you are using a location that has adequate disk space for the installation source files. If you do not have enough disk space in the default location, you can change the location.

Installing the client components
Use the IBM Predictive Maintenance and Quality Deployment Wizard to copy the client installation files to your computer. You must run each installation program individually after the client installation files are copied to your computer.

Installing IBM SPSS Collaboration and Deployment Services Deployment Manager
You must install IBM SPSS® Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.

Installation of the Integration Bus clients
For IBM Predictive Maintenance and Quality, you must install MQ Explorer, Integration Toolkit, and Integration Explorer.

Installing Framework Manager for IBM Predictive Maintenance and Quality
Install IBM Cognos® Framework Manager to create or edit models and publish packages for IBM Cognos Business Intelligence.

Copying the license files to each client computer
After you install the IBM Predictive Maintenance and Quality client components, you must copy the swidtag file and license folder from where you installed the artifacts to the computers on which you install an IBM Predictive Maintenance and Quality client.

Client componentsClient components for IBM Predictive Maintenance and Quality are available to be installed.For more information about installing and using the client components, see the documentation provided with the component.After the client installation files are copied to your computer, some paths for the compressed files can be long. You might need to use a decompression utility other than the one provided by Microsoft Windows to decompress the files.Database connectivityInstall IBM Data Server Runtime Client to enable connectivity to the databases. In a multinode deployment, you must use the same configuration values for every instance of IBM Data Server Runtime Client that you install. The configuration values include the installation directory, instance name, instance password, and instance home directory. The previous sentence was added to address defect 27427.Predictive modeling and decision managementInstall the following components so that you can modify or create predictive models and so that you can perform decision management tasks:IBM SPSS Collaboration and Deployment Services Deployment ManagerIBM SPSS Modeler Client PremiumOptionally, install the following components:IBM SPSS Statistics ClientIBM SPSS Collaboration and Deployment Services DocumentationIBM Analytical Decision Management DocumentationIBM SPSS Modeler Premium DocumentationBusiness intelligenceInstall IBM Cognos Framework Manager so that you can modify the reporting model metadata. Framework Manager is a 32-bit application so it requires the 32-bit IBM Data Server Runtime Client. Before you use IBM Cognos Framework Manager: Install IBM Data Server Runtime ClientRestart the computerCatalog the databases Optionally, install the following components: IBM Cognos Business Intelligence SamplesIBM Cognos Dynamic Query AnalyzerIBM Cognos for Microsoft OfficeIBM Cognos Lifecycle ManagerIBM Cognos Software Development KitIBM Cognos Supplementary Languages DocumentationIntegration BusInstall the following components:Integration Bus ToolkitWebSphere MQ for WindowsUse the Integration Bus Toolkit to create, manage, deploy, and delete message flows and associated resources in a development environment.Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.

Client components

Client components for IBM® Predictive Maintenance and Quality are available to be installed.

For more information about installing and using the client components, see the documentation provided with the component.

Important: After the client installation files are copied to your computer, some paths for the compressed files can be long. You might need to use a decompression utility other than the one provided by Microsoft Windows to decompress the files.

Database connectivity

Install IBM Data Server Runtime Client to enable connectivity to the databases. In a multinode deployment, you must use the same configuration values for every instance of IBM Data Server Runtime Client that you install. The configuration values include the installation directory, instance name, instance password, and instance home directory.

Predictive modeling and decision management

Install the following components so that you can modify or create predictive models and so that you can perform decision management tasks:

IBM SPSS® Collaboration and Deployment Services Deployment Manager

IBM SPSS Modeler Client Premium

Optionally, install the following components:

IBM SPSS Statistics Client

IBM SPSS Collaboration and Deployment Services Documentation

IBM Analytical Decision Management Documentation

IBM SPSS Modeler Premium Documentation

Business intelligence

Install IBM Cognos® Framework Manager so that you can modify the reporting model metadata.

Framework Manager is a 32-bit application so it requires the 32-bit IBM Data Server Runtime Client. Before you use IBM Cognos Framework Manager:

Install IBM Data Server Runtime Client

Restart the computer

Catalog the databases

Optionally, install the following components:

IBM Cognos Business Intelligence Samples

IBM Cognos Dynamic Query Analyzer

IBM Cognos for Microsoft Office

IBM Cognos Lifecycle Manager

IBM Cognos Software Development Kit

IBM Cognos Supplementary Languages Documentation

Integration Bus

Install the following components:

Integration Bus Toolkit

WebSphere® MQ for Windows

Use the Integration Bus Toolkit to create, manage, deploy, and delete message flows and associated resources in a development environment.

Parent topic: Client component installation

Starting the Deployment Wizard for the client componentsUse the IBM Predictive Maintenance and Quality Launchpad to start the Deployment Wizard.You must know the location of the pm_q_clt_2.5.2_win_en.tar.gz file that you downloaded from Passport Advantage in Downloading and decompressing the installation filesYou must download the IBM Predictive Maintenance and Quality solution from IBM Passport Advantage, and then decompress the files to run the solution installer..Decompress the pm_q_clt_2.5.2_win_en.tar.gz file.Copy the component installation files to each computer on which you want to install the component.Go to the disk1 directory.Right-click Launchpad.exe or Launchpad64.exe and then select Run-as_Administrator.The Welcome page displays.Click Documentation and Release Notes. A link to the Predictive Maintenance and Quality Knowledge Center is displayed where you can access the product documentation.Click Client Content.A list of client components displays.Click Deploy Client.Click Start the Predictive Maintenance and Quality Client Deployment Wizard. In the Software License Agreement window, read the license agreement terms, and click Accept.The Deployment Wizard opens.Click Next.Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.

Starting the Deployment Wizard for the client components

Use the IBM® Predictive Maintenance and Quality Launchpad to start the Deployment Wizard.

Before you begin

You must know the location of the pm_q_clt_2.5.2_win_en.tar.gz file that you downloaded from Passport Advantage® in Downloading and decompressing the installation files.

Procedure

Decompress the pm_q_clt_2.5.2_win_en.tar.gz file.

Copy the component installation files to each computer on which you want to install the component.

Go to the disk1 directory.

Right-click Launchpad.exe or Launchpad64.exe and then select Run-as_Administrator.

The Welcome page displays.

Click Documentation and Release Notes.

A link to the Predictive Maintenance and Quality Knowledge Center is displayed where you can access the product documentation.

Click Client Content.

A list of client components displays.

Click Deploy Client.

Click Start the Predictive Maintenance and Quality Client Deployment Wizard.

In the Software License Agreement window, read the license agreement terms, and click Accept.

The Deployment Wizard opens.

Click Next.

Parent topic: Client component installation

Changing the temporary location for installation filesThe Deployment Wizard uses a temporary directory for installation source files. You must ensure that you are using a location that has adequate disk space for the installation source files. If you do not have enough disk space in the default location, you can change the location.For example, the default location is tmp/SL_23621/SolutionEnabler/com/ibm/jsdt/webserver/tree. If space is limited on your C drive, you can change the temporary location to another drive.The temporary files include jar files that are used during the installation, which you might want to delete after you complete the installation.In the Deployment Wizard, click EditPreferences.The Deployment Preferences window appears.In the Deployment Package Path box, select an existing location.Click OK.Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.

Changing the temporary location for installation files

The Deployment Wizard uses a temporary directory for installation source files. You must ensure that you are using a location that has adequate disk space for the installation source files. If you do not have enough disk space in the default location, you can change the location.

For example, the default location is tmp/SL_23621/SolutionEnabler/com/ibm/jsdt/webserver/tree. If space is limited on your C drive, you can change the temporary location to another drive.

The temporary files include jar files that are used during the installation, which you might want to delete after you complete the installation.

Procedure

In the Deployment Wizard, click Edit > Preferences.

The Deployment Preferences window appears.

In the Deployment Package Path box, select an existing location.

Click OK.

Parent topic: Client component installation

Installing the client componentsUse the IBM Predictive Maintenance and Quality Deployment Wizard to copy the client installation files to your computer. You must run each installation program individually after the client installation files are copied to your computer.You might need to adjust your Windows User Access Control (UAC) settings so that you can run the installation program for the client components.You can choose from the following client deployments: PMQ Client Installers - 64 BitPMQ Client Installers - 32 BitIn the Deployment Wizard, select one of the deployment options and then click Next. A list of the client installers is displayed.Select the installers that you want deploy and click Next.For each installer that you selected, change or keep the default installation path that is displayed in the Client Deployment Image Location field and click Next.The default installation path is C:\IBM\PMQ2.5.2.Click Deploy all.You can also deploy individual installers by clicking Deploy task beside the installer task. Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.

Installing the client components

Use the IBM® Predictive Maintenance and Quality Deployment Wizard to copy the client installation files to your computer. You must run each installation program individually after the client installation files are copied to your computer.

Tip: You might need to adjust your Windows User Access Control (UAC) settings so that you can run the installation program for the client components.

About this task

You can choose from the following client deployments:

PMQ Client Installers - 64 Bit

PMQ Client Installers - 32 Bit

Procedure

In the Deployment Wizard, select one of the deployment options and then click Next. A list of the client installers is displayed.

Select the installers that you want deploy and click Next.

For each installer that you selected, change or keep the default installation path that is displayed in the Client Deployment Image Location field and click Next. The default installation path is C:\IBM\PMQ2.5.2.

Click Deploy all. You can also deploy individual installers by clicking Deploy task beside the installer task.

Parent topic: Client component installation

Installing IBM SPSS Collaboration and Deployment Services Deployment ManagerYou must install IBM SPSS Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.Install IBM SPSS Collaboration and Deployment Services Deployment Manager on a computer that has the Microsoft Windows 7 or Microsoft Windows 8 operating systems installed.Go to the install_location\Client\Analytics\IBM SPSS Collaboration and Deployment Services Deployment Manager directory.By default, the install_location is C:\IBM\PMQ252\.Decompress the installation package.In the folder containing the installation files, double-click install.exe to start the IBM SPSS Collaboration and Deployment Services Deployment Manager installation.Follow the steps in the wizard to install the client component.For more information about the installation of Deployment Manager, see the IBM SPSS Collaboration and Deployment Services Deployment Manager7 Installation (www.ibm.com/support/knowledgecenter/SS69YH_7.0.0/cads_manager_install_ddita/model_management/thick/thick_install_overview.dita).Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.Adding a content server connection for IBM SPSS Collaboration and Deployment ServicesYou must add a connection to your IBM SPSS Collaboration and Deployment Services repository in the IBM SPSS Collaboration and Deployment Services Deployment Manager client.Adding users and groups to IBM SPSS Collaboration and Deployment ServicesYou use IBM SPSS Collaboration and Deployment Services Deployment Manager to manage users and groups. You must add an administrator user for IBM Predictive Maintenance and Quality.Importing the resource definitions into IBM SPSS Collaboration and Deployment ServicesPredictive Maintenance and Quality resource definitions include credential definitions, data source definitions, message domains, promotion policies, server definitions, and server cluster specifications. These resources are required for running jobs.Adding credential definitions to IBM SPSS Collaboration and Deployment ServicesYou must add user credential definitions in IBM SPSS Collaboration and Deployment Services Deployment Manager. You must add the credentials for your IBM SPSS admin user, the database instance owner, and the root user on the Predictive Analytics node computer.Adding server and resource definitions to IBM SPSS Collaboration and Deployment ServicesYou must add server and resource definitions in Deployment Manager.

Installing IBM SPSS Collaboration and Deployment Services Deployment Manager

You must install IBM® SPSS® Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.

Install IBM SPSS Collaboration and Deployment Services Deployment Manager on a computer that has the Microsoft Windows 7 or Microsoft Windows 8 operating systems installed.

Procedure

Go to the install_location\Client\Analytics\IBM SPSS Collaboration and Deployment Services Deployment Manager directory.

By default, the install_location is C:\IBM\PMQ252\.

Decompress the installation package.

In the folder containing the installation files, double-click install.exe to start the IBM SPSS Collaboration and Deployment Services Deployment Manager installation.

Follow the steps in the wizard to install the client component.

For more information about the installation of Deployment Manager, see the IBM SPSS Collaboration and Deployment Services Deployment Manager7 Installation (www.ibm.com/support/knowledgecenter/SS69YH_7.0.0/cads_manager_install_ddita/model_management/thick/thick_install_overview.dita).

Adding a content server connection for IBM SPSS Collaboration and Deployment Services
You must add a connection to your IBM SPSS Collaboration and Deployment Services repository in the IBM SPSS Collaboration and Deployment Services Deployment Manager client.

Adding users and groups to IBM SPSS Collaboration and Deployment Services
You use IBM SPSS Collaboration and Deployment Services Deployment Manager to manage users and groups. You must add an administrator user for IBM Predictive Maintenance and Quality.

Importing the resource definitions into IBM SPSS Collaboration and Deployment Services
Predictive Maintenance and Quality resource definitions include credential definitions, data source definitions, message domains, promotion policies, server definitions, and server cluster specifications. These resources are required for running jobs.

Adding credential definitions to IBM SPSS Collaboration and Deployment Services
You must add user credential definitions in IBM SPSS Collaboration and Deployment Services Deployment Manager. You must add the credentials for your IBM SPSS admin user, the database instance owner, and the root user on the Predictive Analytics node computer.

Adding server and resource definitions to IBM SPSS Collaboration and Deployment Services
You must add server and resource definitions in Deployment Manager.

Parent topic: Client component installation

Adding a content server connection for IBM SPSS Collaboration and Deployment ServicesYou must add a connection to your IBM SPSS Collaboration and Deployment Services repository in the IBM SPSS Collaboration and Deployment Services Deployment Manager client.After you add the connection, the server folder displays in the Content Explorer, and you can log in to the server.On your Microsoft Windows computer, start IBM SPSS Collaboration and Deployment Services Deployment Manager.For example, click StartDeployment Manager.Click FileNewContent Server Connection.In the Connection Name box, enter a name for your Collaboration and Deployment Services repository.In the Host box, enter the name or IP address of the Predictive Analytics node computer.In the Port box, enter 9080.The default port number that is used by the WebSphere Application Server instance is 9080. If you are using a single node installation of Predictive Maintenance and Quality, the port number is 9082. If you are using Oracle Database, the default port number is 80.Click Finish.Click the connection name that you created.In the User ID and Password boxes, enter the credentials for the CNDS server.Click OK.Installing IBM SPSS Collaboration and Deployment Services Deployment ManagerYou must install IBM SPSS Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.

Adding a content server connection for IBM SPSS Collaboration and Deployment Services

You must add a connection to your IBM® SPSS® Collaboration and Deployment Services repository in the IBM SPSS Collaboration and Deployment Services Deployment Manager client.

After you add the connection, the server folder displays in the Content Explorer, and you can log in to the server.

Procedure

On your Microsoft Windows computer, start IBM SPSS Collaboration and Deployment Services Deployment Manager. For example, click Start > Deployment Manager.

Click File > New > Content Server Connection.

In the Connection Name box, enter a name for your Collaboration and Deployment Services repository.

In the Host box, enter the name or IP address of the Predictive Analytics node computer.

In the Port box, enter 9080.

The default port number that is used by the WebSphere® Application Server instance is 9080.

Important: If you are using a single node installation of Predictive Maintenance and Quality, the port number is 9082.

Note: If you are using Oracle Database, the default port number is 80.

Click Finish.

Click the connection name that you created.

In the User ID and Password boxes, enter the credentials for the CNDS server.

Click OK.

Parent topic: Installing IBM SPSS Collaboration and Deployment Services Deployment Manager

Adding users and groups to IBM SPSS Collaboration and Deployment ServicesYou use IBM SPSS Collaboration and Deployment Services Deployment Manager to manage users and groups. You must add an administrator user for IBM Predictive Maintenance and Quality.In Deployment Manager, click ToolsServer Administration.Click Click here to define a new administrative server connection.In the Name box, enter a name for your server, and click Next.In the Host box, enter the name or IP address of Predictive Analytics node computer.In the Port box, enter the port number of for the WebSphere instance. The default value is 9080.If you are using a single node installation of Predictive Maintenance and Quality, the port number is 9082.Click Finish.Double-click the connection name that you created.In the User ID box, enter admin.In the Password box, enter admin.Click OK.Expand Users and Groups, and double-click Local User Repository.Select Show all available users/groups.Click New Group.Enter administrator.Select Show all available users.Under Available users, move the admin user to Groups contains users.Click OK.Click New Group.Enter DM Administrator.Select Show all available users.Under Available users, move the admin user to Groups contains users.Click OK.Click New Group.Enter DM Users.Select Show all available users.Under Available users, move the admin user to Groups contains users.Click OK.Double-click Roles.Click New Role.In the Role Name box, enter DM Administrator.Click Select All to add all actions for this user role.Click OK.Select the DM Administrator role, and click Edit Users and Groups.Click Show all available users/groups.Under Available users, move the DM Administrator group to Users/Groups Assigned to Role.Click OK.Click New Role.In the Role Name box, enter DM User.Click Select All to add all actions for this user role.Click OK.Select the DM User role, and click Edit Users and Groups.Click Show all available users/groups.Under Available users, move the DM Users group to Users/Groups Assigned to Role.Click OK.Installing IBM SPSS Collaboration and Deployment Services Deployment ManagerYou must install IBM SPSS Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.

Adding users and groups to IBM SPSS Collaboration and Deployment Services

You use IBM® SPSS® Collaboration and Deployment Services Deployment Manager to manage users and groups. You must add an administrator user for IBM Predictive Maintenance and Quality.

Procedure

In Deployment Manager, click Tools > Server Administration.

Click Click here to define a new administrative server connection.

In the Name box, enter a name for your server, and click Next.

In the Host box, enter the name or IP address of Predictive Analytics node computer.

In the Port box, enter the port number of for the WebSphere® instance. The default value is 9080.

Important: If you are using a single node installation of Predictive Maintenance and Quality, the port number is 9082.

Click Finish.

Double-click the connection name that you created.

In the User ID box, enter admin.

In the Password box, enter admin.

Click OK.

Expand Users and Groups, and double-click Local User Repository.

Select Show all available users/groups.

Click New Group.

Enter administrator.

Select Show all available users.

Under Available users, move the admin user to Groups contains users.

Click OK.

Click New Group.

Enter DM Administrator.

Select Show all available users.

Under Available users, move the admin user to Groups contains users.

Click OK.

Click New Group.

Enter DM Users.

Select Show all available users.

Under Available users, move the admin user to Groups contains users.

Click OK.

Double-click Roles.

Click New Role.

In the Role Name box, enter DM Administrator.

Click Select All to add all actions for this user role.

Click OK.

Select the DM Administrator role, and click Edit Users and Groups.

Click Show all available users/groups.

Under Available users, move the DM Administrator group to Users/Groups Assigned to Role.

Click OK.

Click New Role.

In the Role Name box, enter DM User.

Click Select All to add all actions for this user role.

Click OK.

Select the DM User role, and click Edit Users and Groups.

Click Show all available users/groups.

Under Available users, move the DM Users group to Users/Groups Assigned to Role.

Click OK.

Parent topic: Installing IBM SPSS Collaboration and Deployment Services Deployment Manager

Importing the resource definitions into IBM SPSS Collaboration and Deployment ServicesPredictive Maintenance and Quality resource definitions include credential definitions, data source definitions, message domains, promotion policies, server definitions, and server cluster specifications. These resources are required for running jobs.You must import these resource definitions into IBM SPSS Collaboration and Deployment Services Deployment Manager.The resource files are installed onto the Predictive Analytics node computer by the Server Artifact installer. You must copy the content files from the Analytics node to the computer where you installed Deployment Manager.Copy the Analytics node contents to your Windows-based computer by using either an FTP client or by using a shared directory.The contents files are installed to /opt/IBM/PMQ by default on the Analytics node computer.Start Deployment Manager, and select the Content Explorer tab.Right-click Content Repository, and click Import.Browse to and select the pes files from the Analytics node server artifacts.The artifacts include the following files:IBMPMQ_ARMOR_ANALYTICS.pesIBMPMQ_INTEGRATED_FEATURE_BASED_ANALYTICS.pesIBMPMQ_MAINTENANCE_ANALYTICS.pesIBMPMQ_SENSOR_ANALYTICS.pesIBMPMQ_SENSOR_FEATURE_BASED_ANALYTICS.pesIBMPMQ_TOP_FAILURE_PREDICTORS.pesIBMPMQ_WARRANTY.pesClick Open.Accept the default options in the Import window, and click OK.Repeat the previous steps to import each pes file.Installing IBM SPSS Collaboration and Deployment Services Deployment ManagerYou must install IBM SPSS Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.

Importing the resource definitions into IBM SPSS Collaboration and Deployment Services

Predictive Maintenance and Quality resource definitions include credential definitions, data source definitions, message domains, promotion policies, server definitions, and server cluster specifications. These resources are required for running jobs.

You must import these resource definitions into IBM® SPSS® Collaboration and Deployment Services Deployment Manager.

The resource files are installed onto the Predictive Analytics node computer by the Server Artifact installer. You must copy the content files from the Analytics node to the computer where you installed Deployment Manager.

Procedure

Copy the Analytics node contents to your Windows-based computer by using either an FTP client or by using a shared directory.

The contents files are installed to /opt/IBM/PMQ by default on the Analytics node computer.

Start Deployment Manager, and select the Content Explorer tab.

Right-click Content Repository, and click Import.

Browse to and select the pes files from the Analytics node server artifacts.

The artifacts include the following files:

IBMPMQ_ARMOR_ANALYTICS.pes

IBMPMQ_INTEGRATED_FEATURE_BASED_ANALYTICS.pes

IBMPMQ_MAINTENANCE_ANALYTICS.pes

IBMPMQ_SENSOR_ANALYTICS.pes

IBMPMQ_SENSOR_FEATURE_BASED_ANALYTICS.pes

IBMPMQ_TOP_FAILURE_PREDICTORS.pes

IBMPMQ_WARRANTY.pes

Click Open.

Accept the default options in the Import window, and click OK.

Repeat the previous steps to import each pes file.

Parent topic: Installing IBM SPSS Collaboration and Deployment Services Deployment Manager

Adding credential definitions to IBM SPSS Collaboration and Deployment ServicesYou must add user credential definitions in IBM SPSS Collaboration and Deployment Services Deployment Manager. You must add the credentials for your IBM SPSS admin user, the database instance owner, and the root user on the Predictive Analytics node computer.If any of the users already exist, then you must update the user passwords as described in this procedure. In Deployment Manager, click Content Explorer.Expand Resource DefinitionsCredentials.Right-click Credentials, and click NewCredentials Definition.In the Name box, enter admin, and click Next.In the User ID box, enter admin.In the Password box, enter the password you entered for the WebSphere Application Server Profile Administrative User Name.In the Security Provider box, select Local User Repository.Click Finish.Right-click Credentials, and click NewCredentials Definition.In the Name box, enter db2inst1, and click Next.In the User ID box, enter db2inst1.In the Password box, enter the password for your db2inst1 user.Leave the Security Provider box blank.Click Finish.Right-click Credentials, and click NewCredentials Definition.In the Name box, enter modeler, and click Next.In the User ID box, enter root.In the Password box, enter the password for the root user on the Analytics node computer.Leave the Security Provider box blank.Click Finish.Installing IBM SPSS Collaboration and Deployment Services Deployment ManagerYou must install IBM SPSS Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.

Adding credential definitions to IBM SPSS Collaboration and Deployment Services

You must add user credential definitions in IBM® SPSS® Collaboration and Deployment Services Deployment Manager. You must add the credentials for your IBM SPSS admin user, the database instance owner, and the root user on the Predictive Analytics node computer.

About this task

Important:

If any of the users already exist, then you must update the user passwords as described in this procedure.

Procedure

In Deployment Manager, click Content Explorer.

Expand Resource Definitions > Credentials.

Right-click Credentials, and click New > Credentials Definition.

In the Name box, enter admin, and click Next.

In the User ID box, enter admin.

In the Password box, enter the password you entered for the WebSphere Application Server Profile Administrative User Name.

In the Security Provider box, select Local User Repository.

Click Finish.

Right-click Credentials, and click New > Credentials Definition.

In the Name box, enter db2inst1, and click Next.

In the User ID box, enter db2inst1.

In the Password box, enter the password for your db2inst1 user.

Leave the Security Provider box blank.

Click Finish.

Right-click Credentials, and click New > Credentials Definition.

In the Name box, enter modeler, and click Next.

In the User ID box, enter root.

In the Password box, enter the password for the root user on the Analytics node computer.

Leave the Security Provider box blank.

Click Finish.

Parent topic: Installing IBM SPSS Collaboration and Deployment Services Deployment Manager

Adding server and resource definitions to IBM SPSS Collaboration and Deployment ServicesYou must add server and resource definitions in Deployment Manager.If you are not using a computer that is running Microsoft Windows 7 or Microsoft Windows 8 operating systems, some entries, such as server types, might not display correctly.If any of the servers exist, then you must update their properties as described in this procedure. In Deployment Manager, click Content Explorer.Expand Resource Definitions.Perform the following steps to add server definitions: Double-click localhost. In the Server URL field, type the IP address and HTTP Transport port of the Analytics node.For example, http://analytics_node_name:Http_port_number/ .Click Back and verify that the Name is localhost and the Type is Content Repository Service. Click Finish.Double-click modeler.Click Back and verify that the Name is modeler and the Type is Modeler Service. Click Next.Type the host name in the Host field, 28054 in the Port field, and the SPSS Modeler Server installation location the Default data path field. The default SPSS Modeler Server installation path is /opt/IBM/SPSS/ModelerServer/17.0/demos.Click Finish.Perform the following steps to add resource definitions:Expand the Credentials folder.Double-click admin.If you changed CADS credentials, update them, and click Finish. In the Security Provider field, select Local User Repository.Double-click IBMPMQ, enter the credentials for your Oracle Database, and click Finish.Double-click modeler, enter the credentials of the target system, and click Finish.Installing IBM SPSS Collaboration and Deployment Services Deployment ManagerYou must install IBM SPSS Collaboration and Deployment Services Deployment Manager to complete the configuration of IBM Predictive Maintenance and Quality.

Adding server and resource definitions to IBM SPSS Collaboration and Deployment Services

You must add server and resource definitions in Deployment Manager.

If you are not using a computer that is running Microsoft Windows 7 or Microsoft Windows 8 operating systems, some entries, such as server types, might not display correctly.

Procedure

Important: If any of the servers exist, then you must update their properties as described in this procedure.

In Deployment Manager, click Content Explorer.

Expand Resource Definitions.

Perform the following steps to add server definitions:

Double-click localhost.

In the Server URL field, type the IP address and HTTP Transport port of the Analytics node. For example, http://analytics_node_name:Http_port_number/ .

Click Back and verify that the Name is localhost and the Type is Content Repository Service.

Click Finish.

Double-click modeler.

Click Back and verify that the Name is modeler and the Type is Modeler Service.

Click Next.

Type the host name in the Host field, 28054 in the Port field, and the SPSS® Modeler Server installation location the Default data path field.

The default SPSS Modeler Server installation path is /opt/IBM/SPSS/ModelerServer/17.0/demos.

Click Finish.

Perform the following steps to add resource definitions:

Expand the Credentials folder.

Double-click admin.

If you changed CADS credentials, update them, and click Finish. In the Security Provider field, select Local User Repository.

Double-click IBMPMQ, enter the credentials for your Oracle Database, and click Finish.

Double-click modeler, enter the credentials of the target system, and click Finish.

Parent topic: Installing IBM SPSS Collaboration and Deployment Services Deployment Manager

Installation of the Integration Bus clientsFor IBM Predictive Maintenance and Quality, you must install MQ Explorer, Integration Toolkit, and Integration Explorer.Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.Installing MQ ExplorerIBM Integration Explorer client application requires that MQ Explorer is installed on the same computer.Installing the Integration Bus client applicationsInstall the IBM Predictive Maintenance and Quality Integration Bus client applications. The applications include IBM Integration Toolkit and IBM Integration Explorer.Connecting to your WebSphere MQ brokerConnect to the queue manager you created on the IBM Predictive Maintenance and Quality Integration Bus node computer.

Installation of the Integration Bus clients

For IBM® Predictive Maintenance and Quality, you must install MQ Explorer, Integration Toolkit, and Integration Explorer.

Installing MQ Explorer
IBM Integration Explorer client application requires that MQ Explorer is installed on the same computer.

Installing the Integration Bus client applications
Install the IBM Predictive Maintenance and Quality Integration Bus client applications. The applications include IBM Integration Toolkit and IBM Integration Explorer.

Connecting to your WebSphere MQ broker
Connect to the queue manager you created on the IBM Predictive Maintenance and Quality Integration Bus node computer.

Parent topic: Client component installation

Installing MQ ExplorerIBM Integration Explorer client application requires that MQ Explorer is installed on the same computer.Go to the install_location\Client\Integration Bus\IBM Integration Bus directory.By default, the install_location is C:\IBM\PMQ\.Decompress the installation file that is named IIB_IBToolkit_WS_MQ_WINDOWS_X86-64.zip.In the decompressed directory, go to the integrationbus\WebSphere_MQ_V7.5.0.1 directory, and double-click MQLaunch.exe.Click Software Requirements, and ensure that you are using a supported operating system.Click Network Configuration, and select No for Configuring WebSphere MQ for Windows domain users.Click WebSphere MQ Installation, and click Launch IBM Websphere MQ Installer.On the Setup Type page, select Custom, and click Next.On the Features page, select only MQ Explorer to be installed.Ensure that all other features are set to Do not install this feature.Click Next.Click Install, and click Finish.Installation of the Integration Bus clientsFor IBM Predictive Maintenance and Quality, you must install MQ Explorer, Integration Toolkit, and Integration Explorer.

Installing MQ Explorer

IBM® Integration Explorer client application requires that MQ Explorer is installed on the same computer.

Procedure

Go to the install_location\Client\Integration Bus\IBM Integration Bus directory.

By default, the install_location is C:\IBM\PMQ\.

Decompress the installation file that is named IIB_IBToolkit_WS_MQ_WINDOWS_X86-64.zip.

In the decompressed directory, go to the integrationbus\WebSphere_MQ_V7.5.0.1 directory, and double-click MQLaunch.exe.

Click Software Requirements, and ensure that you are using a supported operating system.

Click Network Configuration, and select No for Configuring WebSphere MQ for Windows domain users.

Click WebSphere MQ Installation, and click Launch IBM Websphere MQ Installer.

On the Setup Type page, select Custom, and click Next.

On the Features page, select only MQ Explorer to be installed.

Ensure that all other features are set to Do not install this feature.

Click Next.

Click Install, and click Finish.

Parent topic: Installation of the Integration Bus clients

Installing the Integration Bus client applicationsInstall the IBM Predictive Maintenance and Quality Integration Bus client applications. The applications include IBM Integration Toolkit and IBM Integration Explorer.Ensure that MQ Explorer is already installed.Go to the directory where you decompressed the Integration Bus client application installers.In the decompressed directory, in the integrationbus directory, double-click mqsilaunchpad.exe.Select the check boxes for IBM Integration Toolkit, and IBM Integration Explorer. Clear the check box for IBM Integration Bus.If it is not already installed, IBM Installation Manager is installed with IBM Integration Toolkit.Click Launch Installation for IBM Integration Bus.IBM Installation Manager appears.Follow the steps in IBM Installation Manager to install IBM Integration Toolkit.When you are prompted to open a product, select None, and click Finish.The installer for IBM Integration Explorer appears.Follow the steps in the wizard to install IBM Integration Explorer.Installation of the Integration Bus clientsFor IBM Predictive Maintenance and Quality, you must install MQ Explorer, Integration Toolkit, and Integration Explorer.

Installing the Integration Bus client applications

Install the IBM® Predictive Maintenance and Quality Integration Bus client applications. The applications include IBM Integration Toolkit and IBM Integration Explorer.

Before you begin

Ensure that MQ Explorer is already installed.

Procedure

Go to the directory where you decompressed the Integration Bus client application installers.

In the decompressed directory, in the integrationbus directory, double-click mqsilaunchpad.exe.

Select the check boxes for IBM Integration Toolkit, and IBM Integration Explorer. Clear the check box for IBM Integration Bus.

If it is not already installed, IBM Installation Manager is installed with IBM Integration Toolkit.

Click Launch Installation for IBM Integration Bus.

IBM Installation Manager appears.

Follow the steps in IBM Installation Manager to install IBM Integration Toolkit.

When you are prompted to open a product, select None, and click Finish.

The installer for IBM Integration Explorer appears.

Follow the steps in the wizard to install IBM Integration Explorer.

Parent topic: Installation of the Integration Bus clients

Connecting to your WebSphere MQ brokerConnect to the queue manager you created on the IBM Predictive Maintenance and Quality Integration Bus node computer.In a terminal window, type the following command (all on one line):The following code block is split into to parts so that the content displays correctly in the PDF output. If it is not split, the content runs over the page and gets cut off.setmqaut -m pmqmanager -t queue -n SYSTEM.MQEXPLORER.REPLY.MODEL -g mqm +browse -get +putFrom the Start menu, click All ProgramsIBM WebSphere MQWebSphere MQ Explorer.The first time that you start WebSphere MQ Explorer, you are prompted for a workspace location.In the MQ Explorer - Navigator, under IBM WebSphere MQ, right-click Queue Managers, and select Add Remote Queue Manager.Enter the name of your queue manager, select Connect directly, and click Next.For example, enter pmqmanager.In the Connection details section, enter the following information, and click Next.In the Host name or IP address box, enter the information for your Integration Bus node computer.In the Port number box, enter the listener port number. The default is 1414.In the Server-connection channel box, enter SYSTEM.BKR.CONFIGOn the Specify user identification details page, select Enable user identification.In the Userid box, enter mqm.The first time that you add a user, you must enable password saving. Click Passwords Preferences Page, and then select Save passwords to file to enable the feature, and click OK.Click Enter password.Enter the user's password, and click OK.Click Finish.The queue manager appears in the list, and the status appears as running.Installation of the Integration Bus clientsFor IBM Predictive Maintenance and Quality, you must install MQ Explorer, Integration Toolkit, and Integration Explorer.

Connecting to your WebSphere MQ broker

Connect to the queue manager you created on the IBM® Predictive Maintenance and Quality Integration Bus node computer.

Procedure

In a terminal window, type the following command (all on one line):

setmqaut -m pmqmanager -t queue -n SYSTEM.MQEXPLORER.REPLY.MODEL -g mqm

+browse -get +put

From the Start menu, click All Programs > IBM WebSphere MQ > WebSphere MQ Explorer.

The first time that you start WebSphere® MQ Explorer, you are prompted for a workspace location.

In the MQ Explorer - Navigator, under IBM WebSphere MQ, right-click Queue Managers, and select Add Remote Queue Manager.

Enter the name of your queue manager, select Connect directly, and click Next. For example, enter pmqmanager.

In the Connection details section, enter the following information, and click Next.

In the Host name or IP address box, enter the information for your Integration Bus node computer.

In the Port number box, enter the listener port number. The default is 1414.

In the Server-connection channel box, enter SYSTEM.BKR.CONFIG

On the Specify user identification details page, select Enable user identification.

In the Userid box, enter mqm.

The first time that you add a user, you must enable password saving. Click Passwords Preferences Page, and then select Save passwords to file to enable the feature, and click OK.

Click Enter password.

Enter the user's password, and click OK.

Click Finish. The queue manager appears in the list, and the status appears as running.

Parent topic: Installation of the Integration Bus clients

Installing Framework Manager for IBM Predictive Maintenance and Quality Install IBM Cognos Framework Manager to create or edit models and publish packages for IBM Cognos Business Intelligence.Go to the install_location\Client\Business Intelligence\IBM Cognos Framework Manager directory.By default, the install_location is C:\IBM\PMQ\.Decompress fm_10.2.2_win_ml.tar.gz, and then decompress fm_10.2.2_win_ml.tar.Go to the win32 directory, and double-click the issetup.exe file.Follow the steps in the wizard to install the product.When notified with an information message about installing the Supplementary Languages Documentation, click OKOn the last page of the installation wizard, select Start IBM Cognos Configuration to configure Cognos Framework Manager.Click Finish.In IBM Cognos Configuration, in the Explorer panel, select Environment.In the Gateway URI value, change localhost to the name or IP address of the Business Intelligence (BI) node computer.In the Dispatcher URI for external applications value, change localhost to the name or IP address of the Business Intelligence (BI) node computer.In the Dispatcher URI for external applications value, change 9300 to 9080. 9080 is the port number that is used by WebSphere Application Server for IBM Cognos Business Intelligence.Click FileSave.Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.

Installing Framework Manager for IBM Predictive Maintenance and Quality

Install IBM® Cognos® Framework Manager to create or edit models and publish packages for IBM Cognos Business Intelligence.

Procedure

Go to the install_location\Client\Business Intelligence\IBM Cognos Framework Manager directory.

By default, the install_location is C:\IBM\PMQ\.

Decompress fm_10.2.2_win_ml.tar.gz, and then decompress fm_10.2.2_win_ml.tar.

Go to the win32 directory, and double-click the issetup.exe file.

Follow the steps in the wizard to install the product.

When notified with an information message about installing the Supplementary Languages Documentation, click OK

On the last page of the installation wizard, select Start IBM Cognos Configuration to configure Cognos Framework Manager.

Click Finish.

In IBM Cognos Configuration, in the Explorer panel, select Environment.

In the Gateway URI value, change localhost to the name or IP address of the Business Intelligence (BI) node computer.

In the Dispatcher URI for external applications value, change localhost to the name or IP address of the Business Intelligence (BI) node computer.

In the Dispatcher URI for external applications value, change 9300 to 9080. 9080 is the port number that is used by WebSphere® Application Server for IBM Cognos Business Intelligence.

Click File > Save.

Parent topic: Client component installation

Copying the license files to each client computerAfter you install the IBM Predictive Maintenance and Quality client components, you must copy the swidtag file and license folder from where you installed the artifacts to the computers on which you install an IBM Predictive Maintenance and Quality client.Do not rename the folders or files.Copy the swidtag file from the iso-swid folder where you installed the artifacts to each computer on which you install a client.For example, copy the file so that you have a C:\IBM\PMQ2.5.2\iso-swid folder that contains a swidtag file.Copy the license folder from the folder where you installed the artifacts to each computer on which you install a client.For example, copy the folder and contents so that you have a C:\IBM\PMQ2.5.2\license folder that contains the license files.Client component installationThere are several client components that are included with IBM Predictive Maintenance and Quality. You can install the components as you require.

Copying the license files to each client computer

After you install the IBM® Predictive Maintenance and Quality client components, you must copy the swidtag file and license folder from where you installed the artifacts to the computers on which you install an IBM Predictive Maintenance and Quality client.

Important: Do not rename the folders or files.

Procedure

Copy the swidtag file from the iso-swid folder where you installed the artifacts to each computer on which you install a client.

For example, copy the file so that you have a C:\IBM\PMQ2.5.2\iso-swid folder that contains a swidtag file.

Copy the license folder from the folder where you installed the artifacts to each computer on which you install a client.

For example, copy the folder and contents so that you have a C:\IBM\PMQ2.5.2\license folder that contains the license files.

Parent topic: Client component installation

Stop and start solution software servicesIBM Predictive Maintenance and Quality is an integrated solution that includes many products. If you must stop the services, you must do so in the correct order. The product services must also be started in the correct order.Stop solution servicesYou must stop the IBM Predictive Maintenance and Quality node services in a specific order.Start solution servicesYou must start the IBM Predictive Maintenance and Quality node services in a specific order.

Stop and start solution software services

IBM® Predictive Maintenance and Quality is an integrated solution that includes many products. If you must stop the services, you must do so in the correct order. The product services must also be started in the correct order.

Stop solution services
You must stop the IBM Predictive Maintenance and Quality node services in a specific order.

Start solution services
You must start the IBM Predictive Maintenance and Quality node services in a specific order.

Stop solution servicesYou must stop the IBM Predictive Maintenance and Quality node services in a specific order.Stop the node services in the following order:Master Data Management (MDM) nodeYou must stop the services on the Master Data Management (MDM) node before you stop services on other nodes.Business Intelligence (BI) nodeYou must stop the IBM Cognos Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.Integration Bus nodeYou must stop the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.Predictive Analytics nodeYou must stop the IBM SPSS services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.data nodeYou must stop the IBM DB2 instance on the IBM Predictive Maintenance and Quality data node computer.Stop and start solution software servicesIBM Predictive Maintenance and Quality is an integrated solution that includes many products. If you must stop the services, you must do so in the correct order. The product services must also be started in the correct order.Stopping services on the MDM node computerYou must stop the services on the Master Data Management (MDM) node before you stop services on other nodes.Stopping services on the BI node computerYou must stop the IBM Cognos Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.Stopping services on the Integration Bus node computerYou must stop the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.Stopping services on the Analytics node computerYou must stop the IBM SPSS services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.Stopping services on the data node computerYou must stop the IBM DB2 instance on the IBM Predictive Maintenance and Quality data node computer.

Stop solution services

You must stop the IBM® Predictive Maintenance and Quality node services in a specific order.

Stop the node services in the following order:

Master Data Management (MDM) node

Business Intelligence (BI) node

Integration Bus node

Predictive Analytics node

data node

Stopping services on the MDM node computer
You must stop the services on the Master Data Management (MDM) node before you stop services on other nodes.

Stopping services on the BI node computer
You must stop the IBM Cognos Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.

Stopping services on the Integration Bus node computer
You must stop the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.

Stopping services on the Analytics node computer
You must stop the IBM SPSS services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.

Stopping services on the data node computer
You must stop the IBM DB2 instance on the IBM Predictive Maintenance and Quality data node computer.

Parent topic: Stop and start solution software services

Stopping services on the MDM node computerYou must stop the services on the Master Data Management (MDM) node before you stop services on other nodes.Log in to the MDM node computer as root.Go to the MDM installation location.For example, go to /opt/IBM/MDMPIM.Go to the /bin/go directory.Enter the following command:./stop_local.shGo to the WebSphere Application Server profile directory when MDM is running.For example, go to /opt/IBM/WebSphere/AppServer/profiles/MDMProfile/bin.Enter the following command:./stopServer.sh server1Stop solution servicesYou must stop the IBM Predictive Maintenance and Quality node services in a specific order.

Stopping services on the MDM node computer

You must stop the services on the Master Data Management (MDM) node before you stop services on other nodes.

Procedure

Log in to the MDM node computer as root.

Go to the MDM installation location. For example, go to /opt/IBM/MDMPIM.

Go to the /bin/go directory.

Enter the following command:

./stop_local.sh

Go to the WebSphere® Application Server profile directory when MDM is running. For example, go to /opt/IBM/WebSphere/AppServer/profiles/MDMProfile/bin.

Enter the following command:

./stopServer.sh server1

Parent topic: Stop solution services

Stopping services on the BI node computerYou must stop the IBM Cognos Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.You stop the IBM Cognos BI services by stopping the WebSphere Application Server profile where IBM Cognos BI is running.Log in to the BI node computer as root.Go to the WebSphere Application Server profile directory when IBM Cognos BI is running.For example, go to /opt/IBM/WebSphere/AppServer/profiles/CustomProfile/bin.Enter the following command:./stopServer.sh server1Go to the IBM HTTP Server bin directory.For example, go to /opt/IBM/HTTPServer/bin.Enter the following command:./apachectl -f ./conf/httpd.conf -k stopStop solution servicesYou must stop the IBM Predictive Maintenance and Quality node services in a specific order.

Stopping services on the BI node computer

You must stop the IBM® Cognos® Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.

You stop the IBM Cognos BI services by stopping the WebSphere® Application Server profile where IBM Cognos BI is running.

Procedure

Log in to the BI node computer as root.

Go to the WebSphere Application Server profile directory when IBM Cognos BI is running. For example, go to /opt/IBM/WebSphere/AppServer/profiles/CustomProfile/bin.

Enter the following command:

./stopServer.sh server1

Go to the IBM HTTP Server bin directory. For example, go to /opt/IBM/HTTPServer/bin.

Enter the following command:

./apachectl -f ./conf/httpd.conf -k stop

Parent topic: Stop solution services

Stopping services on the Integration Bus node computerYou must stop the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.Log in to the Integration Bus node computer as root.Change to the mqm user.For example, enter the following command:su - mqmuserGo to the IBM Integration Bus bin directory.For example, go to /opt/ibm/mqsi/9.0.0.2/bin.Enter the following command:./mqsistop pmqbroker -iEnter the following command to verify that the services are stopped:./mqsilist pmqbrokerStop solution servicesYou must stop the IBM Predictive Maintenance and Quality node services in a specific order.

Stopping services on the Integration Bus node computer

You must stop the IBM® Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.

Procedure

Log in to the Integration Bus node computer as root.

Change to the mqm user. For example, enter the following command:

su - mqmuser

Go to the IBM Integration Bus bin directory. For example, go to /opt/ibm/mqsi/9.0.0.2/bin.

Enter the following command:

./mqsistop pmqbroker -i

Enter the following command to verify that the services are stopped:

./mqsilist pmqbroker

Parent topic: Stop solution services

Stopping services on the Analytics node computerYou must stop the IBM SPSS services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.Log in to the Analytics node computer as root.Go to the WebSphere Application Server SPSSProfile/bin directory.For example, go to /opt/IBM/WebSphere/AppServer/profiles/SPSSProfile/bin.Enter the following command:./stopServer.sh server1Go to the IBM SPSS Modeler Server directory.For example, go to /usr/IBM/SPSS/ModelerServer/17.0.Enter the following command:./modelersrv.sh stopTo verify whether any services are still running enter the following command:ps -ef | grep statisticsdTo stop any services that are still running enter the following command:kill -9 'cat statisticsd.pid'Stop solution servicesYou must stop the IBM Predictive Maintenance and Quality node services in a specific order.

Stopping services on the Analytics node computer

You must stop the IBM® SPSS® services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.

Procedure

Log in to the Analytics node computer as root.

Go to the WebSphere® Application Server SPSSProfile/bin directory. For example, go to /opt/IBM/WebSphere/AppServer/profiles/SPSSProfile/bin.

Enter the following command:

./stopServer.sh server1

Go to the IBM SPSS Modeler Server directory. For example, go to /usr/IBM/SPSS/ModelerServer/17.0.

Enter the following command:

./modelersrv.sh stop

To verify whether any services are still running enter the following command:

ps -ef | grep statisticsd

To stop any services that are still running enter the following command:

kill -9 'cat statisticsd.pid'

Parent topic: Stop solution services

Stopping services on the data node computerYou must stop the IBM DB2 instance on the IBM Predictive Maintenance and Quality data node computer.Log in to the data node computer as root.In a terminal window, type the following command to change the DB2 instance owner:su - db2inst1Enter the following command to stop the DB2 administration server:db2stopStop solution servicesYou must stop the IBM Predictive Maintenance and Quality node services in a specific order.

Stopping services on the data node computer

You must stop the IBM® DB2® instance on the IBM Predictive Maintenance and Quality data node computer.

Procedure

Log in to the data node computer as root.

In a terminal window, type the following command to change the DB2 instance owner:

su - db2inst1

Enter the following command to stop the DB2 administration server:

db2stop

Parent topic: Stop solution services

Start solution servicesYou must start the IBM Predictive Maintenance and Quality node services in a specific order.Start the node services in the following order:data nodeYou must start the IBM DB2 instance on the IBM Predictive Maintenance and Quality data node computer.Predictive Analytics nodeYou must start the IBM SPSS services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.Integration Bus nodeYou must start the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.Business Intelligence (BI) nodeYou must start the IBM Cognos Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.Master Data Management (MDM) nodeStart the services on the Master Data Management (MDM) node after you start services on other nodes.Stop and start solution software servicesIBM Predictive Maintenance and Quality is an integrated solution that includes many products. If you must stop the services, you must do so in the correct order. The product services must also be started in the correct order.Starting services on the data node computerYou must start the IBM DB2 instance on the IBM Predictive Maintenance and Quality data node computer.Starting services on the Analytics node computerYou must start the IBM SPSS services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.Starting services on the Integration Bus node computerYou must start the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.Starting services on the BI node computerYou must start the IBM Cognos Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.Starting services on the MDM node computerStart the services on the Master Data Management (MDM) node after you start services on other nodes.

Start solution services

You must start the IBM® Predictive Maintenance and Quality node services in a specific order.

Start the node services in the following order:

data node

Predictive Analytics node

Integration Bus node

Business Intelligence (BI) node

Master Data Management (MDM) node

Starting services on the data node computer
You must start the IBM DB2 instance on the IBM Predictive Maintenance and Quality data node computer.

Starting services on the Analytics node computer
You must start the IBM SPSS services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.

Starting services on the Integration Bus node computer
You must start the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.

Starting services on the BI node computer
You must start the IBM Cognos Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.

Starting services on the MDM node computer
Start the services on the Master Data Management (MDM) node after you start services on other nodes.

Parent topic: Stop and start solution software services

Starting services on the data node computerYou must start the IBM DB2 instance on the IBM Predictive Maintenance and Quality data node computer.Log in to the data node computer as root.In a terminal window, type the following command to change the DB2 instance owner:su - db2inst1Enter the following command to stop the DB2 administration server:db2startStart solution servicesYou must start the IBM Predictive Maintenance and Quality node services in a specific order.

Starting services on the data node computer

You must start the IBM® DB2® instance on the IBM Predictive Maintenance and Quality data node computer.

Procedure

Log in to the data node computer as root.

In a terminal window, type the following command to change the DB2 instance owner:

su - db2inst1

Enter the following command to stop the DB2 administration server:

db2start

Parent topic: Start solution services

Starting services on the Analytics node computerYou must start the IBM SPSS services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.Log in to the Analytics node computer as root.Go to the WebSphere Application Server SPSSProfile/bin directory.For example, go to /opt/IBM/WebSphere/AppServer/profiles/SPSSProfile/bin.Enter the following command:./startServer.sh server1Go to the IBM SPSS Modeler Server directory.For example, go to /usr/IBM/SPSS/ModelerServer/17.0.Enter the following command:./modelersrv.sh startStart solution servicesYou must start the IBM Predictive Maintenance and Quality node services in a specific order.

Starting services on the Analytics node computer

You must start the IBM® SPSS® services on the IBM Predictive Maintenance and Quality Predictive Analytics node computer.

Procedure

Log in to the Analytics node computer as root.

Go to the WebSphere® Application Server SPSSProfile/bin directory. For example, go to /opt/IBM/WebSphere/AppServer/profiles/SPSSProfile/bin.

Enter the following command:

./startServer.sh server1

Go to the IBM SPSS Modeler Server directory. For example, go to /usr/IBM/SPSS/ModelerServer/17.0.

Enter the following command:

./modelersrv.sh start

Parent topic: Start solution services

Starting services on the Integration Bus node computerYou must start the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.Log in to the Integration Bus node computer as root.Change to the mqm user.For example, enter the following command:su - mqmuserGo to the IBM Integration Bus bin directory.For example, go to /opt/ibm/mqsi/9.0.0.2/bin.Enter the following command:./mqsistart pmqbrokerEnter the following command to verify that the services are started:./mqsilist pmqbroker or ./mqsilist pmqbroker -e pmqgroup1. The latter command lists all entries that are running under pmqgroup1.Enter the following commands: START LISTENER ENDStart solution servicesYou must start the IBM Predictive Maintenance and Quality node services in a specific order.

Starting services on the Integration Bus node computer

You must start the IBM® Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer.

Procedure

Log in to the Integration Bus node computer as root.

Change to the mqm user. For example, enter the following command:

su - mqmuser

Go to the IBM Integration Bus bin directory. For example, go to /opt/ibm/mqsi/9.0.0.2/bin.

Enter the following command:

./mqsistart pmqbroker

Enter the following command to verify that the services are started:

./mqsilist pmqbroker or ./mqsilist pmqbroker -e pmqgroup1. The latter command lists all entries that are running under pmqgroup1.

Enter the following commands:

START LISTENER

END

Parent topic: Start solution services

Starting services on the BI node computerYou must start the IBM Cognos Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.You start the IBM Cognos BI services by starting the WebSphere Application Server profile where IBM Cognos BI is running.Log in to the BI node computer as root.Go to the WebSphere Application Server profile directory when IBM Cognos BI is running.For example, go to /opt/IBM/WebSphere/AppServer/profiles/COGNOSProfile/bin.Enter the following command:./startServer.sh server1Go to the IBM HTTP Server bin directory.For example, go to /opt/IBM/HTTPServer/bin.Enter the following command:./apachectl -f ./conf/httpd.conf -k startStart solution servicesYou must start the IBM Predictive Maintenance and Quality node services in a specific order.

Starting services on the BI node computer

You must start the IBM® Cognos® Business Intelligence services and IBM HTTP Server on the IBM Predictive Maintenance and Quality Business Intelligence (BI) node computer.

You start the IBM Cognos BI services by starting the WebSphere® Application Server profile where IBM Cognos BI is running.

Procedure

Log in to the BI node computer as root.

Go to the WebSphere Application Server profile directory when IBM Cognos BI is running. For example, go to /opt/IBM/WebSphere/AppServer/profiles/COGNOSProfile/bin.

Enter the following command:

./startServer.sh server1

Go to the IBM HTTP Server bin directory. For example, go to /opt/IBM/HTTPServer/bin.

Enter the following command:

./apachectl -f ./conf/httpd.conf -k start

Parent topic: Start solution services

Starting services on the MDM node computerStart the services on the Master Data Management (MDM) node after you start services on other nodes.Log in to the MDM node computer as root.Go to the MDM installation location.For example, go to /opt/IBM/MDM.Go to the /bin/go directory.Enter the following command:./start_local.shGo to the WebSphere Application Server profile directory when MDM is running.For example, go to /opt/IBM/WebSphere/AppServer/profiles/MDMProfile/bin.Enter the following command:./startServer.sh server1Start solution servicesYou must start the IBM Predictive Maintenance and Quality node services in a specific order.

Starting services on the MDM node computer

Start the services on the Master Data Management (MDM) node after you start services on other nodes.

Procedure

Log in to the MDM node computer as root.

Go to the MDM installation location. For example, go to /opt/IBM/MDM.

Go to the /bin/go directory.

Enter the following command:

./start_local.sh

Go to the WebSphere® Application Server profile directory when MDM is running. For example, go to /opt/IBM/WebSphere/AppServer/profiles/MDMProfile/bin.

Enter the following command:

./startServer.sh server1

Parent topic: Start solution services

Product license filesAfter you manually install IBM Predictive Maintenance and Quality, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed an Predictive Maintenance and Quality component.Copying the component license files to each component computerThe swidtag file and license directory must exist on each server node computer and each computer on which you install a client that is used with Predictive Maintenance and Quality.Updating your software tag file if you change product usageIf you change your usage of IBM Predictive Maintenance and Quality, such as to a non-production environment from a production environment, you must switch the software tags for your installation.

Product license files

After you manually install IBM® Predictive Maintenance and Quality, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed an Predictive Maintenance and Quality component.

Copying the component license files to each component computer
The swidtag file and license directory must exist on each server node computer and each computer on which you install a client that is used with Predictive Maintenance and Quality.

Updating your software tag file if you change product usage
If you change your usage of IBM Predictive Maintenance and Quality, such as to a non-production environment from a production environment, you must switch the software tags for your installation.

Copying the component license files to each component computerThe swidtag file and license directory must exist on each server node computer and each computer on which you install a client that is used with Predictive Maintenance and Quality. swidtag files are provided for both production and non-production use of Predictive Maintenance and Quality. You must copy the appropriate swidtag file for your usage. Do not rename the directory or files If you installed on a Red Hat Enterprise Linux operating system by using the solution installer, the license files are automatically copied to each server node computer.On the computer where you decompressed the artifact files, go to the iso-swid or iso-swid_NonProduction directory, and decompress the file, if applicable.Copy the swidtag file to each computer on which you installed an Predictive Maintenance and Quality component.For example, on Microsoft Windows operating systems, copy the file so that you have a C:\IBM\PMQ2.5.2\iso-swid directory that contains a swidtag file. On Linux operating systems, you would have an /opt/IBM/PMQ2.5.2/iso-swid directory that contains a swidtag file.From the directory where you decompressed the artifact files, decompress the license.zip file, and then copy the license directory to each computer where you installed an Predictive Maintenance and Quality component.For example, On Microsoft Windows operating systems, copy the directory and contents so that you have a C:\IBM\PMQ2.5.2\license directory that contains the license files. On Linux operating systems, you would have an /opt/IBM/PMQ2.5.2/license directory that contains the license files.The following folders must exist on each computer on which you installed an Predictive Maintenance and Quality component:On Microsoft Windows operating systems (both server and client components):C:\IBM\PMQ2.5.2\license (containing the product license files)C:\IBM\PMQ2.5.2\iso-swid (containing the product swidtag file)On Linux operating systems where a server component is installed: /opt/IBM/PMQ2.5.2/license (containing the product license files) /opt/IBM/PMQ2.5.2/iso-swid (containing the product swidtag file)Product license filesAfter you manually install IBM Predictive Maintenance and Quality, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed an Predictive Maintenance and Quality component.

Copying the component license files to each component computer

The swidtag file and license directory must exist on each server node computer and each computer on which you install a client that is used with Predictive Maintenance and Quality.

swidtag files are provided for both production and non-production use of Predictive Maintenance and Quality. You must copy the appropriate swidtag file for your usage.

Note: Do not rename the directory or files

If you installed on a Red Hat Enterprise Linux operating system by using the solution installer, the license files are automatically copied to each server node computer.

Procedure

On the computer where you decompressed the artifact files, go to the iso-swid or iso-swid_NonProduction directory, and decompress the file, if applicable.

Copy the swidtag file to each computer on which you installed an Predictive Maintenance and Quality component.

For example, on Microsoft Windows operating systems, copy the file so that you have a C:\IBM\PMQ2.5.2\iso-swid directory that contains a swidtag file. On Linux operating systems, you would have an /opt/IBM/PMQ2.5.2/iso-swid directory that contains a swidtag file.

From the directory where you decompressed the artifact files, decompress the license.zip file, and then copy the license directory to each computer where you installed an Predictive Maintenance and Quality component.

For example, On Microsoft Windows operating systems, copy the directory and contents so that you have a C:\IBM\PMQ2.5.2\license directory that contains the license files. On Linux operating systems, you would have an /opt/IBM/PMQ2.5.2/license directory that contains the license files.

Results

The following folders must exist on each computer on which you installed an Predictive Maintenance and Quality component:

On Microsoft Windows operating systems (both server and client components):

C:\IBM\PMQ2.5.2\license (containing the product license files)

C:\IBM\PMQ2.5.2\iso-swid (containing the product swidtag file)

On Linux operating systems where a server component is installed:

/opt/IBM/PMQ2.5.2/license (containing the product license files)

/opt/IBM/PMQ2.5.2/iso-swid (containing the product swidtag file)

Parent topic: Product license files

Updating your software tag file if you change product usageIf you change your usage of IBM Predictive Maintenance and Quality, such as to a non-production environment from a production environment, you must switch the software tags for your installation.You must copy the appropriate software tag file to each computer on which an Predictive Maintenance and Quality server or client component is installed.On the computer where you decompressed the artifact files, go to the iso-swid or iso-swid_NonProduction directory, and decompress the file, if applicable.Copy the swidtag file to each computer on which you installed an Predictive Maintenance and Quality component and replace the existing file.For example, on Microsoft Windows operating systems, copy the file so that you have a C:\IBM\PMQ2.5.2\iso-swid directory that contains a swidtag file. On Linux operating systems, you would have an /opt/IBM/PMQ2.5.2/iso-swid directory that contains a swidtag file.Product license filesAfter you manually install IBM Predictive Maintenance and Quality, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed an Predictive Maintenance and Quality component.

Updating your software tag file if you change product usage

If you change your usage of IBM® Predictive Maintenance and Quality, such as to a non-production environment from a production environment, you must switch the software tags for your installation.

You must copy the appropriate software tag file to each computer on which an Predictive Maintenance and Quality server or client component is installed.

Procedure

On the computer where you decompressed the artifact files, go to the iso-swid or iso-swid_NonProduction directory, and decompress the file, if applicable.

Copy the swidtag file to each computer on which you installed an Predictive Maintenance and Quality component and replace the existing file.

For example, on Microsoft Windows operating systems, copy the file so that you have a C:\IBM\PMQ2.5.2\iso-swid directory that contains a swidtag file. On Linux operating systems, you would have an /opt/IBM/PMQ2.5.2/iso-swid directory that contains a swidtag file.

Parent topic: Product license files

Accessibility features Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products. For information about the commitment that IBM has to accessibility, see the IBM Accessibility Center (www.ibm.com/able).IBM Cognos HTML documentation has accessibility features. PDF documents are supplemental and, as such, include no added accessibility features. Report output In IBM Cognos Administration, you can enable system-wide settings to create accessible report output. For more information, see the IBM Cognos Business Intelligence Administration and Security Guide. In IBM Cognos Report Studio, you can enable settings to create accessible output for individual reports. For more information, see the IBM Cognos Report Studio User Guide. You can access the previously mentioned documents at IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter).

Accessibility features

Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products.

For information about the commitment that IBM has to accessibility, see the IBM Accessibility Center (www.ibm.com/able).

IBM Cognos HTML documentation has accessibility features. PDF documents are supplemental and, as such, include no added accessibility features.

Report output

In IBM Cognos Administration, you can enable system-wide settings to create accessible report output. For more information, see the IBM Cognos Business Intelligence Administration and Security Guide. In IBM Cognos Report Studio, you can enable settings to create accessible output for individual reports. For more information, see the IBM Cognos Report Studio User Guide. You can access the previously mentioned documents at IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter).

TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.Progress bar shows null% as valueDuring the installation, the progress bar in the Run Progress box shows null%.Installation stops abruptlyDuring the installation, an error is displayed in the solution installer and the log file appears to have also ended abruptly.Run Progress box shows more nodes than are in your configurationThe Run Progress box shows the installation progress. It might show more nodes than you are using in your configuration.JAVA_HOME not set when starting IBM Cognos ConfigurationAfter you install IBM Predictive Maintenance and Quality as a sudo user, you receive a message that the JAVA_HOME environment variable is not set.CONFIGURATION ERROR:Specified config file /etc/opscode/pivotal.rb does not exist errorYou have reinstalled the solution installer after you used the cleanup.sh script, and when you run the solution installer you get an error message like the following:Solution installer indicates successful completion but progress bars are not completeDuring the installation, a message in the solution installer indicates that the installation has completed successfully, but the Run Progress box shows that some installation tasks are not yet complete. No Server Connection when you view log details from solution installerWhile you are running an installation, you click Get Details and you get a No Server Connection page in your web browser. This error can occur if the server is not properly registered in the domain controller or the DHCP server.Modeler Server type not displaying in resource definitionsIn IBM Predictive Maintenance and Quality, if the Modeler Server type does not display in resource definitions in IBM SPSS Collaboration and Deployment Services Deployment Manager, try closing Deployment Manager and opening it again.Unable to import the company archive in MDMIf you cannot import the IBM Predictive Maintenance and Quality company archive in the Master Data Management (MDM) console, you can manually import the archive.Error installing IBM Cognos BIThe IBM Cognos Business Intelligence installer requires a specific library file in order to run.Restarting the queue manager and brokerAfter a IBM Predictive Maintenance and Quality Integration Bus node server restart, you might need to restart the queue manager and broker.Subscription to live feed failed error in DashboardWhen you subscribe to a dashboard, you receive the following error message: Subscription to live feed failed. Please connect to administrator.Error loading shared libraries: libImbCmdLib.soAn error message that states libImbCmdLib.so: cannot open shared object file: No such file or directory can indicate that environment variables are not correct.Errors deploying Cognos BI server artifactsWhile you are deploying the IBM Cognos BI server artifacts, you receive error messages in the master log. This issue can be caused by entering the incorrect value for the IBM Cognos BI dispatcher URI in the Deployment Wizard.Improving performance for IBM Cognos reportsTo improve the performance of IBM Cognos Business Intelligence reports, you can run a cron job that is created by the installation. IBM Integration Bus related nodes are missing after migrationAfter you migrate IBM Predictive Maintenance and Quality, you open MQ Explorer and IBM Integration Bus related nodes are missing.Master Data Management web portal available only in Internet Explorer 9 browsersYou must use Microsoft Internet Explorer version 9 to access the IBM InfoSphere Master Data Management web portal.Error configuring NFS mount settingsYou are configuring network file system (NFS) mounts on the Integration Bus node and the Predictive Analytics node computers to allow file transfers between these nodes. When you restart the Linux services, an error occurs.Initialization error when configuring IBM SPSS Collaboration and Deployment ServicesIn IBM Predictive Maintenance and Quality, if the task for configuring the IBM SPSS Collaboration and Deployment Services displays a database initialization error, run the traceroute command to ensure communication between the Predictive Analytics node and the data node.Error starting IBM HTTP ServerYou receive the following error when you start the IBM HTTP Server: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory.Error executing action run on resource execute[extract_zip]When you start the artifacts solution installer after using it previously to install the artifacts, you get Error executing action run on resource execute[extract_zip].System error when you log in to the Predictive Maintenance and Quality dashboard applicationYou are logging in to the Predictive Maintenance and Quality dashboard application and you receive a system error. This error can occur if data was not loaded into the database.Error Forever Node.js module is not runningYou try to access the Forever log file using the forever list command and receive an error Forever Node.js module is not running.

Troubleshooting

This section contains troubleshooting information for the IBM® Predictive Maintenance and Quality installation.

Progress bar shows null% as value
During the installation, the progress bar in the Run Progress box shows null%.

Installation stops abruptly
During the installation, an error is displayed in the solution installer and the log file appears to have also ended abruptly.

Run Progress box shows more nodes than are in your configuration
The Run Progress box shows the installation progress. It might show more nodes than you are using in your configuration.

JAVA_HOME not set when starting IBM Cognos Configuration
After you install IBM Predictive Maintenance and Quality as a sudo user, you receive a message that the JAVA_HOME environment variable is not set.

CONFIGURATION ERROR:Specified config file /etc/opscode/pivotal.rb does not exist error
You have reinstalled the solution installer after you used the cleanup.sh script, and when you run the solution installer you get an error message like the following:

Solution installer indicates successful completion but progress bars are not complete
During the installation, a message in the solution installer indicates that the installation has completed successfully, but the Run Progress box shows that some installation tasks are not yet complete.

No Server Connection when you view log details from solution installer
While you are running an installation, you click Get Details and you get a No Server Connection page in your web browser. This error can occur if the server is not properly registered in the domain controller or the DHCP server.

Modeler Server type not displaying in resource definitions
In IBM Predictive Maintenance and Quality, if the Modeler Server type does not display in resource definitions in IBM SPSS® Collaboration and Deployment Services Deployment Manager, try closing Deployment Manager and opening it again.

Unable to import the company archive in MDM
If you cannot import the IBM Predictive Maintenance and Quality company archive in the Master Data Management (MDM) console, you can manually import the archive.

Error installing IBM Cognos BI
The IBM Cognos® Business Intelligence installer requires a specific library file in order to run.

Restarting the queue manager and broker
After a IBM Predictive Maintenance and Quality Integration Bus node server restart, you might need to restart the queue manager and broker.

Subscription to live feed failed error in Dashboard
When you subscribe to a dashboard, you receive the following error message: "Subscription to live feed failed. Please connect to administrator."

Error loading shared libraries: libImbCmdLib.so
An error message that states libImbCmdLib.so: cannot open shared object file: No such file or directory can indicate that environment variables are not correct.

Errors deploying Cognos BI server artifacts
While you are deploying the IBM Cognos BI server artifacts, you receive error messages in the master log. This issue can be caused by entering the incorrect value for the IBM Cognos BI dispatcher URI in the Deployment Wizard.

Improving performance for IBM Cognos reports
To improve the performance of IBM Cognos Business Intelligence reports, you can run a cron job that is created by the installation.

IBM Integration Bus related nodes are missing after migration
After you migrate IBM Predictive Maintenance and Quality, you open MQ Explorer and IBM Integration Bus related nodes are missing.

Master Data Management web portal available only in Internet Explorer 9 browsers
You must use Microsoft Internet Explorer version 9 to access the IBM InfoSphere® Master Data Management web portal.

Error configuring NFS mount settings
You are configuring network file system (NFS) mounts on the Integration Bus node and the Predictive Analytics node computers to allow file transfers between these nodes. When you restart the Linux services, an error occurs.

Initialization error when configuring IBM SPSS Collaboration and Deployment Services
In IBM Predictive Maintenance and Quality, if the task for configuring the IBM SPSS Collaboration and Deployment Services displays a database initialization error, run the traceroute command to ensure communication between the Predictive Analytics node and the data node.

Error starting IBM HTTP Server
You receive the following error when you start the IBM HTTP Server: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory.

Error executing action run on resource execute[extract_zip]
When you start the artifacts solution installer after using it previously to install the artifacts, you get "Error executing action run on resource execute[extract_zip]".

System error when you log in to the Predictive Maintenance and Quality dashboard application
You are logging in to the Predictive Maintenance and Quality dashboard application and you receive a system error. This error can occur if data was not loaded into the database.

Error Forever Node.js module is not running
You try to access the Forever log file using the forever list command and receive an error Forever Node.js module is not running.

Progress bar shows null% as valueDuring the installation, the progress bar in the Run Progress box shows null%.A value of null% in the progress bar does not indicate that the installation stopped. Allow the installation to proceed. The correct value is displayed when the installation is complete.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Progress bar shows null% as value

During the installation, the progress bar in the Run Progress box shows null%.

A value of null% in the progress bar does not indicate that the installation stopped. Allow the installation to proceed. The correct value is displayed when the installation is complete.

Parent topic: Troubleshooting

Installation stops abruptlyDuring the installation, an error is displayed in the solution installer and the log file appears to have also ended abruptly.This problem can occur because the underlying Chef server is overloaded with roles and is unable to process any new requests.To resolve this problem, do the following steps:On the computer where you are running the solution installer, go to the <solution_installer_path>/PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Mapper/roles directory.List the files in the directory. For example, enter ls. Note the full name of the db2node#.json file. The # part of the file name is a number.Go to the /root/chef-repo directory.Enter the following command: knife role from file <solution_installer_path>/PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Mapper/roles/db2node#.json Ensure that you use correct # part of the file name. After the command has completed, you should see a message that says: Updated Role db2node#!Go back to the solution installer, and run the installation again.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Installation stops abruptly

During the installation, an error is displayed in the solution installer and the log file appears to have also ended abruptly.

This problem can occur because the underlying Chef server is overloaded with roles and is unable to process any new requests.

To resolve this problem, do the following steps:

On the computer where you are running the solution installer, go to the <solution_installer_path>/PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Mapper/roles directory.

List the files in the directory. For example, enter ls.

Note the full name of the db2node#.json file. The # part of the file name is a number.

Go to the /root/chef-repo directory.

Enter the following command:

knife role from file <solution_installer_path>/PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Mapper/roles/db2node#.json

Ensure that you use correct # part of the file name.

After the command has completed, you should see a message that says:

Updated Role db2node#!

Go back to the solution installer, and run the installation again.

Parent topic: Troubleshooting

Run Progress box shows more nodes than are in your configurationThe Run Progress box shows the installation progress. It might show more nodes than you are using in your configuration.Allow the installation to proceed, and wait to ensure that each of the nodes that are shown in the Run Progress box indicate that the installation is complete.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Run Progress box shows more nodes than are in your configuration

The Run Progress box shows the installation progress. It might show more nodes than you are using in your configuration.

Allow the installation to proceed, and wait to ensure that each of the nodes that are shown in the Run Progress box indicate that the installation is complete.

Parent topic: Troubleshooting

JAVA_HOME not set when starting IBM Cognos ConfigurationAfter you install IBM Predictive Maintenance and Quality as a sudo user, you receive a message that the JAVA_HOME environment variable is not set. You can resolve this be setting the JAVA_HOME environment variable. You must use the JRE that is provided with the WebSphere Application Server installation.On the Business Intelligence (BI) node computer, in terminal window, enter the following command:export JAVA_HOME=/WebSphere_Install_location/AppServer/javaFor example, enter export JAVA_HOME=/opt/IBM/WebSphere/AppServer/javaGo to the /opt/ibm/cognos/c10_64/bin64 directory.Type the following command:./cogconfig.sh IBM Cognos Configuration starts.If you want to save this setting for future session, add the command to the user's .bash_profile file.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

JAVA_HOME not set when starting IBM Cognos Configuration

After you install IBM® Predictive Maintenance and Quality as a sudo user, you receive a message that the JAVA_HOME environment variable is not set.

You can resolve this be setting the JAVA_HOME environment variable. You must use the JRE that is provided with the WebSphere® Application Server installation.

Procedure

On the Business Intelligence (BI) node computer, in terminal window, enter the following command:

export JAVA_HOME=/WebSphere_Install_location/AppServer/java

For example, enter

export JAVA_HOME=/opt/IBM/WebSphere/AppServer/java

Go to the /opt/ibm/cognos/c10_64/bin64 directory.

Type the following command:

./cogconfig.sh

IBM Cognos® Configuration starts.

If you want to save this setting for future session, add the command to the user's .bash_profile file.

Parent topic: Troubleshooting

CONFIGURATION ERROR:Specified config file /etc/opscode/pivotal.rb does not exist errorYou have reinstalled the solution installer after you used the cleanup.sh script, and when you run the solution installer you get an error message like the following: ERROR: CONFIGURATION ERROR:Specified config file /etc/opscode/pivotal.rb does not existCould not find organisation solinst ERROR: CONFIGURATION ERROR:Specified config file /etc/opscode/pivotal.rb does not existCould not find These messages occur because one of the services that is used by the solution installer is still running and a port is still in use. To resolve this error, restart you machine, and then run the setup.sh script again.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

"CONFIGURATION ERROR:Specified config file /etc/opscode/pivotal.rb does not exist" error

You have reinstalled the solution installer after you used the cleanup.sh script, and when you run the solution installer you get an error message like the following:

ERROR: CONFIGURATION ERROR:Specified config file /etc/opscode/pivotal.rb does not existCould not find organisation solinst

ERROR: CONFIGURATION ERROR:Specified config file /etc/opscode/pivotal.rb does not existCould not find

These messages occur because one of the services that is used by the solution installer is still running and a port is still in use.

To resolve this error, restart you machine, and then run the setup.sh script again.

Parent topic: Troubleshooting

Solution installer indicates successful completion but progress bars are not completeDuring the installation, a message in the solution installer indicates that the installation has completed successfully, but the Run Progress box shows that some installation tasks are not yet complete. In this situation, you can check the log file to determine whether the installation is completed or not.On the computer where you are running the solution installer, go to the <solution_installer_path>/PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Logs directory.Enter the following command to view the log file: tail -f LOG_FILE_<timestamp>.logIf messages are still being written to the log file, that means that the installation is still in progress. In this case, you must wait until no further messages are written to the log file.After no further messages are written to the log file, you can continue with installation by testing the products.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Solution installer indicates successful completion but progress bars are not complete

During the installation, a message in the solution installer indicates that the installation has completed successfully, but the Run Progress box shows that some installation tasks are not yet complete.

In this situation, you can check the log file to determine whether the installation is completed or not.

On the computer where you are running the solution installer, go to the <solution_installer_path>/PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Logs directory.

Enter the following command to view the log file:

tail -f LOG_FILE_<timestamp>.log

If messages are still being written to the log file, that means that the installation is still in progress. In this case, you must wait until no further messages are written to the log file.

After no further messages are written to the log file, you can continue with installation by testing the products.

Parent topic: Troubleshooting

No Server Connection when you view log details from solution installerWhile you are running an installation, you click Get Details and you get a No Server Connection page in your web browser. This error can occur if the server is not properly registered in the domain controller or the DHCP server.To get the log file, you can log in to the computer where you are running the solution installer, and go to the <solution_installer_path>/PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Logs directory.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

No Server Connection when you view log details from solution installer

While you are running an installation, you click Get Details and you get a No Server Connection page in your web browser. This error can occur if the server is not properly registered in the domain controller or the DHCP server.

To get the log file, you can log in to the computer where you are running the solution installer, and go to the <solution_installer_path>/PMQ_2.5.2_linux/SolutionInstaller/NodeRoot/Downloads/Logs directory.

Parent topic: Troubleshooting

Modeler Server type not displaying in resource definitionsIn IBM Predictive Maintenance and Quality, if the Modeler Server type does not display in resource definitions in IBM SPSS Collaboration and Deployment Services Deployment Manager, try closing Deployment Manager and opening it again.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Modeler Server type not displaying in resource definitions

In IBM® Predictive Maintenance and Quality, if the Modeler Server type does not display in resource definitions in IBM SPSS® Collaboration and Deployment Services Deployment Manager, try closing Deployment Manager and opening it again.

Parent topic: Troubleshooting

Unable to import the company archive in MDMIf you cannot import the IBM Predictive Maintenance and Quality company archive in the Master Data Management (MDM) console, you can manually import the archive.Log in to the MDM node computer as root.Copy the IBMPMQ.zip file from /opt/IBM/PMQ/MDM_version directory to the /opt/IBM/PMQ directory.Enter the following command:$TOP/bin/importCompanyFromZip.sh --company_code=IBMPMQ --zipfile_path=/opt/IBM/PMQ/IBMPMQ.zipTroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Unable to import the company archive in MDM

If you cannot import the IBM® Predictive Maintenance and Quality company archive in the Master Data Management (MDM) console, you can manually import the archive.

Procedure

Log in to the MDM node computer as root.

Copy the IBMPMQ.zip file from /opt/IBM/PMQ/MDM_version directory to the /opt/IBM/PMQ directory.

Enter the following command:

$TOP/bin/importCompanyFromZip.sh --company_code=IBMPMQ --zipfile_path=/opt/IBM/PMQ/IBMPMQ.zip

Parent topic: Troubleshooting

Error installing IBM Cognos BI The IBM Cognos Business Intelligence installer requires a specific library file in order to run.If you encounter this error installing IBM Predictive Maintenance and Quality, see the IBM support page (http://www.ibm.com/support/docview.wss?uid=swg21612290) for information on how to correct the error.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Error installing IBM Cognos BI

The IBM® Cognos® Business Intelligence installer requires a specific library file in order to run.

If you encounter this error installing IBM Predictive Maintenance and Quality, see the IBM support page (http://www.ibm.com/support/docview.wss?uid=swg21612290) for information on how to correct the error.

Parent topic: Troubleshooting

Restarting the queue manager and brokerAfter a IBM Predictive Maintenance and Quality Integration Bus node server restart, you might need to restart the queue manager and broker.Log on to the Integration Bus node computer.In a terminal window, go to the installation_location/mqsi/9.0.0.2/bin directory.For example, if you installed to the default location, go to the /opt/ibm/mqsi/9.0.0.2/bin directory.Change to the mqm user.For example, su mqm.Enter the following command to load the profile that is needed for the mqm user, and press Enter:. ~/.bash_profileEnter the following command to start the queue manager:strmqm queue_manager_nameFor example, to start the default broker named pmqmanager, enter:strmqm pmqmanagerEnter the following command to start the broker:mqsistart broker_nameFor example, to start the default broker named pmqbroker, enter:mqsistart pmqbrokerTroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Restarting the queue manager and broker

After a IBM® Predictive Maintenance and Quality Integration Bus node server restart, you might need to restart the queue manager and broker.

Procedure

Log on to the Integration Bus node computer.

In a terminal window, go to the installation_location/mqsi/9.0.0.2/bin directory. For example, if you installed to the default location, go to the /opt/ibm/mqsi/9.0.0.2/bin directory.

Change to the mqm user. For example, su mqm.

Enter the following command to load the profile that is needed for the mqm user, and press Enter:

. ~/.bash_profile

Enter the following command to start the queue manager:

strmqm queue_manager_name

For example, to start the default broker named pmqmanager, enter:

strmqm pmqmanager

Enter the following command to start the broker:

mqsistart broker_name

For example, to start the default broker named pmqbroker, enter:

mqsistart pmqbroker

Parent topic: Troubleshooting

Subscription to live feed failed error in DashboardWhen you subscribe to a dashboard, you receive the following error message: Subscription to live feed failed. Please connect to administrator.This issue can occur if the broker on the Integration Bus node computer is not running.For more information about starting services on the Integration Bus node computer, see Starting services on the Integration Bus node computerYou must start the IBM Integration Bus services on the IBM Predictive Maintenance and Quality Integration Bus node computer..TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

"Subscription to live feed failed" error in Dashboard

When you subscribe to a dashboard, you receive the following error message: "Subscription to live feed failed. Please connect to administrator."

This issue can occur if the broker on the Integration Bus node computer is not running.

For more information about starting services on the Integration Bus node computer, see Starting services on the Integration Bus node computer.

Parent topic: Troubleshooting

Error loading shared libraries: libImbCmdLib.soAn error message that states libImbCmdLib.so: cannot open shared object file: No such file or directory can indicate that environment variables are not correct.Verify the environment variables, specifically ones that are related to the IBM Integration Bus broker.Also, ensure that the link inside /opt/ibm/mqsi/9.0.0.2/lib/headless is removed.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Error loading shared libraries: libImbCmdLib.so

An error message that states libImbCmdLib.so: cannot open shared object file: No such file or directory can indicate that environment variables are not correct.

Verify the environment variables, specifically ones that are related to the IBM® Integration Bus broker.

Also, ensure that the link inside /opt/ibm/mqsi/9.0.0.2/lib/headless is removed.

Parent topic: Troubleshooting

Errors deploying Cognos BI server artifactsWhile you are deploying the IBM Cognos BI server artifacts, you receive error messages in the master log. This issue can be caused by entering the incorrect value for the IBM Cognos BI dispatcher URI in the Deployment Wizard.The following error message appears in the master log:[exec] java.net.MalformedURLException: For input string: "<port>" [exec] at java.net.URL.<init>(URL.java:613) [exec] at java.net.URL.<init>(URL.java:476) [exec] at java.net.URL.<init>(URL.java:425) [exec] at Import_Partial_Whole.connectToReportServer (Import_Partial_Whole.java:353) [exec] at Import_Partial_Whole.main(Import_Partial_Whole.java:137) [exec] Exception in thread "main" java.lang.NullPointerException [exec] at Import_Partial_Whole.addArchive(Import_Partial_Whole.java:396) [exec] at Import_Partial_Whole.deployContent(Import_Partial_Whole.java:238) [exec] at Import_Partial_Whole.main(Import_Partial_Whole.java:149)To resolve this problem, you must enter the host name and the port number for the IBM Cognos Dispatcher URI in the Deployment Wizard. For example, http://hostname:port/p2pd/servlet/dispatch.You must enter the correct hostname value and port number. The default port number is 9080.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Errors deploying Cognos BI server artifacts

While you are deploying the IBM® Cognos® BI server artifacts, you receive error messages in the master log. This issue can be caused by entering the incorrect value for the IBM Cognos BI dispatcher URI in the Deployment Wizard.

The following error message appears in the master log:

[exec] java.net.MalformedURLException: For input string: "<port>"
[exec]     at java.net.URL.<init>(URL.java:613)
[exec]     at java.net.URL.<init>(URL.java:476)
[exec]     at java.net.URL.<init>(URL.java:425)
[exec]     at Import_Partial_Whole.connectToReportServer
              (Import_Partial_Whole.java:353)
[exec]     at Import_Partial_Whole.main(Import_Partial_Whole.java:137)
[exec] Exception in thread "main" java.lang.NullPointerException
[exec]     at Import_Partial_Whole.addArchive(Import_Partial_Whole.java:396)
[exec]     at Import_Partial_Whole.deployContent(Import_Partial_Whole.java:238)
[exec]     at Import_Partial_Whole.main(Import_Partial_Whole.java:149)

To resolve this problem, you must enter the host name and the port number for the IBM Cognos Dispatcher URI in the Deployment Wizard. For example, http://hostname:port/p2pd/servlet/dispatch.

You must enter the correct hostname value and port number. The default port number is 9080.

Parent topic: Troubleshooting

Improving performance for IBM Cognos reportsTo improve the performance of IBM Cognos Business Intelligence reports, you can run a cron job that is created by the installation. The cron job is run every hour by default. However, you can modify that interval. The cron job is automatically created on the data node computer, in the /home/db2inst1 directory and is named mycron. If you want to change the interval for running the job, you must update the cron job by using the following command: Vi crontab -eTroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Improving performance for IBM Cognos reports

To improve the performance of IBM® Cognos® Business Intelligence reports, you can run a cron job that is created by the installation.

The cron job is run every hour by default. However, you can modify that interval.

The cron job is automatically created on the data node computer, in the /home/db2inst1 directory and is named mycron.

If you want to change the interval for running the job, you must update the cron job by using the following command:

Vi crontab -e

Parent topic: Troubleshooting

IBM Integration Bus related nodes are missing after migrationAfter you migrate IBM Predictive Maintenance and Quality, you open MQ Explorer and IBM Integration Bus related nodes are missing. You can resolve this issue by forcing the program to reinitialize the MBExplorer plugin.On the Integration Bus node computer, go to the MQExplorer_Installation/eclipse/links directory. For example, go to the /opt/mqm/mqexplorer/eclipse/links directory.Make a copy of com.ibm.wmadmin.broker.explorer.link as a backup. You will copy this file back to this directory later.Delete com.ibm.wmadmin.broker.explorer.link.Go to the /opt/mqm/bin directory.Enter the following command to start MQ Explorer:./strmqcfg -cAfter MQ Explorer is fully loaded, close the program.Go back to the /opt/mqm/mqexplorer/eclipse/links directory.Replace com.ibm.wmadmin.broker.explorer.link from your backup.Go back to the /opt/mqm/bin directory.Restart MQ Explorer using the following command:./strmqcfg -cTroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

IBM Integration Bus related nodes are missing after migration

After you migrate IBM® Predictive Maintenance and Quality, you open MQ Explorer and IBM Integration Bus related nodes are missing.

You can resolve this issue by forcing the program to reinitialize the MBExplorer plugin.

Procedure

On the Integration Bus node computer, go to the MQExplorer_Installation/eclipse/links directory. For example, go to the /opt/mqm/mqexplorer/eclipse/links directory.

Make a copy of com.ibm.wmadmin.broker.explorer.link as a backup. You will copy this file back to this directory later.

Delete com.ibm.wmadmin.broker.explorer.link.

Go to the /opt/mqm/bin directory.

Enter the following command to start MQ Explorer:

./strmqcfg -c

After MQ Explorer is fully loaded, close the program.

Go back to the /opt/mqm/mqexplorer/eclipse/links directory.

Replace com.ibm.wmadmin.broker.explorer.link from your backup.

Go back to the /opt/mqm/bin directory.

Restart MQ Explorer using the following command:

./strmqcfg -c

Parent topic: Troubleshooting

Master Data Management web portal available only in Internet Explorer 9 browsersYou must use Microsoft Internet Explorer version 9 to access the IBM InfoSphere Master Data Management web portal.The URL is http://mdm_node_name:7507/utils/enterLogin.jspTroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Master Data Management web portal available only in Internet Explorer 9 browsers

You must use Microsoft Internet Explorer version 9 to access the IBM® InfoSphere® Master Data Management web portal.

The URL is http://mdm_node_name:7507/utils/enterLogin.jsp

Parent topic: Troubleshooting

Error configuring NFS mount settingsYou are configuring network file system (NFS) mounts on the Integration Bus node and the Predictive Analytics node computers to allow file transfers between these nodes. When you restart the Linux services, an error occurs.You enter the service portmap restart command and receive the following error: portmap: unrecognized serviceTo resolve the problem, restart the operating system and then reissue the command. TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Error configuring NFS mount settings

You are configuring network file system (NFS) mounts on the Integration Bus node and the Predictive Analytics node computers to allow file transfers between these nodes. When you restart the Linux services, an error occurs.

You enter the service portmap restart command and receive the following error:

portmap: unrecognized service

To resolve the problem, restart the operating system and then reissue the command.

Parent topic: Troubleshooting

Initialization error when configuring IBM SPSS Collaboration and Deployment ServicesIn IBM Predictive Maintenance and Quality, if the task for configuring the IBM SPSS Collaboration and Deployment Services displays a database initialization error, run the traceroute command to ensure communication between the Predictive Analytics node and the data node.On the Analytics node computer, enter the following command:traceroute data_node_nameWhere data_node_name is the name or IP address of the data node computer.Try the task again.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Initialization error when configuring IBM SPSS Collaboration and Deployment Services

In IBM® Predictive Maintenance and Quality, if the task for configuring the IBM SPSS® Collaboration and Deployment Services displays a database initialization error, run the traceroute command to ensure communication between the Predictive Analytics node and the data node.

Procedure

On the Analytics node computer, enter the following command:

traceroute data_node_name

Where data_node_name is the name or IP address of the data node computer.

Try the task again.

Parent topic: Troubleshooting

Error starting IBM HTTP ServerThis topic added to resolve defect 27537.You receive the following error when you start the IBM HTTP Server: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory.The problem might be because you are trying to start IBM HTTP Server outside of a WebSphere Application Server environment in which required libraries are not found. To resolve the problem, see Troubleshooting IBM HTTP Server startup (www.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_troubleshooting_ihs_startup.html).TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Error starting IBM HTTP Server

You receive the following error when you start the IBM® HTTP Server: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory.

The problem might be because you are trying to start IBM HTTP Server outside of a WebSphere Application Server environment in which required libraries are not found. To resolve the problem, see Troubleshooting IBM HTTP Server startup (www.ibm.com/support/knowledgecenter/SSZH4A_6.2.0/com.ibm.worklight.installconfig.doc/admin/t_troubleshooting_ihs_startup.html).

Parent topic: Troubleshooting

Error executing action run on resource execute[extract_zip]When you start the artifacts solution installer after using it previously to install the artifacts, you get Error executing action run on resource execute[extract_zip].On each node where you have installed artifacts, delete the directory that contains the artifacts. For example, on the data node computer, delete the /opt/IBM/PMQ/Data directory.Open the artifacts solution installer in a web browser.Click Run.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Error executing action run on resource execute[extract_zip]

When you start the artifacts solution installer after using it previously to install the artifacts, you get "Error executing action run on resource execute[extract_zip]".

Procedure

On each node where you have installed artifacts, delete the directory that contains the artifacts. For example, on the data node computer, delete the /opt/IBM/PMQ/Data directory.

Open the artifacts solution installer in a web browser.

Click Run.

Parent topic: Troubleshooting

System error when you log in to the Predictive Maintenance and Quality dashboard application You are logging in to the Predictive Maintenance and Quality dashboard application and you receive a system error. This error can occur if data was not loaded into the database.To resolve this error, load the Predictive Maintenance and Quality sample data into the database. For more information, see SamplesSample data is provided so that you can see the IBM Predictive Maintenance and Quality solution work end-to-end..After the data is loaded, you can access the Predictive Maintenance and Quality dashboard application.TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

System error when you log in to the Predictive Maintenance and Quality dashboard application

You are logging in to the Predictive Maintenance and Quality dashboard application and you receive a system error. This error can occur if data was not loaded into the database.

To resolve this error, load the Predictive Maintenance and Quality sample data into the database. For more information, see Samples.

After the data is loaded, you can access the Predictive Maintenance and Quality dashboard application.

Parent topic: Troubleshooting

Error Forever Node.js module is not runningThis topic created for RTC task 27628 and 27569.You try to access the Forever log file using the forever list command and receive an error Forever Node.js module is not running.Perform this task to install the Forever module so that you can access the Forever log file.On the computer that contains the solution installer, make sure the Forever module is not installed. Open a terminal window and enter the following command: npm uninstall forever -gInstall the Forever module. Go to the /SolutionInstaller/NodeJS/ directory and enter the following command: npm install forever-0.14.1.tgz -gThe Forever module is installed and starts. You can now access the Forever log file. TroubleshootingThis section contains troubleshooting information for the IBM Predictive Maintenance and Quality installation.

Error Forever Node.js module is not running

You try to access the Forever log file using the forever list command and receive an error Forever Node.js module is not running.

About this task

Perform this task to install the Forever module so that you can access the Forever log file.

Procedure

On the computer that contains the solution installer, make sure the Forever module is not installed. Open a terminal window and enter the following command: npm uninstall forever -g

Install the Forever module. Go to the /SolutionInstaller/NodeJS/ directory and enter the following command: npm install forever-0.14.1.tgz -g The Forever module is installed and starts.

Results

You can now access the Forever log file.

Parent topic: Troubleshooting

SamplesSample data is provided so that you can see the IBM Predictive Maintenance and Quality solution work end-to-end.Loading the sample dataSample data is installed as part of the IBM Predictive Maintenance and Quality server artifact installation. You can load the sample data to see an example of the Predictive Maintenance and Quality solution from end-to-end.Loading the ENU sample dataENU Sample data is installed as part of the IBM Predictive Maintenance and Quality server artifact installation. The data covers examples for substations, distribution transformers, and poles and cables.Modify master data references for blank entriesSome master data, which is not mandatory from a business aspect, are required due to foreign key relationships within the IBM Predictive Maintenance and Quality data model. To overcome this, Predictive Maintenance and Quality uses the concept of an NA (not applicable) master data row entry. As a result, whenever such master data references have a blank value, Predictive Maintenance and Quality uses the -NA- business key code row reference. You must configure the master data tables that require the -NA- entries.Verifying that the sample data was loaded correctlyYou can verify that the IBM Predictive Maintenance and Quality sample data was loaded by checking the error and log directories and viewing reports.Removing sample data from the databaseBefore you load live production data in IBM Predictive Maintenance and Quality, all sample data must be removed from the database.

Samples

Sample data is provided so that you can see the IBM® Predictive Maintenance and Quality solution work end-to-end.

Loading the sample data
Sample data is installed as part of the IBM Predictive Maintenance and Quality server artifact installation. You can load the sample data to see an example of the Predictive Maintenance and Quality solution from end-to-end.

Loading the ENU sample data
ENU Sample data is installed as part of the IBM Predictive Maintenance and Quality server artifact installation. The data covers examples for substations, distribution transformers, and poles and cables.

Modify master data references for blank entries
Some master data, which is not mandatory from a business aspect, are required due to foreign key relationships within the IBM Predictive Maintenance and Quality data model. To overcome this, Predictive Maintenance and Quality uses the concept of an NA (not applicable) master data row entry. As a result, whenever such master data references have a blank value, Predictive Maintenance and Quality uses the -NA- business key code row reference. You must configure the master data tables that require the -NA- entries.

Verifying that the sample data was loaded correctly
You can verify that the IBM Predictive Maintenance and Quality sample data was loaded by checking the error and log directories and viewing reports.

Removing sample data from the database
Before you load live production data in IBM Predictive Maintenance and Quality, all sample data must be removed from the database.

Loading the sample dataSample data is installed as part of the IBM Predictive Maintenance and Quality server artifact installation. You can load the sample data to see an example of the Predictive Maintenance and Quality solution from end-to-end.The sample data is provided in different languages. If you want to change the language of the data, you must ensure that the Predictive Maintenance and Quality data store content is deleted, and that you restart your brokers. You can verify that the data was loaded by using commands to check the Predictive Maintenance and Quality queues. You can check the queues by running the following commands: runmqsc pmqmanager Display q(PMQ.*) WHERE(CURDEPTH NE 0)Log in to the Integration Bus node computer as the mqm user.The user must be the mqm user or a member of the mqm group. If you copy the files as another user, they might not be processed by the Integration Bus node components.Load the master data.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set1-MasterData/<language>/Set1/ directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/masterdatain directory one file at a time.WebSphere Message Broker automatically loads the files from that directory. The files are automatically removed after they are loaded.The files must be copied one at a time.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set1-MasterData/<language>/Set2/ directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/masterdatain directory one file at a time.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set1-MasterData/<language>/Set3/ directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/masterdatain directory one file at a time.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set1-MasterData/<language>/Set4/ directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/masterdatain directory one file at a time.Load the event data.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set2-EventData directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set3-EventData directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.Set the appropriate time triggers in the PMQ_orchestration_definition_batch.xml file.Go to the /var/PMQ/MQSIFileInput/properties directory.Open PMQ_orchestration_definition_batch.xml in a text editor.Locate each of the following sections, and set the <scheduled_time> value to an appropriate time.Predictive Maintenance and Quality feature and identifier valueFeature<Identifer> valueTopNFailureTopNMaintenanceMaintenanceSensor Analytics TrainingHSTriggerFeature Based Analytics TrainingFHSTriggerIntegrated Analytics TrainingIHSTriggerUse the following command to stop AutoTrigger.msgflow in the PMQBatchIntegration application:mqsistopmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTriggerUse the following command to restart AutoTrigger.msgflow in the PMQBatchIntegration application:mqsistartmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTriggerLoad the event data for scoring.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set4-EventData directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.Load the batch data for Inspection, Warranty, and Parametric.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Sample_PMQ/language/Set5-BatchData directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/batchdatain directory one file at a time.SamplesSample data is provided so that you can see the IBM Predictive Maintenance and Quality solution work end-to-end.

Loading the sample data

Sample data is installed as part of the IBM® Predictive Maintenance and Quality server artifact installation. You can load the sample data to see an example of the Predictive Maintenance and Quality solution from end-to-end.

The sample data is provided in different languages. If you want to change the language of the data, you must ensure that the Predictive Maintenance and Quality data store content is deleted, and that you restart your brokers.

Tip: You can verify that the data was loaded by using commands to check the Predictive Maintenance and Quality queues. You can check the queues by running the following commands:

runmqsc pmqmanager
Display q(PMQ.*) WHERE(CURDEPTH NE 0)

Procedure

Log in to the Integration Bus node computer as the mqm user.

Important: The user must be the mqm user or a member of the mqm group. If you copy the files as another user, they might not be processed by the Integration Bus node components.

Load the master data.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set1-MasterData/<language>/Set1/ directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/masterdatain directory one file at a time.

WebSphere® Message Broker automatically loads the files from that directory. The files are automatically removed after they are loaded.

Important: The files must be copied one at a time.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set1-MasterData/<language>/Set2/ directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/masterdatain directory one file at a time.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set1-MasterData/<language>/Set3/ directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/masterdatain directory one file at a time.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set1-MasterData/<language>/Set4/ directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/masterdatain directory one file at a time.

Load the event data.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set2-EventData directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set3-EventData directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.

Set the appropriate time triggers in the PMQ_orchestration_definition_batch.xml file.

Go to the /var/PMQ/MQSIFileInput/properties directory.

Open PMQ_orchestration_definition_batch.xml in a text editor.

Locate each of the following sections, and set the <scheduled_time> value to an appropriate time.

Table 14. Predictive Maintenance and Quality feature and identifier value

Feature
<Identifer> value

TopNFailure
TopN

Maintenance
Maintenance

Sensor Analytics Training
HSTrigger

Feature Based Analytics Training

FHSTrigger

Integrated Analytics Training

IHSTrigger

Use the following command to stop AutoTrigger.msgflow in the PMQBatchIntegration application:

mqsistopmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

Use the following command to restart AutoTrigger.msgflow in the PMQBatchIntegration application:

mqsistartmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

Load the event data for scoring.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set4-EventData directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.

Load the batch data for Inspection, Warranty, and Parametric.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Sample_PMQ/language/Set5-BatchData directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/batchdatain directory one file at a time.

Parent topic: Samples

Loading the ENU sample dataENU Sample data is installed as part of the IBM Predictive Maintenance and Quality server artifact installation. The data covers examples for substations, distribution transformers, and poles and cables. The sample data is provided in different languages. If you want to change the language of the data, you must ensure that the Predictive Maintenance and Quality data store content is deleted, and that you restart your brokers. You can verify that the data was loaded by using commands to check the Predictive Maintenance and Quality queues. You can check the queues by running the following commands: runmqsc pmqmanager Display q(PMQ.*) WHERE(CURDEPTH NE 0)Log in to the Integration Bus node computer as the mqm user.The user must be the mqm user or a member of the mqm group. If you copy the files as another user, they might not be processed by the Integration Bus node components.Load the data.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set6-EventData_ENU directory.Copy the following files, in sequence, to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.event_observation_parameter*.csv—Loads parameter data.event_observation_*_training.csv—Loads training data.event_observation_pole_inspection.csv—Loads pole data.Set the appropriate time triggers in the PMQ_orchestration_definition_batch.xml file.Go to the /var/PMQ/MQSIFileInput/properties directory.Open PMQ_orchestration_definition_batch.xml in a text editor.Locate each of the following sections, and set the <scheduled_time> value to an appropriate time.Predictive Maintenance and Quality feature and identifier valueFeature<Identifer> valueDistribution transformer Current ageingDTCADistribution transformer Projected ageingDTPAFeature Based Analytics TrainingFHSTriggerIntegrated Analytics TrainingIHSTriggerFeature Based Analytics for PolesPOLEFBAUse the following command to stop AutoTrigger.msgflow in the PMQBatchIntegration application:mqsistopmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTriggerUse the following command to restart AutoTrigger.msgflow in the PMQBatchIntegration application:mqsistartmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTriggerLoad the event data for scoring.Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set6-EventData_ENU directory.Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.For example, copy event_observation_feature_*_scoring.csv.Reset the time triggers in the PMQ_orchestration_definition_batch.xml file.Go to the /var/PMQ/MQSIFileInput directory.Open PMQ_orchestration_definition_batch.xml in a text editor.Locate each of the following sections, and set the <sequence_time> value to an appropriate time.Predictive Maintenance and Quality feature and identifier valueFeature<Identifer> valueDistribution transformer Current agingDTCADistribution transformer Projected agingDTPA If you are resetting the scheduler of any batch feature that is set to run for a duration_in_days that is greater than 1 day, then you must restart AutoTrigger.msgflow in the PMQBatchIntegration application to see the changes immediately.Use the following command to stop AutoTrigger.msgflow in the PMQBatchIntegration application:mqsistopmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTriggerUse the following command to restart AutoTrigger.msgflow in the PMQBatchIntegration application:mqsistartmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTriggerSamplesSample data is provided so that you can see the IBM Predictive Maintenance and Quality solution work end-to-end.

Loading the ENU sample data

ENU Sample data is installed as part of the IBM® Predictive Maintenance and Quality server artifact installation. The data covers examples for substations, distribution transformers, and poles and cables.

The sample data is provided in different languages. If you want to change the language of the data, you must ensure that the Predictive Maintenance and Quality data store content is deleted, and that you restart your brokers.

Tip: You can verify that the data was loaded by using commands to check the Predictive Maintenance and Quality queues. You can check the queues by running the following commands:

runmqsc pmqmanager
Display q(PMQ.*) WHERE(CURDEPTH NE 0)

Procedure

Log in to the Integration Bus node computer as the mqm user.

Important: The user must be the mqm user or a member of the mqm group. If you copy the files as another user, they might not be processed by the Integration Bus node components.

Load the data.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set6-EventData_ENU directory.

Copy the following files, in sequence, to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time.

event_observation_parameter*.csv—Loads parameter data.

event_observation_*_training.csv—Loads training data.

event_observation_pole_inspection.csv—Loads pole data.

Set the appropriate time triggers in the PMQ_orchestration_definition_batch.xml file.

Go to the /var/PMQ/MQSIFileInput/properties directory.

Open PMQ_orchestration_definition_batch.xml in a text editor.

Locate each of the following sections, and set the <scheduled_time> value to an appropriate time.

Table 15. Predictive Maintenance and Quality feature and identifier value

Feature
<Identifer> value

Distribution transformer Current ageing
DTCA

Distribution transformer Projected ageing
DTPA

Feature Based Analytics Training

FHSTrigger

Integrated Analytics Training
IHSTrigger

Feature Based Analytics for Poles
POLEFBA

Use the following command to stop AutoTrigger.msgflow in the PMQBatchIntegration application:

mqsistopmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

Use the following command to restart AutoTrigger.msgflow in the PMQBatchIntegration application:

mqsistartmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

Load the event data for scoring.

Go to the /var/PMQ/MQSIFileInput/PMQSampleData/Set6-EventData_ENU directory.

Copy the contents of that directory to the /var/PMQ/MQSIFileInput/eventdatain directory one file at a time. For example, copy event_observation_feature_*_scoring.csv.

Reset the time triggers in the PMQ_orchestration_definition_batch.xml file.

Go to the /var/PMQ/MQSIFileInput directory.

Open PMQ_orchestration_definition_batch.xml in a text editor.

Locate each of the following sections, and set the <sequence_time> value to an appropriate time.

Table 16. Predictive Maintenance and Quality feature and identifier value

Feature
<Identifer> value

Distribution transformer Current aging

DTCA

Distribution transformer Projected aging

DTPA

Note: If you are resetting the scheduler of any batch feature that is set to run for a duration_in_days that is greater than 1 day, then you must restart AutoTrigger.msgflow in the PMQBatchIntegration application to see the changes immediately.

Use the following command to stop AutoTrigger.msgflow in the PMQBatchIntegration application:

mqsistopmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

Use the following command to restart AutoTrigger.msgflow in the PMQBatchIntegration application:

mqsistartmsgflow pmqbroker -e pmqgroup1 -k PMQBatchIntegration -m AutoTrigger

Parent topic: Samples

Modify master data references for blank entriesSome master data, which is not mandatory from a business aspect, are required due to foreign key relationships within the IBM Predictive Maintenance and Quality data model. To overcome this, Predictive Maintenance and Quality uses the concept of an NA (not applicable) master data row entry. As a result, whenever such master data references have a blank value, Predictive Maintenance and Quality uses the -NA- business key code row reference. You must configure the master data tables that require the -NA- entries.The following table provides the table names that require the -NA- entries and samples master data files that you can use to reference which tables require the entries.Tables that require -NA- entries, and sample files you can referenceTable nameSample master data fileMASTER_GROUP_DIMgroup_dim_upsert.csvMASTER_LOCATIONlocation_upsert.csvMASTER_MATERIAL_TYPEmaterial_type_upsert.csvMASTER_PROCESSprocess_upsert.csvMASTER_PRODUCTproduct_upsert.csvMASTER_SOURCE_SYSTEMsource_system_upsert.csvMASTER_SUPPLIERsupplier_upsert.csvMASTER_MATERIALmaterial_upsert.csvMASTER_PRODUCTION_BATCHproduction_batch_upsert.csvMASTER_RESOURCEresource_upsert.csvSamplesSample data is provided so that you can see the IBM Predictive Maintenance and Quality solution work end-to-end.

Modify master data references for blank entries

Some master data, which is not mandatory from a business aspect, are required due to foreign key relationships within the IBM® Predictive Maintenance and Quality data model. To overcome this, Predictive Maintenance and Quality uses the concept of an NA (not applicable) master data row entry. As a result, whenever such master data references have a blank value, Predictive Maintenance and Quality uses the -NA- business key code row reference. You must configure the master data tables that require the -NA- entries.

The following table provides the table names that require the -NA- entries and samples master data files that you can use to reference which tables require the entries.

Table 17. Tables that require -NA- entries, and sample files you can reference

Table name | Sample master data file
MASTER_GROUP_DIM | group_dim_upsert.csv
MASTER_LOCATION | location_upsert.csv
MASTER_MATERIAL_TYPE | material_type_upsert.csv
MASTER_PROCESS | process_upsert.csv
MASTER_PRODUCT | product_upsert.csv
MASTER_SOURCE_SYSTEM | source_system_upsert.csv
MASTER_SUPPLIER | supplier_upsert.csv
MASTER_MATERIAL | material_upsert.csv
MASTER_PRODUCTION_BATCH | production_batch_upsert.csv
MASTER_RESOURCE | resource_upsert.csv

Parent topic: Samples

Verifying that the sample data was loaded correctlyYou can verify that the IBM Predictive Maintenance and Quality sample data was loaded by checking the error and log directories and viewing reports.Check the error directory on the Integration Bus node computer to ensure that there were no errors when the data was loaded.Check the status of the IBM SPSS jobs by reviewing the following files in the Integration Bus node log directory of the ESB node: TopNFailureLog.txtMaintenanceLog.txtTraining_HS_in.csvTraining_FBA_in.csvTraining_IHS_in.csv If the sample data was loaded correctly, then the previously listed files are not created.The following reports are populated with the sample data:Sample data and reportsDataReport or dashboardMaster dataAudit ReportsResourceSite Overview dashboard Equipment dashboard Advance KPI Trend reportsProcess and materialProduct Quality dashboard and Material Usage by Production batch reportSPCSPC - Histogram SPC - X bar R/S chartQEWSQEWS Inspection QEWSL WarrantyMaintenance, sensor health score, and integrated health scoreMaintenance Overview dashboard Maintenance Health and Failure Detail report Maintenance Advance Sorting reportTopNFailureTop N Failure Analysis reportIf you are using the ENU sample data, check the status of the SPSS jobs by reviewing the following log files:dt_currentageing_in.csvdt_projectedageing_in.csvSamplesSample data is provided so that you can see the IBM Predictive Maintenance and Quality solution work end-to-end.

Verifying that the sample data was loaded correctly

You can verify that the IBM® Predictive Maintenance and Quality sample data was loaded by checking the error and log directories and viewing reports.

Procedure

Check the error directory on the Integration Bus node computer to ensure that there were no errors when the data was loaded.

Check the status of the IBM SPSS jobs by reviewing the following files in the Integration Bus node log directory of the ESB node:

TopNFailureLog.txt

MaintenanceLog.txt

Training_HS_in.csv

Training_FBA_in.csv

Training_IHS_in.csv

Note: If the sample data was loaded correctly, then the previously listed files are not created.

The following reports are populated with the sample data:

Table 18. Sample data and reports

Data
Report or dashboard

Master data

Audit Reports

Resource

Site Overview dashboard

Equipment dashboard

Advance KPI Trend reports

Process and material

Product Quality dashboard and

Material Usage by Production batch report

SPC

SPC - Histogram

SPC - X bar R/S chart

QEWS

QEWS Inspection

QEWSL Warranty

Maintenance, sensor health score, and integrated health score

Maintenance Overview dashboard

Maintenance Health and Failure Detail report

Maintenance Advance Sorting report

TopNFailure

Top N Failure Analysis report

If you are using the ENU sample data, check the status of the SPSS jobs by reviewing the following log files:

dt_currentageing_in.csv

dt_projectedageing_in.csv

Parent topic: Samples

Removing sample data from the databaseBefore you load live production data in IBM Predictive Maintenance and Quality, all sample data must be removed from the database. This procedure deletes all the contents of the event and master data tables. Its scope is not limited to the supplied sample data and so any additional content that is loaded is also deleted. If test events were loaded from the sample master data, the test events must also be removed. For more information, see the IBM Predictive Maintenance and Quality Solution Guide.Do one of the following steps to connect to the IBMPMQ database: If the IBMPMQ database is in IBM DB2, type the following command:db2 connect to IBMPMQ user user_name using passwordIf the IBMPMQ database is in Oracle Database, then connect to it using the appropriate Oracle command. To remove the sample data from an IBM DB2 database, do the following steps: Enter the following SQL statements to remove the sample data:DELETE FROM PMQSCH.PARAMETRIC_KPI; DELETE FROM PMQSCH.PARAMETRIC_PROFILE; DELETE PMQSCH.LIFETIME_KPI; DELETE PMQSCH.LIFETIME_PROFILE; DELETE PMQSCH.PRODUCT_PROFILE; DELETE PMQSCH.PRODUCT_KPI; DELETE PMQSCH.RESOURCE_PROFILE; DELETE PMQSCH.RESOURCE_KPI; DELETE PMQSCH.MATERIAL_PROFILE; DELETE PMQSCH.PROCESS_KPI; DELETE PMQSCH.PROCESS_PROFILE; DELETE PMQSCH.PROFILE_PARAMETER; DELETE FROM PMQSCH.EVENT_PROFILE; DELETE PMQSCH.EVENT_OBSERVATION; DELETE PMQSCH.EVENT; DELETE PMQSCH.MASTER_RESOURCE_CONNECTION; DELETE PMQSCH.MASTER_PROFILE_MAPPING; DELETE PMQSCH.MASTER_RESOURCE_PRODUCTION_BATCH; DELETE PMQSCH.MASTER_PRODUCTION_BATCH; DELETE PMQSCH.SERVICE; DELETE PMQSCH.MASTER_PRODUCT_HIERARCHY; DELETE PMQSCH.MASTER_PRODUCT; DELETE PMQSCH.MASTER_RESOURCE_HIERARCHY; DELETE PMQSCH.MASTER_RESOURCE; DELETE PMQSCH.MASTER_PROFILE_VARIABLE; DELETE PMQSCH.MASTER_MATERIAL; DELETE PMQSCH.MASTER_MATERIAL_TYPE; DELETE PMQSCH.MASTER_PROFILE_CALCULATION; DELETE PMQSCH.MASTER_RESOURCE_TYPE; DELETE PMQSCH.MASTER_MEASUREMENT_TYPE; DELETE PMQSCH.MASTER_VALUE_TYPE; DELETE PMQSCH.MASTER_SUPPLIER; DELETE PMQSCH.MASTER_SOURCE_SYSTEM; DELETE PMQSCH.MASTER_PROCESS_HIERARCHY; DELETE PMQSCH.MASTER_PROCESS; DELETE PMQSCH.MASTER_LOCATION; DELETE PMQSCH.MASTER_GROUP_DIM; DELETE PMQSCH.MASTER_EVENT_TYPE; DELETE PMQSCH.MASTER_EVENT_CODE; DELETE PMQSCH.MASTER_OBSERVATION_LOOKUP; DELETE PMQSCH.MAINTENANCE_TRENDS; DELETE PMQSCH.MAINTENANCE_DAILY; DELETE PMQSCH.MAINTENANCE_ADM_RECOMMENDATIONS; DELETE PMQSCH.TOPN_PREDICTORS; DELETE PMQSCH.KEY_LOOKUP; DELETE PMQSCH.LANGUAGE; DELETE PMQSCH.TENANT; DELETE PMQSCH.PMQ_USER; DELETE PMQSCH.PMQ_CHART_CONFIG;Enter the following SQL statements to alter tables:ALTER TABLE PMQSCH .EVENT ALTER COLUMN EVENT_ID RESTART WITH 1; ALTER TABLE PMQSCH .LANGUAGE ALTER COLUMN LANGUAGE_ID RESTART WITH 1; ALTER TABLE PMQSCH .TENANT ALTER COLUMN TENANT_ID RESTART WITH 1; ALTER TABLE PMQSCH .KEY_LOOKUP ALTER COLUMN KEY_LOOKUP_ID RESTART WITH 1; ALTER TABLE PMQSCH .MASTER_PROFILE_CALCULATION ALTER COLUMN MASTER_PROFILE_CALCULATION_ID RESTART WITH 1;To remove the sample data from Oracle Database, do the following steps: Enter the following SQL statements to remove the sample data:DELETE FROM PMQSCH.PARAMETRIC_KPI; DELETE FROM PMQSCH.PARAMETRIC_PROFILE; DELETE PMQSCH.LIFETIME_KPI; DELETE PMQSCH.LIFETIME_PROFILE; DELETE PMQSCH.PRODUCT_PROFILE; DELETE PMQSCH.PRODUCT_KPI; DELETE PMQSCH.RESOURCE_PROFILE; DELETE PMQSCH.RESOURCE_KPI; DELETE PMQSCH.MATERIAL_PROFILE; DELETE PMQSCH.PROCESS_KPI; DELETE PMQSCH.PROCESS_PROFILE; DELETE PMQSCH.PROFILE_PARAMETER; DELETE FROM PMQSCH.EVENT_PROFILE; DELETE PMQSCH.EVENT_OBSERVATION; DELETE PMQSCH.EVENT; DELETE PMQSCH.MASTER_RESOURCE_CONNECTION; DELETE PMQSCH.MASTER_PROFILE_MAPPING; DELETE PMQSCH.MASTER_RESOURCE_PRODBATCH; DELETE PMQSCH.MASTER_PRODUCTION_BATCH; DELETE PMQSCH.SERVICE; DELETE PMQSCH.MASTER_PRODUCT_HIERARCHY; DELETE PMQSCH.MASTER_PRODUCT; DELETE PMQSCH.MASTER_RESOURCE_HIERARCHY; DELETE PMQSCH.MASTER_RESOURCE; DELETE PMQSCH.MASTER_PROFILE_VARIABLE; DELETE PMQSCH.MASTER_MATERIAL; DELETE PMQSCH.MASTER_MATERIAL_TYPE; DELETE PMQSCH.MASTER_PROFILE_CALCULATION; DELETE PMQSCH.MASTER_RESOURCE_TYPE; DELETE PMQSCH.MASTER_MEASUREMENT_TYPE; DELETE PMQSCH.MASTER_VALUE_TYPE; DELETE PMQSCH.MASTER_SUPPLIER; DELETE PMQSCH.MASTER_SOURCE_SYSTEM; DELETE PMQSCH.MASTER_PROCESS_HIERARCHY; DELETE PMQSCH.MASTER_PROCESS; DELETE PMQSCH.MASTER_LOCATION; DELETE PMQSCH.MASTER_GROUP_DIM; DELETE PMQSCH.MASTER_EVENT_TYPE; DELETE PMQSCH.MASTER_EVENT_CODE; DELETE PMQSCH.MASTER_OBSERVATION_LOOKUP; DELETE PMQSCH.MAINTENANCE_TRENDS; DELETE PMQSCH.MAINTENANCE_DAILY; DELETE PMQSCH.MAINT_ADM_RECOMMENDATIONS; DELETE PMQSCH.TOPN_PREDICTORS; DELETE PMQSCH.KEY_LOOKUP; DELETE PMQSCH.LANGUAGE; DELETE PMQSCH.TENANT; DELETE PMQSCH.PMQ_USER; DELETE PMQSCH.PMQ_CHART_CONFIG;Enter the following SQL statements to alter tables:ALTER TABLE PMQSCH .EVENT ALTER COLUMN EVENT_ID RESTART WITH 1; ALTER TABLE PMQSCH .LANGUAGE ALTER COLUMN LANGUAGE_ID RESTART WITH 1; ALTER TABLE PMQSCH .TENANT ALTER COLUMN TENANT_ID RESTART WITH 1; ALTER TABLE PMQSCH .KEY_LOOKUP ALTER COLUMN KEY_LOOKUP_ID RESTART WITH 1; ALTER TABLE PMQSCH .MASTER_PROFILE_CALCULATION ALTER COLUMN MASTER_PROFILE_CALCULATION_ID RESTART WITH 1;Do one of the following steps to disconnect from the IBMPMQ database: If the IBMPMQ database is in IBM DB2, type the following command:db2 connect resetIf the IBMPMQ database is in Oracle Database, then disconnect from it using the appropriate command. Restart the pmqgroup1 integration server (in previous versions, called an execution group).For more information, see the IBM Integration Bus documentation.SamplesSample data is provided so that you can see the IBM Predictive Maintenance and Quality solution work end-to-end.

Removing sample data from the database

Before you load live production data in IBM® Predictive Maintenance and Quality, all sample data must be removed from the database.

This procedure deletes all the contents of the event and master data tables. Its scope is not limited to the supplied sample data and so any additional content that is loaded is also deleted.

Before you begin

If test events were loaded from the sample master data, the test events must also be removed. For more information, see the IBM Predictive Maintenance and Quality Solution Guide.

Procedure

Do one of the following steps to connect to the IBMPMQ database:

If the IBMPMQ database is in IBM DB2, type the following command:

db2 connect to IBMPMQ user user_name using password

If the IBMPMQ database is in Oracle Database, then connect to it using the appropriate Oracle command.

To remove the sample data from an IBM DB2 database, do the following steps:

Enter the following SQL statements to remove the sample data:

DELETE FROM PMQSCH.PARAMETRIC_KPI;
DELETE FROM PMQSCH.PARAMETRIC_PROFILE;
DELETE PMQSCH.LIFETIME_KPI;
DELETE PMQSCH.LIFETIME_PROFILE;
DELETE PMQSCH.PRODUCT_PROFILE;
DELETE PMQSCH.PRODUCT_KPI;
DELETE PMQSCH.RESOURCE_PROFILE;
DELETE PMQSCH.RESOURCE_KPI;
DELETE PMQSCH.MATERIAL_PROFILE;
DELETE PMQSCH.PROCESS_KPI;
DELETE PMQSCH.PROCESS_PROFILE;
DELETE PMQSCH.PROFILE_PARAMETER;
DELETE FROM PMQSCH.EVENT_PROFILE;
DELETE PMQSCH.EVENT_OBSERVATION;
DELETE PMQSCH.EVENT;
DELETE PMQSCH.MASTER_RESOURCE_CONNECTION;
DELETE PMQSCH.MASTER_PROFILE_MAPPING;
DELETE PMQSCH.MASTER_RESOURCE_PRODUCTION_BATCH;
DELETE PMQSCH.MASTER_PRODUCTION_BATCH;
DELETE PMQSCH.SERVICE;
DELETE PMQSCH.MASTER_PRODUCT_HIERARCHY;
DELETE PMQSCH.MASTER_PRODUCT;
DELETE PMQSCH.MASTER_RESOURCE_HIERARCHY;
DELETE PMQSCH.MASTER_RESOURCE;
DELETE PMQSCH.MASTER_PROFILE_VARIABLE;
DELETE PMQSCH.MASTER_MATERIAL;
DELETE PMQSCH.MASTER_MATERIAL_TYPE;
DELETE PMQSCH.MASTER_PROFILE_CALCULATION;
DELETE PMQSCH.MASTER_RESOURCE_TYPE;
DELETE PMQSCH.MASTER_MEASUREMENT_TYPE;
DELETE PMQSCH.MASTER_VALUE_TYPE;
DELETE PMQSCH.MASTER_SUPPLIER;
DELETE PMQSCH.MASTER_SOURCE_SYSTEM;
DELETE PMQSCH.MASTER_PROCESS_HIERARCHY;
DELETE PMQSCH.MASTER_PROCESS;
DELETE PMQSCH.MASTER_LOCATION;
DELETE PMQSCH.MASTER_GROUP_DIM;
DELETE PMQSCH.MASTER_EVENT_TYPE;
DELETE PMQSCH.MASTER_EVENT_CODE;
DELETE PMQSCH.MASTER_OBSERVATION_LOOKUP;
DELETE PMQSCH.MAINTENANCE_TRENDS;
DELETE PMQSCH.MAINTENANCE_DAILY;
DELETE PMQSCH.MAINTENANCE_ADM_RECOMMENDATIONS;
DELETE PMQSCH.TOPN_PREDICTORS;
DELETE PMQSCH.KEY_LOOKUP;
DELETE PMQSCH.LANGUAGE;
DELETE PMQSCH.TENANT;
DELETE PMQSCH.PMQ_USER;
DELETE PMQSCH.PMQ_CHART_CONFIG;

Enter the following SQL statements to alter tables:

ALTER TABLE "PMQSCH "."EVENT" ALTER COLUMN "EVENT_ID" RESTART WITH 1;
ALTER TABLE "PMQSCH "."LANGUAGE" ALTER COLUMN "LANGUAGE_ID" RESTART WITH 1;
ALTER TABLE "PMQSCH "."TENANT" ALTER COLUMN "TENANT_ID" RESTART WITH 1;
ALTER TABLE "PMQSCH "."KEY_LOOKUP" ALTER COLUMN "KEY_LOOKUP_ID" RESTART WITH 1;
ALTER TABLE "PMQSCH "."MASTER_PROFILE_CALCULATION" ALTER COLUMN
"MASTER_PROFILE_CALCULATION_ID" RESTART WITH 1;

To remove the sample data from Oracle Database, do the following steps:

Enter the following SQL statements to remove the sample data:

DELETE FROM PMQSCH.PARAMETRIC_KPI;
DELETE FROM PMQSCH.PARAMETRIC_PROFILE;
DELETE PMQSCH.LIFETIME_KPI;
DELETE PMQSCH.LIFETIME_PROFILE;
DELETE PMQSCH.PRODUCT_PROFILE;
DELETE PMQSCH.PRODUCT_KPI;
DELETE PMQSCH.RESOURCE_PROFILE;
DELETE PMQSCH.RESOURCE_KPI;
DELETE PMQSCH.MATERIAL_PROFILE;
DELETE PMQSCH.PROCESS_KPI;
DELETE PMQSCH.PROCESS_PROFILE;
DELETE PMQSCH.PROFILE_PARAMETER;
DELETE FROM PMQSCH.EVENT_PROFILE;
DELETE PMQSCH.EVENT_OBSERVATION;
DELETE PMQSCH.EVENT;
DELETE PMQSCH.MASTER_RESOURCE_CONNECTION;
DELETE PMQSCH.MASTER_PROFILE_MAPPING;
DELETE PMQSCH.MASTER_RESOURCE_PRODBATCH;
DELETE PMQSCH.MASTER_PRODUCTION_BATCH;
DELETE PMQSCH.SERVICE;
DELETE PMQSCH.MASTER_PRODUCT_HIERARCHY;
DELETE PMQSCH.MASTER_PRODUCT;
DELETE PMQSCH.MASTER_RESOURCE_HIERARCHY;
DELETE PMQSCH.MASTER_RESOURCE;
DELETE PMQSCH.MASTER_PROFILE_VARIABLE;
DELETE PMQSCH.MASTER_MATERIAL;
DELETE PMQSCH.MASTER_MATERIAL_TYPE;
DELETE PMQSCH.MASTER_PROFILE_CALCULATION;
DELETE PMQSCH.MASTER_RESOURCE_TYPE;
DELETE PMQSCH.MASTER_MEASUREMENT_TYPE;
DELETE PMQSCH.MASTER_VALUE_TYPE;
DELETE PMQSCH.MASTER_SUPPLIER;
DELETE PMQSCH.MASTER_SOURCE_SYSTEM;
DELETE PMQSCH.MASTER_PROCESS_HIERARCHY;
DELETE PMQSCH.MASTER_PROCESS;
DELETE PMQSCH.MASTER_LOCATION;
DELETE PMQSCH.MASTER_GROUP_DIM;
DELETE PMQSCH.MASTER_EVENT_TYPE;
DELETE PMQSCH.MASTER_EVENT_CODE;
DELETE PMQSCH.MASTER_OBSERVATION_LOOKUP;
DELETE PMQSCH.MAINTENANCE_TRENDS;
DELETE PMQSCH.MAINTENANCE_DAILY;
DELETE PMQSCH.MAINT_ADM_RECOMMENDATIONS;
DELETE PMQSCH.TOPN_PREDICTORS;
DELETE PMQSCH.KEY_LOOKUP;
DELETE PMQSCH.LANGUAGE;
DELETE PMQSCH.TENANT;
DELETE PMQSCH.PMQ_USER;
DELETE PMQSCH.PMQ_CHART_CONFIG;

Enter the following SQL statements to alter tables:

ALTER TABLE "PMQSCH "."EVENT" ALTER COLUMN "EVENT_ID" RESTART WITH 1;
ALTER TABLE "PMQSCH "."LANGUAGE" ALTER COLUMN "LANGUAGE_ID" RESTART WITH 1;
ALTER TABLE "PMQSCH "."TENANT" ALTER COLUMN "TENANT_ID" RESTART WITH 1;
ALTER TABLE "PMQSCH "."KEY_LOOKUP" ALTER COLUMN "KEY_LOOKUP_ID" RESTART WITH 1;
ALTER TABLE "PMQSCH "."MASTER_PROFILE_CALCULATION" ALTER COLUMN
"MASTER_PROFILE_CALCULATION_ID" RESTART WITH 1;

Do one of the following steps to disconnect from the IBMPMQ database:

If the IBMPMQ database is in IBM DB2, type the following command:

db2 connect reset

If the IBMPMQ database is in Oracle Database, then disconnect from it using the appropriate command.

Restart the pmqgroup1 integration server (in previous versions, called an execution group).

For more information, see the IBM Integration Bus documentation.

Parent topic: Samples

Supporting programs licensed with IBM Predictive Maintenance and QualityThe following supporting programs are licensed with Predictive Maintenance and Quality.Supporting programs IBM Cognos Business Intelligence Analytics AdministratorIBM SPSS Analytical Decision Management IBM SPSS Analytical Decision Management ApplicationIBM SPSS Collaboration and Deployment Services IBM SPSS Collaboration and Deployment Services Deployment Portal IBM SPSS Modeler Gold Server IBM SPSS Modeler Solution Publisher IBM SPSS Modeler Server Premium IBM SPSS Statistics Server Standard IBM SPSS Statistics - Essentials for Python IBM SPSS Collaboration and Deployment Services Adapters for Statistics IBM SPSS Data Access Pack IBM DB2 Enterprise Server Edition Version IBM WebSphere Application Server Network Deployment IBM Installation Manager and Packaging Utility for the Rational Software Development PlatformIBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services IBM SPSS Analytic Server IBM ILOG CPLEX Enterprise Server IBM Integration Bus Manufacturing Pack for EnterpriseSupporting programs - Client installation IBM Cognos Business Intelligence Software Development Kit IBM Cognos Business Intelligence Samples IBM Cognos Cube Designer IBM Cognos Supplementary Languages Documentation IBM SPSS Collaboration and Deployment Services Deployment Manager IBM Cognos Framework ManagerIBM Cognos Lifecycle ManagerIBM Cognos for Microsoft OfficeIBM Cognos Dynamic Query AnalyzerIBM SPSS Modeler Gold Keyless IBM SPSS Concurrent Licensing Tools IBM SPSS Statistics Standard IBM SPSS Statistics Client / Developer Documentation IBM WebSphere MQ IBM Integration Bus IBM ILOG CPLEX Optimization Studio

Supporting programs licensed with IBM Predictive Maintenance and Quality

The following supporting programs are licensed with Predictive Maintenance and Quality.

Supporting programs

IBM® Cognos® Business Intelligence Analytics Administrator

IBM SPSS® Analytical Decision Management

IBM SPSS Analytical Decision Management Application

IBM SPSS Collaboration and Deployment Services

IBM SPSS Collaboration and Deployment Services Deployment Portal

IBM SPSS Modeler Gold Server

IBM SPSS Modeler Solution Publisher

IBM SPSS Modeler Server Premium

IBM SPSS Statistics Server Standard

IBM SPSS Statistics - Essentials for Python

IBM SPSS Collaboration and Deployment Services Adapters for Statistics

IBM SPSS Data Access Pack

IBM DB2® Enterprise Server Edition Version

IBM WebSphere® Application Server Network Deployment

IBM Installation Manager and Packaging Utility for the Rational® Software Development Platform

IBM InfoSphere® Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services

IBM SPSS Analytic Server

IBM ILOG® CPLEX® Enterprise Server IBM Integration Bus Manufacturing Pack for Enterprise

Supporting programs - Client installation

IBM Cognos Business Intelligence Software Development Kit

IBM Cognos Business Intelligence Samples

IBM Cognos Cube Designer

IBM Cognos Supplementary Languages Documentation

IBM SPSS Collaboration and Deployment Services Deployment Manager

IBM Cognos Framework Manager

IBM Cognos Lifecycle Manager

IBM Cognos for Microsoft Office

IBM Cognos Dynamic Query Analyzer

IBM SPSS Modeler Gold Keyless

IBM SPSS Concurrent Licensing Tools

IBM SPSS Statistics Standard

IBM SPSS Statistics Client / Developer Documentation

IBM WebSphere MQ

IBM Integration Bus

IBM ILOG CPLEX Optimization Studio

Programs not authorized by the IBM Predictive Maintenance and Quality licenseThe following programs are not authorized with the IBM Predictive Maintenance and Quality, and the use of these programs is not authorized by the Predictive Maintenance and Quality license.IBM Cognos Analysis for Microsoft Excel (IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Analysis Studio (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Business Intelligence Transformer (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Connection Installer for IBM Cognos Insight (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Data Manager Connector (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Insight (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Metric Designer (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Metric Studio (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Metrics Manager (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Query Studio (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos TM1 Package Connector (of IBM Cognos Business Intelligence Analytic Administrator) IBM Connections (of IBM Cognos Business Intelligence Analytic Administrator) IBM DB2 Workgroup Server Edition (of IBM Cognos Business Intelligence Analytic Administrator and IBM SPSS Analytic Server) IBM Tivoli Directory Integrator Identity Edition (of IBM Cognos Business Intelligence Analytic Administrator) IBM Business Intelligence Pattern (of IBM Cognos Business Intelligence Analytic Administrator) IBM Business Intelligence Pattern with Blu Acceleration (of IBM Cognos Business Intelligence Analytic Administrator) IBM Cognos Real-time Monitoring (of IBM Cognos Business Intelligence Analytic Administrator) Embedded version of IBM WebSphere Application Server ("embedded WebSphere Application Server").( of IBM Tivoli System Automation for Multiplatforms ( of IBM DB2 Enterprise Server Edition) ) embedded WebSphere Application Server ( of IBM Tivoli Directory Server - Client Only (component) ( of IBM DB2 Enterprise Server Edition ) ) IBM Cloudscape (of IBM Tivoli System Automation for Multiplatforms (of IBM DB2 Enterprise Server Edition) IBM Data Studio (of IBM DB2 Enterprise Server Edition) IBM DB2 Enterprise Server Edition (of IBM Tivoli Directory Server - Client Only (component) (of IBM DB2 Enterprise Server Edition) ) pureScale Feature (of IBM DB2 Enterprise Server Edition) IBM General Parallel File System (GPFS) for AIX ( of IBM DB2 Enterprise Server Edition Version) IBM General Parallel File System (GPFS) for Linux Multiplatform (of IBM DB2 Enterprise Server Edition) IBM Mobile Database (of IBM DB2 Enterprise Server Edition (of IBM DB2 Enterprise Server Edition Version) ) IBM Mobile Database Sync (of IBM DB2 Enterprise Server Edition) IBM Tivoli Storage Flashcopy Manager (of IBM DB2 Enterprise Server Edition) WebSphere Application Server (of IBM Tivoli Directory Server- Client Only (component) (of IBM DB2 Enterprise Server Edition) ) IBM InfoSphere Change Data Capture (of IBM DB2 Enterprise Server Edition) IBM DB2 Connect 10.5 (component) ( of IBM DB2 Enterprise Server Edition) IBM Cognos Business Intelligence (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM Content Integrator (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM Process Server Standard for Non-production Environment (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM InfoSphere Data Explorer (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM InfoSphere BigInsights Standard Edition (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM Integration Bus Healthcare Pack (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM InfoSphere Blueprint Director (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM InfoSphere Information Server for Data Quality (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM Process Center Standard (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM Process Designer (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM Process Server Standard (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM Security Directory Server (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM WebSphere Application Server Base (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) Workflow engine including Collaboration Areas(of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) Rational Application Developer for WebSphere Software (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) Global Data Synchronization Component (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) IBM WebSphere Portal Server (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services) J2SE Rule Execution Server (of IBM Integration Bus) IBM Integration Bus Manufacturing Pack for Factory IBM DB2 Workgroup Server Edition Version( of IBM Tivoli Directory Server - Client Only (component) ( of IBM DB2 Enterprise Server Edition Version)) IBM WebSphere Application Server Developer Tools for Eclipse (of IBM WebSphere Application Server Network Deployment) IBM WebSphere eXtreme Scale (of IBM WebSphere Application Server Network Deployment) IBM WebSphere Application Server (of IBM SPSS Analytic Server)

Programs not authorized by the IBM Predictive Maintenance and Quality license

The following programs are not authorized with the IBM® Predictive Maintenance and Quality, and the use of these programs is not authorized by the Predictive Maintenance and Quality license.

IBM Cognos Analysis for Microsoft Excel (IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Analysis Studio (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Business Intelligence Transformer (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Connection Installer for IBM Cognos Insight (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Data Manager Connector (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Insight (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Metric Designer (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Metric Studio (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Metrics Manager (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Query Studio (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos TM1 Package Connector (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Connections (of IBM Cognos Business Intelligence Analytic Administrator)

IBM DB2 Workgroup Server Edition (of IBM Cognos Business Intelligence Analytic Administrator and IBM SPSS Analytic Server)

IBM Tivoli Directory Integrator Identity Edition (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Business Intelligence Pattern (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Business Intelligence Pattern with Blu Acceleration (of IBM Cognos Business Intelligence Analytic Administrator)

IBM Cognos Real-time Monitoring (of IBM Cognos Business Intelligence Analytic Administrator)

Embedded version of IBM WebSphere Application Server ("embedded WebSphere Application Server").( of IBM Tivoli System Automation for Multiplatforms ( of IBM DB2 Enterprise Server Edition) )

embedded WebSphere Application Server ( of IBM Tivoli Directory Server - Client Only (component) ( of IBM DB2 Enterprise Server Edition ) )

IBM Cloudscape (of IBM Tivoli System Automation for Multiplatforms (of IBM DB2 Enterprise Server Edition)

IBM Data Studio (of IBM DB2 Enterprise Server Edition)

IBM DB2 Enterprise Server Edition (of IBM Tivoli Directory Server - Client Only (component) (of IBM DB2 Enterprise Server Edition) )

pureScale Feature (of IBM DB2 Enterprise Server Edition)

IBM General Parallel File System (GPFS) for AIX ( of IBM DB2 Enterprise Server Edition Version)

IBM General Parallel File System (GPFS) for Linux Multiplatform (of IBM DB2 Enterprise Server Edition)

IBM Mobile Database (of IBM DB2 Enterprise Server Edition (of IBM DB2 Enterprise Server Edition Version) )

IBM Mobile Database Sync (of IBM DB2 Enterprise Server Edition)

IBM Tivoli Storage Flashcopy Manager (of IBM DB2 Enterprise Server Edition)

WebSphere Application Server (of IBM Tivoli Directory Server- Client Only (component) (of IBM DB2 Enterprise Server Edition) )

IBM InfoSphere Change Data Capture (of IBM DB2 Enterprise Server Edition) IBM DB2 Connect 10.5 (component) ( of IBM DB2 Enterprise Server Edition)

IBM Cognos Business Intelligence (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM Content Integrator (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM Process Server Standard for Non-production Environment (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM InfoSphere Data Explorer (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM InfoSphere BigInsights Standard Edition (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM Integration Bus Healthcare Pack (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM InfoSphere Blueprint Director (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM InfoSphere Information Server for Data Quality (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM Process Center Standard (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM Process Designer (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM Process Server Standard (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM Security Directory Server (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM WebSphere Application Server Base (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

Workflow engine including Collaboration Areas(of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

Rational Application Developer for WebSphere Software (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

Global Data Synchronization Component (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

IBM WebSphere Portal Server (of IBM InfoSphere Master Data Management Collaboration Server - Collaborative Edition for Non-Financial Services)

J2SE Rule Execution Server (of IBM Integration Bus)

IBM Integration Bus Manufacturing Pack for Factory

IBM DB2 Workgroup Server Edition Version( of IBM Tivoli Directory Server - Client Only (component) ( of IBM DB2 Enterprise Server Edition Version))

IBM WebSphere Application Server Developer Tools for Eclipse (of IBM WebSphere Application Server Network Deployment)

IBM WebSphere eXtreme Scale (of IBM WebSphere Application Server Network Deployment)

IBM WebSphere Application Server (of IBM SPSS Analytic Server)

Administration tool and product portal referenceUpdates for 2.5.2 made using content provided by Sudarshan (Appendix_G.doc)The administrative tools and portals for IBM Predictive Maintenance and Quality are in several locations.The following table shows you access information for the tools and portals. Unless otherwise noted, the information applies to single or multinode configurations of IBM Predictive Maintenance and Quality.Administration tool and product portal reference Administration tool or portal and descriptionURL or locationBI node: WebSphere Application Server Administrative Console The WebSphere Application Server Administrative Console is the administration tool for WebSphere. The WebSphere Application Server Administrative Console runs on each node computer where WebSphere is installed. Use the console to start and stop applications.http://server_node_name:9060/ibm/console Where server_node_name is the name or IP address of a node computer where WebSphere is installed.IBM Cognos Business Intelligence Use IBM Cognos Connection to access reports. Use IBM Cognos Administration to configure IBM Cognos BI. For example, add data source connections or set security.http://bi_node_name:81/ibmcognos/ Where bi_node_name is the name or IP address of BI node computer.SPSS Node: WebSphere Application Server Administrative Console Use IBM SPSS Collaboration and Deployment Services Deployment Manager to configure IBM SPSS server settings.http://analytics_node_name:9061/console Where analytics_node_name is the name or IP address of Predictive Analytics node computer.SPSS Collaborative & Deployment Service Configuration http://analytics_node_name:9081/configWhere analytics_node_name is the name or IP address of Predictive Analytics node computer.SPSS Collaborative & Deployment Service pebhttp://analytics_node_name:9081/pebWhere analytics_node_name is the name or IP address of Predictive Analytics node computer.IBM Master Data Management WebSphere Application Server Administrative Console Single node configuration: http://mdm_node_name:9062/ibm/console Five node configuration: http://mdm_node_name:9061/ibm/console Where mdm_node_name is the name or IP address of Master Data Management (MDM) node computer. If you use the predefined installation template for three node or four node configurations, IBM Master Data Management is not installed. Master Data Management Portal Single or five node configuration: http://mdm_node_name:7507/utils/enterLogin.jsp Where mdm_node_name is the name or IP address of Master Data Management (MDM) node computer. If you use the predefined installation template for three node or four node configurations, IBM Master Data Management is not installed.

Administration tool and product portal reference

The administrative tools and portals for IBM® Predictive Maintenance and Quality are in several locations.

The following table shows you access information for the tools and portals. Unless otherwise noted, the information applies to single or multinode configurations of IBM Predictive Maintenance and Quality.

Table 19. Administration tool and product portal reference .

Administration tool or portal and description
URL or location

BI node: WebSphere Application Server Administrative Console

The WebSphere Application Server Administrative Console is the administration tool for WebSphere®.

The WebSphere Application Server Administrative Console runs on each node computer where WebSphere is installed.

Use the console to start and stop applications.

http://server_node_name:9060/ibm/console

Where server_node_name is the name or IP address of a node computer where WebSphere is installed.

IBM Cognos Business Intelligence

Use IBM Cognos Connection to access reports.

Use IBM Cognos Administration to configure IBM Cognos® BI. For example, add data source connections or set security.

http://bi_node_name:81/ibmcognos/

Where bi_node_name is the name or IP address of BI node computer.

SPSS Node: WebSphere Application Server Administrative Console

Use IBM SPSS Collaboration and Deployment Services Deployment Manager to configure IBM SPSS® server settings.

http://analytics_node_name:9061/console

Where analytics_node_name is the name or IP address of Predictive Analytics node computer.

SPSS Collaborative & Deployment Service Configuration
http://analytics_node_name:9081/config

Where analytics_node_name is the name or IP address of Predictive Analytics node computer.

SPSS Collaborative & Deployment Service peb
http://analytics_node_name:9081/peb

Where analytics_node_name is the name or IP address of Predictive Analytics node computer.

IBM Master Data Management WebSphere Application Server Administrative Console

Single node configuration: http://mdm_node_name:9062/ibm/console

Five node configuration: http://mdm_node_name:9061/ibm/console

Where mdm_node_name is the name or IP address of Master Data Management (MDM) node computer.

Note: If you use the predefined installation template for three node or four node configurations, IBM Master Data Management is not installed.

Master Data Management Portal

Single or five node configuration: http://mdm_node_name:7507/utils/enterLogin.jsp

Where mdm_node_name is the name or IP address of Master Data Management (MDM) node computer.

Note: If you use the predefined installation template for three node or four node configurations, IBM Master Data Management is not installed.

NoticesThis information was developed for products and services offered worldwide.This material may be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. This document may describe products, services, or features that are not included in the Program or license entitlement that you have purchased. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Software Group Attention: Licensing 3755 Riverside Dr. Ottawa, ON K1V 1B7 Canada Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.This Software Offering does not use cookies or other technologies to collect personally identifiable information.©

Notices

This information was developed for products and services offered worldwide.

This material may be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. This document may describe products, services, or features that are not included in the Program or license entitlement that you have purchased.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law

IBM Japan Ltd.

19-21, Nihonbashi-Hakozakicho, Chuo-ku

Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Software Group

Attention: Licensing

3755 Riverside Dr.

Ottawa, ON

K1V 1B7

Canada

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

©

© Product Information This document applies to IBM Predictive Maintenance and Quality Version 2.5.2 and may also apply to subsequent releases. Copyright Licensed Materials - Property of IBM © Copyright IBM Corp. 2013, 2016. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. The following terms are trademarks or registered trademarks of other companies: Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the United States and other countries.Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Notices

©

Product Information

This document applies to IBM Predictive Maintenance and Quality Version 2.5.2 and may also apply to subsequent releases.

Copyright

Licensed Materials - Property of IBM

© Copyright IBM Corp. 2013, 2016.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at " Copyright and trademark information " at www.ibm.com/legal/copytrade.shtml.

The following terms are trademarks or registered trademarks of other companies:

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Parent topic: Notices