Before installing Messenger, ensure that your system meets the following requirements:
GroupWise Messenger 18 administration is done through GroupWise 18. You must have a GroupWise 18 system installed with at least one domain and at least one GroupWise Post Office before installing Messenger 18. Once installed, Messenger uses the LDAP information (eDirectory, Active Directory, and GroupWise LDAP) and can incorporate users from GroupWise. For more information on installing GroupWise 18, see the GroupWise 18 Installation Guide. In addition, you need the following configured in GroupWise:
A license needs to be configured for GroupWise. For more information, see
Licensing in the GroupWise 18 Administration Guide.
LDAP needs to be configured on the GroupWise Message Transfer Agent (MTA) for authentication. For information on configuring LDAP, see
Configuring the GroupWise LDAP Server in the GroupWise 18 Administration Guide.
Any of the following operating systems:
Micro Focus Open Enterprise Server (OES) 2018, plus the latest Support Pack
SUSE Linux Enterprise Server (SLES) 12, plus the latest Support Pack
New in Messenger 18.1: SUSE Linux Enterprise Server (SLES) 15, plus the latest Support Pack
NOTE:When installing on SLES 15, you must have the following installed on the server before installing Messenger:
Legacy module (For information on installing SLES 15 modules, see SUSE documentation, Modules & Extensions Quick Start.)
IMPORTANT:The glibc-32bit RPM is required before installing the Messenger 18 RPMs. Some versions of SLES do not have this RPM installed by default. If your server does not have this RPM installed, please do so before attempting to install the Messenger RPMs.
NOTE:Messenger 18.x is not supported in a clustered environment.
Hardware and Software requirements:
2.2 GHz processor; multi-processor system recommended
Static IP address
8 GB RAM
40 GB for the Messenger software and database.
Server Certificate requirements:
For a secure Messenger system, you should configure the server and agents to use TLS. We recommend you use commercially signed certificates from a Trusted Root Certificate Authority (CA). For example, GoDaddy, Digicert, and so forth). For your convenience, Messenger can generate certificates until you obtain your commercially signed certificates. When generating certificates, keep in mind the following certificate best practices for Messenger:
If you obtain your certificates from an intermediate CA, the certificate for that intermediate CA and all other intermediate CAs leading to the Trusted Root CA must be appended to your certificate file.
For TLS communication between the agents and server, the Fully Qualified Domain Name (FQDN) of the server should be used for the Subject Alternative Name (SAN) on the certificate. Also, the Messenger agents should be configured with the FQDN instead of the IP address.
IMPORTANT:The certificates must be in PEM format for Messenger to use them. The private key for the PEM certificate does not have a password.
Further guidance on creating certificates for GroupWise can be found in
Configuring Server Certificates and TLS in the GroupWise 18 Administration Guide.
You must have the following rights when you run the Messenger Installation program:
Root rights to the server where the Messenger agents will be installed