Metamerge logo
Search

Advanced Search
*
*
*
* HOME DOCUMENTS & RESOURCES DOWNLOADS EARLY TECH ACCESS SUPPORT FAQ KNOWN ISSUES OLD VERSIONS
*
 Up

 

Version 4.6.7

Date: 2002-02-11

This patch is cumulative with the previous ones, you do not need to install any older patches.  After this patch, both Admin Tool and Metamerge Integration Server will have version 4.6.7.

Warnings

  • Some hooks are called slightly differently than they used to.  Refer to the section about Bugs Fixed.
  • Since the behaviour of the LDIF parser has changed a little (see Improvements) it will create an extra line as well as try to Base64 encode data if you have used spaces at the end of Attributes. (This is to protect the space so it does not get lost).

Bugs fixed

  • NT4/ADSI Connector: Connector could clear passwords during update 
  • LDAP Connector with Open LDAP: LDAP Connector's configuration tab returned NullPointerException when getting the contexts of OpenLDAP 
  • File Encryption:  Configuration files were not encrypted correctly
  • File Logging: If log file could not be created, a strange error message could appear 
  • task.getLogFilePath method was broken.  Now returns an absolute path.
  • Hooks, Before Connector Initialised: A scripting error in the before_connector_initialize hook would induce a call to the epilog without passing through the data flow. The epilog would then define its work object as a result of the AL data flow (null in this case)
  • Hooks, Override Add: If the override_add hook was enabled, the addonly_ok hook was incorrectly called after the add operation
  • Hooks, Lookup Mode, very special case.  Description not for the weak hearted: If you had a lookup connector, and did not allow duplicates, and found multiple entries when looking up, and had not enabled the "On Multiple" Hook, and had an "On Error" hook, execution would continue after calling the "On Error" Hook, using the first Entry found, just as if this had been an "On Multiple" Hook. This is a logical error, after calling the "On Error" Hook, the connector should not proceed, except for calling the "After Lookup->On Success" Hook. 

Improvements

  • IBM SecureWay Changelog Connector is added
  • XML Parser: The XML parser would generate CDATA_SECTION_NODEs on output, but it ignored that text type on input, it would only read TEXT_NODEs
  • LDIF Parser: LDIF parser would generate Base64 encoding on output but failed to parse B64 on input.
    When B64 encountered on input the parser now trims the B64 string (this is safe) to remove the initial space that caused MimeUtility to misinterpret the string.
    LDIF parser now creates an extra line with version number (this is to be more compliant with the standard (RFC 2849))
  • Outlook Connector: Changed the quoting mechanism in the lookup function so names containing a single quote (') does not break down the Connector
  • GUI: Escape key now acts as Cancel in the dialogues.
  • Statistics:  The lookup statistic now counts only lookups which succeeded.  It used to count unsuccessful lookups as well.
  • LDAP Connector:  New default value for Authentication is Simple (it was Anonymous).  This could be confusing since Anonymous stilled used user-name and password if these were supplied.
  • Hooks, Default OK: In the default_success Hook (After ...-> On Success), if an error occurred, it  was silently ignored. Now calls default_error when an error occurs, and/or terminates the AssemblyLine
  • Improved Flow Control: 
    In the EventHandler, the system.skipEntry() and system.restartEntry() were not implemented.
    In the Iterator (AssemblyLine), system.restartEntry() was not implemented, and system.ignoreEntry() did the same as system.skipEntry().
    In other connectors of the  AssemblyLine, system.abortAssemblyLine could cause an error Hook to be called.
  • Error Messages:  Slightly improvements of some of the error messages.  

 

Renaming of Connectors

4.6.7 renames certain Connectors to remove confusion.  Old scripts will still work, but new files should use the new term.

  • ADSI renamed to NT4.  You should remove your adsi.jar in the jars/Connector directory in order to stop the old name from showing up.
 

Know, pending issues:

Pending issues for the latest version, is found on the Known Issues Page.  

Bugs fixed earlier, see : 4.6.1, 4.6.2, 4.6.3, 4.6.4, 4.6.5, 4.6.6

 

*
  Metamerge Integrator version 4.6 ©Copyright Metamerge AS 2000-2002 Last edited 2002-06-10 contact us