IntroductionThe IBM Customer Experience Analytics for Communication Service Providers solution gives you the information and insight that you need to provide proactive service to your customers.Audience This guide is intended for administrators and users of the Customer Experience Analytics for Communication Service Providers solution. It provides information on installation, configuration, and use of the Customer Experience Analytics for Communication Service Providers solution. Finding information To find product documentation on the web, including all translated documentation, access IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter). You can also access PDF versions of the documentation from the IBM Industry Customer Intelligence Solutions web page (www.ibm.com/support/docview.wss?uid=swg27041723).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 Customer Experience Analytics for Communication Service Providers 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. . Customer Experience Analytics for Communication Service Providers 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.Samples disclaimer Sample files may contain fictional data manually or machine generated, factual data compiled from academic or public sources, or data used with permission of the copyright holder, for use as sample data to develop sample applications. Product names referenced may be the trademarks of their respective owners. Unauthorized duplication is prohibited.

Introduction

The IBM Customer Experience Analytics for Communication Service Providers solution gives you the information and insight that you need to provide proactive service to your customers.

Audience

This guide is intended for administrators and users of the Customer Experience Analytics for Communication Service Providers solution. It provides information on installation, configuration, and use of the Customer Experience Analytics for Communication Service Providers solution.

Finding information

To find product 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 Customer Experience Analytics for Communication Service Providers have accessibility features. For more information, see Accessibility features.

Customer Experience Analytics for Communication Service Providers 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.

Samples disclaimer

Sample files may contain fictional data manually or machine generated, factual data compiled from academic or public sources, or data used with permission of the copyright holder, for use as sample data to develop sample applications. Product names referenced may be the trademarks of their respective owners. Unauthorized duplication is prohibited.

OverviewIBM Customer Experience Analytics for Communication Service Providers is a prepackaged solution that works with IBM Predictive Customer Intelligence.Before you install the application, IBM Predictive Customer Intelligence must be installed on your system.IBM Customer Experience Analytics for Communication Service Providers is a solution that helps measure and improve customer network experience. The solution uses advanced analytics capability to measure network activity across locations, devices, and applications.The solution provides customer experience team members in the telecommunications industry a comprehensive customer experience analytics dashboard. The dashboard displays customer experience analytics across all services in one simple access view, including metrics such as:Unacceptable experience trendsDropped callsVideo experienceWeb experienceDevice usageApplication usageOverall customer experience scores What need does the solution address? Customer experience teams have many unanswered questions due to limited data and analytics. Some of these questions include:Why are my customers not satisfied or happy?How can we measure our overall customer experience score?What factors impact customer satisfaction and happiness?How can we drill down into specific factors, such as web, video, voice, and messaging services based on a customer usage profile? What does the solution provide? IBM Customer Experience Analytics for Communication Service Providers provides the following features:An overall customer experience score based on a weighted score for web, video, voice, and messaging services.The ability to discover key issues impacting overall customer experience scores, such as technologies, applications, devices, and locations.Processing of large volumes of raw usage data from network data sources such as voice or SMS CDRs, and Data Network Records XDRs.

Overview

IBM® Customer Experience Analytics for Communication Service Providers is a prepackaged solution that works with IBM Predictive Customer Intelligence.

Important: Before you install the application, IBM Predictive Customer Intelligence must be installed on your system.

IBM Customer Experience Analytics for Communication Service Providers is a solution that helps measure and improve customer network experience. The solution uses advanced analytics capability to measure network activity across locations, devices, and applications.

The solution provides customer experience team members in the telecommunications industry a comprehensive customer experience analytics dashboard. The dashboard displays customer experience analytics across all services in one simple access view, including metrics such as:

Unacceptable experience trends

Dropped calls

Video experience

Web experience

Device usage

Application usage

Overall customer experience scores

What need does the solution address?

Customer experience teams have many unanswered questions due to limited data and analytics. Some of these questions include:

Why are my customers not satisfied or happy?

How can we measure our overall customer experience score?

What factors impact customer satisfaction and happiness?

How can we drill down into specific factors, such as web, video, voice, and messaging services based on a customer usage profile?

What does the solution provide?

IBM Customer Experience Analytics for Communication Service Providers provides the following features:

An overall customer experience score based on a weighted score for web, video, voice, and messaging services.

The ability to discover key issues impacting overall customer experience scores, such as technologies, applications, devices, and locations.

Processing of large volumes of raw usage data from network data sources such as voice or SMS CDRs, and Data Network Records XDRs.

Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.installationconfigurationsolutiontopologyCustomer Experience Analytics for Communication Service Providers consists of the following nodes: An Analytics Platform node.A Mediation node.A Business Intelligence node.The IBM Predictive Customer Intelligence topology also includes a Predictive Analytics node, data node, and an Integration Bus node, which are not used in the Customer Experience Analytics for Communication Service Providers solution.Contents of the solution packageThe IBM Customer Experience Analytics for Communication Service Providers solution package contains several parts.Overview of the installation and configuration processThis is an overview of the general tasks that you must perform to install and configure the Customer Experience Analytics for Communication Service Providers solution. PrerequisitesBefore you install the Customer Experience Analytics for Communication Service Providers solution, there are prerequisites that must be met.Modifying the sudoers file for the Linux user who runs the installationTo run the Customer Experience Analytics for Communication Service Providers installation in a Linux environment, you must be either root user or have sudo permission on each node computer, and you must disable requiretty during the installation.Computer firewall settings required for the installation on LinuxThe solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.Installing the solution installerBefore using the Solution Installer to configure and deploy the nodes in a Linux environment, you must install the Solution Installer. Deploying the installation files on the nodesYou use the Solution Installer to deploy the installation files to the appropriate nodes in your solution. Deploying content on the Business Intelligence nodeYou must deploy the content files (report images and Framework Manager model) for the Customer Experience Analytics for Communication Service Providers solution.Setting up the Cognos Framework Manager modelOpen the project file in IBM Cognos Framework Manager and save it.Deploying the IBM Cognos BI reportsYou use IBM Cognos Administration to deploy the reports.Installing the Analytics PlatformThe Analytics Platform is software that is installed on your Analytics Platform nodes. It manages the creation of your data sets in the Apache Hadoop ecosystem. Analytics Platform allows deployment of data sets and management of those data sets, which makes up the basis of your solution. Creating a data source connection to the BigInsights databaseYou must create a data source connection from the Business Intelligence node to the IBM BigInsights database that is on the Analytics Platform node.Installing the SLM tagging functionalityYou can deploy the slm tagging functionality on the Analytics Platform node.Installation and configuration of the Mediation node Mediation software is deployed on the mediation nodes in your deployment, manages the loading and aggregation of your telecommunication (telco) data into the Apache Hadoop ecosystem, and works in conjunction with the Analytics Platform. The mediation software works with the Infosphere Streams software installed on your mediation nodes. It manages the loading and key performance indicator (kpi) calculation of your telco data and prepares the data for analysis by the end user. The volume of data to be analyzed will determine how many mediation nodes are required in your platform.

Installation and configuration

The IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Customer Experience Analytics for Communication Service Providers consists of the following nodes:

An Analytics Platform node.

A Mediation node.

A Business Intelligence node.

Note: The IBM Predictive Customer Intelligence topology also includes a Predictive Analytics node, data node, and an Integration Bus node, which are not used in the Customer Experience Analytics for Communication Service Providers solution.

Contents of the solution package
The IBM® Customer Experience Analytics for Communication Service Providers solution package contains several parts.

Overview of the installation and configuration process
This is an overview of the general tasks that you must perform to install and configure the Customer Experience Analytics for Communication Service Providers solution.

Prerequisites
Before you install the Customer Experience Analytics for Communication Service Providers solution, there are prerequisites that must be met.

Modifying the sudoers file for the Linux user who runs the installation
To run the Customer Experience Analytics for Communication Service Providers installation in a Linux environment, you must be either root user or have sudo permission on each node computer, and you must disable requiretty during the installation.

Computer firewall settings required for the installation on Linux
The solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.

Installing the solution installer
Before using the Solution Installer to configure and deploy the nodes in a Linux environment, you must install the Solution Installer.

Deploying the installation files on the nodes
You use the Solution Installer to deploy the installation files to the appropriate nodes in your solution.

Deploying content on the Business Intelligence node
You must deploy the content files (report images and Framework Manager model) for the Customer Experience Analytics for Communication Service Providers solution.

Setting up the Cognos Framework Manager model
Open the project file in IBM Cognos Framework Manager and save it.

Deploying the IBM Cognos BI reports
You use IBM Cognos Administration to deploy the reports.

Installing the Analytics Platform
The Analytics Platform is software that is installed on your Analytics Platform nodes. It manages the creation of your data sets in the Apache Hadoop ecosystem. Analytics Platform allows deployment of data sets and management of those data sets, which makes up the basis of your solution.

Creating a data source connection to the BigInsights database
You must create a data source connection from the Business Intelligence node to the IBM BigInsights® database that is on the Analytics Platform node.

Installing the SLM tagging functionality
You can deploy the slm tagging functionality on the Analytics Platform node.

Installation and configuration of the Mediation node
Mediation software is deployed on the mediation nodes in your deployment, manages the loading and aggregation of your telecommunication (telco) data into the Apache Hadoop ecosystem, and works in conjunction with the Analytics Platform. The mediation software works with the Infosphere Streams software installed on your mediation nodes. It manages the loading and key performance indicator (kpi) calculation of your telco data and prepares the data for analysis by the end user. The volume of data to be analyzed will determine how many mediation nodes are required in your platform.

Contents of the solution packageThe IBM Customer Experience Analytics for Communication Service Providers solution package contains several parts.packagecontentsThe following parts are included in the solution package:Solution Installer. This puts the installation packages on the nodes required for a particular deployment architecture.IBM Cognos Business Intelligence (BI) reports and IBM Cognos Framework Manager modelsThe Analytics Platform contains the software for data management and ETL (extract, transfer, and load) and will be installed on the Analytics Platform and Streams nodes.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Contents of the solution package

The IBM® Customer Experience Analytics for Communication Service Providers solution package contains several parts.

The following parts are included in the solution package:

Solution Installer. This puts the installation packages on the nodes required for a particular deployment architecture.

IBM Cognos® Business Intelligence (BI) reports and IBM Cognos Framework Manager models

The Analytics Platform contains the software for data management and ETL (extract, transfer, and load) and will be installed on the Analytics Platform and Streams nodes.

Parent topic: Installation and configuration

Overview of the installation and configuration processThis is an overview of the general tasks that you must perform to install and configure the Customer Experience Analytics for Communication Service Providers solution. installationoverviewThe following diagram provides a high-level overview of the installation and configuration process. If you are viewing this diagram from the IBM Knowledge Center, you can click on a task to go to the procedure for that task.Diagram that provides an overview of the installation processrect121,17,247,69Contents of the solution packageThe IBM Customer Experience Analytics for Communication Service Providers solution package contains several parts.rect117,70,247,89Computer firewall settings required for the installation on LinuxThe solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.rect36,147,189,224Installing the solution installerBefore using the Solution Installer to configure and deploy the nodes in a Linux environment, you must install the Solution Installer. rect231,369,322,403Installing the Analytics PlatformThe Analytics Platform is software that is installed on your Analytics Platform nodes. It manages the creation of your data sets in the Apache Hadoop ecosystem. Analytics Platform allows deployment of data sets and management of those data sets, which makes up the basis of your solution. rect341,366,392,404Deploying content on the Business Intelligence nodeYou must deploy the content files (report images and Framework Manager model) for the Customer Experience Analytics for Communication Service Providers solution.rect405,364,466,407Installing IBM InfoSphere StreamsPerform the following tasks:Install prerequisite software.Download the solution from IBM Passport Advantage.Plan where you want the various parts of the solution to reside. For example, you must decide which computers to use for the Analytics Platform node and Streams node.Run the Solution Installer to deploy the installation files to the relevant nodes.Set up the IBM Cognos Framework Manager model.Install IBM Cognos reports. Install and configure the Analytics Platform node .Install and configure the Streams node.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Overview of the installation and configuration process

This is an overview of the general tasks that you must perform to install and configure the Customer Experience Analytics for Communication Service Providers solution.

The following diagram provides a high-level overview of the installation and configuration process. If you are viewing this diagram from the IBM Knowledge Center, you can click on a task to go to the procedure for that task.

Perform the following tasks:

Install prerequisite software.

Download the solution from IBM Passport Advantage®.

Plan where you want the various parts of the solution to reside. For example, you must decide which computers to use for the Analytics Platform node and Streams node.

Run the Solution Installer to deploy the installation files to the relevant nodes.

Set up the IBM Cognos® Framework Manager model.

Install IBM Cognos reports.

Install and configure the Analytics Platform node .

Install and configure the Streams node.

Parent topic: Installation and configuration

PrerequisitesBefore you install the Customer Experience Analytics for Communication Service Providers solution, there are prerequisites that must be met.installationprerequisitesmaster nodeEnsure the following conditions are met before you install the solution:IBM Predictive Customer Intelligence version 1.1.0 is installed and configured and you have applied all known fix packs to it. IBM InfoSphere BigInsights 4.1.0 is installed and configured on the Analytics Platform node. IBM InfoSphere Streams 4.0.1 is installed and configured on the Streams nodes. For more information, see the installation instructions for IBM InfoSphere Streams 4.0.1 on IBM Knowledge Center.You have a Red Hat Enterprise Linux operating system that you can install to. The Solution Installer works only on that version of Linux. You understand your deployment environment. There are a combination of nodes that you must install to, so you need to determine where you want the various components of the solution to reside.You have administration rights and the ability to copy files between computers.In the context of the Customer Experience Analytics for Communication Service Providers solution, the BigInsights master node is one of the Analytics Platform nodes.Installing IBM Predictive Customer Intelligence version 1.1.0 To install PCI version 1.1.0, refer to the IBM Predictive Customer Intelligence Installation Guide 1.1.0 on IBM Knowledge Center. Ensure that you adhere to the following sections in this guide:Prerequisites and installation preparationSolution architectureSupported operating systems and hardware requirementsPrerequisites for using the solution installerInstall IBM Predictive Customer Intelligence by using the solution installerManually install IBM Predictive Customer IntelligenceTroubleshooting (if necessary) Install PCI on the designated PCI nodes in your deployment.Installing IBM InfoSphere BigInsights 4.1.0 Before installing IBM InfoSphere BigInsights 4.1.0, you must first install IBM Open Platform (IOP) with Apache Hadoop. This is an IBM open-source download that provides the components and services to start your Hadoop project, including development tools, a management dashboard, and cluster management tools. This download is available form the IBM Open Platform with Apache Hadoop 4.1 web page. To prepare your environment and servers, refer to the documentation Preparing to install IBM Open Platform with Apache Hadoop on IBM Knowledge Center. To install IOP with Apache Hadoop, refer to the documentation Installing the IBM Open Platform with Apache Hadoop software on IBM Knowledge Center. This documentation will guide you through the key set up and installation steps, including reference architectureminimum system requirementspreparing your environmentdefault ports To ensure reliability, you may wish to use a mirror site rather than IBM's hosted repository. If you require a repository, refer to Creating a mirror repository for the IBM Open Platform with Apache Hadoop software. The repository can be installed on the same computer as IOP with Apache Hadoop. Regarding the information provided in the topic Installing the IBM BigInsights value-added services on IBM Open Platform with Apache Hadoop, ensure the following added value services are installed. These services should be deployed on your designated Analytics Platform nodes: BigInsights HomeBigInsights -- Big SQL ServiceBigInsights -- Data Server Manager ServiceInstalling IBM IBM InfoSphere Streams 4.0.1 IBM InfoSphere Streams enables you to capture, analyze, and act on business data from a broad range of sources. Using real-time analytic processing (RTAP) technology, InfoSphere Streams can continuously analyze massive volumes of streaming data in real time, with extremely fast response times. InfoSphere Streams must be installed before you install the IBM Streams mediation package, which is part of the IBM Customer Experience Analytics for Communication Service Providers solution. To install InfoSphere Streams 4.0.1, refer to Installing IBM InfoSphere Streams on IBM Knowledge Center. Follow the instructions for installing the product on the designated Streams mediation nodes in your deployment. Please note the following: InfoSphere Streams provides a dependency checker script that you run on your system before installing the product. This script verifies that your system meets the software requirements for InfoSphere Streams. To run the dependency checker script, enter the ./dependency_checker.sh command from/opt/tnf/streams/StreamsInstallFiles.If required, correct any dependencies and run the dependency checker again. The following message will be displayed once all dependencies are in place:=== Summary of Errors and Warnings === CDISI0003I The dependency checker evaluated the system and did not find errors or warnings.If the dependency checker display the following warning, the ulimit settings need to be updated and the device rebooted. Please refer to Guidelines for configuring Linux ulimit settings for InfoSphere Streams. Warning: CDISI3044W The system soft limit for the maximum number of processes is low: 1024Install InfoSphere Streams in console mode using the following command: ./InfoSphereStreamsSetup.bin -i consoleInstallation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Prerequisites

Before you install the Customer Experience Analytics for Communication Service Providers solution, there are prerequisites that must be met.

Ensure the following conditions are met before you install the solution:

IBM Predictive Customer Intelligence version 1.1.0 is installed and configured and you have applied all known fix packs to it.

IBM® InfoSphere® BigInsights® 4.1.0 is installed and configured on the Analytics Platform node.

IBM InfoSphere Streams 4.0.1 is installed and configured on the Streams nodes. For more information, see the installation instructions for IBM InfoSphere Streams 4.0.1 on IBM Knowledge Center.

You have a Red Hat Enterprise Linux operating system that you can install to. The Solution Installer works only on that version of Linux.

You understand your deployment environment. There are a combination of nodes that you must install to, so you need to determine where you want the various components of the solution to reside.

You have administration rights and the ability to copy files between computers.

In the context of the Customer Experience Analytics for Communication Service Providers solution, the BigInsights master node is one of the Analytics Platform nodes.

Installing IBM Predictive Customer Intelligence version 1.1.0

To install PCI version 1.1.0, refer to the IBM Predictive Customer Intelligence Installation Guide 1.1.0 on IBM Knowledge Center.

Ensure that you adhere to the following sections in this guide:

Prerequisites and installation preparation

Solution architecture

Supported operating systems and hardware requirements

Prerequisites for using the solution installer

Install IBM Predictive Customer Intelligence by using the solution installer

Manually install IBM Predictive Customer Intelligence

Troubleshooting (if necessary)

Install PCI on the designated PCI nodes in your deployment.

Installing IBM InfoSphere BigInsights 4.1.0

Before installing IBM InfoSphere BigInsights 4.1.0, you must first install IBM Open Platform (IOP) with Apache Hadoop. This is an IBM open-source download that provides the components and services to start your Hadoop project, including development tools, a management dashboard, and cluster management tools. This download is available form the IBM Open Platform with Apache Hadoop 4.1 web page.

To prepare your environment and servers, refer to the documentation Preparing to install IBM Open Platform with Apache Hadoop on IBM Knowledge Center.

To install IOP with Apache Hadoop, refer to the documentation Installing the IBM Open Platform with Apache Hadoop software on IBM Knowledge Center.

This documentation will guide you through the key set up and installation steps, including

reference architecture

minimum system requirements

preparing your environment

default ports

To ensure reliability, you may wish to use a mirror site rather than IBM's hosted repository. If you require a repository, refer to Creating a mirror repository for the IBM Open Platform with Apache Hadoop software. The repository can be installed on the same computer as IOP with Apache Hadoop.

Regarding the information provided in the topic Installing the IBM BigInsights value-added services on IBM Open Platform with Apache Hadoop, ensure the following added value services are installed. These services should be deployed on your designated Analytics Platform nodes:

BigInsights Home

BigInsights -- Big SQL Service

BigInsights -- Data Server Manager Service

Installing IBM IBM InfoSphere Streams 4.0.1

IBM InfoSphere Streams enables you to capture, analyze, and act on business data from a broad range of sources. Using real-time analytic processing (RTAP) technology, InfoSphere Streams can continuously analyze massive volumes of streaming data in real time, with extremely fast response times.

InfoSphere Streams must be installed before you install the IBM Streams mediation package, which is part of the IBM Customer Experience Analytics for Communication Service Providers solution.

To install InfoSphere Streams 4.0.1, refer to Installing IBM InfoSphere Streams on IBM Knowledge Center. Follow the instructions for installing the product on the designated Streams mediation nodes in your deployment. Please note the following:

InfoSphere Streams provides a dependency checker script that you run on your system before installing the product. This script verifies that your system meets the software requirements for InfoSphere Streams. To run the dependency checker script, enter the ./dependency_checker.sh command from/opt/tnf/streams/StreamsInstallFiles.

If required, correct any dependencies and run the dependency checker again. The following message will be displayed once all dependencies are in place:

=== Summary of Errors and Warnings ===
CDISI0003I The dependency checker evaluated the system and did not find errors or warnings.

If the dependency checker display the following warning, the ulimit settings need to be updated and the device rebooted. Please refer to Guidelines for configuring Linux ulimit settings for InfoSphere Streams.

Warning: CDISI3044W The system soft limit for the maximum number of processes is low: 1024

Install InfoSphere Streams in console mode using the following command: ./InfoSphereStreamsSetup.bin -i console

Parent topic: Installation and configuration

Modifying the sudoers file for the Linux user who runs the installationTo run the Customer Experience Analytics for Communication Service Providers installation in a Linux environment, you must be either root user or have sudo permission on each node computer, and you must disable requiretty during the installation.To install with sudo user permissions, you must add the user to the sudoers file.installationmodifying sudoers fileconfigurationmodifying sudoers filesudoers fileLog in as root user.Enter the following command to open the sudoers file for editing:visudo -f /etc/sudoersLocate the following line:Defaults requirettyPress the I key to insert text.Type a number sign (#) in front of Defaults requiretty to comment out the line.For example, the line will appears as #Defaults requirettyIf you run the installer as a user with sudo user permissions, go to the end of the file, and add the following line for your user:username ALL=(ALL) NOPASSWD: ALLPress the Esc key, and enter :wq to save and close the file.Repeat these steps on each computer on which you install a Customer Experience Analytics for Communication Service Providers node.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Modifying the sudoers file for the Linux user who runs the installation

To run the Customer Experience Analytics for Communication Service Providers installation in a Linux environment, you must be either root user or have sudo permission on each node computer, and you must disable requiretty during the installation.

To install with sudo user permissions, you must 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

Locate the following line:

Defaults requiretty

Press the I key to insert text.

Type a number sign (#) in front of Defaults requiretty to comment out the line. For example, the line will appears as #Defaults requiretty

If you run the installer as a user with sudo user permissions, go to the end of the file, and add the following line for your user:

username ALL=(ALL) NOPASSWD: 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 Customer Experience Analytics for Communication Service Providers node.

Parent topic: Installation and configuration

Computer firewall settings required for the installation on LinuxThe solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.To ensure bidirectional communication, you must configure your firewall settings for the installation. Alternatively, you can temporarily disable your firewall during the installation. A script is provided to open all necessary ports on the installation node. You can either use the firewall.sh script, open the ports manually, or disable the firewall settings. In addition to opening ports on the installation node computer, you must open some ports on each computer to which content from the solution will be copied.firewall settingsInstallation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.Disabling firewall settings during installation (optional)If you choose to temporarily disable your computer's firewall during the installation of the IBM Customer Experience Analytics for Communication Service Providers solution, ensure that you enable the firewall on each node after the installation is complete.Manually configuring firewall settings on the installation nodeIf you prefer not to disable your firewall settings or use the firewall.sh script, you can manually configure your firewall settings on the installation node.Configuring your firewall settings on the installation node computer by using the firewall scriptYou can run the firewall.sh script to open the ports on a Linux installation node.Configuring firewall settings on other computers that will contain content from the solutionOn all node computers to which content from the solution will be copied, the ports 443, 9683, and 8080 must be opened for the installation process.

Computer firewall settings required for the installation on Linux

The solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.

To ensure bidirectional communication, you must configure your firewall settings for the installation. Alternatively, you can temporarily disable your firewall during the installation.

A script is provided to open all necessary ports on the installation node. You can either use the firewall.sh script, open the ports manually, or disable the firewall settings.

In addition to opening ports on the installation node computer, you must open some ports on each computer to which content from the solution will be copied.

Disabling firewall settings during installation (optional)
If you choose to temporarily disable your computer's firewall during the installation of the IBM® Customer Experience Analytics for Communication Service Providers solution, ensure that you enable the firewall on each node after the installation is complete.

Manually configuring firewall settings on the installation node
If you prefer not to disable your firewall settings or use the firewall.sh script, you can manually configure your firewall settings on the installation node.

Configuring your firewall settings on the installation node computer by using the firewall script
You can run the firewall.sh script to open the ports on a Linux installation node.

Configuring firewall settings on other computers that will contain content from the solution
On all node computers to which content from the solution will be copied, the ports 443, 9683, and 8080 must be opened for the installation process.

Parent topic: Installation and configuration

Disabling firewall settings during installation (optional)If you choose to temporarily disable your computer's firewall during the installation of the IBM Customer Experience Analytics for Communication Service Providers solution, ensure that you enable the firewall on each node after the installation is complete.firewall settingsdisablingIf you disable your computer's firewall during the installation, you must still ensure that the required ports are opened on each node computer when you restart your firewall.Log on to the computer as the root user or as a user with sudo permissions.Type the following command: /etc/init.d/iptables stop /etc/init.d/iptables saveRepeat these steps on each computer on which you install a node and on the server from which you are running the installation.After the installation is complete, on each node, type /etc/init.d/iptables start to restart your firewall.Computer firewall settings required for the installation on LinuxThe solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.

Disabling firewall settings during installation (optional)

If you choose to temporarily disable your computer's firewall during the installation of the IBM® Customer Experience Analytics for Communication Service Providers solution, ensure that you enable the firewall on each node after the installation is complete.

About this task

Important: If you disable your computer's firewall during the installation, you must still ensure that the required ports are opened on each node computer when you restart your firewall.

Procedure

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

Type the following command:

/etc/init.d/iptables stop

/etc/init.d/iptables save

Repeat these steps on each computer on which you install a node and on the server from which you are running the installation.

What to do next

After the installation is complete, on each node, type /etc/init.d/iptables start to restart your firewall.

Parent topic: Computer firewall settings required for the installation on Linux

Manually configuring firewall settings on the installation nodeIf you prefer not to disable your firewall settings or use the firewall.sh script, you can manually configure your firewall settings on the installation node.firewall settingsmanually configuringAs the root user or as a user with sudo permissions, log on to the computer that contains the solution installer node .Back up your existing firewall settings by typing the following command: ./etc/init.d/iptables saveOn the computer that contains the solution installer node, add rules for the ports that are required by the installer by typing the following commands:iptables -I INPUT -p tcp --dport 8080 -j ACCEPT iptables -I OUTPUT -p tcp --sport 8080 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I INPUT -p tcp --dport 443 -j ACCEPT iptables -I OUTPUT -p tcp --sport 443 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I INPUT -p tcp --dport 9683 -j ACCEPT iptables -I OUTPUT -p tcp --sport 9683 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I OUTPUT -p tcp --dport 22 -j ACCEPT iptables -I INPUT -p tcp --sport 22 -m state --state RELATED,ESTABLISHED -j ACCEPTComputer firewall settings required for the installation on LinuxThe solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.

Manually configuring firewall settings on the installation node

If you prefer not to disable your firewall settings or use the firewall.sh script, you can manually configure your firewall settings on the installation node.

Procedure

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

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

On the computer that contains the solution installer node, add rules for the ports that are required by the installer by typing the following commands:

iptables -I INPUT -p tcp --dport 8080 -j ACCEPT
iptables -I OUTPUT -p tcp --sport 8080 -m state --state
RELATED,ESTABLISHED -j ACCEPT

iptables -I INPUT -p tcp --dport 443 -j ACCEPT
iptables -I OUTPUT -p tcp --sport 443 -m state --state
RELATED,ESTABLISHED -j ACCEPT

iptables -I INPUT -p tcp --dport 9683 -j ACCEPT
iptables -I OUTPUT -p tcp --sport 9683 -m state --state
RELATED,ESTABLISHED -j ACCEPT

iptables -I OUTPUT -p tcp --dport 22 -j ACCEPT
iptables -I INPUT -p tcp --sport 22 -m state --state
RELATED,ESTABLISHED -j ACCEPT

Parent topic: Computer firewall settings required for the installation on Linux

Configuring your firewall settings on the installation node computer by using the firewall scriptYou can run the firewall.sh script to open the ports on a Linux installation node.firewall settingsconfigure with scriptfirewall.shThe firewall.sh script opens the following ports on the solution installer node: 8080 incoming443 incoming9683 incoming22 outgoingAs the root user or as a user with sudo permissions, log on to the computer that contains the solution installer node.Back up your existing firewall settings by typing the following command: /etc/init.d/iptables save.Run the firewall.sh script.Computer firewall settings required for the installation on LinuxThe solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.

Configuring your firewall settings on the installation node computer by using the firewall script

You can run the firewall.sh script to open the ports on a Linux installation node.

About this task

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

8080 incoming

443 incoming

9683 incoming

22 outgoing

Procedure

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

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

Run the firewall.sh script.

Parent topic: Computer firewall settings required for the installation on Linux

Configuring firewall settings on other computers that will contain content from the solutionOn all node computers to which content from the solution will be copied, the ports 443, 9683, and 8080 must be opened for the installation process.firewall settingson all computersOn each of the computers to which content for the solution will be copied, add rules for the ports that are required by the installer by typing the following commands:iptables -I OUTPUT -p tcp --dport 443 -j ACCEPT iptables -I INPUT -p tcp --sport 443 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I OUTPUT -p tcp --dport 9683 -j ACCEPT iptables -I INPUT -p tcp --sport 9683 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I OUTPUT -p tcp --dport 8080 -j ACCEPT iptables -I INPUT -p tcp --sport 8080 -m state --state RELATED,ESTABLISHED -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 are applied by using the following command:iptables -L The added port appears in the list.Repeat these steps on each computer on which you will install an IBM Customer Experience Analytics for Communication Service Providers node.Computer firewall settings required for the installation on LinuxThe solution installer requires bidirectional communication with each node when you install a server component or server artifact component, and your firewall can interfere with this communication.

Configuring firewall settings on other computers that will contain content from the solution

On all node computers to which content from the solution will be copied, the ports 443, 9683, and 8080 must be opened for the installation process.

Procedure

On each of the computers to which content for the solution will be copied, add rules for the ports that are required by the installer by typing the following commands:

iptables -I OUTPUT -p tcp --dport 443 -j ACCEPT
iptables -I INPUT -p tcp --sport 443 -m state --state RELATED,ESTABLISHED -j ACCEPT

iptables -I OUTPUT -p tcp --dport 9683 -j ACCEPT
iptables -I INPUT -p tcp --sport 9683 -m state --state RELATED,ESTABLISHED -j ACCEPT

iptables -I OUTPUT -p tcp --dport 8080 -j ACCEPT
iptables -I INPUT -p tcp --sport 8080 -m state --state RELATED,ESTABLISHED -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 are applied by using the following command:

iptables -L

The added port appears in the list.

Repeat these steps on each computer on which you will install an IBM® Customer Experience Analytics for Communication Service Providers node.

Parent topic: Computer firewall settings required for the installation on Linux

Installing the solution installerBefore using the Solution Installer to configure and deploy the nodes in a Linux environment, you must install the Solution Installer. Here's a short video that shows you how to install the Solution Installer: http://youtu.be/9u6ZOk8iyt4 The steps that are shown in the video are described in the following procedure.Log on to the computer where you downloaded the solution package.Decompress the solution package. Go to the solution installer directory in the following location: opt/IBM/IS_CSP_CustomerAnalytics_1.0.1/SolutionInstaller.If you haven't already opened the ports required by the solution installer, you can open them by running the following command: ./firewall.shEnter the following command:./setup.sh username first name last name email Username is the name that can be used to log on to the Chef server. It must be all lowercase characters. First and last names are for display purposes only. Email is used for notifications from Chef server. The password for the user that is created in chef is optional. If it is not included, it will be prompted for at login.The web server is started and the URL for the Solution Installer displays in the command line window.A browser window might open automatically. If it doesn't, copy and paste the URL into a web browser and bookmark it. Use the Solution Installer to deploy the installation files to the nodes in your solution. Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Installing the solution installer

Before using the Solution Installer to configure and deploy the nodes in a Linux environment, you must install the Solution Installer.

About this task

Here's a short video that shows you how to install the Solution Installer:

http://youtu.be/9u6ZOk8iyt4

The steps that are shown in the video are described in the following procedure.

Procedure

Log on to the computer where you downloaded the solution package.

Decompress the solution package.

Go to the solution installer directory in the following location: opt/IBM/IS_CSP_CustomerAnalytics_1.0.1/SolutionInstaller.

If you haven't already opened the ports required by the solution installer, you can open them by running the following command:

./firewall.sh

Enter the following command:

./setup.sh username first name last name email

Username is the name that can be used to log on to the Chef server. It must be all lowercase characters. First and last names are for display purposes only. Email is used for notifications from Chef server. The password for the user that is created in chef is optional. If it is not included, it will be prompted for at login.

The web server is started and the URL for the Solution Installer displays in the command line window.

A browser window might open automatically. If it doesn't, copy and paste the URL into a web browser and bookmark it.

What to do next

Use the Solution Installer to deploy the installation files to the nodes in your solution.

Parent topic: Installation and configuration

Deploying the installation files on the nodesYou use the Solution Installer to deploy the installation files to the appropriate nodes in your solution. installationdeploying installation filesserversnodesnodesrequirementsEnsure that you know the URL for accessing the Solution Installer. Ensure that you know the following information for each of the nodes in your solution: Host name or IP addressA user ID and password that has write permissions to the /opt/ directory. Each node must also meet the following requirements: Has a valid DNS name that is resolvable. Does not have Chef server or client software installed on it.In this task, you create an installation configuration of your solution by dragging objects onto a canvas, adding components to the objects, and defining properties for the components. The Industry Solution Installer runs on the latest versions of Chrome and Firefox. It does not run on Internet Explorer and it is untested on Safari.In a web browser, go to the Solution Installer.Read the license agreement and click Accept.Click New Configuration and then click OK.From the Mandatory Content List pane, select Node. A visual representation of an empty node is displayed on the canvas.In the Property Editor, type a name for the node, and in the Host Name box, specify the server on which the node will be placed. For example, you might create a node that is named BI Node.Enter a username and password for a user that has sudo access. 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 adding Cognos BI Content, then a message indicates that the node is not yet valid.From the Optional Content list, drag any content that you want to add into the appropriate node. The reason that this content is optional is because you might already have some of the necessary components installed in your environment.For every node that you want to add content to, define the node and then drag content objects onto it.If you want to save the configuration to use or refer to in the future, click Save Configuration.Click Validate.The progress of the validation is displayed. If the validation fails, look at the log file to troubleshoot the problem. After all nodes are defined, the contents are specified, and each node is validated, click Run.The scripts and files that are used to install and configure the solution are copied to the target nodes.Complete the installation of the solution on each of the nodes. Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Deploying the installation files on the nodes

You use the Solution Installer to deploy the installation files to the appropriate nodes in your solution.

Before you begin

Ensure that you know the URL for accessing the Solution Installer.

Ensure that you know the following information for each of the nodes in your solution:

Host name or IP address

A user ID and password that has write permissions to the /opt/ directory.

Each node must also meet the following requirements:

Has a valid DNS name that is resolvable.

Does not have Chef server or client software installed on it.

About this task

In this task, you create an installation configuration of your solution by dragging objects onto a canvas, adding components to the objects, and defining properties for the components.

Important: The Industry Solution Installer runs on the latest versions of Chrome and Firefox. It does not run on Internet Explorer and it is untested on Safari.

Procedure

In a web browser, go to the Solution Installer.

Read the license agreement and click Accept.

Click New Configuration and then click OK.

From the Mandatory Content List pane, select Node.

A visual representation of an empty node is displayed on the canvas.

In the Property Editor, type a name for the node, and in the Host Name box, specify the server on which the node will be placed.

For example, you might create a node that is named BI Node.

Enter a username and password for a user that has sudo access.

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 adding Cognos BI Content, then a message indicates that the node is not yet valid.

From the Optional Content list, drag any content that you want to add into the appropriate node. The reason that this content is optional is because you might already have some of the necessary components installed in your environment.

For every node that you want to add content to, define the node and then drag content objects onto it.

If you want to save the configuration to use or refer to in the future, click Save Configuration.

Click Validate. The progress of the validation is displayed. If the validation fails, look at the log file to troubleshoot the problem.

After all nodes are defined, the contents are specified, and each node is validated, click Run. The scripts and files that are used to install and configure the solution are copied to the target nodes.

What to do next

Complete the installation of the solution on each of the nodes.

Parent topic: Installation and configuration

Deploying content on the Business Intelligence nodeYou must deploy the content files (report images and Framework Manager model) for the Customer Experience Analytics for Communication Service Providers solution.nodesBusiness Intelligence nodeLog on to the BI node as the root user or as a user with sudo permissions.Decompress the following files: CSP_CustomerAnalytics_FMProject.zipCSP_CustomerAnalytics_Images.zip Extract the CSP_CustomerAnalytics_BIContent.zip folder and copy it to the Cognos_Install_location/Deployment folder on the BI node computer.Copy the CSP_CustomerAnalytics_Images folder to the Cognos_Install_location/webcontent/samples folder on the BI node computer. If a folder of this name already exists at the destination location, merge the two folders. Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Deploying content on the Business Intelligence node

You must deploy the content files (report images and Framework Manager model) for the Customer Experience Analytics for Communication Service Providers solution.

Procedure

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

Decompress the following files:

CSP_CustomerAnalytics_FMProject.zip

CSP_CustomerAnalytics_Images.zip

Extract the CSP_CustomerAnalytics_BIContent.zip folder and copy it to the Cognos_Install_location/Deployment folder on the BI node computer.

Copy the CSP_CustomerAnalytics_Images folder to the Cognos_Install_location/webcontent/samples folder on the BI node computer. If a folder of this name already exists at the destination location, merge the two folders.

Parent topic: Installation and configuration

Setting up the Cognos Framework Manager modelOpen the project file in IBM Cognos Framework Manager and save it.Framework ManagerThe user ID that you log in with when you open Framework Manager must belong to the db2admins group. On the Business Intelligence node, open Cognos Framework Manager.Click Open a project.Select the File_saved_location/CSP_CustomerAnalytics_FMModel/ CSP_CustomerAnalytics_FMModel.cpf file.Click OK. The model opens and you can view the data model, sources, and package.Publish the package.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Setting up the Cognos Framework Manager model

Open the project file in IBM Cognos Framework Manager and save it.

Before you begin

The user ID that you log in with when you open Framework Manager must belong to the db2admins group.

Procedure

On the Business Intelligence node, open Cognos Framework Manager.

Click Open a project.

Select the File_saved_location/CSP_CustomerAnalytics_FMModel/ CSP_CustomerAnalytics_FMModel.cpf file.

Click OK. The model opens and you can view the data model, sources, and package.

Publish the package.

Parent topic: Installation and configuration

Deploying the IBM Cognos BI reportsYou use IBM Cognos Administration to deploy the reports.reportsEnsure that CSP_CustomerAnalytics_BIContent.zip is in the Cognos_install_location/Deployment folder on the Business Intelligence node.Open a web browser on the Business Intelligence node.Go to the IBM Cognos BI portal URL. For example, go to http://cognos node/ibmcognos/.On the Welcome page, click Administer IBM Cognos Content. Click the Configuration tab, and then click Content Administration. On the toolbar, click New Import. In the Deployment Archive pane, select deployment archive (CSP_CustomerAnalytics_BIContent.zip), and click Next. In the Specify a name and description pane, accept the default or enter a new name, and click Next.In the Select the public folders and directory content pane, select all of the packages in the table, leave the Options as default, ensure that the Disable after import option is unselected, and click Next. In the Specify the general options pane, accept the defaults, and click Next.On the Review the summary page, click Next.On the Select an action page, select Save and run once, and click Finish. On the Run with options page, accept the defaults, and click Run, and then click OK.Select View the details of this import after closing this window and click OK. In IBM Cognos Administration, click Home.The content is available in Public FoldersCSP_CustomerAnalytics_BIContent_ModelCSP_CustomerAnalyticsCSP_CustomerAnalytics_Analysis_Report.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Deploying the IBM Cognos BI reports

You use IBM Cognos Administration to deploy the reports.

Before you begin

Ensure that CSP_CustomerAnalytics_BIContent.zip is in the Cognos_install_location/Deployment folder on the Business Intelligence node.

Procedure

Open a web browser on the Business Intelligence node.

Go to the IBM Cognos BI portal URL. For example, go to http://cognos node/ibmcognos/.

On the Welcome page, click Administer IBM Cognos Content.

Click the Configuration tab, and then click Content Administration.

On the toolbar, click New Import.

In the Deployment Archive pane, select deployment archive (CSP_CustomerAnalytics_BIContent.zip), and click Next.

In the Specify a name and description pane, accept the default or enter a new name, and click Next.

In the Select the public folders and directory content pane, select all of the packages in the table, leave the Options as default, ensure that the Disable after import option is unselected, and click Next.

In the Specify the general options pane, accept the defaults, and click Next.

On the Review the summary page, click Next.

On the Select an action page, select Save and run once, and click Finish.

On the Run with options page, accept the defaults, and click Run, and then click OK.

Select View the details of this import after closing this window and click OK.

In IBM Cognos Administration, click Home. The content is available in Public Folders > CSP_CustomerAnalytics_BIContent_Model > CSP_CustomerAnalytics > CSP_CustomerAnalytics_Analysis_Report.

Parent topic: Installation and configuration

Installing the Analytics PlatformThe Analytics Platform is software that is installed on your Analytics Platform nodes. It manages the creation of your data sets in the Apache Hadoop ecosystem. Analytics Platform allows deployment of data sets and management of those data sets, which makes up the basis of your solution. Analytics Platformvedia componentTo install and configure the Analytics Platform, refer to the Analytics Platform Installation and Configuration Guide for CSP Solutions available from the following location: http://www-01.ibm.com/support/docview.wss?uid=swg27046047This document describes the installation and configuration of Analytics Platform software and data sets for Communication Service Provider (CSP) solutions. It includes operations that are required to be performed on your Analytics Platform nodes in your deployment.In the context of the Customer Experience Analytics for Communication Service Providers solution, the BigInsights master node is one of the Analytics Platform nodes.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Installing the Analytics Platform

The Analytics Platform is software that is installed on your Analytics Platform nodes. It manages the creation of your data sets in the Apache Hadoop ecosystem. Analytics Platform allows deployment of data sets and management of those data sets, which makes up the basis of your solution.

To install and configure the Analytics Platform, refer to the Analytics Platform Installation and Configuration Guide for CSP Solutions available from the following location: http://www-01.ibm.com/support/docview.wss?uid=swg27046047

This document describes the installation and configuration of Analytics Platform software and data sets for Communication Service Provider (CSP) solutions. It includes operations that are required to be performed on your Analytics Platform nodes in your deployment.

In the context of the Customer Experience Analytics for Communication Service Providers solution, the BigInsights master node is one of the Analytics Platform nodes.

Parent topic: Installation and configuration

Creating a data source connection to the BigInsights databaseYou must create a data source connection from the Business Intelligence node to the IBM BigInsights database that is on the Analytics Platform node.data source connectionBigInsights databaseOpen a web browser on the BI node.Go to the IBM Cognos BI portal URL.For example, go to http://cognos node/ibmcognos.On the Welcome page, click Administer IBM Cognos Content. Click the Configuration tab, and then click Data Source Connections. Click New Data Source.In the Name field, type BigDataDb2 (or BigDataDb3 if you already have a BigDataDb2 connection), and then click Next.From the Type list, select JDBC. Ensure that Configure JDBC connection is selected and click Next.From the Type list, select IBM InfoSphere BigInsights (Big SQL). Locate the connection information for the JDBC URL field in the image shown in step 8. To find the connection settings on the Apache Ambari tool, click Services, then click BigInsights - Big SQL. Click the Configs tab, and note the db2_port_number. Click the Summary tab.To locate the server name, click the link for the Big SQL Head node. On a multi-node installation, only the head nodes can be queried. The node name appears below the Ambari banner, in this case hadoop2.com: Using the information from steps 10-14, on the Specify the JDBC connection string page, specify the server name, port number, and database name.Click Test the connection, then click Test.On the View the results page, the status of the connection tests for the dynamic query mode is Succeeded.Click Close, click Close again, and then click Finish.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Creating a data source connection to the BigInsights database

You must create a data source connection from the Business Intelligence node to the IBM® BigInsights® database that is on the Analytics Platform node.

Procedure

Open a web browser on the BI node.

Go to the IBM Cognos® BI portal URL. For example, go to http://cognos node/ibmcognos.

On the Welcome page, click Administer IBM Cognos Content.

Click the Configuration tab, and then click Data Source Connections.

Click New Data Source.

In the Name field, type BigDataDb2 (or BigDataDb3 if you already have a BigDataDb2 connection), and then click Next.The IM Cognos Administration page, showing Data Source Connections fields: Name, Description (left blank), Screen Tip (left blank), and directory Location (Cognos).

From the Type list, select JDBC. Ensure that Configure JDBC connection is selected and click Next.Data Source Connections page, showing a Type pulldown menu, isolation level (already selected), and Configure JDBC connection check box.

From the Type list, select IBM InfoSphere BigInsights (Big SQL).

Locate the connection information for the JDBC URL field in the image shown in step 8.

To find the connection settings on the Apache Ambari tool, click Services, then click BigInsights - Big SQL.

Click the Configs tab, and note the db2_port_number.

Click the Summary tab.

To locate the server name, click the link for the Big SQL Head node.

Note: On a multi-node installation, only the head nodes can be queried.

The node name appears below the Ambari banner, in this case hadoop2.com:

Using the information from steps 10-14, on the Specify the JDBC connection string page, specify the server name, port number, and database name.

Click Test the connection, then click Test. On the View the results page, the status of the connection tests for the dynamic query mode is Succeeded.

Click Close, click Close again, and then click Finish.

Parent topic: Installation and configuration

Installing the SLM tagging functionalityYou can deploy the slm tagging functionality on the Analytics Platform node.A RPM Package Manager (RPM) is contained in the rapidanalytics/build/slm/ci-slm-deployment-1.0.0.rpm folder. To install this RPM, follow these steps:Install the SLM via the RPM installer by typing the following command: rpm -i bis-main-2*.rpmThe files will be copied to /opt/tnf/apps/slm.Running SLM tagging:A Cron job needs to be created that runs the SLM tagging command daily, just after midnight:java -cp /opt/tnf/apps/slm/lib/log4j-1.2.16.jar:/opt/tnf/apps/slm/lib/* com.tnf.slm.SlmMain The SLM tagging process appends to a log file in the directory, with the extension .slmtag: /opt/tnf/apps/slm/log/<log file>.slmtag This log file is used by IBM to ensure that the product is being used according to its license.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Installing the SLM tagging functionality

You can deploy the slm tagging functionality on the Analytics Platform node.

About this task

A RPM Package Manager (RPM) is contained in the rapidanalytics/build/slm/ci-slm-deployment-1.0.0.rpm folder. To install this RPM, follow these steps:

Procedure

Install the SLM via the RPM installer by typing the following command:

rpm -i bis-main-2*.rpm

The files will be copied to /opt/tnf/apps/slm.

Running SLM tagging:

A Cron job needs to be created that runs the SLM tagging command daily, just after midnight:

java -cp /opt/tnf/apps/slm/lib/log4j-1.2.16.jar:/opt/tnf/apps/slm/lib/* com.tnf.slm.SlmMain

The SLM tagging process appends to a log file in the directory, with the extension .slmtag: /opt/tnf/apps/slm/log/<log file>.slmtag

This log file is used by IBM to ensure that the product is being used according to its license.

Parent topic: Installation and configuration

Installation and configuration of the Mediation node Mediation software is deployed on the mediation nodes in your deployment, manages the loading and aggregation of your telecommunication (telco) data into the Apache Hadoop ecosystem, and works in conjunction with the Analytics Platform. The mediation software works with the Infosphere Streams software installed on your mediation nodes. It manages the loading and key performance indicator (kpi) calculation of your telco data and prepares the data for analysis by the end user. The volume of data to be analyzed will determine how many mediation nodes are required in your platform.installationMediation nodeMediation nodevedia componentmediationvedia component To install and configure the Mediation node, you will need to reference information on Analytics Platform 2.0.This information includes the following:installation prerequisitesRPM installationVedia Supercollector installationstreams domain and instance configurationcustomizationadministrationTo perform these operations, refer to the Analytics Platform Mediation Installation and Configuration Guide for CSP Solutions available from the Industry Solutions Customer Intelligence Solutions version 1.0 documentation web page. This document provides information regarding installation, deployment, configuration, and maintenance of the mediation layer of Analytics Platform 2.0. This platform is similar to Analytics Platform 1.0, except that 2.0 is Streams-based and 1.0 is Vedia-based.The mediation solutions include the following components:Supercollector (Vedia-based)Lookup Manager (Streams-based)ITE Application to produce 5 minute aggregations (Streams-based)Raw TDR processing Application (Streams-based)DB Loader Application (Streams-based)Please note that the Analytics Platform Mediation Installation and Configuration Guide for CSP Solutions will not cover the installation of the Streams platform, which is a prerequisite for the application deployment. Also, the Hadoop installation and Hadoop-based aggregation are not covered in the document.Installation and configurationThe IBM Customer Experience Analytics for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Installation and configuration of the Mediation node

Mediation software is deployed on the mediation nodes in your deployment, manages the loading and aggregation of your telecommunication (telco) data into the Apache Hadoop ecosystem, and works in conjunction with the Analytics Platform. The mediation software works with the Infosphere Streams software installed on your mediation nodes. It manages the loading and key performance indicator (kpi) calculation of your telco data and prepares the data for analysis by the end user. The volume of data to be analyzed will determine how many mediation nodes are required in your platform.

To install and configure the Mediation node, you will need to reference information on Analytics Platform 2.0.

This information includes the following:

installation prerequisites

RPM installation

Vedia Supercollector installation

streams domain and instance configuration

customization

administration

To perform these operations, refer to the Analytics Platform Mediation Installation and Configuration Guide for CSP Solutions available from the Industry Solutions Customer Intelligence Solutions version 1.0 documentation web page.

This document provides information regarding installation, deployment, configuration, and maintenance of the mediation layer of Analytics Platform 2.0. This platform is similar to Analytics Platform 1.0, except that 2.0 is Streams-based and 1.0 is Vedia-based.

The mediation solutions include the following components:

Supercollector (Vedia-based)

Lookup Manager (Streams-based)

ITE Application to produce 5 minute aggregations (Streams-based)

Raw TDR processing Application (Streams-based)

DB Loader Application (Streams-based)

Please note that the Analytics Platform Mediation Installation and Configuration Guide for CSP Solutions will not cover the installation of the Streams platform, which is a prerequisite for the application deployment. Also, the Hadoop installation and Hadoop-based aggregation are not covered in the document.

Parent topic: Installation and configuration

Using Customer Experience Analytics for Communications Service ProvidersThis section describes a typical user case that shows how to use the Customer Experience Analytics for Communication Service Providers solution to understand customer experience trends. Workflow and user roles This workflow shows how the solution can be used to thoroughly provide a dashboard and key metrics to a communication service provider. For this example, a customer experience team member is interested in understanding customer experience trends. This person has also been asked to investigate a specific customer complaint. A typical process workflow is described Using the Customer Experience DashboardThe Customer Experience Analytics for Communication Service Providers solution provides in-depth analytics to help communication service providers evaluate customer experience trends and metrics.

Using Customer Experience Analytics for Communications Service Providers

This section describes a typical user case that shows how to use the Customer Experience Analytics for Communication Service Providers solution to understand customer experience trends.

Workflow and user roles

This workflow shows how the solution can be used to thoroughly provide a dashboard and key metrics to a communication service provider.

For this example, a customer experience team member is interested in understanding customer experience trends. This person has also been asked to investigate a specific customer complaint. A typical process workflow is described

Using the Customer Experience Dashboard
The Customer Experience Analytics for Communication Service Providers solution provides in-depth analytics to help communication service providers evaluate customer experience trends and metrics.

Using the Customer Experience DashboardThe Customer Experience Analytics for Communication Service Providers solution provides in-depth analytics to help communication service providers evaluate customer experience trends and metrics.Customer Experience DashboardThis task describes how a typical customer experience team member would use the dashboard to evaluate customer trends and metrics, as well as investigate a specific customer complaint. The screen shots shown are for example purposes and will vary depending on your particular implementation. Open the Customer Experience Dashboard for the past week. The metrics for the past week include dropped call rate and unacceptable web experience.Click to view the Unacceptable Experience Trend report. The communications service provider has an SLA of 4.5%. The customer experience team member investigates why the SLA went above that level on Monday and Friday. The team member looks at the reports in the menu on the left-hand side of the screen.Click to view the Dropped Calls Trend Overview report.The bar chart shows the number of dropped calls and the line chart shows a corresponding dropped call rate. The report below the chart includes the number of affected customers. The dropped call rate on Monday and Friday was particularly high and may warrant further investigation.Click through the (Video Experience) and (Web Experience) reports on the left-hand menu. Click to view the Device Data Usage Distribution report. The bar chart shows the total volume and average volume per user of the top ten devices by average volume per user. The report below the chart includes the number of unique users. The average volume per user of Nokia Luria 920 and BlackBerry Q10 users is particularly high, and the total volume of Apple iPhone 4 users is much higher than any other device. Click to view the Application Data Usage Distribution report.The bar chart shows the total volume and average volume per user of the top ten applications by average volume per user. The report below the chart includes the number of unique users. The average volume per user of Sopcast is particularly high, and the total volume of Netflix Video users is higher than any other device.Click to view the Single Customer Experience Analysis report.The report provides a high level overview of a subscriber's activity. The experience section of the report can be filtered to show only a specific type of experience, such as Video Experience. The cells section of the report can show either Top Cells by Call (for voice) or Top Cells by Volume (for data).Using Customer Experience Analytics for Communications Service ProvidersThis section describes a typical user case that shows how to use the Customer Experience Analytics for Communication Service Providers solution to understand customer experience trends.

Using the Customer Experience Dashboard

The Customer Experience Analytics for Communication Service Providers solution provides in-depth analytics to help communication service providers evaluate customer experience trends and metrics.

About this task

This task describes how a typical customer experience team member would use the dashboard to evaluate customer trends and metrics, as well as investigate a specific customer complaint. The screen shots shown are for example purposes and will vary depending on your particular implementation.

Procedure

Open the Customer Experience Dashboard for the past week. The metrics for the past week include dropped call rate and unacceptable web experience.Dashboard showing 14% unacceptable, 3.0% dropped call rate, 3.0% rate of customers with more than three dropped calls, 19.0% unacceptable video experience, and 14.0% unacceptable web experience.

Click Icon for the Unacceptable Experience Trend report. to view the Unacceptable Experience Trend report.

The communications service provider has an SLA of 4.5%. The customer experience team member investigates why the SLA went above that level on Monday and Friday. The team member looks at the reports in the menu on the left-hand side of the screen.

Click Icon for the Dropped Calls Trend Overview report. to view the Dropped Calls Trend Overview report.

The bar chart shows the number of dropped calls and the line chart shows a corresponding dropped call rate. The report below the chart includes the number of affected customers. The dropped call rate on Monday and Friday was particularly high and may warrant further investigation.

Click through the Icon for the Video Experience report. (Video Experience) and Icon for the Web Experience report. (Web Experience) reports on the left-hand menu.

Click Icon for the Device Data Usage Distribution report. to view the Device Data Usage Distribution report. Bar chart showing Nokia Lumia 920 and BlackBerry Q10 with the highest average volume per user, and Apple iPhone 4 with the highest total volume.

The bar chart shows the total volume and average volume per user of the top ten devices by average volume per user. The report below the chart includes the number of unique users. The average volume per user of Nokia Luria 920 and BlackBerry Q10 users is particularly high, and the total volume of Apple iPhone 4 users is much higher than any other device.

Click Icon for the Application Data Usage Distribution report. to view the Application Data Usage Distribution report.Bar chart showing Sopcast with the highest average volume per user of 1.9 GB, and Netflix Video with the highest total volume of 10,710.80 GB.

The bar chart shows the total volume and average volume per user of the top ten applications by average volume per user. The report below the chart includes the number of unique users. The average volume per user of Sopcast is particularly high, and the total volume of Netflix Video users is higher than any other device.

Click Icon for the Single Customer Experience Analysis report. to view the Single Customer Experience Analysis report.

The report provides a high level overview of a subscriber's activity.

The experience section of the report can be filtered to show only a specific type of experience, such as Video Experience.

The cells section of the report can show either Top Cells by Call (for voice) or Top Cells by Volume (for data).

Parent topic: Using Customer Experience Analytics for Communications Service Providers

Accessibility features Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products. accessibilityFor 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).

The data provision toolThe data provision tool loads, deletes, and exports data from the provision tables. The provision tables contain customer relationship management data.data provision tooldata provision tablesloadingcustomer relationship dataconfiguration files db2_connection.propertiesThe data provision tool is installed in the /opt/tnf/apps/bis-main-var/bisprovisioning-tool folder and consists of the following parts: load.shLoads and updates provision tables. load-all.shChecks all the files in the .csv folder and loads them at the same time.delete.shReads records from input files and deletes records from IBM InfoSphere BigInsights by using key values.export.shExports records from IBM InfoSphere BigInsights to text files.Usage You must specify key values for all operations. The key field names are obtained by the provision tools from the table metadata. The primary key must be defined in table DDL. In the following examples the primary key field is tac:create table device ( tac varchar(32) primary key, model varchar(64), vendor varchar (64) ); The follow example contains two primary keys:create table device ( tac varchar(32), model varchar(64), vendor varchar (64), primary key (tac, model) ); To see the parameters for load.sh type, the script name with no parameters in a command-line window: Usage: load.sh [options] Options: * --file, -f CSV file with data * --table, -t DB Table name--file, -fA list of input files that are separated by the pipe (|) character.--table, -tThe table name. The table name can include a dot separated schema. For example, load.sh -f device.csv -t device. delete.sh and export.sh take the same parameters. The data provision tool reads table metadata and converts the input text file into an Apache Parquet or plain text formatted file and populates specified table with the data. It updates existing records and inserts new records.Creating dictionary tables Run the /opt/tnf/apps/bis-main/bis-dbconfig/install-db.sh script with table group name parameters. The script /opt/tnf/apps/bis-main/bis-main.sh creates a dictionary table in the database when it starts. You cannot modify the data in IBM InfoSphere BigInsights directly. The data provision tool updates the database tables and exports them to IBM InfoSphere BigInsights. During the export stage, the data provision tool must know the storage format. Apache Parquet and plain text formats are supported. Update the storage format in the/opt/tnf/apps/bis-main/bis-tools/bisprovisioning-tool/cfg/hive-storage.properties file. Input files The data input format is a pipe (|) separated utf-8 encoded plain text file with headers. The header can start with a number sign (#). Header values must match the dictionary table case insensitive field names. For example, TAC|MODEL|VENDOR 12345678|Zamyang|CiaobaoConfiguration files The data provision tool IBM DB2 database configuration location is /opt/tnf/apps/bis-main-var/bis-demon/cfg/db2_connection.properties. For example, db.url=jdbc:db2://localhost:50000/tnfbis db.user=catalog db.password=db2where db.url is the JDBC URL string of the database, db.user is the database user ID, and db.password is the database password.

The data provision tool

The data provision tool loads, deletes, and exports data from the provision tables. The provision tables contain customer relationship management data.

The data provision tool is installed in the /opt/tnf/apps/bis-main-var/bisprovisioning-tool folder and consists of the following parts:

load.sh

Loads and updates provision tables.

load-all.sh

Checks all the files in the .csv folder and loads them at the same time.

delete.sh

Reads records from input files and deletes records from IBM® InfoSphere® BigInsights® by using key values.

export.sh

Exports records from IBM InfoSphere BigInsights to text files.

Usage

You must specify key values for all operations. The key field names are obtained by the provision tools from the table metadata. The primary key must be defined in table DDL. In the following examples the primary key field is tac:

create table device (
tac varchar(32) primary key, model varchar(64),
vendor varchar (64)
);

The follow example contains two primary keys:

create table device (
tac varchar(32),
model varchar(64), vendor varchar (64), primary key (tac, model)
);

To see the parameters for load.sh type, the script name with no parameters in a command-line window:

Usage: load.sh [options] Options:
* --file, -f
CSV file with data * --table, -t
DB Table name

--file, -f

A list of input files that are separated by the pipe (|) character.

--table, -t

The table name. The table name can include a dot separated schema. For example, load.sh -f device.csv -t device.

delete.sh and export.sh take the same parameters.

The data provision tool reads table metadata and converts the input text file into an Apache Parquet or plain text formatted file and populates specified table with the data. It updates existing records and inserts new records.

Creating dictionary tables

Run the /opt/tnf/apps/bis-main/bis-dbconfig/install-db.sh script with table group name parameters. The script /opt/tnf/apps/bis-main/bis-main.sh creates a dictionary table in the database when it starts.

You cannot modify the data in IBM InfoSphere BigInsights directly. The data provision tool updates the database tables and exports them to IBM InfoSphere BigInsights. During the export stage, the data provision tool must know the storage format. Apache Parquet and plain text formats are supported. Update the storage format in the/opt/tnf/apps/bis-main/bis-tools/bisprovisioning-tool/cfg/hive-storage.properties file.

Input files

The data input format is a pipe (|) separated utf-8 encoded plain text file with headers. The header can start with a number sign (#). Header values must match the dictionary table case insensitive field names. For example,

TAC|MODEL|VENDOR
12345678|Zamyang|Ciaobao

Configuration files

The data provision tool IBM DB2 database configuration location is /opt/tnf/apps/bis-main-var/bis-demon/cfg/db2_connection.properties. For example,

db.url=jdbc:db2://localhost:50000/tnfbis
db.user=catalog
db.password=db2

where db.url is the JDBC URL string of the database, db.user is the database user ID, and db.password is the database password.

TroubleshootingThis section contains troubleshooting information for the Customer Experience Analytics for Communication Service Providers installation.troubleshootingTroubleshooting a problemTroubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.

Troubleshooting

This section contains troubleshooting information for the Customer Experience Analytics for Communication Service Providers installation.

Troubleshooting a problem
Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.

Troubleshooting a problemTroubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.troubleshootingReview the following table to help you or customer support resolve a problem.Troubleshooting actions and descriptionsActionsDescriptionA product fix might be available to resolve your problem.Apply all known fix packs, or service levels, or program temporary fixes (PTF).Look up error messages by selecting the product from the IBM Support Portal, and then typing the error message code into the Search support box (http://www.ibm.com/ support/entry/portal/).Error messages give important information to help you identify the component that is causing the problem.Reproduce the problem to ensure that it is not just a simple error.If samples are available with the product, you might try to reproduce the problem by using the sample data.Ensure that the installation successfully finished.The installation location must contain the appropriate file structure and the file permissions. For example, if the product requires write access to log files, ensure that the directory has the correct permission.Review all relevant documentation, including release notes, technotes, and proven practices documentation.Search the IBM Knowledge Center to determine whether your problem is known, has a workaround, or if it is already resolved and documented.Review recent changes in your computing environment.Sometimes installing new software might cause compatibility issues.If the items in the table did not guide you to a resolution, you might need to collect diagnostic data. This data is necessary for an IBM technical-support representative to effectively troubleshoot and assist you in resolving the problem.TroubleshootingThis section contains troubleshooting information for the Customer Experience Analytics for Communication Service Providers installation.Troubleshooting resourcesTroubleshooting resources are sources of information that can help you resolve a problem that you are having with an IBM product.Troubleshooting the FTP collection of files in Analytics PlatformThere are solutions for known issues in the FTP collection of files in Analytics Platform. After the solution installer is run, Chef processes are still running after the cleanup.sh script is executedAfter the cleanup.sh script is run on the solution installer node, all Chef processes should be terminated. However, in some cases Chef processes are still running.

Troubleshooting a problem

Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.

Review the following table to help you or customer support resolve a problem.

Table 1. Troubleshooting actions and descriptions.

Actions | Description
A product fix might be available to resolve your problem. | Apply all known fix packs, or service levels, or program temporary fixes (PTF).
Look up error messages by selecting the product from the IBM® Support Portal, and then typing the error message code into the Search support box (http://www.ibm.com/ support/entry/portal/). | Error messages give important information to help you identify the component that is causing the problem.
Reproduce the problem to ensure that it is not just a simple error. | If samples are available with the product, you might try to reproduce the problem by using the sample data.
Ensure that the installation successfully finished. | The installation location must contain the appropriate file structure and the file permissions. For example, if the product requires write access to log files, ensure that the directory has the correct permission.
Review all relevant documentation, including release notes, technotes, and proven practices documentation. | Search the IBM Knowledge Center to determine whether your problem is known, has a workaround, or if it is already resolved and documented.
Review recent changes in your computing environment. | Sometimes installing new software might cause compatibility issues.

If the items in the table did not guide you to a resolution, you might need to collect diagnostic data. This data is necessary for an IBM technical-support representative to effectively troubleshoot and assist you in resolving the problem.

Troubleshooting resources
Troubleshooting resources are sources of information that can help you resolve a problem that you are having with an IBM product.

Troubleshooting the FTP collection of files in Analytics Platform
There are solutions for known issues in the FTP collection of files in Analytics Platform.

After the solution installer is run, Chef processes are still running after the cleanup.sh script is executed
After the cleanup.sh script is run on the solution installer node, all Chef processes should be terminated. However, in some cases Chef processes are still running.

Parent topic: Troubleshooting

Troubleshooting resourcesIBM Predictive Customer Intelligence | Troubleshooting resourcesTroubleshooting resources are sources of information that can help you resolve a problem that you are having with an IBM product.troubleshootingresourcesSupport PortalThe IBM Support Portal is a unified, centralized view of all technical support tools and information for all IBM systems, software, and services. The IBM Support Portal lets you access all the IBM support resources from one place. You can tailor the pages to focus on the information and resources that you need for problem prevention and faster problem resolution. Familiarize yourself with the IBM Support Portal by viewing the demo videos (https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos). Find the content that you need by selecting your products from the IBM Support Portal (http://www.ibm.com/support/entry/portal).Before contacting IBM Support, you will need to collect diagnostic data (system information, symptoms, log files, traces, and so on) that is required to resolve a problem. Gathering this information will help to familiarize you with the troubleshooting process and save you time.Service requestService requests are also known as Problem Management Reports (PMRs). Several methods exist to submit diagnostic information to IBM Software Technical Support.To open a PMR or to exchange information with technical support, view the IBM Software Support Exchanging information with Technical Support page (http://www.ibm.com/software/support/exchangeinfo.html).Fix CentralFix Central provides fixes and updates for your system's software, hardware, and operating system.Use the pull-down menu to navigate to your product fixes on Fix Central (http://www.ibm.com/systems/support/fixes/en/fixcentral/help/getstarted.html). You may also want to view Fix Central help.IBM developerWorksIBM developerWorks provides verified technical information in specific technology environments.As a troubleshooting resource, developerWorks provides easy access to the most popular practices, in addition to videos and other information: developerWorks (http://www.ibm.com/developerworks).IBM RedbooksIBM Redbooks are developed and published by the IBM International Technical Support Organization, the ITSO. IBM Redbooks (http://www.redbooks.ibm.com) provide in-depth guidance about such topics as installation and configuration and solution implementation.Software support and RSS feedsIBM Software Support RSS feeds are a quick, easy, and lightweight format for monitoring new content added to websites.After you download an RSS reader or browser plug-in, you can subscribe to IBM product feeds at IBM Software Support RSS feeds (https://www.ibm.com/software/support/rss).Log filesLog files can help you troubleshoot problems by recording the activities that take place when you work with a product.Error messagesThe first indication of a problem is often an error message. Error messages contain information that can be helpful in determining the cause of a problem.Troubleshooting a problemTroubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.

Troubleshooting resources

Troubleshooting resources are sources of information that can help you resolve a problem that you are having with an IBM® product.

Support Portal

The IBM Support Portal is a unified, centralized view of all technical support tools and information for all IBM systems, software, and services.

The IBM Support Portal lets you access all the IBM support resources from one place. You can tailor the pages to focus on the information and resources that you need for problem prevention and faster problem resolution. Familiarize yourself with the IBM Support Portal by viewing the demo videos (https://www.ibm.com/blogs/SPNA/entry/the_ibm_support_portal_videos).

Find the content that you need by selecting your products from the IBM Support Portal (http://www.ibm.com/support/entry/portal).

Before contacting IBM Support, you will need to collect diagnostic data (system information, symptoms, log files, traces, and so on) that is required to resolve a problem. Gathering this information will help to familiarize you with the troubleshooting process and save you time.

Service request

Service requests are also known as Problem Management Reports (PMRs). Several methods exist to submit diagnostic information to IBM Software Technical Support.

To open a PMR or to exchange information with technical support, view the IBM Software Support Exchanging information with Technical Support page (http://www.ibm.com/software/support/exchangeinfo.html).

Fix Central

Fix Central provides fixes and updates for your system's software, hardware, and operating system.

Use the pull-down menu to navigate to your product fixes on Fix Central (http://www.ibm.com/systems/support/fixes/en/fixcentral/help/getstarted.html). You may also want to view Fix Central help.

IBM developerWorks

IBM developerWorks® provides verified technical information in specific technology environments.

As a troubleshooting resource, developerWorks provides easy access to the most popular practices, in addition to videos and other information: developerWorks (http://www.ibm.com/developerworks).

IBM Redbooks

IBM Redbooks® are developed and published by the IBM International Technical Support Organization, the ITSO.

IBM Redbooks (http://www.redbooks.ibm.com) provide in-depth guidance about such topics as installation and configuration and solution implementation.

Software support and RSS feeds

IBM Software Support RSS feeds are a quick, easy, and lightweight format for monitoring new content added to websites.

After you download an RSS reader or browser plug-in, you can subscribe to IBM product feeds at IBM Software Support RSS feeds (https://www.ibm.com/software/support/rss).

Log files

Log files can help you troubleshoot problems by recording the activities that take place when you work with a product.

Error messages

The first indication of a problem is often an error message. Error messages contain information that can be helpful in determining the cause of a problem.

Parent topic: Troubleshooting a problem

Troubleshooting the FTP collection of files in Analytics PlatformThere are solutions for known issues in the FTP collection of files in Analytics Platform. Analytics Platformtroubleshootingtransaction data record (TDR)configuration filesVediamain.cfgCollection.xmlOn Analytics Platform mediation nodes, the function in Analytics Platform that collects transaction data record (TDR) files for storage in Analytics Platform is Vedia. To verify that the collection of TDRs from the CSP probe or probes is working, note that each probe's collector will be defined in mediation. Use the secure shell (SSH) to connect to the correct collector. The allocation of collectors can be found in the file Vediamain.cfg at /opt/tnf/apps/vedia/cfg/Vediamain.cfg.To check FileLoader logs, the format is logs/Collection_1/FileLoader092708.log.When the application is running, messages would appear in the following format. For this example, Vedia is comparing TDRs in tmp against files on the probe: [CFileListJob::GetNewFilesList] [TaskTest] Getting list of /var/opt/tnf/tdrs/ *.* [CFileListJob::GetNewFilesList] [TaskTest] Files: 196, Match: 182, Old: 178The files that are being collected correctly are shown in the following example:[CFileDownloadJob::Process] Task - downloading midas/netrofeed/netro_20130918200012.log.gz [CFileDownloadJob::Process] Task - download netro_20130918200012.log.gz (9600142) [CProbe::Store] Save: /opt/tnf/apps/vedia/tmp/Collection_1_FileLoader.dat [CFileListJob::Save] LastListTime: 20130918200012, Files: 664 [CFileListJob::GetNewFilesList] [Task] Getting list of midas/netrofeed/ *.* [CFileListJob::GetNewFilesList] [Task] Files: 251, Match: 223, Old: 221 [CFileDownloadJob::Process] Task - downloading midas/netrofeed/netro_20130918200015.log.gz [CFileDownloadJob::Process] Task - download netro_20130918200015.log.gz (9013063)In contrast, the following is an example of a file that can no longer connect to a probe. Typically, if FTP is not working, the ports are not open, permissions are not set up correctly on the probe, the probe is down, or connectivity between the probe and mediation has dropped. FTP not working TO FIND example of ftp failing Full queues represent full applications within the chain. The following is an example of a file that has full queues somewhere along the chain. If one application is full, then the preceding application cannot output to the queue, thus impacting the queues (creating a knock-on effect). The queues will need be examined for skipping.1C8F - 19/09 11:00:55.200 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C8F - 19/09 11:01:00.242 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C91 - 19/09 11:01:00.461 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C8F - 19/09 11:01:05.402 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C8F - 19/09 11:01:10.431 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C8F - 19/09 11:01:15.482 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C8F - 19/09 11:01:20.642 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C8F - 19/09 11:01:25.838 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C91 - 19/09 11:01:30.525 - [CFileListJob::GetNewFilesList] Skip getting of files list 1C8F - 19/09 11:01:31.063 - [CFileListJob::GetNewFilesList] Skip getting of files list If skipping is noticed in Vedia logs and does not stop, restart Vedia. Some skipping will occur on restart, but wait up to five minutes for it to clear. It typically takes one to five minutes for the skipping messages to clear from the logs. Recommendations:When collecting files and Match is 0, the regex in the FileLoader configuration is incorrect. Review and correct this in the configuration steps. If FileLoader understands the files from the network to be Old, contact the person responsible for the production of network files to correct the date and time of the files. Occasionally, FTP jobs will fail to collect a file, but FileLoader will retry. Investigate situations where there are many failures, causing files that fail to be collected. Check the configuration and verify that the mediation node can reach the host of the network files (probe). If there is a network problem, contact the person responsible for the network files. When the configuration is correct and network connectivity is confirmed, restart the Vedia processes and ensure there are no further reported exceptions. Queues commonly will fill after a long outage period. Vedia will attempt to collect all files and process them immediately. The number of files is determined by a period of time and is set in Collection.xml. If the look back period is, for example, greater than 20 minutes and there are Skip getting of files list messages in the log, then reset the look back period. Carefully tune anything greater than 20. Do not simply increase to 300 minutes, as this can overload Vedia. The following is configured in Collection.xml:module name="FileLoader"id="FileLoader"> <probe name="FileLoader"log-file="FileLoader"log--process="2"> <files> <ftp id="Task"host="Data" url="ftp://{probe-ip}"port="21" user="{probe-user}"password="{probe-password}" remotedir="{probe-dir}"storagedir="tmp/data_{probe-no}" filename-regex="{probe-files_mask}" ftp-timeout="60"ftp-downloads="1"attempt-timeout="1" delete-processed="0"process-file-ignore-age="0" max-process-file-age="20"time-shift-="-3600" compression_="GNUZIP" start-format="{probe-file-date-format}" detection-interval="60"> </ftp> </files> <output name="LoadedFiles"model="File"limit="50"/> </probe> </module> process-file-ignore-age directs Vedia to load all the old files. Always set this to 0 in a production environment. max-process-file-age defines, in minutes, how old the files on the probe can be before they will be rejected as being too old. detection-interval indicates how often to check for files, in seconds. download-threads indicates how many threads to download with. Note that, if this is set cumulatively across all collectors to be a higher value than the probe can process, this may impact the probe and it may reject files. max-try indicates how many times to attempt to download a file. Troubleshooting a problemTroubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.

Troubleshooting the FTP collection of files in Analytics Platform

There are solutions for known issues in the FTP collection of files in Analytics Platform.

On Analytics Platform mediation nodes, the function in Analytics Platform that collects transaction data record (TDR) files for storage in Analytics Platform is Vedia.

To verify that the collection of TDRs from the CSP probe or probes is working, note that each probe's collector will be defined in mediation. Use the secure shell (SSH) to connect to the correct collector. The allocation of collectors can be found in the file Vediamain.cfg at /opt/tnf/apps/vedia/cfg/Vediamain.cfg.

To check FileLoader logs, the format is logs/Collection_1/FileLoader092708.log.

When the application is running, messages would appear in the following format. For this example, Vedia is comparing TDRs in tmp against files on the probe:

[CFileListJob::GetNewFilesList] [TaskTest] Getting list of /var/opt/tnf/tdrs/ *.*
[CFileListJob::GetNewFilesList] [TaskTest] Files: 196, Match: 182, Old: 178

The files that are being collected correctly are shown in the following example:

[CFileDownloadJob::Process] Task - downloading midas/netrofeed/netro_20130918200012.log.gz
[CFileDownloadJob::Process] Task - download netro_20130918200012.log.gz (9600142)
[CProbe::Store] Save: /opt/tnf/apps/vedia/tmp/Collection_1_FileLoader.dat
[CFileListJob::Save] LastListTime: 20130918200012, Files: 664
[CFileListJob::GetNewFilesList] [Task] Getting list of midas/netrofeed/ *.*
[CFileListJob::GetNewFilesList] [Task] Files: 251, Match: 223, Old: 221
[CFileDownloadJob::Process] Task - downloading midas/netrofeed/netro_20130918200015.log.gz
[CFileDownloadJob::Process] Task - download netro_20130918200015.log.gz (9013063)

In contrast, the following is an example of a file that can no longer connect to a probe. Typically, if FTP is not working, the ports are not open, permissions are not set up correctly on the probe, the probe is down, or connectivity between the probe and mediation has dropped.

FTP not working

TO FIND example of ftp failing

Full queues represent full applications within the chain. The following is an example of a file that has full queues somewhere along the chain. If one application is full, then the preceding application cannot output to the queue, thus impacting the queues (creating a knock-on effect). The queues will need be examined for skipping.

1C8F - 19/09 11:00:55.200 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C8F - 19/09 11:01:00.242 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C91 - 19/09 11:01:00.461 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C8F - 19/09 11:01:05.402 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C8F - 19/09 11:01:10.431 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C8F - 19/09 11:01:15.482 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C8F - 19/09 11:01:20.642 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C8F - 19/09 11:01:25.838 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C91 - 19/09 11:01:30.525 - [CFileListJob::GetNewFilesList]
Skip getting of files list
1C8F - 19/09 11:01:31.063 - [CFileListJob::GetNewFilesList]
Skip getting of files list

If skipping is noticed in Vedia logs and does not stop, restart Vedia. Some skipping will occur on restart, but wait up to five minutes for it to clear. It typically takes one to five minutes for the skipping messages to clear from the logs.

Recommendations:

When collecting files and Match is 0, the regex in the FileLoader configuration is incorrect. Review and correct this in the configuration steps.

If FileLoader understands the files from the network to be Old, contact the person responsible for the production of network files to correct the date and time of the files.

Occasionally, FTP jobs will fail to collect a file, but FileLoader will retry. Investigate situations where there are many failures, causing files that fail to be collected. Check the configuration and verify that the mediation node can reach the host of the network files (probe). If there is a network problem, contact the person responsible for the network files.

When the configuration is correct and network connectivity is confirmed, restart the Vedia processes and ensure there are no further reported exceptions.

Queues commonly will fill after a long outage period. Vedia will attempt to collect all files and process them immediately. The number of files is determined by a period of time and is set in Collection.xml. If the look back period is, for example, greater than 20 minutes and there are Skip getting of files list messages in the log, then reset the look back period. Carefully tune anything greater than 20. Do not simply increase to 300 minutes, as this can overload Vedia.

The following is configured in Collection.xml:

module name="FileLoader"id="FileLoader">
  <probe name="FileLoader"log-file="FileLoader"log--process="2">
  <files>
    <ftp id="Task"host="Data"
    url="ftp://{probe-ip}"port="21"
    user="{probe-user}"password="{probe-password}"
    remotedir="{probe-dir}"storagedir="tmp/data_{probe-no}"
    filename-regex="{probe-files_mask}"
    ftp-timeout="60"ftp-downloads="1"attempt-timeout="1"
    delete-processed="0"process-file-ignore-age="0"
    max-process-file-age="20"time-shift-="-3600"
    compression_="GNUZIP"
    start-format="{probe-file-date-format}"
    detection-interval="60">
    </ftp>
  </files>
  <output name="LoadedFiles"model="File"limit="50"/>
  </probe>
</module>

process-file-ignore-age directs Vedia to load all the old files. Always set this to 0 in a production environment.

max-process-file-age defines, in minutes, how old the files on the probe can be before they will be rejected as being too old.

detection-interval indicates how often to check for files, in seconds.

download-threads indicates how many threads to download with. Note that, if this is set cumulatively across all collectors to be a higher value than the probe can process, this may impact the probe and it may reject files.

max-try indicates how many times to attempt to download a file.

Parent topic: Troubleshooting a problem

After the solution installer is run, Chef processes are still running after the cleanup.sh script is executedAfter the cleanup.sh script is run on the solution installer node, all Chef processes should be terminated. However, in some cases Chef processes are still running.troubleshootingcleanup.shIf you try to run the solution installer setup.sh file again, you might receive a message that required ports are in use, or creation of the chef user might fail.The solution to this issue is to reboot the installation node after you run the "cleanup.sh" script. This information applies only to the solution installer node and not the client/target nodes. The solution installer runs on the latest versions of Chrome and Firefox. It is not tested on Safari and does not run on Internet Explorer.Troubleshooting a problemTroubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.

After the solution installer is run, Chef processes are still running after the cleanup.sh script is executed

After the cleanup.sh script is run on the solution installer node, all Chef processes should be terminated. However, in some cases Chef processes are still running.

If you try to run the solution installer setup.sh file again, you might receive a message that required ports are in use, or creation of the chef user might fail.

The solution to this issue is to reboot the installation node after you run the "cleanup.sh" script.

Note: This information applies only to the solution installer node and not the client/target nodes.

Attention: The solution installer runs on the latest versions of Chrome and Firefox. It is not tested on Safari and does not run on Internet Explorer.

Parent topic: Troubleshooting a problem

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 Industry Customer Intelligence Solutions Version 1.0.0 and may also apply to subsequent releases. Copyright Licensed Materials - Property of IBM © Copyright IBM Corp. 2015, 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: 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. Notices

©

Product Information

This document applies to IBM Industry Customer Intelligence Solutions Version 1.0.0 and may also apply to subsequent releases.

Copyright

Licensed Materials - Property of IBM

© Copyright IBM Corp. 2015, 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:

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.

Parent topic: Notices