- Riva Integration Server Platform Requirements
- Riva Integration Server for Exchange
- Riva Integration Server for GroupWise
- Riva GroupWise WebParts for SharePoint
Riva Integration Server Platform Requirements
Riva Server Requirements
- Operating System: Windows XP, Windows 7, Windows Server 2003 / 2003 R2 / 2008 / 2008 R2
- Software Requirements: Microsoft .NET 2.0 SP2 +
- Minimum Processor (CPU): Intel P4 / AMD Athlon XP (supports x86 and x64 architectures)
- Minimum Memory (RAM): 256 MB
- Minimum Disk Space: 500 MB
Riva Integration Server for Exchange
- Certified Messaging Systems: Microsoft Exchange 2010, 2007 SP1 with Rollup 1+, 2003 SP1+, On-premise or Hosted.
- Exchange 2010 and 2007: Riva connects to Exchange 2010 and 2007 using Exchange Web Services (EWS). These are installed and configured by default if Web Access in enabled in your environment.
- Exchange 2003: Riva connects to Exchange 2003 using MAPI. This requires the Outlook client be installed on the Riva system. Because of the Outlook client requirement, Riva must run on a system other than the Exchange 2003 server.
- Hosted Exchange: Riva connects to Hosted Exchange systems using API access to Exchange Web Services (EWS). This is the same access as is required to support Apple Mail Exchange Configuration and the latest release of Entourage for Mac (WSE). If your hosted contract provides support for Apple Mail Exchange or Entourage for MAC WSE, Riva is also supported. To configure your connection for Hosted Exchange, provide the URL that is used to connect for Apple Mail Exchange configuration. To date, we have confirmed compatibility with numerous Hosted Exchange systems including BPOS Exchange Online, MailStreet and Intermedia.
: The Exchange connector must be configured with an account that has been assigned "Full Access" or "Impersonate" permissions to the mailboxes to be managed by Riva. This is the same requirement as other third-party sync applications like BlackBerry Enterprise Server.
Riva Integration Server for GroupWise
- Certified Messaging Systems: Novell GroupWise 8+ and 7.0 SP3 + (with SOAP enabled Post Offices)
- Software Requirements:GroupWise client (to match the GroupWise server version). Latest Novell client (to match the version or eDirectory). ConsoleOne with the GroupWise and LDAP snap-ins installed on the server - required primarily for trouble shooting.
- To configure the eDirectory connection and the GroupWise Trusted Application Key, Riva requires an account with Supervisor rights to the eDirectory system and GroupWise primary domain to register the Trusted Application Key. A second option for the Groupwise connector is to use an account that has Read/Write GroupWise proxy access to the accounts that will be synchronised by Riva.
Riva GroupWise WebParts for SharePoint
- GroupWise WebAccess must be installed. We highly recommend a seperate instance of GroupWise WebAccess be used. Riva SharePoint WebParts requires the replacement of the default WebAccess templates that may affect user access to normal WebAccess features.
- GWIA must be installed and configured.
- Users' GroupWise email addresses must the same on GroupWise and SharePoint.
- SOAP must be enabled on your GW post offices.
- The SharePoint server must have access to your GW system (from a firewall perspective).
- SharePoint and WebAccess must exist in the same parent domain (eg: *.omni-ts.com).
- Outbound port 80 is required for the SharePoint server to access the GW WebAccess URLs.
- Outbound port 7191 is required for the SharePoint server to access the Soap services on your GW server.
- To configure the WebAccess security settings, access to ConsoleOne with the GroupWise plug-ins installed is required.
- Access to the WebAccess server's file system is required to update the template files.
- To take advantage of NMAS and provide single-sign for users, make sure password extraction is enabled for users with iManager and a valid SSL certificate is available (LDAP+SSL is required - usually port 636).
- This is no software to configure on the end-users workstations.
For testing purposes, we recommend you set up a new WebAccess Agent (or complete WebAccess installation) on a separate server. That way, testing will not have an impact on your production WebAccess server.