Gordon Welling Admin Group

Manager Technnical Support Services
Joined: 11-December-2003 Location: Canada Posts: 550
|
| Posted: 20-August-2008 at 5:02pm
|
|
|
In addition to the information in the Riva Enterprise for Linux Admin Guide forum post, the following are the steps to install and configure Riva Enterprise Edition on Linux. One of the limitations of running GroupWise on Linux is the fact it is not possible to create a GroupWise Trusted Application key does not exist on the Linux platform. The Trusted Application Key must therefore be created on a Windows box (virtual or desktop is fine). Step One: Install Riva from a Windows Machine to Create the Trusted Application Key on the GroupWise System To configure Riva Enterprise Edition, follow the Installation Guide up to page 16: http://www.omni-ts.com/documentation/messaging/riva-setup-an d-licensing-guide.pdf Work through the initial installation and create the Trusted Application Key on a Windows box (virtual or other) that has the GroupWise and Novell clients installed. This is the same process you would have gone through to install the BlackBerry Enterprise Server or GroupWise Mobile Server or many archiving solutions if you have ever configured a trusted application key for those types of systems. Before installing the GroupWise Trusted Application, you must be authenticated to the eDirectory tree that contains the GroupWise system information. You must have supervisor rights to the eDirectory system, the eDirectory GroupWise objects and supervisor file system rights to the directory that contains the GroupWise Domain file system. If GroupWise is running on Linux, you must be able to access the GroupWise domain file system structure with either a SAMBA share or a NSS share. To confirm you have appropriate rights, you should be able to map a drive to the Linux server running GroupWise and be able to use ConsoleOne to access the GroupWise objects on that server. The eDirectory account you are logged in as when you create the trusted application key does not need to have a GroupWise account. The account you use to test the trusted key during the installation must have a GroupWise account. It can be any valid GroupWise account on the system. It does not have to have supervisor rights to the GroupWise system. Make sure you save the trusted application key to a file after creating the key. When you get to the trusted application key step during Step Two, the installation on the Linux system, you will open the file you saved and copy the name of the key and trusted application value into the appropriate fields in the installation screen. This allows you to use the key created from the Windows installation with the Linux configuration. After generating the trusted application key, refer to your POA screen. There will be an administrative acknowledgment that the trusted key was registered on your system. Until that acknowledgment is processed, the connection test will fail. You can see what the acknowledgment looks like with GroupWise running on a NetWare server on page 13 of the installation guide: http://www.omni-ts.com/documentation/messaging/riva-setup-an d-licensing-guide.pdf With GroupWise running on NetWare, the text it records is:
Code:
| ADM: Completed: Update object in Post Office - Trusted Application (Domain: XXX) |
|
|
After the trusted key is properly registered, the Trusted Application will display in the ConsoleOne Trusted Application Tab. There is nothing that needs to be done in ConsoleOne to register or configure the trusted key. After this is completed, you can exit the Windows installation process. Step Two: Install Riva on the Linux System Download the latest release of Riva which contains the required installation files from: http://www.omni-ts.com/download/riva-collaboration.html Extract the riva-latest.zip file and refer to the Riva Enterprise for Linux Admin Guide for specific installation steps which includes latest information on how to prepare your server. This includes directions on how to update to Mono 1.9.1 if it is not already on your system and which Mono components are required for Riva. One of the limitations of running Riva on Linux is that it will not be able to run policies, applications or reports that user the Windows Object or Admin APIs. Please refer to Riva Modules Available on Linux for the complete list of policies, applications and reports that are available on Riva running on Linux.
After Riva Enterprise is installed on your system, please refer to Riva CRM Enterprise Edition - Installation and Configuration to configure Riva on Linux for CRM integration.
Depending on the CRM you are using, you will need to configure the appropriate authentication strategy. By default, SugarCRM Professional and Enterprise and Info@hand version 5.3.2 support sudo mode (Impersonation). Please refer to the following forum posts for instructions that your environment: Step Three: Request Licence File
After you configure Riva your Riva CRM policy, right-click the policy, select "Request Licence", select the Riva CRM checkbox, select the Request a Trial Licence radio button, select the CRM Synchronization checkbox, select Yes to continue. Work through the process and send us the resulting file. When you receive the file, copy it to the Riva\Licenses directory and restart Riva.
Edited by Gordon Welling on 04-September-2008 at 4:44pm
|