This topic describes how the users on the production Lotus® Expeditor Server 6.1 system will be moved onto the Lotus Expeditor Server 6.2 system, after you have performed and tested the migration.
Before final migration from the Lotus Expeditor Server 6.1.x production system to the new Lotus Expeditor Server 6.2 system, you must confirm success of the following items:
- Installation and configuration of the target Lotus Expeditor Server 6.2 system
- Identification of all components to be migrated
- Successful migration of components from Lotus Expeditor Server 6.1 system to Lotus Expeditor Server 6.2 system
- Testing and confirmation that you have migrated all functionality required and met QA exit criteria using a limited test user subset. Testing should cover:
- Verify security is correctly configured by logging on the WebSphere® Application Server administration console with the Lotus Expeditor admin user ID and password.
- Verify that a sample of expected users and groups can be seen from the WebSphere Application Server administration console.
- DB2® Everyplace® client applications sync successfully with the server.
- Test clients can register with Client Management Services, inventory tasks run successfully, and software tasks can be distributed to test clients.
- MQ Everyplace applications work successfully.
- Scheduling of a maintenance window of Lotus Expeditor Server 6.1 that enables the final migration to Lotus Expeditor Server 6.2.
At the scheduled WebSphere Everyplace Deployment 6.1 maintenance window, the following occurs:
- # The Lotus Expeditor Server 6.1 system will be taken offline, preventing any further changes to the component user data.
- # The components targeted for migration will be migrated again from the Lotus Expeditor Server 6.1 system.
- # The user data of each component will be the most current available data, and the starting point for the user data of the Lotus Expeditor Server 6.2 system. (All test data currently contained on the Lotus Expeditor Server 6.2 system will be replaced by this migration procedure)
- The Lotus Expeditor Server 6.2 server will be brought online and access will be allowed.
- At this point, Lotus Expeditor Server 6.1 clients must redirected to the Lotus Expeditor Server 6.2 system. There are three options to enable this:
- Option 1: Update DNS entry for the Lotus Expeditor Server 6.1 host to point to the IP address of the Lotus Expeditor Server 6.2 host. Use this option if you want to recycle server running Lotus Expeditor Server 6.1 and do not want to keep it for emergency switch back. Also, this method is useful if you are using MQ Everyplace applications and you do not want to update the host name used by your MQ Everyplace client applications.
- Option 2: Update the HTTP server plug-in on the Lotus Expeditor Server 6.1 host to route requests to the Lotus Expeditor Server 6.2 system. Use this option if you want to keep the Lotus Expeditor Server 6.1 around for emergency switch back. This option is not available if you are using MQ Everyplace applications since MQ Everyplace does not utilize HTTP. To update the HTTP server plug-in on the Lotus Expeditor Server 6.1 system, follow these steps:
Option 3: Update the client configuration to change the server address to the new Lotus Expeditor Server 6.2 system. The server address is stored in multiple places depending upon the usage of MQe applications, DB2e synchronization, and client management. This methodology can be used in conjunction with one of the other options or by itself. For example, you could employ the option of using a DNS update as a temporary measure to direct all clients to the new server. At that point, the individual clients could be updated with the correct address.
- Upgrade the WebSphere Web server plug-in to the version for WAS 6.1. WebSphere Application Server v6.1 web server plugin supports interacting with WebSphere Application Server v6.02. The reverse is not supported (6.02 Web server plugin talking with WebSphere6.1 server).
- Apply the same fix pack level being used by the Lotus Expeditor Server 6.2 system to the WebSphereApplication Server 6 HTTP server and plug-in on the original WebSphere Everyplace Deployment 6.0 HTTP server.
- Copy the plugin.xml file from the Lotus Expeditor Server 6.2 system to the Lotus Expeditor Server 6.1 system.
- Make a backup of the httpd.conf file used by the HTTP server.
- Edit the httpd.conf file used by the HTTP server on the Lotus Expeditor Server 6.1 system and change the WebSpherePluginConfig statement to point to the plugin.xml file copied from the Lotus Expeditor Server 6.2 system.
Sunsetting of the Lotus Expeditor 6.1 Server
If you chose option 1 in the final migration steps above, you can recycle it for other uses after your final migration testing is completed and your Lotus Expeditor 6.2 system is working as desired.
If you chose option 2 in the final migration steps above, you should wait to recycle the 6.1 system after all clients have started using the Lotus Expeditor 6.2 system directly. You can check the HTTP server access log to determine how much traffic your HTTP server is seeing from 6.1 clients. Also, you may schedule a Client Management job or client management services task to update the host name for the 6.1 client being managed by the 6.1 server. See Client Migration for instructions on how to configure the host name update job. After the clients connect to the server and process this job, they should connect directly with the Lotus Expeditor 6.2. You can use the Client Management console to view clients that have successfully run the job.
Switch back to Lotus Expeditor Server 6.2
Option 2 allows the Lotus Expeditor Server 6.1 system to stay intact, allowing for emergency switch back to the previous configuration in the event of a Lotus Expeditor Server 6.2 problem.
Any switch back performed is expected to be done in a short amount of time after the final migration. After clients have migrated to the Lotus Expeditor Server 6.2 client, they will need to reinstall the Lotus Expeditor Server 6.1 client if a switch back is performed.
The procedure for switching back to the Lotus Expeditor Server 6.1 server is:
- Shut down the HTTP server.
- Restore the backup of the httpd.conf file.
- Restart the HTTP Server.
- Start all Lotus Expeditor Server 6.1 component servers.
This topic provides instructions on upgrading the network configuration of all existing clients to the Lotus Expeditor Server 6.2. After the Lotus Expeditor Server 6.2 server comes online, you need to initiate the process upgrading and updating the network configuration of all existing clients to the Lotus Expeditor Server 6.2 server. You have the option of using one or more of the following methods to upgrade your users:
- New Device Manager Services jobs - You can create Device Manager jobs to update the Client Management server host name configured in existing clients. You can use this process instead of one of the techniques above to switch Lotus Expeditor 6.1 users to the new Lotus Expeditor Server 6.2. Perform the following steps to create a job to update the Client Management server host name:
- Start the Device Manager Server console and log into the Lotus Expeditor Server 6.1.
- Select Device Classes.
- Right click on the device class for your target devices (for instance, Win32, Linux®, OSGi) and select Submit job.
- On the target device panel, select the option to target the job to all devices in the device class (for instance, Win32, Linux, OSGi) and select the status of currently enrolled devices.
- Click Next to continue.
- On the job attribute panel, fill in the following information:
Click Next to continue.
On the job parameters panel, select DM Account, click on Add Group and fill in the following information:
- Job Type: Device Configuration
- Description: Description of the job (for example, Update Server host name for Win32 devices)
# Click Next to continue.
# On the Summary panel, click OK.
# Click Close on the window showing the job was created successfully.
- Action: Modify
- Name: Name of the OSGi account on the client.
- Address: Client Management server URL with new host name (for instance, http://newhost/dmserver/OMADMServletAuthRequired)
Configure a Client Management Services Task to update the enterprise management agent account to access the new Lotus Expeditor Server 6.2. This process can be utilized after using one of the methods to switch the Expeditor 6.1 users to use the Lotus Expeditor Server 6.2.
The Lotus Expeditor administrators can contact users, informing them of the need to:
- Reconfigure their devices with the new host name and confirm that Client Management is enabled.
- Install the client upgrade to Lotus Expeditor 6.1 manually.
See Developing Applications for Lotus Expeditor 6.1.x
for more information on the migrating clients.
Parent topic: Migrating from Lotus Expeditor Server 6.1.x to 6.2: XPD622