Fix Pack Notes for
WebSphere Adapter for Siebel Enterprise Version 6.0.0.1

 

This document contain the following sections:

COMPLETED CHANGE REQUESTS

UPGRADE INSTRUCTIONS

 

Completed Change Requests against the Fix Pack

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

Adapter Version

CR Number/APAR Number

CR details

Description of fix done

6.0.0.1

72360

Siebel 7.8 support

Adapter now supports Siebel v7.8

73430

HCG_BIDI:No BiDisupport for EventMethod property (BO ASI)

EventMethod property has BiDi support now. BiDi format can be added through BiDiContextEventMethod member in BusinessObjectEditor.

73522

HCG_BIDI:Siebel EMD-BiDi support is missing for connection string

BiDi support was added to ConnectionString in EMD GUI. BiDi format can be specified in EMD GUI window.

73670

Sample Siebel server-side event-generation scripts do not work as shipped

Now Object Name and Object key values in the events comply with the inbound sample being shipped with the adapter

73785

In event processing retrieve is happening for Delete verb which should not happen

When the event type is 'Delete' retrieval of the business object will not happen.

73812

HCG_BIDI: Siebel - Add logging functionality

BiDi special methods have now appropriate logging/tracing messages that can appear in log files.

74213

Event status does not update properly during event processing.

Mark the event status properly for different status.

48839

When polling in UNORDERED delivery mode, if an error occurred, events delivered could show up as undelivered in the event table

Events are now cleaned up when delivered in this scenario.

73563

Publishing business objects as byte arrays caused performance problems

Changed the byte array to HexBinary encoding.

72743

Byte arrays for published business objects would show up in the log as one line per byte.

HexBinary encoding helps this a lot. We also recommend running production systems with log level WARNING, so these messages will not appear at all in the log with that level.

73738

Inbound CEI events would not correlate

Fixed this to add correlation information.

73449

BiDi format for connection metadata was not handling an empty string correctly

This has been fixed.

73477

Enhance BiDi log/trace capabilities

Tracing has been added for BiDi diagnostics.

73566 

Business Object BiDi format not working correctly.

This has been fixed.

73143

BiDi properties were not validated in EMD

The BiDi properties are now validated in EMD.

73023

The TurnBiDiOff property in EMD was appearing in a confusing way

This has been fixed. The default is "false" when BiDi in EMD is active.

73295

Contextual LTR or RTL component of BiDi format is not passed from EMD 1st screen to 5th

This has been fixed.

72745

Inconsistent time and date format between log and trace

The trace time format has been updated to match the logs format.

67575

AccessControlException thrown when Java 2 security is turned on in the WPS

Changes have been made to ensure that AccessControlException is not thrown when Java 2 security is turned on.

67845

Default ManagedConnectionFactory credentials do not work properly.

Updated connection code to use credentials specified in the outbound properties when no authentication alias is configured.

 

Upgrade Instructions

To upgrade to the Fix Pack version 6.0.0.1, do the following:

  1. Ensure you have followed the Installation Instructions section in the download link before proceeding further.
  2. If you need to use the Fix Pack for EMD, delete the connector project in the WID, import the new rar and apply the EIS specific dependency files. The following steps describe how to do the same.

v     Open the Java Build Path for the SCA module and remove the Connector project selected on projects tab.

v     Open the dependency editor and remove the connector project.

v     Delete the connector project from workspace.

v     Import the new rar file. Add any dependency files from EIS specific APIs as needed.

v     Open Java build path for the SCA module and select the Connector project selected on projects tab.

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

  1. If you need to update deployed applications on the WPS

v     Select "Update" for the corresponding application on the WPS Admin Console

v     Select "Single Module" with relative path as name of the rar file CWYES_Siebel.rar.

v     Click the Browse button on local file system to select the updated rar file that has the changes.

v     Select the default values in the remaining steps and click Finish. This will ensure that existing configurations e.g. MCF, are not changed and jars will be merely updated.

Last modified: Dec 10, 2005