Visimage3 Setup for Fiserv Online Clients

From Vital Soft Wiki
Revision as of 21:37, 20 August 2024 by Johno (talk | contribs) (Switching Existing Users from HP-UX to Linux)
Jump to: navigation, search

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 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 details.

New Stunnel Certificates (May 2024)

Effective May 13, 2024, clients must install new certificate files which can be downloaded here. Follow these steps to install the certificates:

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)

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):

[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

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.

Switching Existing Users from HP-UX to Linux

It's extremely simple to update an existing user's stunnel configuration and switch them from HP-UX to Linux:

Modify the stunnel.conf file and update the "connect =" value as shown below.

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

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.

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:

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.