Vital Signs New Install

Overview

The following information is a step by step overview of the installation process of Vital Signs.

HPUX Server Requirements

OS

• HPUX PA-Risc 11.11
• HPUX PA-Risc/ITANIUM 11.23
• HPUX PA-Risc/ITANIUM 11.31

Software

• Python 2.7.3
• Python configObj Library

Windows Server Requirements

The Windows server does all of the heavy lifting for Vital Signs after the data has been extracted from Eloquence.

OS / Hardware

• Vital Signs Windows Server Recommendations

Software

• QlikView Server
• QlikView Client
• Python x32 2.7.3
• Windows Server Firewall Settings

Step 1 - Initial Meeting

After purchasing Vital Signs you will receive an email requesting to schedule a meeting between Vital Soft and the individuals who will be overseeing the Vital Signs project. During this initial meeting the contact information for the following will be requested by Vital Soft :

• Project Lead
• VPN Access
• HPUX/UC4 Installation and Setup
• Windows Server Installation and Setup

Share and Loan Product Grouping

• shxrefCCYYMMDD.xls
• lnxrefCCYYMMDD.xls

Credit Union Specific Customization

• CU Customization
• Custom Attributes

Install Check List

HPUX

• HPUX Python Install
• Python configobj module Install
• /VSJOBS symbolic link
• /ASKPLUS/vsdata/vitalsigns.ini configured with proper FTP information

Windows

• Python 32bit
• Pyparsing Python Module
• Microsoft Excel 2007 or later (Open Office Calc will limit Document Distribution Functionality)
• IIS 7+ / FTP 7.5+ (FTPes is currently only supported with FileZilla Server)
• .NET Framework 3.5+
• Sftp client (winscp, filezilla, etc..) for HPUX script transfers (optional)
• Qlikview Client
• Qlikview Server
• vitalsigns.zip unzipped to vitalsigns directory

Post Install Configuration

• Membership Analysis Initial Setup

• Transaction Analysis Initial Setup

Transaction Analysis Initial Run

• Extract 23 months of History Data

   login bolive
   cd /var/summit/spectrum/LIVE
   
   # Extract CMNDFILE
   /VSJOBS/JVSLOAD_HIST CMNDFILE=1
   
   # Extract 360 days of History data from 2 years ago 
   # Replace YYYYMMDD with 2 years ago to the current date
   /VSJOBS/JVSLOAD_HIST YYYYMMDD DAYS=30 LOOP=12
   
   # Extract the final year of History data
   /VSJOBS/JVSLOAD_HIST DAYS=30 LOOP=12
   
   # Extract the remaining days  (JVSLOAD_HIST default to extracting 30 days from the last extract Date held in HISTLOG)
   /VSJOBS/JVSLOAD_HIST

Membership Analysis Initial Run

• Extract Prior EOM (Note replace YYYYMMDD with the prior EOM date)

   login bolive
   cd /var/summit/spectrum/LIVE
   /VSJOBS/JVSLOAD_MBRSHLN EOM YYYYMMDD

• Extract Current Day

   login bolive
   cd /var/summit/spectrum/LIVE
   /VSJOBS/JVSLOAD_MBRSHLN

UC4 Job Setup

Note: There is no need to have your job plans pause and wait for completion of these jobs before continuing with the next step

Daily Jobs

   ## HIST DAILY
   ## Run nightly- between 12:01 and 1 am, including weekends
   ## Should be run prior to the MEMBERSHIP_ANALYSIS DAILY
   ## Login as bolive
   set -e
   cd /var/summit/spectrum/LIVE
   /VSJOBS/JVSLOAD_HIST

   ## MEMBERSHIP_ANALYSIS DAILY
   ## Run nightly – after JVSLOAD_HIST and prior to 5am
   ## Do not run on days when the EOM job (see below) is scheduled
   ## Login as bolive
   set -e
   cd /var/summit/spectrum/LIVE
   /VSJOBS/JVSLOAD_MBRSHLN

EOM Job

   ## MEMBERSHIP_ANALYSIS EOM
   ## Run after report databases have been created
   ## Login as bolive
   set -e
   cd /var/summit/spectrum/LIVE
   /VSJOBS/JVSLOAD_MBRSHLN eom &YYYYMMDD
   #Where &YYYYMMDD is a UC4 variable containing the last day of the month

UC4 Error Alerts

   #Main Vital Signs Errors
   serious error occurred while processing
   Errors found in log.  Printing last 20 lines

   #Vital Signs Listener Error
   Error xmlrpc exception

   #FTP Errors
   Unable to connect
   Unable to login
   Error in uploading the remote file.