Upgrading to Lotus Notes Adapter 6.0
You can upgrade to Lotus Notes Adapter 6.0 from Lotus Notes Adapter 1.0.x.
To upgrade from
Lotus Notes Adapter 1.0.x
1. Alias management and other services that were available with Lotus Notes Adapter 1.0.x are not available in Lotus Notes Adapter 6.0 (see
Unavailable Services and Records for a complete list). If your Lotus Notes Adapter 1.0.x integrations use any services or records that are no longer available, disable or delete the corresponding flow steps in your integrations. If necessary, replace the functionality with other flow or Java services. If you are not sure whether your integrations use any of the unavailable services or records, use the Find Dependents tool in Designer.
For instructions on this step, see the webMethods Service Development Help for your release.
2. Create a list of each alias you currently use in Lotus Notes Adapter 1.0.x. Include all information about the alias, including user, password, and host.
3. In Integration Server Administrator for Lotus Notes Adapter 1.0.x, disable the LotusNotes 1.0.x package. Do not disable the user-defined package that contains your integrations. For instructions, see the webMethods Integration Server Administrator’s Guide for your release.
5. In Integration Server Administrator for Lotus Notes Adapter 6.0, configure a Lotus Notes Adapter 6.0 connection for each alias you recorded in step 2. For instructions, see
Adapter Connections. 6. In Designer, do the following:
a. Configure an adapter service that executes the createSession method in the lotus.domino.Session class for each connection object you created in step 5. For instructions, see
Adapter Services. b. Modify the wm.ln.authentication:login service in the WmLotusNotesAdapter package, as follows:
If you only have one alias, modify the
wm.ln.authentication:login service to call the adapter service you created in step 6a.
If you have more than one alias, modify the signature of the
wm.ln.authentication:login service to have an alias string as input. Based on the value of this string, the service should call the createSession adapter service that is associated with the corresponding connection for the alias provided.
In either case, make sure the login service leaves a session object at the root level of the pipeline.
7. Perform acceptance testing to make sure the integrations, adapter connections, and adapter services are functioning correctly.