Difference between revisions of "Vital Signs New Install"
>Johno (→Configuration Meeting) |
>Johno (→UC4 Job Setup) |
||
Line 392: | Line 392: | ||
'''MEMBER/SHARE/LOAN Extract''' | '''MEMBER/SHARE/LOAN Extract''' | ||
− | :The daily job should run every night, '''except | + | :The daily job should run every night, '''except at month-end'''. Generally should be scheduled to run after midnight, but can be run anytime after CU close. |
## MBRSHLN - DAILY | ## MBRSHLN - DAILY |
Revision as of 18:37, 30 November 2015
Contents
- 1 Overview
- 2 HPUX Server Requirements
- 3 Windows Server Requirements
- 4 Initial Meeting
- 5 Configuration Meeting
- 6 Installation
- 7 Post Install Configuration
- 8 Transaction Analysis Initial Run
- 9 Membership Analysis Initial Run
- 10 Trial Balance Reconciliation
- 11 Trial Balance Reconciliation Askplus Queries
- 12 Membership Totals Reconciliation
- 13 Restore/Extract Prior EOM Report Databases
- 14 UC4 Job Setup
- 15 Schedule Training
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
- Python configObj Library
- AskPlus 8.3.3 or later
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
- .NET 4.0 framework
- IIS FTP Server
- QlikView Server x64
- QlikView Client x64
- Python 2.7
- Open Office Calc / Excel 2007 or later
- The Vital Signs Document Distribution module is not supported by Open Office. Excel 2007 or newer is required.
- Note : Office 2010/2012 require the following changes for Document Distribution to generate xls/xlsx files : Vital_Signs_FAQ#GetExcelWorkbookObj
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
Credit Union Specific Customization
Share and Loan Product Grouping
Installation
HPUX
Windows Server x64
- Installing Python on Windows
- Installing the Pyparsing Python Module
- Installing Qlikview Client x64
- Installing Qlikview Server x64
- Installing Vital Signs on Windows
- Setup Vital Signs Listener Task
Post Install Configuration
Membership Analysis Initial Setup
Transaction Analysis Initial Setup
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
Trial Balance Reconciliation
The Trial Balance Reconciliation chart is designed to help reconcile the Share and Loan counts & balances to the Spectrum Trial Balance report (PGNTB - Member Trial Balance)
The chart can be found in the Membership_Analysis_by_ACCOUNT document under the Member Charts tab
The chart data is affected by the following Configuration Files in vitalsigns\YOURCU\data\config
- VitalSigns.xls
- Contains the variables to exclude specific shares and loans (vTB_Exclude_LoanAction, vTB_Exclude_Collateral and vTB_Exclude_DescAbrv)
- Membership_Analysis.xls
- Contains the balance ranges used in this chart on the Ranges sheet (TRIAL-BAL)
The chart is divided into two main sections: Balance by Account and Balance by Suffix
Balance by Account
- Balance ranges are calculated based on the total balance for each member account. These totals should tie back to the Summit Trial Balance.
Balance by Suffix
- Balance ranges are determined by the individual suffix balance.
Closed Suffixes: All CLOSED suffixes that qualify for the trial balance
- Closed shares qualify if the balance is non zero, or if the suffix is a share draft account
- Closed loans qualify if the balance is non zero, or if the credit limit is greater than zero
Excluded Suffixes: All OPEN suffixes that do NOT qualify for the trial balance
- These are shown this section with negative counts and balances
- These are ALSO included in the Open Suffixes section
Open Suffixes: All OPEN suffixes
- This total should match the Vital Signs Open Share/Loan totals on the status bar
Shares Breakdown Criteria
- Included:
- Balance <> 0
- Share Draft Acconts (CF(21) <> " ")
- Excluded:
- Charged Off shares
- Desc Abrv = $(vTB_Exclude_DescAbrv)
Loans Breakdown Criteria
- Included:
- Balance <> 0
- Credit Limit > 0
- Excluded:
- Charged Off loans
- Action = O,T,A
- Collateral = $(vTB_Exclude_Collateral)
Trial Balance Reconciliation Askplus Queries
Shares Count and Balance by Suffix
- Use the following query in Askplus to match to the Share Count and Balance in the Vital Signs Trial Balance Reconciliation chart
- Note: "COS" can be modified to reflect the vTB_Exclude_DescAbrv list found in vitalsigns.xls
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 by Suffix
- Use the following query in Askplus to match to the Loan Count and Balance in the Vital Signs Trial Balance Reconciliation chart
- Note: "O","T","A" 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","A" 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 or Askplus Queries, 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","A" AND (LOAN-FILE.BALANCE <> 0 OR LOAN-FILE.CREDIT-LIM > 0) END REPORT S1, ACTION T1, ACTION, TAB1 T1, ACCOUNT, TAB2, COUNT END
What to look for if the Open Shares Count or Balance is lower than the Vital Signs status bar
- Check for duplicate Shares in Vital Signs
- Login to the Windows server as the Vital Signs admin user and open the Membership_Analysis_by_ACCOUNT locally
- Click the Custom Charts tab
- Right click the grey area and create a chart, choose straight table
- Add SH_ACCOUNT and SH_SUFFIX as the dimensions
- Add =count(SH_SUFFIX) as an expression
- Click Finish
- Double click the top right column Header =count(SH_SUFFIX)
- Double click it one more time to sort it descending
- If you see counts of 2 for many suffixes, check the SHXREFCCYYMMDD.xls for duplicate values in Column A
- If you see counts greater than 2 for suffix 00 please contact support@vital-soft.com
What to look for if the Open Loans Count or Balance is lower than the Vital Signs status bar
- Check for duplicate Loans in Vital Signs
- Login to the Windows server as the Vital Signs admin user and open the Membership_Analysis_by_ACCOUNT locally
- Click the Custom Charts tab
- Right click the grey area and create a chart, choose straight table
- Add LN_ACCOUNT and LN_SUFFIX as the dimensions
- Add =count(LN_SUFFIX) as an expression
- Click Finish
- Double click the top right column Header =count(LN_SUFFIX)
- Double click it one more time to sort it descending
- If you see counts of 2 for many suffixes, check the LNXREFCCYYMMDD.xls for duplicate values in Column A
Membership Totals Reconciliation
Open Deposit Count and Balance
- Use the following query in Askplus to match to the Open Shares Count and Balance in the Membership_Analysis_by_ACCOUNT status bar
- Note: 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
Open Loan Count and Balance
- Use the following query in Askplus to match to the Open Loans Count and Balance
- Note: 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. %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
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
HISTORY Extract
- The HISTORY extract job should run every day after midnight. There is no special end of month version of the history job.
## HIST - DAILY ## Run nightly- between 12:01 and 1 am, including weekends ## Login as bolive set -e /VSJOBS/JVSLOAD_HIST
MEMBER/SHARE/LOAN Extract
- The daily job should run every night, except at month-end. Generally should be scheduled to run after midnight, but can be run anytime after CU close.
## MBRSHLN - DAILY ## Run nightly – should be scheduled to complete prior to 6am ## Do NOT run on the Vital Signs EOM ## Login as bolive set -e /VSJOBS/JVSLOAD_MBRSHLN
- At month-end, a special version of the job must be run specifying the EOM parm and the date. This job will read the REPORT database, so it must be run after the report database has been updated. The daily MBRSHLN extract should not be run at month-end.
## MBRSHLN - EOM ## Run on the Vital Signs EOM after report databases have been created ## Login as bolive set -e /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.