ibolt V3 SP2 Release Notes

Transcription

1 ibolt V3 SP2 Release Notes Welcome to ibolt V3 SP2, which has been designed to deliver an easy-touse, flexible, and cost-effective business integration solution. This document highlights the new and enhanced features that have been added to ibolt V3 SP2. For information about previous ibolt versions, see the PastReleaseNotes.pdf file provided with this installation. General Information Installing ibolt You can find information about installing ibolt in the ibolt Installation Guide.pdf. The guide also contains information about the prerequisites for using ibolt flow components. ibolt Technical Notes Magic s International Technical Support produces ibolt Technical Notes on a range of useful topics. You can find the Technical Notes in the ibolt Help and on Magic Software Enterprises Website. ibolt V3 SP2 Certification For information about the various platforms on which ibolt V3 SP2 has been certified for operation by Magic Software Enterprises, refer to the ibolt V3 Certification document. Migrating from ibolt V2.5 to ibolt V3 SP2 ibolt provides a wizard to easily migrate your project from ibolt V2.5 to ibolt V3 SP2. This wizard is available through a shortcut in the ibolt installation s Start menu. Note: We recommend reading the Migration chapter in the ibolt V3 SP2 Help before migrating your ibolt V2.5 projects. Make sure to perform the following actions after the Migration process: 1. Open and review all Data Mapper steps in the mapping screen by clicking the Map button. Verify that all connections and expressions are still valid and click OK to save changes. 2. Open and review all steps where an XML interface was used to verify that all connections and expressions are still valid. Click OK to save changes. March

2 3. Due to changes in schema locations, the following components require reconfiguration (click the Configuration button): SAP Business One, SAP R/3, Salesforce, JD Edwards, Notes DB. Click OK to save changes. Upgrading from ibolt V3 SP1 to ibolt V3 SP2 ibolt will automatically upgrade a project developed in ibolt V3 SP1 to ibolt V3 SP2. Make sure to manually copy your project directory to the new installation s Projects directory. Supported Internal Databases ibolt V3 supports the following internal databases: Oracle 9i (OCI 32-bit only) Oracle 10g (OCI 32-bit only) Microsoft SQL Server 2000 Microsoft SQL Server 2005 ODBC 3 and above MySQL 5.x DB2 UDB 8 DB2/400 V4.4 and above New Features HL7 Converter ibolt V3 SP2 includes the HL7 converter, which allows you to convert HL7 2.x messages to XML and vice versa. Sample Projects This release includes a set of sample projects that demonstrate ibolt features. You can install these projects as part of the ibolt installation process. Migration Enhancements Changes were made in the Migration utility to lower to a minimum the amount of connections that require remapping. The migration process now: o o Handles SQL statements with case differences between the statement in ibolt and the names of the database fields. Adds an execution condition to all Data Mapper mapped destinations to avoid the creation of empty elements if the source element is missing. ibolt V3 SP2 Release Notes March

3 o Adds a condition (identical to the compound condition) to the update expression condition in the Data Mapper. IFS Services in unipaas Service IFS Services are now supported in a unipaas service (see the Change of Behavior section below for additional details). Mapper Enhancements The Connect all option is now available for a single occurrence compound. Deleting a compound connection does not automatically delete all child connections, but gives you the option to map an alternative parent compound. Change of Behavior The following services were removed from the ifs_services of ibolt V3 (these refer to services that appear when the Load Server Services check box is selected in ibolt s unipaas Configuration dialog box): AbortFlow StoreSavePointData RetrieveSavePointData In addition, the following changes were made to the unipaas component s services: InvokeFlow Added new parameter: pi. BP ID (1 first parameter) Removed parameters: pio. User String (6), pio. User Blob (7), pio. User Status Code (8) Use SetParam with the required variable name (C.UserString, for example) before calling the InvokeFlow. InvokeFlowDelay Added new parameters: pi. BP ID (1), pi. Seconds (6) ScheduleFlow Added new parameter: pi. BP ID (1) BAM_Service Size changed: pi. user string (from 260 to 1000) PSSSubscribe Added new parameter: pi. BP ID (3) Renamed parameter: pi. Flow ID (from: pi. Flow) PSSRemove Added new parameter: pi. BP ID (2) PSSSubRemove Added new parameter: pi. BP ID (2) ODSSave Changed parameters: po. User Data BLOB (from Binary to ANSI) po. User Data String (from A32000 to U1000) po. User Data Logical (from numeric 1 to logical) ibolt V3 SP2 Release Notes March

4 ODSSaveStr ODSSaveNum ODSSaveLog ODSSaveBLB ODSGet ODSGetStr ODSGetLog Changed: pi. User Data String (from A32000 to U1000) Changed: pi. User Data Number (from 11.4 to 12.4) Changed: pi. User Data Logical (from numeric 1 to logical) Changed: pi. User Data Blob (from binary to ANSI) Changed parameters: po. User Data Logical (from numeric 1 to logical) po. User Data String (from A32000 to U1000) Changed: po. User Data String (from A32000 to U1000) Changed: po. User Data Logical (from numeric 1 to logical) Known Issues The Upgrade option of the Installation utility is currently not operational. You need to install ibolt V3 SP2 as a separate installation. When upgrading from ibolt V3 to ibolt V3 SP2, you need to redefine the Password fields in your resources. The Scheduler and the Flow Enablement section are not imported in the current build. The MaxNumberofThreads property in the Server settings is not saved correctly. You should set it manually by adding [MAGIC_ENV]MaxConcurrentRequests = <the Max number of threads> to the Ifs.ini file. The reserved thread to stop the Server is not always available. When starting the Debugger from the Flow context menu (debugging one flow), the flow will be executed immediately (AutoStart behavior). When the flow execution is completed once, any triggers that are defined will wait for external events. The Debugger hangs when you execute Step or Continue on a breakpoint defined in an Error flow. In the Salesforce connector, when using multiple operations of Add/Update/Delete/Upsert, the operation is limited to 200 records in one chunk. If the source data contains more than 200 records, the data has to be split into chunks of 200 records. Unicode data cannot be mapped to XML nodes encoded as base64. If you run a project with.net framework support, and you receive the Error in.net invocation:ifc1.ifc1 Code: Set Property: iboltframework.dll location error, you should unregister and then re-register the Iboltinvoker.dll file by using this command: RegAsm iboltinvoker.dll /tlb:iboltinvoker.tlb ibolt V3 SP2 Release Notes March

5 ibolt V3 SP2 Fixed Problems After migrating and then clicking on the Mapper, the connections to DateTime fields were lost and the following error was displayed: "path not exist/attribute was changed" When migrating from ibolt 2.5 SP10 to ibolt V3, spaces were added to the element name from the Data Mapper source There were problems importing a flow when the flow name was in Hebrew When migrating a Salesforce component to ibolt V3 SP1, an object could not be selected, unless a new resource was created. Magic Software Enterprises Ltd provides the information in this document as is and without any warranties, including merchantability and fitness for a particular purpose. In no event will Magic Software Enterprises Ltd be liable for any loss of profit, business, use, or data or for indirect, special, incidental or consequential damages of any kind whether based in contract, negligence, or other tort. Magic Software Enterprises Ltd may make changes to this document and the product information at any time without notice and without obligation to update the materials contained in this document. Magic is a trademark of Magic Software Enterprises Ltd. Copyright Magic Software Enterprises, March 2009 ibolt V3 SP2 Release Notes March