Interim Fix Notes for
WebSphere Adapter for Email Version 6.0.2.IF1

 

This document contains the following sections:

COMPLETED CHANGE REQUESTS

UPGRADE INSTRUCTIONS

 

Completed change requests in the Interim Fix

This Interim Fix contains fixes for the change requests listed in the table below.

Note: Some common short forms used in the descriptions are listed below:

Adapter Version

CR Number/APAR Number

CR details

Description of fix done

6.0.2.IF1

86984

IBM WebSphere Adapter for Email 6.0.2 creates archive files invalid filenames in z/OS

Email adapter now creates archive files with valid filenames.

 

 Upgrade instructions

 To upgrade to the Inetrim fix version 6.0.2.IF1, do the following:

  1. Ensure you have followed the "Installation Instructions" section in the download link before proceeding.
  2. If you need to use the Interim fix for EMD (Enterprise Metadata Discovery), delete the connector project in WID (WebSphere Integration Developer), import the new RAR file and apply the EIS specific dependency files. The following steps describe how to do this.

Open the Java build path for the SCA module and remove the Connector project selected on the Projects tab.

Open the dependency editor and remove the connector project.

Delete the connector project from the workspace.

Import the new RAR file, CWYEM_EMail. Add any dependency files from EIS specific APIs as needed.

Open the Java build path for the SCA module and select the Connector project on the Projects tab.

Open the dependency editor and add the connector project if it is not already present. Then select the Deploy with Module check box.

  1. If you need to update deployed applications on WebSphere Process Server, take the follosing steps:

Select Update for the corresponding application on the WebSphere Process Server administrative console.

Select Single Module with a relative path as the name of the RAR file : CWYEM_EMail.rar.

Click Browse on the local file system to select the updated RAR file that has the changes.

Select the default values in the remaining steps and click Finish. This will ensure that existing configurations, for example, MCF (ManagedConnectionFactory), are not changed and JAR files will be merely updated.

  

Last modified: January 3, 2007