Contact us at 408.675.5020 or sales@identitymaestro.com

Home Page

Knowledge Base Search     Advanced

[NW] Legacy GroupWise Support: Simple Deployment

Article ID: 384
Last updated: 01 Aug, 2016

[NW] This KB Article needs revision work

These instructions apply to those environments that host GroupWise on NetWare servers or on NSS volumes (NCP mount shares) on Linux servers. 

There are three tasks to configure GroupWise connections:

Install the Remote Agent for GroupWise

If the Remote Agent for GroupWise was not installed on the eControl Host Server, re-run the eControl installation (Window x86 or Windows x64) and ensure that the Remote Agent for GroupWise is selected at the "Custom Setup" window.


Do not configure the "Remote Agent" settings in the eDirectory connection.
 

Create the GroupWise Connection

This process involves running the “Novell GroupWise” connection wizard to create an eControl connection to a target GroupWise domain and post office.  This procedure should detect all of the GroupWise internal domains and post offices and create corresponding GroupWise connections. 

To create the GroupWise system connections:

  1. If the “eControl Connection Config Utility” is not already open, click "Start" > "All Programs" > "Omni" > "eControl" > "Configure Connections". This will open the utility.

  2. Under "New Connection" click the "Novell GroupWise" button.

  3. In the “Welcome to the GroupWise Wizard” window, ensure that the "Enterprise Connection" option is selected, and click Next >.

  4. At the “Trusted Application Key” window:

    ►  Select “Create a new Trusted Application Key” if this is the first installation of eControl and a trusted application key has not been created before (proceed to step 5), or

    Select “Manually Provide an existing Trusted Application Key” option is a trusted key has been created and you have the key information (proceed to step 9).

    Click Next >.

  5. At the “Welcome to the Trusted Application Wizard” window, click Next >.

  6. At the “Collect Trusted Application Parameters” window, specify the path to the wpdomain.db file for the GroupWise domain that Riva will connect to (can be a mapped drive or UNC path to a GroupWise domain hosted on a NSS volume, or a NCP mount share, or a local drive) and the desired Application Name for the trusted key.


    Leave the IP Address field empty.

    Click Next >.

  7. At the “Collect Trusted Application Options” window, ensure that “Overwrite a Trusted Application Key with the same name as this one?” is selected and click Next >.

  8. At the “Generation Successful” window, click “Save to disk …” and save a copy of the trusted key information (tip - save as <keyname>-TrustedKeyInfo.txt in the path of the Domain, e.g. \\Demi\Sys\GrpWise\Dom1\eControl36Key-TrustedKeyInfo.txt. 



    Click Finish.

  9. At the “Trusted Application Key Test” window, specify the Trusted Application Name and Trusted Application Key (if not automatically provided … this can occur if you chose to “Manually Provide an existing Trusted Application Key” in step 4).


    Add the GroupWise Client Address (IP address or DNS name) and Port number of the post office hosting the GroupWise account for the eControl service account, and the corresponding GroupWise account name, and click Next >.

  10. At the “Choose detection type” window, click Next >.

  11. At the “Choose an eDirectory Connection” window, select the eDirectory tree that hosts the GroupWise system and click Next >.

  12. If there are GroupWise post offices that are not configured for SOAP, an “Errors While Detecting GroupWise Configuration” window will open.  Click OK.


     

  13. In the “GroupWise Connection Detected” window, click the GroupWise domain and post office objects that will not be managed by eControl and click Remove.  This will move those objects to the “Connections not to add” text box.



    Click Next >.

  14. In the “Internet Addressing” window, select the applicable Address Format from the drop-down list for the primary internet email address domain and click Next >.

  15. In the “Automatic Configuration Results” window, the GroupWise connections that will be added are displayed. 



    Click Finish
    The eDirectory and GroupWise connections will be visible in connections list.

  16. Repeat steps 1 to 13 for each additional GroupWise system being managed by eControl.

Confirm the GroupWise Connection

This step is necessary to confirm and configure the GroupWise post office connections:

  1. In the connections list panel, open the primary GroupWise Post Office connection by double-clicking the connection object.

  2. Under the “General” tab, confirm that the correct account details are recorded:

    Confirm that the GroupWise trusted application key name is displayed as the “Username”.

  3. Under the “Connections” tab, highlight the client-soap connection target and click the "Test the connection target" link.  Provide a GroupWise account name from this post office to test.



    Click the OK button.

  4. Under the "Test Trusted Key" tab, provide a GroupWise account name to test and click the "Test Key" button.



    Click OK and Save >>.

  5. Repeat steps 1 to 4 for each GroupWise Post Office connection.

Confirm the GroupWise Connections

This step is confirm the GroupWise connection options for the production GroupWise domains and post offices and test connection targets:

  1. In the connections list panel, open the primary GroupWise domain connection by double-clicking the connection object.

  2. Under the “General” tab, confirm that the correct account details are recorded:

     
  3. Under the "Connection Targets" tab, highlight the domain-mtp:// target and confirm that the correct IP address and Port are specified for the domain.
  4. Under the "Options" tab, confirm that the path to the local GroupWise domain is specified.
  5. Choose to Cancel >> to close the domain connection object.  Note that no connection target or trusted key testing is performed on GroupWise domain connection objects.

  6. In the connections list panel, open the primary GroupWise post office connection object.

  7. Under the “General” tab, confirm that the correct account details are recorded:

    Confirm that the GroupWise trusted application key name is displayed as the “Username”.

  8. Under the “Connections” tab, highlight the client-soap connection target and click the "Test the connection target" link.  Provide a GroupWise account name from this post office to test.



    Click the OK button.

  9. Under the "Options" tab, confirm that the path to the local GroupWise domain is specified.

  10. Under the "Test Trusted Key" tab, provide a GroupWise account name to test and click the "Test Key" button.



    Click OK and Save >>.

  11. Repeat steps 6 to 10 for each additional GroupWise post office connection.

Configure the Remote Agent Settings on the eControl Host Server

Perform these steps on the eControl Host Server to configure the eDirectory tree connection remote agent settings to connect back to the GroupWise system through the Remote Agent service:

  1. In the connections list panel, open the eDirectory tree connection by double-clicking the connection object.

  2. Under the “Remote Agent” tab, ensure that the the IP address of the Host server is 127.0.0.1 and choose to Save the connection settings.  Do not test the Remote Agent setting yet.

  3. Open the Windows Services management tool and restart the Omni eControl Connection Agent service.

  4. In the connections list panel, open the eDirectory tree connection by double-clicking the connection object.

  5. Under the “Remote Agent” tab, choose to "Test" the settings.


    The connection should test as successful.  That is the correct result and indicates that requests to the GroupWise system originating from the eControl Host Server and being directed to the Remote Agent Server.  Click OK to close the test window and Cancel to close the eDirectory connection.
     
  6. Perform an IISRESET /RESTART to restart the eControl web server and load the eDirectory and GroupWise connection settings.

This article was:   Helpful | Not helpful Report an issue


Article ID: 384
Last updated: 01 Aug, 2016
Revision: 2
Views: 160
Comments: 0
print  Print email  Email to friend share  Share pool  Add to pool comment  Add comment
Prev     Next
[NW] Options for Connecting ServiceControl to Legacy GroupWise       [NW] Legacy GroupWise Support: Local Domain Deployment