Vital Signs Upgrade to 1.6

Summary

Instructions for Upgrading to 1.6 from 1.5

Download Vital Signs 1.6

Download Vital Signs for HPUX Download Vital Signs for Windows

Staged Upgrade

Windows

Install Qlikview 11 Client

Install Qlikview 11 Client

Setup Staging Directory

Login to the Windows server as the vitalsigns administrator

Create a directory named v16_vitalsigns

Extract the 1.6 Vitalsigns zip files (VSIGNS-Windows-16xx.zip) into v16_vitalsigns

Rename CU1 to match the production vitalsigns/YOURCU acronym.

Copy the production config files (No Samp Files) from vitalsigns\YOURCU\data\config\ contents into v16_vitalsigns\YOURCU\data\config\

• Carefully merge vitalsigns.xls with vitalsigns-samp.xls
  • In the vitalsigns.xls on the GlobalVars sheet
    • Make sure vUseAcctXref = 1
    • Make sure that vReportFrequencies exists : Daily, Weekly, Monthly
  • Save vitalsigns-samp.xls to vitalsigns.xls

Carefully merge membership_analysis.xls with membership_analysis-samp.xls NOTE : there is a new LN_VAR_RATE_CODE dimension

• Save membership_analysis-samp.xls to membership_analysis.xls

Carefully merge documentdistribution.xls with documentdistribution-samp.xls

• Save documentdistribution-samp.xls to documentdistribution.xls

Carefully merge VS_BRANCH_INFO.xls with the VS_BRANCH_INFO-samp.xls

• Save VS_BRANCH_INFO-samp.xls to VS_BRANCH_INFO.xls
• BranchReassign.xls
  • If this files doesn't exist, review the Vital Signs-v15 - Transaction Analysis Setup.pdf
  • Rename BranchReassign.xls BranchReassign-temp.xls until you have all of the Branch Numbers for the Credit Union and their corresponding drawer numbers (Including Virtual Branches)
  • Get a list of the Branch numbers and associated drawer numbers for the CU
    • Virtual Branches are supported as well - A Virtual Branch is a Branch number that does not exist in Spectrum but can be assigned to real drawer numbers and tracked in Transaction Analysis
  • Important - If BranchReassign.xls is found without being completely filled out, any matching drawer numbers with a 0 branch will be dropped from Vital Signs. It is VERY important to get all of the branch information correct the first time. It is important to also list reserved drawer numbers that can potentially be assigned to a branch in the future.

Copy Data_Change-samp.xls as Data_Change.xls

Merge vitalsigns/YOURCU/data/config/start_vsigns_srv.vbs with start_vsigns_srv.samp

Merge vitalsigns/YOURCU/data/config/vsigns_srv.ini with vsigns_srv.samp

NOTE: Set QV_UNICODE in vsigns_srv.ini with QlikView 11 compatible UTF-16LE

QV_UNICODE   "UTF-16LE"

Merge Custom Presentation Document Changes

Open the following presentation level documents in 2 QlikView windows side by side NOTE : the left qlik document should be from the production vitalsigns\YOURCU and the right from the v16_vitalsigns.

Compare the bookmarks/reports/Custom Charts in each of the documents. Export/Import any custom reports/bookmarks to the new Qvw files, copy any Custom Charts to the new Qvw files

• Daily_Membership_Summary.qvw
• Weekly_Membership_Summary.qvw
• Monthly_Membership_Summary.qvw
• Membership_Analysis_by_ACCOUNT.qvw
• Membership_Analysis_by_SSN.qvw (Might not be in use)
• Transaction_Analysis.qvw
• Loan_Application.qvw
• Spectrum_Data_Change.qvw

Populate New Documents

Backup the qvd directory as qvd_v15

Edit v16_vitalsigns\bin\custom\Set_Custom_Paths.txt and set the QVDataPath to the live path containing the qvd directory

QVDataPath = 'C:\vitalsigns\YOURCU\data\';

Membership_Analysis_by_ACCOUNT

• Open v16_vitalsigns/YOURCU/data/Read_Qvd_Membership_Analysis.qvw
  • Click File->Reload
  • Save the document when it has finished reloading

• Open v16_vitalsigns/YOURCU/data/Read_Qvd_Membership_Analysis_by_ACCOUNT.qvw
  • Click Filed->Reload
  • Save the document when it has finished reloading

• Open v16_vitalsigns/YOURCU/Membership_Analysis_by_ACCOUNT.qvw
  • Click File->Reload
  • Save the document when it has finished reloading
  • When reloading Membership_Analysis_by_ACCOUNT for the very first time do the following:
    • Select the Mbr Select tab
    • Click the "Clear and Set all to Open" button
    • Select the Current Date in the upper left
    • Right click the Date select box and click properties and browse to the General Tab
    • Enable the "Always 1 selected" option, hit OK
    • Save the document.

• Look at the Mbr Attributes as well to make sure things look as they should
  • • Browse to the Overview Sheet and click the button labeled "Post Reload (Local Access Only)"
    • Verify that the Attributes now look correct
    • Hit Clear
    • Select the Mbr Select Sheet
    • Save the document

Loan Application (If in Use)

• Reload and Save
  • v16_vitalsigns\YOURCU\data\Read_Qvd_Loan_Application.qvw
  • v16_vitalsigns\YOURCU\Loan_Application.qvw

Spectrum_Data_Change

• Reload and Save
  • v16_vitalsigns\YOURCU\data\Read_Qvd_Data_Change.qvw
  • v16_vitalsigns\YOURCU\Spectrum_Data_Change.qvw

Transaction_Analysis

• Reload and Save
  • v16_vitalsigns\YOURCU\data\Read_Qvd_Transaction_Analysis.qvw
  • v16_vitalsigns\YOURCU\Transaction_Analysis.qvw

HPUX

Login as the askplus user

Copy the vsdata directory to vsdata-bkup-YYYYMMDD

cd /ASKPLUS
cp -Rp vsdata vsdata-bkup-20140201

As the askplus user, transfer binary VSIGNS-HPUX-16xx.gz into /ASKPLUS/ and unzip/untar it :

gunzip VSIGNS-HPUX-1601.gz
tar -xvf VSIGNS-HPUX-1601

Merge vitalsigns.ini with vitalsigns.samp

Merge vsreload.ini with vsreload.samp

Place the new Spectrum_Data_Change file for the specific CPU type (Itanium/PA-Risc) in /ASKPLUS

• datachng.sl (.so for Itanium)
• (owner askplus:users and 750 permissions)

Confirm that the /VSJOBS symbolic link exists :

Example:

$ ls /VSJOBS
JVSLOAD_GLDATA      JVSLOAD_HIST        JVSLOAD_MBRSHLN
JVSRELOAD           JVSLOAD_OANR

If the /VSJOBS symbolic link does not exist, login as root and create it :

ln -s /ASKPLUS/vsdata/jobs /VSJOBS

Check for custom attributes in the /ASKPLUS/vsdata-bkup-CCYYMMDD/scripts/VSCALC-CUSTOM-ATTR file

more /ASKPLUS/vsdata-bkup-CCYYMMDD/scripts/VSCALC-CUSTOM-ATTR

• If custom criteria exists, merge it into the /ASKPLUS/vsdata/scripts/VSCALC-CUSTOM-ATTR

Verify the following macros in /ASKPLUS/vsdata/custom/live/vsmacdef

NOTE : Compare the vsmacdef against the new version in /ASKPLUS/vsdata/custom/test/

• If site uses OANR

Macro VS-EXTRACT-OANR = 1

• If the site has visa info in Spectrum

Macro VS-EXTRACT-VISAINFO = 1

• If the site uses lender

Macro VS-EXTRACT-LOANAP = 1

Verify the following macros in /ASKPLUS/vsdata/custom/live/vsmacdef under Macro VS-CHGOFF-LOAN

** Added for Trial Balance extracts:
Macro VS-TRBAL-SHARE    = (SHARE-FILE.BALANCE <> 0 OR SHARE-FILE.CONTROL-FLAGS(21) <> " ")
Macro VS-TRBAL-LOAN     = (LOAN-FILE.BALANCE <> 0 OR LOAN-FILE.CREDIT-LIM > 0)

*** Use the following macros if you want to include non-zero escrow balance loans in the trial bal chart
*** - The macros with the same names (below) MUST be disabled with comments.
*Macro VS-TRBAL-INC-ESCTOTS = 1
*Macro VS-TRBAL-ESCROW-LINK = link l1, account splice "-" splice !format("99", suffix) :: esctots.acct-sfx-key
*Macro VS-TRBAL-ESCROW-MBR = (!range((LOAN-ADDENDUM.BALANCE <> 0, $MISSING), "1/"))
*Macro VS-TRBAL-ESCROW-LN = (ESCTOTS.ESCROW_BALANCE <> 0, $MISSING)

*** Use the following macros if zero balance escrow loans Should NOT be included
*** - The macros with the same names (above) MUST be disabled with comments.
Macro VS-TRBAL-INC-ESCTOTS = 0
Macro VS-TRBAL-ESCROW-LINK = * No Link
Macro VS-TRBAL-ESCROW-MBR = ($FALSE)
Macro VS-TRBAL-ESCROW-LN = ($FALSE)

Loan_Application changes to /ASKPLUS/vsdata/vsreload.ini

• If the CU uses lender, uncomment the loanap read and presentation level tasks in the [MBRSHLN_Daily] group

[MBRSHLN_Daily]
...
#task15=Read_Qvd_Loan_Application
task16=Read_Qvd_Data_Change
task21=Membership_Analysis_by_ACCOUNT
#task22=Membership_Analysis_by_SSN
task23=Daily_Membership_Summary
#task24=Loan_Application
task25=Spectrum_Data_Change

Going Live

Windows

Login to Windows as the Vital Signs admin user

Open Task Manager and end the process named python.exe *32 - This is the Vital Signs Listener

Email the end users that VitalSigns will be down for a while during the migration to QlikView 11 Server

Open the Administrative Tools->Services window and stop the QlikView Server services from top to bottom

Open Windows Explorer and browse to the vitalsigns directory

Backup v15 files

Copy the bin directory to bin_v15

Change directory into YOURCU/data

Create a folder Presentation-Level_v15

Copy all of the vitalsigns/YOURCU/ qvw files into vitalsigns/YOURCU/data/Presentation-Level_v15

Create a directory named Read-Level_v15

Copy all of the vitalsigns/YOURCU/data/*.qvw files into vitalsigns/YOURCU/data/Read-Level_v15/

Copy vitalsigns\bin to bin_v15

Copy vitalsigns\YOURCU\data\config to config_v15

Copy vitalsigns\YOURCU\data\mbrshln to mbrshln_v15

Copy vitalsigns\YOURCU\data\hist to hist_v15

Merge 1.6 files into production

Copy all of the files from v16_vitalsigns/bin/ to vitalsigns/bin/

Copy all of the files from v16_vitalsigns/YOURCU/data/config/ to vitalsigns/YOURCU/data/config/

Copy the Read Level qvw file from v16_vitalsigns/YOURCU/data/mbrshln/ to vitalsigns/YOURCU/data/mbrshln/

Copy the Read Level qvw file from v16_vitalsigns/YOURCU/data/hist/ to vitalsigns/YOURCU/data/hist/

Copy all of the Read Level qvw files from v16_vitalsigns/YOURCU/data/ to vitalsigns/YOURCU/data/

Copy all of the Presentation Level qvw files from v16_vitalsigns/YOURCU/ to vitalsigns/YOURCU/

Install Qlik 11 Server x64

Installing Qlikview 11 Server

Try to connect to the Server with the Qlik 11 client on another machine and browse the new Vital Signs documents

HPUX

Gather the latest CMNDFILE

login as bolive
/VSJOBS/JVSLOAD_HIST CMNDFILE=1

Test run the nightly jobs

login as bolive
/VSJOBS/JVSLOAD_HIST

login bolive
/VSJOBS/JVSLOAD_MBRSHLN

Start the Python Listener on the Windows server (Scheduled Task or data\config\start_vsigns_srv.vbs)

Test the framework with a simple reload

login bolive
/VSJOBS/JVSRELOAD Transaction_Analysis

Populate the Weekly Document using the last Sunday date

login bolive
/VSJOBS/JVSRELOAD MBRSHLN_Weekly CCYYMMDD

Populate the Monthly Summary Document using the last EOM date

login bolive
/VSJOBS/JVSRELOAD MBRSHLN_Monthly CCYYMMDD

UC4

Modify the UC4 jobs as shown here :

Daily Jobs
  HIST DAILY
    ##Run nightly- between 12:01 and 1 am.
    ##Login as bolive
    set -e
    /VSJOBS/JVSLOAD_HIST
			
  MEMBERSHIP_ANALYSIS
    ##Run nightly – prior to 5am
    ##Do not run on days when the EOM job (see below) is scheduled
    ##Login as bolive
    set -e
    /VSJOBS/JVSLOAD_MBRSHLN


Month End Jobs
  MEMBERSHIP_ANALYSIS
    ##Run 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 being
    #closed

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

If you have any issues, please contact support at 1-800-848-2576 ext 21 or email support@vital-soft.com