Vital Soft Wiki - User contributions [en]

Transaction Configuration Overview

2025-09-29T17:00:05Z

Johno:

=Summary=
The primary goal of the Transaction Analysis document is to display all of the transactions performed at physical branch locations. The document uses the information stored in the SHARE-HISTORY and LOAN-HISTORY datasets. Since there is usually more information in these sets than what is necessary, the document has multiple types of filters that need to be set up before first use. The three levels of filters are Branch Filtering, Teller Filtering, and Command Filtering. By configuring these options it is possible to tailor the document to display only the desired transactions.

Note: all of the underlying history is archived, even if it is filtered out of the final Vital Signs document. None of the filters discussed in this overview permanently removes archived information.

=Types of Filters=

==Branch Filtering==

Branch-level filtering is the primary way the Transaction Analysis document removes unwanted transactions. A list of the desired branches is specified in a spreadsheet and any transactions not performed at these branches are removed from the document.

The name of the configuration spreadsheet is brinfoYYYYMMDD.xls. It is stored in the ../cuname/data/config Vital Signs directory.

Note that if the option to use accounting centers as branches is set, the brinfo file should contain a list of the desired centers.

The brinfo file is also where the branch’s lobby and extended hours are specified. These hours are for reporting purposes only -- not for transaction filtering. Even if a transaction occurs outside of the specified open and close hours, it is still reported (provided it meets the other filtering conditions). The closing hours can affect how teller hours are calculated -- see the section ‘Calculating Time Worked’ later in this overview.

==Teller Filtering==

There are many system-generated teller codes used by Spectrum for its back office processing. There are also employees who may process transactions that you do not wish to see in the final document. The teller-level filtering enables any transactions associated with these teller codes to be removed.

By default, the Transaction Analysis document will attempt to exclude the system-generated tellers. Any teller initials that are greater than 3 characters, as well as teller initials that do not start or end with a letter, are excluded.
For example, the teller code:

:'''AB1'''

would be excluded, but the code:

:'''C2D'''

would be allowed, since the first and last characters were alphabetic.

For back office employees with valid teller codes that you wish to exclude, use the TC_TELLERS.xls configuration file. It is also possible to override the default automatic exclusion here as well. If, for example, AB1 was really a valid teller, its code could be changed to not exclude it automatically. See the ‘Configuring the TC_CODES and TC_TELLER Files’ section for more information.

Finally, it is possibly to change the rules used to identify system-generated tellers. If your site has different parameters for this, let us know and we will customize the document’s code for you.

==Command Filtering==

The final way to filter the incoming history data is by the type and command of each record. The type of command is the Spectrum TYPE field. For example, types of 100, 101, and 102 are all monetary transactions. By default, all types are allowed in to the final Transaction Analysis document. It is possible to remove unwanted types by specifying them in the main ‘VitalSigns.xls’ configuration file.

The setting is on the ‘Transaction’ sheet in the xls file, and is called

:'''vTR_Exclude_Type'''

Use a semi-colon separated list of value to specify which types to exclude. For example, types 499, 699 and 999 are all system-generated records used to store extra information about other commands in case an UNDO is performed. These records can be excluded by listing them as

:'''499;699;999'''

for this setting.

Individual commands can be filtered as well. The command codes are the 4-letter Spectrum commands. Use the

:'''vTR_Exclude_Cmnd'''

setting for this. An example is the cash dispenser command DISP. Many sites do not want occurrences of this command reported so it is filtered out. If there are other commands you wish filtered, use a semi-colon separated list.

=Automatic Duplication Filtering=

Some history transactions that are stored in the database are not unique. It is possible for the same record to be stored multiple times. This can affect the transaction counts reported by Vital Signs.

There is a setting in the VitalSigns.xls file that can affect how history records get filtered. This is the

:'''vTR_Count_Dup_Trans'''

setting. There are three possible values: ALL, EXACT, KEY

The ‘ALL’ value allows all duplicate records into the document.

The ‘EXACT’ value will compare the entire history record of each entry and only allow distinct values into the document.

The ‘KEY’ value is similar to ‘EXACT’ but will only compare the non-binary portions of non-monetary transactions when filtering. This is important for a single datachange command that might be stored as multiple records. The binary information is different for each record, so ‘EXACT’ would not filter the duplicates, even though the multiple records were really one command.

‘KEY’ is the recommended setting for all new installs. The other options are mainly to support existing sites that previously used the older settings.

=Configuring BRINFO Files=

The Transaction Analysis document uses a set of configuration files to decide which branches to include.

This is done with the files called brinfo########.xls, where the ####### is a CYMD date. There should already be a sample in your data/config directory on the VitalSigns Windows server.

The brinfo file(s) specify the branches and their hours. If you only put one instance of the file on the server, the branches/times will be used for the entire time frame (default is 12 months) tracked by the document. If your branch hours ever change, ie you need to add a new branch or modify drive-thru hours, you make another instance of the brinfo file with the date you want the new times to take effect. After a few years, it would be normal to have three or four different brinfo files on the system.

Here are the guidelines for setting up a brinfo file.

# You should list each branch (by branch number) that you want tracked. These should be any branch where transactions are done by physical tellers (whether it is an actual branch or the call center.) Do not include any back-office or automated branches.
# Each branch should have seven lines, one for each day of the week. The sample xls file can be used as a model. Both the day names and numbers are listed, so there would be no confusion on whether Sunday or Monday was the first day of the week.
# The next two columns, XLS_OPEN and XLS_CLOSE are the lobby hours of the branch. These should be in a 24-hour clock format, rounded to the nearest half-hour period. Note that all transactions, regardless of time, are included in the document, so you don't have to worry about listing "closed" as 5:00 and losing transactions that occur at 5:01. The lobby hours are only there to help identify transactions that happen outside of the normal open hours.
# The XLS_FTE is an obsolete field and has been deprecated. It is there only for compatability with the older Teller Activity document.
# The XLS_EXT_OPEN and XLS_EXT_CLOSE columns are if you want to track drive-thru (or any special early/late hours) separately from the main lobby hours. The EXT_OPEN time should be earlier than the XLS_OPEN time, and the EXT_CLOSE time should be later than the XLS_CLOSE time. If there are no extended times, just put 0. There is a special case supported if you want a day to be considered all extended times, ie a Saturday w/ only drive-thru hours. In this case, set the XLS_OPEN and XLS_CLOSE to 0, and set XLS_EXT_OPEN and XLS_EXT_CLOSE to the branch hours for that day.
# For Sundays (and possibly Saturdays) when the branches are regularly closed, put 0's for all 4 open/close hours columns. Note that closed days due to holidays or special circumstances are handled elsewhere. You should only create a new brinfo file when a branch's regular schedule changes, or a new branch is added.
# The EXT_FTE is an obsolete field and has been deprecated. It is there only for compatability with the older Teller Activity document.

Date the new brinfo file with today's date and copy it to the data/config directory. If you know occurrences in the last two years where branch hours were changed, you may want to create a second brinfo file to reflect the old times. Be sure to rename/remove the sample brinfo20080101.xls file if it exists.

* Click [[brinfoCCYYMMDD.xls|here]] for more information on how to set up the brinfo file.

* Click [[vs_branch_info.xls|here]] for more information on adding new branches to the vs_branch_info file.

=Configuring the TC_CODES and TC_TELLER Files=

Vital Signs gives you the ability to group sets of tellers together, enabling quick selection. It also uses these codes to filter unwanted tellers (back office or automated tellers, for example) from the document. Two spreadsheet configuration files are used for this: TC_CODES.xls and TC_TELLERS.xls.

Both of these spreadsheets are different from the brinfo files in that there is always only a single version of each on the system. The brinfo files are date-stamped, ie brinfo20090301.xls, and multiple dates are allowed to document the changes in branch hours over time. Although there is always only one TC_TELLERS.xls file, it allows you to specify date ranges inside the document to mark teller code changes that occur on specific dates.

You should always back up the old TC_CODES and TC_TELLERS files before overwriting them with a new version.

The first file (TC_CODES) should already be on your system -- you can modify it to contain the different codes you want to use for classifying the people who perform transactions.

Each code must be assigned to a group, either "T" for the teller group, or "O" for the others. The Teller Group should include all employees whose MAIN function is to perform transactions. The Other Group is for people who perform transactions when needed but it is not their main function (Ie Managers or Loan Officers).

You can have multiple codes within the same group, ie "Full Time Teller", "Floating Teller" etc. Each of these codes will be selectable in the Vital Signs document. You do not want to make the codes too specific though, or they can become too difficult to maintain.

Once the codes are set up, you can create the TC_TELLERS.xls sheet. The best way to do this is to go to the Maintenance tab and export the teller list to create an Excel file. Vital Signs will give you a table with all the tellers in your system who have performed transaction in the past 12 months. You can right click this table and choose "export" and create an xls file from it.

The xls file will have all of your current tellers, with either an <nowiki><X></nowiki> or an <nowiki><M></nowiki> as the teller code. An <nowiki><X></nowiki> means that this teller code should be excluded and no transaction counts for the teller will be imported. We have some rules to automatically mark 4 character teller codes, as well as three char codes that start or end w/ a number (ie "AT1") as excluded by default. If there is a teller code you want to track that is marked as excluded, you can change it to a valid code and all of the old transaction will be included on the next refresh. (All excluded transactions are archived -- they are just not presented in the final document.)

An <nowiki><M></nowiki> code means the teller does not yet have a valid code defined. You will need to change the code to one of the new codes you set up in TC_CODES, ie "TLR" or "FLT". There are columns to add a date range in case a teller's status changes over time. (This is meant more for a permanent change, like a promotion from CSR to Asst. Manager -- you do not want to create roles so specific that a single teller is constantly moving between them.)

As new employees start performing transactions, they will be added to the Vital Signs document as <nowiki><M></nowiki>. The document will remind you on the "Details" tabs that there are unassigned transactions in the current date range. This means you should re-export the teller table from the maintenance page and update the codes.

Updating the TC_TELLERS file is necessary to maintain the teller codes, otherwise new tellers will keep the <nowiki><M></nowiki> (missing) status.

Vital Signs will never overwrite any entry you place (with one exception --see below) so it is possible for you to be proactive and add new tellers to the system before they have any transactions. In this case, you would need to add the entire row of information directly to the TC_TELLERS.xls file instead of re-exporting the table from inside the document.

There is one other system status, the unassigned <nowiki><U></nowiki> status. This is a special marker to alert you of a date range problem with a teller, ie an overlapping date range where the teller might have two (or no) roles assigned. It shouldn't come up for any teller where you haven't modified the effective dates. In the case of a date conflict however, the system will create a new entry for the employee for the conflicting date range and add a <nowiki><U></nowiki> status. Any part of the date ranges where there was no conflict will be preserved with the original status.

Finally, you might notice some of the automatically generated teller entries contain teller names, while some only have their initials repeated in the name column. If the name is missing, it means the teller no longer exists in the TELLER-INFO dataset and their name could not be identified. Remember that ALL transactions in the last 12 months are used, so it is common to have transactions performed by former employees. If you know the names of these tellers, you can add them to the spreadsheet. This is also true if you want to change the name of an existing teller for reporting purposes. The new name will take precedence over the TELLER-INFO name. Note -- this is for names column only, not the initials column. You cannot change someone's initials since it is the key value used to identify the transactions -- they would just show as <nowiki><M></nowiki> with their original initials the next time you refreshed the document.

* Click [[tc_tellers.xls|here]] for more information on how to set up the tc_tellers file.

* Click [[tc_codes.xls|here]] for more information on how to set up the tc_codes file.

For questions please contact support@vital-soft.com or 1-800-848-2576 ext 21

Transaction Configuration Overview

2025-09-29T16:56:50Z

Johno:

=Summary=
The primary goal of the Transaction Analysis document is to display all of the transactions performed at physical branch locations. The document uses the information stored in the SHARE-HISTORY and LOAN-HISTORY datasets. Since there is usually more information in these sets than what is necessary, the document has multiple types of filters that need to be set up before first use. The three levels of filters are Branch Filtering, Teller Filtering, and Command Filtering. By configuring these options it is possible to tailor the document to display only the desired transactions.

Note: all of the underlying history is archived, even if it is filtered out of the final Vital Signs document. None of the filters discussed in this overview permanently removes archived information.

=Types of Filters=

==Branch Filtering==

Branch-level filtering is the primary way the Transaction Analysis document removes unwanted transactions. A list of the desired branches is specified in a spreadsheet and any transactions not performed at these branches are removed from the document.

The name of the configuration spreadsheet is brinfoYYYYMMDD.xls. It is stored in the ../cuname/data/config Vital Signs directory.

Note that if the option to use accounting centers as branches is set, the brinfo file should contain a list of the desired centers.

The brinfo file is also where the branch’s lobby and extended hours are specified. These hours are for reporting purposes only -- not for transaction filtering. Even if a transaction occurs outside of the specified open and close hours, it is still reported (provided it meets the other filtering conditions). The closing hours can affect how teller hours are calculated -- see the section ‘Calculating Time Worked’ later in this overview.

Click [[brinfoCCYYMMDD.xls|here]] for more information on how to set up the brinfo file.

Click [[vs_branch_info.xls|here]] for more information on adding new branches to the vs_branch_info file.

==Teller Filtering==

There are many system-generated teller codes used by Spectrum for its back office processing. There are also employees who may process transactions that you do not wish to see in the final document. The teller-level filtering enables any transactions associated with these teller codes to be removed.

By default, the Transaction Analysis document will attempt to exclude the system-generated tellers. Any teller initials that are greater than 3 characters, as well as teller initials that do not start or end with a letter, are excluded.
For example, the teller code:

:'''AB1'''

would be excluded, but the code:

:'''C2D'''

would be allowed, since the first and last characters were alphabetic.

For back office employees with valid teller codes that you wish to exclude, use the TC_TELLERS.xls configuration file. It is also possible to override the default automatic exclusion here as well. If, for example, AB1 was really a valid teller, its code could be changed to not exclude it automatically. See the ‘Configuring the TC_CODES and TC_TELLER Files’ section for more information.

Finally, it is possibly to change the rules used to identify system-generated tellers. If your site has different parameters for this, let us know and we will customize the document’s code for you.

Click [[tc_tellers.xls|here]] for more information on how to set up the tc_tellers file.

Click [[tc_codes.xls|here]] for more information on how to set up the tc_codes file.

==Command Filtering==

The final way to filter the incoming history data is by the type and command of each record. The type of command is the Spectrum TYPE field. For example, types of 100, 101, and 102 are all monetary transactions. By default, all types are allowed in to the final Transaction Analysis document. It is possible to remove unwanted types by specifying them in the main ‘VitalSigns.xls’ configuration file.

The setting is on the ‘Transaction’ sheet in the xls file, and is called

:'''vTR_Exclude_Type'''

Use a semi-colon separated list of value to specify which types to exclude. For example, types 499, 699 and 999 are all system-generated records used to store extra information about other commands in case an UNDO is performed. These records can be excluded by listing them as

:'''499;699;999'''

for this setting.

Individual commands can be filtered as well. The command codes are the 4-letter Spectrum commands. Use the

:'''vTR_Exclude_Cmnd'''

setting for this. An example is the cash dispenser command DISP. Many sites do not want occurrences of this command reported so it is filtered out. If there are other commands you wish filtered, use a semi-colon separated list.

=Automatic Duplication Filtering=

Some history transactions that are stored in the database are not unique. It is possible for the same record to be stored multiple times. This can affect the transaction counts reported by Vital Signs.

There is a setting in the VitalSigns.xls file that can affect how history records get filtered. This is the

:'''vTR_Count_Dup_Trans'''

setting. There are three possible values: ALL, EXACT, KEY

The ‘ALL’ value allows all duplicate records into the document.

The ‘EXACT’ value will compare the entire history record of each entry and only allow distinct values into the document.

The ‘KEY’ value is similar to ‘EXACT’ but will only compare the non-binary portions of non-monetary transactions when filtering. This is important for a single datachange command that might be stored as multiple records. The binary information is different for each record, so ‘EXACT’ would not filter the duplicates, even though the multiple records were really one command.

‘KEY’ is the recommended setting for all new installs. The other options are mainly to support existing sites that previously used the older settings.

=Configuring BRINFO Files=

The Transaction Analysis document uses a set of configuration files to decide which branches to include.

This is done with the files called brinfo########.xls, where the ####### is a CYMD date. There should already be a sample in your data/config directory on the VitalSigns Windows server.

The brinfo file(s) specify the branches and their hours. If you only put one instance of the file on the server, the branches/times will be used for the entire time frame (default is 12 months) tracked by the document. If your branch hours ever change, ie you need to add a new branch or modify drive-thru hours, you make another instance of the brinfo file with the date you want the new times to take effect. After a few years, it would be normal to have three or four different brinfo files on the system.

Here are the guidelines for setting up a brinfo file.

# You should list each branch (by branch number) that you want tracked. These should be any branch where transactions are done by physical tellers (whether it is an actual branch or the call center.) Do not include any back-office or automated branches.
# Each branch should have seven lines, one for each day of the week. The sample xls file can be used as a model. Both the day names and numbers are listed, so there would be no confusion on whether Sunday or Monday was the first day of the week.
# The next two columns, XLS_OPEN and XLS_CLOSE are the lobby hours of the branch. These should be in a 24-hour clock format, rounded to the nearest half-hour period. Note that all transactions, regardless of time, are included in the document, so you don't have to worry about listing "closed" as 5:00 and losing transactions that occur at 5:01. The lobby hours are only there to help identify transactions that happen outside of the normal open hours.
# The XLS_FTE is an obsolete field and has been deprecated. It is there only for compatability with the older Teller Activity document.
# The XLS_EXT_OPEN and XLS_EXT_CLOSE columns are if you want to track drive-thru (or any special early/late hours) separately from the main lobby hours. The EXT_OPEN time should be earlier than the XLS_OPEN time, and the EXT_CLOSE time should be later than the XLS_CLOSE time. If there are no extended times, just put 0. There is a special case supported if you want a day to be considered all extended times, ie a Saturday w/ only drive-thru hours. In this case, set the XLS_OPEN and XLS_CLOSE to 0, and set XLS_EXT_OPEN and XLS_EXT_CLOSE to the branch hours for that day.
# For Sundays (and possibly Saturdays) when the branches are regularly closed, put 0's for all 4 open/close hours columns. Note that closed days due to holidays or special circumstances are handled elsewhere. You should only create a new brinfo file when a branch's regular schedule changes, or a new branch is added.
# The EXT_FTE is an obsolete field and has been deprecated. It is there only for compatability with the older Teller Activity document.

Date the new brinfo file with today's date and copy it to the data/config directory. If you know occurrences in the last two years where branch hours were changed, you may want to create a second brinfo file to reflect the old times. Be sure to rename/remove the sample brinfo20080101.xls file if it exists.

=Configuring the TC_CODES and TC_TELLER Files=

Vital Signs gives you the ability to group sets of tellers together, enabling quick selection. It also uses these codes to filter unwanted tellers (back office or automated tellers, for example) from the document. Two spreadsheet configuration files are used for this: TC_CODES.xls and TC_TELLERS.xls.

Both of these spreadsheets are different from the brinfo files in that there is always only a single version of each on the system. The brinfo files are date-stamped, ie brinfo20090301.xls, and multiple dates are allowed to document the changes in branch hours over time. Although there is always only one TC_TELLERS.xls file, it allows you to specify date ranges inside the document to mark teller code changes that occur on specific dates.

You should always back up the old TC_CODES and TC_TELLERS files before overwriting them with a new version.

The first file (TC_CODES) should already be on your system -- you can modify it to contain the different codes you want to use for classifying the people who perform transactions.

Each code must be assigned to a group, either "T" for the teller group, or "O" for the others. The Teller Group should include all employees whose MAIN function is to perform transactions. The Other Group is for people who perform transactions when needed but it is not their main function (Ie Managers or Loan Officers).

You can have multiple codes within the same group, ie "Full Time Teller", "Floating Teller" etc. Each of these codes will be selectable in the Vital Signs document. You do not want to make the codes too specific though, or they can become too difficult to maintain.

Once the codes are set up, you can create the TC_TELLERS.xls sheet. The best way to do this is to go to the Maintenance tab and export the teller list to create an Excel file. Vital Signs will give you a table with all the tellers in your system who have performed transaction in the past 12 months. You can right click this table and choose "export" and create an xls file from it.

The xls file will have all of your current tellers, with either an <nowiki><X></nowiki> or an <nowiki><M></nowiki> as the teller code. An <nowiki><X></nowiki> means that this teller code should be excluded and no transaction counts for the teller will be imported. We have some rules to automatically mark 4 character teller codes, as well as three char codes that start or end w/ a number (ie "AT1") as excluded by default. If there is a teller code you want to track that is marked as excluded, you can change it to a valid code and all of the old transaction will be included on the next refresh. (All excluded transactions are archived -- they are just not presented in the final document.)

An <nowiki><M></nowiki> code means the teller does not yet have a valid code defined. You will need to change the code to one of the new codes you set up in TC_CODES, ie "TLR" or "FLT". There are columns to add a date range in case a teller's status changes over time. (This is meant more for a permanent change, like a promotion from CSR to Asst. Manager -- you do not want to create roles so specific that a single teller is constantly moving between them.)

As new employees start performing transactions, they will be added to the Vital Signs document as <nowiki><M></nowiki>. The document will remind you on the "Details" tabs that there are unassigned transactions in the current date range. This means you should re-export the teller table from the maintenance page and update the codes.

Updating the TC_TELLERS file is necessary to maintain the teller codes, otherwise new tellers will keep the <nowiki><M></nowiki> (missing) status.

Vital Signs will never overwrite any entry you place (with one exception --see below) so it is possible for you to be proactive and add new tellers to the system before they have any transactions. In this case, you would need to add the entire row of information directly to the TC_TELLERS.xls file instead of re-exporting the table from inside the document.

There is one other system status, the unassigned <nowiki><U></nowiki> status. This is a special marker to alert you of a date range problem with a teller, ie an overlapping date range where the teller might have two (or no) roles assigned. It shouldn't come up for any teller where you haven't modified the effective dates. In the case of a date conflict however, the system will create a new entry for the employee for the conflicting date range and add a <nowiki><U></nowiki> status. Any part of the date ranges where there was no conflict will be preserved with the original status.

Finally, you might notice some of the automatically generated teller entries contain teller names, while some only have their initials repeated in the name column. If the name is missing, it means the teller no longer exists in the TELLER-INFO dataset and their name could not be identified. Remember that ALL transactions in the last 12 months are used, so it is common to have transactions performed by former employees. If you know the names of these tellers, you can add them to the spreadsheet. This is also true if you want to change the name of an existing teller for reporting purposes. The new name will take precedence over the TELLER-INFO name. Note -- this is for names column only, not the initials column. You cannot change someone's initials since it is the key value used to identify the transactions -- they would just show as <nowiki><M></nowiki> with their original initials the next time you refreshed the document.

For questions please contact support@vital-soft.com or 1-800-848-2576 ext 21

Membership analysis.xls

2025-08-06T15:47:01Z

Johno: /* Control Flags */

== Overview ==

The Membership Analysis spreadsheet contains Ranges, Dimensions, Fields and Accounts specific to Vital Signs during the nightly reloads

== Ranges Sheet ==
'''This sheet contains range information used by the Vital Signs Membership_Analysis Application

These ranges are reapplied each time the Membership_Analysis application is reloaded
The assigned range is >= IM_LOW and < The next IM_LOW value specified

The IM_TIER Column is used for setting a hierarchy for the ranges used below'''

''Note: typically this is only used for Credit Tier''

'''SHARE-BAL'''

Used to calculate Share Balance Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
SHARE-BAL Null No Shares
SHARE-BAL Negative
SHARE-BAL 0.00 Zero
SHARE-BAL 0.01 $0.01 to $4
SHARE-BAL 5.00 $5 to $499
SHARE-BAL 500.00 $500 - $999
SHARE-BAL 1,000.00 $1K - $4,999
SHARE-BAL 5,000.00 $5K - $9,999
SHARE-BAL 10,000.00 $10K - $49,999
SHARE-BAL 50,000.00 $50K - $99,999
SHARE-BAL 100,000.00 $100K and over

'''LOAN-BAL'''

Used to calculate Loan Balance Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
LOAN-BAL Null No Loans
LOAN-BAL Negative
LOAN-BAL 0.00 Zero
LOAN-BAL 0.01 $0.01 to $999
LOAN-BAL 1,000.00 $1K to $4,999
LOAN-BAL 5,000.00 $5K to $9,999
LOAN-BAL 10,000.00 $10,000 - $49,999
LOAN-BAL 50,000.00 $50,000 - $99,999
LOAN-BAL 100,000.00 $100K and over

'''TRIAL-BAL'''

Used in the Trial Balance page and should not be modified

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
TRIAL-BAL Negative
TRIAL-BAL 0.00 Zero
TRIAL-BAL 0.01 $0.01 - $10.00
TRIAL-BAL 10.01 $10.01 - $25.00
TRIAL-BAL 25.01 $25.01 - $100.00
TRIAL-BAL 100.01 $100.01 - $500.00
TRIAL-BAL 500.01 $500.01 - $1,000
TRIAL-BAL 1,000.01 $1,000.01 - $2,000
TRIAL-BAL 2,000.01 $2,000.01 - $3,000
TRIAL-BAL 3,000.01 $3,000.01 - $5,000
TRIAL-BAL 5,000.01 $5,000.01 - $10,000
TRIAL-BAL 10,000.01 $10,000.01 - $20,000
TRIAL-BAL 20,000.01 $20,000.01 - $40,000
TRIAL-BAL 40,000.01 $40,000.01 - $100,000
TRIAL-BAL 100,000.01 $100,000.01 and Over

'''MBR-AGE'''

Used to calculate Member Age Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
MBR-AGE Zero (No age)
MBR-AGE 1 Under 16
MBR-AGE 16 16 to 20
MBR-AGE 21 21 to 25
MBR-AGE 26 26 to 30
MBR-AGE 31 31 to 35
MBR-AGE 36 36 to 40
MBR-AGE 41 41 to 45
MBR-AGE 46 46 to 50
MBR-AGE 51 51 to 55
MBR-AGE 56 56 to 60
MBR-AGE 61 61 to 65
MBR-AGE 66 66 to 70
MBR-AGE 71 71 to 75
MBR-AGE 76 76 and over

'''ACCT-AGE'''

Used to calculate Account Age Ranges - how long the member has been a member

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
ACCT-AGE Less than 1 Year
ACCT-AGE 1 1 – 2 Years
ACCT-AGE 3 3 – 5 Years
ACCT-AGE 6 6 – 10 Years
ACCT-AGE 11 11 – 20 Years
ACCT-AGE 21 21 Years +

'''CREDIT-SCORE'''

Used to calculate Credit Score Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
CREDIT_SCORE F F (No Score)
CREDIT_SCORE 1 E E (Less than 520)
CREDIT_SCORE 520 D D (520 - 580)
CREDIT_SCORE 581 C C (581 - 620)
CREDIT_SCORE 621 B B (621 - 700)
CREDIT_SCORE 701 A A (701 - 720)
CREDIT_SCORE 721 A+ A+ (Over 721)

'''DELQ-DAYS'''

Used when displaying Delinquent Loans

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
DELQ-DAYS Current
DELQ-DAYS 1 1-15 Days
DELQ-DAYS 16 16-30 Days
DELQ-DAYS 31 31-60 Days
DELQ-DAYS 61 61-90 Days
DELQ-DAYS 91 91-120 Days
DELQ-DAYS 121 121-180 Days
DELQ-DAYS 181 6 Mths - 1 Year
DELQ-DAYS 366 Over 1 Year

'''CHANGE-BAL'''

Used to calculate balance Changes for both Share and Loan Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
CHANGE-BAL Neg: Over $100K
CHANGE-BAL -99,999.99 Neg: $50K to $100K
CHANGE-BAL -49,999.99 Neg: $10K to $50K
CHANGE-BAL -9,999.99 Neg: $5K to $10K
CHANGE-BAL -4,999.99 Neg: $1K to $5K
CHANGE-BAL -999.99 Neg: .01 to $1K
CHANGE-BAL 0.00 Zero
CHANGE-BAL 0.01 .01 to $1k
CHANGE-BAL 1,000.00 $1K to $5K
CHANGE-BAL 5,000.00 $5K to $10K
CHANGE-BAL 10,000.00 $10,000 - $50K
CHANGE-BAL 50,000.00 $50,000 - $100K
CHANGE-BAL 100,000.00 $100K and over

'''RATES'''

Used to calculate rate ranges for both shares (DIV_RATE) and loans (APR)

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
RATES Negative
RATES 0.00% Zero
RATES 0.00% <= 0.50%
RATES 0.50% >= 0.50% < 1.00%
RATES 1.00% >= 1.00% < 1.50%
RATES 1.50% >= 1.50% < 2.00%
RATES 2.00% >= 2.00% < 2.50%
RATES 2.50% >= 2.50% < 3.00%
RATES 3.00% >= 3.00% < 3.50%
RATES 3.50% >= 3.50% < 3.75%
RATES 3.75% >= 3.75% < 4.00%

'''DTI-RATIO'''

Used for the Debit To Income Ratio

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
DTI-RATIO Negative
DTI-RATIO 0.00% Zero
DTI-RATIO 0.01% <= 25%
DTI-RATIO 25.01% 25.01% - 40%
DTI-RATIO 40.01% 40.01% - 46%
DTI-RATIO 46.01% Over 46%

'''LTV'''

Used for Loan-to-Value

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
LTV Negative
LTV 0.00% Zero
LTV 0.01% <= 80%
LTV 80.01% 80.01% - 90%
LTV 90.01% 90.01% - 100%
LTV 100.01% Over 100%

'''MAT-DAYS'''

Used for the Maturity Days

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
MAT-DAYS 1-30 Days
MAT-DAYS 31 31-60 Days
MAT-DAYS 61 61-90 Days
MAT-DAYS 91 91-120 Days
MAT-DAYS 121 121-180 Days
MAT-DAYS 181 6 Mths - 1 Year
MAT-DAYS 366 1 – 2 Years
MAT-DAYS 731 2 – 3 Years
MAT-DAYS 1,096 3 – 4 Years
MAT-DAYS 1,461 4 – 5 Years
MAT-DAYS 1,826 Over 5 Years

'''LATE-PMTS'''

Used for counting Late Payments

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
LATE-PMTS None Late
LATE-PMTS 1 One Late
LATE-PMTS 2 2 – 3 Late
LATE-PMTS 4 4 – 5 Late
LATE-PMTS 6 6 – 10 Late
LATE-PMTS 11 > 10 Late

== Dimensions Sheet ==

This sheet can be used to create custom dimensions for output by tables and charts in Vital Signs

The columns in this sheet are DIMNAME, GROUPNAME, GROUPLABEL and GROUPSORTBY

'''DIMNAME'''
The name of the Dimension - "MBR, SH or LN"

'''GROUPNAME'''
The name of the field in Vital Signs

'''GROUPLABEL'''
The description of the dimension that appears in Vital Signs in the drop down list

'''GROUPSORTBY'''
The custom sort for this dimension

'''Default Groups'''
DIMNAME GROUPNAME GROUPLABEL GROUPSORTBY
MBR MBR_BRANCH_NAME Mbr Curr Branch =MBR_BRANCH_SORT
MBR MBR_ORIG_BRANCH_NAME Mbr Orig Branch =MBR_ORIG_BRANCH_SORT
MBR MBR_ORIG_OPEN_MTH Orig Open Mth Ascii
MBR MBR_ESCHEAT_MTH Mbr Escheat Date Ascii
MBR MBR_AGE_RANGE Mbr Age Range =MBR_AGE_RANGE_SORT
MBR MBR_ACCT_AGE_RANGE Acct Age Range =MBR_ACCT_AGE_RANGE_SORT
MBR MBR_RELATE_FLAG Mbr Relate Flag Ascii
MBR MBR_TOT_SHBAL_RANGE Mbr Total Dep Balance =MBR_TOT_SHBAL_RANGE_SORT
MBR MBR_TOT_LNBAL_RANGE Mbr Total Loan Balance =MBR_TOT_LNBAL_RANGE_SORT
MBR MBR_SH_BAL_CHANGE_RANGE Mbr Dep Bal Change =MBR_SH_BAL_CHANGE_RANGE_SORT
MBR MBR_LN_BAL_CHANGE_RANGE Mbr Loan Bal Change =MBR_LN_BAL_CHANGE_RANGE_SORT
MBR MBR_CITY Mbr City Ascii
MBR MBR_ZIP Mbr Zipcode Numeric
MBR MBR_DEPARTMENT Mbr Department Ascii
MBR MBR_SELLER_NAME Mbr Seller Name Ascii

DIMNAME GROUPNAME GROUPLABEL GROUPSORTBY
SH MBR_AGE_RANGE Mbr Age Range =MBR_AGE_RANGE_SORT
SH MBR_ACCT_AGE_RANGE Acct Age Range =MBR_ACCT_AGE_RANGE_SORT
SH MBR_RELATE_FLAG Mbr Relate Flag Ascii
SH SH_BRANCH_NAME Share Branch =SH_BRANCH_SORT
SH SH_ORIG_BRANCH_NAME Share Orig Branch =SH_ORIG_BRANCH_SORT
SH SH_BAL_RANGE Share Balance =SH_BAL_RANGE_SORT
SH SH_BAL_CHANGE_RANGE Share Bal Change =SH_BAL_CHANGE_RANGE_SORT
SH SH_OPEN_MTH Open Date Ascii
SH SH_DAYS_NEG_RANGE Neg Days =SH_DAYS_NEG_RANGE_SORT
SH SH_CERT_MAT_DATE_MTH Cert Maturity Date Ascii
SH SH_DESC_ABRV_LONGDESC Desc Abrv Ascii
SH SH_DIV_RATE_RANGE Div Rate =SH_DIV_RATE_RANGE_SORT
SH SH_SELLER_NAME Share Seller Ascii
SH SH_RECORDER_NAME Share Recorder Ascii
SH =SH_TYPE_PROD Share Type Numeric # Use an equals for expressions or groups.

DIMNAME GROUPNAME GROUPLABEL GROUPSORTBY
LN MBR_AGE_RANGE Mbr Age Range =MBR_AGE_RANGE_SORT
LN MBR_ACCT_AGE_RANGE Acct Age Range =MBR_ACCT_AGE_RANGE_SORT
LN MBR_RELATE_FLAG Mbr Relate Flag Ascii
LN LN_BRANCH_NAME Loan Branch =LN_BRANCH_SORT
LN LN_ORIG_BRANCH_NAME Loan Orig Branch =LN_ORIG_BRANCH_SORT
LN LN_BAL_RANGE Loan Balance =LN_BAL_RANGE_SORT
LN LN_BAL_CHANGE_RANGE Loan Bal Change =LN_BAL_CHANGE_RANGE_SORT
LN LN_COLLATERAL_DESC Collateral Ascii
LN LN_ENTRY_MTH Loan Open Date Ascii
LN LN_APR_RANGE Loan APR =LN_APR_RANGE_SORT
LN LN_SELLER_NAME Loan Seller Ascii
LN LN_OFFICER_NAME Loan Officer Ascii
LN LN_VI_DEALER Dealer Name Ascii
LN LN_CREDIT_TIER_DESC Credit Tier Ascii
LN =LN_TYPE_PROD Loan Type Numeric # Use an equals for expressions or groups.

== Control Flags ==

This sheet can be used to add control flags that will appear on the Mbr Select, Deposit Select and Loan Select tabs in Vital Signs.

The columns in this sheet are Type, Flag, FieldName, Label and SortBy

'''Type'''
The type of the flag. Must be one of: MBR, SH or LN.

'''Flag'''
This is the control flag number.

'''FieldName'''
A unique name that will be used internally as the name of this field. Must be all uppercase with no spaces. The underscore is the only allowed special character.

'''Label'''
The name of the flag that user will see in Vital Signs when they make the selection.

'''SortBy'''
In most cases should be set to "Ascii(Desc)" so the Yes will appear before No in the dropdown.

'''Examples'''
Type Flag FieldName Label SortBy

MBR 1 MBR_COMMERCIAL_ACCT_FLG Commercial Account Ascii(Desc)
MBR 29 MBR_DECEASED_FLG Member Deceased Ascii(Desc)

SH 21 SH_DRAFT_ACCT_FLG Draft Account Ascii(Desc)
SH 57 SH_XMAS_CLUB_FLG Christmas Club Account Ascii(Desc)

LN 42 LN_TDR_FLG Loan TDR Ascii(Desc)

== Fields Sheet ==

This sheet defines which fields are loaded into the Vital Signs applications

'''Table Column'''
The internal table name in Vital Signs

'''FieldName Column'''
The internal field name in Vital Signs

'''InitialLoad Column'''
Yes/No flag for loading the field into the Summary and Detail Membership applications

'''SummaryLoad'''
Yes/No flag for loading the field into the Summary (Monthly_Membership_Summary, Weekly_Membership_Summary and Daily_Membership_Summary) applications

'''DetailLoad'''
Yes/No flag for loading the field into the Detail (Membership_Analysis_by_ACCOUNT) application

'''DataChng'''
Yes/No flag for loading the field into the Data Change (Spectrum_Data_Change) application

'''LoanApp'''
Yes/No flag for loading the field into the Loan App (Loan_App) application

== Accounts Sheet ==

This sheet allows for listing Member Accounts that should be dropped from Vital Signs

'''MBR_ACCOUNT'''
The member account number

'''EXCLUDE_ACCOUNT'''
Yes/No flag to exclude the MBR_ACCOUNT

Membership analysis.xls

2025-08-06T15:43:12Z

Johno: /* Control Flags */

Membership analysis.xls

2025-08-06T15:42:15Z

Johno:

== Overview ==

The Membership Analysis spreadsheet contains Ranges, Dimensions, Fields and Accounts specific to Vital Signs during the nightly reloads

== Ranges Sheet ==
'''This sheet contains range information used by the Vital Signs Membership_Analysis Application

These ranges are reapplied each time the Membership_Analysis application is reloaded
The assigned range is >= IM_LOW and < The next IM_LOW value specified

The IM_TIER Column is used for setting a hierarchy for the ranges used below'''

''Note: typically this is only used for Credit Tier''

'''SHARE-BAL'''

Used to calculate Share Balance Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
SHARE-BAL Null No Shares
SHARE-BAL Negative
SHARE-BAL 0.00 Zero
SHARE-BAL 0.01 $0.01 to $4
SHARE-BAL 5.00 $5 to $499
SHARE-BAL 500.00 $500 - $999
SHARE-BAL 1,000.00 $1K - $4,999
SHARE-BAL 5,000.00 $5K - $9,999
SHARE-BAL 10,000.00 $10K - $49,999
SHARE-BAL 50,000.00 $50K - $99,999
SHARE-BAL 100,000.00 $100K and over

'''LOAN-BAL'''

Used to calculate Loan Balance Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
LOAN-BAL Null No Loans
LOAN-BAL Negative
LOAN-BAL 0.00 Zero
LOAN-BAL 0.01 $0.01 to $999
LOAN-BAL 1,000.00 $1K to $4,999
LOAN-BAL 5,000.00 $5K to $9,999
LOAN-BAL 10,000.00 $10,000 - $49,999
LOAN-BAL 50,000.00 $50,000 - $99,999
LOAN-BAL 100,000.00 $100K and over

'''TRIAL-BAL'''

Used in the Trial Balance page and should not be modified

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
TRIAL-BAL Negative
TRIAL-BAL 0.00 Zero
TRIAL-BAL 0.01 $0.01 - $10.00
TRIAL-BAL 10.01 $10.01 - $25.00
TRIAL-BAL 25.01 $25.01 - $100.00
TRIAL-BAL 100.01 $100.01 - $500.00
TRIAL-BAL 500.01 $500.01 - $1,000
TRIAL-BAL 1,000.01 $1,000.01 - $2,000
TRIAL-BAL 2,000.01 $2,000.01 - $3,000
TRIAL-BAL 3,000.01 $3,000.01 - $5,000
TRIAL-BAL 5,000.01 $5,000.01 - $10,000
TRIAL-BAL 10,000.01 $10,000.01 - $20,000
TRIAL-BAL 20,000.01 $20,000.01 - $40,000
TRIAL-BAL 40,000.01 $40,000.01 - $100,000
TRIAL-BAL 100,000.01 $100,000.01 and Over

'''MBR-AGE'''

Used to calculate Member Age Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
MBR-AGE Zero (No age)
MBR-AGE 1 Under 16
MBR-AGE 16 16 to 20
MBR-AGE 21 21 to 25
MBR-AGE 26 26 to 30
MBR-AGE 31 31 to 35
MBR-AGE 36 36 to 40
MBR-AGE 41 41 to 45
MBR-AGE 46 46 to 50
MBR-AGE 51 51 to 55
MBR-AGE 56 56 to 60
MBR-AGE 61 61 to 65
MBR-AGE 66 66 to 70
MBR-AGE 71 71 to 75
MBR-AGE 76 76 and over

'''ACCT-AGE'''

Used to calculate Account Age Ranges - how long the member has been a member

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
ACCT-AGE Less than 1 Year
ACCT-AGE 1 1 – 2 Years
ACCT-AGE 3 3 – 5 Years
ACCT-AGE 6 6 – 10 Years
ACCT-AGE 11 11 – 20 Years
ACCT-AGE 21 21 Years +

'''CREDIT-SCORE'''

Used to calculate Credit Score Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
CREDIT_SCORE F F (No Score)
CREDIT_SCORE 1 E E (Less than 520)
CREDIT_SCORE 520 D D (520 - 580)
CREDIT_SCORE 581 C C (581 - 620)
CREDIT_SCORE 621 B B (621 - 700)
CREDIT_SCORE 701 A A (701 - 720)
CREDIT_SCORE 721 A+ A+ (Over 721)

'''DELQ-DAYS'''

Used when displaying Delinquent Loans

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
DELQ-DAYS Current
DELQ-DAYS 1 1-15 Days
DELQ-DAYS 16 16-30 Days
DELQ-DAYS 31 31-60 Days
DELQ-DAYS 61 61-90 Days
DELQ-DAYS 91 91-120 Days
DELQ-DAYS 121 121-180 Days
DELQ-DAYS 181 6 Mths - 1 Year
DELQ-DAYS 366 Over 1 Year

'''CHANGE-BAL'''

Used to calculate balance Changes for both Share and Loan Ranges

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
CHANGE-BAL Neg: Over $100K
CHANGE-BAL -99,999.99 Neg: $50K to $100K
CHANGE-BAL -49,999.99 Neg: $10K to $50K
CHANGE-BAL -9,999.99 Neg: $5K to $10K
CHANGE-BAL -4,999.99 Neg: $1K to $5K
CHANGE-BAL -999.99 Neg: .01 to $1K
CHANGE-BAL 0.00 Zero
CHANGE-BAL 0.01 .01 to $1k
CHANGE-BAL 1,000.00 $1K to $5K
CHANGE-BAL 5,000.00 $5K to $10K
CHANGE-BAL 10,000.00 $10,000 - $50K
CHANGE-BAL 50,000.00 $50,000 - $100K
CHANGE-BAL 100,000.00 $100K and over

'''RATES'''

Used to calculate rate ranges for both shares (DIV_RATE) and loans (APR)

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
RATES Negative
RATES 0.00% Zero
RATES 0.00% <= 0.50%
RATES 0.50% >= 0.50% < 1.00%
RATES 1.00% >= 1.00% < 1.50%
RATES 1.50% >= 1.50% < 2.00%
RATES 2.00% >= 2.00% < 2.50%
RATES 2.50% >= 2.50% < 3.00%
RATES 3.00% >= 3.00% < 3.50%
RATES 3.50% >= 3.50% < 3.75%
RATES 3.75% >= 3.75% < 4.00%

'''DTI-RATIO'''

Used for the Debit To Income Ratio

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
DTI-RATIO Negative
DTI-RATIO 0.00% Zero
DTI-RATIO 0.01% <= 25%
DTI-RATIO 25.01% 25.01% - 40%
DTI-RATIO 40.01% 40.01% - 46%
DTI-RATIO 46.01% Over 46%

'''LTV'''

Used for Loan-to-Value

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
LTV Negative
LTV 0.00% Zero
LTV 0.01% <= 80%
LTV 80.01% 80.01% - 90%
LTV 90.01% 90.01% - 100%
LTV 100.01% Over 100%

'''MAT-DAYS'''

Used for the Maturity Days

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
MAT-DAYS 1-30 Days
MAT-DAYS 31 31-60 Days
MAT-DAYS 61 61-90 Days
MAT-DAYS 91 91-120 Days
MAT-DAYS 121 121-180 Days
MAT-DAYS 181 6 Mths - 1 Year
MAT-DAYS 366 1 – 2 Years
MAT-DAYS 731 2 – 3 Years
MAT-DAYS 1,096 3 – 4 Years
MAT-DAYS 1,461 4 – 5 Years
MAT-DAYS 1,826 Over 5 Years

'''LATE-PMTS'''

Used for counting Late Payments

Example:
IM_KEY IM_LOW IM_TIER IM_DESC
LATE-PMTS None Late
LATE-PMTS 1 One Late
LATE-PMTS 2 2 – 3 Late
LATE-PMTS 4 4 – 5 Late
LATE-PMTS 6 6 – 10 Late
LATE-PMTS 11 > 10 Late

== Dimensions Sheet ==

This sheet can be used to create custom dimensions for output by tables and charts in Vital Signs

The columns in this sheet are DIMNAME, GROUPNAME, GROUPLABEL and GROUPSORTBY

'''DIMNAME'''
The name of the Dimension - "MBR, SH or LN"

'''GROUPNAME'''
The name of the field in Vital Signs

'''GROUPLABEL'''
The description of the dimension that appears in Vital Signs in the drop down list

'''GROUPSORTBY'''
The custom sort for this dimension

'''Default Groups'''
DIMNAME GROUPNAME GROUPLABEL GROUPSORTBY
MBR MBR_BRANCH_NAME Mbr Curr Branch =MBR_BRANCH_SORT
MBR MBR_ORIG_BRANCH_NAME Mbr Orig Branch =MBR_ORIG_BRANCH_SORT
MBR MBR_ORIG_OPEN_MTH Orig Open Mth Ascii
MBR MBR_ESCHEAT_MTH Mbr Escheat Date Ascii
MBR MBR_AGE_RANGE Mbr Age Range =MBR_AGE_RANGE_SORT
MBR MBR_ACCT_AGE_RANGE Acct Age Range =MBR_ACCT_AGE_RANGE_SORT
MBR MBR_RELATE_FLAG Mbr Relate Flag Ascii
MBR MBR_TOT_SHBAL_RANGE Mbr Total Dep Balance =MBR_TOT_SHBAL_RANGE_SORT
MBR MBR_TOT_LNBAL_RANGE Mbr Total Loan Balance =MBR_TOT_LNBAL_RANGE_SORT
MBR MBR_SH_BAL_CHANGE_RANGE Mbr Dep Bal Change =MBR_SH_BAL_CHANGE_RANGE_SORT
MBR MBR_LN_BAL_CHANGE_RANGE Mbr Loan Bal Change =MBR_LN_BAL_CHANGE_RANGE_SORT
MBR MBR_CITY Mbr City Ascii
MBR MBR_ZIP Mbr Zipcode Numeric
MBR MBR_DEPARTMENT Mbr Department Ascii
MBR MBR_SELLER_NAME Mbr Seller Name Ascii

DIMNAME GROUPNAME GROUPLABEL GROUPSORTBY
SH MBR_AGE_RANGE Mbr Age Range =MBR_AGE_RANGE_SORT
SH MBR_ACCT_AGE_RANGE Acct Age Range =MBR_ACCT_AGE_RANGE_SORT
SH MBR_RELATE_FLAG Mbr Relate Flag Ascii
SH SH_BRANCH_NAME Share Branch =SH_BRANCH_SORT
SH SH_ORIG_BRANCH_NAME Share Orig Branch =SH_ORIG_BRANCH_SORT
SH SH_BAL_RANGE Share Balance =SH_BAL_RANGE_SORT
SH SH_BAL_CHANGE_RANGE Share Bal Change =SH_BAL_CHANGE_RANGE_SORT
SH SH_OPEN_MTH Open Date Ascii
SH SH_DAYS_NEG_RANGE Neg Days =SH_DAYS_NEG_RANGE_SORT
SH SH_CERT_MAT_DATE_MTH Cert Maturity Date Ascii
SH SH_DESC_ABRV_LONGDESC Desc Abrv Ascii
SH SH_DIV_RATE_RANGE Div Rate =SH_DIV_RATE_RANGE_SORT
SH SH_SELLER_NAME Share Seller Ascii
SH SH_RECORDER_NAME Share Recorder Ascii
SH =SH_TYPE_PROD Share Type Numeric # Use an equals for expressions or groups.

DIMNAME GROUPNAME GROUPLABEL GROUPSORTBY
LN MBR_AGE_RANGE Mbr Age Range =MBR_AGE_RANGE_SORT
LN MBR_ACCT_AGE_RANGE Acct Age Range =MBR_ACCT_AGE_RANGE_SORT
LN MBR_RELATE_FLAG Mbr Relate Flag Ascii
LN LN_BRANCH_NAME Loan Branch =LN_BRANCH_SORT
LN LN_ORIG_BRANCH_NAME Loan Orig Branch =LN_ORIG_BRANCH_SORT
LN LN_BAL_RANGE Loan Balance =LN_BAL_RANGE_SORT
LN LN_BAL_CHANGE_RANGE Loan Bal Change =LN_BAL_CHANGE_RANGE_SORT
LN LN_COLLATERAL_DESC Collateral Ascii
LN LN_ENTRY_MTH Loan Open Date Ascii
LN LN_APR_RANGE Loan APR =LN_APR_RANGE_SORT
LN LN_SELLER_NAME Loan Seller Ascii
LN LN_OFFICER_NAME Loan Officer Ascii
LN LN_VI_DEALER Dealer Name Ascii
LN LN_CREDIT_TIER_DESC Credit Tier Ascii
LN =LN_TYPE_PROD Loan Type Numeric # Use an equals for expressions or groups.

== Control Flags ==

This sheet can be used to add control flags that will appear on the Mbr Select, Deposit Select and Loan Select tabs in Vital Signs.

The columns in this sheet are Type, Flag, FieldName, Label and SortBy

'''Type'''
The type of the flag. Must be one of: MBR, SH or LN.

'''Flag'''
This is the control flag number.

'''FieldName'''
A unique name that will be used internally as the name of this field. Must be all uppercase with no spaces. The underscore is the only allowed special character.

'''Label'''
The name of the flag that user will see in Vital Signs when they make the selection.

'''SortBy'''
In most cases should be set to "Ascii(Desc)" so the Yes will appear before No in the dropdown.

'''Examples'''
Type Flag FieldName Label SortBy
MBR 1 MBR_COMMERCIAL_ACCT_FLG Commercial Account Ascii(Desc)
MBR 29 MBR_DECEASED_FLG Member Deceased Ascii(Desc)

SH 21 SH_DRAFT_ACCT_FLG Draft Account Ascii(Desc)
SH 57 SH_XMAS_CLUB_FLG Christmas Club Account Ascii(Desc)

LN 42 LN_TDR_FLG Loan TDR Ascii(Desc)

== Fields Sheet ==

This sheet defines which fields are loaded into the Vital Signs applications

'''Table Column'''
The internal table name in Vital Signs

'''FieldName Column'''
The internal field name in Vital Signs

'''InitialLoad Column'''
Yes/No flag for loading the field into the Summary and Detail Membership applications

'''SummaryLoad'''
Yes/No flag for loading the field into the Summary (Monthly_Membership_Summary, Weekly_Membership_Summary and Daily_Membership_Summary) applications

'''DetailLoad'''
Yes/No flag for loading the field into the Detail (Membership_Analysis_by_ACCOUNT) application

'''DataChng'''
Yes/No flag for loading the field into the Data Change (Spectrum_Data_Change) application

'''LoanApp'''
Yes/No flag for loading the field into the Loan App (Loan_App) application

== Accounts Sheet ==

This sheet allows for listing Member Accounts that should be dropped from Vital Signs

'''MBR_ACCOUNT'''
The member account number

'''EXCLUDE_ACCOUNT'''
Yes/No flag to exclude the MBR_ACCOUNT

Upgrading Stunnel to the Latest Version

2025-07-14T18:07:58Z

Johno: /* Verify the TLS Level Used for the Connection */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 2 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
** Choose the file: stunnel-5.75-win64-installer.exe
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel using Add/Remove Programs or by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do '''NOT''' run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file.
* Run Notepad (or Notepad++) as Administrator
* Open and edit the following file:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Run Powershell as the Administrator and uninstall/reinstall the stunnel '''service'''
* When Windows Powershell is running, enter the following commands:
** Paste the commands individually (not all 3 at once).
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. If Services is still running, exit and restart Services as the Administrator so that the list of services is refreshed.
** If you receive an error, or the service does not restart, reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

=== Verify the TLS Level Used for the Connection ===
* After successfully starting server in Visimage, open the <code>C:\Program Files (x86)\stunnel\config\stunnel.log</code> file.
* Look for the following lines toward the bottom of the log file:
<pre>
TLS connected: new session negotiated
TLSv1.3 ciphersuite: TLS... (256-bit encryption)
</pre>
* If your TLS level is 1.2 or 1.3 you are all set.
* If the TLS level is 1.1 or lower, contact Vital Soft support for assistance.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-14T18:07:25Z

Johno: /* Verify the TLS Level Used for the Connection */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 2 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
** Choose the file: stunnel-5.75-win64-installer.exe
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel using Add/Remove Programs or by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do '''NOT''' run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file.
* Run Notepad (or Notepad++) as Administrator
* Open and edit the following file:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Run Powershell as the Administrator and uninstall/reinstall the stunnel '''service'''
* When Windows Powershell is running, enter the following commands:
** Paste the commands individually (not all 3 at once).
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. If Services is still running, exit and restart Services as the Administrator so that the list of services is refreshed.
** If you receive an error, or the service does not restart, reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

=== Verify the TLS Level Used for the Connection ===
* After successfully starting server in Visimage, open the <code>C:\Program Files (x86)\stunnel\config\stunnel.log</code> file.
* Look for the following lines toward the bottom of the log file:
<pre>
TLS connected: new session negotiated
TLSv1.3 ciphersuite: TLS... (256-bit encryption)
</pre>
* If your TLS level is 1.2 or 1.3 you are all set.
* If the TLS level is less thamn 1.2, contact Vital Soft support for assistance.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-14T18:07:10Z

Johno: /* Verify the TLS Level Used for the Connection */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 2 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
** Choose the file: stunnel-5.75-win64-installer.exe
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel using Add/Remove Programs or by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do '''NOT''' run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file.
* Run Notepad (or Notepad++) as Administrator
* Open and edit the following file:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Run Powershell as the Administrator and uninstall/reinstall the stunnel '''service'''
* When Windows Powershell is running, enter the following commands:
** Paste the commands individually (not all 3 at once).
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. If Services is still running, exit and restart Services as the Administrator so that the list of services is refreshed.
** If you receive an error, or the service does not restart, reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

=== Verify the TLS Level Used for the Connection ===
* After successfully starting server in Visimage, open the <code>C:\Program Files (x86)\stunnel\config\stunnel.log</code> file. O
* Look for the following lines toward the bottom of the log file:
<pre>
TLS connected: new session negotiated
TLSv1.3 ciphersuite: TLS... (256-bit encryption)
</pre>
* If your TLS level is 1.2 or 1.3 you are all set.
* If the TLS level is less thamn 1.2, contact Vital Soft support for assistance.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-14T18:06:28Z

Johno: /* Verify the TLS Level Used for the connection */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 2 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
** Choose the file: stunnel-5.75-win64-installer.exe
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel using Add/Remove Programs or by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do '''NOT''' run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file.
* Run Notepad (or Notepad++) as Administrator
* Open and edit the following file:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Run Powershell as the Administrator and uninstall/reinstall the stunnel '''service'''
* When Windows Powershell is running, enter the following commands:
** Paste the commands individually (not all 3 at once).
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. If Services is still running, exit and restart Services as the Administrator so that the list of services is refreshed.
** If you receive an error, or the service does not restart, reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

=== Verify the TLS Level Used for the Connection ===
* After successfully starting server in Visimage, open the stunnel log file. Open:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.log
</pre>
* Look for the following lines toward the bottom of the log file:
<pre>
TLS connected: new session negotiated
TLSv1.3 ciphersuite: TLS... (256-bit encryption)
</pre>
* If your TLS level is 1.2 or 1.3 you are all set.
* If the TLS level is less thamn 1.2, contact Vital Soft support for assistance.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-14T18:05:39Z

Johno: /* Install the Stunnel Service */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 2 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
** Choose the file: stunnel-5.75-win64-installer.exe
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel using Add/Remove Programs or by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do '''NOT''' run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file.
* Run Notepad (or Notepad++) as Administrator
* Open and edit the following file:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Run Powershell as the Administrator and uninstall/reinstall the stunnel '''service'''
* When Windows Powershell is running, enter the following commands:
** Paste the commands individually (not all 3 at once).
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. If Services is still running, exit and restart Services as the Administrator so that the list of services is refreshed.
** If you receive an error, or the service does not restart, reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

=== Verify the TLS Level Used for the connection ===
* After successfully starting server in Visimage, open the stunnel log file. Open:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.log
</pre>
* Look for the following lines toward the bottom of the log file:
<pre>
TLS connected: new session negotiated
TLSv1.3 ciphersuite: TLS... (256-bit encryption)
</pre>
* If your TLS level is 1.2 or 1.3 you are all set.
* If the TLS level is less thamn 1.2, contact Vital Soft support for assistance.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-14T18:02:11Z

Johno:

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 2 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
** Choose the file: stunnel-5.75-win64-installer.exe
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel using Add/Remove Programs or by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do '''NOT''' run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file.
* Run Notepad (or Notepad++) as Administrator
* Open and edit the following file:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Run Powershell as the Administrator and uninstall/reinstall the stunnel '''service'''
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. If Services is still running, exit and restart Services as the Administrator so that the list of services is refreshed.
** If you receive an error, or the service does not restart, reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

=== Verify the TLS Level Used for the connection ===
* After successfully starting server in Visimage, open the stunnel log file. Open:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.log
</pre>
* Look for the following lines toward the bottom of the log file:
<pre>
TLS connected: new session negotiated
TLSv1.3 ciphersuite: TLS... (256-bit encryption)
</pre>
* If your TLS level is 1.2 or 1.3 you are all set.
* If the TLS level is less thamn 1.2, contact Vital Soft support for assistance.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-08T22:37:23Z

Johno: /* Install the Stunnel Service */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. If Services is still running, exit and restart Services as the Administrator so that the list of services is refreshed.
** If the service does not restart, reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-08T22:36:11Z

Johno: /* Install the Stunnel Service */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. You will need to exit and restart Services as the Administrator
** If the service does not restart, you will need to reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-08T22:35:51Z

Johno: /* Verifying the Installation */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. You will need to exit and restart Services as the Administrator
* If the service does not restart, you will need to reboot your PC.

=== Verifying the Installation ===
* If you rebooted your PC, run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-08T22:34:34Z

Johno:

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].
* Run Visimage, goto Edit Connections and make a note of the port number(s) you are using for LIVE/EOM and CERT.
** You are probably using 30501 and 30502, or 30503 and 30504.

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
** Check that the accept port numbers match what you are currently using. If not, make the appropriate edits.
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. You will need to exit and restart Services as the Administrator
* If the service does not restart, you will need to reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-08T21:32:41Z

Johno:

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation may require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Restart the "Stunnel TLS wrapper" service. You will need to exit and restart Services as the Administrator
* If the service does not restart, you will need to reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-08T21:28:47Z

Johno: /* Customize the Stunnel Configuration */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\config\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-08T21:28:30Z

Johno: /* Install the Certificates */

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\config
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>
=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-07-08T21:28:04Z

Johno:

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30502
connect = visimage-cert.fiservapps.com:8004
</pre>
=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\"Program Files (x86)"\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Install Stunnel

2025-07-03T16:38:20Z

Johno:

=== Prepare for Stunnel Install ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Download the latest version of stunnel [https://stunnel.org/downloads here].
* Download the Fiserv Certificate files [https://vital-soft.com/?page_id=544&product=stunnel&release=current here].

=== Installing Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:\Program Files (x86)\stunnel\conf
</pre>

=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>

=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Install Stunnel

2025-07-03T16:34:29Z

Johno: Created page with "=== Prepare for Stunnel Install === * Please note that installation does require a reboot of your PC / workstation. * You may need Admin level access to your PC to complete th..."

=== Prepare for Stunnel Install ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Installing Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Visimage3 Setup for Fiserv Online Clients

2025-07-03T16:31:36Z

Johno:

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host.

=== Installing Stunnel for the First Time ===
Follow these [[Install Stunnel|instructions]] to install Stunnel 5.75 for the first time. See below for instructions to upgrade Stunnel to version 5.75.

=== Upgrading Stunnel to Support TLS 1.2 ===
In July 2025 Fiserv will be requiring all stunnel connections to use TLS 1.2. To support this change, clients will need to upgrade stunnel to the latest version (currently 5.75 in June 2025). Follow these instructions for [[Upgrading Stunnel to the Latest Version]]. We encourage you to contact Vital Soft support if you need assistance performing the upgrade.

=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords.
* Passwords shorter than the minimum length will not be permitted.
* Existing passwords will not be effected and do not need to be changed until they expire.
* The new minimum length requirement will apply when users change their passwords and when Admin users reset passwords or add new users.
* Visimage3 version 3.4.2.31 and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:
<pre>
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
</pre>

Visimage3 Setup for Fiserv Online Clients

2025-07-03T16:28:05Z

Johno:

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host.

=== Upgrading Stunnel to Support TLS 1.2 ===
In July 2025 Fiserv will be requiring all stunnel connections to use TLS 1.2. To support this change, clients will need to upgrade stunnel to the latest version (currently 5.75 in June 2025). Follow these instructions for [[Upgrading Stunnel to the Latest Version]]. We encourage you to contact Vital Soft support if you need assistance performing the upgrade.

=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords.
* Passwords shorter than the minimum length will not be permitted.
* Existing passwords will not be effected and do not need to be changed until they expire.
* The new minimum length requirement will apply when users change their passwords and when Admin users reset passwords or add new users.
* Visimage3 version 3.4.2.31 and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:
<pre>
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
</pre>

Upgrading Stunnel to the Latest Version

2025-07-03T16:26:06Z

Johno:

'''NOTE:'''
* You must upgrade stunnel on all workstations using Visimage3 prior to '''July 29th, 2025'''.
* Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-06-24T19:44:57Z

Johno:

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv and told that it is ok to proceed.

'''NOTE:''' you must upgrade stunnel on all workstations using Visimage3 prior to the deadline provided by Fiserv in their client communication bulletin. Don't forget to also update any virtual machines that run Visimage3 scheduled jobs.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-06-24T19:40:13Z

Johno:

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv and told that it is ok to proceed.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
=== Customize the Stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
=== Install the Stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-06-24T19:39:39Z

Johno: /* Prepare for Stunnel Upgrade */

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv and told that it is ok to proceed.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files (in another location) - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
=== Customize the stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
=== Install the stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-06-24T19:38:27Z

Johno:

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv and told that it is ok to proceed.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Install the Certificates ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
=== Customize the stunnel Configuration ===
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Remove the semi-colon comments from the debug and output lines (lines 11 & 12):
<pre>
debug=info
output=stunnel.log
</pre>
* Add the following lines after "output=stunnel.log":
<pre>
CAfile = certs.pem
cert = stunnel.pem

[Visimage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[Visimage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
=== Install the stunnel Service ===
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-06-24T19:32:32Z

Johno: /* Complete the Installation */

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv and told that it is ok to proceed.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Customize the Installation ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Add the following lines (which can be copied from the stunnel.conf file that was saved in step 1):
<pre>
CAfile = certs.pem
cert = stunnel.pem

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-06-24T19:27:25Z

Johno:

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv and told that it is ok to proceed.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* You may need Admin level access to your PC to complete the install.
* Save copies of the following 3 files - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Complete the Installation ===
* Copy the the saved certificate files from step 1 (certs.pem, stunnel.pem) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
* Edit the stunnel configuration file. The file is located here:
<pre>
C:\Program Files (x86)\stunnel\conf\stunnel.conf
</pre>
* Add the following lines (which can be copied from the stunnel.conf file that was saved in step 1):
<pre>
CAfile = certs.pem
cert = stunnel.pem

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-06-11T18:02:48Z

Johno:

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* Save copies of the following 3 files - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Complete the Installation ===
* Copy the three saved files from step 1 (certs.pem, stunnel.pem and stunnel.conf) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
* When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".
* If the service is running, launch Visimage3 and test that you are able to successfully start server.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Upgrading Stunnel to the Latest Version

2025-06-11T17:59:35Z

Johno: /* Verifying the Installation */

Upgrading Stunnel to the Latest Version

2025-06-11T17:57:54Z

Johno: /* Complete the Installation */

Upgrading Stunnel to the Latest Version

2025-06-11T17:56:18Z

Johno: /* Uninstall the Previous Version of Stunnel */

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* Save copies of the following 3 files - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was removed. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Complete the Installation ===
* Copy the three saved files from step 1 (certs.pem, stunnel.pem and stunnel.conf) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".

Upgrading Stunnel to the Latest Version

2025-06-11T17:55:46Z

Johno: /* Uninstall the Previous Version of Stunnel */

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* Save copies of the following 3 files - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the currently installed version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was deleted. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Complete the Installation ===
* Copy the three saved files from step 1 (certs.pem, stunnel.pem and stunnel.conf) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".

Upgrading Stunnel to the Latest Version

2025-06-11T17:54:56Z

Johno:

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv.

=== Prepare for Stunnel Upgrade ===
* Please note that installation does require a reboot of your PC / workstation.
* Save copies of the following 3 files - you will need them later in the upgrade process.
<pre>
C:\Program Files\stunnel\certs.pem
C:\Program Files\stunnel\stunnel.pem
C:\Program Files\stunnel\stunnel.conf
</pre>
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* Stop the Stunnel service
<pre>
Run the Windows Services program, locate the stunnel service and click Stop.
</pre>
* Uninstall the current version (5.01) of stunnel by running the following program.
<pre>
C:\Program Files\stunnel\uninstall.exe
</pre>
* Verify that the <code>C:\Program Files\stunnel</code> directory was deleted. If it remains, use File Manager to delete it.

=== Install Stunnel ===
* Install the most recent version of stunnel (5.75 in June 2025.)
** Choose the options that are appropriate for your organization.
** By default, stunnel will be installed in <code>C:\Program Files (x86)\</code>
** During installation you will be asked questions to create a default certificate. This certificate will not be used, so you can enter whatever values you choose or just press Enter on all of the prompts.
** Do NOT run stunnel at the end of installation.

=== Complete the Installation ===
* Copy the three saved files from step 1 (certs.pem, stunnel.pem and stunnel.conf) into the following directory:
<pre>
C:\Program Files (x86)\stunnel\conf
</pre>
* Install the stunnel '''service''' using Powershell. If you installed stunnel for all users on the computer, you may need to run Powershell as the Administrator.
When Windows Powershell is running, enter the following commands:
<pre>
cd C:\Program Files (x86)\stunnel\bin
./stunnel -uninstall
./stunnel -install
</pre>
* Reboot your PC.

=== Verifying the Installation ===
* Run Windows Services and verify that the stunnel service is running. The service is now called "Stunnel TLS Wrapper".

Visimage3 Setup for Fiserv Online Clients

2025-06-11T17:09:19Z

Johno:

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host. A special Fiserv installation of stunnel can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here].


=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords.
* Passwords shorter than the minimum length will not be permitted.
* Existing passwords will not be effected and do not need to be changed until they expire.
* The new minimum length requirement will apply when users change their passwords and when Admin users reset passwords or add new users.
* Visimage3 version 3.4.2.31 and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:
<pre>
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
</pre>

Upgrading Stunnel to the Latest Version

2025-06-11T17:06:56Z

Johno: Created page with "'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv. === Prepare for Stunnel Upgrade === * Save copies of the following 3 files - you will need..."

'''DO NOT UPGRADE STUNNEL''' until you have been contacted by Vital Soft or Fiserv.

=== Prepare for Stunnel Upgrade ===
* Save copies of the following 3 files - you will need them later in the upgrade process.
* Download the latest version of stunnel [https://stunnel.org/downloads here].

=== Uninstall the Previous Version of Stunnel ===
* 1
* Two

=== Install Stunnel ===
*

=== Complete the Installation ===

Visimage3 Setup for Fiserv Online Clients

2025-06-11T17:01:18Z

Johno:

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host. A special Fiserv installation of stunnel can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here].

=== Upgrading Stunnel to Support TLS 1.2 ===
In Q3 2025 Fiserv will be requiring all stunnel connections to use TLS 1.2. To support this change, clients will need to upgrade stunnel to the latest version (currently 5.75 in June 2025). DO NOT UPGRADE STUNNEL until you are contacted by Vital Soft or Fiserv. Follow these instructions for [[Upgrading Stunnel to the Latest Version]].

=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords.
* Passwords shorter than the minimum length will not be permitted.
* Existing passwords will not be effected and do not need to be changed until they expire.
* The new minimum length requirement will apply when users change their passwords and when Admin users reset passwords or add new users.
* Visimage3 version 3.4.2.31 and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:
<pre>
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
</pre>

Visimage3 Setup for Fiserv Online Clients

2025-06-11T16:59:41Z

Johno:

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host. A special Fiserv installation of stunnel can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here].

=== Upgrading Stunnel to Support TLS 1.2 ===
In Q3 2025 Fiserv will be requiring all stunnel connections to use TLS 1.2. To support this change, clients will need to upgrade stunnel to the latest version (currently 5.75 in June 2025). DO NOT UPGRADE STUNNEL until you are contacted by Vital Soft or Fiserv. Follow these instructions for [[Upgrading Stunnel to the latest version]].

=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords.
* Passwords shorter than the minimum length will not be permitted.
* Existing passwords will not be effected and do not need to be changed until they expire.
* The new minimum length requirement will apply when users change their passwords and when Admin users reset passwords or add new users.
* Visimage3 version 3.4.2.31 and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:
<pre>
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
</pre>

Visimage3 Setup for Fiserv Online Clients

2025-06-11T16:57:37Z

Johno:

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host. A special Fiserv installation of stunnel can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here].

=== Upgrading Stunnel to Support TLS 1.2 ===
In Q3 2025 Fiserv will be requiring all stunnel connections to use TLS 1.2. To support this change, clients will need to upgrade stunnel to the latest version (currently 5.75 in June 2025). DO NOT UPGRADE STUNNEL until you are contacted by Vital Soft or Fiserv. Follow these instructions for [Upgrading Stunnel to the latest version].

=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords.
* Passwords shorter than the minimum length will not be permitted.
* Existing passwords will not be effected and do not need to be changed until they expire.
* The new minimum length requirement will apply when users change their passwords and when Admin users reset passwords or add new users.
* Visimage3 version 3.4.2.31 and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:
<pre>
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
</pre>

Visimage3 Setup for Fiserv Online Clients

2025-05-19T15:32:30Z

Johno: /* Changing Visimage3 User Passwords */

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host. A special Fiserv installation of stunnel can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here].

=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords.
* Passwords shorter than the minimum length will not be permitted.
* Existing passwords will not be effected and do not need to be changed until they expire.
* The new minimum length requirement will apply when users change their passwords and when Admin users reset passwords or add new users.
* Visimage3 version 3.4.2.31 and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:
<pre>
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
</pre>

Contact Us

2025-05-19T15:26:28Z

Johno: /* Hours */

== Hours ==

M-F 6:30am-3:30pm PST

== Support ==

1-800-848-2576 ext 21

support@vital-soft.com

Visimage3 Setup for Fiserv Online Clients

2025-04-23T19:39:20Z

Johno:

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host. A special Fiserv installation of stunnel can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here].

=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords. Passwords shorter than the minimum length will not be permitted. This applies when adding new users and when resetting passwords. Visimage3 version 3.4.2.x and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:

<pre>
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
</pre>

Visimage3 Setup for Fiserv Online Clients

2025-04-23T18:57:58Z

Johno:

=== Visimage3 Setup ===
After installing Visimage3, Fiserv Online Clients '''must also install stunnel''' which is used to encrypt all communication between Visimage3 and the host. A special Fiserv installation of stunnel can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here].

=== Connecting to Spectrum Databases via Linux ===
In Q3/Q4 of 2024, Fiserv will require that all Visimage3 connections be made via a Linux server. When the transition is complete, clients will no longer be able to connect directly to HP-UX as had been done previously.

Click here for more [[Visimage3 Linux Connections for Fiserv Online Clients|details]] on updating users and task scheduler jobs to use the new Linux connection.

=== New Stunnel Certificates (May 2024) ===
Effective May 13, 2024, clients must install new certificate files which can be downloaded [https://vital-soft.com/?page_id=544&product=stunnel&release=current here]. Follow these steps to install the certificates:
<pre>
unzip the Stunnel_Certs_May_2024.zip file
copy stunnel.pem and certs.pem to C:/Program Files/stunnel
restart the stunnel service (or reboot your PC)
</pre>
These certificates must be installed on all client PCs where Visiamge3 is installed. If you have a VM configured to execute Visimage3 tasks automatically, don't forget to install the new certificates on that system also.

=== Stunnel Configuration ===
Once stunnel has been installed you must edit the stunnel.conf file and modify the [VisImage Client] section or create a new section. By default, the stunnel.conf file is located in C:\Program Files\stunnel.

The below sample shows 3 sections for '''users wishing to have easy access to HP-UX (Prod), Linux (Prod) and Linux (Cert)'''. This setup is '''only''' for those users who are testing and need to be able to switch between multiple connections:

<pre>
[VisImage Client]
; Prod connection to HP-UX
client = yes
accept = 30501
connect = 100.96.0.25:30502

[VisImage Linux Prod]
; Prod connection to Linux
client = yes
accept = 30503
connect = visimage.fiservapps.com:8004

[VisImage Linux Cert]
; Cert connection to Linux
client = yes
accept = 30504
connect = visimage-cert.fiservapps.com:8004
</pre>
Notes:
* Section Name:
** The name of the section is not important, but must be unique
* Accept Port:
** The port must be different in each section
** The port must match the port specified in the Visimage3 connection (see below)
* Connect Address and Port for HP-UX connections:
** The IP address shown is only a sample
** The connect port will always be 30502 for HP-UX
* Connect Address and Port for Linux connections:
** Always use visimage.fiservapps.com for Prod, and visimage-cert.fiservapps.com for Cert
** The connect port will always be 8004 on Linux

'''If you have already rebooted your PC since installing stunnel, stop and restart the stunnel service. Otherwise reboot.'''

=== Checking the Stunnel Restart ===
After restarting the service (or rebooting) verify that the stunnel.log file has been updated. Open the log file in Notepad and scroll to the end of the file. If you do not see new entries written showing that the service was restarted then there is an issue with the configuration file. Double check that the stunnel.conf file still exists and was not accidentally renamed while it was being edited.

=== Visimage3 Server Configuration ===
When creating a Visimage3 connection, use the following parameters:
{| class="wikitable" style="border-spacing: 2,2,2,2;"
|'''Option''' ||'''Value'''
|-
| Host Address || 127.0.0.1
|-
| Host Port || 30501
|-
| Host Profile Name || username!live or username!eom
|}
Notes:
* When connecting via stunnel, the Host Address is always 127.0.0.1 (localhost)
* The port number specified in the connection must match the corresponding '''Accept =''' port entered in the stunnel.conf file
* The Host Profile Name is the username assigned by Fiserv. For example, joverton.
* The username is always followed by either '''!live''' (for the live databases) or '''!eom''' for the end of month (report) databases.

=== Changing Visimage3 User Passwords ===

In May 2025, Fiserv will begin enforcing a minimum length of 12 characters for Visimage3 User passwords. Passwords shorter than the minimum length will not be permitted. This applies when adding new users and when resetting passwords. Visimage3 version 3.4.2.x and earlier will allow users to attempt to use a shorter password but the reset will fail with the following error:

{{{
Unknown Error: <5:1:299> Error - Unable to reset password. Password is too short. Len=x, Min Len Required=12.
}}}

Testpage

2025-04-23T18:47:29Z

Johno: Created page with "Test"

Test

Visimage3 Linux Connections for Fiserv Online Clients

2024-08-29T23:27:24Z

Johno: /* Accessing Files Created by Spectrum Programs */

=== What Databases Does the Linux Connection Use ===
When you start server in Visimage using the Linux connection, you connect to AskPlus on a Linux server. AskPlus then opens the Spectrum databases (over the network) on the corresponding HP-UX server. As before, Visimage3 has direct access to your most recent (live) and month-end (eom) databases.

What has changed is that AskPlus can no longer access '''files''' created on HP-UX. Therefore if you have any existing Visimage3 reports that use files created by Spectrum programs (pextract, d3307, etc.) you must request that Fiserv modify the jobs to transfer the files to the Linux server.

=== Accessing Files Created by Spectrum Programs ===
Some clients may have reports that require including unencrypted data. Since Visimage3 cannot decrypt fields like SSN, the solution is usually to have Fiserv run a pextract that includes the ACCOUNT number and the decrypted SSN value in a delimited file. In other scenarios, you may need access to values that are not stored in the database, like "loan payoff amount", or "loan delinquent amount." Again, the solution for this is to request that Fiserv run the appropriate pextract (or similar program) to generate the required data in a CSV file.

Since AskPlus (running on Linux) can no longer open files on HP-UX, you must contact Fiserv to have the jobs modified so that the extract files are now created on the Linux server. Typically, no other changes will be required.

=== Visimage3 Passwords ===
The Visimage3 passwords are '''not''' shared between HP-UX and Linux. It is likely that an Admin user will need to reset your password. If no Admin users are able to connect, contact Fiserv for assistance.

=== Switching Existing Users from HP-UX to Linux ===
Modify the stunnel.conf file and update the "connect =" value to update an existing user's stunnel configuration and switch them from HP-UX to Linux:

<pre>
[VisImage Client]
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004
</pre>

'''Do not''' change the accept port, just update the connect address and port. The only reason to change the accept port is if you want to maintain multiple connections.

'''Stop and restart the stunnel service.'''

=== Updating the Visimage3 Setup for Automated Tasks ===
Make the same changes as shown above for your users.
* '''Do not''' change the '''name''' of the Visimage3 connection. This name is stored in the Task Scheduler and should never be changed.
* After updating stunnel.conf (and restarting stunnel), reset the Visimage3 password.

=== When Should I Switch ===
Once you have successfully tested connections for multiple users and have successfully tested any (Task Scheduler) Automated Tasks then it's time to switch. There is no reason to continue using the HP-UX connection once you have successfully completed testing. Remember, both the HP-UX and Linux connections are accessing the same databases. It is just AskPlus that has moved.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Visimage3 Linux Connections for Fiserv Online Clients

2024-08-29T23:25:36Z

Johno: /* What Databases Does the Linux Connection Use */

=== What Databases Does the Linux Connection Use ===
When you start server in Visimage using the Linux connection, you connect to AskPlus on a Linux server. AskPlus then opens the Spectrum databases (over the network) on the corresponding HP-UX server. As before, Visimage3 has direct access to your most recent (live) and month-end (eom) databases.

What has changed is that AskPlus can no longer access '''files''' created on HP-UX. Therefore if you have any existing Visimage3 reports that use files created by Spectrum programs (pextract, d3307, etc.) you must request that Fiserv modify the jobs to transfer the files to the Linux server.

=== Accessing Files Created by Spectrum Programs ===
Some clients may have reports that require including unencrypted data. Since Visimage3 cannot decrypt fields like SSN, the solution in the past was usually to have Fiserv run a pextract that included the ACCOUNT number and the decrypted SSN value in a delimited file. In other scenarios, you may need access to values that are not stored in the database, like "loan payoff amount", or "loan delinquent amount." Again, the solution for this was to request that Fiserv run the appropriate pextract (or similar program) to generate the required data in a CSV file.

Since AskPlus (running on Linux) can no longer open files on HP-UX, this solution no longer works. For these reports, we are recommending that you convert the Visimage3 context that uses these files into AskPlus code that Fiserv can add to the existing job that generates the file. With the added code, instead of just producing a file, the Fiserv job will create all of the needed output.

Contact our support department if you need help with making these changes.

=== Visimage3 Passwords ===
The Visimage3 passwords are '''not''' shared between HP-UX and Linux. It is likely that an Admin user will need to reset your password. If no Admin users are able to connect, contact Fiserv for assistance.

=== Switching Existing Users from HP-UX to Linux ===
Modify the stunnel.conf file and update the "connect =" value to update an existing user's stunnel configuration and switch them from HP-UX to Linux:

<pre>
[VisImage Client]
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004
</pre>

'''Do not''' change the accept port, just update the connect address and port. The only reason to change the accept port is if you want to maintain multiple connections.

'''Stop and restart the stunnel service.'''

=== Updating the Visimage3 Setup for Automated Tasks ===
Make the same changes as shown above for your users.
* '''Do not''' change the '''name''' of the Visimage3 connection. This name is stored in the Task Scheduler and should never be changed.
* After updating stunnel.conf (and restarting stunnel), reset the Visimage3 password.

=== When Should I Switch ===
Once you have successfully tested connections for multiple users and have successfully tested any (Task Scheduler) Automated Tasks then it's time to switch. There is no reason to continue using the HP-UX connection once you have successfully completed testing. Remember, both the HP-UX and Linux connections are accessing the same databases. It is just AskPlus that has moved.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Visimage3 Linux Connections for Fiserv Online Clients

2024-08-20T22:11:29Z

Johno:

=== What Databases Does the Linux Connection Use ===
When you start server in Visimage using the Linux connection, you connect to AskPlus on a Linux server. AskPlus then opens the Spectrum databases (over the network) on the corresponding HP-UX server. As before, Visimage3 has direct access to your most recent (live) and month-end (eom) databases.

What has changed is that AskPlus can no longer access '''files''' created on HP-UX. Therefore any existing Visimage3 reports that use files created by Spectrum programs (pextract, d3307, etc.) must be modified.

=== Accessing Files Created by Spectrum Programs ===
Some clients may have reports that require including unencrypted data. Since Visimage3 cannot decrypt fields like SSN, the solution in the past was usually to have Fiserv run a pextract that included the ACCOUNT number and the decrypted SSN value in a delimited file. In other scenarios, you may need access to values that are not stored in the database, like "loan payoff amount", or "loan delinquent amount." Again, the solution for this was to request that Fiserv run the appropriate pextract (or similar program) to generate the required data in a CSV file.

Since AskPlus (running on Linux) can no longer open files on HP-UX, this solution no longer works. For these reports, we are recommending that you convert the Visimage3 context that uses these files into AskPlus code that Fiserv can add to the existing job that generates the file. With the added code, instead of just producing a file, the Fiserv job will create all of the needed output.

Contact our support department if you need help with making these changes.

=== Visimage3 Passwords ===
The Visimage3 passwords are '''not''' shared between HP-UX and Linux. It is likely that an Admin user will need to reset your password. If no Admin users are able to connect, contact Fiserv for assistance.

=== Switching Existing Users from HP-UX to Linux ===
Modify the stunnel.conf file and update the "connect =" value to update an existing user's stunnel configuration and switch them from HP-UX to Linux:

<pre>
[VisImage Client]
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004
</pre>

'''Do not''' change the accept port, just update the connect address and port. The only reason to change the accept port is if you want to maintain multiple connections.

'''Stop and restart the stunnel service.'''

=== Updating the Visimage3 Setup for Automated Tasks ===
Make the same changes as shown above for your users.
* '''Do not''' change the '''name''' of the Visimage3 connection. This name is stored in the Task Scheduler and should never be changed.
* After updating stunnel.conf (and restarting stunnel), reset the Visimage3 password.

=== When Should I Switch ===
Once you have successfully tested connections for multiple users and have successfully tested any (Task Scheduler) Automated Tasks then it's time to switch. There is no reason to continue using the HP-UX connection once you have successfully completed testing. Remember, both the HP-UX and Linux connections are accessing the same databases. It is just AskPlus that has moved.

[[Visimage3 Setup for Fiserv Online Clients|Back...]]

Visimage3 Linux Connections for Fiserv Online Clients

2024-08-20T22:06:13Z

Johno:

=== What Databases Does the Linux Connection Use ===
When you start server in Visimage using the Linux connection, you connect to AskPlus on a Linux server. AskPlus then opens the Spectrum databases (over the network) on the corresponding HP-UX server. As before, Visimage3 has direct access to your most recent (live) and month-end (eom) databases.

What has changed is that AskPlus can no longer access '''files''' created on HP-UX. Therefore any existing Visimage3 reports that use files created by Spectrum programs (pextract, d3307, etc.) must be modified.

=== Accessing Files Created by Spectrum Programs ===
Some clients may have reports that require including unencrypted data. Since Visimage3 cannot decrypt fields like SSN, the solution in the past was usually to have Fiserv run a pextract that included the ACCOUNT number and the decrypted SSN value in a delimited file. In other scenarios, you may need access to values that are not stored in the database, like "loan payoff amount", or "loan delinquent amount." Again, the solution for this was to request that Fiserv run the appropriate pextract (or similar program) to generate the required data in a CSV file.

Since AskPlus (running on Linux) can no longer open files on HP-UX, this solution no longer works. For these reports, we are recommending that you convert the Visimage3 context that uses these files into AskPlus code that Fiserv can add to the existing job that generates the file. With the added code, instead of just producing a file, the Fiserv job will create all of the needed output.

Contact our support department if you need help with making these changes.

=== Visimage3 Passwords ===
The Visimage3 passwords are '''not''' shared between HP-UX and Linux. It is likely that an Admin user will need to reset your password. If no Admin users are able to connect, contact Fiserv for assistance.

=== Switching Existing Users from HP-UX to Linux ===
Modify the stunnel.conf file and update the "connect =" value to update an existing user's stunnel configuration and switch them from HP-UX to Linux:

<pre>
[VisImage Client]
client = yes
accept = 30501
connect = visimage.fiservapps.com:8004
</pre>

'''Do not''' change the accept port, just update the connect address and port. The only reason to change the accept port is if you want to maintain multiple connections.

'''Stop and restart the stunnel service.'''

=== Updating the Visimage3 Setup for Automated Tasks ===
Make the same changes as shown above for your users.
* '''Do not''' change the '''name''' of the Visimage3 connection. This name is stored in the Task Scheduler and should never be changed.
* After updating stunnel.conf (and restarting stunnel), reset the Visimage3 password.

[[Visimage3 Setup for Fiserv Online Clients|back]]