Capstone Origination Suite: Decision Accelerator

Capstone Decision Accelerator Administrator’s Guide
ADMINISTRATOR’S
GUIDE
FA I R I S A A C E N T E R P R I S E O R I G I N AT I O N S O L U T I O N S
2.0 Capstone® Origination Suite
Decision Accelerator
This document is the confidential, unpublished property of Fair Isaac Corporation. Receipt or possession
of it does not convey rights to divulge, reproduce, use, or allow others to use it except as expressly
provided in the license agreement between user and Fair Isaac Corporation.
The information in this document is subject to change without notice. If you find any problems in this
documentation, please report them to us in writing. Fair Isaac Corporation does not warrant that this
documentation is error-free, nor are there any other warranties with respect to the documentation except
as may be provided in the license agreement.
© 2006 - 2008 Fair Isaac Corporation. All rights reserved.
Fair Isaac, FICO, FICO Expansion, Capstone, and Blaze Advisor are trademarks or registered
trademarks of Fair Isaac Corporation in the United States and may be trademarks or registered
trademarks of Fair Isaac Corporation in other countries. Other product and company names herein may
be trademarks of their respective owners.
Document Revision A
Last Revised July 10, 2008
Version 2.0
Template LG5.2
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About Capstone Decision Accelerator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Conventions Used in this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Contacting Fair Isaac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Related Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Technical Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
About Fair Isaac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
CHAPTER 1
Decision Accelerator Administration Overview . . . . . . . . . . . 9
Capstone Origination Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Decision Accelerator System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Using Decision Accelerator with Intelligent Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
License Renewals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing License Keys for Blaze Advisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installing License Keys for the SMW and Process Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Administrative Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
CHAPTER 2
Managing User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
User Administration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Pre‐defined User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Installed User IDs and Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Adding Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Creating Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Adding New Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Retaining Authentication and Authorization Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Custom Authentication and Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Reverting to Default Authentication and Authorization Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Disabling Authentication and Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
CHAPTER 3
Managing Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
The Configuration Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Promoting Strategy Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Creating Additional Configuration Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
The Data Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Fair Isaac Confidential and Proprietary Information 3

Contents
Reporting Needs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Score Model Baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Score Model Bin Baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Importing Final Application Decision and Final Offer History Data . . . . . . . . . . . . . . . . . . 38
Purging Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
The Testing Data Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
CHAPTER 4
Managing the Data Storage Service . . . . . . . . . . . . . . . . . . 41
Data Storage Service Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Setting Up the DSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
CHAPTER 5
Decision Accelerator Reports. . . . . . . . . . . . . . . . . . . . . . . . 47
Reports Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Reports and the Data Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Score Model Development Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Final Application Decision and Final Offer History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Exporting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Report Tree Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
CHAPTER 6
Extracting Data for Testing Strategies . . . . . . . . . . . . . . . . 55
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Using the STF to Extract Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
The STF Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Extracting Simulation Data from the DSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
AP PEN DI X A
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Decision Accelerator Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Log File Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
What To Do Before You Contact Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Gather Relevant Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4 Fair Isaac Confidential and Proprietary Information

Preface
Welcome to the Capstone Decision Accelerator Administrator’s Guide, a guide to help

administrators manage Capstone® Origination Suite Decision Accelerator, a Web‐based
application decisioning solution. Capstone Decision Accelerator enables you to manage
complex decisioning strategies and automatically decision credit applications using
advanced rules management technology.
About Capstone Decision Accelerator

Capstone Decision Accelerator is an originations product built upon Fair Isaac’s
Enterprise Decision Management technology platform. Specifically designed for new
account originations, Decision Accelerator is ideal for building and maintaining the
policies, practices, and procedures that define the complex business strategies found in
the originations process. Decision Accelerator leverages the full power of Fair Isaac
Blaze Advisor™ to provide companies with proven rules management technology that
supports the entire process for designing, building, and maintaining rules‐based
decision applications. Decision Accelerator is a core component of Fair Isaac’s
Enterprise Origination Solutions, which includes Capstone Intelligent Data Manager, a
robust data acquisition and communications management software application.
Fair Isaac’s origination solutions help financial institutions, telecommunications
carriers, and insurance companies efficiently target and obtain ideal customers while
compressing decision cycles and reducing application processing costs. Decision
Accelerator offers state‐of‐the‐art multi‐platform services that can augment or replace
current processes, depending on business needs. Decision Accelerator includes a
Strategy Management Workstation that allows business users to develop originations
strategies by creating and maintaining lending products through product strategies,
decision flows, rulesets, score models, scenarios, decision trees and decision tables. Combined,
these components allow credit grantors to realize greater profitability by booking more
loans, cutting losses, and reducing operational costs and delays through the
deployment of consistent strategies and leading predictive analytics.

Preface
Conventions Used in this Guide

To help you find and understand the information in this guide, we have used some
standard text formats and symbols to visually convey special information. The
following conventions are used throughout this guide.
Convention Item Examples

Italic Placeholders for information Replace username with your own
that you supply name.
New, glossary, or emphasized Categorical fields are
terms non-numeric.
The value is not returned in test
mode.
Bold Menu names and commands Choose File > Open.
on menus
Buttons Click OK.
Fields Enter the name in the Label box.
Monospace Text that you need to enter In the Minimum Observations
box, enter 3600.
Code HRESULT
AddProjectToService ([in] BSTR
User);
Related Documentation
Capstone Decision Accelerator users may find the following documentation useful:
Capstone Decision Accelerator Installation Guide
Capstone Decision Accelerator Getting Started Guide
Capstone Decision Accelerator User’s Guide
Capstone Decision Accelerator Developer’s Guide
Capstone Decision Accelerator Supported Platforms Guide
Capstone Decision Accelerator Release Notes
Capstone Decision Accelerator Strategy Management Workstation Help
Blaze Advisor’s Developing Rule Maintenance Applications
Capstone Intelligent Data Manager documentation, if this
Capstone Origination Suite module was purchased

Capstone Origination Suite
Decision Accelerator Administrator’s Guide
Contacting Fair Isaac

Fair Isaac offers technical support and services ranging from self‐help tools to direct
assistance from a Fair Isaac technical support engineer.
Product Support
Support is available to all clients who have purchased a Fair Isaac product and have an
active support or maintenance contract. To expedite the resolution of your problem,
please provide the following information:
Your client ID or license number
Your name, phone number, and email address or fax number
The software product to which the problem pertains
A description of the problem
As much information as possible about your operating system, environment, and
the conditions under which the problem occurred
For support on any Fair Isaac product, use one of the following methods to contact
Fair Isaac.
Email
Put the product name in the Subject line of any email you send to Fair Isaac Product
Support at support@fairisaac.com.
Telephone
Asia‐Pacific, Latin America, and the Caribbean: +1 (415) 446‐6185.
Europe, Middle‐East, and Africa: +44 (0)870‐420‐3777.
South Africa (toll free): 0800‐996‐153.
UK (toll free): 0800‐0152‐153.
US and Canada (toll free): 1 (877) 4FI‐SUPP (1‐877‐434‐7877).
Internet
Find support information by going to http://www.fairisaac.com/support.
Related Services
Consulting: A Fair Isaac Consulting representative may be assigned to work with you
throughout your implementation. Their services may include project management,
system customization, instruction on the system, and technical support during the
implementation and testing process. These services may be arranged by contract. For
information, contact your Fair Isaac account representative.
Strategy Consulting: Fair Isaac offers consulting services to assist you in using

Decision Accelerator to meet your business needs. These services may be arranged by
contract. For information, contact your Fair Isaac account representative.

Preface
Conferences and Seminars: Fair Isaac offers conferences and seminars on our

products and services. For announcements concerning these events, go to http://
www.fairisaac.com or contact your Fair Isaac account representative.
Technical Publications
Fair Isaac continually looks for new ways to improve and enhance the value of the
products and services we provide. If you have comments or suggestions regarding how
we can improve this documentation, please let us know by sending your suggestions to
techpubs@fairisaac.com.
About Fair Isaac

Fair Isaac Corporation (NYSE:FIC) makes decisions smarter. The company’s solutions
and technologies for Enterprise Decision Management give businesses the power to
automate more processes, and apply more intelligence to every customer interaction.
Through increasing the precision, consistency, and agility of their decisions, Fair Isaac
clients worldwide increase sales, build customer value, cut fraud losses, manage credit
risk, reduce operational costs, meet changing compliance demands, and enter new
markets more profitably. Founded in 1956, Fair Isaac powers hundreds of billions of
decisions a year in financial services, insurance, telecommunications, retail, consumer
branded goods, healthcare, and the public sector. Fair Isaac also helps millions of
individuals manage their credit health through the www.myfico.com Web site. Visit
Fair Isaac online at www.fairisaac.com.

CHAPTER 1
Decision Accelerator Administration

Overview
This chapter provides an overview of Decision Accelerator and tasks typically assigned
to administrators. The following topics are included:
Decision Accelerator System Overview
Using Decision Accelerator with Intelligent Data Manager
License Renewals
Administrative Tasks

CHAPTER 1: Decision Accelerator Administration Overview

The Capstone Origination Suite is a multi‐product origination system designed to meet
your credit application decisioning needs.
At this time, the Capstone Origination Suite consists of two products:

Capstone Decision Accelerator—A comprehensive rules and decision management
system designed specifically for new account originations
Capstone Intelligent Data Manager—An advanced connectivity and data
management system that provides pre‐developed interfaces to US and Canadian
consumer credit reporting agencies (CRAs), business bureaus, Equifax Commercial
Solutions, and to the FICO® Expansion score service, and may be extended to access
other data providers
Each component functions as a stand‐alone product; however, used together, Decision
Accelerator and Intelligent Data Manager provide a unified solution to your business
needs.
Decision Accelerator System Overview

Decision Accelerator provides a decision (for example, approve, decline, investigate) for
each credit application that is processed through the Capstone Process Server. Application
data is passed from a calling application to Decision Accelerator in input XML
documents. Decision Accelerator returns the application data, including decisions and
reasons, to the calling application in output XML documents. All application data is
returned as part of the output XML document. It can also be saved into a data repository
for use in testing and report generation.
Information about your institution’s products and strategies is stored in a configuration
repository. In order to provide a decision for each credit application, Decision
Accelerator refers to product strategies in the configuration repository and processes
each application according to these strategies. Your institution’s risk management
analysts use the Strategy Management Workstation (SMW) to set up credit products
based on your institution’s business policies.
As administrator, you work directly with the Strategy Testing Facility (STF), the Report
Viewer, and the Capstone Data Storage Service (DSS). You also control user access to
Decision Accelerator components and manage the three Decision Accelerator
repositories—the data repository, configuration repository, and testing data repository.
Figure 1 provides an example of a typical Decision Accelerator system, set up in a Web
service environment. Note that different configurations are possible. For example, the
SMW and Process Server can be hosted on separate application servers if desired. The
STF and an associated test data repository is installed on the Process Server/SMW host
by default, but can be installed on the client host if desired (as shown in Figure 1 on
page 11).

Client Host Process Server/SMW Host
Testing Data Data

Repository Repository
Data Storage
Report Viewer
Web Service
Strategy Testing Process Server

Facility Web Service
SMW
Web Application
DA Web Server
System
Administrator/
Risk Management Web Browser
Analyst
Configuration
Repository
Calling Application Host
Calling
Application
External
Interfaces
Figure 1: Physical view of the Decision Accelerator system in a Web service environment
It may be desirable to incorporate multiple repositories under certain circumstances.
For example, if your Decision Accelerator installation hosts multiple clients, and each
client requires physically separate configuration repositories for security purposes,
setting up separate repositories will ensure that Client 1 and Client 2 cannot access
other’s configurations. You may also decide to have multiple repositories for optimal
system performance or for testing purposes. It is expected that your institution will set
up a configuration repository in two or more environments: a production environment
and one or more development and test environments.
Figure 2 on page 12 shows an example of a Decision Accelerator system with multiple
configuration repositories. Each repository has a corresponding SMW Web application.
A single DSS can handle multiple repositories without any additional configuration.
Generating additional repositories is discussed in Chapter 3, “Managing Repositories.”

Process Server/SMW Host
Data
Repository
DA Web Server
Report Viewer
Client Host 1 Client Host 2
Data Storage
Testing Data Web Service Testing Data
Strategy Testing Process Server Strategy Testing

Facility Web Service Facility
Admin/ SMW SMW Admin/

Web Browser Web Browser
Analyst Web Application 1 Web Application 2 Analyst
Configuration Configuration
Repository 1 Repository 2
Calling Application
External
Interfaces
Figure 2: Example of a Decision Accelerator system with multiple repositories

Using Decision Accelerator with Intelligent Data

Manager
If your institution has purchased Intelligent Data Manager to pull data from external data
sources for Decision Accelerator, you may be tasked with maintaining Intelligent Data
Manager components. If desired, Decision Accelerator and Intelligent Data Manager
can be configured to use Decision Accelerator’s DSS, Report Viewer, and data
repository. For example, Intelligent Data Manager could access the data repository and
Report Viewer shown in Figure 1 in order to produce Intelligent Data Manager system
reports.
Each installation of a Capstone Origination Suite product has a separate system ID.

Based on the system ID, the Process Server determines which repository goes with the
system and which stateless server to invoke.
Figure 3 on page 14 shows a typical installation of Decision Accelerator using Intelligent
Data Manager.

Testing Data Data

Data Storage
Report Viewer
Web Service

SMW Application
DA Web Server
System
Administrator/
Analyst Configuration
Repository
Calling
Application
External
Interfaces
IDM Server Host
Dataflow
Dataflow Manager
Configuration
Web Service
Workstation
Configuration Message
Repository DB
Connection Connection
Application Configuration Manager
Administrator Workstation Web Service
Microsoft IIS
External Data Sources
Figure 3: Physical view of a system using Decision Accelerator and Intelligent Data Manager in a Web service environment
See Also For information about processing applications using Decision Accelerator

and Intelligent Data Manager, see the Capstone Decision Accelerator Developer’s Guide.

License Renewals
Valid Decision Accelerator development and deployment license keys are required at
the time of installation. The license keys expire periodically and must be promptly
renewed and installed in order to avoid disruption of service. When you need to renew
your license keys, contact fulfillment@fairisaac.com and request a renewal. When
contacting Fair Isaac Product Fulfillment, put “Decision Accelerator” in the subject line
along with the word “Fulfillment”, and include the name of your organization in the
body of the email.
After the renewed license keys are received, they must be installed in Blaze Advisor
folders, then installed for each SMW and for the Process Server.
Installing License Keys for Blaze Advisor

When installing license keys in Blaze Advisor, use your Decision Accelerator license
keys as the Blaze Advisor license keys. For Windows installation, you can use the Blaze
Advisor Update License utility. If you have installed Blaze Advisor through a Decision
Accelerator installation, the license key file will be in the following folder:
C:\fairisaac\EOS\Blaze\license\com\blazesoft\licenseKeys\keys.properties
Follow the instructions below for the operating system on which Blaze Advisor is
installed.
Note For UNIX installations, the installation must be initiated from an X Windows
terminal emulator program (xterm) running in a UNIX shell.
To update the Blaze Advisor license keys in Windows

1 Choose Start > Programs > Blaze Advisor 6.5 > Update License.
2 Enter license keys for Blaze Advisor Development and Blaze Advisor Deployment
in the fields provided
3 Click Apply, then click OK.
To update the Blaze Advisor license keys in UNIX

1 Go to the bin subdirectory in your Blaze Advisor directory, then enter:
installLicense.sh
This starts up a small utility that you can use to update your licenses.
2 In the utility, enter license keys for Blaze Advisor Development and Blaze Advisor
Deployment in the fields provided.
3 Click Apply, then click OK.
See Also For more information on installing license keys for Blaze Advisor, see the

Blaze Advisor Installation and Setup document.

Installing License Keys for the SMW and Process Server

Follow the instructions below for your deployment type.
To install renewed license keys for a Decision Accelerator Web service

deployment using Tomcat
1 Install the license key for each SMW.
If you have only one SMW Web application and the default location was used when
Decision Accelerator was installed, the license key needs to be installed in the
following folder:
‐ For Windows:
C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps\
SMW.<sysid>\WEB-INF\classes\com\blazesoft\licenseKeys\
keys.properties
(where <sysid> is the system ID used when Decision Accelerator was installed)
‐ For UNIX:
<TomcatPath>/webapps/SMW.<sysid>/WEB INF/classes/com/blazesoft/
licenseKeys/keys.properties
where <sysid> is the system ID used when Decision Accelerator was installed.
2 Install the license key for the Process Server.
Assuming the default location was used when Decision Accelerator was installed,
the license key needs to be installed in the following folder:
‐ For Windows:
C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps\
ps\WEB-INF\classes\com\blazesoft\licenseKeys\keys.properties
‐ For UNIX:
<TomcatPath>/webapps/ps/WEB-INF/classes/com/blazesoft/licenseKeys/
keys.properties
To install renewed license keys for a Decision Accelerator deployment using

WebSphere (EJB or Web service)
X Install the license key for each SMW.
Assuming the default location was used when Decision Accelerator was installed,
the license key needs to be installed in the following folder:
‐ For Windows:
C:\Program Files\WebSphere\AppServer\installedApps\<ServerName>\
Strategy Management Workstation sysid.ear\SMW.sysid.war\WEB-INF\
classes\com\blazesoft\licenseKeys
‐ For UNIX:
<WSRoot>/WebSphere/AppServer/installedApps/<ServerName>/Strategy
Management Workstation sysid.ear/SMW.sysid.war/WEB-INF/classes/com/
blazesoft/licenseKeys
Note There is no need to install a license key specifically for the Process Server when
using WebSphere. Installing the renewed license keys in Blaze Advisor and installing
the license keys for the SMW is all that is required.

Administrative Tasks
As administrator, you work directly with the following Decision Accelerator
components:
Strategy Testing Facility (STF)
Report Viewer
Data Storage Service (DSS)
Decision Accelerator repositories
In addition, you manage user access to the Decision Accelerator system, and ensure that
licenses are promptly renewed.
This guide provides information for tasks typically assigned to Decision Accelerator
administrators:
Chapter 2, “Managing User Access,” discusses Decision Accelerator authentication
and authorization files and setting up new users.
Chapter 3, “Managing Repositories,” discusses the three Decision Accelerator
repositories—the data repository, configuration repository, and testing data
repository—and maintenance tasks such as generating additional repositories,
migrating strategy changes to production, and inserting baseline score information in
score model baseline tables.
Chapter 4, “Managing the Data Storage Service,” describes the DSS and configuring
DSS parameters.
Chapter 5, “Decision Accelerator Reports,” describes how to generate Decision
Accelerator reports.
Chapter 6, “Extracting Data for Testing Strategies,” provides information on using
the STF to extract testing data from the data repository for testing purposes.
Appendix A, “Troubleshooting,” provides information on troubleshooting and
contacting Product Support if necessary.
The Glossary contains a list of common Decision Accelerator terms.
You may also wish to consult the Capstone Decision Accelerator Developer’s Guide for
detailed information on XML transaction processing, and the Capstone Decision
Accelerator User’s Guide for information on using the SMW to set up business policies.


CHAPTER 2
Managing User Access
This chapter includes the following sections:
User Administration Overview
Adding Users
Creating Passwords
Adding New Roles
Retaining Authentication and Authorization Changes
Custom Authentication and Authorization
Reverting to Default Authentication and Authorization Settings
Disabling Authentication and Authorization

CHAPTER 2: Managing User Access
User Administration Overview

When you install Decision Accelerator, authentication and authorization is enabled, and
users cannot connect to the SMW without supplying a valid user ID and optional
password. The Report Viewer, which is accessed through the SMW, requires a valid
user ID with reporting permissions. The user ID is used by the versioning service to
keep track of which users make which changes to components within the SMW.
Each SMW user is assigned to a “role,” which determines the repository object (or
multiple objects) the user can access. This allows the system administrator to grant users
only those permissions required to perform their duties.
As administrator, you can add new users, add and change passwords, and assign users
to roles. Authentication and authorization is maintained using authentication.xml
and authorization.xml files. Each configuration repository has its own
authentication.xml and authorization.xml file, stored in the repository’s home folder
(for example, C:\FairIsaac\EOS\DA\data\BlazeRepository.sysid). These files are
manually edited using a text editor or XML editor (such as Altova XMLSpy).
Important Ensure that you edit the correct authentication.xml and
authorization.xml files.
Pre-defined User Roles

Decision Accelerator includes the following pre‐defined user roles:
admin—Full read/write access to all SMW screens.
reports—Full read/write access to the Report Viewer.
group1—Read‐only access to all SMW screens.
A “system” role is also included, but this role is for Fair Isaac’s internal purposes only.
Installed User IDs and Passwords

Decision Accelerator installation sets up three users. Table 1 lists information about
these users. User IDs and passwords are case‐sensitive.
Table 1: Default Users and Passwords

User ID Password Role(s) Access
admin admin admin, reports read-write
guest1 [none] group1 read-only
guest2 [none] group1 read-only
You can control access to Decision Accelerator by assigning users to certain roles. For
example, to give users permission to view SMW screens without making any
modifications, assign them to group1.

Adding Users
If you are using Decision Accelerator in a multi‐user environment, it is recommended
you immediately create an administrative user whose ID is known only to the user
administrator.
To administer user IDs, passwords and roles, you must manually edit the
authentication.xml file, which is stored in the root of each system’s repository folder.
This XML document can be edited using any text editor or XML editor (for example,
Altova XMLSpy).
<Authentication>
<Roles>
<Role roleId="admin" description=""/>
<Role roleId="group1" description=""/>
<Role roleId="system" description=""/>
<Role roleId="reports" description="Users in this role will be able to view DA
Reports"/>
</Roles>
<Users>
<User userId="admin"
password="%21%23%2F%29zW%C2%A5%C2%A7C%E2%80%B0J%0EJ%E2%82%AC%1F%C3%83"
firstName="" lastName="" email=""/>

<User userId="guest1" password="" firstName="" lastName="" email=""/>
<User userId="system" password="" firstName="" lastName="" email=""/>
</Users>
<UserRoles>
<UserRole roleId="admin" userId="admin"/>
<UserRole roleId="reports" userId="admin"/>
<UserRole roleId="group1" userId="guest1"/>
<UserRole roleId="group1" userId="guest2"/>
<UserRole roleId="system" userId="system"/>
</UserRoles>
</Authentication>
Figure 4: The authentication.xml file with default user IDs and passwords
To add a user, first create a new user record for the user by assigning a user ID and user
role, then assign a password to the user. When creating a new user ID and user role, it is
easiest to copy existing records, then modify them for the new user.
To create a new user

1 Using a text editor or XML editor, open the authentication.xml file for the config‐
uration repository that the user needs to access. The authentication.xml file is
located in the repository’s home folder, for example:
In Windows, C:\FairIsaac\EOS\DA\data\BlazeRepository.sysid
In UNIX, <EOSpath>/FairIsaac/EOS/DA/data/BlazeRepository.sysid
2 Locate an existing user record and copy it. User records are located in the Users
section of the authentication.xml file and look like the following:
3 In the new record, replace the copy’s userId attribute with the new user’s ID.

4 Optionally, change the firstName, lastName, and email attributes. These three
attributes are used for your own identification purposes only; they are not used for
authentication.
5 Locate an existing user role record with the role you want to assign the new user,
then copy it, and paste it into the list of user role records. User role assignments are
located in the UserRoles section of the authentication.xml file.and look like the
following:
<UserRole userId="guest1" roleId="group1"/>
See Also For information on the roles that are already set up in Decision

Accelerator, see “Pre‐defined User Roles” on page 20.
6 In the new record, replace the copy’s UserId attribute with the new user’s ID.
See the following section for creating passwords for new users.
Creating Passwords
Creating passwords for new users is repository‐specific. Be sure you follow the
instructions below for each repository the user will access. The procedure differs
depending on which operating system you are using, Windows or UNIX. For Windows,
see “To create a password for a user on Windows.” For UNIX, see “To create a
password for a user on UNIX.”
Note The pre‐configured admin password in the authentication.xml file shipped

with Decision Accelerator is not valid for installations on Solaris operating systems. For
a description of the steps that must be taken to ensure the installation is successful on
Solaris, see the Capstone Decision Accelerator Release Notes.
To create a password for a user on Windows

1 Open a Windows command prompt window and type the following command,
then press Enter:
cd c:\fairisaac\EOS\DA\data\BlazeRepository.<sysid>
(where <sysid> is the name of the repository where the password will be set)
2 Run the GeneratePassword batch file and specify the password as a parameter by
typing the following, then press Enter. Note that the batch file name is not case‐
sensitive; however, the password itself is case‐sensitive.
GeneratePassword.bat password
(where “password” is the password you are assigning)
The result of the GeneratePassword batch file is an unreadable string.
3 Once the unreadable string is displayed, use the Mark and Copy commands from the
command prompt window to copy the string to the clipboard.
4 Paste the unreadable string from the clipboard into the password attribute of the
new user’s record in the authentication.xml file for this repository, for example:
<User userId=MyName password="_M%CC%3BZ%A7e%D6%1D%83%27%DE%B8%82%CF%99"
... />
5 Save and close the authentication.xml file.

To create a password for a user on UNIX

1 Navigate to the following directory:
<EOSPath>/fairisaac/EOS/DA/data/BlazeRepository.<sysid>
(where <EOSPath> is your installation path to the fairisaac directory,
and <sysid> is the name of the repository where the password will be set)
2 Run the GeneratePassword.sh file and specify the password as a parameter by
typing the following, then press Enter. Note that the password is case‐sensitive.
GeneratePassword.sh password
(where “password” is the password you are assigning)
The result of the GeneratePassword file is an unreadable string.
3 Copy and paste the unreadable string into the password attribute of the new user’s
record in the authentication.xml file for this repository, for example:
<User userId=MyName password="_M%CC%3BZ%A7e%D6%1D%83%27%DE%B8%82%CF%99"
... />
4 Save and close the authentication.xml file.
Adding New Roles

The pre‐defined roles provide basic authorization controls that are suitable for most
situations; however, authorization allows roles to be created with very specific access to
very specific repository objects.
Note Because there is a high probability that creating roles manually may lead to
errors, it is recommended that all users be assigned one of the installed roles. However,
administrators requiring more fine‐grained authorization control can create a new role
by copying a record in the Roles section of authentication.xml and replacing the
roleId attribute. Then the new role must be defined by creating a record for it in the
authorization.xml file in the system’s repository folder.
Retaining Authentication and Authorization

Changes
Edited authentication.xml and authorization.xml files are overwritten whenever the
automated Decision Accelerator installation is run. To avoid losing any changes you
have made to these files, when you re‐install, copy the changes (or the entire repository)
from their install folder to another location, and then paste them back into the install
folder after the reinstallation.
Custom Authentication and Authorization

Decision Accelerator supports custom authentication and authorization mechanisms. If
you would like to implement your own authentication or authorization mechanism,
please contact Fair Isaac Product Support or Fair Isaac Consulting.

Reverting to Default Authentication and

Authorization Settings
If you encounter errors upon editing the authentication.xml or authorization.xml
files located in the Blaze Advisor installation folder, you can refer to extra copies of
these files to obtain the original settings. The extra files are located in
C:\FairIsaac\EOS\DA\data\Advisor65_Support\Advisor_Home (on Windows) or
<EOSpath>/FairIsaac/EOS/DA/data/Advisor65_Support/Advisor_Home (on UNIX).
Disabling Authentication and Authorization

Administrators should not disable authentication and authorization; however, if it does
become necessary to do so, authentication and authorization can be disabled by editing
the repository configuration file com_blazesoft_repository_config.cfg in the
repository’s root directory.
The repository configuration file is an XML/text file that can be edited with any text or
XML editor. To disable authentication and authorization but keep versioning enabled,
remove these three lines from the repository configuration file.
<RepositoryAuthorizationManagerFactory>
<JavaName> com.fairisaac.eos.da.security... </JavaName>
</RepositoryAuthorizationManagerFactory>

CHAPTER 3
Managing Repositories
Overview
The Configuration Repository
The Data Repository
The Testing Data Repository

CHAPTER 3: Managing Repositories
Overview
There are three types of Decision Accelerator repositories (databases):
The configuration repository, which stores business strategies. The SMW writes to
the configuration repository at design time. Typically there are at least two
configuration repositories, one residing in a development environment and one
residing in a production environment. In this situation, the Process Server refers to
the repository in the development environment when processing test applications,
and refers to the data in the production configuration repository when processing
“real” applications.
The data repository, which stores transaction data. The Data Storage Service (DSS)
writes transaction data to the data repository, where the data is available for report
generation and testing.
The testing data repository, which stores transaction data that the Strategy Testing
Facility (STF) has obtained from the data repository, plus other test files that were
generated manually. This data is used for testing business strategies.
Figure 5 on page 27 provides an example of a Decision Accelerator system, set up in a
Web service environment.

Testing Data Data

Data Storage
Report Viewer
Web Service

SMW
Web Application
DA Web Server
System
Administrator/
Analyst
Configuration
Repository
Calling
Application
External
Interfaces
Figure 5: Physical view of the Decision Accelerator system in a Web service environment
Managing the Decision Accelerator repositories includes the following tasks:
Migrating strategies from the development configuration repository to the
production server. This should be done after strategies are created and tested in the
development environment.
Revising reason codes and associated message text to include meaningful
explanations. Optionally, Decision Accelerator can provide scoring reason codes
and message text in transaction data. If desired, you may replace the default values
so that at design time, risk management analysts can select from a list of reasons
with meaningful text, rather than generic codes.
Specifying score model baselines in tables residing in the data repository. Certain
reports, such as the Population Stability Report, require this information in order to
be generated properly.
Ensuring that final application decision data and final offer history data is available
in the data repository, if necessary. This data must be imported from your front‐end
application processing system. Certain reports, such as the System Decision
Analysis Report, require this data in order to be generated properly.

Creating additional configuration repositories. Each configuration repository is
paired with an SMW Web application. Your institution may wish to create multiple
repositories for testing purposes, or for optimal system performance, or to
accommodate multiple clients. Note that a single DSS can handle multiple
repositories without any additional configuration.
The Configuration Repository

Administrators may be charged with the following tasks regarding the configuration
repository:
Promoting strategy changes that have been created or modified in the development
environment into the production environment.
Modifying score model reason codes.
Generating additional configuration repositories.
Promoting Strategy Changes

Strategy changes need to be promoted so that applications can be processed using the
revised strategies. The strategies are stored in the configuration repository, which is
accessed by the Process Server when applications are processed. In addition to initial
deployment, each time strategies are updated, the updates need to be promoted to the
production repository.
Typically, risk management analysts create and modify strategies on a development
server. The strategies are promoted to the production server after they have been tested.
This means there are at least two Decision Accelerator configuration repositories. Figure
6 on page 29 illustrates how, in Web service deployment, changes are made in the SMW,
which accesses the SMW Web application on the SMW/Process Server host machine in a
development environment. After testing, the repository changes are promoted to
production.

Development Production
Decision Decision
Process Server Process Server
Accelerator Accelerator
Web Service Web Service
Rule Service Rule Service
Decision Decision
.Server .Server
Config File Config File
SMW Web Configuration Configuration

Application Update Repository Promote Repository Repository
Repository Changes
SMW/Process Server Host Process Server Host
Figure 6: Updating and promoting strategies to production for Web service deployment
Figure 7 illustrates the same process for EJB deployment.
Development Production
Decision Decision
Process Server Process Server
EJB EJB
Rule Service Rule Service
Decision Decision
.Server .Server
Config File Config File
SMW Web Configuration Configuration

Application Update Repository Promote Repository Repository
Repository Changes
SMW/Process Server Host Process Server Host
Figure 7: Updating and promoting strategies to production for EJB deployment

Strategies are promoted to the production server by copying the entire configuration
repository located in the development server and pasting it into the production server.
Figure 8 on page 31 shows a sample repository structure, which may include the
following folders:
BlazeRepository.<sysid>—The root configuration repository folder, for the
repository whose name is <sysid>.
authoring—The parent folder for component‐specific folders.
categories—The parent folder for all category‐specific folders.
bobcat—An example of a product category‐specific folder.
_Items for_bobprod—An example of a product‐specific folder.
configuration.sys—The parent folder for all component‐specific parent folders.
datamethod.sys—An example of a component‐specific folder; in this case, where
all data methods are stored.
Important The repository files must be modified using the SMW. Directly modifying
the contents of any repository file may result in the complete failure of the Process
Server and may also prevent the SMW from attaching to it, thus rendering your
repository useless.

Figure 8: Sample repository folder structure
To promote changes to the production server

To promote changes to the repository in production, manually copy the updated
repository files in the development environment and paste them into the production
environment. The entire BlazeRepository.<sysid> folder must be copied and pasted
when promoting repository changes.
After copying the repository files to production, do one of the following, depending on
your Decision Accelerator deployment:
Restart the Process Server stateless session bean application within the WebSphere
application server, or restart WebSphere itself.
Restart the Process Server Web application within the Tomcat Web server, or restart
Tomcat itself.
It is recommended that you do this during off hours.
Note If you have a cluster of servers, you must copy the updated repository files to
every server and restart every server.

Creating Additional Configuration Repositories

If desired, you can create multiple configuration repositories. Additional configuration
repositories and SMW Web applications are generated together. In certain situations
you may want to create additional configuration repositories, for example if you need to
accommodate multiple clients and want to keep their configuration repositories
physically separate.
Note Decision Accelerator must be completely installed before you can create a
secondary configuration repository and SMW Web application pair.
To generate an additional configuration repository and SMW Web application

1 Open a command prompt and navigate to C:\FairIsaac\EOS (Windows) or <EOS-
Path>/FairIsaac/EOS (UNIX; where <EOSPath> is your installation path to the
FairIsaac directory).
2 For Windows, open the build.properties file, which is located in
C:\FairIsaac\EOS and do the following (this step is not needed for UNIX
installations):
a For Tomcat: Remove any value that appears after the websphere_home =
setting. Then, in the lib directories section, verify that the value
${websphere_home}/lib does not appear after dir2.lib. If this is shown,
remove “${websphere_home}/lib”.
b Verify that the tomcat_port is set to the correct port (for example, tomcat_port
=8080).
c Change the versionmanager.key property to read:
versionmanager.key =kxksrisgtestjasdjlhu
d Change the versionmanager.value property to read:
versionmanager.value =thegang
e If using the DSS, set the dss_dialect to the value appropriate for your database
type:
‐ For MySQL:
com.hnc.capstone.persistence.dialects.MySQLDialect
‐ For SQL Server:
com.hnc.capstone.persistence.dialects.SQLServerDialect
‐ For Oracle:
com.hnc.capstone.persistence.dialects.OracleDialect
f If using the DSS, set the dss_driver to the appropriate value for your database
type:
‐ For MySQL:
com.mysql.jdbc.driver

‐ For SQL Server:
com.microsoft.sqlserver.jdbc.SQLServerDriver
‐ For Oracle:
oracle.jdbc.driver.OracleDriver
g If using the DSS, for the dss_db_url, use the appropriate URL for the selected
database type:
‐ For MySQL:
jdbc:mysql://localhost/da1_2
‐ For SQL Server:
jdbc:sqlserver://localhost:1433;databaseName=da1_2
‐ For Oracle:
jdbc:oracle:thin:@localhost:1521:da1_2
h If using the DSS, set dss_userid and dss_pass to a valid database user ID and
password.
i Save and close the build.properties file.
Important Omitting the ‐D portion may have a disastrous effect. You should back
up your repository before attempting step 3.
3 Type the following command, then press Enter:
ant genrma –Dsystem_id=<system ID>
where <system ID> is the system ID of the new system to be created. For example:
ant genrma –Dsystem_id=test
Important If you type the comment “ant genrma” without the “–D” portion, it will
use the default value for system ID (“sysid”); if you already have a repository using
the default name, it will be destroyed.
A new versioned configuration repository, BlazeRepository.<system ID>, will be
created along with a new SMW.war file, named SMW.<system ID>.war.
4 Manually deploy the SMW.war file to the Web application server using the server’s
management utility. (Refer to your server’s documentation for instructions.)
Reason Codes
When business analysts set up score models in the SMW, they set up a rule condition for
each characteristic bin. They may set up score models so that for each rule representing
a bin, a reason code is returned if the rule fires. Reason codes can provide users with
meaningful reasons why a particular score was assigned. Decision Accelerator comes
with predefined reason codes (RC00‐RC99) and associated message text (MESSAGE00‐
MESSAGE99). In order to make the codes more meaningful to your institution, you can
replace the numeric codes with names for the reasons, and add meaningful message
text.

To modify reason codes and add corresponding message text, you must use Blaze
Advisor’s Builder. Score model reasons are defined in the Score Model Reasons
Template, which is located in the configuration repository (named
BlazeRepository.<system id>).
Figure 9: Navigating to the Score Model Reasons Template in Blaze Advisor
To modify reason codes and message text

1 Open Blaze Advisor.
2 Choose File > Connect to Repository > New.
3 Choose File Repository (BVS shared workspace).
4 Enter a name for the repository connection and click OK.
5 Navigate to C:\FairIsaac\EOS\DA\data (Windows) or <EOSPath>/FairIsaac/EOS/
DA/data (UNIX) and select BlazeRepository.<sysid>, (where <sysid> is the system ID
of the Decision Accelerator configuration repository).
6 Enter your user ID and password and click OK. The BlazeRepository folder should
open in the Repository tab of the Explorer panel.
7 Open the project folder. Choose File > Open Project > EOS and click OK.

8 In the Project tab of the Explorer pane, navigate to Design > ScoreModel > Score

Model Reasons Template > DA_Reason_Code_List.
9 Double‐click DA_Reason_Code_List. All of the reason codes will appear in the right
pane.
Figure 10: The DA_Reason_Code_List table in Blaze Advisor
10 For each Name, Code, and Message you wish to change, click in the text box and
revise the text as desired.
11 When you are finished with the revisions, save the template, then close Blaze
Advisor.
12 You must restart the Process Server and the SMW server for the changes to take
effect.

The Data Repository

The data in the data repository is used for generating reports and testing strategies. At
runtime, the Process Server moves transaction data to the DSS, which stores the data in
the data repository. Each data set in the repository has a corresponding schema, and the
structure of the database tables for each data set is based on this schema.
See Also For more information about the DSS, see Chapter 4, “Managing the Data

Storage Service.” For more information about Decision Accelerator schemas, see the
Capstone Decision Accelerator Developer’s Guide.
Administrators may be charged with the following tasks regarding the data repository:
Ensuring that the data repository contains data required for reporting.
Purging old data that is no longer needed.
Reporting Needs
Certain Decision Accelerator reports require final application decision data or final offer
history data in order to be generated properly. Additionally, score model information,
such as score intervals, score model baselines and score model bin baselines, is
necessary for certain scoring reports. Chapter 5, “Decision Accelerator Reports,”
describes Decision Accelerator reports and specifies any data required from the
application processing system for successful report generation.
Score Model Baselines

Population standards— score ranges and expected percentages—must be specified in
the data repository before the Population Stability report can be generated. The analytic
modeler who developed the score model should supply this information to you. You
must manually enter this information in the ScoreModelDevBaseline table in the data
repository. The table includes the following columns:
ScoreModelName—The name of the score model
RangeLower—The minimum score range for the score interval
RangeUpper—The maximum score range for score interval
Baseline—The expected percentage of final scores to fall in the given range
Note For each score model, the table will contain as many rows as there are bins or
score ranges.
Use a database tool of your choosing, or work with your IT staff, to populate the table.
The following sample SQL code is provided as a guide:
insert into scoremodeldevbaseline (scoremodelname,rangelower,rangeupper,baseline)

values ('SM1',0,100,5.0000);
values ('SM1',101,250,50.0000);
values ('SM1',251,600,40.0000);
values ('SM1',601,999,5.0000);
values ('SM2',500,999,100.0000);


values ('SM3',500,750,50.0000);
values ('SM3',751,999,50.0000);
Score Model Bin Baselines

Before the Characteristic Analysis report is generated, you must manually enter score
model bin baselines in the ScoreModelBinBaseline table in the data repository. The
analytic modeler who developed the score model should supply this information to
you. Use a database tool of your choosing, or work with your IT staff, to populate the
table. The table includes the following columns:
ScoreModelName—The name of the score model
CharacteristicName—The name of the characteristic
BinLabel—The name of the bin
BaselinePct—The expected percentage for the value of a given characteristic to fall
in this bin
Use a database tool of your choosing, or work with your IT staff, to populate the table.
The following sample SQL code is provided as a guide:
insert into scoremodelbinbaseline

(scoremodelname,characteristicname,binlabel,baseline) values
('SM1','Char1','Bin1',50.0000);
('SM1','Char1','Bin2',25.0000);
('SM1','Char1','Bin3',25.0000);
('SM1','Char2','Bin1',10.0000);
('SM1','Char2','Bin2',70.0000);
('SM1','Char2','Bin3',5.0000);
('SM1','Char2','Bin4',5.0000);
('SM1','Char2','Bin5',10.0000);
('SM2','Char1','Bin1',25.0000);
('SM2','Char1','Bin2',75.0000);
('SM2','Char2','Bin1',20.0000);
('SM2','Char2','Bin2',20.0000);


('SM2','Char2','Bin3',30.0000);
('SM2','Char2','Bin4',10.0000);
('SM2','Char2','Bin5',20.0000);
When the report is generated, the system uses the values from the
ScoreModelBinBaseline database table for the row whose ScoreModel,
CharacteristicName, and BinName match this score model, characteristic, and bin.
Importing Final Application Decision and Final Offer History

Data
Administrators need to ensure that final application decision data and final offer history
data, which are not included in Decision Accelerator transaction data, are available in
the data repository for report generation. This data needs to be imported from your
front‐end application processing system.
See Also For information on revising the SQL code to import this data, see the Capstone

Decision Accelerator Developer’s Guide.
Purging Data
The data repository stores transaction data cumulatively. It is recommended that you
develop a schedule for clearing and/or purging data. Truncation scripts are provided in
the Decision Accelerator installation which may be used to clear data used for reporting
and testing from the data repository. Note, however, that running these scripts will
remove all of the DSS‐related data from the database tables, so the scripts should be
used with caution. Assuming Decision Accelerator was installed in the default location,
the scripts are available in the following folder:
For Windows: C:\FairIsaac\EOS\DA\data\ddl
For UNIX: <EOSPath>/fairisaac/EOS/DA/data/dll (where <EOSPath> is your
installation path to the fairisaac directory)
The Testing Data Repository

The DSS stores a percentage of application data in the data repository for the purpose of
testing business strategies. The percentage that is stored for this purpose is specified for
each category in the Category Properties page of the SMW. When the user wants to use
DSS data in testing, the STF is used to send a request to the DSS to extract the testing
data. The data is then copied in the data repository and pasted into the testing data
repository where it may be used in the STF for testing, most likely as a batch. The testing
data repository and the STF reside on the client host machine.

Testing Data Data

Strategy Testing Data Storage

System
Administrator DA Web Server
STF
Config
File
Figure 11: The STF and associated components
See Also For information on setting up the STF and using it to extract data for testing,

see Chapter 6, “Extracting Data for Testing Strategies.” For information on setting the
percentage of application data to hold for testing purposes, and using the STF to test
strategies, see the Capstone Decision Accelerator User’s Guide.


CHAPTER 4
Managing the Data Storage Service
Data Storage Service Overview
Setting Up the DSS

CHAPTER 4: Managing the Data Storage Service
Data Storage Service Overview

The Data Storage Service (DSS) is a component of the Capstone Origination Suite. Its
purpose is to save and store transaction data for reporting and testing. The DSS is
provided as a Web service named DataStorageService. Within this service, the
saveDocument operation stores processing history from each transaction to a database
(referred to as the “data repository”). The data stored in the data repository can be used
for the following:
Testing newly developed or updated strategies using the Strategy Testing Facility
(STF). Strategies can be tested to ensure they are set up correctly, and to compare
their performance to existing strategies. Decision Accelerator stores a percentage of
requests received at runtime through the use of the DSS and provides this data to
the STF for testing newly developed strategies created using the SMW. The SMW
provides a test storage percentage setting in the Category Properties page where users
may specify a percentage of applications to be sent to the data repository for testing.
Running Decision Accelerator reports. The DSS stores processing history
information, which is used in standard Decision Accelerator reports. Using the
Report Viewer, you can view reports generated from data collected and stored by
the DSS.
Running Intelligent Data Manager reports. The DSS stores processing history
information which is used in standard Intelligent Data Manager reports.
See Also
For more information on Decision Accelerator testing, see Chapter 6,
“Extracting Data for Testing Strategies.”
For more information on generating Decision Accelerator reports, see Chapter
5, “Decision Accelerator Reports.”
Note that the DSS is not suitable for long‐term data storage, and should only be used for
reporting and testing.
Figure 12 on page 43 shows the DSS and the Decision Accelerator components it serves.
During application processing, processing history is persisted through the DSS as the
last event in each performDecision request.
Using the Report Viewer, reports may be generated from the saved data. A percentage
of processed application data may be saved to the data repository for testing. The STF
extracts this data and uses it for testing. Analysts can test different strategies and they
can also run reports against the data in order to evaluate the effectiveness of
champion/challenger strategies. The percentage of transactions whose data is saved to
the DSS is determined by the value of the Test Storage Percentage field, which is set in
the Category Properties screen in the SMW.

Testing Data
Repository
Strategy Testing Data

Facility Repository
System
Administrator Data Storage
Web Browser Report Viewer
Web Service
Process Server
Web Service
DA Web Server
Calling
Application
External
Interfaces Calling Application Host
Figure 12: The DSS and associated components
Note that certain reports require final application decision data from your application
processing system. In order to run reports, the required data must be manually
populated into the database tables. Score model baselines, or population standards,
must be populated so that the Population Stability Report can be generated, and final
decision data from your front‐end application processing system must be populated so
that certain reports, such as the System Decision Analysis Report, can be generated.
Your IT staff can create a program to transfer final decision data from your application
processing system to the Decision Accelerator data repository so that these reports can
be generated properly. For more information on transferring final decision data to the
data repository, see the Capstone Decision Accelerator Developer’s Guide.

Setting Up the DSS

Before sending requests to the DSS, you must configure it for database and Web service
access.
Database Configuration
Before DSS installation, your database should be installed and it should be configured
with DSS core tables. During DSS installation, you are prompted to enter preliminary
database information. The database connection settings made during DSS installation
are stored in temporary storage, active in the current instance of the Web service. If the
Web server is shut down or if the service is restarted, the database configuration
settings will be lost. To make the connection settings permanent, you must modify the
api.cfg file, then restart the service. The api.cfg file is located in the Web server’s
dss\WEB-INF\classes folder (dss/WEB-INF/classes for UNIX).
The ConnectionPoolSize configuration value used by the dss.war deployment file is set
in the /WEB-INF/classes/api.cfg file. This configuration file should be set to a
reasonable value, based on the concurrent number of requests sent to the Process
Server. Setting the value too small may result in DSS errors in the log file and data
records not being stored. The current default for ConnectionPoolSize is 15. This
number is dependent on your configuration and environment and may need to be
discussed with your database administrator, especially if increasing the number
increases the number of licenses required for the particular database accessed by the
DSS. The Web server or the DSS module deployed on the Web server should be
restarted after the change.
After the installation, the necessary DSS database tables must be manually installed
using the Decision Accelerator‐specific database scripts and Data Definition Language
(DDL) files provided in the Decision Accelerator installation. The DSS core scripts are
found in the C:\FairIsaac\EOS\DSS\data directory (<EOSpath>/FairIsaac/EOS/DSS/
data for UNIX). The scripts generate and populate database tables capable of persisting
data for supported schemas. The database tables are also used for reporting.
Note When installing the DSS, you are able to select a database and generate reports
when using an Oracle, MySQL, or SQL Server database.
See Also
For more information on installing the DSS and running the database scripts, see
the “Data Storage Service Installation” chapter in the Capstone Decision Accelerator
Installation Guide.
For information on administrative tasks concerning the Decision Accelerator data
repository, see Chapter 3, “Managing Repositories.”
See the Capstone Decision Accelerator Release Notes for the types of databases the
current version of Decision Accelerator allows.

Schemas
The schemas supported by the DSS are:
Decision Accelerator Processing History schema (used for Decision Accelerator
reports)
Decision Accelerator Strategy Test Facility schema


CHAPTER 5
Decision Accelerator Reports
Decision Accelerator includes several reports that you may use to monitor system
performance and business strategies. This chapter includes the following sections:
Reports Overview
Reports and the Data Repository
Generating Reports
Exporting Reports
Report Tree Views

CHAPTER 5: Decision Accelerator Reports
Reports Overview
Decision Accelerator provides the ability to generate several reports using the Report
Viewer, which is installed with Decision Accelerator. There are two types of Decision
Accelerator reports: decision reports and scoring reports. Decision Accelerator reports
can help with the following:
Monitoring various aspects of processing
Estimating the effect of new/changed strategies
Analyzing and comparing new strategies to existing strategies
Finding ways to refine strategies
Monitoring model performance
Table 2 describes the reports that are available with this release of Decision Accelerator.
Table 2: Summary of Decision Accelerator Reports

Report Type Report Name Description
Decision System Decision Displays how many of each type of
Analysis Decision Accelerator decision were made
during the reporting period, and optionally
how the Decision Accelerator decisions
correlate with final application decisions
made by the application processing system.
System Decision by Displays the relationship between the final
Score Range decision made by Decision Accelerator and
the score returned by a score model. For
each decision result type, and for each
score band defined for this score model, the
report displays the number of times the
score model's score fell within that score
band when Decision Accelerator's final
decision matched that result type.
Scenario Execution Displays the number of times each scenario
Analysis was executed within a specific decision tree
and provides total scenario executions per
decision tree.
Ruleset Report Displays how rules in a specific ruleset
contributed to Decision Accelerator
decisions, and optionally how those
decisions correlate with final the application
decision made by the application
processing system.
Decision Reason Displays, for each decision result type, the
Analysis frequency of occurrence of each reason
that contributed to a Decision Accelerator
final decision of that decision result type,
and optionally the correlation between each
reason and the final application decision
made by the application processing system.

Table 2: Summary of Decision Accelerator Reports (continued)

Report Type Report Name Description
Decision Flow Analysis Displays the distribution of candidate
decisions and decision flow step result
values generated in decision flow steps,
within decision flows.
Pricing Decision Analysis Provides, for a pricing scenario, a summary
of Decision Accelerator offer
recommendations, actual offers made, and
applicant reactions to those offers. The
report includes only those offers for which a
final application decision is provided by the
application processing system.
Override Tracking Monitors how often the decisions
recommended by scoring scenarios are
overridden by a credit analyst. The report
includes only those offers for which a final
application decision is provided by the
application processing system.
Scoring Characteristic Analysis Provides information useful in analyzing
score model characteristics for score
models defined and executed within
Decision Accelerator (does not include
custom score models executed as an
internal service). Includes detailed analysis
and a summary.
Population Stability Provides information useful in analyzing the
stability of a score model, relative to its
expected performance across score
ranges. The report also provides a stability
index, which is an overall measure of the
stability of the score model.
Final Score Provides information useful in analyzing a
score model's approval rate relative to a
specific score cutoff, and whether there are
inconsistencies that require further
investigation.
See Also For more information about Decision Accelerator reports, see the Capstone

Decision Accelerator User’s Guide.
Reports and the Data Repository

When applications are processed, Decision Accelerator sends transaction data to the
DSS. The DSS then writes the transaction data to the data repository, where it is
available for report generation.
Certain reports require more information than Decision Accelerator transaction data in
order to be generated properly. Table 3 on page 50 lists the reports available in Decision
Accelerator and the data that—in addition to Decision Accelerator transaction data—
should be available in the data repository before the reports are generated.

Table 3: Additional Data for Decision Accelerator Reports

Final
Score Model Application Final Offer
Report Information Decision History
System Decision Analysis X
Scenario Execution Analysis
Ruleset X
Decision Reason Analysis X
Decision Flow Analysis
Pricing Decision Analysis X X
System Decision by Score Range X
Characteristic Analysis X
Population Stability X
Final Score X
Override Tracking X
Score Model Development Information

The following score model information is required by certain reports (as shown in Table
3) in order to be generated as expected:
Score model development baselines—For each score range defined by the analytic
modeler for each score model, the expected occurrences of scores within the score
range)
Score model bin baselines—For each characteristic defined for each score model, the
list of bins and their expected occurrence percentages, as defined by the analytic
modeler
This information should be provided by your analytic modelers. You need to enter this
information in the appropriate tables in the data repository before running these
reports. For information on updating the data repository tables with this information,
see Chapter 3, “Managing Repositories.”
Final Application Decision and Final Offer History Data

When a final decision is reached on an application and an offer has been made to the
applicant, your application processing system should update the application’s
reporting records in the Decision Accelerator data repository with final application
decision data—the final decision made in your application processing system (as
opposed to the recommended decision supplied by Decision Accelerator). This data is
required for generation of most Decision Accelerator reports. In addition, certain
reports also require final offer history data (the offer made to the applicant), which must
also be supplied to Decision Accelerator by your application processing system.
You may pass this data from your application processing system into the Decision
Accelerator data repository by modifying and running a SQL script. For more
information, see the Capstone Decision Accelerator Developer’s Guide.

Generating Reports
Decision Accelerator reports are generated by the Report Viewer, which performs
queries that extract data from the data repository. The Report Viewer is accessed
through the SMW. In order to generate reports, you must log into the SMW as a user
who is configured as a member of the Reports group.
See Also For information on configuring users, see Chapter 2, “Managing User

Access.”
Using the Report Viewer, you select the system for which to generate the reports. For
example, you may want to generate reports using data in your development system’s
data repository, or your production system’s data repository. You may also apply filters
such as date range and product to target the report data. The filters available for a given
report depends on whether it is a decision report or scoring report. Table 4 lists filters
that you may specify for each type of report.
Table 4: Report Filters

Report Type Filter
Decision reports System, reporting period, category, product, decision flow
Scoring reports System, reporting period, decision flow/scoring scenario, score model
To generate reports
1 Log into the SMW as a user who is configured as a member of the Reports group.
2 Click Reports on the menu bar.
3 Select the report you wish to generate.
4 Follow the prompts to enter parameters for the report.
See Table 4 for expected filters.
If you do not wish to filter a specific parameter, enter the percent character (%)
in that parameter to match all values.
5 Click the Print icon to generate the report.
If you have the required Adobe Acrobat printer driver, you may print the report as
a PDF if desired.
Exporting Reports
Decision Accelerator reports can be exported to a Crystal Reports (RPT), Adobe Acrobat
(PDF), Microsoft Word ‐ Editable (RTF), Rich Text Format (RTF), or Comma Separated
Values (CSV) format. This aids in regression‐testing efforts allowing users to save an
electronic copy of reports for use in comparisons.
To export reports
1 Log into the SMW as a user who is configured as a member of the Reports group.
2 Click Reports on the menu bar.

3 Select the report you wish to export.
4 Follow the prompts to enter parameters for the report.
See Table 4 on page 51 for expected filters.
If you do not wish to filter a specific parameter, enter the percent character (%)
in that parameter to match all values.
5 Click Export Report to display the Export Report dialog box.
Figure 13: Export Report dialog box
6 Select the file format to export the report to.
7 Select the report page range (all pages or certain pages of the report).
8 Click OK. A dialog box appears prompting you to open or save the file for each file
format selected.
Report Tree Views

The Report Viewer includes a Show/Hide Group Tree button. When selected, a tree view
navigation pane appears to the left of the report display pane as shown in Figure 14 on
page 53. The navigation pane displays the tree view of the returned report data
allowing you to use this view as a search mechanism. When the Show/Hide Group Tree
button is not selected, the tree view navigation pane is hidden.

Figure 14: Report Viewer with the Show/Hide Group Tree button selected


CHAPTER 6
Extracting Data for Testing Strategies
This chapter includes information on using the Strategy Testing Facility (STF) to extract
data from the data repository for testing.
The following sections are included:
Overview
Using the STF to Extract Data

CHAPTER 6: Extracting Data for Testing Strategies
Overview
The Strategy Testing Facility (STF) is supplied with Decision Accelerator. The Decision
Accelerator STF can be used to test the Process Server after installation, and can also be
used to test strategies that are already in production that have been modified. The STF
also allows business users to perform “what if” type testing and view the expected
outcome of policy changes before they are implemented. Any unexpected outcomes can
be rectified before actual applications are processed using the new strategies, and any
challenger decision flow can be tested and compared to the performance of any champion
decision flow.
In the SMW, for each product category, risk management analysts can establish a test
storage percentage (0‐100) of applications for which the results will be stored in the DSS
data repository, accessible for testing. Based on random digit generation for the STF, at
runtime the applications that have a random digit below the percent threshold are
recorded to the data repository. These applications are stored in XML format with an
identifier, and will include all data present at the end of the application transaction.
As an administrator, you may be called upon to extract data from the data repository for
testing purposes. Use the STF to extract the data. To obtain testing data from the data
repository, the STF requests the data from the DSS. The DSS then sends the data from
the data repository to the STF, which sends it to the testing data repository.
Note The system does not distinguish between test and production data; in other
words, the test storage percentage set in the SMW is applied to both test transactions
and “real” transactions.
See Also For information on testing the Process Server after installation, see the

Capstone Decision Accelerator Installation Guide.
Using the STF to Extract Data

Periodically, you will extract data from the DSS to store in the testing data repository,
where it will be available for testing. By default, data is extracted to the extractor
folder, a sub‐folder of the STF folder. You can change the location by modifying the
STF.config file.
The STF is located in the C:\fairisaac\EOS\Utilities\STF folder (on Windows) or the
<EOSpath>/fairsaac/EOS/Utilities/STF directory (on UNIX, where <EOSpath> is the
directory in which the Process Server was installed), assuming the default location was
used during installation.
The STF Configuration File

Before using the STF, be sure the STF configuration file (STF.config) is set correctly,
and modify the file if necessary. See Figure 15 for an example of the STF.config file.
The STF.config file is an XML‐based configuration file that contains elements and
attributes that control the STFʹs interactions with other applications, including the DSS.
To control DSS data extractions, there is an element named “Target”, whose “name”
attribute is set to “Run Data Extractor”. The Target element contains a sub‐element

called “DataExtractor”, which has attributes that control the STF’s interactions with the
DSS for data extraction. Depending on your environment, you may need to change the
value of one or more of the following attributes of the DataExtractor element:
URL—This attribute is set to the DSSʹs URL, and is set up during the Decision
Accelerator installation procedure, based on the information you provide. If the
DSS is not installed at this URL, the STF will not be able to interact with the DSS.
Check this value and be sure it exactly matches the DSS URL.
TimeOutSeconds—This attribute holds a time out setting that controls the amount of
time that the STF will give the DSS to return requested XML files before timing out
and returning control to the user. The default value is 60 seconds for DataExtractor
and 600 seconds (10 minutes) for all other Web services. If you find the DSS is
timing out, you may need to increase this value.
OutputPath—An output path to the location where the output files will be stored.
The default output location is STF\extractor. Change this path if desired.
<DataExtractor
URL="http://localhost:8090/dss/services/DSS"
Namespace="urn:serviceGetRootData"
OperationName="getRootData"
ParamName="inputXML"
TimeOutSeconds="600"
OutputPath="./extractor" />
Figure 15: The STF.config file
Extracting Simulation Data from the DSS

Follow the procedure below to extract testing data from the data repository.
To extract data for testing

1 Ensure that the DSS is running.
2 Navigate to the STF folder.
3 At a command prompt, launch STF by typing runSTF. (You can also create a
shortcut to runSTF.bat in Windows.)
4 In the STF, select Invoke Data Extractor from the Invoke Target list box, then select
Browse.
5 Select DSSExtract.xml and click Open > Load to load it.

6 Click Invoke.
The STF creates single XML files for each transaction and places them in the
extractor sub‐folder of the STF, assuming the default location for extracted files is
used. Each file is named estimator_datan.xml (where n represents a sequential
number).
Note
You can have the output generated in a different location than the extractor folder
by modifying the STF.config file. See “The STF Configuration File” on page 56.

CHAPTER 6: Extracting Data for Testing Strategies
The DSS will send back XML images of all applications that are stored in the data
repository. If you want it to send only a subset, you must delete from the data
repository the records that you donʹt need before extracting simulation data.
See Also For information on executing tests using the STF, see the Capstone Decision

Accelerator User’s Guide.

APPENDIX A
Troubleshooting
This appendix offers solutions that may be helpful as you use Decision Accelerator. It
covers:
Decision Accelerator Errors
What To Do Before You Contact Product Support

APPENDIX A: Troubleshooting
Decision Accelerator Errors

Decision Accelerator errors may occur during design time (using the SMW) or runtime
(processing test and production transactions). Errors occurring at design time are
displayed in the SMW and documented in the Capstone Decision Accelerator User’s Guide.
Errors, warnings, and informational messages that are returned in output XML
documents are documented in the Capstone Decision Accelerator Developer’s Guide.
Log File Errors

Possible SMW error:
Unable to change timestamp of class file—This error may appear in the system

output log when using WebSphere and results in poor SMW user interface performance.
To resolve this error, remove the class files in WebSphere/AppServer/temp/<HostName>/
<ServerName>/Strategy_Management_Workstation_sysid/SMW.sysid.war/.
If this error occurs, contact Fair Isaac Product Support. For contact information, see
“Product Support” on page 7.
What To Do Before You Contact Product Support

If you experience Decision Accelerator errors, consult the appropriate documentation.
For a listing of Decision Accelerator documentation, see “Related Documentation” on
page 6. Release notes typically include contents of the release, installation/license
information, known limitations, product support, and compatibility information.
Consult other reference materials as needed for related components such as database
management systems, compilers, and operating systems.
Gather Relevant Information

If you’ve completed this initial research and are still unable to resolve your problem,
contact Fair Isaac Product Support. The following information is critical to resolving a
problem:
Your client ID or license number (if applicable)
Your phone number and a fax number or email address
The name and version of the Fair Isaac software to which the issue pertains
The name and version of the operating system and database
The environment in which the error is occurring (test or production)
Both an overview and a detailed description of the problem, including any relevant
error messages
Frequency with which the condition occurs
Whether you are able to replicate the problem, and if so, the steps taken to recreate
the problem

Any changes that may have been made to the environment (for example,
maintenance work that may have been performed or any hardware/software
changes made to the server, workstation, operating system, or data feed)
Any changes to the Fair Isaac application, including new configuration or software
upgrades
Copies of Process Server log files, Web server log files, configuration files, and
screen prints of errors
Troubleshooting Checklist
Before you call Product Support, follow these steps.
Isolate the problem as precisely as possible using debugging facilities and error logs
as appropriate, and try to find a consistent way to reproduce it.
Try to reproduce the problem on another platform or test system.
Whenever possible, modify a Fair Isaac‐provided example or test case so that it
causes the same problem.
If the problem is not consistently reproducible, check whether it may be related to
insufficient memory, memory leaks, search paths, or files that may be missing from
certain directories or class path.
Verify that the versions of the database, compilers, operating system, browser,
drivers, etc. that you’re using are certified and supported by Fair Isaac.
Identify any changes in your environment that may have an impact on the
Fair Isaac software (for example, database maintenance, service pack deployment,
upgrade of a system component, operating system patches).
If applicable, try to isolate various components of your solution to simplify the
troubleshooting (for example, pull out a subset of rules or code from the bulk of
your application). Support can assist you best if they get a small sample of your
application to work with. If possible, send Support a small test case with
instructions, so they can run the test case.
See Also For information on how to contact Fair Isaac Product Support, see “Product

Support” on page 7.

APPENDIX A: Troubleshooting

Glossary
A
analytic modeler A person who creates analytic models to be applied to data in making decisions.
See also: model.
Ant A Java-based build tool from Apache. It uses XML-based configuration files rather
than shell commands; this allows it to be used for developing software across
multiple platforms.
API Application Programming Interface. A specification that defines how one piece of
computer software can communicate with another. It describes how a developer
can access the methods, properties, and constructors of a set of classes. Providing
an API allows a business to offer its tools to external developers without exposing
the underlying code.
application The set of data provided by an institution’s customer or prospect that is processed
using a product’s strategy to determine whether the institution should offer the
product to the customer and what the details of the offer should be.
See also: product, product strategy.
application administrator A person who controls system user access, granting users only those permissions
required to perform their duties and ensuring access to information is given only to
those who require its use.
For Intelligent Data Manager, the person who uses the Connection Configuration
Workstation to set up connections to data sources, and the Dataflow Configuration
Workstation to set up data source parameters.
attribute In an XML document, a field contained by an element that is used to hold data
values. Each attribute maps to a field associated with an object in the
Capstone Origination Suite data model. XML attributes with the same name can
appear in multiple places and are uniquely identified by their complete path name.
In Decision Accelerator, fields in rule authoring correspond to XML attributes and

elements in transaction documents. For example, the Income object has a field
called “Frequency”, which can have a value of “Monthly”, which describes how
often the income is received.
See also: element, node, object.

Glossary
B ^ Top
baseline score When using a score model that returns distanced reasons, the baseline score for
each characteristic is a user-specified value that is used in calculating score
reason distances. The baseline score value for each characteristic is usually
provided by your modelers and is considered to be a neutral value for score
purposes. A baseline score is not needed if you are using a score model that
returns ranked reasons or no reasons.
See also: score model characteristic, score model type.
bin In a score model, a set of possible values for a characteristic. Bins are rule
conditions that must be mutually exclusive and collectively exhaustive so that a
data value passed to a characteristic can only fall into one bin.
See also: score model, score model characteristic.
Blaze Advisor The Fair Isaac product used by Decision Accelerator to develop and deploy
custom rules and rule services.
BlazeRepository See: configuration repository
business rules engineer The person responsible for designing and implementing the business rules
required to satisfy the company’s business policies
C
calling application An application, created by an interface developer, that sends transactions to the
Process Server. Each transaction requests a decision result. Typically, the calling
application needs to interface with the client’s existing application processing
system. Synonymous with “client application”.
See also: API, interface developer.
Capstone Data Storage See Data Storage Service.

Service
Capstone Origination A multi-product origination system designed for credit application processing and
Suite decisioning. At this time, Capstone Origination Suite includes two products:
Decision Accelerator and Intelligent Data Manager.
See also: Intelligent Data Manager.
Capstone Process Server See Process Server.
category See product category.

Administrator’s Guide
challenger decision flow An alternative decision flow for a product that handles some portion of applications
until the challenger decision flow is either discarded or deemed to be better than
the current champion. In the latter case, the challenger replaces the champion.
See also: champion decision flow, product strategy.
champion decision flow For a product with more than one decision flow, the champion is the most
established one and is used as a reference against which challenger decision flows
are evaluated. The champion decision flow typically handles the majority of the
applications for a product.
See also: challenger decision flow, product strategy.
characteristic See score model characteristic.
class In the Java programming language, a class is a category of object that defines the
common characteristics shared by a family of related objects. Specifically, it lists
shared properties and methods, and specifies the interfaces implemented by the
class.
classpath An environmental variable which tells the JVM where to look for class or JAR files
to import or interpret.
See also: JVM.
client application See calling application.
client host The computer that hosts the Web browser through which users access the SMW
and the Report Viewer. Also hosts the STF and testing data repository.
See also: Report Viewer, SMW, STF, testing data repository.
configuration file A text file that contains the specifications for a Capstone Origination Suite
component such as the Process Server, a rule service, or an internal service.
Sometimes referred to as a “config file”.
See also: Process Server, rule service.
configuration repository In Decision Accelerator, a storage system that contains information about your
categories, products, product strategies, decision flows, and associated
components that implement your business policy. Also known as
“BlazeRepository.sysid” (where sysid is the system ID you assigned to the
repository during installation).
In Intelligent Data Manager, a storage system that contains information about the
physical and logical configurations to external data sources.
See also: data repository, decision flow, decision table, decision tree, product,
product category, product strategy, repository, rule, ruleset, system ID.
CRA Credit Reporting Agency. A source of consumer credit reports, such as Experian,
Equifax, TransUnion, Equifax Canada, or TransUnion Canada.

Glossary
credit application See application.
D
data model The business data model supplied with Capstone Origination Suite is a description
of the objects and fields necessary for decision transactions. It provides a structure
for the rules used for decisioning, input XML documents for decision requests, and
output XML documents for decisions. The data model is represented externally by
an XML schema in XSD format and can be customized if necessary for your
business policy.
See also: schema.
data repository The data repository is the database used by the DSS to save XML data for use in
standard reports and testing.
See also: configuration repository, DSS, repository.
Data Storage Service See DSS.
Decision Accelerator The Capstone Origination Suite product that provides strategy and decision
management capability. It can be used in conjunction with data retrieval, analytics,
and application processing systems in order to provide a complete application
processing solution.
See also Capstone Origination Suite.
decision A credit decision requested by a calling application for a transaction and returned
by the decisioning application. Decisions appear in the order that they were
created, with the most conservative decision(s) marked “final”.
For example, if five rulesets recorded decisions there will be five decisions in the
output. If one of these is “approve”, and the other four are declines, the four
declines will all have “Final” as their decision status.
decision flow The graphical representation of a flow of decision-related steps that are executed
to perform the processing for a product.
See also: product strategy.
decision table A tabular representation of a ruleset that allows you to create and maintain a large
number of rules. A decision table generates a specific value used to support a
business decision, where the rules for generating the value are more easily
expressed in tabular form, such as a credit limit assignment table.
See also: rule.
decision tree A graphical representation of a ruleset. A decision tree consists of a connected set
of conditions and actions. Using decision trees in the SMW, you can create and
maintain rules using a familiar tree format.
See also: rule, scenario, SMW.

DSS Capstone Data Storage Service. A Web service that provides persistence of XML
data to the data repository. For Decision Accelerator, processing history
information to feed database tables used in standard Decision Accelerator reports.
It also stores a percentage of responses by Decision Accelerator for the purpose of
providing data to the STF.
See also: data repository, STF, Web service.
E
EJB Enterprise JavaBeans. A component architecture for the development and
deployment of object-oriented, distributed, enterprise-level applications. EJBs
hand off concurrency, transaction handling, and persistence tasks to the EJB
container so that the beans can focus on business logic.
See also: EJB container.
EJB container An entity that provides life-cycle management, security, transaction, naming,
deployment, runtime, and other services to the EJB. An EJB container is provided
by an EJB or J2EE server.
See also: EJB, J2EE.
element In an XML document, a field used to hold other elements and attributes. Some
elements can hold values (such as message descriptions or ARF text) that are too
long to be held by attributes. These elements may not contain attributes.
A complex element is an XML element that contains other elements and/or

attributes. A simple element is an element that can contain text content; it does not
contain other elements or attributes. A complex element is equivalent to an object
in the Capstone Origination Suite data model.
See also: attribute, data model, node, object, schema.
enterprise application A server that hosts an enterprise application, allowing multiple clients to connect to
server the server and run the same program at the same time. An enterprise application is
an application hosted on a server that simultaneously provides services to a large
number of users, usually over a computer network. An example of an enterprise
application server is the Java-based product WebSphere.
See also: WebSphere.
F
FICO® Expansion score The credit risk of an applicant, expressed in the form of a numeric score produced
by a FICO model using data from providers other than traditional CRAs.
FICO® Expansion score A service that provides the ability to assess the credit risk of consumers with little
service or no credit histories at the three major US credit reporting agencies.

Glossary
I
Intelligent Data Manager The Capstone Origination Suite product that provides connectivity and data
management capabilities. It can be used in conjunction with strategy and decision
management, analytics, and application processing systems in order to provide a
complete application processing solution.
See also: Capstone Origination Suite.
interface In the Java programming language, a collection of method definitions and constant
values. Classes can implement interfaces by using the “implements” keyword.
Interface also refers to the code that integrates the client’s application processing
system with the Process Server.
See also: calling application, class, Process Server.
interface developer A person who uses the Developer’s Guide to develop interfaces that provide data
to and receive data from the Process Server. The interface developer is also
responsible for understanding the data requirements defined by risk management
as well as connecting to multiple bank systems to obtain various data elements.
The interface developer also maintains the interfaces after the system reaches the
production environment.
See also: calling application, Process Server.
J
J2EE Java 2 Platform, Enterprise Edition. An environment for developing and deploying
enterprise applications. The J2EE platform provides services, APIs, and protocols
that allow developers to create multi-tiered applications.
See also: API.
J2EE app server An application server that provides the operating environment for the Process
Server, DSS, and Report Viewer.
See also: DSS, Process Server, Report Viewer.
JDBC Java Database Connectivity. A Java API that enables Java programs to execute
SQL statements. This allows Java programs to interact with any SQL-compliant
database. In order for the DSS to operate properly, a user must edit the api.cfg file
located in the Web server’s dss\WEB-INF\classes folder (dss/WEB-INF/classes for
UNIX) to set up JDBC parameters that specify the data source and user
information DSS needs to access the database.
See also: DSS.

JRE Java Runtime Environment. Part of the Java Development Kit (JDK), comprising
the Java Virtual Machine (JVM), core classes, and supporting files. It provides the
minimum requirements for executing a Java application, so it can be used to
distribute the runtime environment without the entire JDK.
See also: JVM.
JVM Java virtual machine. A software “execution engine” that interprets compiled Java
bytecode in Java class files for a computer’s processor so that it can perform a
Java program’s instructions. This allows applications to run on any platform without
having to be rewritten or recompiled.
M
model A complex set of calculations that operates on a large amount of data and returns a
relatively simple value.
N
node An element or attribute in an XML document. Nodes in the
Capstone Origination Suite data model correspond to fields in Decision Accelerator
rules.
See also: attribute, element.
O
object In a data model, an entity that contains the data fields used in product strategies to
implement business policy. An object is equivalent to a complex element in an XML
schema.
See also: data model, element, schema.
operations manager A person who manages introduction of Capstone Origination Suite, monitors daily
application processing activities, and reports results to risk management.
P
population stability Representation of changes in a scoring population over time. Recent applicants
scores are compared with those of a previously established baseline group.
Population stability data is a gauge of a model's ability to rank order risk.
See also: population stability index, score model
population stability index In score models, a measurement of the degree of deviation of final scores from the
current population of applications as compared to the application scores of the
population used to develop a model.
See also: population stability, score model.

Glossary
population standards In score models, the percentage of the development population that falls within a
percent score range. This field is paired with population standards score. The sum of all
percent values entered must be 100%. To ensure that the standards cover the
complete range of possible score values, the last standard must have a “Score”
that is greater than the maximum possible score value. This value is used in
measuring population stability and the data produced can help you track changes
that may affect the acceptance rate for each scoring population.
See also: population standards score, score model.
population standards In score models, a value used in measuring population stability. This value
score represents the upper bound of a score range for a specific scoring population. Its
occurrences correspond with occurrences of the Population Standards Percent
field.
See also: population standards percent, score model.
port An integer that identifies a specific process on a remote server when a

Transmission Control Protocol (TCP) connection is made from a client machine.
Process Server Capstone Process Server. A Web service or stateless session bean that allows the
calling application to interface with Decision Accelerator or Intelligent Data
Manager. The calling application sends an origination application to the Process
Server in an input XML document; the Process Server returns the decision
response and/or request result to the calling application in an output XML
document.
See also: calling application, Process Server host, product, stateless session bean,
Web service.
Process Server host The computer that hosts the Process Server; it receives requests from and returns
responses to the client’s calling application.
See also: calling application, Process Server.
product A loan, credit card, or other product or service provided by an institution.
product category A group of products that an institution considers similar in some way. Also referred
to as a “category”.
See also: product.
product strategy The component that specifies the logic used to determine which decision flow will
be executed, for one or more products. The product strategy is implemented as a
specialized decision tree whose action nodes specify decision flows to be
executed. Each product may have a single product strategy, and if the product
strategy does not specify a decision flow, the product's default decision flow is
used if one has been specified.
See also: decision flow, decision tree, product.

R
Report Viewer A mechanism for users to select and view reports to be generated from data
collected in the DSS database for both Decision Accelerator and Intelligent Data
Manager. Decision Accelerator reports provide assessments of performance of
product strategies in their production and strategy testing environments. Intelligent
Data Manager reports provide administrative information on CRA performance,
data source usage and CRA billing.
See also: DSS, product strategy.
repository In Decision Accelerator, a storage system that contains information about product
strategy components (the configuration repository, also known as the
BlazeRepository), transaction data used for reporting (the data repository), or data
used for testing (the testing data repository).
In Intelligent Data Manager, a storage system that contains information about the
physical and logical configurations to external data sources (the configuration
repository) or transaction data used for reporting (the data repository).
See also: configuration repository, data repository, testing data repository.
risk management analyst A person who performs policy rule gap analysis to determine if system-delivered
rules meet current bank requirements. Works directly with business rules engineer
and interface developers to implement required changes to the system. Uses a
GUI-based system to modify, add, change, and delete rules, processes, credit limit
assignment matrices, pricing information, and general loan decisioning
parameters.
See also: business rules engineer, interface developer, rule.
risk manager A person who is responsible for implementing credit strategies. Works to define
credit risk thresholds that are set based on industry trends and portfolio
performance. Directs entire risk management function leveraging data from all
aspects of the credit life cycle to determine and set policies to implement. Monitors
all risk based systems in the credit enterprise including originations, collections,
recovery, and servicing.
See also: product strategy.
rule The basic unit of rule processing that represents organizational decisions and
policies. Rules are statements in the form: If “some condition” is true, then do
“some action”. Rules are grouped into rulesets, or represented as decision tables
or decision trees.
See also: decision, decision table, decision tree, product strategy, ruleset.
rule service The component of the Process Server that provides the execution environment for
strategies defined in SMW, and thus makes those strategies accessible to calling
applications.

Glossary
ruleset A categorical grouping of business rules and the parameters associated with each
rule; a subset of related rules from the rule library.
See also: rule.
S
scenario A specialized type of decision tree action that represents possible outcomes. There
are three types of scenarios:
Decision scenarios—result in decisions and associated reasons

Pricing scenarios—result in product offerings for an application
Scoring scenarios—execute score models and result in decisions based on
scores returned from those score models
Scenarios can be used across multiple categories and products, and are accessed
from the SMW Navigator pane.
schema A model for describing the internal data structure used in Decision Accelerator and
enabling the definition, transmission, validation, and interpretation of data between
systems. The Decision Accelerator XML schema is based on the Decision
Accelerator data model. Each element in the schema has a unique name and is
equivalent to an object in the data model. Each attribute of an element is equivalent
to a field of an object in the data model. Elements that have no attributes are also
fields.
See also: attribute, element, node, object.
score model A mathematical formula used to predict the likelihood of future behavior for a
customer or prospect, or compute a value. Score models can use two types of
calculations: additive and logistic regression. Score models are implementation
types that can be accessed directly from a decision flow step, or from a scoring
scenario.
score model Data (such as bureau score, income, or city) that is used as a calculation criterion
characteristic by a score model. A characteristic can have a numeric (integer or real) or a string
data type.
See also: score model.

score model type In score model properties, a setting that allows you to determine if and how score
model reasons are returned. There are three score model types:
No Reasons. Choose this option when you do not want to return reason codes.
Ranked Reasons. Choose this option when you want to return reason codes
based on their priority order in the reason code list, which is a fixed set of 100
reason codes ranked from 00 to 99. Depending on the reason code priorities set
by your organization, the most important reason codes appear near the top of
the list. When reason codes are returned, you see the topmost 10 reasons.
Distanced Reasons. Choose this option when you want to return reason codes
based on a calculation of distance from the baseline score, rather than by their
priority order. Reasons are returned in descending order. When you choose this
option, priority-order ranking is used for tie-breaking purposes where there is
more than one computed score reason distance that is the same. When reason
codes are returned, you see the topmost 10 reasons.
See also: score model.
scoring population A subset of a credit portfolio that presents a unique risk or treatment requirement.
SMW Strategy Management Workstation. The GUI used by risk management analysts to
define business strategies in Decision Accelerator. Using the SMW, users can
define all aspects of their strategies.
See also: Blaze Advisor, SMW host.
SMW host The computer that hosts the SMW on a Web application server. The SMW user
accesses the host machine by entering the host’s address in their browser.
See also: Blaze Advisor, SMW.
SSB See: stateless session bean.
stateless session bean A session bean that does not maintain a conversational state for a particular client.
The bean’s instance variables may contain a state during method invocation, but it
is not retained when the invocation is finished.
See also: EJB.
STF Strategy Testing Facility. A Web service client used for testing purposes. In
Decision Accelerator, it is used to test newly developed strategies created on the
SMW using data found in the testing data repository.
See also: SMW, product strategy, Web service.
STF Batch Utility A utility that allows you to do strategy testing in a batch mode without interacting
with the STF user interface.
See also: STF, product strategy.
strategy See product strategy.
Strategy Management See SMW.

Workstation

Glossary
Strategy Testing Facility See STF.
system A configuration repository, SMW, and rule service that together support the
creation and execution of strategies associated with a specific entity, such as a
company, department, or line of business.
See also: configuration repository, rule service, SMW, system ID.
system ID A unique identifier for a specific system. When the Process Server receives a
request from the calling application, it routes it to the rule service associated with
the system whose system ID matches the value of the Application/
@DeliveryOptionCode attribute in the calling application’s request.
See also: Process Server, rule service, system.
system/application A person who performs system setup and ensures system is operating properly.
architect This person works closely with interface developers and testers to ensure system
architecture performs efficiently.
system/network A person who performs any of the following tasks: deploys Decision Accelerator on
administrator the physical resources, per the capacity plan; ensures Decision Accelerator
remains operational in the production environment; monitors network resources;
monitors Decision Accelerator server configuration and deployment; monitors
performance and general network latency; assists users with accessibility issues;
administers passwords and user settings for the broad network community; works
in conjunction with the application administrator to synchronize application log-on
settings with network log-on settings.
See also: application administrator.
T
test storage percentage A setting in the Category Properties page that specifies the percentage of
application results to be sent to the DSS for use in the Strategy Testing Facility
(STF).
See also: DSS, STF.
testing data repository A data repository that contains XML data used by the STF in the development and
testing of Decision Accelerator strategies.
See: STF, repository.
Tomcat Open-source, Java-based application server software that runs servlets and
supports the Java Server Pages (JSP) specification.
V
VisualInvoke A tool used to test Intelligent Data Manager connections to the external data
sources.

W
Web server A web server that provides the operating environment for the Process Server, DSS
and Report Viewer.
See also: DSS, Process Server, Report Viewer.
Web service A software system designed to support interoperable interaction of machines over
a network. A Web service is typically made available from a business’ Web server.
Requests and responses use standard Web protocols such as HTTP and data-
interchange formats such as XML.
In Decision Accelerator, an internal service that executes a call to an external

system. Web services are defined and accessed through the Web Service
Properties page. To use the Web service in a product strategy, you define a
decision flow with a decision flow step whose implementation is a data method
sequence. The data method sequence executes a data method that prepares a
Web service request message, invokes the Web service, and then handles the
response. A Web service can be used to invoke Intelligent Data Manager.
WebSphere A set of Java-based tools from IBM that allows customers to create and manage
applications across multiple computing platforms. The main product in this tool set
is the WebSphere Application Server (WAS), which customers can use to connect
clients with Java applications or servlets.
WSDL An XML-based language that defines how to communicate with a Web service and
specifies the services offered therein.
See also: Web service.
X
XML Extensible Markup Language. A system for tagging and organizing documents,
designed especially for Web use. XML users can create their own customized tags,
enabling the definition, transmission, validation, and interpretation of data between
systems and between organizations.

Glossary

Index
A administrative tasks 36
and the DSS 42
adding new repositories 32 reporting needs 36
adding users 21 database configuration 44
administrative tasks 17 DDL files 44
configuration repository 28 Decision Accelerator
data repository 36 and Intelligent Data Manager 13
exporting reports 51 license keys 15
extracting test data 56 overview 10
report generation 51 reports overview 48
reporting needs 49 schemas 45
setting up the DSS 44 development environment 28
users 20 documentation 6
application processing 10 DSS 10
authentication 20 associated components 43
custom 23 database configuration 44
disabling 24 DDL files 44
reverting to defaults 24 overview 42
authentication.xml file 21, 23 reports 42
authorization 20 setup 44
custom 23 testing 42
disabling 24
reverting to defaults 24
authorization.xml file 23
E
error messages 60
B exporting reports 51
extracting test data 57
baselines 37
F
C
final application decision data 38, 50
challenger decision flows 56
champion decision flows 56
Characteristic Analysis Report
I
score model bin baselines 37 installing license keys 15
configuration repository 10, 28
administrative tasks 28 L
creating new repositories 32
license keys, renewing and installing 15
file structure 30
log file
promoting strategies to production 31
errors 60
ConnectionPoolSize configuration 44
creating passwords 22
UNIX 23 M
Windows 22 multiple repositories 11
D
data repository 10, 36

Index
P score model dev baselines 36
score model information 50
passwords, creating 22 scoring reports 48
UNIX 23 System Decision Analysis
Windows 22 data requirements 50
Population Stability description 48
score model dev baselines 36 System Decision by Score Range
population standards 36 data requirements 50
Process Server 13 description 48
production environment 28 repositories 26, 28
purging data 38 configuration repository 10, 28
data repository 10, 36
R sample repository structure 30
reason codes 33 testing data repository 10, 38
modifying 34 roles 23
renewing license keys 15
report tree views 52 S
Report Viewer 10, 51 schemas 45
reports score model baselines 36
Characteristic Analysis score model bin baselines 37
data requirements 50 score models
description 49 information for reports 50
score model bin baselines 37 reason codes 33
Decision Flow Analysis Show/Hide Group Tree button 52
data requirements 50 SMW 10, 28
description 49 STF 10, 38, 56
Decision Reason Analysis configuration file 56
data requirements 50 location in UNIX 56
description 48 location in Windows 56
decision reports 48 using 56
description of 48 strategies, promoting to production 31
DSS 42 system IDs 13, 33
exporting 51
filters 51
final application decision data 36, 38, 50
T
Final Score test storage percentage 42, 56
data requirements 50 testing 56
description 49 challenger decision flows 56
generating 51 champion decision flows 56
Override Tracking DSS 42
data requirements 50 extracting test data 57
description 49 test storage percentage 42, 56
overview 48 using the STF 56
Population Stability testing data repository 10, 38
data requirements 50 tree view navigation pane 52
description 49 troubleshooting 60
Pricing Decision Analysis checklist 61
data requirements 50 truncation scripts 38
description 49
required data 43 U
Ruleset Report
user administration overview 20
data requirements 50
users
description 48
adding 21
Scenario Execution Analysis
adding user roles 23
data requirements 50
installed user names and passwords 20
description 48
score model bin baselines 37

X
XML files 10

Index

Capstone Origination Suite: Decision Accelerator

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Capstone Origination Suite: Decision Accelerator

Încărcat de

Drepturi de autor:

Formate disponibile

Capstone Decision Accelerator Administrator’s Guide

2.0 Capstone® Origination Suite

Fair Isaac Confidential and Proprietary Information 3

4 Fair Isaac Confidential and Proprietary Information

Welcome to the Capstone Decision Accelerator Administrator’s Guide, a guide to help

About Capstone Decision Accelerator

Fair Isaac Confidential and Proprietary Information 5

Conventions Used in this Guide

Convention Item Examples

6 Fair Isaac Confidential and Proprietary Information

Contacting Fair Isaac

Strategy Consulting: Fair Isaac offers consulting services to assist you in using

Fair Isaac Confidential and Proprietary Information 7

Conferences and Seminars: Fair Isaac offers conferences and seminars on our

About Fair Isaac

8 Fair Isaac Confidential and Proprietary Information

Decision Accelerator Administration

Fair Isaac Confidential and Proprietary Information 9

Capstone Origination Suite

At this time, the Capstone Origination Suite consists of two products:

Decision Accelerator System Overview

10 Fair Isaac Confidential and Proprietary Information

Client Host Process Server/SMW Host

Testing Data Data

Strategy Testing Process Server

Calling Application Host

Fair Isaac Confidential and Proprietary Information 11

Process Server/SMW Host

Strategy Testing Process Server Strategy Testing

Admin/ SMW SMW Admin/

Calling Application Host

Figure 2: Example of a Decision Accelerator system with multiple repositories

12 Fair Isaac Confidential and Proprietary Information

Using Decision Accelerator with Intelligent Data

Each installation of a Capstone Origination Suite product has a separate system ID.

Fair Isaac Confidential and Proprietary Information 13

Client Host Process Server/SMW Host

Testing Data Data

Strategy Testing Process Server

Calling Application Host

IDM Server Host

External Data Sources

See Also For information about processing applications using Decision Accelerator

14 Fair Isaac Confidential and Proprietary Information

Installing License Keys for Blaze Advisor

To update the Blaze Advisor license keys in Windows

To update the Blaze Advisor license keys in UNIX

See Also For more information on installing license keys for Blaze Advisor, see the

Fair Isaac Confidential and Proprietary Information 15

Installing License Keys for the SMW and Process Server

To install renewed license keys for a Decision Accelerator Web service

To install renewed license keys for a Decision Accelerator deployment using

16 Fair Isaac Confidential and Proprietary Information

Fair Isaac Confidential and Proprietary Information 17

18 Fair Isaac Confidential and Proprietary Information

Managing User Access

Fair Isaac Confidential and Proprietary Information 19

User Administration Overview

Pre-defined User Roles

Installed User IDs and Passwords

Table 1: Default Users and Passwords

20 Fair Isaac Confidential and Proprietary Information