Vital Signs New Install

From Vital Soft Wiki
Revision as of 00:32, 1 January 2013 by >Jeremyb (→‎Review Figures)
Jump to: navigation, search

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

Software


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


Configuration Meeting

Share and Loan Product Grouping

Credit Union Specific Customization


Installation

HPUX

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


Transaction Analysis Initial Run

  • Extract 24 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


Review Figures

  • Membership totals

Use the following query in Askplus to match to the Open Shares Count and Balance

In the example below, replace the macros %VS-ACTIVE-SHARE and %VS-CHGOFF-SHARE with the matching criteria found in the /ASKPLUS/vsdata/custom/live/vsmacdef 

open membrs.report;

FIND PRIMARY=SHARE-FILE;
%VS-ACTIVE-SHARE AND
NOT (%VS-CHGOFF-SHARE)
END

REPORT
TF1, SHARE-FILE.ACCOUNT, TAB1, COUNT
TF1, SHARE-FILE.BALANCE, TAB2, ADD
END


Use the following query in Askplus to match to the Open Loans Count and Balance

In the example below, replace the macros %VS-OPEN-LOAN and %VS-CHGOFF-LOAN with the matching criteria found in the /ASKPLUS/vsdata/custom/live/vsmacdef

Note: %VS-OPEN-LOAN will contain the macro %VS-ACTIVE-LOAN which should also be replaced by the criteria found in vsmacdef. 

open membrs.report;

FIND PRIMARY=LOAN-FILE;
%VS-OPEN-LOAN AND
NOT (%VS-CHGOFF-LOAN)
END

REPORT
TF1, LOAN-FILE.ACCOUNT, TAB1, COUNT
TF1, LOAN-FILE.BALANCE, TAB2, ADD
END


  • PMANSTAT Reconciliation with Vital Signs Trial balance

Shares Count and Balance 

open membrs.report;

FIND PRIMARY=SHARE-FILE;
SHARE-FILE.DESC-ABRV <> "COS" AND
(SHARE-FILE.BALANCE <> 0 OR SHARE-FILE.CONTROL-FLAGS(21) <> " ")
END

REPORT
TF1, SHARE-FILE.ACCOUNT, TAB1, COUNT
TF1, SHARE-FILE.BALANCE, TAB2, ADD
END


Loans Count and Balance

Note: "O","T" can be modified to reflect the vTB_Exclude_LoanAction list found in vitalsigns.xls 

open membrs.report;

FIND PRIMARY=LOAN-FILE;
LOAN-FILE.ACTION <> "O","T" AND
(LOAN-FILE.BALANCE <> 0 OR
 LOAN-FILE.CREDIT-LIM > 0)
END

REPORT
TF1, LOAN-FILE.ACCOUNT, TAB1, COUNT
TF1, LOAN-FILE.BALANCE, TAB2, ADD
END

Note: If the Loan counts and balances are higher in Vital Signs compared to PMANSTAT, use the following to find other Actions to add to vTB_Exclude_LoanAction in vitalsigns.xls : 

FIND PRIMARY=LOAN-FILE;
LOAN-FILE.ACTION <> "D","O","T" AND
(LOAN-FILE.BALANCE <> 0 OR
   LOAN-FILE.CREDIT-LIM > 0)
END

R
S1, ACTION
T1, ACTION, TAB1
T1, ACCOUNT, TAB2, COUNT
END

Restore/Extract Prior EOM Report Databases

Step 1 Choose where the desired data will be restored into (eloq-TEST or eloq-TRAIN) Enter this location into the /ASKPLUS/vsrvtcp.ini file by doing the following:

Login to HPUX as the askplus user Edit /ASKPLUS/vsrvtcp.ini At the end of the file, you will find the [vsdata_live_restore] section, modify "EQ_DBSERVER" to the correct value example : 

[vsdata_live_restore]
login=bolive
Directory=/var/summit/spectrum/LIVE/vsdata
TEMP=/var/summit/spectrum/LIVE/vsdata/temp
EQ_DBSERVER=localhost:eloq-TEST
script_path=/ASKPLUS/vsdata/scripts
custom_path=/ASKPLUS/vsdata/custom/live
Vmgr=/ASKPLUS/vsdata/custom/live/vmgr_eom


Step 2 - (Required only during INITIAL Setup/Extract for Vital Signs)

Restore the year end membrs.report and membr2.report databases to the Eloquence instance you selected in step 1.

Run the extracts for the year end that was restored in step 2 

Login as bolive
cd /var/summit/spectrum/LIVE
run /VSJOBS/JVSLOAD_MBRSHLN restore 20101231


Step 3 - (Optional)

Restore any prior month end membrs.report and membr2.report databases to the Eloquence instance you selected in step 1.

Run the extracts for the month end that was restored: 

Login as bolive
cd /var/summit/spectrum/LIVE
/VSJOBS/JVSLOAD_MBRSHLN restore 20110131

Repeat step 3 for all the months that you want to load


Step 4

Process the new EOM extracts to the Vital Signs documents on the Windows Server – login bolive – cd /var/summit/spectrum/LIVE – /VSJOBS/JVSRELOAD MBRSHLN_Monthly YYYYMMDD – YYYYMMDD must be the most recent month end extract or most recent month end available on the Windows Server hosting Vital Signs Once the RELOAD has completed your new data will be available to view in Vital Signs.


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.


Schedule Training

Once Vital Signs has been installed, configured and is running nightly, the initial Training via Webinar can be scheduled. Contact training@vital-soft.com for more information.

Retrieved from "https://wiki.vital-soft.com/index.php?title=Vital_Signs_New_Install&oldid=770"