7.6 Modifying Configuration Information in ConsoleOne

  1. Start ConsoleOne on Windows.

  2. Connect to the domain that owns the migrated post office.

  3. Perform the following modifications:

  4. When you are finished working in ConsoleOne and have verified your configuration changes, skip to Section 7.7, Stopping the Source POA.

7.6.1 Reconfiguring the Migrated Post Office

  1. Browse to and right-click the Post Office object, then click Properties.

  2. Click GroupWise > Identification.

  3. In the UNC Path field, change the path to the location on the destination Linux server where you copied the post office. For example:

    \\linuxsvr3\gwsystem\research

    For a Linux server, ConsoleOne interprets the UNC path as a Linux path. Do not put a Linux path with front slashes in the UNC Path field, because backslashes are expected.

  4. Click OK to save the new Linux path information for the post office.

  5. Continue with Reconfiguring the Migrated POA.

7.6.2 Reconfiguring the Migrated POA

  1. In ConsoleOne, browse to and right-click the POA object for the post office, then click Properties.

  2. Click GroupWise > Identification.

  3. In the Platform field, select Linux, then click Apply.

  4. Click GroupWise > Log Settings.

  5. Make sure that the Log File Path field is empty so that the Linux POA creates its log files in the default location (/var/log/novell/groupwise/post_office_name.poa) on the Linux server.

  6. Click OK to save the configuration information for the Linux POA.

  7. If you need to copy document storage areas to the Linux server, continue with Moving Remote Document Storage Areas.

    or

    Skip to Section 7.6.8, Verifying the Post Office Configuration Changes.

7.6.3 Moving Remote Document Storage Areas

For background information about this process, see Section 4.4.3, Remote Document Storage Areas for a Post Office.

If the Server Migration Utility detected one or more remote document storage areas belonging to a post office, it provided a list of their locations as described in Section 7.2, Handling Remote Document Storage Areas. To move your remote storage locations:

  1. Mount each remote document storage area to the Linux server where you want the remote document storage area to reside.

    If you need help with a mount command, see Section 1.1, Mount Commands to review the mount commands used by the Server Migration Utility.

  2. On the Linux server, change to the directory where you had the Server Migration Utility store the Linux RPMs during the migration (worksheet item 7)

    The default location is /tmp/groupwise/software/bin. At this point in the migration process, the GroupWise Database Copy utility (DBCopy) has been installed, so you can use it to manually copy the remote document storage areas.

  3. Copy each remote document storage area to its planned destination (worksheet item 8), using the following dbcopy command:

    ./dbcopy -m -b /storage_area_directory /destination_directory

    The -m switch indicates that DBCopy is being used for migration to Linux.The -b switch indicates that DBCopy is being used to migrate a documentation storage area containing document BLOB (binary large object) files.

  4. Continue with Reconfiguring Remote Document Storage Areas.

7.6.4 Reconfiguring Remote Document Storage Areas

  1. In ConsoleOne, browse to and right-click a Library object for the post office, then click Properties.

  2. Click GroupWise > Storage Areas.

  3. Select a storage area, then click Edit.

  4. In the Linux Path field, specify the full path for the remote document storage area, then click OK.

    NOTE:Do not edit the UNC path. Editing the UNC Path might cause the path format to become invalid.

  5. Repeat Step 3 and Step 4 for each storage area in the list, then click OK.

  6. Repeat Step 1 through Step 6 for each library in the post office.

  7. If using SSL continue with Reconfiguring SSL Certificates.

    or

    Skip to Section 7.6.7, Updating the POA IP Address.

7.6.5 Reconfiguring SSL Certificates

  1. In ConsoleOne, browse to and right-click the POA object for the post office, then click Properties.

  2. Click GroupWise > SSL Settings.

  3. In the Certificate file field, change the path to the location of the certificate file on the destination Linux server. For example:

    /opt/novell/groupwise/agents/bin/certificate_file_name.crt

  4. In the SSL key file field, change the path to the location of the SSL key file on the destination Linux server. For example:

    /opt/novell/groupwise/agents/bin/key_file_name.key

  5. Click OK to save the changes.

  6. If using WebAccess, continue with Update Post Office Links for WebAccess.

    or

    Skip to Section 7.6.7, Updating the POA IP Address.

7.6.6 Update Post Office Links for WebAccess

  1. In ConsoleOne, browse to and right-click the WebAccess object, then click Properties.

  2. Click Post Office Links.

  3. Select the appropriate post office and click Edit Link.

  4. Select an Access Mode from the drop-down menu.

  5. Fill in the required information for your new post office location.

  6. Click OK and OK again to save your new settings.

  7. Continue with Updating the POA IP Address.

7.6.7 Updating the POA IP Address

Updating the POA IP address must be the last configuration change you make in ConsoleOne. After you change the IP address, the POA can no longer communicate with the MTA because it is no longer using the IP address the MTA is configured to expect.

  1. In ConsoleOne, browse to and right-click the POA object for the post office, then click Properties.

  2. Click GroupWise > Network Address.

  3. In the TCP/IP Address field, specify the IP address of the destination Linux server.

  4. Click OK to save the new IP address.

  5. Continue with Verifying the Post Office Configuration Changes.

7.6.8 Verifying the Post Office Configuration Changes

You can verify that the configuration changes have been replicated to the domain at the POA Web console.

  1. Display the POA Web console.

    http://source_server_address:port_number

    For more information about the POA Web console, see Using the POA Web Console in Post Office Agent in the GroupWise 7 Administration Guide.

  2. Click MTP Status to check the status of the link between the MTA for the domain and the source POA on NetWare or Windows.

    The Receive link should display Closed because the MTA is now configured to communicate with the migrated post office’s POA on a new IP address.

  3. Continue with Stopping the Source POA.