Prologue Unattended Process for GL Update

After every bank processing day, there is a process that runs overnight where general ledger information from Fiserv is automatically loaded into Prologue. This process involves a combination of Windows scheduled tasks, batch files, and custom AutoIT executables. This document will give the time line for these events and the steps involved.

Abbreviation Key: The following abbreviations are used to represent banks and file paths:

• BBB – Bank Abbreviations
  1. Blue Grass Federal – BGF
  2. First Federal Lakewood – FFL
  3. First Mutual Bank – FMB
  4. Martinsville First – MFB
  5. Warsaw Federal – WSW
• ### - Institution Numbers
  1. Blue Grass Federal – 123
  2. First Federal Lakewood – 110
  3. First Mutual Bank – 052
  4. Martinsville First – 077
  5. Warsaw Federal – 043
• M.MDD – 4-digit month and day

Between 2:00 - 3:30 AM a text file containing the raw GL information is delivered from Fiserv, through an FTP process on EOM-VM to the five Earth\Groups\UnattendedProcessing\SourceFiles\BBB### folders. These files typically have the name format: CD110_VS_###GLPCM.MDD. For example, the file from March 15th for BGF would be CD110_VS_123GLPC0.315.

2. Fiserv File Renamed

Starting at 4:00 AM scheduled tasks run on the Prologue server that renames these files so that Prologue can process them.  The files are renamed using the following format: ###GLPC.BBB. A copy of the original file, un-renamed file is saved in the backup folder.

3. Prologue Unattended Process Runs

Starting at 5:00 AM scheduled tasks run on the Prologue server that launch a batch file to launch Prologue with the unattended process parameters. These scheduled task runs as ffl\unattend since that is what Prologue needs to log in as to work. Sample text for one of the batch files is attached.   Below are the names and schedules for these tasks:

• FFL: Prologue-Unattend – 5:00 AM
• FMB: Prologue-Unattend-BSB – 5:15 AM
• WSW: Prologue-Unattend-Warsaw – 5:30 AM
• BGF: Prologue-Unattend-Blue Grass – 5:45 AM
• MFB: Prologue-Unattend-MFSB – 6:00 AM

The results of these process are saved to the G:\Shared\UnattendedProcessing\Results\BBB### folders. When the process completes it also sends an email to Accounting indicating whether it succeed or failed.

4. What Can Go Wrong

While the overall process is straightforward there some things that can cause it to fail:

• File from Fiserv not delivered by 4:00 AM. If the file is delivered after 4:00, the file renaming process will have to be run manually. This can be done by using the executables in the G:\Shared\UnattendedProcessing\Scripts folder, or by running the 5 UnattendRename scheduled tasks on the Prologue server.  Once the files are renamed, the 5 scheduled tasks for Unattended Processing on the Prologue server can be launched.  When running these scheduled tasks manually, allow 1- 2 minutes between each task to allow them to complete.  You will probably not see Prologue running so you can monitor the Results folders to see if new files get added.  Once you see a file in the Results folder for a bank, you can run the next task.   Alternatively, Accounting should be able to manually run the Unattended process.
• Multiple Days Missed. The unattended process may not run for multiple days due to Fiserv issues or over a weekend.  In this situation you will need manually run the file rename process and Prologue Unattended process once for each bank one day at a time and then repeat the process until all missed days are processed.
• Fiserv changes the file name format. This could impact the automated file renaming process. Notify the Enterprise Systems group and the Service Desk so that they can adjust the scripts.
• Password change for ffl\unattend. Since the password is saved in the scheduled task it would need to be updated there for the task to succeed.
• User group change for ffl\unattend. The user running the task needs access to be in the Shared-UnattendedProcessing-M Active Directory group for the process to work.
• Client failures on the Prologue server. The Prologue application has to be able to launch and login as Unattend for the process to work. This can be tested by logging into the server.