The original concept for WEM was something designed specifically for the SPIRIT MIS, this predecessor was called SWEM (SPIRIT WIC EBT Middleware). It was designed to allow the SPIRIT system to communicate with newer Universal Interface (2014) based EBT systems. As a need arose for a different client to make use of similar technology, along with a need to change some key pieces of how SWEM functioned, WEM was born.
There are some key differences between WEM and SWEM, and those are discussed in a different document.
For more information, see the FAQ Page for WEM.
Additional prerequisite software requirements are referenced in the Installation Guide.
* 750 MB assumes file storage and database storage is handled elsewhere. If a single machine hosts the entire environment, additional storage will be necessary.
The WEM is a Middleware system, but it's one that comprises many subsystems. Understanding what each of the components does is important in understanding how to configure and install those components to fit the needs of the hosting environment. This System Overview Document attempts to provide the necessary information to help make decisions about installation and configuration of WEM.
WEM is installed using a typical windows installer (MSI) file, this file invokes an installation wizard. This Installation Guide provides a step-by-step guide for installing the software.
WEM has a very complex configuration subsystem. Most of the configuration is driven by a .JSON (JavaScript Object Notation) file that is located in the application's Configuration folder. There is a standalone application for editing this file in a Graphical User Interface (GUI), and a version of this tool is also being developed for use in the admin website. The .JSON file contains information for each of the WIC agencies hosted in the instance as well as the individual endpoints for those agencies, and global settings at a higher level as well. Read More about configuration here.
WEM processes data between disparate systems and supports multiple systems in this configuration. As a result of this, WEM has myriad rules that are applied as processing is performed. Many of these rules are static within the Middleware infrastructure, others are dynamic by nature and are controlled by the configuration module. It is important to understand how the various pieces fit together and how the processing is managed. Read More about processing rules here.
| Version | Summary | Release Date |
|---|---|---|
| 2.2.1.0 | Address performance issues with caching and removes NServiceBus from the message processing pipeline. Includes numerous bug fixes related to Smart Card | 01/18/2017 |
| 2.2.0.0 | Makes slight database modifications including adding the machine name to the database. Adds encryption to the wem-config file. | N/A |
| Version | Summary | Release Date |
|---|---|---|
| 2.1.1.1 | Hotfix build to correct an issue with processing redemption files. | 04/17/2017 |
| 2.1.1.0 | Corrects a version number error where 2.1.0.5 was incorrectly listed as a 2.1.0 build instead of a 2.1.1 build. | 03/10/2017 |
| 2.1.0.5 | Includes changes for 2.1.0.4, cleans up some packages referenced by the code in an effort to optimize development efforts, addresses internal code comments | 03/09/2017 |
| 2.1.0.4 | Added support to correctly handle redemption file routing in a smart card deployment This build was never deployed independently | N/A |
| 2.1.0.3 | Addressed two separate truncation issues on cat/subcat and redemption files | 02/20/2017 |
| 2.1.0.2 | Removed unnecessary plugins from the message service installation path to reduce load placed on MSMQ. | 02/16/2017 |
| 2.1.0.1 | Brought in changes from 2.0.2.5 that was inadvertently left out of the 2.1.0.0 build. | 02/15/2017 |
| 2.1.0.0 | Major improvements in file processing performance, plus some configuration toolkit and installer tweaks. | 02/10/2017 |
| Version | Summary | Release Date |
|---|---|---|
| 2.0.2.5 | Corrected an issue with the Category Subcategory file conversion, and an issue where large HGTNs were not handled correctly in the Redemption File. | 01/24/2017 |
| 2.0.2.4 | Corrected a specific issue introduced in 2.0.1.5 with "pre-formatted" files. | 12/22/2016 |
| 2.0.2.3 | Change to support more effectively support card diagnostics in a Smart Card environment. | 12/22/2016 |
| 2.0.2.2 | Bug fixes for File Processing. | 12/21/2016 |
| 2.0.2.1 | Bug fixes for File Processing, additional support for communication with the Solutran S3 system. | 12/20/2016 |
| 2.0.2.0 | Bug fixes for File Processing, additional support for smart card including split routing of messages and confirmation of message completion. | 12/18/2016 |
| 2.0.1.5 | Bug fixes for File Processing. | 12/16/2016 |
| 2.0.1.4 | Bug fixes for File Processing. | 12/12/2016 |
| 2.0.1.3 | Bug fixes for File Processing. | 12/01/2016 |
| 2.0.1.2 | Support for S3 in Montana, support for Smart Card diagnostic tools, bug fixes. | 12/01/2016 |
| 2.0.1.1 | Empty Files Cause a Processing Error. | 11/28/2016 |
| 2.0.1.0 | Update to incorporate Smart Card changes and bug fixes. | 11/23/2016 |
| 2.0.0.10 | Major update adding support for a new SPIRIT interface to the WEM Middleware. | 11/04/2016 |
| Version | Summary | Release Date |
|---|---|---|
| 1.0.0.31 | Corrective release to address an issue with an incompatibility related to the database interface and the high availability group cluster. | 06/17/2016 |
| 1.0.0.30 | Corrective release containing fixes for 3 bugs and an enhancement. | 06/08/2016 |
| 1.0.0.27 | This is the first official release. It corrects several issues found during UAT. | 05/04/2016 |
| 1.0.0.23 | This was the UAT release of the software. All known issues have been resolved via incremental patches against internal development and QA environments. | 04/07/2016 |
| 1.0.0.13 | This was the first 'complete' build of the software, with all of the components represented. | 03/09/2016 |
| 1.0.0.10 | Corrective release to address an issue where success was returned when message processing failed. | 03/04/2016 |
| 1.0.0.7 | Added support for Account Setup and Benefit Transaction Messages. | 03/02/2016 |
| 1.0.0.1 | Initial Release. | 02/14/2016 |