IntroductionThe IBM Behavior Based Client Insight for Wealth Management 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 Behavior Based Client Insight for Wealth Management solution. It provides information on installation, configuration, and use of the Behavior Based Client Insight for Wealth Management 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 Behavior Based Client Insight for Wealth Management 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. . Behavior Based Client Insight for Wealth Management HTML documentation has accessibility features. PDF documents are supplemental and, as such, include no added accessibility features. Forward-looking statements This documentation describes the current functionality of the product. References to items that are not currently available may be included. No implication of any future availability should be inferred. Any such references are not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of features or functionality remain at the sole discretion of IBM.Samples disclaimer Sample files may contain fictional data manually or machine generated, factual data compiled from academic or public sources, or data used with permission of the copyright holder, for use as sample data to develop sample applications. Product names referenced may be the trademarks of their respective owners. Unauthorized duplication is prohibited.

Introduction

The IBM Behavior Based Client Insight for Wealth Management 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 Behavior Based Client Insight for Wealth Management solution. It provides information on installation, configuration, and use of the Behavior Based Client Insight for Wealth Management 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 Behavior Based Client Insight for Wealth Management have accessibility features. For more information, see Accessibility features.

Behavior Based Client Insight for Wealth Management 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 Behavior Based Client Insight for Wealth Management provides prebuilt analytics that help retail wealth management firms to plan and execute programs for growing and retaining clients and increasing profitability through improved client satisfaction.The solution includes IBM Predictive Customer Intelligence, a solution data model, reporting and dashboard templates, predictive and prescriptive models, and application interfaces for integration with operational systems. It uses enterprise and third-party data that is related to historical and current transactions, research data, client behavioral information, and household relationships. Scope of the solution This version of the solution provides prebuilt models for the following analytics: Client behavioral segmentationClient peer group analysisHousehold relationship analysisClient attrition analysisLife event predictionCross- sell propensityEmail tone analysisTailored news alertsPersonality Insight All analytics within the scope of the solution relate to information on the firm’s clients and prospects within the limits of the number of clients purchased in the license entitlement. The solution may not be used for analytics other than those in the solution scope described here.

Overview

The IBM Behavior Based Client Insight for Wealth Management provides prebuilt analytics that help retail wealth management firms to plan and execute programs for growing and retaining clients and increasing profitability through improved client satisfaction.

The solution includes IBM Predictive Customer Intelligence, a solution data model, reporting and dashboard templates, predictive and prescriptive models, and application interfaces for integration with operational systems. It uses enterprise and third-party data that is related to historical and current transactions, research data, client behavioral information, and household relationships.

Scope of the solution

This version of the solution provides prebuilt models for the following analytics:

Client behavioral segmentation

Client peer group analysis

Household relationship analysis

Client attrition analysis

Life event prediction

Cross- sell propensity

Email tone analysis

Tailored news alerts

Personality Insight

All analytics within the scope of the solution relate to information on the firm’s clients and prospects within the limits of the number of clients purchased in the license entitlement. The solution may not be used for analytics other than those in the solution scope described here.

Using the Behavior Based Client Insight for Wealth Management solutionThe IBM Behavior Based Client Insight for Wealth Management solution provides financial advisors with dashboard that help them to understand and provide better service to their clients while also increasing revenue for the company.using the solutionFor each client, historical data analysis is used to generate a life event model and transaction history. The solution provides analysis of each client’s financial position and also develops a psychographic profile, which defines such things as the customer’s willingness to accept risk for the potential of higher returns. The solution uses this information to divide the client base into behavioral segments and provide predictions about each client's life events. The solution provides wealth advisors with suggestions for the best actions to take for each client.An example of the Behavior Based Client Insight for Wealth Management solution in actionThis fictitious example shows how the IBM Behavior Based Client Insight for Wealth Management solution provides insight that helps an investment advisor to provide the best possible recommendations for his clients.

Using the Behavior Based Client Insight for Wealth Management solution

The IBM Behavior Based Client Insight for Wealth Management solution provides financial advisors with dashboard that help them to understand and provide better service to their clients while also increasing revenue for the company.

For each client, historical data analysis is used to generate a life event model and transaction history. The solution provides analysis of each client’s financial position and also develops a psychographic profile, which defines such things as the customer’s willingness to accept risk for the potential of higher returns. The solution uses this information to divide the client base into behavioral segments and provide predictions about each client's life events. The solution provides wealth advisors with suggestions for the best actions to take for each client.

An example of the Behavior Based Client Insight for Wealth Management solution in action
This fictitious example shows how the IBM Behavior Based Client Insight for Wealth Management solution provides insight that helps an investment advisor to provide the best possible recommendations for his clients.

An example of the Behavior Based Client Insight for Wealth Management solution in actionThis fictitious example shows how the IBM Behavior Based Client Insight for Wealth Management solution provides insight that helps an investment advisor to provide the best possible recommendations for his clients.Bruce Sizemore is a financial advisor with 30 clients under management. He would like to take on more clients without reducing the client experience or the level of service he is able to provide. The solution will help Bruce to quickly determine which of his customers require immediate action and provide recommended actions.Bruce logs in to the solution portlet on his desktop and sees the following view.The numbers at the top of the dashboard tell Bruce that six of his clients are at risk of attrition. The first client on the Analyst Dashboard is Alex Anderson, a high net worth customer who is in danger of attrition. Bruce, wants to keep Alex as a client. He clicks Alex's name to go to the Client Profile report.The Top Events section of the Client Profile report for Alex indicates that client attrition is predicted and prompts Bruce to look at the Client Attrition donut chart for the recommended actions. Bruce sees from the Client Attrition donut chart that Alex has an 88% chance of removing his assets from the company. Bruce clicks below the donut chart to see that the recommended action to avoid Alex's attrition. The recommendation is call Alex and discuss increased portfolio returns. The rationale for the recommendation is also shown. Before making a phone call to Alex, Bruce studies the profile to understand how best to interact with Alex. The Relationship Coach section provides insight into Alex's personality. The Conversation Starters section provides a list of Alex's interests and provides links to articles related to those interests. The Portfolio Discussions section provides information on companies in Alex's investment portfolio that are in the news so that Bruce can be up-to-date on recent events related to those investments.After studying Alex's profile, Bruce gives Alex a call and discusses how he plans to increase the returns from Alex's portfolio. With the insights gained from the Client Profile report, Bruce is able to establish a rapport with Alex, who decides to continue as a client of the firm.After providing service to Alex, Bruce goes back to the Analyst Dashboard and sees that one of his clients, Ian Gray, is expecting a baby. The birth of a child shows up as a detected event and the Recent Communications section shows a Twitter feed in which Ian announces the birth of his child.Bruce phones Ian to congratulate him on the birth of his child and to start a discussion about upgrading his life insurance coverage and starting an education fund for the child.Using the Behavior Based Client Insight for Wealth Management solutionThe IBM Behavior Based Client Insight for Wealth Management solution provides financial advisors with dashboard that help them to understand and provide better service to their clients while also increasing revenue for the company.

An example of the Behavior Based Client Insight for Wealth Management solution in action

This fictitious example shows how the IBM Behavior Based Client Insight for Wealth Management solution provides insight that helps an investment advisor to provide the best possible recommendations for his clients.

Bruce Sizemore is a financial advisor with 30 clients under management. He would like to take on more clients without reducing the client experience or the level of service he is able to provide. The solution will help Bruce to quickly determine which of his customers require immediate action and provide recommended actions.

Bruce logs in to the solution portlet on his desktop and sees the following view.

The numbers at the top of the dashboard tell Bruce that six of his clients are at risk of attrition. The first client on the Analyst Dashboard is Alex Anderson, a high net worth customer who is in danger of attrition. Bruce, wants to keep Alex as a client. He clicks Alex's name to go to the Client Profile report.

The Top Events section of the Client Profile report for Alex indicates that client attrition is predicted and prompts Bruce to look at the Client Attrition donut chart for the recommended actions.

Bruce sees from the Client Attrition donut chart that Alex has an 88% chance of removing his assets from the company. Bruce clicks below the donut chart to see that the recommended action to avoid Alex's attrition.

The recommendation is call Alex and discuss increased portfolio returns. The rationale for the recommendation is also shown. Before making a phone call to Alex, Bruce studies the profile to understand how best to interact with Alex. The Relationship Coach section provides insight into Alex's personality. The Conversation Starters section provides a list of Alex's interests and provides links to articles related to those interests. The Portfolio Discussions section provides information on companies in Alex's investment portfolio that are in the news so that Bruce can be up-to-date on recent events related to those investments.

After studying Alex's profile, Bruce gives Alex a call and discusses how he plans to increase the returns from Alex's portfolio. With the insights gained from the Client Profile report, Bruce is able to establish a rapport with Alex, who decides to continue as a client of the firm.

After providing service to Alex, Bruce goes back to the Analyst Dashboard and sees that one of his clients, Ian Gray, is expecting a baby. The birth of a child shows up as a detected event and the Recent Communications section shows a Twitter feed in which Ian announces the birth of his child.

Bruce phones Ian to congratulate him on the birth of his child and to start a discussion about upgrading his life insurance coverage and starting an education fund for the child.

Parent topic: Using the Behavior Based Client Insight for Wealth Management solution

ReportsThe Behavior Based Client Insight for Wealth Management solution provides reports with dashboard templates, sample predictive models, and application interfaces for integration. reportsThe reports provide information about clients, including financial positions and psychographic profiles based on life event models and transaction history.The following analytics reports are provided:Analyst DashboardRelationship ViewSegmentation ViewClient ProfileAnalyst Dashboard reportWhen an adviser logs in to the solution, the Analyst Dashboard report provides a list of all clients for that analyst.Relationship View reportThe Relationship View report provides a visual representation of how a selected client is related to other people, companies, and organizations. The information in this report is not acquired through analytics, but through information that the wealth management company has entered regarding a client's relationships.Segmentation View reportThe Segmentation View report provides information about a selected segment. You can select any segment to display a list of all clients in that segment, and you can filter the list by detected or predicted life events.Client profile reportThe Client Profile report provides details about a client and recommended actions for the financial advisor.

Reports

The Behavior Based Client Insight for Wealth Management solution provides reports with dashboard templates, sample predictive models, and application interfaces for integration.

The reports provide information about clients, including financial positions and psychographic profiles based on life event models and transaction history.

The following analytics reports are provided:

Analyst Dashboard

Relationship View

Segmentation View

Client Profile

Analyst Dashboard report
When an adviser logs in to the solution, the Analyst Dashboard report provides a list of all clients for that analyst.

Relationship View report
The Relationship View report provides a visual representation of how a selected client is related to other people, companies, and organizations. The information in this report is not acquired through analytics, but through information that the wealth management company has entered regarding a client's relationships.

Segmentation View report
The Segmentation View report provides information about a selected segment. You can select any segment to display a list of all clients in that segment, and you can filter the list by detected or predicted life events.

Client profile report
The Client Profile report provides details about a client and recommended actions for the financial advisor.

Analyst Dashboard reportWhen an adviser logs in to the solution, the Analyst Dashboard report provides a list of all clients for that analyst.reportsanalyst dashboardThe report provides summary information for each client, including a list of their accounts, their net worth, and predicted or detected life events and recommended actions.The top row of the report delivers the following information: SegmentsUse this box to filter the report if you want to show only clients from the selected segment.Clients at risk for attritionShows the number of clients who show a high probability of leaving the company.Clients with product propensityShows the number of clients that have a high propensity of buying a product from the company.Client's assets ownedShows the percentage of the adviser’s business that is internal rather than external. If the percentage has increased month over month, it is displayed in green. If it has declined, it is displayed in red. If it remains unchanged, it is displayed in gray. The body of the report provides summary information for each client, including their accounts, net worth, detected and predicted events and recommendations for action by the adviser. The Net Worth number includes three types of assets: Internal assets, which include the company's products that are held by the client, for example, units in a mutual fund that is run by the company.External assets, which are under management by the company but consist of financial products from other companies, for example, mutual funds that are run by another company.Manually-added assets, which include all assets added manually into the system, for example the value of a house.Click a client's name or picture to see a detailed profile for that client. Click the Relationship View link for a visual representation of the client's relationships with other people and companies. Click the name of the segment, for example Business Owners, to see details for that segment.ReportsThe Behavior Based Client Insight for Wealth Management solution provides reports with dashboard templates, sample predictive models, and application interfaces for integration.

Analyst Dashboard report

When an adviser logs in to the solution, the Analyst Dashboard report provides a list of all clients for that analyst.

The report provides summary information for each client, including a list of their accounts, their net worth, and predicted or detected life events and recommended actions.

The top row of the report delivers the following information:

Segments

Use this box to filter the report if you want to show only clients from the selected segment.

Clients at risk for attrition

Shows the number of clients who show a high probability of leaving the company.

Clients with product propensity

Shows the number of clients that have a high propensity of buying a product from the company.

Client's assets owned

Shows the percentage of the adviser’s business that is internal rather than external. If the percentage has increased month over month, it is displayed in green. If it has declined, it is displayed in red. If it remains unchanged, it is displayed in gray.

The body of the report provides summary information for each client, including their accounts, net worth, detected and predicted events and recommendations for action by the adviser. The Net Worth number includes three types of assets:

Internal assets, which include the company's products that are held by the client, for example, units in a mutual fund that is run by the company.

External assets, which are under management by the company but consist of financial products from other companies, for example, mutual funds that are run by another company.

Manually-added assets, which include all assets added manually into the system, for example the value of a house.

Click a client's name or picture to see a detailed profile for that client. Click the Relationship View link for a visual representation of the client's relationships with other people and companies. Click the name of the segment, for example Business Owners, to see details for that segment.

Parent topic: Reports

Relationship View reportThe Relationship View report provides a visual representation of how a selected client is related to other people, companies, and organizations. The information in this report is not acquired through analytics, but through information that the wealth management company has entered regarding a client's relationships.reportsrelationship viewThe Relationship View report can be accessed from the Analyst Dashboard report or from the Segmentation View report. It shows an advisor how his client is related to other clients, non-clients, entities, households, and accounts. It helps an advisor to efficiently link prospects to clients. For example, an advisor might ask a satisfied client for a referral to a person who appears in the client's relationship chart.ReportsThe Behavior Based Client Insight for Wealth Management solution provides reports with dashboard templates, sample predictive models, and application interfaces for integration.

Relationship View report

The Relationship View report provides a visual representation of how a selected client is related to other people, companies, and organizations. The information in this report is not acquired through analytics, but through information that the wealth management company has entered regarding a client's relationships.

The Relationship View report can be accessed from the Analyst Dashboard report or from the Segmentation View report. It shows an advisor how his client is related to other clients, non-clients, entities, households, and accounts. It helps an advisor to efficiently link prospects to clients. For example, an advisor might ask a satisfied client for a referral to a person who appears in the client's relationship chart.

Parent topic: Reports

Segmentation View reportThe Segmentation View report provides information about a selected segment. You can select any segment to display a list of all clients in that segment, and you can filter the list by detected or predicted life events.reportssegmentation viewEach segment is represented by a number that represents the net worth for the segment, a donut chart that shows the percentage of the total net worth of all the advisor's clients, and a brief description of the segment. To show a list of clients in a segment, click the Explore link for that segment.You can also view a pop-up window that indicates the key characteristics for a selected segment by clicking the View Segments link beside the report title.With the Life Event filter, you can select detected and predicted events to filter the list of clients. For example, to see a list of clients who have recently bought a home, you would select New Home Purchase in the Detected branch of the filter. After you apply the filter, the list includes only clients who have recently purchased a home.From the client list, you can click the client's name for details about the client or click Relationship View to see the client's relationships.ReportsThe Behavior Based Client Insight for Wealth Management solution provides reports with dashboard templates, sample predictive models, and application interfaces for integration.

Segmentation View report

The Segmentation View report provides information about a selected segment. You can select any segment to display a list of all clients in that segment, and you can filter the list by detected or predicted life events.

Each segment is represented by a number that represents the net worth for the segment, a donut chart that shows the percentage of the total net worth of all the advisor's clients, and a brief description of the segment. To show a list of clients in a segment, click the Explore link for that segment.

You can also view a pop-up window that indicates the key characteristics for a selected segment by clicking the View Segments link beside the report title.

With the Life Event filter, you can select detected and predicted events to filter the list of clients. For example, to see a list of clients who have recently bought a home, you would select New Home Purchase in the Detected branch of the filter. After you apply the filter, the list includes only clients who have recently purchased a home.

From the client list, you can click the client's name for details about the client or click Relationship View to see the client's relationships.

Parent topic: Reports

Client profile reportThe Client Profile report provides details about a client and recommended actions for the financial advisor.reportsclient profileThe report contains contact the following information for the client:Contact informationIncomeInternal Assets, which shows the market value of the client's assets that are under management by the wealth management firmExternal Assets, which shows the market value of the client's assets that are not being managed by the wealth management firmNet Worth, which is represented by a number and also by a chart that shows changes in net worth over the past year and the proportion of internal assets relative to external and manually-added assetsTop Events, which lists events detected in the past month and also lists events that are predicted to occur in the future. Past Events, which shows only detected events that have occurred in the past.Charts that show Client Attrition, along with the reasoning (provided in a pop-up window), Top Life Event (detected or predicted) and the top two product propensities.Conversation Starters, which provide links to recent articles that relate to the client's interests. It uses the Alchemy API Relationship Coach, which provides an overview of the client's personality and insights that will help the financial advisor understand how to interact with the client. The Relationship Coach functionality uses Watson Personality Insights to ingest unstructured text from clients and develop a psychographic profile on the client. It also provides insights tied to any upper quartile (> 75%) or lower quartile value (<25%). Portfolio Discussions, which provides links to recent news related to investments in the client's portfolio. It uses the Tailored News and Alerts model to crawl a data source, such as news data, and provide summarized text outputs and rate the sentiment of each article. The Tailored News and Alerts model is implemented using the Alchemy API, Watson Explorer, and Classifier4J. It returns news on a client’s portfolio and stock information.Recent Communications, which shows recent comments and communications by the client through social media and email interactionsClient Attrition predicts the likelihood of the client removing their business from the company. It uses such data points as, but not limited to, the client’s wealth investment data, tenure with the company, monthly number of logins, number of calls, and trades. Included in the analytics that predict attrition is the Email Tone Analyzer. It analyzes the general tone of the client towards the firm, based on past internal interaction data, such as emails or Twitter. It categorizes word sentiment based on a custom library and uses it for extracting scores. This library can be extended to any line of business and incrementally built upon.The Client Attrition model also provides the rationale for the prediction and provides a recommendation. You can hover your mouse pointer over the link below the Client Attrition donut chart to display the reasoning and recommendation.ReportsThe Behavior Based Client Insight for Wealth Management solution provides reports with dashboard templates, sample predictive models, and application interfaces for integration.

Client profile report

The Client Profile report provides details about a client and recommended actions for the financial advisor.

The report contains contact the following information for the client:

Contact information

Income

Internal Assets, which shows the market value of the client's assets that are under management by the wealth management firm

External Assets, which shows the market value of the client's assets that are not being managed by the wealth management firm

Net Worth, which is represented by a number and also by a chart that shows changes in net worth over the past year and the proportion of internal assets relative to external and manually-added assets

Top Events, which lists events detected in the past month and also lists events that are predicted to occur in the future.

Past Events, which shows only detected events that have occurred in the past.

Charts that show Client Attrition, along with the reasoning (provided in a pop-up window), Top Life Event (detected or predicted) and the top two product propensities.

Conversation Starters, which provide links to recent articles that relate to the client's interests. It uses the Alchemy API

Relationship Coach, which provides an overview of the client's personality and insights that will help the financial advisor understand how to interact with the client. The Relationship Coach functionality uses Watson Personality Insights to ingest unstructured text from clients and develop a psychographic profile on the client. It also provides insights tied to any upper quartile (> 75%) or lower quartile value (<25%).

Portfolio Discussions, which provides links to recent news related to investments in the client's portfolio. It uses the Tailored News and Alerts model to crawl a data source, such as news data, and provide summarized text outputs and rate the sentiment of each article. The Tailored News and Alerts model is implemented using the Alchemy API, Watson Explorer, and Classifier4J. It returns news on a client’s portfolio and stock information.

Recent Communications, which shows recent comments and communications by the client through social media and email interactions

Client Attrition predicts the likelihood of the client removing their business from the company. It uses such data points as, but not limited to, the client’s wealth investment data, tenure with the company, monthly number of logins, number of calls, and trades. Included in the analytics that predict attrition is the Email Tone Analyzer. It analyzes the general tone of the client towards the firm, based on past internal interaction data, such as emails or Twitter. It categorizes word sentiment based on a custom library and uses it for extracting scores. This library can be extended to any line of business and incrementally built upon.

The Client Attrition model also provides the rationale for the prediction and provides a recommendation. You can hover your mouse pointer over the link below the Client Attrition donut chart to display the reasoning and recommendation.

Parent topic: Reports

Creating and managing customer segmentsIn the Behavior Based Client Insight for Wealth Management solution, users with the appropriate permissions can add, edit, or delete behavioral customer segments by using the Segmentation Tool.configurationsegmentation toolFor more information, see Customizing segmentsThe Behavioral Segmentation REST API allows you to create and delete custom segments and their associated segment definitions. The Segmentation Tool provides an interface for quickly editing or creating new segments.The following screen capture shows the Segmentation Tool page when it is opened. When the Hints control is set to ON, a description is displayed when you hover your mouse pointer over each field on the page.The following table shows the categories that are available:Wealth data dictionaryCategoriesSub-categoriesASSETSBonds, Commodities, Credits, Derivatives, Estate Funds, Forex, Money Market, Stocks, OthersTRADINGBonds, Commodities, Credits, Derivatives, Estate Funds, Forex, Money Market, Stocks, OthersFUNDINGRegular, Rare, LumpyINTERACTIONRare, Frequent, Less FrequentThe categories are defined based on the customer transactions data. ASSETSAssets owned by the user in any of the listed sub-categories.TRADINGTrading activity performed by the user in any of the listed sub-categories.FUNDINGFunding pattern for the user.INTERACTIONInteraction pattern for the user. Implies interaction with the wealth manager.With the Segmentation Tool you can create or change the rules that determine which customers are assigned to each segment. The tool uses mean and standard deviation to target certain percentages of customers.For example, if you want to create a segment for the top 25 percent of customers who have assets consisting mostly of stocks , you select Assets as the category and Stocks as the value. You choose greater in the Operator field, choose plus in the +/- field, and type 0.67 in the Multiplier/Count field. If you want to select the top 10 percent of customers, you would use 1.28 as your multiplier. Mean and standard deviation are automatically calculated based on the data in your database. Editing a segmentIn the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to make changes to an existing customer segment.Deleting a segmentIn the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to delete an existing customer segment.Adding a new segmentIn the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to add a new customer segment.

Creating and managing customer segments

In the Behavior Based Client Insight for Wealth Management solution, users with the appropriate permissions can add, edit, or delete behavioral customer segments by using the Segmentation Tool.

For more information, see Customizing segments

The following screen capture shows the Segmentation Tool page when it is opened. When the Hints control is set to ON, a description is displayed when you hover your mouse pointer over each field on the page.

The following table shows the categories that are available:

Table 1. Wealth data dictionary

Categories | Sub-categories
ASSETS | Bonds, Commodities, Credits, Derivatives, Estate Funds, Forex, Money Market, Stocks, Others
TRADING | Bonds, Commodities, Credits, Derivatives, Estate Funds, Forex, Money Market, Stocks, Others
FUNDING | Regular, Rare, Lumpy
INTERACTION | Rare, Frequent, Less Frequent

The categories are defined based on the customer transactions data.

ASSETS

Assets owned by the user in any of the listed sub-categories.

TRADING

Trading activity performed by the user in any of the listed sub-categories.

FUNDING

Funding pattern for the user.

INTERACTION

Interaction pattern for the user. Implies interaction with the wealth manager.

With the Segmentation Tool you can create or change the rules that determine which customers are assigned to each segment. The tool uses mean and standard deviation to target certain percentages of customers.

For example, if you want to create a segment for the top 25 percent of customers who have assets consisting mostly of stocks , you select Assets as the category and Stocks as the value. You choose greater in the Operator field, choose plus in the +/- field, and type 0.67 in the Multiplier/Count field. If you want to select the top 10 percent of customers, you would use 1.28 as your multiplier. Mean and standard deviation are automatically calculated based on the data in your database.

Editing a segment
In the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to make changes to an existing customer segment.

Deleting a segment
In the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to delete an existing customer segment.

Adding a new segment
In the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to add a new customer segment.

Editing a segmentIn the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to make changes to an existing customer segment.Open the Segmentation Tool page.In the Segment Name box, select the segment that you want to edit.Click Edit.To change an existing rule, in the Definition section, you can select a different operator, +/-, and multiplier/count. You can delete an existing rule by clicking X for the rule. To clear all rules, click Clear. If you select range as your operator, then +/- is automatically selected. Some categories may not require you to choose an operator, +/-, or multiplier/count.To add a new rule to the segment, select a category, and click Add Rule. A new line is added to the Definition section of the page.Click Update to save your changes.Creating and managing customer segmentsIn the Behavior Based Client Insight for Wealth Management solution, users with the appropriate permissions can add, edit, or delete behavioral customer segments by using the Segmentation Tool.

Editing a segment

In the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to make changes to an existing customer segment.

Procedure

Open the Segmentation Tool page.

In the Segment Name box, select the segment that you want to edit.

Click Edit.

To change an existing rule, in the Definition section, you can select a different operator, +/-, and multiplier/count. You can delete an existing rule by clicking X for the rule. To clear all rules, click Clear.

Note: If you select range as your operator, then +/- is automatically selected. Some categories may not require you to choose an operator, +/-, or multiplier/count.

To add a new rule to the segment, select a category, and click Add Rule. A new line is added to the Definition section of the page.

Click Update to save your changes.

Parent topic: Creating and managing customer segments

Deleting a segmentIn the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to delete an existing customer segment.Open the Segmentation Tool page.In the Segment Name box, select the segment that you want to delete.Click Delete.Creating and managing customer segmentsIn the Behavior Based Client Insight for Wealth Management solution, users with the appropriate permissions can add, edit, or delete behavioral customer segments by using the Segmentation Tool.

Deleting a segment

In the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to delete an existing customer segment.

Procedure

Open the Segmentation Tool page.

In the Segment Name box, select the segment that you want to delete.

Click Delete.

Parent topic: Creating and managing customer segments

Adding a new segmentIn the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to add a new customer segment.Open the Segmentation Tool page.Click Add New.In the Segment Name box, type a name for the new segment.In the Category box, select the category of rule that you want to add to the new segment, and click Add Rule. A line is added to the Definition section of the page. If you select range as your operator, then +/- is automatically selected. Some categories may not require you to choose an operator, +/-, or multiplier/count.To add more rules, repeat step 4.After you define all the rules that you want to add to the new segment, click Submit.Creating and managing customer segmentsIn the Behavior Based Client Insight for Wealth Management solution, users with the appropriate permissions can add, edit, or delete behavioral customer segments by using the Segmentation Tool.

Adding a new segment

In the Behavior Based Client Insight for Wealth Management solution, you can use the Segmentation Tool to add a new customer segment.

Procedure

Open the Segmentation Tool page.

Click Add New.

In the Segment Name box, type a name for the new segment.

In the Category box, select the category of rule that you want to add to the new segment, and click Add Rule. A line is added to the Definition section of the page.

Note: If you select range as your operator, then +/- is automatically selected. Some categories may not require you to choose an operator, +/-, or multiplier/count.

To add more rules, repeat step 4.

After you define all the rules that you want to add to the new segment, click Submit.

Parent topic: Creating and managing customer segments

Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.installationconfigurationThe solution is for use with IBM Predictive Customer Intelligence.Overview of the installation and configuration processThere are several groups of tasks that you must complete to install and configure the Behavior Based Client Insight for Wealth Management solution.Planning the installation and configuration of the solutionPrepare a deployment plan to specify which part of the solution is to be deployed and on which computer node.PrerequisitesBefore you install the IBM Behavior Based Client Insight for Wealth Management solution, there are prerequisites that must be met.Contents of the download packageThe Behavior Based Client Insight for Wealth Management package, which you download from Passport Advantage, contains several parts.Downloading the solutionYou must download the Behavior Based Client Insight for Wealth Management solution from IBM Passport Advantage.Modifying the sudoers file for the Linux user who runs the installationTo run the Behavior Based Client Insight for Wealth Management 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.The Industry Solution InstallerThe Industry Solution Installer provides automation that helps you to install the solution.Creating the databaseBefore you can use the IBM Behavior Based Client Insight for Wealth Management solution, you must create a database.Creating and running stored proceduresIf, when you created the database for the Behavior Based Client Insight for Wealth Management solution, you chose not to load the sample data, then you need to run additional commands to create and run stored procedures. If you loaded the sample data, then you do not need to complete this task.Importing IBM SPSS project streams, models, and rulesIBM SPSS project streams, models, rules, and other artifacts are contained in a repository export file (.pes) for the IBM Behavior Based Client Insight for Wealth Management solution. If you want to modify or view these artifacts, you must copy the export file to the computer where IBM SPSS Collaboration and Deployment Services Deployment Manager is installed, and open the file.Configuring the data view for IBM SPSS modelsTo configure the data view, IBM SPSS Modeler must be connected to the IBM Behavior Based Client Insight for Wealth Management database through an ODBC data source connection.Configuring ODBC for IBM SPSS Modeler Server on LinuxTo use an ODBC data source with IBM SPSS Modeler Server on a Linux operating system, you must configure the environment.Deploying the IBM Cognos contentFor IBM Cognos Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.Installing the EAR fileThe EAR file contains the REST APIs that you use to embed the IBM Behavior Based Client Insight for Wealth Management solution in your existing system.Adding the default PCI Cognos port number to the web portalAfter you deploy the web portal on your server, users will be able to access Cognos reports that are installed on the same computer.Downloading the solution content to a client computerAfter you have the solution installer running, you can download the solution content files to any client computer.Product license filesAfter you install the Behavior Based Client Insight for Wealth Management solution, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed a component.

Installation and configuration

The installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

The solution is for use with IBM Predictive Customer Intelligence.

Overview of the installation and configuration process
There are several groups of tasks that you must complete to install and configure the Behavior Based Client Insight for Wealth Management solution.

Planning the installation and configuration of the solution
Prepare a deployment plan to specify which part of the solution is to be deployed and on which computer node.

Prerequisites
Before you install the IBM Behavior Based Client Insight for Wealth Management solution, there are prerequisites that must be met.

Contents of the download package
The Behavior Based Client Insight for Wealth Management package, which you download from Passport Advantage, contains several parts.

Downloading the solution
You must download the Behavior Based Client Insight for Wealth Management solution from IBM Passport Advantage.

Modifying the sudoers file for the Linux user who runs the installation
To run the Behavior Based Client Insight for Wealth Management 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.

The Industry Solution Installer
The Industry Solution Installer provides automation that helps you to install the solution.

Creating the database
Before you can use the IBM Behavior Based Client Insight for Wealth Management solution, you must create a database.

Creating and running stored procedures
If, when you created the database for the Behavior Based Client Insight for Wealth Management solution, you chose not to load the sample data, then you need to run additional commands to create and run stored procedures. If you loaded the sample data, then you do not need to complete this task.

Importing IBM SPSS project streams, models, and rules
IBM® SPSS® project streams, models, rules, and other artifacts are contained in a repository export file (.pes) for the IBM Behavior Based Client Insight for Wealth Management solution. If you want to modify or view these artifacts, you must copy the export file to the computer where IBM SPSS Collaboration and Deployment Services Deployment Manager is installed, and open the file.

Configuring the data view for IBM SPSS models
To configure the data view, IBM SPSS Modeler must be connected to the IBM Behavior Based Client Insight for Wealth Management database through an ODBC data source connection.

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

Deploying the IBM Cognos content
For IBM Cognos® Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.

Installing the EAR file
The EAR file contains the REST APIs that you use to embed the IBM Behavior Based Client Insight for Wealth Management solution in your existing system.

Adding the default PCI Cognos port number to the web portal
After you deploy the web portal on your server, users will be able to access Cognos reports that are installed on the same computer.

Downloading the solution content to a client computer
After you have the solution installer running, you can download the solution content files to any client computer.

Product license files
After you install the Behavior Based Client Insight for Wealth Management solution, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed a component.

Overview of the installation and configuration processThere are several groups of tasks that you must complete to install and configure the Behavior Based Client Insight for Wealth Management solution.installationoverviewThe following diagram provides a high-level overview of the installation and configuration process. If you are viewing this diagram from the IBM Knowledge Center, you can click on a task to go to the procedure for that task.Diagram that provides an overview of the installation processrect38,46,276,65PrerequisitesBefore you install the IBM Behavior Based Client Insight for Wealth Management solution, there are prerequisites that must be met.rect38,70,206,81Downloading the solutionYou must download the Behavior Based Client Insight for Wealth Management solution from IBM Passport Advantage.rect88,109,318,125Configuring 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.rect89,130,315,145Installing 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. rect37,186,192,222Deploying the installation files on the nodesYou use the Solution Installer to deploy the installation files to the appropriate nodes in your solution. rect163,294,269,318rect164,335,302,359Deploying the IBM Cognos contentFor IBM Cognos Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.rect163,390,308,401Importing IBM SPSS project streams, models, and rulesIBM SPSS project streams, models, rules, and other artifacts are contained in a repository export file (.pes) for the IBM Behavior Based Client Insight for Wealth Management solution. If you want to modify or view these artifacts, you must copy the export file to the computer where IBM SPSS Collaboration and Deployment Services Deployment Manager is installed, and open the file.rect165,402,309,410Configuring ODBC for IBM SPSS Modeler Server on LinuxTo use an ODBC data source with IBM SPSS Modeler Server on a Linux operating system, you must configure the environment.rect165,411,312,422Installing the EAR fileThe EAR file contains the REST APIs that you use to embed the IBM Behavior Based Client Insight for Wealth Management solution in your existing system.To install the solution, you must complete the following tasks:On the computer from which you want to install the solution, download the tar.gz file from IBM Passport Advantage.Plan where you want the various parts of the solution to reside.Open the ports that are required for the installation. You can do this by running the firewall.sh script, manually opening the ports on the installation node, or disabling the firewall. You also must open ports on the other node computers that are used for the solution.On the installation computer, run the setup.sh file to install the solution installer, and then run the solution installer to deploy files to the locations that you specify.On the Data Node computer, create the DB2 database.On the Analytics Node computer, import the SPSS project streams, models, and rules.On the Analytics node computer, configure the data view for the SPSS models.On the Business Intelligence node computer, install the Cognos content.On either the Business Intelligence Node or Analytics Node computer, install the EAR file.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Overview of the installation and configuration process

There are several groups of tasks that you must complete to install and configure the Behavior Based Client Insight for Wealth Management solution.

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

To install the solution, you must complete the following tasks:

On the computer from which you want to install the solution, download the tar.gz file from IBM Passport Advantage.

Plan where you want the various parts of the solution to reside.

Open the ports that are required for the installation. You can do this by running the firewall.sh script, manually opening the ports on the installation node, or disabling the firewall. You also must open ports on the other node computers that are used for the solution.

On the installation computer, run the setup.sh file to install the solution installer, and then run the solution installer to deploy files to the locations that you specify.

On the Data Node computer, create the DB2 database.

On the Analytics Node computer, import the SPSS project streams, models, and rules.

On the Analytics node computer, configure the data view for the SPSS models.

On the Business Intelligence node computer, install the Cognos content.

On either the Business Intelligence Node or Analytics Node computer, install the EAR file.

Parent topic: Installation and configuration

Planning the installation and configuration of the solutionPrepare a deployment plan to specify which part of the solution is to be deployed and on which computer node.installationplanningconfigurationplanningEnsure that the system ports that will be used by this solution are not used by any other application.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Planning the installation and configuration of the solution

Prepare a deployment plan to specify which part of the solution is to be deployed and on which computer node.

Note: Ensure that the system ports that will be used by this solution are not used by any other application.

Parent topic: Installation and configuration

PrerequisitesBefore you install the IBM Behavior Based Client Insight for Wealth Management solution, there are prerequisites that must be met.installationprerequisitesprerequisites to installationThe following conditions must be met before the solution is installed:IBM Predictive Customer Intelligence version 1.1.0 is installed and configured and you have applied all known fix packs.If you are installing to a Linux environment and plan to use the Solution Installer, 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 is a combination of nodes that you must install to, so you must determine where you want the various components of the solution to reside.You have administration rights and the ability to copy files between computers.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Prerequisites

Before you install the IBM Behavior Based Client Insight for Wealth Management solution, there are prerequisites that must be met.

The following conditions must be met before the solution is installed:

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

If you are installing to a Linux environment and plan to use the Solution Installer, 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 is a combination of nodes that you must install to, so you must determine where you want the various components of the solution to reside.

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

Parent topic: Installation and configuration

Contents of the download packageThe Behavior Based Client Insight for Wealth Management package, which you download from Passport Advantage, contains several parts.download packageThe following parts are included in the package:Solution installer (if you chose the Linux package)DB2 databasesSPSS project streams, models, and rulesCognos BI reports and Dynamic cube modelsEAR file that contains the REST APIsInstallation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Contents of the download package

The Behavior Based Client Insight for Wealth Management package, which you download from Passport Advantage, contains several parts.

The following parts are included in the package:

Solution installer (if you chose the Linux package)

DB2 databases

SPSS project streams, models, and rules

Cognos BI reports and Dynamic cube models

EAR file that contains the REST APIs

Parent topic: Installation and configuration

Downloading the solutionYou must download the Behavior Based Client Insight for Wealth Management solution from IBM Passport Advantage.We don't usually explain how to use PA. Is this topic really required? download packageYou must have a Passport Advantage account and be entitled to the package. Passport Advantage contains package repositories. Instead of downloading the package from Passport Advantage and creating a repository locally, you access the repository on Passport Advantage.Set the Passport Advantage preference to Connect to Passport Advantage.Download the tar.gz fileMove the tar file to the computer from which you want to run the installation.Decompress the file.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Downloading the solution

You must download the Behavior Based Client Insight for Wealth Management solution from IBM Passport Advantage.

Before you begin

You must have a Passport Advantage account and be entitled to the package.

About this task

Passport Advantage contains package repositories. Instead of downloading the package from Passport Advantage and creating a repository locally, you access the repository on Passport Advantage.

Procedure

Set the Passport Advantage preference to Connect to Passport Advantage.

Download the tar.gz file

Move the tar file to the computer from which you want to run the installation.

Decompress the file.

Parent topic: Installation and configuration

Modifying the sudoers file for the Linux user who runs the installationTo run the Behavior Based Client Insight for Wealth Management 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 Behavior Based Client Insight for Wealth Management node.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

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

To run the Behavior Based Client Insight for Wealth Management 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 Behavior Based Client Insight for Wealth Management node.

Parent topic: Installation and configuration

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.firewall settingsInstallation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.Disabling firewall settings during installation (optional)If you choose to temporarily disable your computer's firewall during the installation of the IBM Behavior Based Client Insight for Wealth Management solution, ensure that you enable the firewall on each node after the installation is complete.Configuring your firewall settings on the installation node computer by using the firewall scriptYou can run the firewall.sh script to open the ports on a Linux installation node.Manually configuring firewall settings on the installation nodeIf you prefer not to disable your firewall settings or use the firewall.sh script, you can manually configure your firewall settings on the installation node.Configuring firewall settings on other computers that will contain content from the solutionOn all node computers to which content from the solution will be copied, the ports 443, 9683, and 8080 must be opened for the installation process.

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.

Disabling firewall settings during installation (optional)
If you choose to temporarily disable your computer's firewall during the installation of the IBM® Behavior Based Client Insight for Wealth Management solution, ensure that you enable the firewall on each node after the installation is complete.

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

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

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

Parent topic: Installation and configuration

Disabling firewall settings during installation (optional)If you choose to temporarily disable your computer's firewall during the installation of the IBM Behavior Based Client Insight for Wealth Management 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 during installation (optional)

If you choose to temporarily disable your computer's firewall during the installation of the IBM® Behavior Based Client Insight for Wealth Management 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

Configuring your firewall settings on the installation node computer by using the firewall scriptYou can run the firewall.sh script to open the ports on a Linux installation node.firewall settingsconfigure with scriptfirewall.shThe firewall.sh script opens the following ports on the solution installer node: 8080 incoming443 incoming9683 incoming22 outgoingAs the root user or as a user with sudo permissions, log on to the computer that contains the solution installer node.Back up your existing firewall settings by typing the following command: /etc/init.d/iptables save.Run the firewall.sh script.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.

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

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

About this task

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

8080 incoming

443 incoming

9683 incoming

22 outgoing

Procedure

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

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

Run the firewall.sh script.

Parent topic: Configuring computer firewall settings required for the installation on Linux

Manually configuring firewall settings on the installation nodeIf you prefer not to disable your firewall settings or use the firewall.sh script, you can manually configure your firewall settings on the installation node.firewall settingsmanually configuringAs the root user or as a user with sudo permissions, log on to the computer that contains the solution installer node .Back up your existing firewall settings by typing the following command: ./etc/init.d/iptables saveOn the computer that contains the solution installer node, add rules for the ports that are required by the installer by typing the following commands:iptables -I INPUT -p tcp --dport 8080 -j ACCEPT iptables -I OUTPUT -p tcp --sport 8080 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I INPUT -p tcp --dport 443 -j ACCEPT iptables -I OUTPUT -p tcp --sport 443 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I INPUT -p tcp --dport 9683 -j ACCEPT iptables -I OUTPUT -p tcp --sport 9683 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I OUTPUT -p tcp --dport 22 -j ACCEPT iptables -I INPUT -p tcp --sport 22 -m state --state RELATED,ESTABLISHED -j ACCEPTConfiguring 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

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

Procedure

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

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

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

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

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

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

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

Parent topic: Configuring computer firewall settings required for the installation on Linux

Configuring firewall settings on other computers that will contain content from the solutionOn all node computers to which content from the solution will be copied, the ports 443, 9683, and 8080 must be opened for the installation process.firewall settingson all computersOn each of the computers to which content for the solution will be copied, add rules for the ports that are required by the installer by typing the following commands:iptables -I OUTPUT -p tcp --dport 443 -j ACCEPT iptables -I INPUT -p tcp --sport 443 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I OUTPUT -p tcp --dport 9683 -j ACCEPT iptables -I INPUT -p tcp --sport 9683 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -I OUTPUT -p tcp --dport 8080 -j ACCEPT iptables -I INPUT -p tcp --sport 8080 -m state --state RELATED,ESTABLISHED -j ACCEPTType the following command to save your firewall settings: /etc/init.d/iptables saveType the following command to restart your firewall: /etc/init.d/iptables restartVerify that your changes are applied by using the following command:iptables -L The added port appears in the list.Repeat these steps on each computer on which you will install an IBM Behavior Based Client Insight for Wealth Management node.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.

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

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

Procedure

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

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

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

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

Type the following command to save your firewall settings:

/etc/init.d/iptables save

Type the following command to restart your firewall:

/etc/init.d/iptables restart

Verify that your changes are applied by using the following command:

iptables -L

The added port appears in the list.

Repeat these steps on each computer on which you will install an IBM® Behavior Based Client Insight for Wealth Management node.

Parent topic: Configuring computer firewall settings required for the installation on Linux

The Industry Solution InstallerThe Industry Solution Installer provides automation that helps you to install the solution.installationsolution installerconfigurationsolution installerThe Industry Solution Installer runs on the latest versions of Chrome and Firefox. It is not tested on Safari and does not run on Internet Explorer.The Industry Solution installer provides the following functionality:Deployment of the required files to defined nodes. The option to create a new configuration or start from a configuration that you previously saved.Automated validation.Electronic license acceptance.Automated clean-up of installed files if the license is declined.The setup.sh script installs nodejs, Chef client, and Chef server. It extracts and uploads the cookbooks and sets up everything so that Chef can be used to install the software. Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.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. Deploying the installation files on the nodesYou use the Solution Installer to deploy the installation files to the appropriate nodes in your solution.

The Industry Solution Installer

The Industry Solution Installer provides automation that helps you to install the solution.

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

The Industry Solution installer provides the following functionality:

Deployment of the required files to defined nodes.

The option to create a new configuration or start from a configuration that you previously saved.

Automated validation.

Electronic license acceptance.

Automated clean-up of installed files if the license is declined.

The setup.sh script installs nodejs, Chef client, and Chef server. It extracts and uploads the cookbooks and sets up everything so that Chef can be used to install the software.

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.

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

Parent topic: Installation and configuration

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 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 PCI Solution Installer) has been run on the computer previously, run the following command:./cleanupClient.shGo to the solution installer directory in the following location: opt/IBM/IS_Wealth_Customerinsight_1.0.1/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. The Industry Solution InstallerThe Industry Solution Installer provides automation that helps you to install the solution.

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 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 PCI Solution Installer) has been run on the computer previously, run the following command:

./cleanupClient.sh

Go to the solution installer directory in the following location: opt/IBM/IS_Wealth_Customerinsight_1.0.1/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: The Industry Solution Installer

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

Deploying the installation files on the nodes

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

Before you begin

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

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

Host name or IP address

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

Each node must also meet the following requirements:

Has a valid DNS name that is resolvable.

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

About this task

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

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

Procedure

In a web browser, go to the Solution Installer.

Read the license agreement and click Accept.

Click New Configuration and then click OK.

From the Mandatory Content List pane, select Node.

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

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

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

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

If you click Validate before all the mandatory content is added, a message indicates that the node is not valid. For example, if you validate the BI Node before adding Cognos BI Content, then a message indicates that the node is not yet valid.

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

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

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

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

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

What to do next

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

Parent topic: The Industry Solution Installer

Creating the databaseBefore you can use the IBM Behavior Based Client Insight for Wealth Management solution, you must create a database.databasecreatingThere are two scripts to be run; one to create the database, and another to populate the database. The installer will have copied the compressed file to your data node computer.Log on to the data node computer as root user.On the data node computer, if the compressed file is not already decompressed, then decompress it.Open a terminal window, and go to the directory where the content files were decompressed.Type the following command to change the permissions for the files: chmod 755 *shChange to the database instance owner.For example, su db2inst1In the decompressed folder, run the ./Install_DB.sh script.Do one of the following actions:If you want to load the sample data that is provided with the solution, then run the ./Load_Data.sh script.If you do not want to load the sample data, then run the following SQL commands: INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME, IMPORTANCE_RATING,LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS, POPULATION_DATE,POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY, PROFITABILITY,RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING, SATISFACTION_RATING,SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME, UNIQUE_ID_IN_SOURCE_SYSTEM) values(null,null,null,null,null,null,null,null, null,null,null,null,null,null,null,null,'Conserver',null,null,null); INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING, LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE, POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY, RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING, SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values(null,null,null,null,null,null,null,null,null,null,null,null,null,null, null,null,'Indifferent',null,null,null); INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING, LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE, POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY, RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING, SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values (null,null,null,null,null,null,null,null,null,null,null,null,null,null,null, null,'Straight Arrow',null,null,null); INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING, LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE, POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY, RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING, SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values (null,null,null,null,null,null,null,null,null,null,null,null,null,null,null, null,'Individualistic',null,null,null); INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING, LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE, POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY, RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING, SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values (null,null,null,null,null,null,null,null,null,null,null,null,null,null, null,null,'Hedgers',null,null,null); INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING, LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE, POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY, RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING, SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values (null,null,null,null,null,null,null,null,null,null,null,null,null,null, null,null,'Others',null,null,null);Verify that the tables are created and the data is successfully loaded into the input tables by checking the out.log file, which on a Linux system is in the db2inst1 home directory. In the log file, search for the text: rows were rejected. The value should be zero. If it is not, there are data load issues.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Creating the database

Before you can use the IBM Behavior Based Client Insight for Wealth Management solution, you must create a database.

About this task

There are two scripts to be run; one to create the database, and another to populate the database. The installer will have copied the compressed file to your data node computer.

Procedure

Log on to the data node computer as root user.

On the data node computer, if the compressed file is not already decompressed, then decompress it.

Open a terminal window, and go to the directory where the content files were decompressed.

Type the following command to change the permissions for the files:

chmod 755 *sh

Change to the database instance owner.

For example, su db2inst1

In the decompressed folder, run the ./Install_DB.sh script.

Do one of the following actions:

If you want to load the sample data that is provided with the solution, then run the ./Load_Data.sh script.

If you do not want to load the sample data, then run the following SQL commands:

INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,
IMPORTANCE_RATING,LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,
POPULATION_DATE,POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,
PROFITABILITY,RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,
SATISFACTION_RATING,SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,
UNIQUE_ID_IN_SOURCE_SYSTEM) values(null,null,null,null,null,null,null,null,
null,null,null,null,null,null,null,null,'Conserver',null,null,null);
INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING,
LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE,
POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY,
RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING,
SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM)
values(null,null,null,null,null,null,null,null,null,null,null,null,null,null,
null,null,'Indifferent',null,null,null);
INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING,
LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE,
POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY,
RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING,
SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values
(null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,
null,'Straight Arrow',null,null,null);
INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING,
LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE,
POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY,
RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING,
SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values
(null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,
null,'Individualistic',null,null,null);
INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING,
LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE,
POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY,
RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING,
SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values
(null,null,null,null,null,null,null,null,null,null,null,null,null,null,
null,null,'Hedgers',null,null,null);
INSERT INTO PCIWLTH.CUSTOMER_SEGMENT_MINI_DIMENSION (ANNUAL_INCOME,IMPORTANCE_RATING,
LOYALTY_RATING,MARKET,NET_WORTH,PERFORMANCE_RATING,PERFORMANCE_STATUS,POPULATION_DATE,
POPULATION_DESCRIPTION,POPULATION_TIME,PRIMARY_BRANCH_PROXIMITY,PROFITABILITY,
RELATIONSHIP_AGE,RELATIONSHIP_VALUATION,RETENTION_RATING,SATISFACTION_RATING,
SEGMENT_NAME,SOURCE_SYSTEM_CODE,SOURCE_SYSTEM_NAME,UNIQUE_ID_IN_SOURCE_SYSTEM) values
(null,null,null,null,null,null,null,null,null,null,null,null,null,null,
null,null,'Others',null,null,null);

What to do next

Verify that the tables are created and the data is successfully loaded into the input tables by checking the out.log file, which on a Linux system is in the db2inst1 home directory. In the log file, search for the text: rows were rejected. The value should be zero. If it is not, there are data load issues.

Parent topic: Installation and configuration

Creating and running stored proceduresIf, when you created the database for the Behavior Based Client Insight for Wealth Management solution, you chose not to load the sample data, then you need to run additional commands to create and run stored procedures. If you loaded the sample data, then you do not need to complete this task.stored procedures Save the SEGMENT_SUMMARY_PATTERN procedure into the SEGMENT_SUMMARY_PATTERN.sql file.Go to the following location to download the code for creating the stored procedures: Industry Solutions techdoc (http://www.ibm.com/support/docview.wss?uid=swg27046047).Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Creating and running stored procedures

If, when you created the database for the Behavior Based Client Insight for Wealth Management solution, you chose not to load the sample data, then you need to run additional commands to create and run stored procedures. If you loaded the sample data, then you do not need to complete this task.

Before you begin

Save the SEGMENT_SUMMARY_PATTERN procedure into the SEGMENT_SUMMARY_PATTERN.sql file.

Procedure

Go to the following location to download the code for creating the stored procedures: Industry Solutions techdoc (http://www.ibm.com/support/docview.wss?uid=swg27046047).

Parent topic: Installation and configuration

Importing IBM SPSS project streams, models, and rulesIBM SPSS project streams, models, rules, and other artifacts are contained in a repository export file (.pes) for the IBM Behavior Based Client Insight for Wealth Management solution. If you want to modify or view these artifacts, you must copy the export file to the computer where IBM SPSS Collaboration and Deployment Services Deployment Manager is installed, and open the file.SPSSimportingCopy the .pes file from the computer where you ran the Solution Installer to the computer where IBM SPSS Collaboration and Deployment Services Deployment Manager is installed.The .pes file is available from the SolutionInstaller/NodeRoot/Downloads/IS_Wealth_ClientInsight_1.0.3/Analytics folder on the computer where you ran the Solution Installer.In IBM SPSS Collaboration and Deployment Service Deployment Manager, right-click Content Repository, and click Import.Browse to the .pes fileSelect the following options:Select Resolve conflicts globally , and the following options: Select Add new version of target item or rename source item, and select Source for Use labels from.For Lock Resolution, select Continue import even if some objects cannot be imported due to locking conflicts.For Resolve Invalid Version Conflicts, select Import.For Resource Definitions, select Recommended - Import if there are no Duplicate ID conflicts or Duplicate Name conflicts.Click OK.Under Resource definitions / Credentials, create a new credential named IBMPCIWEATH.Under Resource definitions / Data Sources, create a new data source named IBMPCIWEATH.After the .pes file is imported to the CnDS, open the job and click the step that is listed in the job. The following screen captures use a data source name for another industry solution. When referring to the screen captures, substitute WEALTH for the data source name PCIBNK. Make sure that Modeler Server and Modeler Login fields are set to the correct definitions.Click the ODBC Data Sources tab, and make sure that ODBC DSN and credentials are set to the newly created data source and credential.Content folders and resource definitions are added to the repository alongside any existing content.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Importing IBM SPSS project streams, models, and rules

IBM® SPSS® project streams, models, rules, and other artifacts are contained in a repository export file (.pes) for the IBM Behavior Based Client Insight for Wealth Management solution. If you want to modify or view these artifacts, you must copy the export file to the computer where IBM SPSS Collaboration and Deployment Services Deployment Manager is installed, and open the file.

Procedure

Copy the .pes file from the computer where you ran the Solution Installer to the computer where IBM SPSS Collaboration and Deployment Services Deployment Manager is installed.

The .pes file is available from the SolutionInstaller/NodeRoot/Downloads/IS_Wealth_ClientInsight_1.0.3/Analytics folder on the computer where you ran the Solution Installer.

In IBM SPSS Collaboration and Deployment Service Deployment Manager, right-click Content Repository, and click Import.

Browse to the .pes file

Select the following options:

Select Resolve conflicts globally , and the following options:

Select Add new version of target item or rename source item, and select Source for Use labels from.

For Lock Resolution, select Continue import even if some objects cannot be imported due to locking conflicts.

For Resolve Invalid Version Conflicts, select Import.

For Resource Definitions, select Recommended - Import if there are no Duplicate ID conflicts or Duplicate Name conflicts.

Click OK.

Under Resource definitions / Credentials, create a new credential named IBMPCIWEATH.

Under Resource definitions / Data Sources, create a new data source named IBMPCIWEATH.

After the .pes file is imported to the CnDS, open the job and click the step that is listed in the job.

Note: The following screen captures use a data source name for another industry solution. When referring to the screen captures, substitute WEALTH for the data source name PCIBNK.

Make sure that Modeler Server and Modeler Login fields are set to the correct definitions.

Click the ODBC Data Sources tab, and make sure that ODBC DSN and credentials are set to the newly created data source and credential.

Results

Content folders and resource definitions are added to the repository alongside any existing content.

Parent topic: Installation and configuration

Configuring the data view for IBM SPSS modelsTo configure the data view, IBM SPSS Modeler must be connected to the IBM Behavior Based Client Insight for Wealth Management database through an ODBC data source connection. If your IBM Predictive Customer Intelligence environment uses the IBM SPSS Modeler client logged in to a Modeler server, complete the steps on the Predictive Analytics node computer (where IBM SPSS Modeler Server is installed). If your IBM Predictive Customer Intelligence environment uses the IBM SPSS Modeler Client in a stand-alone environment, complete the steps on the client computer where IBM SPSS Modeler client is installed. The Behavior Based Client Insight for Wealth Management solution uses the Analytic Data View and JDBC source connections for accessing IBM Analytical Decision Manager. When the Behavior Based Client Insight for Wealth Management files are imported through IBM SPSS Collaboration and Deployment Services Deployment Manager, a new version of the Enterprise View is created that contains the tables for the solution.SPSSconfiguring data viewCatalog the database on the client computer.Click StartIBM DB2DB2COPY1 (Default)DB2 Command Window - Administrator.Enter the following command to catalog the database node:db2 catalog tcpip node NODE_NAME remote data_node_name server PORT_NUMBER NODE_NAME can be any value. PORT_NUMBER is 50000 by default.Enter the following command to catalog the PCI database:db2 catalog database WEALTH at node NODE_NAME authentication server You must use the same node_name that you used in the db2 catalog database command.Create an ODBC DSN to point to the Behavior Based Client Insight for Wealth Management database. The database account that is provided in the ODBC connection must be the same user that was used for creating the tables. In the Deployment Manager client, under Resource Definitions, Credentials, open the db2admin credentials and update the user ID and password to the DB2 administrator account of the data node computer.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Configuring the data view for IBM SPSS models

To configure the data view, IBM® SPSS® Modeler must be connected to the IBM Behavior Based Client Insight for Wealth Management database through an ODBC data source connection.

If your IBM Predictive Customer Intelligence environment uses the IBM SPSS Modeler client logged in to a Modeler server, complete the steps on the Predictive Analytics node computer (where IBM SPSS Modeler Server is installed).

If your IBM Predictive Customer Intelligence environment uses the IBM SPSS Modeler Client in a stand-alone environment, complete the steps on the client computer where IBM SPSS Modeler client is installed.

The Behavior Based Client Insight for Wealth Management solution uses the Analytic Data View and JDBC source connections for accessing IBM Analytical Decision Manager. When the Behavior Based Client Insight for Wealth Management files are imported through IBM SPSS Collaboration and Deployment Services Deployment Manager, a new version of the Enterprise View is created that contains the tables for the solution.

Procedure

Catalog the database on the client computer.

Click Start > IBM DB2 > DB2COPY1 (Default) > DB2 Command Window - Administrator.

Enter the following command to catalog the database node:

db2 catalog tcpip node NODE_NAME remote data_node_name server PORT_NUMBER

NODE_NAME can be any value. PORT_NUMBER is 50000 by default.

Enter the following command to catalog the PCI database:

db2 catalog database WEALTH at node NODE_NAME authentication server

You must use the same node_name that you used in the db2 catalog database command.

Create an ODBC DSN to point to the Behavior Based Client Insight for Wealth Management database. The database account that is provided in the ODBC connection must be the same user that was used for creating the tables.

In the Deployment Manager client, under Resource Definitions, Credentials, open the db2admin credentials and update the user ID and password to the DB2® administrator account of the data node computer.

Parent topic: Installation and configuration

Configuring ODBC for IBM SPSS Modeler Server on Linux To use an ODBC data source with IBM SPSS Modeler Server on a Linux operating system, you must configure the environment.SPSSconfiguring ODBCODBCStop the IBM SPSS Modeler Server.Go to the /root/SDAP711 directory. The driver files are installed as part of the Behavior Based Client Insight for Wealth Management 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 end of the script. For example:ODBCINI=/usr/spss/odbc/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. For example, add the data source as: [ODBC Data Sources]WEALTH=IBM DB2 ODBC Driver In the odbc.ini file, create an ODBC data source connection for the WEALTH database. For example, include the following content: [WEALTH] 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=WEALTH 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=db2inst1 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, /usr/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=/usr/spss/odbc/lib else LD_LIBRARY_PATH=/usr/spss/odbc/lib:$LD_LIBRARY_PATH fi export LD_LIBRARY_PATH if [ "$LD_LIBRARY_PATH_64" = "" ]; then LD_LIBRARY_PATH_64=/usr/spss/odbc/lib else LD_LIBRARY_PATH_64=/usr/spss/odbc/lib:$LD_LIBRARY_PATH_64 fi export LD_LIBRARY_PATH_64 ODBCINI=/usr/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 after the line that defines SCLEMDNAME:. <odbc.sh_path> Where odbc.sh_path is the full path to the odbc.sh file.For example: . /usr/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/16.0/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 each database. [WEALTH] Database=WEALTH Protocol=TCPIP DriverUnicodeType=1 Port=50000 Hostname=ip or hostname UID=username PWD=password Save the odbc.ini file.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 more information and troubleshooting tips for connecting to data sources, see the SPSS Modeler documentation (www.ibm.com/support/knowledgecenter/SS3RA7_16.0.0)Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Configuring ODBC for IBM SPSS Modeler Server on Linux

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 Behavior Based Client Insight for Wealth Management 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 end of the script. For example:

ODBCINI=/usr/spss/odbc/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.

For example, add the data source as:

[ODBC Data Sources]WEALTH=IBM DB2 ODBC Driver

In the odbc.ini file, create an ODBC data source connection for the WEALTH database.

For example, include the following content:

[WEALTH]
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=WEALTH
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=db2inst1
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

Important: 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, /usr/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=/usr/spss/odbc/lib
else
		LD_LIBRARY_PATH=/usr/spss/odbc/lib:$LD_LIBRARY_PATH
fi
export LD_LIBRARY_PATH
if [ "$LD_LIBRARY_PATH_64" = "" ]; then
		LD_LIBRARY_PATH_64=/usr/spss/odbc/lib
else
		LD_LIBRARY_PATH_64=/usr/spss/odbc/lib:$LD_LIBRARY_PATH_64
fi
export LD_LIBRARY_PATH_64
ODBCINI=/usr/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 after the line that defines SCLEMDNAME:

. <odbc.sh_path>

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

For example: . /usr/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/16.0/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 each database.

[WEALTH]
Database=WEALTH
Protocol=TCPIP
DriverUnicodeType=1
Port=50000
Hostname=ip or hostname
UID=username
PWD=password

Save the odbc.ini file.

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 more information and troubleshooting tips for connecting to data sources, see the SPSS Modeler documentation (www.ibm.com/support/knowledgecenter/SS3RA7_16.0.0)

Parent topic: Installation and configuration

Deploying the IBM Cognos contentFor IBM Cognos Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.Cognosdeploying contentIBM Cognos contentInstallation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.Preparing the IBM Cognos contentYou must move the IBM Cube Designer content for the IBM Behavior Based Client Insight for Wealth Management solution to the Cognos Deployment folder.Creating a data source connection to the databaseYou must create a data source connection to the Behavior Based Client Insight for Wealth Management database.Deploying dynamic cubes for the sample dataIf you choose to use the sample data for the Behavior Based Client Insight for Wealth Management solution, you must deploy the dynamic cubes.Deploying the IBM Cognos reportsYou must deploy the Behavior Based Client Insight for Wealth Management reports by using IBM Cognos Administration.

Deploying the IBM Cognos content

For IBM® Cognos® Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.

Preparing the IBM Cognos content
You must move the IBM Cube Designer content for the IBM Behavior Based Client Insight for Wealth Management solution to the Cognos Deployment folder.

Creating a data source connection to the database
You must create a data source connection to the Behavior Based Client Insight for Wealth Management database.

Deploying dynamic cubes for the sample data
If you choose to use the sample data for the Behavior Based Client Insight for Wealth Management solution, you must deploy the dynamic cubes.

Deploying the IBM Cognos reports
You must deploy the Behavior Based Client Insight for Wealth Management reports by using IBM Cognos Administration.

Parent topic: Installation and configuration

Preparing the IBM Cognos contentYou must move the IBM Cube Designer content for the IBM Behavior Based Client Insight for Wealth Management solution to the Cognos Deployment folder.Cognospreparing contentIBM Cognos contentCopy the IBM Cube Designer file from the computer where you deployed the solution to the computer where you installed IBM Cognos Framework Manager, and decompress the file.The file is named \BI\Client_ClientInsight_CD.fmd.Download IBM Cognos Business Intelligence Cube Designer software from Passport Advantage. Cube Designer requires Framework manager to be installed on the same node as well. Go to the location where the installation files were downloaded and extracted and then double-click the issetup.exe file.Select the language to use for the installation. The language that you select determines the language of the user interface. All supported languages are installed. You can change the user interface to any of the installed languages after installation.On the Installation Location panel, select the location where Framework Manager is installed.Accept the defaults on the Component Selection page.Follow the directions in the installation wizard to copy the required files to your computer.If you are installing in a directory that contains other IBM Cognos Business Intelligence components, you are prompted to create backup copies of the files that will be replaced.In the Finish page of the installation wizard, complete the following steps:If you want to see the log files, click View for the appropriate log file.If you want to see late-breaking information about the product, select the check box for IBM Cognos Release Notes.Click Finish.Deploying the IBM Cognos contentFor IBM Cognos Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.

Preparing the IBM Cognos content

You must move the IBM® Cube Designer content for the IBM Behavior Based Client Insight for Wealth Management solution to the Cognos Deployment folder.

Procedure

Copy the IBM Cube Designer file from the computer where you deployed the solution to the computer where you installed IBM Cognos® Framework Manager, and decompress the file.

The file is named \BI\Client_ClientInsight_CD.fmd.

Download IBM Cognos Business Intelligence Cube Designer software from Passport Advantage. Cube Designer requires Framework manager to be installed on the same node as well.

Go to the location where the installation files were downloaded and extracted and then double-click the issetup.exe file.

Select the language to use for the installation. The language that you select determines the language of the user interface. All supported languages are installed. You can change the user interface to any of the installed languages after installation.

On the Installation Location panel, select the location where Framework Manager is installed.

Accept the defaults on the Component Selection page.

Follow the directions in the installation wizard to copy the required files to your computer.

If you are installing in a directory that contains other IBM Cognos Business Intelligence components, you are prompted to create backup copies of the files that will be replaced.

In the Finish page of the installation wizard, complete the following steps:

If you want to see the log files, click View for the appropriate log file.

If you want to see late-breaking information about the product, select the check box for IBM Cognos Release Notes.

Click Finish.

Parent topic: Deploying the IBM Cognos content

Creating a data source connection to the databaseYou must create a data source connection to the Behavior Based Client Insight for Wealth Management database.Cognoscreating a data source connectiondata source connectionOpen a web browser.Go to the IBM Cognos BI portal URL.For example, go to http://bi_node_name/ibmcognos/.On the Welcome page, click Administer IBM Cognos Content.Click the Configuration tab, and click Data Source Connections.Click New Data Source.In the Name box, type WEALTH, and then click Next.In the connection page, select IBM DB2, ensure that Configure JDBC connection is selected, and click Next.In the DB2 database name field, type WEALTH.Leave DB2 connect string blank.Under Signons, select both Password and Create a signon that the Everyone group can use, and then type the user ID and password for the DB2 instance owner user that you used to create the database, and click Next.To test whether the parameters are correct, click Test the connection. After you test the connection, click OK to return to the connection page.In the Server name box, enter the name or IP address of your data node computer.In the Port number box, enter the DB2 port number. The default is 50000.In Database name, type WEALTH.To test whether the parameters are correct, click Test the connection. After you test the connection, click OK to return to the connection page.Click Finish.Deploying the IBM Cognos contentFor IBM Cognos Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.

Creating a data source connection to the database

You must create a data source connection to the Behavior Based Client Insight for Wealth Management database.

Procedure

Open a web browser.

Go to the IBM® Cognos® BI portal URL.

For example, go to http://bi_node_name/ibmcognos/.

On the Welcome page, click Administer IBM Cognos Content.

Click the Configuration tab, and click Data Source Connections.

Click New Data Source.

In the Name box, type WEALTH, and then click Next.

In the connection page, select IBM DB2, ensure that Configure JDBC connection is selected, and click Next.

In the DB2 database name field, type WEALTH.

Leave DB2 connect string blank.

Under Signons, select both Password and Create a signon that the Everyone group can use, and then type the user ID and password for the DB2® instance owner user that you used to create the database, and click Next.

Tip: To test whether the parameters are correct, click Test the connection. After you test the connection, click OK to return to the connection page.

In the Server name box, enter the name or IP address of your data node computer.

In the Port number box, enter the DB2 port number. The default is 50000.

In Database name, type WEALTH.

Tip: To test whether the parameters are correct, click Test the connection. After you test the connection, click OK to return to the connection page.

Click Finish.

Parent topic: Deploying the IBM Cognos content

Deploying dynamic cubes for the sample dataIf you choose to use the sample data for the Behavior Based Client Insight for Wealth Management solution, you must deploy the dynamic cubes.Cognosdeploying dynamic cubesdynamic cubescubesYou must create a data source connection to the database that contains the data by completing the steps in the following link: Creating a data source in the Cognos Administration portal (http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.dwe.migrate.doc/data_source_cs_cognos.html)Add the dispatcher and gateway information of the computer in which the data source is created to the Cognos configuration of the local system from which cubes are published (the computer on which the cube designer is installed).Use the following URI to set the dispatcher and the gateway: Gateway URI: http://localhost:80/ibmcognos/cgi-bin/cognos.cgi Dispatcher URI: http://localhost:9080/p2pd/servlet/dispatch Open IBM Cognos Cube Designer and click Open Existing to load the .fmd file.In Cognos Cube Designer, click the data source to display the Properties window.Change the Content Manager data source to the name of the data source connection that is created in Cognos ServerChange the schema name to the name under which data objects are created.Right-click the data source and refresh the metadata.To publish the cubes, right-click a package and click Publish.If a message indicates that the package contains warnings, you can ignore the message.Click OK.Cubes are published to the Cognos server. A message appears to indicate that the cubes are published successfully. Check the status of the cube in Cognos Administration under Data Sources.Initially all cubes have a status of Unknown.Select all the cubes that you published, right-click next to the cube, select Add data store to server group, and click OK. Now the cubes move to an Unavailable status.From the same menu, click Start.If an error message is encountered when you publish the cube, check the log file in C:\Program Files\IBM\cognos\c10_64\logs\XQE on the computer in which IBM Cognos BI is installed. Open the most recent log file with a file name that starts with xqelog followed by a date and time stamp. The error message in the log looks similar to the following message: Deploying the IBM Cognos contentFor IBM Cognos Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.

Deploying dynamic cubes for the sample data

If you choose to use the sample data for the Behavior Based Client Insight for Wealth Management solution, you must deploy the dynamic cubes.

Before you begin

You must create a data source connection to the database that contains the data by completing the steps in the following link:

Creating a data source in the Cognos Administration portal (http://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.dwe.migrate.doc/data_source_cs_cognos.html)

Procedure

Add the dispatcher and gateway information of the computer in which the data source is created to the Cognos configuration of the local system from which cubes are published (the computer on which the cube designer is installed).

Use the following URI to set the dispatcher and the gateway:

Gateway URI: http://localhost:80/ibmcognos/cgi-bin/cognos.cgi

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

Open IBM Cognos Cube Designer and click Open Existing to load the .fmd file.

In Cognos Cube Designer, click the data source to display the Properties window.

Change the Content Manager data source to the name of the data source connection that is created in Cognos Server

Change the schema name to the name under which data objects are created.

Right-click the data source and refresh the metadata.

To publish the cubes, right-click a package and click Publish. If a message indicates that the package contains warnings, you can ignore the message.

Click OK.

Cubes are published to the Cognos server. A message appears to indicate that the cubes are published successfully.

Check the status of the cube in Cognos Administration under Data Sources. Initially all cubes have a status of Unknown.

Select all the cubes that you published, right-click next to the cube, select Add data store to server group, and click OK. Now the cubes move to an Unavailable status.

From the same menu, click Start. If an error message is encountered when you publish the cube, check the log file in C:\Program Files\IBM\cognos\c10_64\logs\XQE on the computer in which IBM Cognos BI is installed. Open the most recent log file with a file name that starts with xqelog followed by a date and time stamp. The error message in the log looks similar to the following message:

Parent topic: Deploying the IBM Cognos content

Deploying the IBM Cognos reportsYou must deploy the Behavior Based Client Insight for Wealth Management reports by using IBM Cognos Administration.Cognosdeploying reportsIBM Cognos reportsreportsOpen a web browser.Go to the IBM Cognos BI portal URL.On the Welcome page, click Administer IBM Cognos Content.On the Configuration tab, click Content Administration.On the toolbar, click the New Import button.In the Deployment Archive pane, select the deployment archive, and click Next.The deployment archive is named Wealth_CustomerInsight_BIContent.zip.In the Specify a name and description pane, accept the default or enter a new name, and click Next.In the Select the public folders and directory content pane, select all of the packages in the table, leave the Options as default, and click Next.Ensure that the Disable after import option is cleared.In the Specify the general options pane, accept the defaults, and click Next.On the Review the summary page, click Next.On the Select an action page, select Save and run once, and click Finish.On the Run with options page, accept the defaults, and click Run, and then click OK.Select View the details of this import after closing this dialog and click OK.In IBM Cognos Administration, click the Home button.The Behavior Based Client Insight for Wealth Management content is available in Public Folders in the Wealth_CustomerInsight_BIContent.zip file.Rave libraries are also available as part of the solution. They are packaged in the Wealth_CustomerInsight_Rave.zip file.Go to the IBM Cognos BI portal URL.For example, go to http://bi_node_name/ibmcognos/.On the Welcome page, click Administer IBM Cognos Content.On the libraries tab, click the Import button.Select the Wealth_CustomerInsight_Rave.zip file, and click Import.Deploying the IBM Cognos contentFor IBM Cognos Business Intelligence, you must create a data source connection, and then deploy the content files for the IBM Behavior Based Client Insight for Wealth Management solution.

Deploying the IBM Cognos reports

You must deploy the Behavior Based Client Insight for Wealth Management reports by using IBM® Cognos® Administration.

Procedure

Open a web browser.

Go to the IBM Cognos BI portal URL.

On the Welcome page, click Administer IBM Cognos Content.

On the Configuration tab, click Content Administration.

On the toolbar, click the New Import button.

In the Deployment Archive pane, select the deployment archive, and click Next.

The deployment archive is named Wealth_CustomerInsight_BIContent.zip.

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

In the Select the public folders and directory content pane, select all of the packages in the table, leave the Options as default, and click Next.

Note: Ensure that the Disable after import option is cleared.

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

On the Review the summary page, click Next.

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

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

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

In IBM Cognos Administration, click the Home button.

The Behavior Based Client Insight for Wealth Management content is available in Public Folders in the Wealth_CustomerInsight_BIContent.zip file.

Rave libraries are also available as part of the solution. They are packaged in the Wealth_CustomerInsight_Rave.zip file.

Go to the IBM Cognos BI portal URL.

For example, go to http://bi_node_name/ibmcognos/.

On the Welcome page, click Administer IBM Cognos Content.

On the libraries tab, click the Import button.

Select the Wealth_CustomerInsight_Rave.zip file, and click Import.

Parent topic: Deploying the IBM Cognos content

Installing the EAR fileThe EAR file contains the REST APIs that you use to embed the IBM Behavior Based Client Insight for Wealth Management solution in your existing system.EAR fileAPIsREST APIsLog in to the WebSphere Application Server Network Deployment administrative console.Load the IS_Wealth_Solution_EAR.ear file into one of the WebSphere Application Server nodes, either the BI node or the Analytics node.Install the application through WebSphere Application Server.Click the Applications link, and then click Install New Application.From the Specify the EAR, WAR, JAR, or SAR module to upload and install page, select Local file system, and then browse to the location on your system of the EAR file.Start the installed application, IS_Wealth.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Installing the EAR file

The EAR file contains the REST APIs that you use to embed the IBM Behavior Based Client Insight for Wealth Management solution in your existing system.

Procedure

Log in to the WebSphere Application Server Network Deployment administrative console.

Load the IS_Wealth_Solution_EAR.ear file into one of the WebSphere Application Server nodes, either the BI node or the Analytics node.

Install the application through WebSphere Application Server.

Click the Applications link, and then click Install New Application.

From the Specify the EAR, WAR, JAR, or SAR module to upload and install page, select Local file system, and then browse to the location on your system of the EAR file.

Start the installed application, IS_Wealth.

Parent topic: Installation and configuration

Adding the default PCI Cognos port number to the web portalAfter you deploy the web portal on your server, users will be able to access Cognos reports that are installed on the same computer.Cognos port numberport numberCognos defaultInitially, the web portal is pointing to Cognos reports on port 80 by default. But IBM Predictive Customer Insight installs Cognos on port 81 by default. So you must complete the following procedure for the HTML files (except login.html) that are in the web portal’s server folder on the server where you deployed the portal.For Websphere Application Server, the web portal’s server folder will be similar to: <server_installation_directory>\profiles\AppSrv01\installedApps\ADMINIB-TJGMVIINode01Cell\IS_<industry>_WebPortalEAR.ear\IS_<industry>_WebPortal.warIn a text editor, open the HTML file or files.Locate the following piece of code: function loadIframe() { var host_name = window.location.hostname; document.getElementById("iframeElement").setAttrib } </script>Add + ":81" to the code, as shown below:function loadIframe() { var host_name = window.location.hostname + ":81"; document.getElementById("iframeElement").setAttrib } </script>Save the HTML file or files.You are now able to access the Cognos reports from the web portal.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Adding the default PCI Cognos port number to the web portal

After you deploy the web portal on your server, users will be able to access Cognos reports that are installed on the same computer.

About this task

Initially, the web portal is pointing to Cognos reports on port 80 by default. But IBM Predictive Customer Insight installs Cognos on port 81 by default. So you must complete the following procedure for the HTML files (except login.html) that are in the web portal’s server folder on the server where you deployed the portal.

Note: For Websphere Application Server, the web portal’s server folder will be similar to: <server_installation_directory>\profiles\AppSrv01\installedApps\ADMINIB-TJGMVIINode01Cell\IS_<industry>_WebPortalEAR.ear\IS_<industry>_WebPortal.war

Procedure

In a text editor, open the HTML file or files.

Locate the following piece of code:

function loadIframe()
{
var host_name = window.location.hostname;
document.getElementById("iframeElement").setAttrib
}
</script>

Add + ":81" to the code, as shown below:

function loadIframe()
{
var host_name = window.location.hostname + ":81";
document.getElementById("iframeElement").setAttrib
}
</script>

Save the HTML file or files.

Results

You are now able to access the Cognos reports from the web portal.

Parent topic: Installation and configuration

Downloading the solution content to a client computerAfter you have the solution installer running, you can download the solution content files to any client computer. The solution installer deploys the content files to the server computers that are running Red Hat Enterprise Linux operating systems where you have the server components running. You can also download the solution content to computers that are running Microsoft Windows operating systems. For example, to load the Collaboration and Deployment Services content on your client computer, you can download the pes file.The solution installer must be running before you can download the solution content files.In a web browser, enter the following URLs to download the content deployment instructions: https://solution_installer_hostname:8080/Downloads/IS_Wealth_ClientInsight_1.0.3/IS_Wealth_ClientInsight_1.0.3_ClientDeploymentFiles.txt Enter the following URLs to download the content:To download the web application content, enter https://solution_installer_hostname:8080/Downloads/IS_Wealth_ClientInsight_1.0.3/Web/Wealth_ClientInsight_Web.zip To download the SPSS content, enter https://solution_installer_hostname:8080/Downloads/IS_Wealth_ClientInsight_1.0.3/Analytics/Wealth_ClientInsight_str.zip To download the Collaboration and Deployment Services content, enter https://solution_installer_hostname:8080/Downloads/IS_Wealth_ClientInsight_1.0.3/Analytics/Wealth_ClientInsight_CDS.pes Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.

Downloading the solution content to a client computer

After you have the solution installer running, you can download the solution content files to any client computer.

The solution installer deploys the content files to the server computers that are running Red Hat Enterprise Linux operating systems where you have the server components running. You can also download the solution content to computers that are running Microsoft Windows operating systems. For example, to load the Collaboration and Deployment Services content on your client computer, you can download the pes file.

Before you begin

The solution installer must be running before you can download the solution content files.

Procedure

In a web browser, enter the following URLs to download the content deployment instructions:

https://solution_installer_hostname:8080/Downloads/IS_Wealth_ClientInsight_1.0.3/IS_Wealth_ClientInsight_1.0.3_ClientDeploymentFiles.txt

Enter the following URLs to download the content:

To download the web application content, enter

https://solution_installer_hostname:8080/Downloads/IS_Wealth_ClientInsight_1.0.3/Web/Wealth_ClientInsight_Web.zip

To download the SPSS content, enter

https://solution_installer_hostname:8080/Downloads/IS_Wealth_ClientInsight_1.0.3/Analytics/Wealth_ClientInsight_str.zip

To download the Collaboration and Deployment Services content, enter

https://solution_installer_hostname:8080/Downloads/IS_Wealth_ClientInsight_1.0.3/Analytics/Wealth_ClientInsight_CDS.pes

Parent topic: Installation and configuration

Product license filesAfter you install the Behavior Based Client Insight for Wealth Management solution, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed a component.Installation and configurationThe installation and configuration of the IBM Behavior Based Client Insight for Wealth Management solution involves downloading the solution package from Passport Advantage and then configuring the various parts of it within your environment.Copying the component license files to each component computerThe swidtag file and license directory must exist on each server node computer and each computer on which you install a component of the IBM Behavior Based Client Insight for Wealth Management solution.Updating your software tag file if you change product usageIf you change your usage of the IBM Behavior Based Client Insight for Wealth Management solution, such as to a non-production environment from a production environment, you must switch the software tags for your installation.

Product license files

After you install the Behavior Based Client Insight for Wealth Management solution, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed a component.

Copying the component license files to each component computer
The swidtag file and license directory must exist on each server node computer and each computer on which you install a component of the IBM Behavior Based Client Insight for Wealth Management solution.

Updating your software tag file if you change product usage
If you change your usage of the IBM Behavior Based Client Insight for Wealth Management solution, such as to a non-production environment from a production environment, you must switch the software tags for your installation.

Parent topic: Installation and configuration

Copying the component license files to each component computerThe swidtag file and license directory must exist on each server node computer and each computer on which you install a component of the IBM Behavior Based Client Insight for Wealth Management solution. swidtag files are provided for both production and non-production use of the solution. You must copy the appropriate swidtag file for your usage. Do not rename the directory or files If you installed on a Red Hat Enterprise Linux operating system by using the solution installer, the license files are automatically copied to each server node computer.On the computer where you decompressed the artifact files, go to the iso-swid or iso-swid_NonProduction directory, and decompress the file, if applicable.Copy the swidtag file to each computer on which you installed a Behavior Based Client Insight for Wealth Management component.For example, on Microsoft Windows operating systems, copy the file so that you have a C:\IBM\BBCI_Wealth_1_0_3\iso-swid directory that contains a swidtag file. On Linux operating systems, you would have an /opt/IBM/BBCI_Wealth_1_0_3/iso-swid directory that contains a swidtag file.From the directory where you decompressed the artifact files, decompress the license.zip file, and then copy the license directory to each computer where you installed a component of the solution.For example, On Microsoft Windows operating systems, copy the directory and contents so that you have a C:\IBM\BBCI_Wealth_1_0_3\license directory that contains the license files. On Linux operating systems, you would have an /opt/IBM/BBCI_Wealth_1_0_3/license directory that contains the license files.The following folders must exist on each computer on which you installed a component of the solution:On Microsoft Windows operating systems (both server and client components):C:\IBM\BBCI_Wealth_1_0_3\license (containing the product license files)C:\IBM\BBCI_Wealth_1_0_3\iso-swid (containing the product swidtag file)On Linux operating systems where a server component is installed: /opt/IBM/BBCI_Wealth_1_0_3/license (containing the product license files) /opt/IBM/BBCI_Wealth_1_0_3/iso-swid (containing the product swidtag file)Product license filesAfter you install the Behavior Based Client Insight for Wealth Management solution, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed a component.

Copying the component license files to each component computer

The swidtag file and license directory must exist on each server node computer and each computer on which you install a component of the IBM Behavior Based Client Insight for Wealth Management solution.

swidtag files are provided for both production and non-production use of the solution. You must copy the appropriate swidtag file for your usage.

Note: Do not rename the directory or files

If you installed on a Red Hat Enterprise Linux operating system by using the solution installer, the license files are automatically copied to each server node computer.

Procedure

On the computer where you decompressed the artifact files, go to the iso-swid or iso-swid_NonProduction directory, and decompress the file, if applicable.

Copy the swidtag file to each computer on which you installed a Behavior Based Client Insight for Wealth Management component.

For example, on Microsoft Windows operating systems, copy the file so that you have a C:\IBM\BBCI_Wealth_1_0_3\iso-swid directory that contains a swidtag file. On Linux operating systems, you would have an /opt/IBM/BBCI_Wealth_1_0_3/iso-swid directory that contains a swidtag file.

From the directory where you decompressed the artifact files, decompress the license.zip file, and then copy the license directory to each computer where you installed a component of the solution.

For example, On Microsoft Windows operating systems, copy the directory and contents so that you have a C:\IBM\BBCI_Wealth_1_0_3\license directory that contains the license files. On Linux operating systems, you would have an /opt/IBM/BBCI_Wealth_1_0_3/license directory that contains the license files.

Results

The following folders must exist on each computer on which you installed a component of the solution:

On Microsoft Windows operating systems (both server and client components):

C:\IBM\BBCI_Wealth_1_0_3\license (containing the product license files)

C:\IBM\BBCI_Wealth_1_0_3\iso-swid (containing the product swidtag file)

On Linux operating systems where a server component is installed:

/opt/IBM/BBCI_Wealth_1_0_3/license (containing the product license files)

/opt/IBM/BBCI_Wealth_1_0_3/iso-swid (containing the product swidtag file)

Parent topic: Product license files

Updating your software tag file if you change product usageIf you change your usage of the IBM Behavior Based Client Insight for Wealth Management solution, such as to a non-production environment from a production environment, you must switch the software tags for your installation.You must copy the appropriate software tag file to each computer on which a server or client component is installed.On the computer where you decompressed the artifact files, go to the iso-swid or iso-swid_NonProduction directory, and decompress the file, if applicable.Copy the swidtag file to each computer on which you installed a component and replace the existing file.For example, on Microsoft Windows operating systems, copy the file so that you have a C:\IBM\BBCI_Wealth_1_0_3\iso-swid directory that contains a swidtag file. On Linux operating systems, you would have an /opt/IBM/BBCI_Wealth_1_0_3/iso-swid directory that contains a swidtag file.Product license filesAfter you install the Behavior Based Client Insight for Wealth Management solution, you must ensure that the appropriate swidtag file and license directory exists on each computer on which you installed a component.

Updating your software tag file if you change product usage

If you change your usage of the IBM Behavior Based Client Insight for Wealth Management solution, such as to a non-production environment from a production environment, you must switch the software tags for your installation.

You must copy the appropriate software tag file to each computer on which a server or client component is installed.

Procedure

On the computer where you decompressed the artifact files, go to the iso-swid or iso-swid_NonProduction directory, and decompress the file, if applicable.

Copy the swidtag file to each computer on which you installed a component and replace the existing file.

For example, on Microsoft Windows operating systems, copy the file so that you have a C:\IBM\BBCI_Wealth_1_0_3\iso-swid directory that contains a swidtag file. On Linux operating systems, you would have an /opt/IBM/BBCI_Wealth_1_0_3/iso-swid directory that contains a swidtag file.

Parent topic: Product license files

Accessibility features Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products. accessibilityFor information about the commitment that IBM has to accessibility, see the IBM Accessibility Center (www.ibm.com/able).IBM Cognos HTML documentation has accessibility features. PDF documents are supplemental and, as such, include no added accessibility features. Report output In IBM Cognos Administration, you can enable system-wide settings to create accessible report output. For more information, see the IBM Cognos Business Intelligence Administration and Security Guide. In IBM Cognos Report Studio, you can enable settings to create accessible output for individual reports. For more information, see the IBM Cognos Report Studio User Guide. You can access the previously mentioned documents at IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter).

Accessibility features

Accessibility features help users who have a physical disability, such as restricted mobility or limited vision, to use information technology products.

For information about the commitment that IBM® has to accessibility, see the IBM Accessibility Center (www.ibm.com/able).

IBM Cognos® HTML documentation has accessibility features. PDF documents are supplemental and, as such, include no added accessibility features.

Report output

In IBM Cognos Administration, you can enable system-wide settings to create accessible report output. For more information, see the IBM Cognos Business Intelligence Administration and Security Guide. In IBM Cognos Report Studio, you can enable settings to create accessible output for individual reports. For more information, see the IBM Cognos Report Studio User Guide. You can access the previously mentioned documents at IBM Knowledge Center (http://www.ibm.com/support/knowledgecenter).

TroubleshootingThis section contains troubleshooting information for the Behavior Based Client Insight for Wealth Management 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.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

This section contains troubleshooting information for the Behavior Based Client Insight for Wealth Management 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.

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.

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 Behavior Based Client Insight for Wealth Management installation.Troubleshooting resourcesTroubleshooting resources are sources of information that can help you resolve a problem that you are having with an IBM product.

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.

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

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.TroubleshootingThis section contains troubleshooting information for the Behavior Based Client Insight for Wealth Management installation.

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

Client data ingestion: SPSS streamsThe IBM solution works with IBM Predictive Customer Insight.SPSSclient data ingestionclient data ingestionTwo SPSS streams are provided that enable the client to ingest data into the solution database. The client data in a predefined Comma Separated Value (CSV) file format is provided to the stream as input, and the stream extracts the data from the CSV file and inserts the records into relevant tables in the solution database. The client data can be of the following types:Customer demographic details (including contact information)Customer transactions dataThere are two separate streams for each of the types of data.Purpose of the SPSS streamsThe SPSS streams act as an important ETL process between the client data and the solution database. CSV formatsThis section provides the CSV formats for both customers and transactions.Prerequisites for the ETL streamsThere are no prerequisites for the Wealth Customer ETL stream. However, there are prerequisites for the Wealth Transaction ETL stream.End result of using the ETL streamsThis page illustrates the results of the ETL streams.

Client data ingestion: SPSS streams

The IBM solution works with IBM Predictive Customer Insight.

Two SPSS streams are provided that enable the client to ingest data into the solution database. The client data in a predefined Comma Separated Value (CSV) file format is provided to the stream as input, and the stream extracts the data from the CSV file and inserts the records into relevant tables in the solution database. The client data can be of the following types:

Customer demographic details (including contact information)

Customer transactions data

There are two separate streams for each of the types of data.

Purpose of the SPSS streams
The SPSS streams act as an important ETL process between the client data and the solution database.

CSV formats
This section provides the CSV formats for both customers and transactions.

Prerequisites for the ETL streams
There are no prerequisites for the Wealth Customer ETL stream. However, there are prerequisites for the Wealth Transaction ETL stream.

End result of using the ETL streams
This page illustrates the results of the ETL streams.

Purpose of the SPSS streamsThe SPSS streams act as an important ETL process between the client data and the solution database. They perform the following operations:Extract raw client data from the CSV filesTransform data according to the solution needs (such as eliminating the unwanted spaces) Filter the transformed data and load it into relevant tables in the solution database By using the streams, clients can easily ingest large sets of data related to customers and their transactions.The following two streams are provided:Wealth Customer ETL – Customer demographic details (including contact information)Wealth Transaction ETL - Customer transactions dataClient data ingestion: SPSS streamsThe IBM solution works with IBM Predictive Customer Insight.

Purpose of the SPSS streams

The SPSS streams act as an important ETL process between the client data and the solution database.

They perform the following operations:

Extract raw client data from the CSV files

Transform data according to the solution needs (such as eliminating the unwanted spaces)

Filter the transformed data and load it into relevant tables in the solution database

By using the streams, clients can easily ingest large sets of data related to customers and their transactions.

The following two streams are provided:

Wealth Customer ETL – Customer demographic details (including contact information)

Wealth Transaction ETL - Customer transactions data

Parent topic: Client data ingestion: SPSS streams

CSV formatsThis section provides the CSV formats for both customers and transactions.In the following CSV files, you must replace the NULL values by default values for the streams to work correctly.Format for the CSV file input to the Wealth Customer ETL "CITY","COUNTRY","EMAIL","POSTCODE_AREA","STATE","STREET","FULL_TELEPHONE_NUMBER", "BIRTH_DATE","FULL_NAME","PHOTO","MARITAL_STATUS","EDUCATION" CITY > city where the customer lives COUNTRY > country where the customer lives EMAIL > customer's email address POSTCODE_AREA > postal code of the area where the customer lives STATE > state where the customer lives STREET > street address where the customer lives FULL_TELEPHONE_NUMBER > customer's telephone number BIRTH_DATE > customer's date of birth FULL_NAME > customer's full name PHOTO > Link to the customer's photo (URL) MARITAL_STATUS > customer's marital status EDUCATION > customer's most recently completed educationSample CSV file for customers "CITY","COUNTRY","EMAIL","POSTCODE_AREA","STATE","STREET", "FULL_TELEPHONE_NUMBER","BIRTH_DATE","FULL_NAME","PHOTO","MARITAL_STATUS","EDUCATION" "Jamaica","US","vereen@yahoo.com","04017","MA","11 smith street","8572055850", "1986-06-17", "Alfonso Osborne","http://hostname/ibmcognos/samples/images/Customer/3.png","Married","Graduate"Format for the CSV file input to the Wealth Transaction ETL "CALENDAR_DATE","NAME","FULL_NAME","BIRTH_DATE","PHOTO", "MARITAL_STATUS","EDUCATION","DESCRIPTION","NAME","NET_CASH_FLOW_AMOUNT" Notice that in the format, there are two instances of "NAME". The first instance of “NAME” relates to the channel name. The second instance of “NAME” relates to the transaction type name. In the stream this is referred to as NAME(1). CALENDAR_DATE > date of the transaction NET_CASH_FLOW_AMOUNT > transaction amount BIRTH_DATE > customer's date of birth FULL_NAME > customer's full name PHOTO > Link to the customer's photo(URL) MARITAL_STATUS > customer's marital status EDUCATION > customer's most recently completed education. DESCRIPTION > relates to geographic area descriptionSample CSV file (transactions) In the following sample there are three transactions related to the customer provided in the customer's csv file. "CALENDAR_DATE","NAME","FULL_NAME","BIRTH_DATE","PHOTO", "MARITAL_STATUS","EDUCATION","DESCRIPTION","NAME","NET_CASH_FLOW_AMOUNT" "1980-04-07","In Person","Alfonso Osborne","1986-06-17", "http://hostname/ibmcognos/samples/images/Customer/3.png", "Married","Graduate","Remote","Credits","90937.90674" "1985-12-07","In Person","Alfonso Osborne","1986-06-17", "http://hostname/ibmcognos/samples/images/Customer/3.png", "Married","Graduate","Remote","Credits","124841.22253" "1985-12-07","In Person","Alfonso Osborne","1986-06-17", "http://hostname/ibmcognos/samples/images/Customer/3.png", "Married","Graduate","Remote","Money Market","-4815.30429"Client data ingestion: SPSS streamsThe IBM solution works with IBM Predictive Customer Insight.

CSV formats

This section provides the CSV formats for both customers and transactions.

Important: In the following CSV files, you must replace the NULL values by default values for the streams to work correctly.

Format for the CSV file input to the Wealth Customer ETL

"CITY","COUNTRY","EMAIL","POSTCODE_AREA","STATE","STREET","FULL_TELEPHONE_NUMBER",
"BIRTH_DATE","FULL_NAME","PHOTO","MARITAL_STATUS","EDUCATION"

CITY > city where the customer lives
COUNTRY > country where the customer lives
EMAIL > customer's email address
POSTCODE_AREA > postal code of the area where the customer lives
STATE > state where the customer lives
STREET > street address where the customer lives
FULL_TELEPHONE_NUMBER > customer's telephone number
BIRTH_DATE > customer's date of birth
FULL_NAME > customer's full name
PHOTO > Link to the customer's photo (URL)
MARITAL_STATUS > customer's marital status
EDUCATION > customer's most recently completed education

Sample CSV file for customers

"CITY","COUNTRY","EMAIL","POSTCODE_AREA","STATE","STREET",
"FULL_TELEPHONE_NUMBER","BIRTH_DATE","FULL_NAME","PHOTO","MARITAL_STATUS","EDUCATION"

"Jamaica","US","vereen@yahoo.com","04017","MA","11 smith street","8572055850", "1986-06-17",
"Alfonso Osborne","http://hostname/ibmcognos/samples/images/Customer/3.png","Married","Graduate"

Format for the CSV file input to the Wealth Transaction ETL

"CALENDAR_DATE","NAME","FULL_NAME","BIRTH_DATE","PHOTO",
"MARITAL_STATUS","EDUCATION","DESCRIPTION","NAME","NET_CASH_FLOW_AMOUNT"

Notice that in the format, there are two instances of "NAME".

The first instance of “NAME” relates to the channel name.

The second instance of “NAME” relates to the transaction type name. In the stream this is referred to as NAME(1).

CALENDAR_DATE > date of the transaction
NET_CASH_FLOW_AMOUNT > transaction amount
BIRTH_DATE > customer's date of birth
FULL_NAME > customer's full name
PHOTO > Link to the customer's photo(URL)
MARITAL_STATUS > customer's marital status
EDUCATION > customer's most recently completed education.
DESCRIPTION > relates to geographic area description

Sample CSV file (transactions)

In the following sample there are three transactions related to the customer provided in the customer's csv file.

"CALENDAR_DATE","NAME","FULL_NAME","BIRTH_DATE","PHOTO",
"MARITAL_STATUS","EDUCATION","DESCRIPTION","NAME","NET_CASH_FLOW_AMOUNT"

"1980-04-07","In Person","Alfonso Osborne","1986-06-17",
"http://hostname/ibmcognos/samples/images/Customer/3.png",
"Married","Graduate","Remote","Credits","90937.90674"

"1985-12-07","In Person","Alfonso Osborne","1986-06-17",
"http://hostname/ibmcognos/samples/images/Customer/3.png",
"Married","Graduate","Remote","Credits","124841.22253"

"1985-12-07","In Person","Alfonso Osborne","1986-06-17",
"http://hostname/ibmcognos/samples/images/Customer/3.png",
"Married","Graduate","Remote","Money Market","-4815.30429"

Parent topic: Client data ingestion: SPSS streams

Prerequisites for the ETL streamsThere are no prerequisites for the Wealth Customer ETL stream. However, there are prerequisites for the Wealth Transaction ETL stream.The following perquisites are required for the Wealth Transaction ETL to work:The Wealth Customer ETL stream must be run first to load the customer details into the INDIVIDUAL_CUSTOMER_DIMENSION table. This is because the Wealth Transaction ETL stream uses this table to establish relationship between the customer and his transactions. Each customer is identified by a distinct key: (FULL_NAME, BIRTH_DATE, PHOTO, MARITAL_STATUS, EDUCATION). A combination of all these values would uniquely identify a customer. Using this key as a reference, only transactions related to the customers that are loaded through the Wealth Customer ETL stream must be provided in the CSV input file for the Wealth Transaction ETL stream.The CALENDAR_DATE provided in the CSV input file must be present in the CALENDAR_DATE_DIMENSION table of the Wealth solution database.The channel name (NAME) provided in the CSV input file must be present in the CHANNEL_DIMENSION table of the Wealth solution database.The transaction type name (NAME(1))provided in the CSV input file must be present in the TRANSACTION_DIMENSION table of the Wealth solution database.The geographic area description (DESCRIPTION) provided in the CSV input file must be present in the GEOGRAPHIC_AREA_DIMENSION table of the Wealth solution database. Client data ingestion: SPSS streamsThe IBM solution works with IBM Predictive Customer Insight.

Prerequisites for the ETL streams

There are no prerequisites for the Wealth Customer ETL stream. However, there are prerequisites for the Wealth Transaction ETL stream.

The following perquisites are required for the Wealth Transaction ETL to work:

The Wealth Customer ETL stream must be run first to load the customer details into the INDIVIDUAL_CUSTOMER_DIMENSION table. This is because the Wealth Transaction ETL stream uses this table to establish relationship between the customer and his transactions.

Each customer is identified by a distinct key: (FULL_NAME, BIRTH_DATE, PHOTO, MARITAL_STATUS, EDUCATION). A combination of all these values would uniquely identify a customer. Using this key as a reference, only transactions related to the customers that are loaded through the Wealth Customer ETL stream must be provided in the CSV input file for the Wealth Transaction ETL stream.

The CALENDAR_DATE provided in the CSV input file must be present in the CALENDAR_DATE_DIMENSION table of the Wealth solution database.

The channel name (NAME) provided in the CSV input file must be present in the CHANNEL_DIMENSION table of the Wealth solution database.

The transaction type name (NAME(1))provided in the CSV input file must be present in the TRANSACTION_DIMENSION table of the Wealth solution database.

The geographic area description (DESCRIPTION) provided in the CSV input file must be present in the GEOGRAPHIC_AREA_DIMENSION table of the Wealth solution database.

Parent topic: Client data ingestion: SPSS streams

End result of using the ETL streamsThis page illustrates the results of the ETL streams.Wealth Customer ETL The stream, shown in the following image, filters and loads the input data from the CSV file. "BIRTH_DATE","FULL_NAME","PHOTO","MARITAL_STATUS","EDUCATION" are inserted into the INDIVIDUAL_CUSTOMER_DIMENSION table. The combination of all these columns forms a distinct key that identifies a particular customer. "CITY","COUNTRY","EMAIL","POSTCODE_AREA","STATE","STREET","FULL_TELEPHONE_NUMBER" are inserted into the CONTACT_INFORMATION_DIMENSION table. The combination of all these columns forms a distinct key that identifies a particular contact. After that, the stream establishes a relationship between a customer and his contacts. This relationship information is stored in the INVOLVED_PARTY_CONTACT_INFORMATION_BRIDGE table. In total, three tables (INDIVIDUAL_CUSTOMER_DIMENSION, CONTACT_INFORMATION_DIMENSION and INVOLVED_PARTY_CONTACT_INFORMATION_BRIDGE) are populated as a result of running this stream.Wealth Transaction ETL The stream, shown in the following image, filters and loads the input data from the CSV file. The stream performs the following steps: Merges the data from the transactions csv file with the CALENDAR_DATE_DIMENSION table using the CALENDAR_DATE field and picks up the corresponding CALENDAR_DATE_DIMENSION_IDs.Merges the data from the transactions csv file with the CHANNEL_DIMENSION table using the NAME field and picks up the corresponding CHANNEL_DIMENSION_IDs. Merges the data from the transactions csv file with the TRANSACTION_DIMENSION table using the NAME field and picks up the correspondingTRANSACTION_DIMENSION_IDs. Merges the data from the transactions csv file with the INDIVIDUAL_CUSTOMER_DIMENSION table using the key: (FULL_NAME, BIRTH_DATE, PHOTO, MARITAL_STATUS, EDUCATION) and picks up the corresponding INDIVIDUAL_CUSTOMER_DIMENSION_IDs. Finally, it inserts the primary keys along with the corresponding NET_CASH_FLOW_AMOUNT field into the TRANSACTION_FACT table as a result of running this stream.Client data ingestion: SPSS streamsThe IBM solution works with IBM Predictive Customer Insight.

End result of using the ETL streams

This page illustrates the results of the ETL streams.

Wealth Customer ETL

The stream, shown in the following image, filters and loads the input data from the CSV file.

"BIRTH_DATE","FULL_NAME","PHOTO","MARITAL_STATUS","EDUCATION" are inserted into the INDIVIDUAL_CUSTOMER_DIMENSION table. The combination of all these columns forms a distinct key that identifies a particular customer.

"CITY","COUNTRY","EMAIL","POSTCODE_AREA","STATE","STREET","FULL_TELEPHONE_NUMBER" are inserted into the CONTACT_INFORMATION_DIMENSION table. The combination of all these columns forms a distinct key that identifies a particular contact.

After that, the stream establishes a relationship between a customer and his contacts. This relationship information is stored in the INVOLVED_PARTY_CONTACT_INFORMATION_BRIDGE table.

In total, three tables (INDIVIDUAL_CUSTOMER_DIMENSION, CONTACT_INFORMATION_DIMENSION and INVOLVED_PARTY_CONTACT_INFORMATION_BRIDGE) are populated as a result of running this stream.

Wealth Transaction ETL

The stream, shown in the following image, filters and loads the input data from the CSV file.

The stream performs the following steps:

Merges the data from the transactions csv file with the CALENDAR_DATE_DIMENSION table using the CALENDAR_DATE field and picks up the corresponding CALENDAR_DATE_DIMENSION_IDs.

Merges the data from the transactions csv file with the CHANNEL_DIMENSION table using the NAME field and picks up the corresponding CHANNEL_DIMENSION_IDs.

Merges the data from the transactions csv file with the TRANSACTION_DIMENSION table using the NAME field and picks up the correspondingTRANSACTION_DIMENSION_IDs.

Merges the data from the transactions csv file with the INDIVIDUAL_CUSTOMER_DIMENSION table using the key: (FULL_NAME, BIRTH_DATE, PHOTO, MARITAL_STATUS, EDUCATION) and picks up the corresponding INDIVIDUAL_CUSTOMER_DIMENSION_IDs.

Finally, it inserts the primary keys along with the corresponding NET_CASH_FLOW_AMOUNT field into the TRANSACTION_FACT table as a result of running this stream.

Parent topic: Client data ingestion: SPSS streams

Generating SLMT logs for license self-complianceSLMT stands for software license metric tagging. It generates a log file that indicates the number of customers in your database so that you can monitor your license compliance.From the Database folder, extract the slmt.zip file.The following two files are in the slmt folder: Wealth.jarWealth.properties The Wealth.jar file contains the slmt source code to generate the xml files, and the Wealth.properties file provides the database details for the Wealth.jar file.In the Wealth.properties file, modify the values for your environment. The file contains the following information: dbaddress={IP_Address/Hostname} // Contains the IP address/hostname of the database node dbport={DB_Port} // Database port for DB2 on the above node dbusername={DB_Username} // DB2 username dbpassword={DB_Password} // DB2 port dbname={WEALTH} // Database name dbtablename={PCIWLTH.INDIVIDUAL_CUSTOMER_DIMENSION} // Table nameSet up a cron job to produce the tags daily. Cron jobs are scheduler services that can be configured to run at a specific time. For example, if the cron job is set to run at 11:59 PM daily, the .jar file runs at 11:59 and the SLMT log file records the number of customers. If customers are added to or removed from the database, it is reflected in the log file. Log in as root on the node where you want the tag files generated. Enter the following command: crontab -eAppend the cron file with the following line {Minute}{Hour}{Day_Of_Month}{Month}{Day_Of_Week} java -jar {Full_path_to_.jar_file} {Full_path_to_.properties_file}For example, to generate the xml files at 11:59 PM daily, use the following command: 59 23 * * * java -jar /root/Downloads/ slmt/Wealth.jar /root/Downloads/slmt/Wealth.propertiesNow you can determine the number of customers in the database by referring to the 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, and then a new log file is created. The following code shows what the slm tag looks like: <SchemaVersion>2.1.1</SchemaVersion> <SoftwareIdentity> <PersistentId>b74be4a978bf4b66bd56271915f0ea5f</PersistentId> <Name>Behavior Based Client Insight for Wealth Management</Name> <InstanceId>/opt/ibm</InstanceId> </SoftwareIdentity> <Metric logTime="2015-12-08T19:57:18-08:00"> <Type>Metric.RESOURCE_VALUE_UNIT</Type> <SubType>CUSTOMERS</SubType> <Value>1000</Value> <Period> <StartTime>2015-12-07T19:57:17-08:00</StartTime> <EndTime>2015-12-08T19:57:17-08:00</EndTime> </Period> </Metric>

Generating SLMT logs for license self-compliance

SLMT stands for software license metric tagging. It generates a log file that indicates the number of customers in your database so that you can monitor your license compliance.

Procedure

From the Database folder, extract the slmt.zip file.

The following two files are in the slmt folder:

Wealth.jar

Wealth.properties

The Wealth.jar file contains the slmt source code to generate the xml files, and the Wealth.properties file provides the database details for the Wealth.jar file.

In the Wealth.properties file, modify the values for your environment.

The file contains the following information:

dbaddress={IP_Address/Hostname}		// Contains the IP address/hostname of the database node
dbport={DB_Port}					// Database port for DB2 on the above node
dbusername={DB_Username}			// DB2 username
dbpassword={DB_Password}			// DB2 port
dbname={WEALTH}					// Database name
dbtablename={PCIWLTH.INDIVIDUAL_CUSTOMER_DIMENSION}			// Table name

Set up a cron job to produce the tags daily.

Cron jobs are scheduler services that can be configured to run at a specific time.

For example, if the cron job is set to run at 11:59 PM daily, the .jar file runs at 11:59 and the SLMT log file records the number of customers. If customers are added to or removed from the database, it is reflected in the log file.

Log in as root on the node where you want the tag files generated.

Enter the following command: crontab -e

Append the cron file with the following line {Minute}{Hour}{Day_Of_Month}{Month}{Day_Of_Week} java -jar {Full_path_to_.jar_file} {Full_path_to_.properties_file}

For example, to generate the xml files at 11:59 PM daily, use the following command:

59 23 * * * java -jar /root/Downloads/
slmt/Wealth.jar /root/Downloads/slmt/Wealth.properties

Results

Now you can determine the number of customers in the database by referring to the 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, and then a new log file is created.

The following code shows what the slm tag looks like:

<SchemaVersion>2.1.1</SchemaVersion>
<SoftwareIdentity>
        <PersistentId>b74be4a978bf4b66bd56271915f0ea5f</PersistentId>
        <Name>Behavior Based Client Insight for Wealth Management</Name>
        <InstanceId>/opt/ibm</InstanceId>
</SoftwareIdentity>
<Metric logTime="2015-12-08T19:57:18-08:00">
        <Type>Metric.RESOURCE_VALUE_UNIT</Type>
        <SubType>CUSTOMERS</SubType>
        <Value>1000</Value>
        <Period>
                <StartTime>2015-12-07T19:57:17-08:00</StartTime>
                <EndTime>2015-12-08T19:57:17-08:00</EndTime>
        </Period>
</Metric>

JDBC connection to WebSphere Application ServerThe IBM Behavior Based Client Insight for Wealth Management solution provides a set of RESTful APIs to allow you to create applications to programmatically execute operations. If you're using Websphere Application Server as your database, you must set up a JDBC connection to the server. The provided instructions and procedures are based on WAS v8.5.5.REST APIsJDBC connection to WebSphereWebSphere Application ServerTo set up your JDBC connection, you must complete the following tasks, in order:Configure the JDBC providerCreate an authentication aliasConfigure the JDBC data sourceConfigure the JDBC provider In this section, you'll set up the DB2 using IBM J2CC Driver (XA) for your JDBC connection.Log in to the WebSphere Application Server console.Navigate to the JDBC providers section. If you already have the DB2 Using IBM J2CC Driver (XA) setup, proceed to Create an authentication alias. Otherwise, create a new JDBC provider by clicking New..., as highlighted in the image.Enter the JDBC provider details as per the following image, then click Next.Use the default Class path settings, as shown in the following image, and click Apply. Specify the directory location where the db2jcc4.jar and db2jcc_license_cisuz.jar files are present on the server. The jar files are included in the WebSphere installation package.Click Next.Review the summary page and click Finish.Create an authentication alias In this section, you'll specify the authorized users (IDs and passwords) who have access to the database.From the WAS console, go to the Global Security section and click J2C authentication data.Click New...In the next page, enter an arbitrary Alias name. Enter the User ID and Password that you use to connect to your database. The Description field is optional. Click Apply and then OK.Configure the JDBC data source In this section, you'll configure your JDBC data source and test the connection.From the WAS console, go to the Data Sources section and click New...In the next page, enter an arbitrary Data source name. Enter jdbc/pciwlth in the JNDI name field. The JNDI name is used by the REST API to connect to the database. Click Next.Choose Select an existing JDBC provider. Select the JDBC provider that you created in the first task. Click Next.Provide the Database name that you wish to access. Provide the Server name that you wish to connect to and the Port number. The remaining details can retain their default settings. Click Next.Set the authentication alias that you created earlier, then click Next.Verify the summary information and click Finish.When you're prompted to save the server configuration changes, click Save.Select the JDBC data source that you have created and click Test connection. If successful, a message will appear indicating that a successful connection was established.

JDBC connection to WebSphere Application Server

The IBM® Behavior Based Client Insight for Wealth Management solution provides a set of RESTful APIs to allow you to create applications to programmatically execute operations. If you're using Websphere Application Server as your database, you must set up a JDBC connection to the server. The provided instructions and procedures are based on WAS v8.5.5.

To set up your JDBC connection, you must complete the following tasks, in order:

Configure the JDBC provider

Create an authentication alias

Configure the JDBC data source

Configure the JDBC provider

In this section, you'll set up the DB2 using IBM J2CC Driver (XA) for your JDBC connection.

Log in to the WebSphere Application Server console.

Navigate to the JDBC providers section.

If you already have the DB2 Using IBM J2CC Driver (XA) setup, proceed to Create an authentication alias. Otherwise, create a new JDBC provider by clicking New..., as highlighted in the image.

Enter the JDBC provider details as per the following image, then click Next.

Use the default Class path settings, as shown in the following image, and click Apply.

Specify the directory location where the db2jcc4.jar and db2jcc_license_cisuz.jar files are present on the server. The jar files are included in the WebSphere installation package.

Click Next.

Review the summary page and click Finish.

Create an authentication alias

In this section, you'll specify the authorized users (IDs and passwords) who have access to the database.

From the WAS console, go to the Global Security section and click J2C authentication data.

Click New...

In the next page, enter an arbitrary Alias name. Enter the User ID and Password that you use to connect to your database. The Description field is optional.

Click Apply and then OK.

Configure the JDBC data source

In this section, you'll configure your JDBC data source and test the connection.

From the WAS console, go to the Data Sources section and click New...

In the next page, enter an arbitrary Data source name.

Enter "jdbc/pciwlth" in the JNDI name field. The JNDI name is used by the REST API to connect to the database.

Click Next.

Choose Select an existing JDBC provider. Select the JDBC provider that you created in the first task. Click Next.

Provide the Database name that you wish to access. Provide the Server name that you wish to connect to and the Port number. The remaining details can retain their default settings. Click Next.

Set the authentication alias that you created earlier, then click Next.

Verify the summary information and click Finish.

When you're prompted to save the server configuration changes, click Save.

Select the JDBC data source that you have created and click Test connection. If successful, a message will appear indicating that a successful connection was established.

REST API referenceThe IBM Behavior Based Client Insight for Wealth Management solution provides a set of RESTful APIs to allow you to create applications to programmatically invoke operations and extend industry solutions capabilities.The representational state transfer (REST) API provides a lightweight interface that uses HTTP requests to communicate to the server. The APIs can be used to extract and aggregate data for further processing in other systems. All supported resources are listed in the following sections and are actionable using a GET operation.Behavior Based Client Insight for Wealth Management REST API reference documentation is accessible in a Swagger interface, which allows you to test supported operations directly from the API documentation. After deploying the EAR file (IS_Wealth_EAR) on a WebSphere Application Server, you can visit the following link to access the API documentation: http://<hostname>:<port>/iswealth-restapiThe Swagger definition file can be accessed at: /iswealth/utility/docs/json/getIf a request returns an empty JSON response, this indicates that there were no records in the database that matched the parameters specified in the request. If an error occurred, one of the following error codes may be returned:IS_WEALTH_ERR00Unknown errorIS_WEALTH_ERR01A customerid is required.IS_WEALTH_ERR02The specified customer_id parameter is invalid.IS_WEALTH_ERR03The specified pagestart parameter is invalid.IS_WEALTH_ERR04The specified pagesize is invalid.IS_WEALTH_ERR05Database errorIS_WEALTH_ERR06A segment parameter is required.IS_WEALTH_ERR07A networth parameter is required.The Behavioral Segmentation REST API allows you to create your own segments and associated segment definitions. This is a generic API that applies to Behavior Based Customer Insight for Banking, Behavior Based Client Insight for Wealth Management, and Behavior Based Customer Insight for Insurance. The following error codes apply to the Behavioral Segmentation REST API.IS_SEGMENTATION_ERR00Unknown errorIS_SEGMENTATION_ERR01Could not parse the JSON input. Please check the JSON input and try again.IS_SEGMENTATION_ERR02Failed to insert the segment into the database.IS_SEGMENTATION_ERR03Category does not exist in the data dictionary.IS_SEGMENTATION_ERR06Database error.IS_SEGMENTATION_ERR15No records found.IS_SEGMENTATION_ERR16Failed to create batch statements for insert.IS_SEGMENTATION_ERR17Failed to insert the segment definitions into the database.IS_SEGMENTATION_ERR18The industry parameter is required.IS_SEGMENTATION_ERR19The industry parameter is incorrect. Supported values are banking, wealth, or insurance.IS_SEGMENTATION_ERR20The segmented parameter is required.Errors will include a flag: false indicator in the response body.The URLs used to issue REST commands must adhere to the US-ASCII character set, including reserved and restricted characters. For example, a space must be URL-encoded as %20.For additional information on the Java API, please reference the provided Javadocs that are included in the installation package. Customizing segmentsThe Behavioral Segmentation REST API allows you to create and delete custom segments and their associated segment definitions. The Segmentation Tool provides an interface for quickly editing or creating new segments.

REST API reference

The IBM® Behavior Based Client Insight for Wealth Management solution provides a set of RESTful APIs to allow you to create applications to programmatically invoke operations and extend industry solutions capabilities.

The representational state transfer (REST) API provides a lightweight interface that uses HTTP requests to communicate to the server. The APIs can be used to extract and aggregate data for further processing in other systems. All supported resources are listed in the following sections and are actionable using a GET operation.

Behavior Based Client Insight for Wealth Management REST API reference documentation is accessible in a Swagger interface, which allows you to test supported operations directly from the API documentation. After deploying the EAR file (IS_Wealth_EAR) on a WebSphere Application Server, you can visit the following link to access the API documentation:

http://<hostname>:<port>/iswealth-restapi

The Swagger definition file can be accessed at: /iswealth/utility/docs/json/get

If a request returns an empty JSON response, this indicates that there were no records in the database that matched the parameters specified in the request. If an error occurred, one of the following error codes may be returned:

IS_WEALTH_ERR00

Unknown error

IS_WEALTH_ERR01

A customerid is required.

IS_WEALTH_ERR02

The specified customer_id parameter is invalid.

IS_WEALTH_ERR03

The specified pagestart parameter is invalid.

IS_WEALTH_ERR04

The specified pagesize is invalid.

IS_WEALTH_ERR05

Database error

IS_WEALTH_ERR06

A segment parameter is required.

IS_WEALTH_ERR07

A networth parameter is required.

The Behavioral Segmentation REST API allows you to create your own segments and associated segment definitions. This is a generic API that applies to Behavior Based Customer Insight for Banking, Behavior Based Client Insight for Wealth Management, and Behavior Based Customer Insight for Insurance. The following error codes apply to the Behavioral Segmentation REST API.

IS_SEGMENTATION_ERR00

Unknown error

IS_SEGMENTATION_ERR01

Could not parse the JSON input. Please check the JSON input and try again.

IS_SEGMENTATION_ERR02

Failed to insert the segment into the database.

IS_SEGMENTATION_ERR03

Category does not exist in the data dictionary.

IS_SEGMENTATION_ERR06

Database error.

IS_SEGMENTATION_ERR15

No records found.

IS_SEGMENTATION_ERR16

Failed to create batch statements for insert.

IS_SEGMENTATION_ERR17

Failed to insert the segment definitions into the database.

IS_SEGMENTATION_ERR18

The industry parameter is required.

IS_SEGMENTATION_ERR19

The industry parameter is incorrect. Supported values are banking, wealth, or insurance.

IS_SEGMENTATION_ERR20

The segmented parameter is required.

Errors will include a "flag: false" indicator in the response body.

The URLs used to issue REST commands must adhere to the US-ASCII character set, including reserved and restricted characters. For example, a space must be URL-encoded as "%20".

Note: For additional information on the Java API, please reference the provided Javadocs that are included in the installation package.

Customizing segments
The Behavioral Segmentation REST API allows you to create and delete custom segments and their associated segment definitions. The Segmentation Tool provides an interface for quickly editing or creating new segments.

Customizing segmentsThe Behavioral Segmentation REST API allows you to create and delete custom segments and their associated segment definitions. The Segmentation Tool provides an interface for quickly editing or creating new segments.For information on using the Segmentation Tool, see the topic Creating and managing customer segmentsIn the Behavior Based Client Insight for Wealth Management solution, users with the appropriate permissions can add, edit, or delete behavioral customer segments by using the Segmentation Tool..Segment data dictionary Segment definitions must conform to the behavioral categories defined in the segment data dictionary. All categories in the data dictionary are top-level and have a corresponding list of sub-categories. When creating a segment, you must provide conditions that define a segment at the sub-category level. The segment data dictionary for your industry solution is specified in the following table. Wealth data dictionaryCategoriesSub-categoriesASSETSBonds, Commodities, Credits, Derivatives, Estate Funds, Forex, Money Market, Stocks, OthersTRADINGBonds, Commodities, Credits, Derivatives, Estate Funds, Forex, Money Market, Stocks, OthersFUNDINGRegular, Rare, LumpyINTERACTIONRare, Frequent, Less Frequent The categories are defined based on the customer transactions data. ASSETSAssets owned by the user in any of the listed sub-categories.TRADINGTrading activity performed by the user in any of the listed sub-categories.FUNDINGFunding pattern for the user.INTERACTIONInteraction pattern for the user. Implies interaction with the wealth manager. Segment definition A segment definition is created by using any combination of these categories and the relevant sub-categories. As mentioned, conditions that define a segment are specified at the sub-category level. Some predefined segments are included in your industry solution. The REST API accepts the segment definition in the form of a JSON input string and persists it to the database. The JSON format for the segment definition is as follows: { "segment": "segment_name", "categories": [ { "name": "category_name", "subcategories": [ {"name": "subcat_name", "operator": "value", "deviation": value}, ... ] }, ... ] } segmentThis attribute is a string that holds the segment name.categoriesThis is an array of categories. Within the categories array for each category, you have:nameThis attribute is a string that holds the category name.subcategoriesThis is an array of subcategories. Within the subcategories array for each subcategory, you have:nameThis attribute is a string that holds the subcategory name.operatorThis attribute is a string that holds the operator value.deviationThis is a float value that is used to specify the number of times the standard deviation. The rules for operator values are determined by the following conditions.greater, if condition used is > (M + deviation*SD).upper, if condition used is > (M - deviation*SD).lower, if condition used is < (M + deviation*SD).less, if condition used is < (M - deviation*SD).equal, if condition used is = value.greater num, if condition used is > value. less num, if condition used is < value.range, if condition used is > (M - deviation*SD) AND (M + deviation*SD).Mean (M) and Standard Deviation (SD) values are calculated at the category level, for each category. These values are calculated by the Segmentation SPSS model using the customer transactions data. As a user, you supply the deviation value (i.e., the number of times the standard deviation). The following example illustrates the segment definition structure.Wealth segment name: Indifferent The following sample JSON input defines these conditions:ASSETS: Bonds > (M – 1.0*SD) ; Stocks < (M + 1.0*SD). The operator value for Bonds is upper. The operator value for Stocks is lower.TRADING: Bonds > (M + 0*SD); Money Market > (M – 0.5*SD); Stocks < (M + 0.5*SD); and Others < (M - 0.5*SD). The operator value Bonds is greater. The operator value Money Market is upper. The operator value Stocks is lower. The operator value Others is less.FUNDING: Funding pattern is Not Lumpy (i.e. Lumpy = 0). There would not be any Mean or Standard Deviation calculated in case of FUNDING category. The operator value is equal and deviation value set to 0.Funding pattern is Irregular (i.e. Regular = 0). There would not be any Mean or Standard Deviation calculated in case of FUNDING category. The operator value is equal and deviation value set to 0.INTERACTION: Interaction pattern is Rare (i.e. Rare = 1). There would not be any Mean or Standard Deviation calculated in case of FUNDING category. The operator value is equal and deviation value set to 1.{ "segment": "Indifferent", "categories": [ { "name": "ASSETS", "subcategories": [ {"name": "Bonds", "operator": "upper", "deviation": 1}, {"name": "Stocks","operator": "lower", "deviation": 1} ] }, { "name": "TRADING", "subcategories": [ {"name": "Bonds", "operator": "greater", "deviation": 0}, {"name": "Money Market", "operator": "upper","deviation": 0.5}, {"name": "Stocks","operator": "lower", "deviation": 0.5}, {"name": "Others","operator": "less", "deviation": 0.5} ] }, { "name": "FUNDING", "subcategories": [ { "name": "Lumpy", "operator": "equal", "deviation": 0}, { "name": "Regular", "operator": "equal", "deviation": 0} ] }, { "name": "INTERACTION", "subcategories": [ {"name": "rare","operator": "equal", "deviation": 1} ] } ] } The Segmentation Framework REST APIs are part of the Framework Enterprise Application (IS_Framework_EAR). Once the EAR is deployed on a WebSphere Application Server, the interactive REST API documentation can be accessed from any browser at the following URL: http://<hostname>:<port>/isframework-restapi You can also create, edit, and delete custom segments using the browser interface that is available in the solution. Once the IS_Framework_EAR is deployed on a WebSphere Application Server, the interface can be accessed by navigating to the following URL: http://<hostname>:<port>/issegmentation-webportalREST API referenceThe IBM Behavior Based Client Insight for Wealth Management solution provides a set of RESTful APIs to allow you to create applications to programmatically invoke operations and extend industry solutions capabilities.

Customizing segments

The Behavioral Segmentation REST API allows you to create and delete custom segments and their associated segment definitions. The Segmentation Tool provides an interface for quickly editing or creating new segments.

For information on using the Segmentation Tool, see the topic Creating and managing customer segments.

Segment data dictionary

Segment definitions must conform to the behavioral categories defined in the segment data dictionary. All categories in the data dictionary are top-level and have a corresponding list of sub-categories. When creating a segment, you must provide conditions that define a segment at the sub-category level. The segment data dictionary for your industry solution is specified in the following table.

Table 3. Wealth data dictionary

Categories | Sub-categories
ASSETS | Bonds, Commodities, Credits, Derivatives, Estate Funds, Forex, Money Market, Stocks, Others
TRADING | Bonds, Commodities, Credits, Derivatives, Estate Funds, Forex, Money Market, Stocks, Others
FUNDING | Regular, Rare, Lumpy
INTERACTION | Rare, Frequent, Less Frequent

The categories are defined based on the customer transactions data.

ASSETS

Assets owned by the user in any of the listed sub-categories.

TRADING

Trading activity performed by the user in any of the listed sub-categories.

FUNDING

Funding pattern for the user.

INTERACTION

Interaction pattern for the user. Implies interaction with the wealth manager.

Segment definition

A segment definition is created by using any combination of these categories and the relevant sub-categories. As mentioned, conditions that define a segment are specified at the sub-category level. Some predefined segments are included in your industry solution. The REST API accepts the segment definition in the form of a JSON input string and persists it to the database. The JSON format for the segment definition is as follows:

{
    "segment": "segment_name",
    "categories": [
        {
             "name": "category_name",
             "subcategories": [
                 {"name": "subcat_name", "operator": "value", "deviation": value}, ...
               ]
         }, ...
     ]
}

segment

This attribute is a string that holds the segment name.

categories

This is an array of categories.

Within the categories array for each category, you have:

name

This attribute is a string that holds the category name.

subcategories

This is an array of subcategories.

Within the subcategories array for each subcategory, you have:

name

This attribute is a string that holds the subcategory name.

operator

This attribute is a string that holds the operator value.

deviation

This is a float value that is used to specify "the number of times the standard deviation".

The rules for operator values are determined by the following conditions.

greater, if condition used is > (M + deviation*SD).

upper, if condition used is > (M - deviation*SD).

lower, if condition used is < (M + deviation*SD).

less, if condition used is < (M - deviation*SD).

equal, if condition used is = value.

greater num, if condition used is > value.

less num, if condition used is < value.

range, if condition used is > (M - deviation*SD) AND (M + deviation*SD).

Note: Mean (M) and Standard Deviation (SD) values are calculated at the category level, for each category. These values are calculated by the Segmentation SPSS model using the customer transactions data. As a user, you supply the deviation value (i.e., the number of times the standard deviation).

The following example illustrates the segment definition structure.

Wealth segment name: Indifferent

The following sample JSON input defines these conditions:

ASSETS: Bonds > (M – 1.0*SD) ; Stocks < (M + 1.0*SD). The operator value for Bonds is upper. The operator value for Stocks is lower.

TRADING: Bonds > (M + 0*SD); Money Market > (M – 0.5*SD); Stocks < (M + 0.5*SD); and Others < (M - 0.5*SD). The operator value Bonds is greater. The operator value Money Market is upper. The operator value Stocks is lower. The operator value Others is less.

FUNDING:

Funding pattern is Not Lumpy (i.e. Lumpy = 0). There would not be any Mean or Standard Deviation calculated in case of FUNDING category. The operator value is "equal" and deviation value set to 0.

Funding pattern is Irregular (i.e. Regular = 0). There would not be any Mean or Standard Deviation calculated in case of FUNDING category. The operator value is "equal" and deviation value set to 0.

INTERACTION: Interaction pattern is "Rare" (i.e. Rare = 1). There would not be any Mean or Standard Deviation calculated in case of FUNDING category. The operator value is "equal" and deviation value set to 1.

{
    "segment": "Indifferent",
    "categories": [
        {
            "name": "ASSETS",
            "subcategories": [
                {"name": "Bonds", "operator": "upper", "deviation": 1},
                {"name": "Stocks","operator": "lower", "deviation": 1}
            ]
        },
        {
            "name": "TRADING",
            "subcategories": [
	         {"name": "Bonds", "operator": "greater", "deviation": 0},
                {"name": "Money Market", "operator": "upper","deviation": 0.5},
                {"name": "Stocks","operator": "lower", "deviation": 0.5},
	         {"name": "Others","operator": "less", "deviation": 0.5}
            ]
        },
        {
            "name": "FUNDING",
            "subcategories": [
                { "name": "Lumpy", "operator": "equal", "deviation": 0},
	         { "name": "Regular", "operator": "equal", "deviation": 0}
            ]
        },
        {
            "name": "INTERACTION",
            "subcategories": [
                {"name": "rare","operator": "equal", "deviation": 1}
            ]
        }
    ]
}

The Segmentation Framework REST APIs are part of the Framework Enterprise Application (IS_Framework_EAR). Once the EAR is deployed on a WebSphere Application Server, the interactive REST API documentation can be accessed from any browser at the following URL:

http://<hostname>:<port>/isframework-restapi

You can also create, edit, and delete custom segments using the browser interface that is available in the solution. Once the IS_Framework_EAR is deployed on a WebSphere Application Server, the interface can be accessed by navigating to the following URL:

http://<hostname>:<port>/issegmentation-webportal

Parent topic: REST API reference

NoticesThis information was developed for products and services offered worldwide.This material may be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. This document may describe products, services, or features that are not included in the Program or license entitlement that you have purchased. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Software Group Attention: Licensing 3755 Riverside Dr. Ottawa, ON K1V 1B7 Canada Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.This Software Offering does not use cookies or other technologies to collect personally identifiable information.©

Notices

This information was developed for products and services offered worldwide.

This material may be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. This document may describe products, services, or features that are not included in the Program or license entitlement that you have purchased.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law

IBM Japan Ltd.

19-21, Nihonbashi-Hakozakicho, Chuo-ku

Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Software Group

Attention: Licensing

3755 Riverside Dr.

Ottawa, ON

K1V 1B7

Canada

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

This Software Offering does not use cookies or other technologies to collect personally identifiable information.

©

© Product Information This document applies to IBM Industry Customer Intelligence Solutions Version 1.0.0 and may also apply to subsequent releases. Copyright Licensed Materials - Property of IBM © Copyright IBM Corp. 2015, 2016. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. Notices

©

Product Information

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

Copyright

Licensed Materials - Property of IBM

© Copyright IBM Corp. 2015, 2016.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM, the IBM logo and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at " Copyright and trademark information " at www.ibm.com/legal/copytrade.shtml.

Parent topic: Notices