Show Hide

 

Feedback

  • Contents
 

Configure a GroupWise provider

To configure a GroupWise provider

  1. In the Mail Configuration dialog box, click the Providers tab. For information on how to access the Mail Configuration dialog box, see Configure a Mail storage source.

  2. In the list of providers, select GroupWise.

  3. Click Enable Provider.

  4. In the GroupWise Configuration dialog box, in the Server box, type the name or IP address of the GroupWise server hosting the POA containing the most CIC users. While the new GroupWise Connector can connect to any POA with SOAP enabled, it is most efficient to connect to the POA that will be used the most. If the GroupWise Connector attempts to access a mailbox on a different post office than the one handled by the POA selected here, it will be redirected to the correct POA.

  5. In the Port field, select the port value. The port value should be the same as the SOAP port for this POA, which by default is 7191. If the POA uses a different port value, select it here.  

  6. In the Username box, type the account that will be used to access the system address book and to send voice mails left by external callers. Typically, it is an account created just for use by CIC.

  7. Click Browse to select the GWTApp.xml file from the appropriate CIC server directory.

    The Groupwise Connector requires that you install CIC as a Trusted Application in GroupWise. This enables CIC to automatically provide GroupWise users access to their mailboxes through email or TUI.

    If you have not yet generated the Trusted Application Key file in ConsoleOne and copied the resulting GWTApp.xml file to a directory on the CIC Server, do so now. For instructions, see the Novell GroupWise Support for CIC Technical Reference in the PureConnect Documentation Library.

  8. To authenticate the server and encrypt subsequent communications, select Use Secure Connections (SSL/TLS).

    If you are using TLS/TLS for SOAP and have obtained the certificate, assigned it to the POA, and enabled SSL for SOAP in the POA, select this option to enable SSL for SOAP in CIC.
    Prerequisites: The server certificate must be available and trusted, before Use Secure Connections (TLS) takes effect.  For more information see CIC Security Features in the PureConnect Documentation Library.

Note: GroupWise uses certificates stored in the Windows certificate store. The GroupWise server has to be using a certificate that has been issued by a CA (Certification Authority, like Verisign) and trusted in the Windows certificate store. If the certificate is self-signed (not issued by a CA), manually add the server’s certificate to your Windows certificate store. To view certificates, run the certificate manager (certmgr.msc) from the Start menu.

Examples:

• The GroupWise administrator has a certificate issued from Verisign. Since Verisign shows up in certmgr.msc under Trusted Root Certification Authorities, just select Use Secure Connections (TLS), and TLS is enabled.

• The GroupWise administrator has a certificate issued from a certificate shop that does not have a Windows certificate store listing. Manually add the certificate to your Trusted Root Certification Authorities, then select Use Secure Connections (TLS).

• The GroupWise administrator created a self-signed certificate (not issued by a CA). Manually add the certificate to your Trusted Root Certification Authorities, then select Use Secure Connections (TLS).

  1. To enable GroupWise server tracing for troubleshooting purposes, select the Enable GroupWise Server-side Tracing checkbox.

Note: For more information, see Novell GroupWise Support for CIC in the Technical Reference Documents section of the PureConnect Documentation Library.

  1. Click OK.

 

Related topics

Configure a Mail storage source

GroupWise requirements