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.
Start ConsoleOne on Windows.
Connect to the domain that owns the migrated post office.
Perform the following modifications to GroupWise objects:
When you are finished working in ConsoleOne and have verified your configuration changes, skip to Section 7.7, Stopping the Original POA on the Source Server.
Browse to and right-click the Post Office object, then click .
Click .
In the 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 field, because backslashes are expected.
Click to save the new Linux path information for the post office.
Continue with Reconfiguring the Migrated POA.
In ConsoleOne, browse to and right-click the POA object for the post office, then click .
Click .
In the field, select , then click .
Click .
Make sure that the 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.
Click to save the configuration information for the Linux POA.
(Conditional) If you need to copy document storage areas to the Linux server, continue with Handling Remote Document Storage Areas.
or
Skip to Section 7.6.7, Verifying the Post Office Configuration Changes.
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, 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.
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.
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.
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.
Continue with Reconfiguring Remote Document Storage Areas.
In ConsoleOne, browse to and right-click a Library object for the post office, then click .
Click .
Select a storage area, then click .
In the field, specify the full path for the remote document storage area, then click .
Do not edit the UNC path. Editing the UNC path might cause the path format to become invalid.
Repeat Step 3 and Step 4 for each storage area in the list, then click .
Repeat Step 1 through Step 6 for each library in the post office.
Continue with Reconfiguring SSL Settings.
If you have not already followed the general instructions in Section 4.6, Handling SSL Certificate and Key Files:
If you have not already followed the general instructions in Section 4.6, Handling SSL Certificate and Key Files:
In ConsoleOne, browse to and right-click the POA object for the post office, then click .
Click .
In the 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
In the 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
Click to save the changes.
(Conditional) If you are using WebAccess, continue with Updating Post Office Links for WebAccess.
or
In ConsoleOne, browse to and right-click the WebAccess object, then click .
Click .
Select the appropriate post office and click .
Select an from the drop-down menu.
Fill in the required information for your new post office location.
Click twice to save your new settings.
Continue with 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.
In ConsoleOne, browse to and right-click the POA object for the post office, then click .
Click .
In the field, specify the IP address of the destination Linux server.
Click to save the new IP address.
Continue with Verifying the Post Office Configuration Changes.
You can verify that the configuration changes have been replicated to the domain at the POA Web console.
Display the POA Web console for the original POA.
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.
Click 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 link should display because the POA is now configured to communicate with the MTA on a new IP address.
Continue with Stopping the Original POA on the Source Server.