|
System Requirements |
Top Previous Next |
|
Client: • Windows based PC any currently supported Microsoft Windows Operating Systems. • Microsoft's .NET Framework Version 4.5 with latest service pack applied. • Rumba Version 7.1.1 or later • 10 MB of hard disk space for installation plus space for processing files • Minimum RAM requirements will vary but will also be affected by the number and type of scripts that will execute. Please allow more RAM if you intend to run a high volume of scripts (more than 5 mainframe scripts at a time) or run frequent web scripts. • For Mainframe or AS/400 scripts, there should be enough available LU’s (Logical Units or Terminal ID’s) to support the highest number of simultaneous mainframe connections that EMUE needs to make. • For web scripts, Internet Explorer 10 or 11. See Appendix C: Internet Explorer Support Policy
Mainframe Applications: • A SNA Server, Novell SAA Server, or TN3270 Server available for Rumba Mainframe – 3270 connection. • For SIGNATURE and INVISION, a separate Logon ID and Password for each simultaneous connection to the application (preferably a dedicated login that is reserved for EMUE). For other applications, multiple simultaneous scripts may be able to share the same Logon ID. Either way we recommend that the sign-ons that EMUE use be dedicated for use by EMUE.
AS/400 Applications: • The application should be available via 5250 terminal connection. • Some applications allow one signon to be logged in multiple times simultaneously. Depending on the application you are working with a Logon ID and Password for each simultaneous connection to the application may be required. For MS4, this is not required, but is recommended. Either way we recommend that the sign-ons that EMUE use be dedicated for use by EMUE.
Web Applications: • EMUE can successfully script web applications that present their interface via HTML, including AJAX and other related technologies. • Logon and password requirements will vary from one application to the next. Usually it is preferable to use logons that are dedicated to EMUE.
Windows Applications: • EMUE can successfully script windows applications via a thick client install.
Environment: • An available SMTP server that can relay email from EMUE to desired recipients. Emails from EMUE are not encrypted, therefore, we recommend that you only reference an SMTP server that is located inside your network (not via the internet) and that the PC only be allowed to relay emails to internal addresses and not external (internet) addresses. • A local computer or domain user account designated to run EMUE. This account should: o Be able to remain signed on to the workstation at all times in order to start script automatically or by schedule (workstation locked is OK). o Have access to all network locations to be used for input files, log files, etc. o Preferably be a dedicated account, which is used only by EMUE. o Be enabled to automatically sign-on to Windows upon restart if possible. • Remote Desktop can be enabled on a Windows 10 PC in order to facilitate sharing. Terminal Services can be used on a Windows 2012R2 Server, Windows 2016 Server or Windows 2019 Server in Administration Mode only (Not User Mode). RDP client access to the server should specify the /CONSOLE option in order to force the use of a shared console session. • EMUE is tested with a standard Windows user account with UAC enabled at the most restrictive level. At that level, all EMUE functions and features are fully operational. Some IT departments may decide to reduce permission levels even further. Those restrictions may prevent functionality.
|