7019091: Retain 3.5.1 Requires Java 6 build 38

This document (7019091) is provided subject to the disclaimer at the end of this document.

Environment

Retain 3.5.1 only

Situation

I have Java 7 installed on my Windows 2012 server. When I run the Retain installer, it tells me that I do not have Java 6 installed. It then forces me to install Java 6. Why is this?

Resolution

Retain 3.x requires Java 6 build 38. To avoid potential incompatibilities or issues with newer versions of Java, the installer forces the Java 6 installation. Retain 4 will require Java 8 and will manifest the same behavior as the 3.5.1 installer, forcing the installation of Java 8 in order to avoid potential issues for a customer’s Retain system.

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2568.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7019090: How to Upgrade Retain (Masterpost)

Since you will be bringing down the server for the upgrade anyway, it is a good idea to see how well your system conforms to our Best Practices.

If you are already running Retain 3.x code upgrading is very easy, but first you should back up Retain.

Upgrade: Retain 3.x to Retain 3.x (Linux)

Upgrade: Retain 3.x to Retain 3.x (Windows)

Upgrading from previous versions of Retain

  • If running Retain 1.x, then you must update to Retain 2.6.2 first before going to 3.x. Refer to the Retain online documentation, “Upgrading Previous Retain Versions

Upgrade: Retain 2.x to Retain 3.x (Linux)

Upgrade: Retain 2.x to Retain 3.x (Windows)

Moving Retain to a New Server

Moving Retain To New Server (Linux to Linux)

Moving Retain To New Server (Linux to Windows)

Moving Retain To New Server (Windows to Linux)

Moving Retain To New Server (Windows to Windows)

Upgrading MySQL

Moving MySQL Database to Another Server

MySQL Upgrade (Linux)

MySQL Upgrade (Windows)

How to Revert a Failed 2.x to 3.x Migrated Database


Installing Reporting and Monitoring Server

How to install Reporting and Monitoring Server after Retain has been installed.

Post Install Items

Once you have upgraded Retain also install the software patches.

For more information browse to our support page or give us a call.

Related:

7019087: Installation of the Retain Outlook Web Access 2013 Plugin

This document (7019087) is provided subject to the disclaimer at the end of this document.

Environment


Retain 3.x

Exchange 2013

Situation

Installing the OWA plugin doesn’t go as expected based on the shipping documentation.

Resolution

Follow these steps for proper installation.

Installation:

The plugin must be installed onto your Exchange server.

Download the Retain install package to your Exchange server and extract it. Don’t worry you are not going to install Retain here, just one bit of it.

In the Retain folder go to toolsexchangeOutlook Web Accesstools and find Outlook Web Access Plugin Setup.exe

Double click to start the install process.

  • It will ask what language to continue in.
  • The installer will ask you to choose a file location for the plugin files. The default is C:Program FilesMicrosoftExchange Serverv15ClientAccessOwa
  • You will have to enter the Retain Server Web Address. This may be the IP address or DNS name. For example: http://10.1.2.4/RetainServer or http://retain.gwava.com/RetainServer. It is not necessary to include the Tomcat port (for example: x.x.x.x:48080)
  • You will then have to enter the Outlook Web Access Address. This is the IP or DNS name of your Exchange server. For example: https://10.1.2.3/owa
  • You will then have the choice to restart IIS after the installation is complete. If you opt to not restart IIS, your users will not have access to the plugin until it is.
  • Click on Install to have the plugin installed to your Exchange server.
  • Click Close when it is complete.

Server Side Setup

  • Once IIS completes the startup process log in to the Exchange Admin Center (https://[your exchange server]/ecp).
  • Select Organization from the left sidebar.
  • Select Apps from the pane top tab bar.
  • Click the down-arrow next to the add + icon, and select ‘Add from file’.
  • Browse to the install location C:Program FilesMicrosoftExchange Serverv15ClientAccessOwaRetain and select manifest.xml and Open.
  • Click Next to install to the server, this will make it available for the users to install to their OWAs. If you double click the plugin you can set it to enabled or mandatory for the client.

Client Side Setup

  • Log into the Outlook Web App (https://[yourserver]/owa) as a user.
  • Click the gear icon near the top right next to your users name and select Manage apps…
  • A list of apps available to the users will be listed. Notice that Retain App is available but disabled. Select the Retain app and in the right sidebar click the Enable link.
  • Navigate back to your inbox with the right arrow or by clicking on your username and choosing My Mail.
  • Browse to any message. Within the Viewer pane on the right or if you open the message in its own window, you will see a Retain link inside a grey bar.
  • Clicking the link will reveal a Retain logo image and clicking on that will open a new window in the Retain archive.

Special thanks to Eric Maughan for compiling this information.

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2339.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7019081: Searches aren’t working and Tomcat loads very slowly

Verify that you have the proper file/folder structure in your index directory.

You can find where your index directory is by looking in your ASConfig.cfg file which is located in:

Windows: Program FilesBeginfiniteretainRetainServerWEB-INFcfg

Linux: /opt/beginfinite/retain/RetainServer/WEB-INF/cfg

Search for the tag: <indexPath>

Once you are in your index path verify that you do have at least the following:

…/index/solrhome

…/index/solrhome/solr.xml

…/index/solrhome/zoo.cfg

…/index/solrhome/zoo_data/

If you are missing solr.xml, zoo.cfg, or zoo_data/, move whichever files you do have (not including the retaincore directory) into a temp folder and restart Tomcat. The software should automatically create the necessary files/folders after Tomcat loads.

Related:

7019080: rcgwavaman throwing substring expression error

This document (7019080) is provided subject to the disclaimer at the end of this document.

Environment


GWAVA 6.5

Suse Linux Enterprise Server (11)

Situation

Running “rcgwavaman” from a specific folder is throwing an error:

gwava6:/ # rcgwavaman status

/sbin/rcgwavaman: line 205: $: substring expression < 0

Resolution

The problem is that an empty file with 0 bytes called “a” existed in the folder from which rcgwavaman was run.

A similar problem would also occur if the file would have a different single letter as file name.

To fix the problem either remove the file or rename it to something with more than one letter.

Afterwards it should be possible to run rcgwavaman correctly from that folder again.

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2875.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7019079: Using LDAP to Login to RetainServer When GroupWise No Longer Installed

You can use LDAP to eDirectory. Here are the steps:

1. Configure LDAP authentication in the GroupWise module inside the RetainServer admin UI.

2. Go to the Management menu in the RetainServer navigation pane and select “Groups“. Edit the “default” group and set the “Authentication Method” to “LDAP authentication (GW)” and mark the box, “Use Exclusively“.

2. Edit …/RetainServer/WEB-INF/classes/config/misc.properties.

3. Search for “custom.ldap.enable“, which should take you down to the bottom section of the file.

4. Edit the following lines to read as follows:

custom.ldap.enable=1

custom.ldap.attributes.requested=mail

custom.ldap.attributes.bind=email

custom.ldap.debug=1

custom.ldap.class=com.gwava.authenticate.gw.AlternativeGWLDAPAuthentication

5.Restart Tomcat.

NOTE: User then must login to RetainServer using their full GroupWise email address (user@domain.com). For example, jdoe@xyzcompany.com.



Custom LDAP Settings Explained

Many of these settings cannot be used. They are there for use in the future when this feature is more fully developed. Features for future use that do not offer any functionality or if not fully understood are greyed out.

custom.ldap.enable= 0 | 1 (default = 0).

When set to 0 (default), Retain follows the normal GWLDAP Authentication path (where GroupWise is installed and running) and ignores the custom.ldap settings below.

Set to 1 to enable

custom.ldap.class=[className] (default = com.gwava.authenticate.gw.CustomLDAPAuthenticatorMethod).

The class of the modified java code. Keep it at the default.

custom.ldap.search=[LDAPQuery, using as placeholder for future]

Default is (&(objectClass=Person)(mail=)) Changing this for initial release is not supported.

DO NOT ENTER

custom.ldap.useuid=0 | 1 (default = 0).

If on, expects to have a UID entry. Otherwise currently expects to see an email entry in LDAP.

The name of the attribute is specified and bound elsewhere.

Set to 0.

custom.ldap.applicationuid=0 | 1 (default = 0).

Use if you are supplying an application UID not an internalUID.

It only matters when custom.ldap.useuid=1.

Set to 0.

custom.ldap.emailsystem=gw | exchange | etc (default = gw).

The type of messaging system this applies to. Initially only gw is supported.

Leave it at the default of “gw”.

custom.ldap.attributes.requested=[comma delimited list] (default = mail)

This is a list of LDAP attributes you want requested. It is the user object’s LDAP attribute name from eDirectory (and future, Active Directory, and others).

Case may matter depending on the LDAP server. For a standard GroupWise system, this is GUID, mail,or nGWObjectID. The mail attribute returns the user’s Internet email address.

If requesting multiple attributes, list them in a single line separated by commas with no spaces between the attribute names and the commas (i.e., mail,nGWObjectID).

Recommended to leave at the default of mail.

custom.ldap.attributes.bind=[comma delimited list] (default = email)

This is a list of Retain address book attributes. These attributes correspond with actual field names in the Retain database’s t_abook field. Any one of the following can be listed and they are case sensitive:

This list must be exactly the same number of attributes as listed in the custom.ldap.attributes.requested and needs to be in the order in which you want each attribute to match. For both attributes (LDAP and Retain), the value in the attribute listed in the first position should match the value in the other attribute. Each item in ..attributes.bind maps to the LDAP attribute specified in ..attributes.requested, meaning that Retain will try to match what is returned from the custom.ldap.attributes.requested list with the custom.ldap.attributes.bind list; thus, they should also be in the order in which they should be mapped. If you want the LDAP attribute of mail to map to the Retain attribute of email, they both should be listed at the first item in their respective lists.

EXAMPLE:

If custom.ldap.attributes.requested reads has mail,nGWobjectID, then the custom.ldap.attributes.bind line must read email,mailbox in that order so that mail maps to email and nGWobjectID maps to mailbox. If those values do not match, this will not work; thus, if John Doe’s Internet email address (mail attribute) were jdoe@xyzcompany.com, then the Retain database’s email attribute should also read jdoe@xyzcompany.com or else it will not be able to make a match. Likewise, if nGWobjectID were “jdoe”, then the Retain database’s mailbox attribute better have “jdoe”.

Recommended to leave at the default of email.

custom.ldap.debug=0 | 1 (default = 0)

Set to “1” to generate more diagnostic logging in the RetainServer log.

Related:

7019078: Messages aren’t being uploaded from my Android device

1. Look at your RetainRouter page and see if there is a current last connection time. If your last connection time is current, proceed to step 2.

a. The last connection time will be reset when Tomcat has been restarted. If you restarted Tomcat recently and the last connection time is blank, you will need to allow the allotted time for the Device Transmission Frequency set in your Mobile module.

b. You can force the mobile app to send data to the Router by opening the app, select the more option by tapping on the 3 dots, select Send Data to Router.

c. If your last connection time is still blank, try accessing the RetainRouter URL in a browser on your mobile device. If you are unable to make the connection, then you likely have a network related issue.

d. Look at the logs on the mobile device. Open the mobile app and select the more option by tapping on the 3 dots, select Logs, then Logs again. This may give you more specific reasons of why you aren’t able to make the connection to the Router. If you need help reading the log, please contact support.

2. Review the RetainRouter log.

a. The logs should be located in:

  • Linux: /var/log/retain-tomcat7/RetainRouter.YYYY-MM-DD.log
  • Windows: …Retaintomcat 7.0logsRetainRouter.YYYY-MM-DD.log

b. If you need help with the log, please contact support.

Related:

7019077: Retain Server Android mobile app is not sending data after re-install of the application

This document (7019077) is provided subject to the disclaimer at the end of this document.

Environment


Retain Service Android mobile application

Situation

The Retain Service Android mobile application does not send data after re-install of the application

Resolution

The android mobile application is designed to require a registration when the app is newly installed. This means that if a user deletes the app and re-installs the app, it still will not function. The user is required to contact the administrator and the registration email will need to be resent. If the old version of the json file is still in the downloads folder on the phone, then no further action is required, the app should then send messages like before. If the json file is no longer in the downloads folder of the phone, then proceed with the normal registration process.

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2827.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related: