High Level Architecture of a typical deployment and recommended architecture implementation:
Manageability
1. Average size of DB + Growth rate? (Sample of typical deployment)?
Average SQL DB is 75 Mb (with 250 users). The database size will increase by 10 -15 % year over year. (Assuming upgrades are implemented and user growth is equal to or less than initial roll-out.)
2. Supported OS (+patch level):
WIC Server requires Windows 2k3 (including all service packs).
3. Supported DB (+patch Level):
Microsoft SQL 2000 (including all service packs)Microsoft MSDE 2000Microsoft SQL 2005 (including all service packs)My SQL.
4. Supported BES (+patch Level):
Exchange 4.0 & 4.1 (including all service packs)Domino 4.0 & 4.1 (including all service packs)GroupWise 4.0 & 4.1 (including all service packs).
5. Supported Client OS (+patch level):
OS 4.0, 4.1, 4.2 and 4.3 (including all point releases).
6. Recommended Specs for Application server and DB server.
Software: Windows 2003 Server: Service Pack 1MS SQL Server 2000BlackBerry® Enterprise Server (with Mobile Data Service enabled)- Microsoft Exchange version 4.1- IBM Lotus Domino version 4.1- Novell GroupWise version 4.1Handhelds at 4.1 or 4.2Microsoft Internet Explorer 6.0 Hardware : Dual PIV (2.5 GHz or higher) 2 GB RAM 100 GB Hard Drive T1 Internet Connection.
7. Recommended Spec on Blackberry device HW + OS to support client application:
32 Mb (or greater) Colour BlackBerry with OS 4.1 or greater.
8. Is there any additional customization, or programming requirements:
There are no additional requirements.
9. How the data is secured between the secure environment and non-RIM devices/e-mail:
Data transferred through BES MDS therefore, fully encrypted (3DES).
10. Software Life-cycle, availability of major release or patches:
Access to major releases or patches is available via the Wallace FTP site or CD. Yearly support includes all patches and / or upgrades to the Wallace software. Upon release, Wallace will notify all customers needing an upgrade / patches and schedule time to assist with the changes.
11. Communications can be logged to external compliance engines which ones are supported?
USA Patriot Act, Sarbanes-Oxley, NASD Rules, NYSE Rule 446,
California’s S.B. 1386, Gramm-Leach Bliley Act.
12. Typical upgrade procedure:
Unless the upgrade is custom request, Wallace provides an installer that will automatically add the additional files / configuration to the WIC server. The handheld clients can be upgraded either through BES Wireless PUSH or manually through OTA (over-the-air) deployment.
13. Desktop Administrator is a client application; can this be installed on multiple desktops?
There is no limitation to the number of WIC administrators installed on desktop computers.
14. Licensing for DR (stand-by server):
There may be an additional fee for redundant server(s).
15. Able to run on VM environment?
Yes, the WIC server can run in a 2k3 VM environment.
16. Recommended method to synchronize DR:
A scheduled backup of the production WIC database restored to the redundant WIC database is recommended. The frequency of the backup should be relative to the number of changes within the WIC system. (IE: Document changes occur weekly therefore, synchronization should be equal to or greater than once a week.)
17. DR execution or fail-over:
The WIC redundant solution is a “cold” back-up. It is recommended that the following points are considered when creating a fail-over process:
18. The WIC Application Server should be tied to the BES redundancy process / strategy:
WIC handheld clients make a call to the WIC Application Server either through an IP or Hostname. Therefore, if the production server was to fail, the hostname can be used to point to the redundant server’s IP or the IP would need to be changed manually on each Blackberry with WIC installed.
If the WIC DB failed an administrator could switch to the mirrored DB using the WICAdmin interface without switching WIC or BES servers. o The redundant plan assumes that there is a back-up BES server that has an identical SRP key.
19. Daily, Weekly or Monthly operating procedures:
There are no required daily / weekly or monthly maintenance requirements. However, it is strongly recommended that the WIC server be rebooted after all local Windows auto-updates as well as after updates the to SQL server hosting the WIC DB and BES server(s).
20. Scheduled maintenance:
The WIC server does not require specific scheduled maintenance. However, if a redundant WIC environment is configured a weekly backup of the WIC production DB is recommended. Also, a server restart after all updates to the server is required (IE: Windows auto-update).
Integration
1. Any 3rd party integration?
WIC can communicate with any database through an ODBC connection or DB extract / script. Wallace will build custom extractors (if required) however, additional changes may apply.
Security
1. Support for LDAP or Active Directory for user authentication?
WIC supports LDAP or Active Directory for user authentication. The two supported authentication types (for administrators) are: Windows NTo SQL.