IntroductionThe Customer Insight 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 Insight for Communication Service Providers solution. It provides information on installation, configuration, and use of the Customer Insight 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 Insight 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 Insight 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 Customer Insight 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 Insight for Communication Service Providers solution. It provides information on installation, configuration, and use of the Customer Insight 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 Insight for Communication Service Providers have accessibility features. For more information, see Accessibility features.

Customer Insight 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.

OverviewThe IBM Customer Insight for Communication Service Providers is a prepackaged solution that works with IBM Predictive Customer Intelligence 1.1.1.solutionoverviewBefore you install the application, IBM Predictive Customer Intelligence 1.1.1 must be installed on your system.IBM Customer Insight for Communication Service Providers is a solution that drives improved marketing through advanced and predictive analytics of customer activity across locations, devices, applications, and interests. It highlights behavior-based information about customers using deep analysis of large volumes of raw and aggregate fixed line and mobile usage data, including internet usage and voice, and SMS activity.The solution also provides a churn management application, utilizing standard churn modelling factors, as well as voice, SMS, and mobile data records, to analyze trends in subscriber voice, SMS, and mobile data usage and to interpret the churn model.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?Why are our NPS (or T-NPS) so low?What segment of customers has the most negative or positive influence on NPS?What changes are required in order to improve NPS?What can be done to improve customers' satisfaction and happiness?What are the factors impacting subscriber churn?Who is most likely to churn in the next few months and why?Who are my most valuable customers? To help address these questions, IBM Customer Insight for Communication Service Providers is composed of three separate components: an NPS correlation model, predictive algorithm, and reporting suitea churn segmentation, scoring, and prediction modelan over-the-top applicationa user profile applicationa customer behavior and profile dataset What does the NPS correlation application provide? The solution helps customer experience team members in the telecommunications industry to determine customer insights by drilling down into Net Promoter Score (NPS) data and providing filters on key factors based on out-of-the-box correlations with network data. The NPS predictive index measures the likeliness of customers to recommend a company's offerings. It is used to gauge a customer's overall satisfaction and brand loyalty. IBM Customer Insight for Communication Service Providers analyzes subscribers' relative satisfaction or happiness with their service based on NPS. The solution allows users to drill down into the data to determine specific issues that correlate with negative NPS . The solution's metrics can be used to:proactively address key issues impacting churn and other issuesmeasure and correlate NPS with subscriber network experienceimprove customer experience and reduce attrition by improving their NPS The NPS correlation application includes an IBM Cognos user interface, which is described in the workflow procedure:a report of prioritized factors impacting transactional-NPS (T-NPS)the ability to quickly view the top factors that negatively affect T-NPS scores within appropriately grouped categories, such as customer, data activity, device, and locationaccess to various data sources to build the profiles of a typical promoter and detractor, which can be used to infer the profiles’ impact across the customer base, gauging NPS for all customers based on similar experiencecombining of data sets such as 2G, 3G, 4G LTE data, NPS survey results, cell, CRM, and device provisioning to create a single Subscriber Analytics Record for each subscriberpredictive models, which correlate subscriber analytics records to identify and address possible causes for poor NPSThe solution is delivered with predefined industry data models, use case specific metrics, and interactive reports.What does the churn management application provide? The churn management application provides an analysis of subscriber data suggesting how and when a customer is likely to churn. The application includes an IBM Cognos user interface, which is described in the workflow procedure:a churn overview providing a relative segmentation of subscribers, based on their churn likelihoodthe ability to filter subscribers based on key factors, including churn propensity, customer value (a "keep score"), predicted churn date, churn factors, and contract type The churn management application helps customer experience team members to understand subscriber experience trends across different "experience" categories, such as mobile data activity (including connectivity and retransmissions), voice, SMS, web browsing, and video. These inputs provide important insights into a subscriber’s experience and are valuable when attempting to predict churn. Furthermore, not all subscribers are equally valuable to Communication Service Providers. Therefore, this solution provides a “keep score” for each subscriber, using a scale of 1-100, with 100 being the most valuable.What does the over-the-top application provide? The over-the-top (OTT) application delivers pre-built out-of-the-box dashboards that Communication Service Providers can use to quickly visualize changing trends in how customers are using devices and applications. The dashboards can be filtered by relevant categories, such as price plan or application. Some of the key visualizations available on the OTT dashboards include the following: top 10 fastest growing OTT applications by volume usagetop 10 video, music, and voice/messaging applications by percentage of customerstop OTT applications by volume for the previous 7 daystop OTT applications by number of customerstop 20 applications by average daily volume top 20 devices by total volumepercentage customer change by application percentage customer change by devicepercentage volume change by deviceWhat does the user profile application provide?The user profile application gives Communication Service Provides the ability to view the type of customer profiles using their network. The dashboards can be filtered by relevant categories, such as mobility profile, age, gender, or device. Some of the key visualizations available are based on the number of subscribers and include the following:mobility profileage range genderusage profiledeviceThe application also provides a dashboard that can be filtered by IMSI, providing visualizations on :device usedmobility, usage, and experience profileshome, work, and weekend locationstop categories, domains, and interestsWhat does the customer behavior dataset provide? The customer behavior dataset is a set of tables customers can access, along with an accompanying data dictionary. The dataset contains subscribers' usage data, including their interests, preferences, and profile. The application analyzes the amount of time subscribers spend browsing, searching, reading, and streaming information on their devices. Each period of activity is categorized, where possible, into one of hundreds of interest categories, enabling communication service providers to categorize their subscribers into hundreds of different micro-segments based upon these interests.

Overview

The IBM® Customer Insight for Communication Service Providers is a prepackaged solution that works with IBM Predictive Customer Intelligence 1.1.1.

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

IBM Customer Insight for Communication Service Providers is a solution that drives improved marketing through advanced and predictive analytics of customer activity across locations, devices, applications, and interests. It highlights behavior-based information about customers using deep analysis of large volumes of raw and aggregate fixed line and mobile usage data, including internet usage and voice, and SMS activity.

The solution also provides a churn management application, utilizing standard churn modelling factors, as well as voice, SMS, and mobile data records, to analyze trends in subscriber voice, SMS, and mobile data usage and to interpret the churn model.

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?

Why are our NPS® (or T-NPS) so low?

What segment of customers has the most negative or positive influence on NPS?

What changes are required in order to improve NPS?

What can be done to improve customers' satisfaction and happiness?

What are the factors impacting subscriber churn?

Who is most likely to churn in the next few months and why?

Who are my most valuable customers?

To help address these questions, IBM Customer Insight for Communication Service Providers is composed of three separate components:

an NPS correlation model, predictive algorithm, and reporting suite

a churn segmentation, scoring, and prediction model

an over-the-top application

a user profile application

a customer behavior and profile dataset

What does the NPS correlation application provide?

The solution helps customer experience team members in the telecommunications industry to determine customer insights by drilling down into Net Promoter Score (NPS) data and providing filters on key factors based on out-of-the-box correlations with network data. The NPS predictive index measures the likeliness of customers to recommend a company's offerings. It is used to gauge a customer's overall satisfaction and brand loyalty.

IBM Customer Insight for Communication Service Providers analyzes subscribers' relative satisfaction or happiness with their service based on NPS. The solution allows users to drill down into the data to determine specific issues that correlate with negative NPS . The solution's metrics can be used to:

proactively address key issues impacting churn and other issues

measure and correlate NPS with subscriber network experience

improve customer experience and reduce attrition by improving their NPS

The NPS correlation application includes an IBM Cognos user interface, which is described in the workflow procedure:

a report of prioritized factors impacting transactional-NPS (T-NPS)

the ability to quickly view the top factors that negatively affect T-NPS scores within appropriately grouped categories, such as customer, data activity, device, and location

access to various data sources to build the profiles of a typical promoter and detractor, which can be used to infer the profiles’ impact across the customer base, gauging NPS for all customers based on similar experience

combining of data sets such as 2G, 3G, 4G LTE data, NPS survey results, cell, CRM, and device provisioning to create a single Subscriber Analytics Record for each subscriber

predictive models, which correlate subscriber analytics records to identify and address possible causes for poor NPS

The solution is delivered with predefined industry data models, use case specific metrics, and interactive reports.

What does the churn management application provide?

The churn management application provides an analysis of subscriber data suggesting how and when a customer is likely to churn. The application includes an IBM Cognos user interface, which is described in the workflow procedure:

a churn overview providing a relative segmentation of subscribers, based on their churn likelihood

the ability to filter subscribers based on key factors, including churn propensity, customer value (a "keep score"), predicted churn date, churn factors, and contract type

The churn management application helps customer experience team members to understand subscriber experience trends across different "experience" categories, such as mobile data activity (including connectivity and retransmissions), voice, SMS, web browsing, and video. These inputs provide important insights into a subscriber’s experience and are valuable when attempting to predict churn. Furthermore, not all subscribers are equally valuable to Communication Service Providers. Therefore, this solution provides a “keep score” for each subscriber, using a scale of 1-100, with 100 being the most valuable.

What does the over-the-top application provide?

The over-the-top (OTT) application delivers pre-built out-of-the-box dashboards that Communication Service Providers can use to quickly visualize changing trends in how customers are using devices and applications.

The dashboards can be filtered by relevant categories, such as price plan or application. Some of the key visualizations available on the OTT dashboards include the following:

top 10 fastest growing OTT applications by volume usage

top 10 video, music, and voice/messaging applications by percentage of customers

top OTT applications by volume for the previous 7 days

top OTT applications by number of customers

top 20 applications by average daily volume

top 20 devices by total volume

percentage customer change by application

percentage customer change by device

percentage volume change by device

What does the user profile application provide?

The user profile application gives Communication Service Provides the ability to view the type of customer profiles using their network.

The dashboards can be filtered by relevant categories, such as mobility profile, age, gender, or device. Some of the key visualizations available are based on the number of subscribers and include the following:

mobility profile

age range

gender

usage profile

device

The application also provides a dashboard that can be filtered by IMSI, providing visualizations on :

device used

mobility, usage, and experience profiles

home, work, and weekend locations

top categories, domains, and interests

What does the customer behavior dataset provide?

The customer behavior dataset is a set of tables customers can access, along with an accompanying data dictionary. The dataset contains subscribers' usage data, including their interests, preferences, and profile. The application analyzes the amount of time subscribers spend browsing, searching, reading, and streaming information on their devices. Each period of activity is categorized, where possible, into one of hundreds of interest categories, enabling communication service providers to categorize their subscribers into hundreds of different micro-segments based upon these interests.

Installation and configurationThe IBM Customer Insight for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.installationconfigurationsolutiontopologyCustomer Insight for Communication Service Providers consists of the following nodes: An Analytics Platform node.A Mediation node.A Business Intelligence node.A Predictive Analytics node.A data node.The IBM Predictive Customer Intelligence topology includes an Integration Bus node, which is not used in the Customer Insight for Communication Service Providers solution.Contents of the solution packageThe IBM Customer Insight 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 Insight for Communication Service Providers solution. Installing the Solution InstallerThe Solution Installer is used to configure and deploy solution content on the PCI-based nodes in your deployment, including the BI node and the Predictive Analytics node. To use the installer, you must first perform the prerequisites and then the steps for installing the Solution Installer. Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Installation and configuration

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

Customer Insight for Communication Service Providers consists of the following nodes:

An Analytics Platform node.

A Mediation node.

A Business Intelligence node.

A Predictive Analytics node.

A data node.

Note: The IBM Predictive Customer Intelligence topology includes an Integration Bus node, which is not used in the Customer Insight for Communication Service Providers solution.

Contents of the solution package
The IBM® Customer Insight 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 Insight for Communication Service Providers solution.

Installing the Solution Installer
The Solution Installer is used to configure and deploy solution content on the PCI-based nodes in your deployment, including the BI node and the Predictive Analytics node. To use the installer, you must first perform the prerequisites and then the steps for installing the Solution Installer.

Installing the solution content
Installing the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Contents of the solution packageThe IBM Customer Insight 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 SPSS Collaboration and Deployment Services packages. This is used for managing SPSS models used in the solution.IBM Cognos Business Intelligence (BI) reports and dashboards.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.Installation and configurationThe IBM Customer Insight for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.

Contents of the solution package

The IBM® Customer Insight 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 SPSS® Collaboration and Deployment Services packages. This is used for managing SPSS models used in the solution.

IBM Cognos® Business Intelligence (BI) reports and dashboards.

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 Insight for Communication Service Providers solution. installationoverviewThe following diagram provides a high-level overview of the installation and configuration process. Diagram that provides an overview of the installation processPerform the following tasks: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 data node and the Analytics Platform streams node. Install and configure IBM Analytics Accelerator Framework for Communication Service Providers and the prerequisite software, including PCI 1.1.1.Load data onto the Analytics Accelerator Framework Platform and verify this data.Run the Solution Installer to deploy the installation files to the relevant nodes at the application layer.Install the Solution datasets.Install the TELCO database.Create the TELCO datasource.Deploy SPSS content.Install IBM Cognos reports. Install IBM Cognos Dashboards. (Do not include framework steps, as they are not required.)Confirm that the reports and dashboards are connecting to BigInsights and reading the data correctly. Confirm that the reports and dashboards have connected and are reading the data correctly.Installation and configurationThe IBM Customer Insight 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 Insight for Communication Service Providers solution.

The following diagram provides a high-level overview of the installation and configuration process.

Perform the following tasks:

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 data node and the Analytics Platform streams node.

Install and configure IBM Analytics Accelerator Framework for Communication Service Providers and the prerequisite software, including PCI 1.1.1.

Load data onto the Analytics Accelerator Framework Platform and verify this data.

Run the Solution Installer to deploy the installation files to the relevant nodes at the application layer.

Install the Solution datasets.

Install the TELCO database.

Create the TELCO datasource.

Deploy SPSS content.

Install IBM® Cognos® reports.

Install IBM Cognos Dashboards. (Do not include framework steps, as they are not required.)

Confirm that the reports and dashboards are connecting to BigInsights and reading the data correctly.

Parent topic: Installation and configuration

Installing the Solution InstallerThe Solution Installer is used to configure and deploy solution content on the PCI-based nodes in your deployment, including the BI node and the Predictive Analytics node. To use the installer, you must first perform the prerequisites and then the steps for installing the Solution Installer. Solution InstallerThe Solution Installer referred to in this section is the Solution Installer for the Customer Insight for Communication Service Providers solution and not the PCI solution.The configuration for the installer is shown on following screen: Customer Insight configuration, showing the content list and the nodes in the Configuration Editor.Installation and configurationThe IBM Customer Insight for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.PrerequisitesBefore you install the Solution Installer for the Customer Insight 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 Insight 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.Configuring 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 Installer softwareBefore you use the Solution Installer to configure and deploy the nodes in a Linux environment, you must install the Solution Installer.

Installing the Solution Installer

The Solution Installer is used to configure and deploy solution content on the PCI-based nodes in your deployment, including the BI node and the Predictive Analytics node. To use the installer, you must first perform the prerequisites and then the steps for installing the Solution Installer.

Note: The Solution Installer referred to in this section is the Solution Installer for the Customer Insight for Communication Service Providers solution and not the PCI solution.

The configuration for the installer is shown on following screen:

Prerequisites
Before you install the Solution Installer for the Customer Insight 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 Insight 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.

Configuring 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 software
Before you use the Solution Installer to configure and deploy the nodes in a Linux environment, you must install the Solution Installer.

Parent topic: Installation and configuration

PrerequisitesBefore you install the Solution Installer for the Customer Insight for Communication Service Providers solution, there are prerequisites that must be met.Solution Installermaster nodeEnsure the following conditions are met before you install the solution: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 modified the sudoers file for the user who runs the installation. You have configured your computer firewall settings for the installation of Linux. Installing the Solution InstallerThe Solution Installer is used to configure and deploy solution content on the PCI-based nodes in your deployment, including the BI node and the Predictive Analytics node. To use the installer, you must first perform the prerequisites and then the steps for installing the Solution Installer.

Prerequisites

Before you install the Solution Installer for the Customer Insight for Communication Service Providers solution, there are prerequisites that must be met.

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

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 modified the sudoers file for the user who runs the installation.

You have configured your computer firewall settings for the installation of Linux.

Parent topic: Installing the Solution Installer

Modifying the sudoers file for the Linux user who runs the installationTo run the Customer Insight 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 Insight for Communication Service Providers node.Installing the Solution InstallerThe Solution Installer is used to configure and deploy solution content on the PCI-based nodes in your deployment, including the BI node and the Predictive Analytics node. To use the installer, you must first perform the prerequisites and then the steps for installing the Solution Installer.

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

To run the Customer Insight 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 Insight for Communication Service Providers node.

Parent topic: Installing the Solution Installer

Configuring 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. You can either disable all firewall settings temporarily or use the firewall.sh script, as described in this document. firewall settingsInstalling the Solution InstallerThe Solution Installer is used to configure and deploy solution content on the PCI-based nodes in your deployment, including the BI node and the Predictive Analytics node. To use the installer, you must first perform the prerequisites and then the steps for installing the Solution Installer. Disabling firewall settings prior to installation with the Solution Installer (optional)If you choose to temporarily disable your computer's firewall during the installation of the Customer Insight 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 during installation with the Solution InstallerDisable your firewall settings using the firewall.sh script. The script must be run on the computer used by the Solution Installer and each node that will contain content from the solution. You can run the firewall.sh script to open the ports on a Linux installation node.

Configuring 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. You can either disable all firewall settings temporarily or use the firewall.sh script, as described in this document.

Disabling firewall settings prior to installation with the Solution Installer (optional)
If you choose to temporarily disable your computer's firewall during the installation of the Customer Insight 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 during installation with the Solution Installer
Disable your firewall settings using the firewall.sh script. The script must be run on the computer used by the Solution Installer and each node that will contain content from the solution. You can run the firewall.sh script to open the ports on a Linux installation node.

Parent topic: Installing the Solution Installer

Disabling firewall settings prior to installation with the Solution Installer (optional)If you choose to temporarily disable your computer's firewall during the installation of the Customer Insight 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.Configuring 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 prior to installation with the Solution Installer (optional)

If you choose to temporarily disable your computer's firewall during the installation of the Customer Insight 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: Configuring computer firewall settings required for the installation on Linux

Manually configuring firewall settings on the installation node during installation with the Solution InstallerDisable your firewall settings using the firewall.sh script. The script must be run on the computer used by the Solution Installer and each node that will contain content from the solution. You 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.Configuring 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.

Manually configuring firewall settings on the installation node during installation with the Solution Installer

Disable your firewall settings using the firewall.sh script. The script must be run on the computer used by the Solution Installer and each node that will contain content from the solution. 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: Configuring computer firewall settings required for the installation on Linux

Installing the Solution Installer softwareBefore you use the Solution Installer to configure and deploy the nodes in a Linux environment, you must install the Solution Installer. The working directory for solution installation files is opt/IBMHere is a short video that shows you how to install the Solution Installer: http://youtu.be/9u6ZOk8iyt4 Please note the version numbers shown in the video may have been updated (the video will still be relevant). 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. If the Solution Installer (including the IBM Predictive Customer Intelligence Solution Installer) has been run on the computer previously, run the following command on each of the nodes:./cleanupClient.shGo to the Solution Installer directory in the following location: opt/IBM/IS_CSP_Customer_Insight_1.0.4/SolutionInstaller.If you haven't already opened the ports that are required by the Solution Installer, you can open them by running the following command: ./firewall.shEnter the following command:sh setup.sh username first_name last_name email password This command creates a user (with the details supplied) for accessing the Solution Installer web server.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. Installing the Solution InstallerThe Solution Installer is used to configure and deploy solution content on the PCI-based nodes in your deployment, including the BI node and the Predictive Analytics node. To use the installer, you must first perform the prerequisites and then the steps for installing the Solution Installer.

Installing the Solution Installer software

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

Before you begin

The working directory for solution installation files is opt/IBM

About this task

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

http://youtu.be/9u6ZOk8iyt4

Please note the version numbers shown in the video may have been updated (the video will still be relevant). 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.

If the Solution Installer (including the IBM Predictive Customer Intelligence Solution Installer) has been run on the computer previously, run the following command on each of the nodes:

./cleanupClient.sh

Go to the Solution Installer directory in the following location: opt/IBM/IS_CSP_Customer_Insight_1.0.4/SolutionInstaller.

If you haven't already opened the ports that are required by the Solution Installer, you can open them by running the following command:

./firewall.sh

Enter the following command:

sh setup.sh username first_name last_name email password

This command creates a user (with the details supplied) for accessing the Solution Installer web server.

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: Installing the Solution Installer

Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights. Analytics PlatformMediation nodevedia componentInstallation and configurationThe IBM Customer Insight for Communication Service Providers solution is for use with IBM Predictive Customer Intelligence.PrerequisiteBefore you install the Customer Insight for Communication Service Providers solution content, there is a prerequisite that must be met.Deploying the installation files on the nodesYou use the Solution Installer to deploy the installation files to the appropriate nodes in your solution. Installing solution datasetsUse the following procedure to install your solution datasets.Deploying reports and content on the Business Intelligence nodeYou must deploy the report, dashboards, and images for the Customer Insight for Communication Service Providers solution.Installing the TELCO databaseTo install the TELCO database on the data node, you run a script that creates the TELCO database, tables, constraints, and indexes. Creating a Cognos Analytics data source connection to the TELCO databaseYou must create a data source connection from the Business Intelligence node to the IBM DB2 database that is on the data node. Deploying the Cognos DashboardsInstallation of the dashboards includes installing the dashboards, datamodule, and dataserver.Scheduling datasetsDatasets are run on a scheduled basis using tables that containing customer information.Deploying IBM SPSS contentYou must create a data source connection, and then import the content files into IBM SPSS Deployment Manager for Collaboration and Deployment Services.Loading data and starting the predictive analytics jobAfter the Analytics Platform is installed, you must configure and run the data load process and start the predictive analytics job. This is required for churn and NPS predictive analytics.

Installing the solution content

Installing the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Prerequisite
Before you install the Customer Insight for Communication Service Providers solution content, there is a prerequisite that must be met.

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

Installing solution datasets
Use the following procedure to install your solution datasets.

Deploying reports and content on the Business Intelligence node
You must deploy the report, dashboards, and images for the Customer Insight for Communication Service Providers solution.

Installing the TELCO database
To install the TELCO database on the data node, you run a script that creates the TELCO database, tables, constraints, and indexes.

Creating a Cognos Analytics data source connection to the TELCO database
You must create a data source connection from the Business Intelligence node to the IBM DB2 database that is on the data node.

Deploying the Cognos Dashboards
Installation of the dashboards includes installing the dashboards, datamodule, and dataserver.

Scheduling datasets
Datasets are run on a scheduled basis using tables that containing customer information.

Deploying IBM SPSS content
You must create a data source connection, and then import the content files into IBM SPSS Deployment Manager for Collaboration and Deployment Services.

Loading data and starting the predictive analytics job
After the Analytics Platform is installed, you must configure and run the data load process and start the predictive analytics job. This is required for churn and NPS predictive analytics.

Parent topic: Installation and configuration

PrerequisiteBefore you install the Customer Insight for Communication Service Providers solution content, there is a prerequisite that must be met.solution contentmaster nodeEnsure that IBM Predictive Customer Intelligence version 1.1.1 is installed and configured and you have applied all known fix packs to it. When installing PCI, you need an additional temporary server from which to run the PCI Solution Installer. See also this Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21612290Installing IBM Predictive Customer Intelligence version 1.1.1 To install PCI version 1.1.1, refer to the IBM Predictive Customer Intelligence Installation Guide 1.1.1 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. The CI SPSS models require the modeler server to be installed at /usr/IBM/SPSS/ModelerServer/17.1/Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Prerequisite

Before you install the Customer Insight for Communication Service Providers solution content, there is a prerequisite that must be met.

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

Note: When installing PCI, you need an additional temporary server from which to run the PCI Solution Installer. See also this Technote: http://www-01.ibm.com/support/docview.wss?uid=swg21612290

Installing IBM Predictive Customer Intelligence version 1.1.1

To install PCI version 1.1.1, refer to the IBM Predictive Customer Intelligence Installation Guide 1.1.1 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.

Note: The CI SPSS models require the modeler server to be installed at /usr/IBM/SPSS/ModelerServer/17.1/

Parent topic: Installing the solution content

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 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 Cognos Analytics node (or Cognos 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 Cognos Analytics node before adding Cognos Analytics (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. Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

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 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 Cognos Analytics node (or Cognos 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 Cognos Analytics node before adding Cognos Analytics (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: Installing the solution content

Installing solution datasetsUse the following procedure to install your solution datasets.solution datasetsdatasetsAs the root or sudo user, start the installer from the directory where you uncompressed the installation package: $ sudo ./analytics-platform/install_telsol.shThe following flags may be passed to the script:FlagMeaning--dont_validate_biginsightsThe validation of IOP and BigInsights takes a few minutes to run. To save time, this validation step can be skipped by passing this flag.-hPrints a message describing the script usage and exits.When installing each use case, the installer will check for an existing installation of that use case and ask if it should be replaced with the version from the installation package. Provide the answer that applies to your situation. For example, -- Installing Customer Behaviours use case... Checking for existing installation of Customer Behaviours use case... WARNING: Previous installation of Customer Behaviours use case found: customer-behaviours - Remove? (y/n):Answering y will result in the removal of the existing use case. The question will be asked a second time to confirm removal. If the existing installation is removed, the installation of the new version will proceed automatically after the removal.Most use cases can run using default configuration values. If non-default configuration values are required for any use case, you can change those values after installation and before the use case is run. However, the Net Promoter Score use case is an exception: the installer will prompt you for the values for the following NPS configuration settings, because they have no valid default values. Enter the required values.NameValueNPS_BUCKET_SIZESet this to as high as possible based on the size of your cluster (reducers), for example, 30.OPERATOR_MCC_MNCExample: ‘1234’,’3198’Some use cases require data provided by the CSP to be loaded (provisioned) into the database before they are run (for example., CRM data). This data should be provided in the form of CSV files. Before attempting to provision your data, the installer will pause to ensure that these files are available in the correct directory.-- Loading provisioned data... Provisioning data to be loaded must be stored as CSV files in /opt/tnf/apps/bis-main-var/bisprovisioning-tool/csv_files/ - if you have any data to provision, please copy it to that directory now and press any key to resume... If the provisioned data CSV files have not already been copied to that directory, do it now and press any key to resume the installer which will attempt to load them. It will determine which files should be loaded into which tables based on the filenames and ask for confirmation that the correct files are being loaded to the correct tables, e.g.,: Table to load data to ------------------- Data file cb_category ----------------------------- csv_files/cb_category_20150320.csv cea_unacceptable_trend_config ----------- csv_files/cea_unacceptable_trend_config_00000000.csv nps_cell_provisioning_table ------------- csv_files/nps_cell_provisioning_table_20150331.csv nps_crm_provisioning_table -------------- csv_files/nps_crm_provisioning_table_20150331.csv nps_device_provisioning_table ----------- csv_files/nps_device_provisioning_table_20150331.csv nps_survey_table ------------------------ csv_files/nps_survey_table_20150429.csv performance_assign_config --------------- csv_files/performance_assign_config_00000000.csv Load data to tables according to the list? (y/n):Review this information and provide the appropriate response. Upon successful installation, the following message is displayed:-- IBM Telecom Solutions installed completed successfully!The entire session is logged in install_telsol.log in the current directory.Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Installing solution datasets

Use the following procedure to install your solution datasets.

Procedure

As the root or sudo user, start the installer from the directory where you uncompressed the installation package:

$ sudo ./analytics-platform/install_telsol.sh

The following flags may be passed to the script:

Flag | Meaning
--dont_validate_biginsights | The validation of IOP and BigInsights takes a few minutes to run. To save time, this validation step can be skipped by passing this flag.
-h | Prints a message describing the script usage and exits.

When installing each use case, the installer will check for an existing installation of that use case and ask if it should be replaced with the version from the installation package. Provide the answer that applies to your situation. For example,

-- Installing Customer Behaviours use case...

          Checking for existing installation of Customer Behaviours use case...

WARNING: Previous installation of Customer Behaviours use case found: customer-behaviours -
Remove? (y/n):

Answering y will result in the removal of the existing use case. The question will be asked a second time to confirm removal. If the existing installation is removed, the installation of the new version will proceed automatically after the removal.

Most use cases can run using default configuration values. If non-default configuration values are required for any use case, you can change those values after installation and before the use case is run. However, the Net Promoter Score use case is an exception: the installer will prompt you for the values for the following NPS configuration settings, because they have no valid default values. Enter the required values.

Name | Value
NPS_BUCKET_SIZE | Set this to as high as possible based on the size of your cluster (reducers), for example, 30.
OPERATOR_MCC_MNC | Example: ‘1234’,’3198’

Some use cases require data provided by the CSP to be loaded (provisioned) into the database before they are run (for example., CRM data). This data should be provided in the form of CSV files. Before attempting to provision your data, the installer will pause to ensure that these files are available in the correct directory.

-- Loading provisioned data...

Provisioning data to be loaded must be stored as CSV files in
/opt/tnf/apps/bis-main-var/bisprovisioning-tool/csv_files/ -

if you have any data to provision, please copy it to that directory now and press any
key to resume...

If the provisioned data CSV files have not already been copied to that directory, do
it now and press any key to

resume the installer which will attempt to load them. It will determine which files
should be loaded into which

tables based on the filenames and ask for confirmation that the correct files are being
loaded to the correct

tables, e.g.,:

Table to load data to ------------------- Data file

cb_category ----------------------------- csv_files/cb_category_20150320.csv
cea_unacceptable_trend_config ----------- csv_files/cea_unacceptable_trend_config_00000000.csv
nps_cell_provisioning_table ------------- csv_files/nps_cell_provisioning_table_20150331.csv
nps_crm_provisioning_table -------------- csv_files/nps_crm_provisioning_table_20150331.csv
nps_device_provisioning_table ----------- csv_files/nps_device_provisioning_table_20150331.csv
nps_survey_table ------------------------ csv_files/nps_survey_table_20150429.csv
performance_assign_config --------------- csv_files/performance_assign_config_00000000.csv
Load data to tables according to the list? (y/n):

Review this information and provide the appropriate response. Upon successful installation, the following message is displayed:

-- IBM Telecom Solutions installed completed successfully!

The entire session is logged in install_telsol.log in the current directory.

Parent topic: Installing the solution content

Deploying reports and content on the Business Intelligence nodeYou must deploy the report, dashboards, and images for the Customer Insight for Communication Service Providers solution.nodesBusiness Intelligence nodeLog on to the BI node as the root user or as a user with sudo permissions.As a root user, copy CI-nps-images-1.0.4.zip from /opt/IBM/IS_CSP_Customer_Insight_1.0.4/ and unzip the contents into/opt/ibm/cognos/analytics/webcontent/bi/samples/images/ As a root user, copy CI-nps-report-1.0.4.zip from /opt/IBM/IS_CSP_Customer_Insight_1.0.4/ to /opt/ibm/cognos/analytics/deploymentAs a root user, copy CI-churn-report-1.0.4.zip from /opt/IBM/IS_CSP_Customer_Insight_1.0.4/ to /opt/ibm/cognos/analytics/deploymentOn a web browser, navigate to <localhost>:9300/bi. This opens the IBM Cognos Analytics page. From the menu on the left-hand side of the page, click Manage and then click Administration Console. This opens IBM Cognos Administration Console in a new tab. Click Configuration and then click Content Administration. This opens a page view of the content to be imported and exported.Click the New Import symbol from the menu on the right-hand side of the page. This launches the New Import wizard. Select CI-nps-report-1.0.4.zip and click Next.On the Specify a name and description page, accept the defaults and click Next.On the Select the public folders, directory and library content page, select all the folders which appear and click Next. On the Specify the general options page, accept the defaults and click Next. On the Review the summary page, accept the defaults and click Next. On the Select an action page, accept the defaults and click Finish. On the Run with options page, accept the defaults and click Run. On the final wizard page, click OK. The import should now be visible on the Content Administration page. Repeat steps 5 to 12 for CI-churn-report-1.0.4.zipInstalling the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Deploying reports and content on the Business Intelligence node

You must deploy the report, dashboards, and images for the Customer Insight for Communication Service Providers solution.

Procedure

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

As a root user, copy CI-nps-images-1.0.4.zip from /opt/IBM/IS_CSP_Customer_Insight_1.0.4/ and unzip the contents into/opt/ibm/cognos/analytics/webcontent/bi/samples/images/

As a root user, copy CI-nps-report-1.0.4.zip from /opt/IBM/IS_CSP_Customer_Insight_1.0.4/ to /opt/ibm/cognos/analytics/deployment

As a root user, copy CI-churn-report-1.0.4.zip from /opt/IBM/IS_CSP_Customer_Insight_1.0.4/ to /opt/ibm/cognos/analytics/deployment

On a web browser, navigate to <localhost>:9300/bi. This opens the IBM Cognos Analytics page.

From the menu on the left-hand side of the page, click Manage and then click Administration Console. This opens IBM Cognos Administration Console in a new tab.

Click Configuration and then click Content Administration. This opens a page view of the content to be imported and exported.

Click the New Import symbol from the menu on the right-hand side of the page. This launches the New Import wizard.

Select CI-nps-report-1.0.4.zip and click Next.

On the Specify a name and description page, accept the defaults and click Next.

On the Select the public folders, directory and library content page, select all the folders which appear and click Next.

On the Specify the general options page, accept the defaults and click Next.

On the Review the summary page, accept the defaults and click Next.

On the Select an action page, accept the defaults and click Finish.

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

On the final wizard page, click OK.

The import should now be visible on the Content Administration page. Repeat steps 5 to 12 for CI-churn-report-1.0.4.zip

Parent topic: Installing the solution content

Installing the TELCO databaseTo install the TELCO database on the data node, you run a script that creates the TELCO database, tables, constraints, and indexes. databaseTELCODB2installationDB2TELCO databaseLog on to the data node with a user ID that has access to the IBM DB2 database.For example, db2inst1.Navigate to /opt/IBM/IS_CSP_CustomerInsight_1.0.4/CSP_CustomerInsight_DBLoader/script/Enter the following command to run the script:db2 -tvf TELCO_Db2.sqlVerify that the database tables exist. Type the following commands: db2 connect to TELCO; db2 list tables for schema NPS;Information similar to the following message is displayed:FACTOR_IMPORTANCE NPS T 2015-06-07-22.46.41.072519 FACT_SCORE NPS T 2015-06-07-22.46.41.815746 MASTER_CUSTOMER NPS T 2015-06-07-22.46.41.833610 MASTER_DATA_ACTIVITY_LOCATION NPS T 2015-06-07-22.46.41.848970 MASTER_DEVICE NPS T 2015-06-07-22.46.41.864207 PREDICTED_NETWORK_NPS_SCORE NPS T 2015-06-07-22.46.41.864587 PREDICTED_SUBSCRIBER_NPS_SCORE NPS T 2015-06-07-22.46.41.864940 STAGING_NPS_SCORE_TABLE NPS T 2015-06-07-22.46.41.865220db2 list tables for schema BBCIInformation similar to the following message is displayed:CGR_DEVICE BBCI T 2015-09-09-02.12.13.907406 CHURN_DATA BBCI T 2015-08-20-15.56.39.964202 CHURN_MANAGEMENT BBCI T 2015-08-19-01.33.27.083252 CHURN_MANAGEMENT_HISTORY BBCI T 2015-09-11-16.47.45.466452 SUBSCRIBER_BILLING BBCI T 2015-09-11-16.03.21.410002 SUBSCRIBER_CARE BBCI T 2015-09-11-16.04.12.393064 SUBSCRIBER_CRM BBCI T 2015-09-11-16.05.00.176739 SUBSCRIBER_LEVEL_CX_SCORE_WEEKLY BBCI T 2015-08-20-16.02.13.778290 CHURN_TREND BBCI T 2015-08-20-16.01.00.876379 TOP_CHURN_FACTORS BBCI T 2015-08-20-16.00.52.486780Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Installing the TELCO database

To install the TELCO database on the data node, you run a script that creates the TELCO database, tables, constraints, and indexes.

Procedure

Log on to the data node with a user ID that has access to the IBM® DB2® database. For example, db2inst1.

Navigate to /opt/IBM/IS_CSP_CustomerInsight_1.0.4/CSP_CustomerInsight_DBLoader/script/

Enter the following command to run the script:

db2 -tvf TELCO_Db2.sql

Verify that the database tables exist. Type the following commands:

db2 connect to TELCO;
db2 list tables for schema NPS;

Information similar to the following message is displayed:

FACTOR_IMPORTANCE              NPS             T     2015-06-07-22.46.41.072519
FACT_SCORE                     NPS             T     2015-06-07-22.46.41.815746
MASTER_CUSTOMER                NPS             T     2015-06-07-22.46.41.833610
MASTER_DATA_ACTIVITY_LOCATION  NPS             T     2015-06-07-22.46.41.848970
MASTER_DEVICE                  NPS             T     2015-06-07-22.46.41.864207
PREDICTED_NETWORK_NPS_SCORE    NPS             T     2015-06-07-22.46.41.864587
PREDICTED_SUBSCRIBER_NPS_SCORE NPS             T     2015-06-07-22.46.41.864940
STAGING_NPS_SCORE_TABLE        NPS             T     2015-06-07-22.46.41.865220

db2 list tables for schema BBCI

Information similar to the following message is displayed:

CGR_DEVICE                       BBCI             T     2015-09-09-02.12.13.907406
CHURN_DATA                       BBCI             T     2015-08-20-15.56.39.964202
CHURN_MANAGEMENT                 BBCI             T     2015-08-19-01.33.27.083252
CHURN_MANAGEMENT_HISTORY         BBCI             T     2015-09-11-16.47.45.466452
SUBSCRIBER_BILLING               BBCI             T     2015-09-11-16.03.21.410002
SUBSCRIBER_CARE                  BBCI             T     2015-09-11-16.04.12.393064
SUBSCRIBER_CRM                   BBCI             T     2015-09-11-16.05.00.176739
SUBSCRIBER_LEVEL_CX_SCORE_WEEKLY BBCI             T     2015-08-20-16.02.13.778290
CHURN_TREND                      BBCI             T     2015-08-20-16.01.00.876379
TOP_CHURN_FACTORS                BBCI             T     2015-08-20-16.00.52.486780

Parent topic: Installing the solution content

Creating a Cognos Analytics data source connection to the TELCO databaseYou must create a data source connection from the Business Intelligence node to the IBM DB2 database that is on the data node. data source connectionTELCO databaseOpen a web browser on the BI node.Navigate to the IBM Cognos Analytics page. Click Manage and then click Data servers. Click Add a dataserver.Based on the connection information that is provided by your database administrator, enter the appropriate information. If applicable, select the authentication mode to be used. Type: db2 Name: TELCO Server: db server Port: 50000 DB: TELCO User: db2inst1Click Test to test the connection.On the View the results page, ensure that the status of the connection tests for the dynamic query mode is Succeeded.Click Save.Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Creating a Cognos Analytics data source connection to the TELCO database

You must create a data source connection from the Business Intelligence node to the IBM DB2 database that is on the data node.

Procedure

Open a web browser on the BI node.

Navigate to the IBM Cognos Analytics page.

Click Manage and then click Data servers.

Click Add a dataserver.

Based on the connection information that is provided by your database administrator, enter the appropriate information. If applicable, select the authentication mode to be used.

Type: db2
Name: TELCO
Server: db server
Port: 50000
DB: TELCO
User: db2inst1

Click Test to test the connection. On the View the results page, ensure that the status of the connection tests for the dynamic query mode is Succeeded.

Click Save.

Parent topic: Installing the solution content

Deploying the Cognos DashboardsInstallation of the dashboards includes installing the dashboards, datamodule, and dataserver.dashboardLog on to the BI node as the root user or as a user with sudo permissions.As a root user, copy ci-dashboards-1.0.4.zip from /opt/IBM/IS_CSP_Customer_Insight_1.0.4/ to /opt/ibm/cognos/analytics/deployment On a web browser, navigate to <localhost>:9300/bi. This opens the IBM Cognos Analytics page. From the menu on the left-hand side of the page, click Manage and then click Administration Console. This opens IBM Cognos Administration Console in a new tab. Click Configuration and then click Content Administration. This opens a page view of the content imported and exported to and from Cognos. Click the New Import symbol from the menu on the right-hand side of the page. This launches the New Import wizard. Select ci-dashboards-1.0.4 and click Next. On the Specify a name and description page, accept the defaults and click Next.On the Select the public folders, directory and library content page, select all the folders which appear and click Next. On the Specify the general options page, accept the defaults and click Next. On the Review the summary page, accept the defaults and click Next. On the Select an action page, accept the defaults and click Finish. On the Run with options page, accept the defaults and click Run. On the final wizard page, click OK. The import should now be visible on the Content Administration page. Repeat steps 5 to 12 for ci-churn-report-1.0.4.zipReturn to the IBM Cognos Analytics page, click Manage and then click Data servers.Click bbci-ott-datasource and then click it again on the next tab that opens on the page.Select Connection details from the ... (three dot) menu. Update the connection details. The RA environment details are:connection name: bbci-ott-datasource port: 32051c database: bigsqlYou will then need to refresh the Cognos datasource. Click bbci-ott-datasource.Next to Cognos, click More...Wait until the status changes to Succeeded. Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights.

Deploying the Cognos Dashboards

Installation of the dashboards includes installing the dashboards, datamodule, and dataserver.

Procedure

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

As a root user, copy ci-dashboards-1.0.4.zip from /opt/IBM/IS_CSP_Customer_Insight_1.0.4/ to /opt/ibm/cognos/analytics/deployment

On a web browser, navigate to <localhost>:9300/bi. This opens the IBM Cognos Analytics page.

From the menu on the left-hand side of the page, click Manage and then click Administration Console. This opens IBM Cognos Administration Console in a new tab.

Click Configuration and then click Content Administration. This opens a page view of the content imported and exported to and from Cognos.

Click the New Import symbol from the menu on the right-hand side of the page. This launches the New Import wizard.

Select ci-dashboards-1.0.4 and click Next.

On the Specify a name and description page, accept the defaults and click Next.

On the Select the public folders, directory and library content page, select all the folders which appear and click Next.

On the Specify the general options page, accept the defaults and click Next.

On the Review the summary page, accept the defaults and click Next.

On the Select an action page, accept the defaults and click Finish.

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

On the final wizard page, click OK.

The import should now be visible on the Content Administration page. Repeat steps 5 to 12 for ci-churn-report-1.0.4.zip

Return to the IBM Cognos Analytics page, click Manage and then click Data servers.

Click bbci-ott-datasource and then click it again on the next tab that opens on the page.

Select Connection details from the ... (three dot) menu.

Update the connection details. The RA environment details are:

connection name: bbci-ott-datasource
port: 32051c
database: bigsql

You will then need to refresh the Cognos datasource.

Click bbci-ott-datasource.

Next to Cognos, click More...Wait until the status changes to Succeeded.

Parent topic: Installing the solution content

Scheduling datasetsDatasets are run on a scheduled basis using tables that containing customer information.Dataset cronjobsmaster nodeMost datasets are run on an hourly, daily, or weekly basis, through cron jobs that are added to a boss's crontab as part of the dataset rpm installation. These can be viewed and modified by running crontab -e as a boss on your Analytic Server node. In a default install, here is the scheduling you will see across the various datasets:DatasetSchedulecustomer-profile-data-setup0.30, every Monday morning (weekly tables)ott-applications02.30, every Monday morning (weekly tables) customer-profile02.30, every Monday morning (weekly tables)user-profile 04.30, every Monday morning (weekly tables)customer-behaviours *.45, every hour (hourly tables)03.15, every day (daily weighted interest tables) 03.30, every day (daily other tables) 00.30, every Monday morning (weekly tables)SPSS jobs are triggered from the customer-profile-data-setup dataset. For more information, see SPSS job triggeringThis topic describes how SPSS jobs are triggered from the customer-profile-data-setup dataset.. This dataset runs at 00.30 on a Monday, two hours before the next dataset is run. If a dataset's models are processing a large amount of data that does not complete before subsequent, dependent datasets are triggered, the dependent datasets will run with old data. It may be necessary to push back the schedules of those datasets to ensure they are not being triggered before all necessary processing completes. To do so, edit the dataset run schedules in crontab -e. Press a while in crontab to make the entries editable, then modify either of the first two fields (which indicate the minute and hour, respectively, in which to run the command on that line). For example, to push ott-applications back by an hour, change the second field in the run_ott-applications.sh line from 2 to 3, then press Esc, w, q, and Return to save and exit.Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights. SPSS job triggeringThis topic describes how SPSS jobs are triggered from the customer-profile-data-setup dataset.

Scheduling datasets

Datasets are run on a scheduled basis using tables that containing customer information.

Most datasets are run on an hourly, daily, or weekly basis, through cron jobs that are added to a boss's crontab as part of the dataset rpm installation. These can be viewed and modified by running crontab -e as a boss on your Analytic Server node. In a default install, here is the scheduling you will see across the various datasets:

Dataset
Schedule

customer-profile-data-setup
0.30, every Monday morning (weekly tables)

ott-applications

02.30, every Monday morning (weekly tables)

customer-profile

02.30, every Monday morning (weekly tables)

user-profile
04.30, every Monday morning (weekly tables)

customer-behaviours

*.45, every hour (hourly tables)

03.15, every day (daily weighted interest tables)

03.30, every day (daily other tables)

00.30, every Monday morning (weekly tables)

SPSS jobs are triggered from the customer-profile-data-setup dataset. For more information, see SPSS job triggering. This dataset runs at 00.30 on a Monday, two hours before the next dataset is run. If a dataset's models are processing a large amount of data that does not complete before subsequent, dependent datasets are triggered, the dependent datasets will run with old data. It may be necessary to push back the schedules of those datasets to ensure they are not being triggered before all necessary processing completes. To do so, edit the dataset run schedules in crontab -e. Press a while in crontab to make the entries editable, then modify either of the first two fields (which indicate the minute and hour, respectively, in which to run the command on that line). For example, to push ott-applications back by an hour, change the second field in the run_ott-applications.sh line from 2 to 3, then press Esc, w, q, and Return to save and exit.

SPSS job triggering
This topic describes how SPSS jobs are triggered from the customer-profile-data-setup dataset.

Parent topic: Installing the solution content

SPSS job triggeringThis topic describes how SPSS jobs are triggered from the customer-profile-data-setup dataset.SPSS job triggeringmaster nodeNumerous SPSS models generate output from the tables populated by the customer-profile-data-setup dataset. When this dataset is run, the models which depend on this dataset are triggered automatically through Collaboration & Deployment Services (C&DS). The files which specify the target C&DS instance and the details of the jobs to be run are located in the customer-profile-data-setup/config folder. The server connection properties are found in spss_server.properties. After setting the username and password properties, theencodePasswordProperties.sh script (also located in the config directory) should be run on this file. Job-specific details are given in the .job_properties files, where each .job_properties file corresponds to a single stream to be run through C&DS. The properties in these files are: SPSSID: The C&DS job ID, which can be found in the C&DS dashboard by selecting the job in the Content Repository and then selecting Properties from the right-click menu. SPSSTriggerModel: A boolean value,which can be set to false to quickly disable the automatic execution of this job (if required). SPSSRunSchedule: A comma-separated list of the days on which this model should be run, using a day's three-letter code, such as mon, tue, thu. Note that a model will only be triggered after running customer-profile-data-setup, so a model will trigger only if set to run on the same day as customer-profile-data-setup. PrerequisiteJobs: An optional field, which allows you to specify job dependencies. Some models rely on the output of other models, so those models must not be triggered until all the models on which they depend have been triggered and completed. The value is a comma-separated string of job names. For example, the customer_profile_best_time_and_medium models depend on output from the customer_profile_location_affinity model, which is also triggered by customer-profile-data-setup, so customer_profile_best_time_and_medium.job_properties specifies a PrerequisiteJobs value of customer_profile_location_affinity to ensure it waits for customer_profile_location_affinity to complete before running. Note that jobs which do not specify any prerequisites will run as normal, without dependencies. : SPSSEndPoint, SPSSUser, and SPSSPasswd. The SPSSEndPoint property is the URL of the C&DS server which serves job requests and is typically in the format http://<machine_address>:9080/process/services/ProcessManagement This will base64 encode the given SPSSPasswd value.Scheduling datasetsDatasets are run on a scheduled basis using tables that containing customer information.

SPSS job triggering

This topic describes how SPSS jobs are triggered from the customer-profile-data-setup dataset.

Numerous SPSS models generate output from the tables populated by the customer-profile-data-setup dataset. When this dataset is run, the models which depend on this dataset are triggered automatically through Collaboration & Deployment Services (C&DS). The files which specify the target C&DS instance and the details of the jobs to be run are located in the customer-profile-data-setup/config folder. The server connection properties are found in spss_server.properties.

After setting the username and password properties, theencodePasswordProperties.sh script (also located in the config directory) should be run on this file. Job-specific details are given in the .job_properties files, where each .job_properties file corresponds to a single stream to be run through C&DS. The properties in these files are:

SPSSID: The C&DS job ID, which can be found in the C&DS dashboard by selecting the job in the Content Repository and then selecting Properties from the right-click menu.

SPSSTriggerModel: A boolean value,which can be set to false to quickly disable the automatic execution of this job (if required).

SPSSRunSchedule: A comma-separated list of the days on which this model should be run, using a day's three-letter code, such as mon, tue, thu. Note that a model will only be triggered after running customer-profile-data-setup, so a model will trigger only if set to run on the same day as customer-profile-data-setup.

PrerequisiteJobs: An optional field, which allows you to specify job dependencies. Some models rely on the output of other models, so those models must not be triggered until all the models on which they depend have been triggered and completed. The value is a comma-separated string of job names. For example, the customer_profile_best_time_and_medium models depend on output from the customer_profile_location_affinity model, which is also triggered by customer-profile-data-setup, so customer_profile_best_time_and_medium.job_properties specifies a PrerequisiteJobs value of customer_profile_location_affinity to ensure it waits for customer_profile_location_affinity to complete before running. Note that jobs which do not specify any prerequisites will run as normal, without dependencies.

Parent topic: Scheduling datasets

Deploying IBM SPSS contentThere is no Predictive Analytics (SPSS) node in CEA so omit this topic for CEA? Yes, confirmed by Brian and Srini.You must create a data source connection, and then import the content files into IBM SPSS Deployment Manager for Collaboration and Deployment Services.Collaboration and Deployment Services Deployment ManagerDeployment ManagerIBM SPSSdata source connectionODBCjobconfiguringEnsure that the following things are in place: IBM SPSS Collaboration and Deployment Services Deployment Manager is installed on the client computer.The CSP_CustomerInsight_CDS.pes file is on the local client computer from which the deployment is performed. The default installation folder for this file is /opt/IBM/IS_Customer_Insight_1.0.4/.You know the admin credentials for the Predictive Analytics node, IBM DB2, and IBM SPSS Collaboration and Deployment Services.Using the Analytics Platform nodeLaunch the IBM Analytic Server at http://host:port/analyticserver/admin/ibm.Log in using your Analytic Server Credentials.Click Datasources.Import each of the zip files located in the IS_CSP_Customer_Insight_1.0.4/analytics-platform/analyticserver_datasources/ directory.Select Actions > Import > Browse and select a data source.Repeat steps 4-5 to import each of the data sources in the list. Using Deployment ManagerStart Deployment Manager.Click File NewContent Server Connection.In the Connection Name field, enter a name that identifies the Predictive Analytics node.In the Server URL field, enter http://analytics_node_IP:9080 and click Finish.Right-click Content Repository and click Import.Browse to and select the CSP_CustomerInsights_CDS.pes file.Click Open.Accept the default options in the Import window, and click OK.The CSP_CustomerInsights_NPS folder, a job in the Jobs folder, and streams in the Modeler Streams folder are created. Repeat steps 6-8 for the CSP_CustomerInsights_Profile.pes file.Update the credential information for the Admin, Db2inst1, and root users so that the job and streams run successfully.In the Content Explorer tab, under Resource Definitions, open the Credentials folder.Update the Admin user with the credentials for the SPSS Collaboration and Deployment Services user that has access to the content repository and runs the job.Update the Db2inst1 user with the credentials for the user that has access to the IBM DB2 database. Update the root user with the credentials for the user that has access to the Modeler Server.Open the job in the Jobs folder and ensure that the user credentials match the credentials of the IBM DB2 instance on the ODBC tab.Verify the server connections are correct for your environment. In the Content Explorer, open the Servers folder and verify the cads and modeler connections. Create an ODBC connection with the name IBMPCI that points to the TELCO database on the data node. For information about how to create an ODBC connection, see Configuring ODBC for IBM SPSS Modeler Server on Linux operating systemsTo use an ODBC data source with IBM SPSS Modeler Server on a Linux operating system, you must configure the environment.. In the odbc.ini file, specify the driver path as /opt/IBM/SDAP711/lib/XEdb227.so.Installing the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights. Configuring ODBC for IBM SPSS Modeler Server on Linux operating systemsTo use an ODBC data source with IBM SPSS Modeler Server on a Linux operating system, you must configure the environment.SPSS job sequencing and triggeringSpecific processing jobs define execution sequences and triggering events for individual files stored in the IBM SPSS Collaboration and Deployment Services Repository.Changing churn factor labelsYou can change the churn factor labels to suit your business needs.Improving the SPSS model performanceYou can fine-tune the SPSS model performance.

Deploying IBM SPSS content

You must create a data source connection, and then import the content files into IBM SPSS Deployment Manager for Collaboration and Deployment Services.

Before you begin

Ensure that the following things are in place:

IBM SPSS Collaboration and Deployment Services Deployment Manager is installed on the client computer.

The CSP_CustomerInsight_CDS.pes file is on the local client computer from which the deployment is performed. The default installation folder for this file is /opt/IBM/IS_Customer_Insight_1.0.4/.

You know the admin credentials for the Predictive Analytics node, IBM DB2, and IBM SPSS Collaboration and Deployment Services.

Procedure

Using the Analytics Platform node

Launch the IBM Analytic Server at http://host:port/analyticserver/admin/ibm.

Log in using your Analytic Server Credentials.

Click Datasources.

Import each of the zip files located in the IS_CSP_Customer_Insight_1.0.4/analytics-platform/analyticserver_datasources/ directory.

Select Actions > Import > Browse and select a data source.

Repeat steps 4-5 to import each of the data sources in the list.

Using Deployment Manager

Start Deployment Manager.

Click File > New > Content Server Connection.

In the Connection Name field, enter a name that identifies the Predictive Analytics node.

In the Server URL field, enter http://analytics_node_IP:9080 and click Finish.

Right-click Content Repository and click Import.

Browse to and select the CSP_CustomerInsights_CDS.pes file.

Click Open.

Accept the default options in the Import window, and click OK. The CSP_CustomerInsights_NPS folder, a job in the Jobs folder, and streams in the Modeler Streams folder are created.

Repeat steps 6-8 for the CSP_CustomerInsights_Profile.pes file.

Update the credential information for the Admin, Db2inst1, and root users so that the job and streams run successfully.

In the Content Explorer tab, under Resource Definitions, open the Credentials folder.

Update the Admin user with the credentials for the SPSS Collaboration and Deployment Services user that has access to the content repository and runs the job.

Update the Db2inst1 user with the credentials for the user that has access to the IBM DB2 database.

Update the root user with the credentials for the user that has access to the Modeler Server.

Open the job in the Jobs folder and ensure that the user credentials match the credentials of the IBM DB2 instance on the ODBC tab.

Verify the server connections are correct for your environment. In the Content Explorer, open the Servers folder and verify the cads and modeler connections.

Create an ODBC connection with the name IBMPCI that points to the TELCO database on the data node.

For information about how to create an ODBC connection, see Configuring ODBC for IBM SPSS Modeler Server on Linux operating systems. In the odbc.ini file, specify the driver path as /opt/IBM/SDAP711/lib/XEdb227.so.

Configuring ODBC for IBM SPSS Modeler Server on Linux operating systems
To use an ODBC data source with IBM SPSS Modeler Server on a Linux operating system, you must configure the environment.

SPSS job sequencing and triggering
Specific processing jobs define execution sequences and triggering events for individual files stored in the IBM SPSS Collaboration and Deployment Services Repository.

Changing churn factor labels
You can change the churn factor labels to suit your business needs.

Improving the SPSS model performance
You can fine-tune the SPSS model performance.

Parent topic: Installing the solution content

Configuring ODBC for IBM SPSS Modeler Server on Linux operating systemsTo use an ODBC data source with IBM SPSS Modeler Server on a Linux operating system, you must configure the environment.Stop the IBM SPSS Modeler Server.Go to the /root/SDAP711 directory. The driver files are installed as part of the IBM Predictive Customer Intelligence Server deployment.Run the setodbcpath.sh script to update the ODBC path in the scripts.Edit the odbc.sh script to add the definition for ODBCINI to the bottom of the script. For example:ODBCINI=/root/SDAP711/odbc.ini; export ODBCINIODBCINI must point to the full file path of the odbc.ini file for IBM SPSS Modeler. The odbc.ini file lists the ODBC data sources that you want to connect to. A default odbc.ini file is installed with the drivers.In the odbc.ini file, add the data source and specify the driver in the [ODBC Data Sources] section of the file. Add the TELCO data source as: [ODBC Data Sources] TELCO=IBM DB2 ODBC DriverIn the odbc.ini file, create a TELCO data source connection.[TELCO] Driver=/opt/ibm/db2/V10.5/lib64/libdb2o.so DriverUnicodeType=1 Description=IBM DB2 ODBC Driver ApplicationUsingThreads=1 AuthenticationMethod=0 BulkBinaryThreshold=32 BulkCharacterThreshold=-1 BulkLoadBatchSize=1024 CharsetFor65535=0 #Database applies to DB2 UDB only Database=TELCO DefaultIsolationLevel=1 DynamicSections=200 EnableBulkLoad=0 EncryptionMethod=0 FailoverGranularity=0 FailoverMode=0 FailoverPreconnect=0 GrantAuthid=PUBLIC GrantExecute=1 GSSClient=native HostNameInCertificate= IpAddress=IP_Address_of_DB_server KeyPassword= KeyStore= KeyStorePassword= LoadBalanceTimeout=0 LoadBalancing=0 LogonID=TELCO MaxPoolSize=100 MinPoolSize=0 Password=password PackageCollection=NULLID PackageNamePrefix=DD PackageOwner= Pooling=0 ProgramID= QueryTimeout=0 ReportCodePageConversionErrors=0 TcpPort=50000 TrustStore= TrustStorePassword= UseCurrentSchema=0 ValidateServerCertificate=1 WithHold=1 XMLDescribeType=-10You must use the driver library libdb2o.so with IBM SPSS Modeler. Ensure that you set DriverUnicodeType=1 to avoid buffer overflow errors when you connect to the database.If you are using the 64-bit version of IBM SPSS Modeler Server, define and export LD_LIBRARY_PATH_64 in the odbc.sh script: if [ "$LD_LIBRARY_PATH_64" = "" ]; then LD_LIBRARY_PATH_64=<library_path> else LD_LIBRARY_PATH_64=<library_path>:$LD_LIBRARY_PATH_64 fi export LD_LIBRARY_PATH_64 Where <library_path> is the same as for the LD_LIBRARY_PATH definition in the script that was initialized with the installation path. For example, /opt/spss/odbc/lib. You can copy the if and export statements for LD_LIBRARY_PATH in the odbc.sh file, append them to the end of the file. Then, replace the LD_LIBRARY_PATH strings in the newly appended if and export statements with LD_LIBRARY_PATH_64. Here is an example of the odbc.sh file for a 64-bit IBM SPSS Modeler Server installation:if [ "$LD_LIBRARY_PATH" = "" ]; then LD_LIBRARY_PATH=/opt/spss/odbc/lib else LD_LIBRARY_PATH=/opt/spss/odbc/lib:$LD_LIBRARY_PATH fi export LD_LIBRARY_PATH if [ "$LD_LIBRARY_PATH_64" = "" ]; then LD_LIBRARY_PATH_64=/opt/spss/odbc/lib else LD_LIBRARY_PATH_64=/opt/spss/odbc/lib:$LD_LIBRARY_PATH_64 fi export LD_LIBRARY_PATH_64 ODBCINI=/opt/spss/odbc/odbc.ini; export ODBCINIEnsure that you export LD_LIBRARY_PATH_64, and define it with the if loop. Configure IBM SPSS Modeler Server to use the driver. Edit modelersrv.sh and add the following line immediately below the line that defines SCLEMDNAME:. <odbc.sh_path> Where odbc.sh_path is the full path to the odbc.sh file.For example: . /opt/spss/odbc/odbc.sh Ensure that you leave a space between the first period and the file path.Save modelersrv.sh.Configure the IBM SPSS Modeler Server to use the ODBC wrapper named libspssodbc_datadirect.so.Go to the /usr/IBM/SPSS/ModelerServer/17.1/bin directory.Remove the existing libspssodbc.so soft link by using the following command:rm –fr libspssodbc.soLink the new wrapper to libspssodbc.so by using the following command:ln –s libspssodbc_datadirect_utf16.so libspssodbc.soConfigure the db2cli.ini file in <db2 instance home>/sqllib/cfg/db2cli.ini to add the sections for the TELCO database.[TELCO] Database=TELCO Protocol=TCPIP DriverUnicodeType=1 Port=50000 Hostname=IP_Address_of_DB_server UID=username PWD=passwordSave odbc.ini.To test the connection, do the following steps:Restart IBM SPSS Modeler Server.Connect to IBM SPSS Modeler Server from a client.Add a database source node to the canvas.Open the node and verify that you can see the data source names that you defined in the odbc.ini file.For additional information and troubleshooting tips for connecting to data sources, see the SPSS Modeler documentation (http://www.ibm.com/support/knowledgecenter/SS3RA7_17.1.0)Deploying IBM SPSS contentYou must create a data source connection, and then import the content files into IBM SPSS Deployment Manager for Collaboration and Deployment Services.

Configuring ODBC for IBM SPSS Modeler Server on Linux operating systems

To use an ODBC data source with IBM® SPSS® Modeler Server on a Linux operating system, you must configure the environment.

Procedure

Stop the IBM SPSS Modeler Server.

Go to the /root/SDAP711 directory.

The driver files are installed as part of the IBM Predictive Customer Intelligence Server deployment.

Run the setodbcpath.sh script to update the ODBC path in the scripts.

Edit the odbc.sh script to add the definition for ODBCINI to the bottom of the script. For example:

ODBCINI=/root/SDAP711/odbc.ini; export ODBCINI

ODBCINI must point to the full file path of the odbc.ini file for IBM SPSS Modeler. The odbc.ini file lists the ODBC data sources that you want to connect to. A default odbc.ini file is installed with the drivers.

In the odbc.ini file, add the data source and specify the driver in the [ODBC Data Sources] section of the file.

Add the TELCO data source as:

[ODBC Data Sources]
TELCO=IBM DB2 ODBC Driver

In the odbc.ini file, create a TELCO data source connection.

[TELCO]
Driver=/opt/ibm/db2/V10.5/lib64/libdb2o.so
DriverUnicodeType=1
Description=IBM DB2 ODBC Driver
ApplicationUsingThreads=1
AuthenticationMethod=0
BulkBinaryThreshold=32
BulkCharacterThreshold=-1
BulkLoadBatchSize=1024
CharsetFor65535=0
#Database applies to DB2 UDB only
Database=TELCO
DefaultIsolationLevel=1
DynamicSections=200
EnableBulkLoad=0
EncryptionMethod=0
FailoverGranularity=0
FailoverMode=0
FailoverPreconnect=0
GrantAuthid=PUBLIC
GrantExecute=1
GSSClient=native
HostNameInCertificate=
IpAddress=IP_Address_of_DB_server
KeyPassword=
KeyStore=
KeyStorePassword=
LoadBalanceTimeout=0
LoadBalancing=0
LogonID=TELCO
MaxPoolSize=100
MinPoolSize=0
Password=password
PackageCollection=NULLID
PackageNamePrefix=DD
PackageOwner=
Pooling=0
ProgramID=
QueryTimeout=0
ReportCodePageConversionErrors=0
TcpPort=50000
TrustStore=
TrustStorePassword=
UseCurrentSchema=0
ValidateServerCertificate=1
WithHold=1
XMLDescribeType=-10

Note: You must use the driver library libdb2o.so with IBM SPSS Modeler.

Ensure that you set DriverUnicodeType=1 to avoid buffer overflow errors when you connect to the database.

If you are using the 64-bit version of IBM SPSS Modeler Server, define and export LD_LIBRARY_PATH_64 in the odbc.sh script:

if [ "$LD_LIBRARY_PATH_64" = "" ]; then
LD_LIBRARY_PATH_64=<library_path>
else
LD_LIBRARY_PATH_64=<library_path>:$LD_LIBRARY_PATH_64
fi
export LD_LIBRARY_PATH_64

Where <library_path> is the same as for the LD_LIBRARY_PATH definition in the script that was initialized with the installation path. For example, /opt/spss/odbc/lib.

Tip: You can copy the if and export statements for LD_LIBRARY_PATH in the odbc.sh file, append them to the end of the file. Then, replace the LD_LIBRARY_PATH strings in the newly appended if and export statements with LD_LIBRARY_PATH_64. Here is an example of the odbc.sh file for a 64-bit IBM SPSS Modeler Server installation:

if [ "$LD_LIBRARY_PATH" = "" ]; then
		LD_LIBRARY_PATH=/opt/spss/odbc/lib
else
		LD_LIBRARY_PATH=/opt/spss/odbc/lib:$LD_LIBRARY_PATH
fi
export LD_LIBRARY_PATH
if [ "$LD_LIBRARY_PATH_64" = "" ]; then
		LD_LIBRARY_PATH_64=/opt/spss/odbc/lib
else
		LD_LIBRARY_PATH_64=/opt/spss/odbc/lib:$LD_LIBRARY_PATH_64
fi
export LD_LIBRARY_PATH_64
ODBCINI=/opt/spss/odbc/odbc.ini; export ODBCINI

Ensure that you export LD_LIBRARY_PATH_64, and define it with the if loop.

Configure IBM SPSS Modeler Server to use the driver. Edit modelersrv.sh and add the following line immediately below the line that defines SCLEMDNAME:

. <odbc.sh_path>

Where odbc.sh_path is the full path to the odbc.sh file.

For example: . /opt/spss/odbc/odbc.sh

Ensure that you leave a space between the first period and the file path.

Save modelersrv.sh.

Configure the IBM SPSS Modeler Server to use the ODBC wrapper named libspssodbc_datadirect.so.

Go to the /usr/IBM/SPSS/ModelerServer/17.1/bin directory.

Remove the existing libspssodbc.so soft link by using the following command:

rm –fr libspssodbc.so

Link the new wrapper to libspssodbc.so by using the following command:

ln –s libspssodbc_datadirect_utf16.so libspssodbc.so

Configure the db2cli.ini file in <db2 instance home>/sqllib/cfg/db2cli.ini to add the sections for the TELCO database.

[TELCO]
Database=TELCO
Protocol=TCPIP
DriverUnicodeType=1
Port=50000
Hostname=IP_Address_of_DB_server
UID=username
PWD=password

Save odbc.ini.

What to do next

To test the connection, do the following steps:

Restart IBM SPSS Modeler Server.

Connect to IBM SPSS Modeler Server from a client.

Add a database source node to the canvas.

Open the node and verify that you can see the data source names that you defined in the odbc.ini file.

For additional information and troubleshooting tips for connecting to data sources, see the SPSS Modeler documentation (http://www.ibm.com/support/knowledgecenter/SS3RA7_17.1.0)

Parent topic: Deploying IBM SPSS content

SPSS job sequencing and triggeringSpecific processing jobs define execution sequences and triggering events for individual files stored in the IBM SPSS Collaboration and Deployment Services Repository.Collaboration and Deployment Services Deployment ManagerDeployment ManagerIBM SPSSsequencingtriggeringFor churn prediction, the jobs which perform the training of the model and the scoring of the model have been separated. The data for training needs to be prepared and loaded in the Customer Insight for Communication Service Providers churn tables. Once this is performed, the job \CSP_CustomerInsight_NPS\Jobs\Training Churn Prediction Model present in IBM SPSS Collaboration and Deployment Services needs to be run from the SPSS CADS Deployment Manager. This will create the predictive model nuggets which will be used subsequently in the job used to score the active customers. Failure to run this job before running the \CSP_CustomerInsight_NPS\Jobs\Scoring Churn Prediction Model will result in error.The job \CSP_CustomerInsight_NPS\Jobs\Scoring Churn Prediction Model will be triggered each time the sqoop job for transferring the churn dataset from the Analytics Platform node to the DB2 data node is complete.The job \CSP_CustomerInsight_NPS\Jobs\Load Report Tables will be triggered each time the sqoop job for transferring the NPS dataset from the Analytics Platform node to the DB2 data node is complete.Deploying IBM SPSS contentYou must create a data source connection, and then import the content files into IBM SPSS Deployment Manager for Collaboration and Deployment Services.

SPSS job sequencing and triggering

Specific processing jobs define execution sequences and triggering events for individual files stored in the IBM® SPSS® Collaboration and Deployment Services Repository.

For churn prediction, the jobs which perform the training of the model and the scoring of the model have been separated. The data for training needs to be prepared and loaded in the Customer Insight for Communication Service Providers churn tables. Once this is performed, the job \CSP_CustomerInsight_NPS\Jobs\Training Churn Prediction Model present in IBM SPSS Collaboration and Deployment Services needs to be run from the SPSS CADS Deployment Manager. This will create the predictive model nuggets which will be used subsequently in the job used to score the active customers. Failure to run this job before running the \CSP_CustomerInsight_NPS\Jobs\Scoring Churn Prediction Model will result in error.

The job \CSP_CustomerInsight_NPS\Jobs\Scoring Churn Prediction Model will be triggered each time the sqoop job for transferring the churn dataset from the Analytics Platform node to the DB2® data node is complete.

The job \CSP_CustomerInsight_NPS\Jobs\Load Report Tables will be triggered each time the sqoop job for transferring the NPS® dataset from the Analytics Platform node to the DB2 data node is complete.

Parent topic: Deploying IBM SPSS content

Changing churn factor labels You can change the churn factor labels to suit your business needs.IBM SPSSchurn factorsEach time the SPSS training job is run, it creates a decision list model. The decision list model nugget is then exported to a .csv file so that it can be provided as an additional input apart from the churn propensity and displayed in the Churn Management Report. The idea is to provide actionable insights for the churn along with providing the churn propensity and the expected churn date.The decision list usually has a list of a few variables expressed as an if/else condition. A business analyst or user can interpret these segments and provide labels which can be used in the churn management report. This will help the users of the churn management report understand the reason for the churn. Providing of labels is optional. In the event that the label is not provided, the base ruleset that appeared in the decision list will appear in the churn factors column.To provide the Churn_Factors with easy to understand labels, the following steps need to be performed.Copy the file Decision List Formatted.csv located in the folder /opt/IBM/SPSS/ModelerServer/17.0/data in the SPSS/Analytics node.Open the comma separated file in a spreadsheet. You will see these columns: ID, NBCORRECT, RECORD_COUNT SCORE, CHURN_RULES, and CHURN_FACTORS.Input values in the Churn_Factors column can be changed to something more meaningful. For instance, a churn rule from the decision list which states OVERALL_EXP_SCORE_5 greaterThan 0.500000 and OVERALL_EXP_SCORE_5 lessOrEqual 3 can be labeled as Low Overall Experience Score and entered in the Churn_Factors column.In the example in step 3, the scoring stream will identify Low Overall Experience Score as the churn factor and display the same based on the Rule Id.Deploying IBM SPSS contentYou must create a data source connection, and then import the content files into IBM SPSS Deployment Manager for Collaboration and Deployment Services.

Changing churn factor labels

You can change the churn factor labels to suit your business needs.

Each time the SPSS training job is run, it creates a decision list model. The decision list model nugget is then exported to a .csv file so that it can be provided as an additional input apart from the churn propensity and displayed in the Churn Management Report. The idea is to provide actionable insights for the churn along with providing the churn propensity and the expected churn date.

The decision list usually has a list of a few variables expressed as an if/else condition. A business analyst or user can interpret these segments and provide labels which can be used in the churn management report. This will help the users of the churn management report understand the reason for the churn. Providing of labels is optional. In the event that the label is not provided, the base ruleset that appeared in the decision list will appear in the churn factors column.

To provide the Churn_Factors with easy to understand labels, the following steps need to be performed.

Copy the file Decision List Formatted.csv located in the folder /opt/IBM/SPSS/ModelerServer/17.0/data in the SPSS/Analytics node.

Open the comma separated file in a spreadsheet. You will see these columns: ID, NBCORRECT, RECORD_COUNT SCORE, CHURN_RULES, and CHURN_FACTORS.

Input values in the Churn_Factors column can be changed to something more meaningful. For instance, a churn rule from the decision list which states OVERALL_EXP_SCORE_5 greaterThan 0.500000 and OVERALL_EXP_SCORE_5 lessOrEqual 3 can be labeled as Low Overall Experience Score and entered in the Churn_Factors column.

In the example in step 3, the scoring stream will identify Low Overall Experience Score as the churn factor and display the same based on the Rule Id.

Parent topic: Deploying IBM SPSS content

Improving the SPSS model performanceYou can fine-tune the SPSS model performance.IBM SPSSIBM SPSSmodel performancechurn predictionThe Model Training stream Churn Prediction Model Training.str is used to train the two predictive models that are used for scoring. The first predictive model is a decision list, which provides the rules to identify segments that have a higher propensity to churn, along with the propensity to churn. The second predictive model is a COX regression model, which uses the attributes of the customer to identify when they are likely to churn.In the decision list, changing the following options can alter the performance characteristics, such as time needed to build the model and overall accuracy of the mode:Decreasing the minimum segment size will create smaller segments. When decreasing the minimum segment size, the maximum number of segments need to be increased correspondingly, so that you can adequately cover the population. For instance, with a minimum segment size of 0.5% and a maximum number of groups of 100, we are likely to cover upwards of 50% of the total population based on their propensity to churn. The rest of the population can be considered as likely to be active. However, increasing the maximum number of segments is likely to increase the model development time proportionately.Increasing the confidence interval for new conditions will decrease the number of segments formed. However, they will be more reliable segments.The analysis weight is currently set as 3 for churned customers and 1 for active customers. This is set in the supernode Data Cleansing in the node Analysis Weight. This results in oversampling of churned customers. This will help provide importance to identifying churned customers. If the number of active customers is very high and there is a need to decrease model development time, the analysis weight can be changed to 1 for churned customers and 0.34 for active customers. This will result in undersampling of active customers and provide improvements in the model development time.The Analysis Weight proportion should reflect the business priorities of how important it is to identify customers likely to churn over the ones that remain active. In an environment where there is a customer churn of 25% a year, an analysis weight of 3:1 might be good to make the importance equal in proportion. In an environment where customer churn is already 50%, an analysis weight proportion of 1:1 might be sufficient.Balancing can be used effectively to reduce the number of records instead of analysis weight, which could reduce the time needed to train for both the Decision List & Cox Regression Model Development.The time required for Model Scoring Churn Prediction Model Scoring.str can be improved by having intermediate tables from which the data can be loaded. Subsequent sections of the stream can read the data for scoring. This can be used to have SQL pushback features increase the speed of the stream overall by distributing a significant portion of the workload to the database.Splitting the data for scoring purposes into multiple divisions and running the streams in parallel can help improve the performance.Deploying IBM SPSS contentYou must create a data source connection, and then import the content files into IBM SPSS Deployment Manager for Collaboration and Deployment Services.

Improving the SPSS model performance

You can fine-tune the SPSS model performance.

The Model Training stream Churn Prediction Model Training.str is used to train the two predictive models that are used for scoring. The first predictive model is a decision list, which provides the rules to identify segments that have a higher propensity to churn, along with the propensity to churn. The second predictive model is a COX regression model, which uses the attributes of the customer to identify when they are likely to churn.

In the decision list, changing the following options can alter the performance characteristics, such as time needed to build the model and overall accuracy of the mode:

Decreasing the minimum segment size will create smaller segments. When decreasing the minimum segment size, the maximum number of segments need to be increased correspondingly, so that you can adequately cover the population. For instance, with a minimum segment size of 0.5% and a maximum number of groups of 100, we are likely to cover upwards of 50% of the total population based on their propensity to churn. The rest of the population can be considered as likely to be active. However, increasing the maximum number of segments is likely to increase the model development time proportionately.

Increasing the confidence interval for new conditions will decrease the number of segments formed. However, they will be more reliable segments.

The analysis weight is currently set as 3 for churned customers and 1 for active customers. This is set in the supernode Data Cleansing in the node Analysis Weight. This results in oversampling of churned customers. This will help provide importance to identifying churned customers. If the number of active customers is very high and there is a need to decrease model development time, the analysis weight can be changed to 1 for churned customers and 0.34 for active customers. This will result in undersampling of active customers and provide improvements in the model development time.

The Analysis Weight proportion should reflect the business priorities of how important it is to identify customers likely to churn over the ones that remain active. In an environment where there is a customer churn of 25% a year, an analysis weight of 3:1 might be good to make the importance equal in proportion. In an environment where customer churn is already 50%, an analysis weight proportion of 1:1 might be sufficient.

Balancing can be used effectively to reduce the number of records instead of analysis weight, which could reduce the time needed to train for both the Decision List & Cox Regression Model Development.

The time required for Model Scoring Churn Prediction Model Scoring.str can be improved by having intermediate tables from which the data can be loaded. Subsequent sections of the stream can read the data for scoring. This can be used to have SQL pushback features increase the speed of the stream overall by distributing a significant portion of the workload to the database.

Splitting the data for scoring purposes into multiple divisions and running the streams in parallel can help improve the performance.

Parent topic: Deploying IBM SPSS content

Loading data and starting the predictive analytics jobAfter the Analytics Platform is installed, you must configure and run the data load process and start the predictive analytics job. This is required for churn and NPS predictive analytics. data loadIBM SPSSjobstartingEnsure that the following conditions are met:The Analytics Platform is installed.You have a user ID that has access to the IBM InfoSphere BigInsights database that is on the Analytics Platform node.IBM InfoSphere BigInsights is running.The IBM DB2 database exists on the data node.The runDBExport.sh script extracts data from the IBM InfoSphere BigInsights database on the Analytics Platform node and loads it into the IBM DB2 database on the data node. The script takes a parameter that runs the following variations of the script: runDBExport.sh npsExtracts and loads the nps data. runDBExport.sh churnExtracts and loads the churn data. The following table lists the parameters in the config.properties file that you must configure:Parameters in the config.properties fileParameterDescriptionDefault valueHiveHostChange the hive host and port numberlocalhost:10000/defaultHiveUserHive user namehiveHivePasswdHive user passwordNo default value.DB2HostDB2 Host and DB2 port numberlocalhost:50000DB2UserDB2 user namedb2inst1DB2PasswdDB2 user passwordNo default value.SqoopHostChange the Sqoop host address and sqoop port numberlocalhost:12000/sqoopHiveDataDirectoryLocation of the Hive warehouse directory on the Analytics Platform node/apps/hive/warehouse/tnf.dbThe hive data directory can be determined by running the desc formatted <table name> command on a hive table and checking the location value. Enter the location after the port number.SPSSEndPointURL of the IBM Predictive Customer Intelligence job. Update the host address.http://localhost:9080/process/services/ProcessManagementSPSSIDJob ID of SPSS. The OBJECT URI of the job to be started. The value can be determined by right-clicking the job in Deployment Manager and selecting properties.No default value.SPSSUserSPSS CADS User ID. Used to log in to the Deployment Manager.adminSPSSPasswdSPSS CADS Password.No default value.Add in Hadoop Port default 8020. You can determine your hive data directory by running the desc formatted <table name> command on a hive table and checking the location value. Enter the same port number that appears in the location field. After you have updated the password, you must apply Base-64 encoding. Base-64 encoding of Sqoop configuration files To Base-64 encode the passwords in each config.properties file, run the following command: script/encodePasswordProperties.sh -f conf/<config_file_name>.properties All plain-text passwords in the configuration file will be encoded. If you need to update a password, you can change the password property in the configuration file to its plain-text equivalent and re-encode just that property. To do this, pass the property name with the -p flag. For example, you could run the following: script/encodePasswordProperties.sh -f conf/<config_file_name>.properties -p <SPSSPasswd> This script must be run on a configuration file prior to running runDBExport.sh, or the decoded plain-text passwords will be invalid and the operation will fail.Log on to the Analytics Platform node.Change directory to /opt/IBM/IS_CSP_Customer_Insight_1.0.4.Decompress the CSP_CustomerInsight_DB folder.Copy the following files to the SqoopHomeDir/lib and HiveHomeDir/lib folders:db2jcc.jardb2jcc_licence_cu.jarOpen the config.properties file and change the parameters to refer to IBM InfoSphere BigInsights and the IBM DB2 database.Refer to the table in About this task for information about the parameters to change.There are two configuration files in /opt/IBM/IS_CSP_CustomerInsight_1.0.4/CSP_CustomerInsight_DB/conf: churn_config.properties and nps_config.properties. Enter the following commands: chmod 755 runDBExport.sh chmod 755 script/sqoop.shInstalling the solution contentInstalling the solution content involves deploying installation files and content on the nodes, installing datasets, configuring the TELCO DB2 database, configuring ETL, configuring SPSS content, deploying reports, dashboards, and creating a connection to BigInsights. Configuring the sample Cognos icon service (optional)The Cognos Dashboards icon service allows Cognos Analytics to access images and other graphical objects.

Loading data and starting the predictive analytics job

After the Analytics Platform is installed, you must configure and run the data load process and start the predictive analytics job. This is required for churn and NPS predictive analytics.

Before you begin

Ensure that the following conditions are met:

The Analytics Platform is installed.

You have a user ID that has access to the IBM® InfoSphere® BigInsights® database that is on the Analytics Platform node.

IBM InfoSphere BigInsights is running.

The IBM DB2® database exists on the data node.

About this task

The runDBExport.sh script extracts data from the IBM InfoSphere BigInsights database on the Analytics Platform node and loads it into the IBM DB2 database on the data node. The script takes a parameter that runs the following variations of the script:

runDBExport.sh nps

Extracts and loads the nps data.

runDBExport.sh churn

Extracts and loads the churn data.

The following table lists the parameters in the config.properties file that you must configure:

Table 1. Parameters in the config.properties file

Parameter
Description
Default value

HiveHost
Change the hive host and port number
localhost:10000/default

HiveUser
Hive user name
hive

HivePasswd
Hive user password
No default value.

DB2Host
DB2 Host and DB2 port number
localhost:50000

DB2User
DB2 user name
db2inst1

DB2Passwd
DB2 user password
No default value.

SqoopHost
Change the Sqoop host address and sqoop port number
localhost:12000/sqoop

HiveDataDirectory
Location of the Hive warehouse directory on the Analytics Platform node
/apps/hive/warehouse/tnf.db

The hive data directory can be determined by running the desc formatted <table name> command on a hive table and checking the location value. Enter the location after the port number.

SPSSEndPoint
URL of the IBM Predictive Customer Intelligence job. Update the host address.
http://localhost:9080/process/services/ProcessManagement

SPSSID

Job ID of SPSS®. The OBJECT URI of the job to be started. The value can be determined by right-clicking the job in Deployment Manager and selecting properties.
No default value.

SPSSUser
SPSS CADS User ID. Used to log in to the Deployment Manager.
admin

SPSSPasswd
SPSS CADS Password.
No default value.

Add in Hadoop Port default 8020. You can determine your hive data directory by running the desc formatted <table name> command on a hive table and checking the location value. Enter the same port number that appears in the location field.

After you have updated the password, you must apply Base-64 encoding.

Base-64 encoding of Sqoop configuration files

To Base-64 encode the passwords in each config.properties file, run the following command:

script/encodePasswordProperties.sh -f conf/<config_file_name>.properties

All plain-text passwords in the configuration file will be encoded. If you need to update a password, you can change the password property in the configuration file to its plain-text equivalent and re-encode just that property. To do this, pass the property name with the -p flag. For example, you could run the following:

script/encodePasswordProperties.sh -f conf/<config_file_name>.properties -p <SPSSPasswd>

This script must be run on a configuration file prior to running runDBExport.sh, or the decoded plain-text passwords will be invalid and the operation will fail.

Procedure

Log on to the Analytics Platform node.

Change directory to /opt/IBM/IS_CSP_Customer_Insight_1.0.4.

Decompress the CSP_CustomerInsight_DB folder.

Copy the following files to the SqoopHomeDir/lib and HiveHomeDir/lib folders:

db2jcc.jar

db2jcc_licence_cu.jar

Open the config.properties file and change the parameters to refer to IBM InfoSphere BigInsights and the IBM DB2 database. Refer to the table in About this task for information about the parameters to change.

Note: There are two configuration files in /opt/IBM/IS_CSP_CustomerInsight_1.0.4/CSP_CustomerInsight_DB/conf: churn_config.properties and nps_config.properties.

Enter the following commands:

chmod 755 runDBExport.sh
chmod 755 script/sqoop.sh

Configuring the sample Cognos icon service (optional)
The Cognos Dashboards icon service allows Cognos Analytics to access images and other graphical objects.

Parent topic: Installing the solution content

Configuring the sample Cognos icon service (optional)The Cognos Dashboards icon service allows Cognos Analytics to access images and other graphical objects. Sample configurationCognos Analytics does not allow dashboards to access such objects using file:// schemes; resources must be accessed over https://. This service provides https:// access. The service is implemented as a Python SimpleHTTPService. It provides a small set of images in PNG and SVG format that can be added. Restart the service after adding or updating images. To run the service, run the following: ./ctl.sh startTo stop the service, run the following: ./ctl.sh stopOnly an Analytics Platform administrative user can execute these commands. By default, the service listens on port 4333. The ctrl.sh script can be edited to listen on a different port. The arguments that can be supplied to IconService.sh are as follows:-p postNo -s certificatePathLoading data and starting the predictive analytics jobAfter the Analytics Platform is installed, you must configure and run the data load process and start the predictive analytics job. This is required for churn and NPS predictive analytics.

Configuring the sample Cognos icon service (optional)

The Cognos Dashboards icon service allows Cognos Analytics to access images and other graphical objects.

Cognos Analytics does not allow dashboards to access such objects using file:// schemes; resources must be accessed over https://. This service provides https:// access.

The service is implemented as a Python SimpleHTTPService. It provides a small set of images in PNG and SVG format that can be added. Restart the service after adding or updating images.

To run the service, run the following:

./ctl.sh start

To stop the service, run the following:

./ctl.sh stop

Only an Analytics Platform administrative user can execute these commands. By default, the service listens on port 4333. The ctrl.sh script can be edited to listen on a different port. The arguments that can be supplied to IconService.sh are as follows:

-p postNo -s certificatePath

Parent topic: Loading data and starting the predictive analytics job

Using Customer Insight for Communication Service ProvidersThis section describes a typical user case that shows how to use the Customer Insight for Communication Service Providers solution to understand customer experience trends. IBM Customer Insight for Communication Service Providers is composed of three separate components:a net promoter score (NPS) correlation applicationa churn management applicationa customer behavior dataset The NPS correlation and churn management applications include an IBM Cognos user interface, which are described in the workflow procedures. The churn management application provides an analysis of subscriber data suggesting how likely and when a customer is likely to churn, as well predicting the factors that influence churn. The customer behavior dataset provides the following:a set of tables customers can accessan accompanying data dictionary The dataset contains subscribers' usage data, including their interests and preferences. The application analyzes the amount of time subscribers spend browsing, searching, reading, and streaming information on their devices. Each period of activity is categorized, where possible, into one of hundreds of interest categories, enabling communication service providers to categorize their subscribers into hundreds of different micro-segments based upon these interests. Workflow and user roles This workflow shows how the NPS correlation application provides a dashboard and key metrics to a communication service provider. For this example, a customer experience team member investigates the NPS score for mobile data. A typical process workflow is described. The workflow also provides a set of key metrics demonstrating the churn management application. For this example, the likelihood of a subscriber's churn propensity is associated with their churn propensity score. This functionality gives communication service providers (CSPs) the ability to identify customers who are likely to churn and also those of greatest value to the CSP. It also provides the ability to predict the factors influencing churn using the top rulesets and subscriber trend data. A typical process workflow is described. Using the NPS correlation applicationThe Customer Insight for Communication Service Providers solution provides in-depth analytics to help communication service providers evaluate key subscriber metrics.Using the churn management applicationThe churn management application utilizes standard churn management inputs, as well as voice, SMS, and mobile data records, to analyze trends in subscriber voice, SMS, and mobile data and to provide an interpretation of the churn model. Using the over-the-top applicationThe over-the-top (OTT) application delivers pre-built out-of-the-box dashboards. Communication Service Providers can quickly visualize changing trends in how customers are using devices and applicationsUsing the profile applicationThe user profile application helps Communication Service Provides to view the type of customer profiles using their network.

Using Customer Insight for Communication Service Providers

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

IBM Customer Insight for Communication Service Providers is composed of three separate components:

a net promoter score (NPS) correlation application

a churn management application

a customer behavior dataset

The NPS correlation and churn management applications include an IBM Cognos user interface, which are described in the workflow procedures.

The churn management application provides an analysis of subscriber data suggesting how likely and when a customer is likely to churn, as well predicting the factors that influence churn.

The customer behavior dataset provides the following:

a set of tables customers can access

an accompanying data dictionary

The dataset contains subscribers' usage data, including their interests and preferences. The application analyzes the amount of time subscribers spend browsing, searching, reading, and streaming information on their devices. Each period of activity is categorized, where possible, into one of hundreds of interest categories, enabling communication service providers to categorize their subscribers into hundreds of different micro-segments based upon these interests.

Workflow and user roles

This workflow shows how the NPS correlation application provides a dashboard and key metrics to a communication service provider. For this example, a customer experience team member investigates the NPS score for mobile data. A typical process workflow is described.

The workflow also provides a set of key metrics demonstrating the churn management application. For this example, the likelihood of a subscriber's churn propensity is associated with their churn propensity score. This functionality gives communication service providers (CSPs) the ability to identify customers who are likely to churn and also those of greatest value to the CSP. It also provides the ability to predict the factors influencing churn using the top rulesets and subscriber trend data. A typical process workflow is described.

Using the NPS correlation application
The Customer Insight for Communication Service Providers solution provides in-depth analytics to help communication service providers evaluate key subscriber metrics.

Using the churn management application
The churn management application utilizes standard churn management inputs, as well as voice, SMS, and mobile data records, to analyze trends in subscriber voice, SMS, and mobile data and to provide an interpretation of the churn model.

Using the over-the-top application
The over-the-top (OTT) application delivers pre-built out-of-the-box dashboards. Communication Service Providers can quickly visualize changing trends in how customers are using devices and applications

Using the profile application
The user profile application helps Communication Service Provides to view the type of customer profiles using their network.

Using the NPS correlation applicationThe Customer Insight for Communication Service Providers solution provides in-depth analytics to help communication service providers evaluate key subscriber metrics.NPS correlation applicationThis task describes how a typical customer experience team member would use the reports to investigate net promoter score (NPS) and transactional-NPS. The data is linked to the actual activity of subscribers. Subscriber data such as services, devices, or location are linked to their NPS, providing an enhanced view of the network and services. The screen shots shown are for example purposes and will vary depending on your particular implementation. Open the Behavior Based Customer Insight Top Factors report.The T-NPS score of -61.02 indicates a high number of unhappy subscribers. This number reflects promoters (approximately 9%) minus detractors (approximately 70%). Factors driving the NPS data are summarized in the bar chart and legend.Filter the data category based on Data Activity. The top 10 factors change to reflect the Data Activity category. The number of applications used on the UTRAN (3G) network is the most significant. Click the Factor Analysis icon to launch the Factor Analysis page for NUM_APPLICATIONS_UTRAN. With the Factor Analysis threshold set at 3, subscribers who are running more than three applications on UTRAN (a 3G network) have much lower NPS scores than those who are using three or less. With a similar number of subscribers, this analysis is statistically significant. The customer experience team can then use this as a means of further investigation. Apply further filters to the analysis, setting the data to show only female customers. With this filter applied, the analysis shows an even greater difference between females who use more than three applications on 3G versus females who use three applications or less on 3G. A customer experience team member might then use this information for further investigation. For example, what type of applications were involved in creating this apparent negative experience for the subscribers in question? Using Customer Insight for Communication Service ProvidersThis section describes a typical user case that shows how to use the Customer Insight for Communication Service Providers solution to understand customer experience trends.

Using the NPS correlation application

The Customer Insight for Communication Service Providers solution provides in-depth analytics to help communication service providers evaluate key subscriber metrics.

About this task

This task describes how a typical customer experience team member would use the reports to investigate net promoter score (NPS) and transactional-NPS. The data is linked to the actual activity of subscribers. Subscriber data such as services, devices, or location are linked to their NPS, providing an enhanced view of the network and services.

The screen shots shown are for example purposes and will vary depending on your particular implementation.

Procedure

Open the Behavior Based Customer Insight Top Factors report.Dashboard showing scores for NPS, detractors, passives, promoters, and subscribers. Factors driving T-NPS, such as gender or age, are shown in a bar chart.

The T-NPS score of -61.02 indicates a high number of unhappy subscribers. This number reflects promoters (approximately 9%) minus detractors (approximately 70%). Factors driving the NPS data are summarized in the bar chart and legend.

Filter the data category based on Data Activity. The top 10 factors change to reflect the Data Activity category. The number of applications used on the UTRAN (3G) network is the most significant. The same dashboard shown in step 1, with the bar chart factors filtered by data activity.

Click the Factor Analysis icon An icon indicating a small line graph, used for the Factor Analysis report. to launch the Factor Analysis page for NUM_APPLICATIONS_UTRAN.Report page showing scores for T-NPS, detractors, passives, promotors, and subscribers, filtered by the specific factor and a threshold.

With the Factor Analysis threshold set at 3, subscribers who are running more than three applications on UTRAN (a 3G network) have much lower NPS scores than those who are using three or less. With a similar number of subscribers, this analysis is statistically significant. The customer experience team can then use this as a means of further investigation.

Apply further filters to the analysis, setting the data to show only female customers.The same report page as step 3, being filtered additionally by gender.

With this filter applied, the analysis shows an even greater difference between females who use more than three applications on 3G versus females who use three applications or less on 3G. A customer experience team member might then use this information for further investigation. For example, what type of applications were involved in creating this apparent negative experience for the subscribers in question?

Parent topic: Using Customer Insight for Communication Service Providers

Using the churn management applicationThe churn management application utilizes standard churn management inputs, as well as voice, SMS, and mobile data records, to analyze trends in subscriber voice, SMS, and mobile data and to provide an interpretation of the churn model. Churn Management applicationThis task describes how a typical customer experience team member would use the reports to investigate a set of subscribers and evaluate their likelihood to churn based on their churn propensity and other factors. It also describes the ability to predict the factors influencing churn using the top rulesets and subscriber trend data The screen shots shown are for example purposes and will vary depending on your particular implementation. Open the Churn Managment Overview report.The main report page shows an overview of the entire subscriber base in the donut chart. Of the 2412 subscribers, 877 are likely to churn based on their churn propensity of >= 0.6. The default report is sorted first by Keep Score and then Churn Propensity Score (both descending). This highlights to communication service providers (CSPs) those subscribers who are the greatest value, as well as those who are most likely to churn.Using the pull-down menus on the report, select the greater than sign (>) and then select a value of 0.60. This filters the subscribers in the Churn Propensity Score column to include only those with a score greater than 0.60. Four other factors are available for filtering:Keep Score: Filters by relative subscriber importance. For example, this factor would allow a customer experience team member to concentrate on those subscribers with a score greater than 50.Churn Date: Provides a projected churn date. For example, this filter would allow a customer experience team member to concentrate on those likely to churn sooner rather than later.Churn Factor: Provides a suggested churn factor. This filter would allow a customer experience team member to segment based on specific factors impacting subscriber satisfaction, including offers which might be available to likely churners (such as Decreasing Prepaid Top Value).Contract Type: Filters by the type of subscribers. For example, this filter would allow a customer experience team member to segment based on Prepay or Postpay subscribers, which may be assigned to different departments.Click the Churn Factors pull-down menu, and select Decreasing Prepaid Top Value.With this filter applied, subscribers are listed whose predominant reason for churn is the decreasing value of their monthly top-up, ranked in descending order by Keep Score and Churn Propensity Score. In this example, there are several very valuable subscribers who are likely to churn by March 2016. These are the subscribers who the CSP would most likely address when attempting to stop subscribers from churning. Click to view the Churn Management Rulesets report. This report contains three report panes: Top 10 Churn Results -- OverallThis pane highlights the top ten rulesets for a specific execution of churn management data. The rulesets are weighted by relevance. This highlights the primary issues contributing to predicted customer churns.Top 5 Churn Rulesets – Trend for Next 6 MonthsThis pane highlights the top five rulesets for a specific execution of churn management data, and predicts the trend of influence for those rulesets for the next six months. This can highlight rising trends in a particular sets of circumstances (such as expiring contracts), which may impact churn rates in the near future.Top 5 Churn Rulesets – Summary for Next 6 MonthsThis pane highlights the top five rulesets for a specific execution of churn management data, and provides an overview of how those rulesets may influence churn over the next six months. The donut charts summarize the predicted percentage of churn contribution and also the estimated number of affected subscribers.Using Customer Insight for Communication Service ProvidersThis section describes a typical user case that shows how to use the Customer Insight for Communication Service Providers solution to understand customer experience trends.

Using the churn management application

The churn management application utilizes standard churn management inputs, as well as voice, SMS, and mobile data records, to analyze trends in subscriber voice, SMS, and mobile data and to provide an interpretation of the churn model.

About this task

This task describes how a typical customer experience team member would use the reports to investigate a set of subscribers and evaluate their likelihood to churn based on their churn propensity and other factors. It also describes the ability to predict the factors influencing churn using the top rulesets and subscriber trend data

The screen shots shown are for example purposes and will vary depending on your particular implementation.

Procedure

Open the Churn Managment Overview report.Basic Churn Management report page showing the data using the default settings.

The main report page shows an overview of the entire subscriber base in the donut chart. Of the 2412 subscribers, 877 are likely to churn based on their churn propensity of >= 0.6. The default report is sorted first by Keep Score and then Churn Propensity Score (both descending). This highlights to communication service providers (CSPs) those subscribers who are the greatest value, as well as those who are most likely to churn.

Using the pull-down menus on the report, select the greater than sign (>) and then select a value of 0.60. The same report shown in Step 1, with 0.60 being selected in the Churn Propensity Score pull-down menu.

This filters the subscribers in the Churn Propensity Score column to include only those with a score greater than 0.60.

Four other factors are available for filtering:

Keep Score: Filters by relative subscriber importance. For example, this factor would allow a customer experience team member to concentrate on those subscribers with a score greater than 50.

Churn Date: Provides a projected churn date. For example, this filter would allow a customer experience team member to concentrate on those likely to churn sooner rather than later.

Churn Factor: Provides a suggested churn factor. This filter would allow a customer experience team member to segment based on specific factors impacting subscriber satisfaction, including offers which might be available to likely churners (such as Decreasing Prepaid Top Value).

Contract Type: Filters by the type of subscribers. For example, this filter would allow a customer experience team member to segment based on Prepay or Postpay subscribers, which may be assigned to different departments.

Click the Churn Factors pull-down menu, and select Decreasing Prepaid Top Value.The same report shown in Step 3, now primarily filtered by Churn Factors.

With this filter applied, subscribers are listed whose predominant reason for churn is the decreasing value of their monthly top-up, ranked in descending order by Keep Score and Churn Propensity Score. In this example, there are several very valuable subscribers who are likely to churn by March 2016. These are the subscribers who the CSP would most likely address when attempting to stop subscribers from churning.

Click Icon for the Churn Rulesets report. to view the Churn Management Rulesets report.

This report contains three report panes:

Top 10 Churn Results -- Overall

This pane highlights the top ten rulesets for a specific execution of churn management data. The rulesets are weighted by relevance. This highlights the primary issues contributing to predicted customer churns.

Top 5 Churn Rulesets – Trend for Next 6 Months

This pane highlights the top five rulesets for a specific execution of churn management data, and predicts the trend of influence for those rulesets for the next six months. This can highlight rising trends in a particular sets of circumstances (such as expiring contracts), which may impact churn rates in the near future.

Top 5 Churn Rulesets – Summary for Next 6 Months

This pane highlights the top five rulesets for a specific execution of churn management data, and provides an overview of how those rulesets may influence churn over the next six months. The donut charts summarize the predicted percentage of churn contribution and also the estimated number of affected subscribers.

Parent topic: Using Customer Insight for Communication Service Providers

Using the over-the-top applicationThe over-the-top (OTT) application delivers pre-built out-of-the-box dashboards. Communication Service Providers can quickly visualize changing trends in how customers are using devices and applicationsOver-the-top applicationThis task describes how a typical customer experience team member would use the OTT dashboards The screen shots shown are for example purposes and will vary depending on your particular implementation. Open the Over the Top Application dashboard. The first dashboard is the OTT overview. This dashboard shows the Fastest Growing OTT Apps by Volume Usage.This dashboard can be filtered by application type to graphically illustrate the top 10 fastest growing OTT applications by volume usage.Click the Customer Summary tab to view the Top Video Apps, Top Music Apps, and Top Voice & Messaging Apps.This dashboard graphically illustrates the following information:top 10 video applications by percentage of customerstop 10 music applications by percentage of customerstop 10 voice and messaging applications by percentage of customersClick the Application Summary tab to view the filters by Top OTT Apps by Volume - Past 7 Days and Top OTT Apps by Number of Users - Past 7 Days.This dashboard can be filtered by top devices and device operating system (OS) to graphically illustrate the following information:top OTT applications by volume for the previous 7 daystop OTT applications by users for the previous 7 daysClick the Price Plan Summary tab to view the Top OTT Apps by Number of Customers and OTT Application Category by Number of Users.This dashboard can be filtered by price plan and application to graphically illustrate the following information:top OTT applications by number of customerstop OTT applications category by number of usersClick the Apps Daily Summary tab to view the Top 20 Apps by Number of Customers, Top 20 Apps by Total Volume, and Top 20 Apps - Average Daily Volume.This dashboard graphically illustrates the following information:top 20 applications by number of customerstop 20 applications by total volumetop 20 applications by average daily volume Click the Device Daily Summary tab to view the Top 20 Devices by Number of Customers, Top 20 Devices by Volume Total, and Top 20 Devices - Average Daily Volume.This dashboard graphically illustrates the following information:top 20 devices by number of customerstop 20 devices by total volumetop 20 devices by average daily volume Click the Change Summary tab to view the apps and devices changing by volume and customers.This dashboard graphically illustrates the following information:percentage customer change by application: filterable by device percentage volume change by application: filterable by device percentage customer change by device: filterable by applicationpercentage volume change by device: filterable by applicationUsing Customer Insight for Communication Service ProvidersThis section describes a typical user case that shows how to use the Customer Insight for Communication Service Providers solution to understand customer experience trends.

Using the over-the-top application

The over-the-top (OTT) application delivers pre-built out-of-the-box dashboards. Communication Service Providers can quickly visualize changing trends in how customers are using devices and applications

About this task

This task describes how a typical customer experience team member would use the OTT dashboards

The screen shots shown are for example purposes and will vary depending on your particular implementation.

Procedure

Open the Over the Top Application dashboard. The first dashboard is the OTT overview. This dashboard shows the Fastest Growing OTT Apps by Volume Usage. OTT Overview Report page showing the fastest growing OTT Apps by volume usage.

This dashboard can be filtered by application type to graphically illustrate the top 10 fastest growing OTT applications by volume usage.

Click the Customer Summary tab to view the Top Video Apps, Top Music Apps, and Top Voice & Messaging Apps. Customer Summary dashboard showing bar charts for each of the three apps charts.

This dashboard graphically illustrates the following information:

top 10 video applications by percentage of customers

top 10 music applications by percentage of customers

top 10 voice and messaging applications by percentage of customers

Click the Application Summary tab to view the filters by Top OTT Apps by Volume - Past 7 Days and Top OTT Apps by Number of Users - Past 7 Days. Application Summary Dashboard, showing treemaps for the filters and bar charts for the apps by volume and number.

This dashboard can be filtered by top devices and device operating system (OS) to graphically illustrate the following information:

top OTT applications by volume for the previous 7 days

top OTT applications by users for the previous 7 days

Click the Price Plan Summary tab to view the Top OTT Apps by Number of Customers and OTT Application Category by Number of Users. Price Plan Summary dashboard showing a treemap filters by price plan and top OTT apps, and a donut chart for OTT application category by number of users.

This dashboard can be filtered by price plan and application to graphically illustrate the following information:

top OTT applications by number of customers

top OTT applications category by number of users

Click the Apps Daily Summary tab to view the Top 20 Apps by Number of Customers, Top 20 Apps by Total Volume, and Top 20 Apps - Average Daily Volume. Apps Daily Summary dashboard showing treemaps for the filters and a bar chart for the top 20 apps.

This dashboard graphically illustrates the following information:

top 20 applications by number of customers

top 20 applications by total volume

top 20 applications by average daily volume

Click the Device Daily Summary tab to view the Top 20 Devices by Number of Customers, Top 20 Devices by Volume Total, and Top 20 Devices - Average Daily Volume. Device Daily Summary dashboard showing treemaps for the filters and a bar chart for the top 20 devices.

This dashboard graphically illustrates the following information:

top 20 devices by number of customers

top 20 devices by total volume

top 20 devices by average daily volume

Click the Change Summary tab to view the apps and devices changing by volume and customers.

This dashboard graphically illustrates the following information:

percentage customer change by application: filterable by device

percentage volume change by application: filterable by device

percentage customer change by device: filterable by application

percentage volume change by device: filterable by application

Parent topic: Using Customer Insight for Communication Service Providers

Using the profile applicationThe user profile application helps Communication Service Provides to view the type of customer profiles using their network. Profile applicationThis task describes how a typical customer experience team member would use the Profile dashboards The screen shots shown are for example purposes and will vary depending on your particular implementation. Open the Mobile Profile dashboard. This dashboard provides the ability to view the mobility profiles of all customers.This dashboard graphically illustrates the following information:Mobility Profile by # of Subscribers: filterable by device, gender, and age rangeDevice by # of Subscribers: filterable by mobility profile, age, and gender Age Range by # of Subscribers: filterable by mobility profile, gender, and device Gender by # of Subscribers: filterable by mobility profile, age, and device Click the Usage Profile tab to view the Usage Profile dashboard.This dashboard graphically illustrates the following information:Usage Profile by # of Subscribers: filterable by device, gender, and age rangeDevice by # of Subscribers: filterable by usage profile, age, and gender Age Range by # of Subscribers: filterable by usage profile, gender, and device Gender by # of Subscribers: filterable by usage profile, age, and deviceClick the Subscriber Profile tab to view metrics for an individual customer. This dashboard can be filtered by IMSI and graphically illustrates the following information:All fields can be used as filters. Device UsedMobility ProfileUsage ProfileExperience ProfilesHome LocationWork LocationWeekend LocationTop CategoriesTop DomainsTop InterestsUsing Customer Insight for Communication Service ProvidersThis section describes a typical user case that shows how to use the Customer Insight for Communication Service Providers solution to understand customer experience trends.

Using the profile application

The user profile application helps Communication Service Provides to view the type of customer profiles using their network.

About this task

This task describes how a typical customer experience team member would use the Profile dashboards

The screen shots shown are for example purposes and will vary depending on your particular implementation.

Procedure

Open the Mobile Profile dashboard. This dashboard provides the ability to view the mobility profiles of all customers. Mobility Profile dashboard providing the charts for mobility profile filters: Busy, Daily Grinder, Delivering the Goods, Homebody, Night Shift, Norm Peterson.

This dashboard graphically illustrates the following information:

Mobility Profile by # of Subscribers: filterable by device, gender, and age range

Device by # of Subscribers: filterable by mobility profile, age, and gender

Age Range by # of Subscribers: filterable by mobility profile, gender, and device

Gender by # of Subscribers: filterable by mobility profile, age, and device

Click the Usage Profile tab to view the Usage Profile dashboard. Usage Profile dashboard providing the charts for usage profile filters: Average User, Big Data, High SMS - Low Data, High Voice, High Voice and SMS, and Low Usage Overall.

This dashboard graphically illustrates the following information:

Usage Profile by # of Subscribers: filterable by device, gender, and age range

Device by # of Subscribers: filterable by usage profile, age, and gender

Age Range by # of Subscribers: filterable by usage profile, gender, and device

Gender by # of Subscribers: filterable by usage profile, age, and device

Click the Subscriber Profile tab to view metrics for an individual customer. Subcriber Profile dashboard showing a "Search for IMSI" box and ten primary boxes, showing each of the data in wordle format, except for Top Categories, which is a bar chart.

This dashboard can be filtered by IMSI and graphically illustrates the following information:

Note: All fields can be used as filters.

Device Used

Mobility Profile

Usage Profile

Experience Profiles

Home Location

Work Location

Weekend Location

Top Categories

Top Domains

Top Interests

Parent topic: Using Customer Insight for Communication 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 Analytics 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 Analytics 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|Ciaobao

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

Accessing the SLM log fileTo determine the number of customers in the database, refer to the SLM log file.SLM logSLM tagThe xml files for SLM tagging are generated in the /opt/slm/*.slmtag folder. Information is added until the log file reaches a certain size; then a new log file is created.Output file location /opt/tnf/apps/ci-slm/log 42ca60df8d764911842164c041bf7c8b.slmtagFormat of the output <SchemaVersion>2.1.1</SchemaVersion> <SoftwareIdentity> <PersistentId>42ca60df8d764911842164c041bf7c8b</PersistentId> <Name>IBM Customer Insights for Communications Service Providers</Name> <InstanceId>/opt/tnf/apps/ci-slm</InstanceId> </SoftwareIdentity> <Metric logTime="2016-07-20T00:01:06+01:00"> <Type>RESOURCE_VALUE_UNIT</Type> <SubType>SUBSCRIBER</SubType> <Value>250000</Value> <Period> <StartTime>2016-07-19T00:01:06+01:00</StartTime> <EndTime>2016-07-20T00:01:06+01:00</EndTime> </Period> </Metric> <Metric logTime="2016-07-21T00:01:03+01:00"> <Type>RESOURCE_VALUE_UNIT</Type> <SubType>SUBSCRIBER</SubType> <Value>250000</Value> <Period> <StartTime>2016-07-20T00:01:02+01:00</StartTime> <EndTime>2016-07-21T00:01:02+01:00</EndTime> </Period> </Metric>

Accessing the SLM log file

To determine the number of customers in the database, refer to the SLM log file.

The xml files for SLM tagging are generated in the /opt/slm/*.slmtag folder. Information is added until the log file reaches a certain size; then a new log file is created.

Output file location

/opt/tnf/apps/ci-slm/log
42ca60df8d764911842164c041bf7c8b.slmtag

Format of the output

<SchemaVersion>2.1.1</SchemaVersion>
<SoftwareIdentity>
     <PersistentId>42ca60df8d764911842164c041bf7c8b</PersistentId>
     <Name>IBM Customer Insights for Communications Service Providers</Name>
     <InstanceId>/opt/tnf/apps/ci-slm</InstanceId>
</SoftwareIdentity>
<Metric logTime="2016-07-20T00:01:06+01:00">
     <Type>RESOURCE_VALUE_UNIT</Type>
     <SubType>SUBSCRIBER</SubType>
     <Value>250000</Value>
     <Period>
          <StartTime>2016-07-19T00:01:06+01:00</StartTime>
          <EndTime>2016-07-20T00:01:06+01:00</EndTime>
     </Period>
</Metric>
<Metric logTime="2016-07-21T00:01:03+01:00">
     <Type>RESOURCE_VALUE_UNIT</Type>
     <SubType>SUBSCRIBER</SubType>
     <Value>250000</Value>
     <Period>
          <StartTime>2016-07-20T00:01:02+01:00</StartTime>
          <EndTime>2016-07-21T00:01:02+01:00</EndTime>
     </Period>
</Metric>

TroubleshootingThis section contains troubleshooting information for the Customer Insight 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 Insight 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 Insight 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 known data provision tool error messagesThere are solutions for known data provision tool error messages that you may encounter in IBM Customer Insight for Communication Service Providers.Troubleshooting SPSSIf your SPSS job fails, there are some troubleshooting steps you can follow to resolve the issue.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 2. 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 known data provision tool error messages
There are solutions for known data provision tool error messages that you may encounter in IBM Customer Insight for Communication Service Providers.

Troubleshooting SPSS
If your SPSS® job fails, there are some troubleshooting steps you can follow to resolve the issue.

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 known data provision tool error messagesThere are solutions for known data provision tool error messages that you may encounter in IBM Customer Insight for Communication Service Providers.troubleshootingdata provision tooldata provision tooltroubleshootingSolutions to known data provision tool error messages in IBM Customer Insight for Communication Service Providers.This table describes some specific errors you may encounter when using the data provision tool in Customer Insight for Communication Service Providers and the action you can take to resolve them.Error messageActionPermission denied. This error is a permission denied error with one of the following two messages:java.io.IOException. Cannot run program "runDBExport.sh": error=13, Permission denied.java.io.IOException. Cannot run program "script/sqoop.sh": error=13, Permission denied.Investigate the DBExport.log to search for the error.Check the permission of runDBExport.sh. Refer to the setup documentation for the appropriate steps. Insert link to the setup or installation document here or perhaps add a relationship table to this topic--KarenCheck the permission of sqoop.sh in the script folder in which the sqoop.sh resides. Refer to the setup documentation for the appropriate steps. Insert link to the setup or installation document here or perhaps add a relationship table to this topic--KarenSqoop job failure IOException[main] LoadDB2 ERROR - java.io.IOException: Can't export data, please check task tracker logs.ERROR tool.ExportTool: Error during export: Export job failed!IllegalArgumentException. [main] LoadDB2 ERROR - Caused by: java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]Verify whether the hive data from the nps_score_table (if it's option 1) or the nps_score_table_latest (if it's option 2) contains the new line character (\n) at the EOF. The location of the hive data is specified by the HiveDataDirectory located in the config.properties file.Verify whether the hive data from the nps_score_table (if it's option 1) or the nps_score_table_latest (if it's option 2) contains valid data in the field mentioned by the value of HiveDataDirectory located in the config.properties file.SPSS job error ERROR - Exception !!! java.io.IOException: Server returned HTTP response code: 500 for URL: http://<SPSSHost>:<port>/process/services/ProcessManagementVerify whether SPSS is running and the correct host name and port number have been used.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 known data provision tool error messages

There are solutions for known data provision tool error messages that you may encounter in IBM® Customer Insight for Communication Service Providers.

Table 3. Solutions to known data provision tool error messages in IBM Customer Insight for Communication Service Providers..

Error message
Action

Permission denied.

This error is a permission denied error with one of the following two messages:

java.io.IOException. Cannot run program "runDBExport.sh": error=13, Permission denied.

java.io.IOException. Cannot run program "script/sqoop.sh": error=13, Permission denied.

Investigate the DBExport.log to search for the error.

Check the permission of runDBExport.sh. Refer to the setup documentation for the appropriate steps.

Check the permission of sqoop.sh in the script folder in which the sqoop.sh resides. Refer to the setup documentation for the appropriate steps.

Sqoop job failure

IOException

[main] LoadDB2 ERROR - java.io.IOException: Can't export data, please check task tracker logs.

ERROR tool.ExportTool: Error during export: Export job failed!

IllegalArgumentException. [main] LoadDB2 ERROR - Caused by: java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]

Verify whether the hive data from the nps_score_table (if it's option 1) or the nps_score_table_latest (if it's option 2) contains the new line character (\n) at the EOF.

Tip: The location of the hive data is specified by the HiveDataDirectory located in the config.properties file.

Verify whether the hive data from the nps_score_table (if it's option 1) or the nps_score_table_latest (if it's option 2) contains valid data in the field mentioned by the value of HiveDataDirectory located in the config.properties file.

SPSS job error

ERROR - Exception !!!

java.io.IOException: Server returned HTTP response code: 500 for URL: http://<SPSSHost>:<port>/process/services/ProcessManagement

Verify whether SPSS® is running and the correct host name and port number have been used.

Parent topic: Troubleshooting a problem

Troubleshooting SPSSIf your SPSS job fails, there are some troubleshooting steps you can follow to resolve the issue.Right-click on the Load Report Tables job in the Jobs folder of CSP_CustomerInsights_NPS.Click Show Job History. This will display information about the job runs, their logs, and their status.Select the job that has failed. The job will have three individual SPSS streams. Select the one which has failed.Open the log associated with the failed stream.Scroll to the end of the job to discover the reason the job failed.Common reasons for the job to fail include the unavailability of resources such as:DatabaseMemoryAny of the prerequisite services such as SPSS Modeler Server and CADSTroubleshooting 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 SPSS

If your SPSS® job fails, there are some troubleshooting steps you can follow to resolve the issue.

Procedure

Right-click on the Load Report Tables job in the Jobs folder of CSP_CustomerInsights_NPS.

Click Show Job History. This will display information about the job runs, their logs, and their status.

Select the job that has failed. The job will have three individual SPSS streams. Select the one which has failed.

Open the log associated with the failed stream.

Scroll to the end of the job to discover the reason the job failed.

Results

Common reasons for the job to fail include the unavailability of resources such as:

Database

Memory

Any of the prerequisite services such as SPSS Modeler Server and CADS

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 Telecom Analytics Solutions Version 1.0.4 and may also apply to subsequent releases. Copyright Licensed Materials - Property of IBM © Copyright IBM Corp. 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.Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Notices

©

Product Information

This document applies to IBM Telecom Analytics Solutions Version 1.0.4 and may also apply to subsequent releases.

Copyright

Licensed Materials - Property of IBM

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

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Parent topic: Notices