LenStar Integration Utility

Vendor Setup Guide

May 2006

www.fairisaac.com

LenStar Integration Utility – Vendor Setup Guide

Revision History

Date of Revision / Summary of Revision / Issued By

Table of Contents

Table of Contents ii

1 Overview 3

2 Vendor Questionarre 3

3 Installation package 3

4 LenStar Admin Mailgroup Settings 4

5 LenStar Database Updates 4

5.1 Monitor Table 5

5.2 Uploadcodesxref Table 5

5.3 Hubmailgroups 6

Copyright © 2006 Fair Isaac Corporation. All rights reserved. ii

Style is Header doc title: Document Title Goes Here

1  Overview

This document describes how to setup a vendor with the LenStar Integration Utility.

2  Vendor Questionarre

The vendor will answer and return the LIU Setup Questionnaire before LenStar will configure the LIU.

3  Installation package

Configure the LIU Install Vendor Package. The LIU Install Vendor Package is located in the Download section of LenStar.

Before you begin configuring the LIU Install Package the following information is needed:

·  Vendor Name

·  Vendor Mailgroup

·  Vendor ID’s from the Vendors Table

The Config.dbf will need to be modified using BRO. The following changes are needed to be made to the Config.dbf:

·  KEYID – Enter the 1st three letters of the vendors mailgroup

·  USER – Enter the Vendor Name

·  MAILGROUP – Enter the Vendors Mailgroup

·  ID – Enter the vendor id. Note: If the vendor has more then one vendor only enter one.

Once these changes are made the install package is ready for the vendor.

The following files will be included in the installation package for the client

·  LenStarIntegrationUtility.exe

·  LenStarIntegrationUtility.bin

·  Liuhttp.log

·  Liusql.log

·  Bro.exe

·  Bro.ini

·  Ace32.dll

·  Adsloc32.dll

·  Axcws.dll

·  The following .dbf and .cdx files are used by the LenStarIntegrationUtility.exe

o  BKCODES

o  BKCOMBO

o  BKAPRMS

o  CLIENTS (includes .fpt file)

o  CLCODES

o  CLPARMS

o  CONFIG (no .cdx file)

o  DICODES

o  DIPARMS

o  FCCODES

o  FCPAMRS

o  FMRPARMS

o  EVCODES

o  EVPARMS

o  LOANTYPE

o  POCCODES

o  POCPARMS

o  SELLER

o  TIMFEES

o  USERS

o  VENDORS (includes .fpt file)

4  LenStar Admin Mailgroup Settings

The vendor must provide the Security Code of the desktop/servicer when the LIU will be running from. The security code will need to be entered in the Mailgroup Settings for the specific vendor

5  LenStar Database Updates

The following tables in the LenStar Database are to be update to ensure the LIU can push and pull the correct information.

5.1  Monitor Table

The monitor table is needed to be update when a client is using the LIU. The following entries are to be made in the monitor table:

5.2  Uploadcodesxref Table

The Uploadcodesxref table is needed to be update when vendors are updating event tracking dates using the LIU. The Uploadcodesxref is to be setup as follows:

The XRefCode in the Uploadcodesxref table is to equal the upload code in the ADO and XML transaction.

This information will be provided by the vendor after they complete the questionnaire.

5.3  Hubmailgroups

This table is needed to be updated when the vendor has more then one vendor id. The Hubmailgroups is to be setup as follows:

Example:

If the Vendor ABC has 5 vendor id’s :

Mailgroup ID: State Served

ABC 5 CA

ABC 10 WA

ABC 17 OR

ABC 25 AZ

ABC 30 NV

The config.dbf already contains the vendor id entry of ‘5’. The remaining vendor id’s will be entered in the Hubmailgroups table.