INSTRUCTIONS FOR APPLYING THE 2.0.0.1 PATCH FOR NT: The 2.0.0.1 patch is delivered with the following files: bin\ConnDesigner.exe lib\CrossWorlds.jar bin\Data\StdConnProps.xml bin\BusObjDesigner.exe bin\CxCommon.dll Caution: Unzipping this patch will OVERWRITE your existing installation's files. CrossWorlds recommends backing up the existing files before applying this patch. To apply the patch, create a %CROSSWORLDS%\patches directory, place the 2.0.0.1_for_NT.zip file into this directory and unzip the file to your %CROSSWORLDS% (c:\crossworlds by default) directory. Copy the following files in the respective directory: in your %CROSSWORLDS%\bin directory: ConnDesigner.exe in your %CROSSWORLDS%\bin\Data directory: StdConnProps.xml in your %CROSSWORLDS%\bin directory: BusObjDesigner.exe in your %CROSSWORLDS%\bin directory: CxCommon.dll in your %CROSSWORLDS%\lib directory: CrossWorlds.jar ----------------------------------------------------------------------------------- CrossWorlds 2.0.0.1 patch for NT contains the following enhancement: CR 14715 (APAR JR17276) - provide 'exactly once' event delivery for connectors (Guaranteed Event Delivery). In this patch, the Guaranteed Event Delivery (GED) is implemented for the JMS event store. To activate this enhancement, users are expected to specify several additional properties using the connector configurator tool. This enhancement will enable the connector infrastructure to manage the JMS event store and guarantees that events are never lost and will never sent twice between the source JMS event store to Destination JMS queue. To activate this enhancement, users are expected to specify several additional properties using the connector configurator tool. Several new configurations properties are required in the local configuration file for connector infrastructure to maintain and read events from the source JMS event store ( Source Queue) and deliver them to destination queue. ContainerManagedEvents = JMS Following standard properties are required, if ContainerManagedEvents property is set to JMS. SourceQueue PollQuantity [DataHandlers] MimeType DHClass DataHandlerConfigMOName Details for those extra propertes are - 1. ContainerManagedEvents = JMS This property has to be set to JMS to turn on the GED feature. Otherwise, connector behaves normally by polling events thru User-agent written part of the code. 2. SourceQueue = SOURCE Queue name This property has to be set. Note: the sourceQueue is on the same MQ manager with other queues. 3. PollQuantity = 1 to 500 PollQuantity is the number of events to be retrieved from the sourcequeue for each poll. 4. PollFrequency = # in mini second This property tells the connector how frequent to retrieve event. 5. MimeType = the DataHander mine type (specified in DataHandlers section) When the MimeType is set, this property alone is used to construct a proper datahandler, i.e. the DHClass property is ignored. NOTE: for the swift datahandler, this property has to be set to swift (in lower case). 6. DHClass = datahandler class location Only when the MimeType is NOT set, DHClass is used to locate the datahandler class. 7. DataHandlerConfigMOName = MO_DataHandler_Default This is a property that has to be set when using with swift datahandler. CR 15345 - add a couple of buttons into the UI to allow the user to be able to select the action for all business objects as either "Overwrite Local" or "Don't Import" (in the case of importing from server, "Don't Import" is replaced by "Overwrite Server") by only one click. This enhancement will significantly save time for the importing process, especially in the Swift project. More details about this enhancement are as follows: Suppose that the user has been importing a number of business object definitions. Then he/she wants to import some .xsd or .txt file (or open a server) that is containing some business object definitions with same names as those imported before. A dialog appears and asks the user to select one of the following actions for these duplicated business objects: Keep Import\RenameLocal Keep Local\Rename Import Overwrite Local Don't Import By default (and for a security reason), all are set as "Keep Import\Rename Local". However, in many cases, the user wants to overwrite or not import the existing business object definitions. Consequently, the user had to select this action one by one for each business object definition. It took much time to finish the process of only setting "overwrite local" for the action column of all these business objects. Adding two buttons "Overwrite Local" and "Don't Import" allow the user to select the action of all the business object as either "Overwrite Local" or "Don't Import" by only one click!