7.6 Modifying Configuration Information in ConsoleOne

IMPORTANT:Do not proceed with the following steps unless you are ready to stop the original POA on the source server for the last time.

  1. Start ConsoleOne on Windows.

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

  3. Perform the following modifications to GroupWise objects:

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

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. Ensure 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. (Conditional) If you need to copy document storage areas to the Linux server, continue with Handling Remote Document Storage Areas.

    or

    Skip to Verifying the Post Office Configuration Changes.

7.6.3 Handling Remote Document Storage Areas

For background information about this process, see 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. See Verifying Remote Document Storage Areas. At this point, you must physically move the remote document storage areas to their new locations on the Linux server and reconfigure their associated Library objects for the new locations.

Moving Remote Document Storage Areas

  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 Mount Commands to review the mount commands used by the Server Migration Utility.

  2. On the Linux server, change to the folder where you had the Server Migration Utility store the Linux RPMs during the migration.

    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, using the following dbcopy command:

    ./dbcopy -m -b /storage_area_folder /destination_folder

    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.

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.

    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. Continue with Reconfiguring SSL Settings.

7.6.4 Reconfiguring SSL Settings

If you have not already followed the general instructions in Handling SSL Certificate and Key Files:

  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. (Conditional) If you are using WebAccess on GroupWise 8, continue with Updating Post Office Links for WebAccess (GroupWise 8 Only).

    or

    Skip to Updating the POA IP Address.

7.6.5 Updating Post Office Links for WebAccess (GroupWise 8 Only)

  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 twice to save your new settings.

  7. Continue with Updating the POA IP Address.

7.6.6 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 that 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.7 Verifying the Post Office Configuration Changes

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

  1. Display the POA console for the original POA.

    http://source_server_address:port_number
  2. Click MTP Status to check the status of the link between the MTA for the domain and the original POA on the source NetWare or Windows server.

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

  3. Continue with Stopping the Original POA on the Source Server.