Past Release Notes - Systems Integration Platform ...ftp.magicsoftware.com/.../Windows/PastReleaseNotes.pdf · Salesforce Connector iBOLT V3 SP1 includes the Salesforce connector,

iBOLT Past Release Notes

T his document includes the release notes of all the iBOLT versions and service packs that precede the current iBOLT release. For information about the current iBOLT release, see the ReleaseNotes.pdf file provided with the iBOLT installation.

iBOLT Version 3 Release Notes Welcome to iBOLT Version 3, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.

This document highlights the new and enhanced features that have been added to iBOLT Version 3.

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 Version 3 Certification For information about the various platforms on which iBOLT Version 3 has been certified for operation by Magic Software Enterprises, refer to the iBOLT V3 Certification document.

Resource Repository The Resource Repository lets you define the external systems that iBOLT needs to access when executing a project. The Resource Repository provides:

• A single location to manage project resources.

• The ability to manage and configure resources without changing the project code.

• The capability to share and reuse resources among several projects.

Service Repository The iBOLT Service Repository lets you define how flows are invoked from an external system. These services are used when you add triggers to a flow. The Service Repository provides:

• A single location for defining and managing project services, outside of the project.

• Simplification of the project's deployment phase.

iBOLT Version 3 Release Notes July 2008 1

ftp://ftp.magicsoftware.com/iboltproduct/Documents/

Version Control You can use iBOLT Version 3 with the Microsoft Visual SourceSafe (VSS) product, allowing you to save, track, and access different versions of your project files. The Version Control feature lets you work in a multi-developer environment.

Component SDK iBOLT Version 3's Component SDK makes it easy for you to develop your own components, based on uniPaaS or Java, for use in the iBOLT Suite. You can quickly generate the new component's initial code, define its methods, or wrap existing Java classes. You can also create new resource types to support your new component.

Data Mapper The Data Mapper enables you to create an association between Sources and Destinations, in different formats. The Data Mapper automatically connects nodes, creating a comprehensive visual association, making it easy to understand and anticipate the results of your mapping. iBOLT Version 3's Data Mapper provides:

• Enhanced execution of database transactions.

• Conditional mapping.

• Offline editing of the Data Mapper, without a live connection to a database.

• XML context forwarding.

• Source node filters that allow you to limit the quantity of information that is processed, thereby delivering excellent mapping performance.

• The ability to update multiple variables during a single iteration of the Data Mapper execution.

• Greatly enhanced error handling capabilities.

• The ability to handle large schemas.


Web Services iBOLT Version 3's Web services are based on Systinet™. This provides a platform-independent, high performance runtime environment for the creation and deployment of Web services. iBOLT's Web services support:

• SOAP 1.1 and 1.2

• WSDL 1.1, SOAP with attachments (DIME and MIME)

• WS-I basic profile

• WS-I attachments profile

In addition, iBOLT's Web services support the latest security standards, including:

• Transport authentication (Basic/Digest)

• SSL

• Kerberos™

• Authentication, encryption, and digital signing of SOAP messages

Floating License Support The floating license mechanism shares licenses between Servers. When a particular project is idle, other projects can utilize its licenses. This enables you to make optimum use of your iBOLT licenses in a multi-project environment.

Environment Variables Environment variables have replaced iBOLT Version 2.5's logical names functionality. Resource and service definitions can use environment variables for additional flexibility.

User Defined Storage (UDS) iBOLT Version 3's User Defined Storage (UDS) feature enables the definition of multi-dimensional storage tables (arrays). These definitions can then be used in your integration flows to store and retrieve multi-instance data types. After defining the UDS models in the dedicated UDS repository, you can define variables based on these models and use them in the Data Mapper and in flows.

Debugger The Debugger lets you test your integration project during development. It runs your project, or attaches to a running project, and enables you to control the way the project is executed. You can control and view execution sequences, flow variables, iBOLT services, and breakpoints. You can debug parallel flows, and you can debug a remote Server that is running on another machine.


Expression Editor iBOLT Version 3's enhanced Expression Editor lets you create expressions with a plain language editor interface. It includes an auto-complete facility and color presentation, for functions and variables, as well as an intuitive toolbar for ease of use.

The following functions have been added to iBOLT Version 3:

Function Description

TranslateNR Translates all environment variables in a string, including nested environment variables, to their actual values.

XMLStr Converts valid XML data into an Alpha string.

XMLVal Converts a string into a valid XML string.

UDSClear Gets the UDS variable name and clears its data.

UDSDeleteRecord Gets the UDS variable name, the index field name, the index field value, and the UDS model as parameters.

UDSGet Gets the UDS variable name and the UDS model name as parameters, and returns a BLOB containing the UDS table data.

UDSGetField Gets the UDS variable name, the index field name, the index field value, the field name, and the UDS model as parameters.

UDSSet Sets the UDS data using the BLOB and the operation.

UDSUpdateField Gets the UDS variable name, the field name, the field data, the index field name, the index field value, and the UDS model as parameters.


Usability Enhancements iBOLT Version 3 contains many features that are designed to enhance usability and to help you to get the most from the iBOLT Suite. These features include:

• Automatic logging information in flow components.

• A unified variables repository.

• An enhanced Scheduler service.

• Improved error management in steps and triggers.

• Unified component interfaces (method and XML).

• Expanding and collapsing branches in the Flow Editor.

• Resizable screens.

Removed Components The following components have been removed from iBOLT Version 3:

• Call COM • FedEx • iBOLT Portal

• Java

• SAPB1 6.5

• SMS • UPS

These components will be converted to work through the NOP service when you migrate iBOLT Version 2.5 projects to iBOLT Version 3. You should convert eDeveloper-based user-defined components individually, and add them to your iBOLT Version 3 project.

Non-Supported Components in iBOLT Version 3

The following components are not supported in iBOLT Version 3:

• SAP R/3 • Salesforce

The iBOLT Version 2.5 eDeveloper trigger is not supported in this version. In iBOLT Version 3, you can define a uniPaaS trigger with the Component SDK, using the existing code.

Removed/Changed Services The Logical Names service has been removed from iBOLT Version 3. You should use the Flow Data service instead.


Migrating from iBOLT Version 2.5 to iBOLT Version 3

Migrating an iBOLT Version 2.5 project to iBOLT Version 3 is fast and easy.

iBOLT provides a wizard to easily migrate your application.

We recommend reading the Migration chapter in the iBOLT V3 Help before migrating your iBOLT Version 2.5 projects.

Additional Changes iBOLT Version 3 contains the following additional changes:

• The Logical data type was changed to Boolean.

• The FTP methods have been removed from the File Management component.

• The LAN to FTP and FTP to FTP methods have been removed from the Directory Scanner component.

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


• ODBC 3 and above

• MySQL 5.x

Known Issues After migrating a project from iBOLT 2.5 to iBOLT V3, if you want to rename your project, you must save the project using the original project name before renaming.

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 and Magic eDeveloper are trademarks of Magic Software Enterprises Ltd.

Copyright © Magic Software Enterprises, July 2008


iBOLT V3 SP1 Release Notes Welcome to iBOLT V3 SP1, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.

This document highlights the new and enhanced features that have been added to iBOLT V3 SP1. For information about previous iBOLT versions, see the PastReleaseNotes.pdf file provided with this installation.

General Information



iBOLT V3 SP1 Certification For information about the various platforms on which iBOLT V3 SP1 has been certified for operation by Magic Software Enterprises, refer to the iBOLT V3 Certification document.

Migrating from iBOLT V2.5 to iBOLT V3 SP1 iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3 SP1. 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 SP1 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.

December 2008 1

ftp://ftp.magicsoftware.com/iboltproduct/Documents/

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 to iBOLT V3 SP1 iBOLT will automatically upgrade a project developed in iBOLT V3 to iBOLT V3 SP1. Make sure to manually copy your project directory to the new installation’s Projects directory.







• MySQL 5.x

• DB2 UDB 8

• DB2/400 V4.4 and above

New Features

Salesforce Connector iBOLT V3 SP1 includes the Salesforce connector, which allows you to integrate the Salesforce.com® CRM solution into your existing business applications.

JD Edwards Connector The JD Edwards connector is designed to provide connectivity to the J. D. Edwards ERP System.

Notes DB Connector The new Notes DB connector is designed to provide access to IBM Lotus Notes databases.

SAP R/3 Connector The SAP R/3 connector is designed to provide access to the SAP R/3 system.

iBOLT V3 SP1 Release Notes December 2008 2

.NET Service The .NET Service is designed to allow execution of code developed in the .NET framework. This iBOLT Service provides backward compatibility to the iBOLT V2.5 .NET component.

Import and Export Functionality The Import and Export functionality provides the ability to easily save and load project objects such as steps, flows or a full business process from one project to another.

Web Services Enhancements Locating and publishing Web Services are provided using the UDDI Server Resource.

Monitor Enhancements The following changes were added to the Monitor:

• Ability to switch Activity Logging on and off during runtime.

• Controlling the Activity Log table size by automatically clearing old records.

• Monitor performance was improved.

Unicode Support Starting with iBOLT V3 SP1, the iBOLT Data Mapper supports Unicode data in the following areas:

• Querying and updating database Unicode columns.

• Reading and writing UTF-8 and UTF-16 XML data.

• Reading and writing Unicode flat files.

Please note the following about this version’s Unicode support:

• The SAP R/3 and SAP Business One components fully support Unicode. All other components support only ANSI in Step mode. If you process Unicode data for these components, the outcome is undetermined.

• The Directory Scanner, HTTP, and Web Services components support Unicode in Trigger mode only.

• iBOLT treats all data saved in BLOBs as binary data. Therefore, in order to view Unicode data, use an application that supports Unicode, such as Notepad.

Changes to Web Services, EJB and COM Services The Service definition of Web Services, EJB and COM require hard-coded property values and will not support environment variables.

Debugger Enhancements The Debugger Context View provides information about UDS variables and allows changing UDS values during Debug sessions.


Enhancements to Resources A Validate button was added to the following Resource types: Domino, FTP, Email and System i. The Validate operation checks connectivity to the defined Resource.

Enhancements to Microsoft Word and Microsoft Excel Components The password fields in the Method interface are encoded.

Mapper Enhancements • iBOLT V3 SP1’s Data Mapper can handle cases where the data includes

the field delimiter character.

• The Boolean data format mapping was changed from Numeric to Logical for Boolean nodes in the XML Source and Destination. This change is applicable for new projects only.

• UDS flow variables can be accessed in the Call Flow operation.

Components XML Interface Changes The ResourceName node was removed from the components’ XSD. The components use the Resource defined in the Step properties.

EJB and JCC Changes The wizard interface of these components was changed to a standard method interface.

Note: For more information about the above changes, see the relevant sections in the iBOLT Help.

Installation Changes Server and Monitor installations were optimized to install only required files and update entries in the Magic.ini file.

License Changes The iBOLT V3 license was changed to include separate FEATURE sections. Components and certain options are available in separate features of the license file, and not as embedded tokens. This change is only applicable to production licenses and is not enforced in Debug session or when a non-production license is used.

For more information see the License section of the iBOLT Help or the iBOLT Installation Guide.


Behavior Changes • In order to execute a project in the Server after running it in Debug

mode, you will need to rebuild the project.

• Error Behavior change: When the Server calls an Error flow or Exception flow, error details will not be saved in the C.UserCode, C.UserString and C.UserBlob variables. These details will be available in the standard error variables: C.sys.LastErrorCode, C.sys.LastErrorDescription and C.sys.LastErrorInfo.

• Component metadata files (XSD files and other project related files generated by SAP Business One, SAP R/3, JDE and Notes DB components) are saved under the project directory and not under the installation's ifclib directory.

• The iBOLT V2.5 Salesforce component retrieved the Objects list directly from Salesforce. In iBOLT V3, the Objects list is saved in the resource file. Therefore, it is only possible to build the list from the resource interface and not from the step itself.

• The Salesforce component’s Operation Success property was changed from Numeric in iBOLT V2.5 to Logical in iBOLT V3. Users must select a Logical variable type after migration.

• The Max instances property’s behavior has changed. In previous releases this property was applied to the main flow and all parallel flows called by it. Starting with iBOLT V3 SP1, the Max instances property is only applied to the main flow and linear flows called by it (flows in the same thread).

Known Issues • 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.

• The Upgrade option of the Installation utility is currently not operational. You will need to install iBOLT V3 SP1 as a separate installation.

• When upgrading from iBOLT V3 to iBOLT V3 SP1, you need to redefine the Password fields in your resources.

• 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.

• The Scheduler and the Flow Enablement section are not imported in the current build.

• If you run a project with .NET framework support, and you receive the Error in .NET invocation:IFC1.IFC1 Code:2140930047 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 SP1 Fixed Problems 522596 – The migration process created a wrong project file extension.

720427 – An SBO project did not execute under an iBOLT V3 Server only installation.

757942 – The Checker always displayed an Error label in the Additional Information pane.

924603 – There was a problem zooming into an entry in the BAM Messages View.

930685 – The Data Mapper did not retain connections.

934117 – SAP B1 stored procedures caused an error.

935736 – The User and Password fields in an Email component were not migrated correctly in projects developed in iBOLT V2.5

965090 – The "Using iBOLT as a Web Services Consumer – Implementation Stages" Help topic contained incorrect information.

918042 – Insert operation failed when "DBTransactionLevel = Record" in DB2/400 Database

727688 – Web Service Resource definition problem in WSDL property.

773459 – SAPB1 connection problem at run time when using Environment Variables in Resource.

759696 – Domino Read Mail method did not work if mail form was defined as 'Bookmark'.


Magic is a trademark of Magic Software Enterprises Ltd.

Copyright © Magic Software Enterprises, December 2008


March 2009 1

iBOLT V3 SP2 Release Notes Welcome to iBOLT V3 SP2, which has been designed to deliver an easy-to-use, 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



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:



ftp://ftp.magicsoftware.com/iboltproduct/Documents/�

iBOLT V3 SP2 Release Notes March 2009 2


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.







• MySQL 5.x

• DB2 UDB 8


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 Handles SQL statements with case differences between the statement in iBOLT and the names of the database fields.

o Adds an execution condition to all Data Mapper mapped destinations to avoid the creation of empty elements if the source element is missing.


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)


ODSSaveStr Changed: pi. User Data – String (from A32000 to U1000)

ODSSaveNum Changed: pi. User Data – Number (from 11.4 to 12.4)

ODSSaveLog Changed: pi. User Data – Logical (from numeric 1 to logical)

ODSSaveBLB Changed: pi. User Data – Blob (from binary to ANSI)

ODSGet Changed parameters: po. User Data – Logical (from numeric 1 to logical) po. User Data – String (from A32000 to U1000)

ODSGetStr Changed: po. User Data – String (from A32000 to U1000)

ODSGetLog 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.


• If you run a project with .NET framework support, and you receive the Error in .NET invocation:IFC1.IFC1 Code:2140930047 Set Property: iBOLTFramework.dll location error, you should unregister and then re-register the Iboltinvoker.dll file by using this command:



iBOLT V3 SP2 Fixed Problems 918279 – 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".

785111 – When migrating from iBOLT 2.5 SP10 to iBOLT V3, spaces were added to the element name from the Data Mapper source.

730995 – There were problems importing a flow when the flow name was in Hebrew.

780440 – When migrating a Salesforce component to iBOLT V3 SP1, an object could not be selected, unless a new resource was created.



Copyright © Magic Software Enterprises, March 2009

May 2009 1

iBOLT V3.1 Release Notes Welcome to iBOLT V3.1, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.

This document highlights the new and enhanced features that have been added to iBOLT V3.1. For information about previous iBOLT versions, see the Past Release Notes.pdf file provided with this installation.

General Information



iBOLT V3.1 Certification For information about the various platforms on which iBOLT V3.1 has been certified for operation by Magic Software Enterprises, refer to the iBOLT V3 Certification document.

Migrating from iBOLT V2.5 to iBOLT V3.1 iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.1. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.

Note: We recommend reading the Migration chapter in the iBOLT Help before migrating your iBOLT V2.5 projects.

Make sure to perform the following actions after the migration process:




iBOLT V3.1 Release Notes May 2009 2



Upgrading from iBOLT V3 SP2 to iBOLT V3.1

iBOLT will automatically upgrade a project developed in iBOLT V3 SP2 to iBOLT V3.1. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.

Supported Internal Databases iBOLT V3.1 supports the following internal databases:





• MySQL 5.x

• DB2 UDB 8


New Features

Project Packager The new iBOLT Project Packager lets you conveniently and easily bundle all relevant iBOLT project files and additional files used by the project in a .zip compressed file for subsequent extraction to a deployment environment.

LDAP Component The new iBOLT LDAP (Lightweight Directory Access Protocol) connector lets you connect to an LDAP server to store and access attribute-based data in a hierarchical data structure.

Google Calendar Component The Google® Calendar component provides connectivity (using the Method interface) between iBOLT and Google Calendar.


Dynamic Logging for Components Control of the Logging option can now be performed dynamically using an environment variable or expression and also remotely from the iBOLT Monitor.

Resource/Service Repository Enhancements • All mandatory properties are now displayed in bold type.

• A Resource button is now available in the Service Repository. Clicking this button brings you directly to the Resource Repository.

File Management Component Enhancements A new method to create and manipulate folders in the LAN has been added.

Directory Scanner Component Enhancements • The mask field has been expanded to 260 characters.

• Folder selection now supports expressions.

• The Return Filename To parameter was added to several methods.

FTP Component Enhancements • FTP over SSL (FTPS) is now supported.

Salesforce Component Enhancements • Attachments are now supported in replication methods.

• Object fields can now be set with Null values.

Email Component Enhancements • SSL is now supported, enhancing the security of Gmail and similar

POP3/SMTP services.

• Sending HTML MIME type email is now supported.

• Expressions in trigger filters are now supported.

SAPB1 Component • User Defined Tables (UDT) can now be added and updated.

• The SAPB1 trigger table status can now be updated.

SAP A1 Component The new SAP A1 connector supports the SAP All-in-One partner solution with the same interface as the existing SAP R/3 connector.

Notes DB Component Enhancements The Notes DB component now supports the following:

• Attachments


• Querying and updating arrays of Alpha values

• Server APIs

Domino Component Enhancements Server APIs are now supported.

Checker and Mapper Code Generation Optimization The Checker and generate processes have been improved.

Data Mapper Enhancements Null content in XML is now supported.

Model XML Validation The ability to validate against an XML Mapper-built schema when an IFC Model is in the destination is now supported.

iBOLT Internal Database – Stronger Password iBOLT is now installed with a stronger password for the user of its internal database.

File Splitter Component Enhancement The component can now provide a comma-delimited list of the split files.

Change of Behavior

Next Step Evaluation Order Next Step evaluation was changed from Step ID to left-to-right sibling visual order.

Flow Completion Behavior An iBOLT flow now completes only after all parallel branches are finished.

Salesforce Error Handling The iBOLT Salesforce component returns the errors in the Return section of the result XML and not as an iBOLT error, correcting previously inconsistent behavior.

SDK: uniPaaS Component In order to regenerate the uniPaaS component, the user must now explicitly click the Generate button. Clicking the OK button only saves the new definitions in the iBOLT metadata.

Known Issues • When upgrading directly from iBOLT V3.0 to iBOLT V3.1, you need to

redefine the password fields in your resources.


• The MaxNumberofThreads property in the Server settings is not saved correctly. You should set it manually by adding to the ifs.ini file: [MAGIC_ENV] MaxConcurrentRequests = <the Max number of threads>

• 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 defined triggers will wait for external events.


• If you run a project with .NET framework support, and you receive the Error in .NET invocation:IFC1.IFC1 Code:2140930047 Set Property: iBOLTFramework.dll location error, you should unregister and then re-register the Iboltinvoker.dll file by using the following command:


• When the checker finds an error in the GoTo condition, the MoveTo operation will jump to the GoTo destination step condition instead of the GoTo condition.

iBOLT V3.1 Fixed Problems 928811 – Update of Data Mapper XML elements with negative numeric values was not possible (they were changed to positive values).

722750 – Using the File2BLB function to read a file to a BLOB worked, but when using the File Management component, the file did not load.

752754 – The installation included an erroneous requester version in the Magic.ini file.

776196 – When using the Data Mapper with a database destination, sending table names in upper case was problematic if the database was case sensitive.

778476 – The iBOLT Monitor kept opening connections to the database and did not close them.

782925 –Defined Compound Level Computations in the Data Mapper service were deleted while creating and deleting a new destination in the Source Destination Management dialog box.

783531 – There was an incorrect XSD for SAP R/3 when trying to work with the ARTMAS05 IDOC.

799487 – The FTP component could not put files in a virtual folder in IIS FTP when the FTP Server (under IIS) had a virtual folder set.

800164 – iBOLT did not set the code page dynamically for sent WebSphere MQ messages.

909177 – Using the IFC Model Destination Append check box in the Data Mapper service resulted in a corrupted XML. When appending data to an existing XML, the new part was created but all the original XML was corrupted.


910388 – During installation, database logical names were not created when selecting to install the database later.

911608 – For the System i Connector, calling the MAGIC400/ADDMULDEC program returned the error Error 713: CPF0006 Errors occurred in command.

911971 – When migrating, the mapping condition was not copied to the update expression in the Compound Level Computation section.

917175 –When an eDeveloper component having an ifs_services Invoke Flow program was migrated, variables such as UserString, UserBlob and UserCode were lost, resulting in the component's logical failure.

918064 – Incorrect error flow behavior occurred when a multi-add operation in SBO generated an error.

919183 – When the connection to the network was lost, the Server / Studio was disconnected from the broker.

919595 – Data mapping of Unicode data from a database source to a flat file destination did not work.

934271 – The Data Mapper wizard failed to add single quotes around flow variables of Alpha type that were used in WHERE clauses.

939979 – While creating a new Version Control project in iBOLT, the following erroneous message was displayed: Project already exists on the server. Try different project name., even though the project did not exist on the server.

941112 – iBOLT used the default numeric 12.4 picture format when mapping, requiring a manual change of the picture setting for each column.

959192 – When trying to create a directory with a Japanese name (Double byte) the customer got question marks for the named directory.

964517 –The List to XML and XML execute methods in the Microsoft Word component did not work.

983502 – In data mapping, the Single Instance filter always returned the first item.

984979 – When the child node had the same name as the parent node, it was not visible on the Mapper screen.

986899 – Select SQL statements having a WHERE clause with more than two AND operators failed to open the Mapper screen.

991371 – The UDSGetField function did not work in the Invoke Flow service.

995331 – When creating an Update on ProductTree, if no data was entered in the TreeCode node of the QueryParam, an error code was generated, but SAP B1 removed all lines from the document except the first.

997173 –The Data Mapper destination template crashed and failed to create the proper result file.

997201 – The Salesforce trigger was not able to retrieve records if multiple records had to be retrieved. The Salesforce trigger generated the error: EXCEEDED_ID_LIMIT: retrieve id limit reached.




Copyright © Magic Software Enterprises, May 2009

June 2009 1

iBOLT V3.1a Release Notes Welcome to iBOLT V3.1a, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.

This document highlights the new and enhanced features that have been added to iBOLT V3.1a. For information about previous iBOLT versions, see the Past Release Notes.pdf file provided with this installation.

General Information



iBOLT V3.1a Certification For information about the various platforms on which iBOLT V3.1 has been certified for operation by Magic Software Enterprises, refer to the iBOLT V3 Certification document.

Migrating from iBOLT V2.5 to iBOLT V3.1a iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.1a. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.






iBOLT V3.1a Release Notes June 2009 2



Upgrading from iBOLT V3.1 to iBOLT V3.1a iBOLT will automatically upgrade a project developed in iBOLT V3.1 to iBOLT V3.1a. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.

Supported Internal Databases iBOLT V3.1a supports the following internal databases:





• MySQL 5.x

• DB2 UDB 8


Known Issues • In iBOLT V3, the length of a variable name is 30 characters. However,

since iBOLT adds a prefix to each variable name, such as F_ , C_ or G_, the maximum size of a variable is 28 characters.

• In the migration process from V2.5 to V3, iBOLT trims the length of the project variables to 28 and reports it in the log.

• When upgrading directly from iBOLT V3.0 to iBOLT V3.1a, you need to redefine the password fields in your resources.





• If you run a project with .NET framework support, and you receive the Error in .NET invocation:IFC1.IFC1 Code:2140930047 Set

iBOLT V3.1a Release Notes June 2009 3

Property: iBOLTFramework.dll location error, you should unregister and then re-register the Iboltinvoker.dll file by using the following command:


• When the Checker finds an error in the GoTo condition, the MoveTo operation will jump to the GoTo destination step condition instead of the GoTo condition.

iBOLT V3.1a Fixed Problems 977943 – An UPDATE query with a WHERE clause having a numeric type of flow variable, gave a runtime error and failed to update the table records. The Monitor log showed the "Incorrect syntax near '12.4'" error.

934946 – When an expression to an unmapped node was cleared, it failed to generate the executable file.

714692 – When a project was upgraded to iBOLT V3.1, the "Duplicate index, data source: MConversionConnections" error was given.

973110 – For SAP B1 triggers, if the polling interval was less than 1 minute at runtime, the "SAPB1 Trigger error: 1006 Internal error - No Polling Interval Is Defined" error was given.

989092 – Connection to the Notes server failed when the Domino and Notes DB components were used in the same project to connect to a common server.



Copyright © Magic Software Enterprises, June 2009

August 2009 1

iBOLT V3.1b Release Notes Welcome to iBOLT V3.1b, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.

This document highlights the new and enhanced features that have been added to iBOLT V3.1b. For information about previous iBOLT versions, see the Past Release Notes.pdf file provided with this installation.

General Information



iBOLT V3.1b Certification For information about the various platforms on which iBOLT V3.1 has been certified for operation by Magic Software Enterprises, refer to the iBOLT V3 Certification document.

Migrating from iBOLT V2.5 to iBOLT V3.1b iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.1b. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.






iBOLT V3.1b Release Notes August 2009 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, and Notes DB. Click OK to save changes.

Upgrading from iBOLT V3.1a to iBOLT V3.1b

iBOLT will automatically upgrade a project developed in iBOLT V3.1a to iBOLT V3.1b. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.

Supported Internal Databases iBOLT V3.1b supports the following internal databases:





• MySQL 5.x

• DB2 UDB 8


New Features and Changes

.NET Service enhancements • The .NET Service has a new option to run the Configuration method

of the .NET class.

• It is now possible to define custom error codes for the .NET Service in the iBOLT Errors repository. These error codes can be set in the .NET class and handled in iBOLT.

• .NET SDK components from iBOLT V2.5 will be automatically migrated to a .NET Service.

• The .NET Service can run and configure existing iBOLT .NET code. For more information, see the iBOLT Help.

Salesforce enhancements The QueryAll operation was added to the Operations list. This new operation also returns the deleted objects in the query result.


HL7 License The HL7 feature is only available with a special license.

Known Issues • Working with the SAP Business One component together with the

Domino component on a local server, may cause problems. It is recommended to work on a network to avoid these problems.

• In iBOLT V3, the length of a variable name is 30 characters. However, since iBOLT adds a prefix to each variable name, such as F., C. or G., the maximum size of a variable is 28 characters.

• When upgrading directly from iBOLT V3.1a to iBOLT V3.1b, you need to redefine the password fields in your resources.

• The MaxNumberofThreads property in the Server settings is not saved correctly. You should set it manually by adding the following to the ifs.ini file: [MAGIC_ENV] MaxConcurrentRequests = <the Max number of threads>






• When the Checker finds an error in the GoTo condition, the MoveTo operation will jump to the GoTo destination step condition instead of the GoTo condition.


iBOLT V3.1b Fixed Problems 978068 – There was an incorrect result when using multiple repeat sections in the Data Mapper template destination.

929075 – The iBOLT Data Mapper wizard did not recognize the Sybase database when connecting with ODBC.

762977 – The SAPB1 2007 component was unable to work with MSSQL 2008.



Copyright © Magic Software Enterprises, August 2009

September 2009 1

iBOLT V3.1 SP1 Release Notes

Welcome to iBOLT V3.1 SP1, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.

This document highlights the new and enhanced features that have been added to iBOLT V3.1 SP1. For information about previous iBOLT versions, see the Past Release Notes.pdf file provided with this installation.

General Information



iBOLT V3.1 SP1 Compatibility For information about the various platforms with which iBOLT V3.1 SP1 is compatible, refer to the iBOLT V3 Compatibility Guide.

This document replaces the previous version’s Certification document.

Migrating from iBOLT V2.5 to iBOLT V3.1 SP1

iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.1 SP1. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.



iBOLT V3.1 SP1 Release Notes September 2009 2





Upgrading from iBOLT V3.1b to iBOLT V3.1 SP1

iBOLT will automatically upgrade a project developed in iBOLT V3.1b to iBOLT V3.1 SP1. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.

In V3 SP1, the System i, COM, Java Class, EJB, JMS, W4 and SAP components appeared in the Lite Version, even though they were not supported. Beginning with iBOLT V3.1, these components were no longer displayed. In iBOLT V3.1 SP1, if you upgrade a Lite Version project that contains one of these components, the components will be replaced with an NOP service.

Supported Internal Databases iBOLT V3.1 SP1 supports the following internal databases:



• Oracle 11 (OCI 32-bit only)



• MySQL 5.x

• DB2 UDB 8



since iBOLT adds a prefix to each variable name, such as F., C. or G., the maximum size of a variable is 28 characters.



• When upgrading directly from iBOLT V3.1b to iBOLT V3.1 SP1, you need to redefine the password fields in your resources.







New Features

Google Docs Component iBOLT V3.1 SP1 includes the Google Docs™ component, which provides connectivity between iBOLT and Google Docs.

XML Handling Component iBOLT V3.1 SP1 includes the XML Handling component, which allows you to work with either an XML file or the XML data that is contained within a Blob variable, and to apply different XML functions to these files or data.

Debugger Enhancements The Debugger interface was redesigned. Contexts are now represented in a hierarchal structure and there is a visual indication of the context currently in Debug mode. Icons were added to indicate the invocation reason and to distinguish between parallel and linear contexts.

Mapper: Create Empty Nodes The XML and IFC Model destination now have a new check box named Always Create Nodes. Until now, the behavior was to always create the Destination node unless the node condition evaluated to False. In iBOLT V3.1 SP1, you can decide not to create a destination node if the Alpha expression is evaluated to an empty string or Null.

SDK: Trigger Component iBOLT now lets you set a non-polling Trigger component in the SDK.


Allow the Dynamic Creation of a Gateway Log The new iBOLT function, Logging (Start/Stop, ‘Filter’), lets you dynamically start and stop filtering options.

Search Options in iBOLT Studio iBOLT now lets you search for business processes, flows, steps in a flow, variables, and nodes in the Data Mapper (for both source and destination)

A Separate Server Error for Each Project The GeneralErrorLog entry was moved from the magic.ini file to the ifs.ini file and each project’s ifs.ini file holds the name of the project in the log.

Creating a Variable in Trigger Configuration You can now open the Variable repository while in trigger configuration.

Packager Enhancements An Extract button was added to Project Packager, which lets you extract the package into the iBOLT installation folder.

iBOLT Monitor Enhancements In the Monitor, you can now easily filter the messages that you want to display. You can decide to display all of the messages or only the error messages or component logging messages.

In addition, the Range from the FSID filter was replaced with a single FSID field.

SDK: Java Component Error Handling For Java errors, you can now map errors thrown from the Java class to errors defined for the Java component in the iBOLT SDK dialog box’s Java Exception Message column.

Build/Debugger Enhancement A View Errors button was added to the error messages that appear when the Checker finds errors when starting the Debugger or building a project. You can click the View Errors button to open the Checker Results dialog box.

Domino Component Enhancement • The Read Mail method has the new IncludeBody parameter, which

will specify whether the body of the mail will be included in the output.

• The Read Calendar Entries method now includes the List Type parameter, where you can decide if the list will be of Entries, Notices, or both, and the Notice Type parameter.

• The new Update Notice method will be used to accept conference/meeting invitations and send an acceptance mail to the chairperson or originator of the conference.


Email Component: Additional Attributes Email messages read by iBOLT will now return additional metadata attributes in the result XML. For each attachment, iBOLT now has the date/time, content language, content type and attachment size.

iBOLT on Oracle 11 iBOLT now supports Oracle 11 as an internal database and as a resource.

Microsoft Dynamics CRM The new iBOLT Dynamics CRM connector lets you work with the Microsoft® Dynamics™ CRM application.

Google Calendar Component: All Day Event Support The Google Calendar component now lets you determine if you want a calendar event to last all day.

Studio Usability Enhancements The Build icon was added to the Studio toolbar.

SAP B1 8.8 The iBOLT SAP B1 2007 component now works with SAP B1 8.8.

WebSphere MQ 7.0 iBOLT now supports the IBM WebSphere® MQ 7.0 client/server.

Salesforce Connector: Reference Using External ID The new iBOLT Salesforce connector function, setRefbyExternalId, lets you reference an object by its external ID instead of by the object ID itself.

WMQ Trigger Enhancement • The returned XML from the trigger now also provides additional

information, including the message ID, correlation ID, and sequence number.

• In the trigger configurations, you can now set the CorrelationID or Group ID for the Get filter.

New Context Variable iBOLT V3.1 SP1 includes the new C.sys.InvokingBPName context variable, which is the business process where the last error occurred or the Invoke Flow was called.

Change in Behavior In the Direct Access Method dialog box, when you open the Variable list for an Out parameter, you can no longer select system variables, such as C.sys.ErrorCode. This change was made, because the system variables


are updated by the iBOLT Server and not by the user. In the Flow Data service, you can still update these variables.

For Directory Scanner steps, you have to manually change the expression to check if it is NULL instead of an empty string. This is due to a change in behavior. Up until V3.1 SP1, when there was no file to process, the step returned an empty string. In V3.1 SP1, the step returns NULL.

iBOLT V3.1 SP1 Fixed Problems 709691 – Debugger: Setting a numeric value according to a picture resulted in an Illegal Variable error message.

724340 – Studio: When creating several applications in the Topology without clicking OK in between, only the last selected icon was shown.

730786 – Studio: When copying a step (with a condition), to a new flow, the condition was not completely deleted. As a result, the step failed at runtime.

735697 – Data Mapper: When executing a Database source, the Data Mapper returned the error: “Error 9805: No value given for one or more required parameters." and failed to create the required file.

779516 – Directory Scanner Trigger: For any trigger action, the "Returned source file name" was always empty when no variable was set in the "Return destination file name to:" property.

783064 – Migration: User-defined components were not migrated. No methods or parameters were shown when the configuration screen was opened.

783188 – The Server started even when the %currentproject% logical name pointed to a file other than the ibp file.

910759 – The XMLs that iBOLT generated for the Salesforce connector were not valid.

930457 – The iBOLT Editor crashed while building projects, in a specific scenario.

935019 – Scroll bars were not working in flows. It kept jumping to the beginning of the flow.

978068 – Data Mapper: An incorrect result was received when mapping to a template containing multiple repeats.

980608 – When using a WSDL with more than 99 operations, the operation’s number appeared as **, in the Web Services Client Resource’s Security tab.

991617 – When migrating V2.5 projects to V3.1, only one out of two eDeveloper components were migrated.

994222 – Data Mapper: When selecting the HL7 component as an IFC Model and clicking the Map button, the following was displayed: 'f:\iBOLT3sp2\ifclib\hl7\xsd\hl7ifc.xsd'

995534 – When using an Upsert function in a Salesforce component, NULL values were not processed.


997326 – The Mapper screen failed to open and the “Information cannot be retrieved....." DB error appeared, when a flow variable was used in a WHERE clause.

999072 – SDK: A "Run-time error'0'" error occurred when a user tried to drag the method inside the component and the component group was “User Components”.



Copyright © Magic Software Enterprises, September 2009

October 2009 1

iBOLT V3.1 SP1a Release Notes

Welcome to iBOLT V3.1 SP1a, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.

This document highlights the new and enhanced features that have been added to iBOLT V3.1 SP1a. For information about previous iBOLT versions, see the Past Release Notes.pdf file provided with this installation.

General Information



iBOLT V3.1 SP1a Compatibility For information about the various platforms with which iBOLT V3.1 SP1a is compatible, refer to the iBOLT V3 Compatibility Guide.


Migrating from iBOLT V2.5 to iBOLT V3.1 SP1a

iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.1 SP1a. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.



iBOLT V3.1 SP1a Release Notes October 2009 2





Upgrading from iBOLT V3.1 SP1 to iBOLT V3.1 SP1a

iBOLT will automatically upgrade a project developed in iBOLT V3.1 SP1 to iBOLT V3.1 SP1a. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.

In V3 SP1, the System i, COM, Java Class, EJB, JMS, W4 and SAP components appeared in the Lite Version, even though they were not supported. Beginning with iBOLT V3.1, these components were no longer displayed. In iBOLT V3.1 SP1, if you upgrade a Lite Version project that contains one of these components, the components will be replaced with an NOP service.

Supported Internal Databases iBOLT V3.1 SP1a supports the following internal databases:






• MySQL 5.x

• DB2 UDB 8



since iBOLT adds a prefix to each variable name, such as F., C. or G., the maximum size of a variable is 28 characters.


iBOLT V3.1 SP1a Release Notes October 2009 3

• When upgrading directly from iBOLT V3.1 SP1 to iBOLT V3.1 SP1a, you need to redefine the password fields in your resources.







iBOLT V3.1 SP1a Fixed Problems 245710 – When migrating to iBOLT 3.1SP1, if a called flow had an Abort Flow step in it, and in the calling flow there was as 23-abort flow error, the calling flow was not aborted.

315804 – iBOLT generated schemas from SAP A1 with forward slash (/) characters, which are invalid.

590768 – When trying to upsert more than 200 records in a Salesforce connector, an error was returned.

724187 – iBOLT 3.1 SP1 crashed after running for a while, in a certain scenario.

732901 – The ibolt_trigger table’s handle status became 1 instead of 0.

912436 – In the Directory Scanner step’s LAN to LAN method, the 'Return File To' parameter did not return the file contents into variables.

987321 – When the database source had a Numeric column with a picture greater than 18, the Checker gave a “Picture len >18 " error, irrespective of the destination picture /type.



Copyright © Magic Software Enterprises, October 2009

January 2010 1

iBOLT V3.2 Release Notes

Welcome to iBOLT V3.2, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.


General Information



iBOLT V3.2 Compatibility For information about the various platforms with which iBOLT V3.2 is compatible, refer to the TTTiBOLT V3 Compatibility Guide.


Migrating from iBOLT V2.5 to iBOLT V3.2 iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.2. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.

Note: We recommend reading the Migration chapter in the iBOLT Help before migrating your iBOLT V2.5 projects. We have updated the Preparing Your Project for Migration topic with additional and important information.


iBOLT V3.2 Release Notes January 2010 2





Upgrading from iBOLT V3.1 SP1a to iBOLT V3.2

iBOLT will automatically upgrade a project developed in iBOLT V3.1 SP1a to iBOLT V3.2. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.








• MySQL 5.x

• DB2 UDB 8


Known Issues • In some iBOLT installations on Windows 2008, the iBOLT services do not

stop properly.




• When upgrading directly from iBOLT V3.1 SP1a to iBOLT V3.2, you need to redefine the password fields in your resources.




• If you run a project with .NET framework support, and you receive the Error in .NET invocation:IFC1.IFC1 Code:2140930047 Set Property: iBOLTFramework.dll location error, you should unregister and then re-register the Iboltinvoker.dll file by using the following command: ‘RegAsm iboltinvoker.dll /tlb:iboltinvoker.tlb’

• The Dynamics CRM connector does not permit switching between users, even if there are two resources with identical parameters except for the user name. The first authenticated user is the one used for the entire server run.

New Features

Exchange 2007 Connector iBOLT V3.2 contains the Exchange 2007 connector, which enables an iBOLT project to interact with the Microsoft® Exchange Server's Contacts and Mail.

TCP Listener Component iBOLT V3.2 includes the TCP Listener component, which enables iBOLT to listen continuously for requests made by a TCP client on a TCP port.

System i Trigger iBOLT V3.2 lets you use the System i connector as a Trigger.

Salesforce Connector Enhancements The Salesforce connector now includes a new Get Timestamp method. Also, additional parameters were added to the Replicate Last Deletes and Replicate Last Updates methods.

Directory Scanner Enhancements The Directory Scanner component now allows you to export log files to formats such as CSV and XML, to enable easier auditing.

The Directory Scanner now supports environment variables for the Mask, Filter, Exclude, File Size, and Polling Interval parameters.


In addition, the Directory Scanner component now lets you work with the TimeStamp filter in the Trigger and method configurations.

WebSphere MQ Enhancements New methods were added to the WebSphere MQ component to support RFH2 header functionality.

Large messages can now be saved directly to a specified file in the Trigger and method configurations, and can now be sent from a source file.

SDK: Component Refresh If you make changes to a component that you created in the Component SDK, you can now refresh and update all steps, simultaneously, that use that particular component.

Data Mapper Enhancements iBOLT now supports XS:Any in the Data Mapper’s destination.

The Data Mapper’s mapping screen now allows you to add a colored background to a specific node, and displays information about the node in a dedicated pane.

The Data Mapper can now work with dynamic SQL statements when you select Database as a destination. These statements are then used “as is”.

In addition, you can now instruct the database to commit each SQL statement automatically (Auto Commit). This can improve performance if you want to connect to a remote database and perform a record level transaction.

Invoke Flow by Expression New fields were added to the Invoke Flow Service that allow you to call a flow by expressions that are evaluated at runtime. The GetBPID and GetFlowID functions were added to iBOLT’s Functions List. These new functions enable you to retrieve a flow or business process ID by name.

Single Database Server Definition The iBOLT installation now has a single database host field for local and remote servers.

Domino Enhancements The Domino component’s XSD has a new node named Form. This gives additional functionality to the Read Mail method, such as permitting the retrieval of emails returned due to errors.

Installation Enhancements You can now control the installation of Systinet when installing iBOLT.


Google Docs Component Method Removed The Remove User Access method has been removed from the Google Docs component. The same functionality can be achieved by using the Set Item Access Control method.

Web Monitor Availability The Web Monitor no longer requires a license.

Studio Enhancements An IFS Settings screen has been added to the iBOLT Studio. This enables you to configure selected ifs.ini (Server) flags directly through the iBOLT Studio and the iBOLT Monitor.

A Print button now appears on the Cross Reference, Checker, and Text Search results screens.

Additional icons have been added to the flow navigation tree, to the Data Mapper, and to the flow indication pane.

A new field, called Project data encoding, has been added to the New Project dialog box.

Resource/Service Import Functionality You can now import individual resources and services that you previously created and saved.

SAP R/3 Additional Node Documentation Additional documentation for the SAP R/3 RFC simple and compound nodes can be seen in the Node Properties dialog box's Additional XML Properties tab.

Schema Connection Error Log Enhancements The Schema Connection Error Log now displays more in depth information about Data Mapper connections that are about to be deleted.

iBOLT V3.2 Fixed Problems 513349 – Changing the editor using the Tools > Class Types menu did not take effect. When trying to change the .NET editor from devenv.exe to vcsexpress.exe, iBOLT tried to load the original editor (devenv.exe).

702399 – When using the Excel component’s Cell method, and setting the Action parameter with the Get Value, Get Formula, or Get Active Row Column options, a duplicate Cell method using the same parameters was created.

706263 – The System i connector’s Help page showed incorrect information for the Run Query method’s Query Name and Query File parameters.


719647 – If the SAPB1 Trigger’s polling interval was less than 1 minute (expressed in seconds) at runtime, the SAPB1 Trigger error 1006 Internal error - No Polling Interval Is Defined was generated.

725572 – The Data Mapper did not support the BLOB LOGGED NOT COMPACT database type.

726618 – In the HTTP Trigger’s configuration screen, the Validation expression parameter gave an Illegal variable error when flow or context variables were used in the Expression Editor.

727825 – When using the Microsoft Visual SourceSafe (VSS) version control, deleting a flow also deleted the main flow, and the flow’s sequence order was not correct.

728661 – The Data Mapper’s XML Source’s Single Instance Filter worked only when a legal parent (compound/complex) node was connected with the Destination’s compound node.

728713 – It was not possible to define a Web service as a consumer when the response returned a header.

728775 – When using the Data Mapper, an error occurred when trying to insert data into a table whose name contained a @ character.

776581 – The Data Mapper did not support SQL statements where one of the field/column names or a table name was a reserved word such as 'Order'.

779954 – When working with SAP R/3, selecting an IDoc extension in the Trigger caused an error if the Trigger was configured to receive a WBBDLD IDoc with an extension.

781709 – The Directory Scanner Trigger returned an error message if iBOLT tried to select a locked file.

783738 – When using the Microsoft Visual SourceSafe (VSS) version control, Data Mapper Source nodes were not available at the Destination after selecting the Print Preview or Project Latest Version options.

785662 – During migration, if a Data Mapper was configured with a positional flat file as a Source, the Format value trimmed the data contained within it. This did not happen in iBOLT V2.

787197 – After migration to iBOLT V3, the iBOLT Studio crashed when trying to open the Data Mapper with the Map button.

794520 – When running certain projects, iBOLT did not create values in the XML Destination when usingthe Data Mapper’s XML Position Forwarding property.

913377 – When defining a Web service as a consumer, while accessing WSDL, a ERROR >> javax.xml.rpc.soap.SOAPFaultException: Server was unable to process request error was given.

913638 – Connected Data Mapper nodes did not appear in the Expression Editor.

915776 – When using the Migration utility’s Upper/Lowercase conversion action, iBOLT converted the entire SQL statement, including variables, to upper case characters.


916188 – The WebSphere MQ component was unable to pass a message of 90M to WebSphere MQ.

929912 – Projects crashed when a Data Mapper contained a Source and an UPDATE Destination in the same Data Mapper on an Oracle database.

931168 – The DB operations’s Update option in the Data Mapper did not work. This occurred only when none of the updated fields were mapped.

931813 –When using the FTP component’s Directory Listing method, the Output XML field's value should be set to No (default) after migration.

934113 – Third level complex references could not be loaded.

934387 – When using the Microsoft Visual SourceSafe (VSS) version control, a Source node at a Destination was not available when the respective flows and business processes were checked out.

934521 – When using the Data Mapper, Expression Editor text was overwritten.

938596 – When using the Microsoft Visual SourceSafe (VSS) version control, the flow sequence was mixed up when a new flow was inserted.

939233 – When using the Data Mapper with a MySQL database, the SQL_WLONGVARCHAR data type was not supported.

940646 – During the migration process, an Email component that was configured with the Quick Receive method, or was configured with the XML interface, lost the mapping connections from some nodes.

971178 – Systinet Web Services framework (SSJ) was not installed during the iBOLT installation if the JAVA_HOME environment variable pointed to any non-Java path.

973488 – When using the SAPB1 connector, if NodesAsProperties was selected as the XML export type, the query result file that was generated was incomplete.

982025 – iBOLT did not abort the flow if there was a SAPB1 error.

982789 – When using the SAPB1 dynamic resource, iBOLT used the first connection defined in the Resource Repository when keeping the connection open.

986401 – The resulting XML in the Data Mapper’s XML Destination contained an illegal extra namespace definition: 'xmlns:=""'.

996960 – After migration, when executing a project containing an Excel component configured with a Cell method set to the GetLastRowColumn, Get Value, or GetActiveRowColumn parameters, a blank value was returned.

998499 – The resulting XML in the Data Mapper’s XML Destination Mapper was invalid because it contained an additional namespace tag.

999610 – When using the Microsoft Visual SourceSafe (VSS) version control, an Index out of bound error occurred when a new business process was inserted.

801443 – The SAPB1 connector failed to update non-English data.

916642 – When using the Data Mapper, the Source node path could not be seen in the connected Destination node’s calculated value expression.


969252 – The Web services consumer did not work when a project was transferred to the deployment server.



Copyright © Magic Software Enterprises, January 2010

April 2010 1




General Information

Installing iBOLT You can find information about installing iBOLT in the iBOLT

. The guide also contains information about the prerequisites for using iBOLT flow components.

Installation Guide.pdf


iBOLT V3.2 SP1 Compatibility For information about the various platforms with which iBOLT V3.2 SP1 is compatible, refer to the iBOLT . V3 Compatibility Guide



iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.2 SP1. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.



iBOLT V3.2 SP1 Release Notes April 2010 2

As a general guideline, we recommend that you examine the Migration log and fix any issues that arise in your iBOLT V2.5 project. You should then run the Migration utility again until all issues are resolved.

Due to changes in schema locations, the following components require reconfiguration (click the Configuration button): SAP Business One, SAP R/3, Salesforce, JD Edwards, and Notes DB. Click OK to save changes.

Upgrading from iBOLT V3.2 to iBOLT V3.2 SP1

iBOLT will automatically upgrade a project developed in iBOLT V3.2 to iBOLT V3.2 SP1. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.








• MySQL 5.x

• DB2 UDB 8

• DB2/400 OS/400 V5R4 and V6R1

Behavior Change • The Max no. of threads field has been removed from the iBOLT

Server Settings dialog box’s Miscellaneous section. You should either set the required threads value in the Assigned License Threads property (under Project > IFS Settings), or directly in the project’s ifs.ini file using:

[MAGIC_ENV]MaxConcurrentRequests = <the Max number of threads>

• The Migration utility performs the mapping operations automatically for all Data Mapper steps and XML interface components.



stop properly.



• When upgrading directly from iBOLT V3.1 SP1a, you need to redefine the password fields in your resources.






• The SharePoint component supports primitive data types only.

New Features

SharePoint Component iBOLT V3.2 SP1 contains the SharePoint component, which enables an iBOLT project to interact with the Microsoft® SharePoint® application. The component allows the following operations to be performed on lists: Query, Create, Update and Delete. The ability to execute queries for the latest changes to lists is also supported.

Salesforce Connector

Bulk API Support iBOLT’s Salesforce connector now supports Salesforce.com’s Bulk API. New operations (Bulk Create, Bulk Update, and Bulk Upsert) have been added to the connector’s XML interface. New methods (Bulk Abort Job, Bulk Check Job State, and Bulk Retrieve Job Results) have been added to the connector’s method interface.


Metadata API Support The Salesforce connector also supports Salesforce.com’s Metadata API. New methods (Metadata CRUD, Metadata Check State, Metadata Deploy, and Metadata Retrieve) have been added to the connector’s method interface.

Endpoint Property in Resource Definitions The Salesforce API endpoint can now be set in the Salesforce resource definitions.

Synchronous Trigger Option The Salesforce connector trigger’s new Synchronous check box lets you synchronize the retrieval of trigger lines and determine their invocation order.

Dynamic Query Filter Using SOQL A new field has been added to object XSDs that are generated by the Salesforce connector. This field allows you to perform advanced queries using WHERE SOQL statements.

Significant Performance Improvements As a result of changes to the WS stack used, the Salesforce connector shows significant performance improvements.

Salesforce API version upgrade The Salesforce connector now supports API 18 and above.

Query Results Split To facilitate the handling of very large query results, it is now possible to split the result into several XML files so they can be processed individually.

HL7 Component Communication Enhancements iBOLT’s HL7 component now contains an additional communication layer. The component can now be used as a trigger, and the new Send HL7 Message method allows you to send HL7 messages to an HL7 server.

SAPB1 Component Enhancements The locking limitation that prevented more than one SAPB1 step running at any given time has now been removed.

Data Mapper Enhancements A Header Line check box was added to the Flat File Destination properties dialog box. This allows you to create a flat file whose header is constructed from your selected delimiter field names.

When using the Data Mapper’s IFC Model Destination, the Always Create Nodes check box is now unchecked by default.


WMQ Component Additional Parameters The Disconnect On Close parameter was added to the WMQ component’s Advanced Quick Get and Advanced Quick Send methods.

System i Trigger Enhancements A new parameter, Key length, has been added to the System i Trigger Configuration dialog box.

JD Edwards Connector Enhancements It is now possible to use a keyword [IBSPACE] to pass a space value to a function when working with the JD Edwards connector.

JMS Component Error Reporting Enhancements The full error (stack trace) is now available in the logs/java/stderr.log.

Migration Enhancements The Migration utility was enhanced to perform mapping operations automatically during the migration process. Any issues resulting from these operations are now available in the migration log.

The Checker now reports an error for all Data Mapper steps or components with an XML interface that require attention after the migration.

iBOLT V3.2 SP1 Fixed Problems 919374 – Special characters were not supported in migrated database resource names.

772447 – Alpha, Time, and Date variables were not surrounded by single quotes in the Data Mapper.

972356 – The schema path of the calling flow's Data Mapper step was not visible when using XML position forwarding.

798816 – It was not possible to concatenate data in the Data Mapper to variables if you wrote <user variable> & <source node>. However, it was possible if you wrote <source node> & <user variable>.

917534 – A calculated value on a relocated node in the Data Mapper could not be changed.

996170 – When using the Data Mapper, iBOLT hung when a nested IF function was used with a complex expression on a node level computation.

719325 – The Directory Scanner’s Return Destination file name contained trailing spaces.

708424 – When the Server Certification Validation field was set to No, the FTP component always tried to validate the server certificate. It gave the following error: Connection to requested FTP server could not be established.

588929 – When using the TCP Listener component, data was processed after the carriage return and not after the data transfer was finished.


916831 – The MSSQL 2008 option was not available in the installation wizard.

929229 – When using the Email component, the wrong default port was used for IMAP.

993605 – In the Component SDK, changing the order of arguments was not handled properly.

995862 - When using the Microsoft Excel component’s Cell method with the Get Value, Get Formula, or GetActiveRowColumn options selected in the Action parameter, and you tried to create a new Cell method with the same parameter, iBOLT copied the previous method with the Value parameter’s direction as In instead of Out.

753710 – The Monitor’s Days to log property was misnamed. It only governed the display and not the actual logging.

785469 – When working with the ODBC MySQL database and the Data Mapper, data was rounded for the FLOAT and DOUBLE data types.

984057 – When the Email trigger was used with an IMAP server, the status of mail that had already been read was changed to Unread.

728599 – When installing iBOLT on a 64-bit machine, the correct 64-bit requester was not installed.



Copyright © Magic Software Enterprises, April 2010

May 2010 1




General Information



iBOLT V3.2 SP1a Compatibility For information about the various platforms with which iBOLT V3.2 SP1a is compatible, refer to the iBOLT V3.2 SP1 Compatibility Guide.


iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.2 SP1a. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.




iBOLT V3.2 SP1a Release Notes May 2010 2

Due to changes in schema locations, the following components require reconfiguration (click the Configuration button): SAP Business One, SAP R/3, Salesforce, JD Edwards, and Notes DB. Click OK to save changes.

Upgrading from iBOLT V3.2 to iBOLT V3.2 SP1a

iBOLT will automatically upgrade a project developed in iBOLT V3.2 to iBOLT V3.2 SP1a. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.








• MySQL 5.x

• DB2 UDB 8

• DB2/400 OS/400 V5R4 and V6R1

Behavior Change • The email filters in the Email component’s Receive methods, as well as

in the trigger configuration, are no longer case-sensitive.


stop properly.



• When upgrading directly from iBOLT V3.1 SP1, you need to redefine the password fields in your resources.


iBOLT V3.2 SP1a Release Notes May 2010 3





• The SharePoint component supports primitive data types only.

iBOLT V3.2 SP1a Fixed Problems 778114 – The Salesforce connector could not update Boolean field values.

921043 – The Salesforce connector could not update Date field values.

995502 – When using the SAP Business One component, the iBOLT Studio crashed when retrieving an object structure with too many user-defined functions.

785469 – When mapping ODBC databases with the Data Mapper, the wrong picture was used for FLOAT and DOUBLE data types.

914024 – The Data Mapper incorrectly handled special XML characters, such as &, when creating UTF8 XMLs.

925478 – A runtime error occurred when using extensions with the SAP R/3 connector.

925479 – The Exchange 2007 connector’s Between query operator did not work.

766269 – When mapping DB2/400 databases with the Data Mapper, the Insert operation failed.

772590 – When mapping MySQL databases with the Data Mapper, there was an error when inserting data to a Unicode field.



Copyright © Magic Software Enterprises, May 2010

July 2010 1

iBOLT V3.2 SP1b Release Notes

Welcome to iBOLT V3.2 SP1b, which has been designed to deliver an easy-to-use, flexible, and cost-effective business integration solution.

This document highlights the new and enhanced features that have been added to iBOLT V3.2 SP1b. For information about previous iBOLT versions, see the Past Release Notes.pdf file provided with this installation.

General Information



iBOLT V3.2 SP1b Compatibility For information about the various platforms with which iBOLT V3.2 SP1b is compatible, refer to the TTTiBOLT V3.2 SP1 Compatibility Guide.

Migrating from iBOLT V2.5 to iBOLT V3.2 SP1b

iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.2 SP1b. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT Version 2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.




iBOLT V3.2 SP1b Release Notes July 2010 2

Due to changes in schema locations, the following components require reconfiguration (click Configuration): SAP Business One, SAP R/3, Salesforce, JD Edwards, and Notes DB. Click OK to save the changes.

Upgrading from iBOLT V3.2 SP1a to iBOLT V3.2 SP1b

iBOLT will automatically upgrade a project developed in iBOLT V3.2 SP1a to iBOLT V3.2 SP1b. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.

Supported Internal Databases iBOLT V3.2 SP1b supports the following internal databases:







• MySQL 5.x

• DB2 UDB 8

• DB2/400 OS/400 V5R4 and V6R1

Behavior Change • The following SharePoint schema changes require the refreshing of the

schema:

o The attachments element that was used to indicate if attachments exist for the items was renamed to attachmentsExist.

o A new attachments section was added to the lists schema.


since iBOLT adds a prefix to each variable name, such as F., C., or G., the maximum size of a variable is 28 characters.









• Sometimes permission problems are encountered when running iBOLT on Windows 2008. To solve this, do one of the following:

o Right-click on the shortcuts, and run the process as an administrator. In this case, the Broker should run as a service (with administration rights) so you will be able to stop or start the server from the Monitor.

o Remove the UAC component if it is not in use.

New Features

SAPB1 Resource – Multiple DI API Support iBOLT now supports the use of multiple SAP Business One Data Interface API versions within a single project. This means that you can work with the SAP Business One DI API version that is located on the same machine as iBOLT, while at the same time connect to a another SAP Business One company, located on a remote server, that is running a different SAP Business One DI API version. You can define the required DI API version through the SAP B1 Resource settings in iBOLT’s Resource Repository.

Salesforce Resource – AllowFieldTruncationHeader Support iBOLT now lets you truncate salesforce.com field values. This enables backward compatibility with projects developed prior to iBOLT V3.2 SP1 (salesforce.com API 12.0).

SharePoint Connector Enhancements The SharePoint connector now enables you to take advantage of the SharePoint server’s ability to add attachments to list items.

In addition, the SharePoint connector can now query based on views.

Web Services Client Resource Enhancement The Web Services Client Resource’s WSDL URL property now supports environment variables.


Web Services Configuration When configuring a Web services step, you can now match the response encoding type with the receiving BLOB by determining the response BLOB type for each operation.

iBOLT Monitor Enhancement You can now specify that you want to delete iBOLT Monitor messages that are older than a selected date.

Database Transaction Support It is now possible to select the DB2/400 DBMS in a flow or Data Mapper level transaction.

SAP Business One 8.8 Connector This version introduces a dedicated SAPB1 connector to support the SAP Business One 8.8 release.

iBOLT V3.2 SP1b Fixed Problems 989680 - The service_types.xml file was deleted, thereby preventing the server from starting.

713220 – Recursion was not identified. This resulted in a Data Mapper crash when opening the node’s calculated value dialog box.

942494 – An error flow was not called when a flow's DB transaction property was set to Yes and the database was also selected for the flow.

782976 – When working with SAPB1, the Delete Document Line method was not available in iBOLT V3 and onwards.

785136 – The Salesforce trigger did not work when the username and password fields were environment variables.

924217 – The SAP R/3 resource’s System Number parameter did not support environment variables.

926228 – The C.UserCode variable was not updated with the trigger.

995502 – When a retrieved SAPB1 object had many UDFs, the iBOLT Studio crashed.

918659 – When upgrading an iBOLT V3.2 project (opening with iBOLT V3.2 SP1a), the upgrade process failed when the project name contained special characters.

772215 – The r3connector.dll and the r3connectorU.dll were missing in the iBOLT Server and Monitor installation.

709228 – The Data Mapper’s DB2/400 GRAPHIC data type was not handled properly.

927277 – The iBOLT Help was opened, and the iBOLT Studio stopped responding, when trying to add a new variable from the condition screen.


912688 – When querying a JD Edwards business function, only elements containing data were returned. Blanks, which are an accepted JD Edwards value, were not returned.

796225 – The Salesforce connector could not find its schema after migration from iBOLT V2.5.

999680 – When using the Data Mapper wizard to insert data into an ODBC database, iBOLT added double quotes to the insert. This caused an error at runtime.



Copyright © Magic Software Enterprises, July 2010

January 2011 1




General Information


When installing iBOLT V3.2 SP2, the new Systinet installation upgrades the existing Systinet installation to version 6.6. If an earlier version of iBOLT was already installed on this machine, there is a specific procedure that you need to follow if you want to use iBOLT V3.2 SP2 and iBOLT up to V3.2 SP1b on the same machine. For detailed information on this issue, see the Options section in Chapter One of the iBOLT Installation Guide.pdf file.


iBOLT V3.2 SP2 Compatibility For information about the various platforms with which iBOLT V3.2 SP2 is compatible, refer to the iBOLT V3.2 SP2 Compatibility Guide.


iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.2 SP2. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT V2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.


iBOLT V3.2 SP2 Release Notes January 2011 2

Note: We recommend reading the Migration chapter in the iBOLT

Help before migrating your iBOLT V2.5 projects. We have updated the Preparing Your Project for Migration topic with additional and important information.



Upgrading from iBOLT V3.2 SP1b to iBOLT V3.2 SP2

iBOLT will automatically upgrade a project developed in iBOLT V3.2 SP1b to iBOLT V3.2 SP2. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.

Systinet Since V3.2 SP2, iBOLT installs Systinet 6.6 and JRE 1.6. This version of Systinet supports Java 1.6.

Java 1.4 will not be supported when working with SSJ.

When upgrading iBOLT from versions earlier than V3.2 SP2, you might encounter the "Web Application Internal Error" message when you open the Systinet Web Console. If this happens, carry out the following steps:

1. Remove or rename every subfolder under the %WASP_HOME%\work subfolder (including the system subfolder and one subfolder per server package).

2. Restart the Systinet server. Systinet will then regenerate the entire content of the work folder.





• Microsoft® SQL Server 2000 (32-bit client only)



• MySQL 5.x

• DB2 UDB 8

• DB2/400 OS/400 V5R4 and V6R1


Behavior Change • The following SharePoint schema changes require the refreshing of the

schema:

o The attachments element that was used to indicate if attachments exist for the items was renamed to attachmentsExist.

o A new attachments section was added to the lists schema.

Known Issues • The Salesforce connector does not work if it is behind a proxy that

requires only basic authentication.

• In iBOLT V3, the length of a variable name is 30 characters. However, since iBOLT adds a prefix to each variable name, such as F., C., or G., the maximum size of a variable is 28 characters.




• Unicode data cannot be mapped to XML nodes encoded as Base64.







• The .NET Service does not currently support .NET Framework 4.


New Features

JRE Version Upgrade iBOLT is now shipped with JRE 6.0.

Systinet Version Upgrade iBOLT is now shipped with Systinet 6.6 with support for Java 6.0.

Support for Dynamics CRM 2011 iBOLT was tested for compatibility with the latest version of Dynamics CRM.

New Trigger Parameter A new monitoring mechanism allows you to identify and recover unresponsive triggers.

New SOQL Query Method in Salesforce Connector A new Salesforce connector method called SOQL Query enables you to send a full SOQL query and receive an XML containing the query result.

Allowing Empty Nodes with SAPB1 A new flag (SAPB1RemoveEmptyNodes=) in the iBOLT ifs.ini file allows you to remove or retain empty nodes that may occur when configuring the SAPB1 connector with an XML interface.

Exchange 2007 XML Configuration Enhancements The Update operation can now be used with the Mail entity in the Exchange 2007 connector’s XML configuration. This can be used, for example, to mark an email as read by updating the IsRead element value to true.

In addition, the Exchange 2007 connector now supports User Fields 1 to 4 when working with the Contacts entity’s Add, Query, and Update operations.

New NULL Function The NULL() function has been added to iBOLT’s list of functions.

Time Filter in Domino Component The Domino component now lets you read calendar entries and contacts based on the time of creation and not just on the date of creation.

Data Mapper Representation Enhancement When using the Data Mapper, float and double XML data types can handle lexical representation containing an optional E or e, followed by an exponent.


Customizing .NET Service Icons When working with the .NET service, you can use your own icons in place of the standard default icon. This enables you to easily distinguish between multiple .NET service instances in the same flow. For additional information, see the .NET Service – Configuration section of the iBOLT Help.

SAP R/3 RFC Callback Enhancement You can now control which programs the RFC callback function can run on a client machine by setting the new RfcAllowStartProgram= flag with the functions’ names.

Required Licensing Information You can now view a list of all the licenses that are required to run your project in a production environment, based on the components that you have configured in the project’s flows.

HTTP Component New REST Method The HTTP component has a new REST method. This method enables you to use the GET, POST, PUT, HEAD, and DELETE HTTP verbs.

Error Handling Concept Paper A new concept paper that explains how iBOLT handles errors has been added to the iBOLT Help and to the iBOLT installation package.

iBOLT V3.2 SP2 Fixed Problems 585187 - When querying an object using Salesforce, the Operation Success variable always returns Success(True) regardless of the query output.

589334 – When using the Java Class connector, the following error was thrown when calling a method with more than four parameters: java.lang.Exception: Incompatible signature and number of arguments!

590864 – The Studio crashed when opening the UDS with the context view in Debug mode.

709967 – The Data Mapper generated an invalid XML file.

710113 – Schedulers were not converted correctly during migration.

712283 – When using the Data Mapper to map a flat file to several DB2400 databases, the last Destination received all the records.

714956 – The HTTP Trigger generated a TCP timeout error on large responses.

715833 – The LDAP Get function did not work, and returned a blank output.


722935 – When using the SAP R/3 connector, if an RFC had two nodes with similar names (such as PARTNER_FUNCTION and PARTNER), the data sent to the RFC was incorrect.

724851 – During migration to iBOLT V3, the wrong metadata value was set for disabled flows.

729784 – The SAPB1 connector could not update fields with an empty value, that is ''.

730587 – When migrating a project that contained an Oracle database Destination with picture >22, it was translated into picture N10.-12.

732536 – When using Salesforce to create a new document, if any BLOB type information was specified inside the Document > Row > Fields > Body parameter, the following error was returned: INVALID_TYPE_ON_FIELD_IN_RECORD.

732995 – When importing or exporting a flow containing a Data Mapper step, calculated values on replicated complex nodes were lost during the import process.

734943 – The Dynamics CRM’s Query operation failed when criteria contained XML illegal characters.

771780 – When using the DebugMapper= flag, SQL statements were not logged properly.

772430 – The .NET Service would not update a logical variable value from .NET code to iBOLT.

776940 – When an environment variable had a value such as A%99%B, it was translated as AB at runtime.

778737 – The Data Mapper created the following invalid namespace definition: xmlns:soap="http://"

780420 – When used with ODBC and the Fox Pro database, the Data Mapper Wizard put double quotes in Select statements.

780668 – The Data Mapper generated errors when several database operations were defined in the Destination.

782456 – The .NET Service did not pass iBOLT BLOB variables to the .NET class.

783279 – The Salesforce connector’s Update Object Structure method failed if the script length exceeded 10K characters.

784321 – When working with XML files, the Data Mapper’s fractionDigits restriction was ignored and only the totalDigits was used for the numeric variable picture.

785148 – RPC-type Web services could not be deployed when using Numeric type input/output arguments.

788195 – When a project contained a Compound Level Computation performed on a Data Mapper Destination, the iBOLT Studio would hang.

793051 – After executing a .NET service, the project created a cmd.exe file that could be seen in the Task Manager and was not released.

803135 – When using the Exchange 2007 connector to query a contact that had a value in its Web page address, the query failed.


803333 – When trying to convert a UTF-8 or UTF-16 encoded XML to an HL7 message, the conversion failed.

918223 – When used in a step, the Web Service Consumer’s operations were not shown when they did not contain any arguments.

918539 – When using the Exchange 2007 connector to perform a Query operation on a Mail entity, the resulting XML was not well-formed if the mail subject contained the & character (ampersand).

935737 – Upserting date fields in the YYYY-MM-DD format resulted in a date value of -1 in Salesforce.

940279 – When using the FTP component’s Get File method, the operation generated an error if the file’s name consisted of Hebrew characters.

967479 – In the iBOLT Studio’s Environment Variable Repository, it was not possible to switch from the User tab to the Internal tab until an entry was defined in the User tab.

967853 – If an Email resource that was defined with environment variables was selected in the Project Properties dialog box’s Environment tab, the following error was returned: Cannot connect to mail server

971603 – When the SAPB1 8.8 connector was added to a project from an earlier version that did not contain this connector, iBOLT looked for the schema in the ifclib folder and not in the projects folder.

976979 – Hebrew characters were not displayed from Web service responses after performing the migration and bridge processes.

978093 – When trying to create a new numeric Data Format with a picture of #.# (for example, 6.5 ; 2.2 ; 9.2), the following error was generated: Wrong number format. A Data Format could contain only one decimal digit and two whole numbers.

978478 – When defining a new SAP A1 service, the following error was returned: There are no resources defined for service '[service name]'

992610 – When using the Salesforce connector’s Replicate All Data method, there was a memory leak.

992710 – In a Data Mapper step with an MSSQL database configured as a Source or a Destination, the SQL statement generated by the wizard referenced the table as Owner instead of Schema.

993549 – When installing iBOLT, there were missing SAP R/3 DLLs when the iBOLT Server and Monitor and iBOLT Server options were selected in the iBOLT Module Selection screen.

996173 – Updating a BLOB variable in the Flow Data Service resulted in the following error: Error 800 Invalid Expression

997904 – When configuring the Data Mapper to work with Oracle databases, the following error was returned if the Oracle resource name was too long: Mapper Db Transaction error: ORA-12154: TNS:could not resolve the connect identifier specified


998854 – A.NET Service step could not be called if one or more flow variables were NULL.



Copyright © Magic Software Enterprises, January 2011

April 2011 1




General Information


When installing iBOLT V3.2 SP2a, the new Systinet installation upgrades the existing Systinet installation to version 6.6 if the existing installation of Systinet is version 6.5.2 (any iBOLT version before V3.2 SP2). If an earlier version of iBOLT was already installed on this machine, there is a specific procedure that you need to follow if you want to use iBOLT V3.2 SP2a and iBOLT up to V3.2 SP1b on the same machine. For detailed information on this issue, see the Options section in Chapter One of the iBOLT Installation Guide.pdf file.


iBOLT Compatibility For information about the various platforms with which this version of iBOLT is compatible, refer to the latest iBOLT Compatibility Guide.


iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.2 SP2a. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT V2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.


iBOLT V3.2 SP2a Release Notes April 2011 2





Upgrading from iBOLT V3.2 SP2 to iBOLT V3.2 SP2a

iBOLT will automatically upgrade a project developed in iBOLT V3.2 SP2 to iBOLT V3.2 SP2a. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.













• MySQL 5.x

• DB2 UDB 8

• DB2/400 OS/400 V5R4 and V6R1


Behavior Change

Domino Component Each attachment will be saved under a unique folder name, but the actual attachment file name will stay intact. In previous versions, the actual attachment name was changed to maintain the uniqueness of the names.







• Unicode data cannot be mapped to XML nodes encoded as Base64.









New Features

Salesforce Connector Enhancement The Salesforce connector’s Query by SOQL method can now split XML result records into several XML files.

Exchange 2007 Connector Enhancements The Exchange 2007 connector can now be configured as a Trigger.

The connector now supports Calendar and Task entities in its XML configuration.

The Calendar entity can now work with extended property name-value pairs.

Dynamics CRM Connector Enhancements The Dynamics CRM connector’s XML configuration has a new Change State operation that can be used to change the state of any Dynamics CRM entity.

In addition, the connector can now work with Microsoft Dynamics® CRM on-demand deployments.

WSDL Port Selection When loading a WSDL, you can now specify which WSDL port will be used for the load process.

Email TLS Support The Email resource’s secure email connection configuration now supports TLS.

HTTP Component URL Length Enhancement The HTTP component can now work with a URL of up to 2500 characters.

MSSQL Client Support iBOLT now supports the MSSQL 64-bit client server.

Julian Date Time Support The GetDate and DateTimeFormat functions now support the Julian date time format.

Data Mapper Call Flow Error Handling You can now use the Data Mapper’s Error behavior parameter’s Exit and Continue settings to control what happens when a flow returns an error to the calling Data Mapper.

Data Mapper anySimpleType Support The Data Mapper now supports the anySimpleType data type.


Domino Component Enhancement When working with the Send Email method, you can now add additional attachments to each Attachment Path, separated by commas.

iBOLT V3.2 SP2a Fixed Problems 966218 – When using the Data Mapper to select a column value containing an Oracle "long raw" data type, which was then mapped into a BLOB variable, the following error was generated: ORA-00932: inconsistent datatypes: expected %s got %s

721274 – In certain scenarios, copying and pasting a step resulted in errors in the step’s expressions.

798797 – Error messages generated when Web Service providers failed to deploy were not cleared even when subsequent deployments were successful.

993466 – When defining a Web Service operation in the Service Repository, the schema's element disregarded the user's choice and always returned to the default value.

722593 – When a Dynamics CRM connector’s entity used a Boolean data type, creating or updating a record for such an entity always set the Boolean type as False.

985187 – Mapping a column with an empty value ('') to a variable set the variable value to NULL instead of blank ('').

777560 – When working with the SAPB1 connector’s user-defined tables, Alphanumeric type fields with text structure were not handled properly.

800909 – In a specific scenario, when mapping a flat file to a database, the insertion of a large quantity of records resulted in a crash.

520849 – When performing a bulk operation with the Salesforce connector, the currency type field was wrongly given a Numeric (260) picture.

713257 – When importing a flow containing a User component whose component ID was already in use in the destination project, the new component referenced the existing component.

981750 – The File Management component’s Delete Folder method deleted the wrong folder when the Folder Name parameter was Null or blank.

915183 – The Data Mapper did not behave correctly when there was a rollback in a called flow.

590615 – The Microsoft® Excel component’s List To XML method did not work.

776283 – The Email component could not read emails when several of the attachments had identical file names.




Copyright © Magic Software Enterprises, April 2011

December 2011 1




General Information


When installing iBOLT V3.2 SP3, the new Systinet installation upgrades the existing Systinet installation to version 6.6 if the existing installation of Systinet is version 6.5.2 (any iBOLT version before V3.2 SP2). If an earlier version of iBOLT was already installed on this machine, there is a specific procedure that you need to follow if you want to use iBOLT V3.2 SP3 and iBOLT up to V3.2 SP1b on the same machine. For detailed information on this issue, see the Options section in Chapter One of the iBOLT Installation Guide.pdf file.




iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.2 SP3. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT V2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.


iBOLT V3.2 SP3 Release Notes December 2011 2





Upgrading from iBOLT V3.2 SP2a to iBOLT V3.2 SP3

iBOLT will automatically upgrade a project developed in iBOLT V3.2 SP2a to iBOLT V3.2 SP3. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.













• MySQL 5.x

• DB2 UDB 8

• DB2/400 OS/400 V5R4 and V6R1


Behavior Changes

Stand-Alone Steps When a flow has a “max instance” definition, and this flow also contains a stand-alone step, the stand-alone step no longer uses the flow’s “max instance” definition.

iBOLT Server Reload For the Broker to reload a server, the project name must be listed in the Mgrb.ini file. From this version, the iBOLT Monitor gives a visual indication if the project is not listed in the Mgrb.ini file. In addition, the server will write a message to the server error log if this situation occurs. For more information, see the Deployment Issues topic in the iBOLT Help.

Scheduler Service The Scheduler service now starts running from the current hour, as long as the Minutes after the hour value has not passed.

SAP R/3 Connector The SAP R/3 connector debug is now activated from iBOLT’s log4j.xml file, and the SAP R/3 debug log files are now called ifc.sapr3.log (for SAP R/3 steps) and ifc.sapr3Trigger.log (for SAP R/3 triggers).

In addition, the default value for the SAP R/3 Configuration screen’s Keep Connection Open parameter has been changed to unchecked. (This also applies to the same parameter in the SAP A1 connector.) For more information, see the SAP R/3 and SAP A1 - XML topic in the iBOLT Help.

External Code Page The default value set in the installation is the system code page. If you want to work with another language whose code page is different from the operating system, you should specifically set that language's code page in the Magic.ini file’s ExternalCodePage field. If no value is assigned, the system's default code page is used.








• Unicode data cannot be mapped to XML nodes encoded as Base64 unless a suitable conversion is performed.








New Features

JD Edwards World Connector iBOLT V3.2 SP3 contains the JD Edwards World connector, which enables an iBOLT project to work with JD Edwards World.

The JD Edwards World connector requires a special license, and you must have a connection to a DB2/400 database.

The following JD Edwards World releases are supported:

• A 7.x

• A 8.x

• A 9.x

SharePoint Connector Enhancements The SharePoint connector now supports Libraries as an entity type. This lets you upload documents into SharePoint, and move them to and from different locations on the server. You can also use this entity type to query, delete, and update documents.

From this version, the SharePoint connector has a new icon in the Components pane.


Dynamics CRM Connector Enhancements The Dynamics CRM connector now includes an Assign operation. This lets you change the owner of a specific entity in your organization.

JDE E1 Connector Name Change and Enhancements The JDE E1 connector is now called the JD Edwards Enterprise One connector. It also has a new icon in the Components pane. This is to distinguish it from the new JD Edwards World connector.

The JD Edwards Enterprise One connector now allows you to search for a specific BSFN according to its name or description.

From this version, the JD Edwards Enterprise One connector uses a connection pooling mechanism to handle connections to the JD Edwards Enterprise One server. The size of this pool can be defined from the JD Edwards Enterprise One resource settings.

Exchange 2007 Connector Enhancements

The Exchange 2007 connector’s XML configuration screen now has the following additional functionality:

• The Impersonate field enables an account on a computer that is hosting an Exchange 2007 server to perform actions by using the permissions that are associated with another account.

• To allow the handling of very large query results, it is now possible to split the result into several XML files so they can be processed individually.

Salesforce Connector Enhancements The Salesforce connector has been upgraded to work with API 23.

Web Service Client Error Message Enhancements When working with a Web service client resource, and the load process fails, Java exception and stack trace information is now displayed in the resulting error message.

Additional Debugging Flags The IFS Settings interface now includes debug options for the SharePoint and Exchange 2007 connectors.

Data Mapper Performance Enhancements Beginning with this version, the Data Mapper delivers enhanced performance when mapping any Source type to an XML Destination.


Support for Chinese Machines To allow iBOLT to work with Chinese machines, the iBOLT installation contains a new folder named Chinese support.

In addition, users working with Chinese machines can now use the SHIFT+SPACE key combination to access the Expression Editor’s auto-complete facility.

HL7 Resource Response Timeout The HL7 resource has a new Response Timeout field. This allows you to control the duration of time that the HL7 step will wait for a response from the HL7 server.

SAP R/3 Enhancement From this version, the SAP R/3 connector is implemented using the JCO API.

In addition, the SAP R/3 connector now uses a connection pooling mechanism to handle connections to the SAP R/3 server. The size of this pool can be defined from the SAP R/3 resource settings.

iBOLT V3.2 SP3 Fixed Problems 915159 – In Navision Web services, when trying to create a record that already exists, the error response from the Web service was handled as a Java exception instead of as an iBOLT fault.

738444 – The Minutes after the hour interval was not calculated from the current hour. See the Scheduler Service topic in the Behavior Changes section (above).

942040 – The “Error thread abnormally terminated” message appeared when using the Data Mapper with a Database Source or Destination while the DB Disconnect parameter was checked.

790954 – When a Web service provider’s Operation Name included spaces, the operation was created with a different name.

990261 – Wrong input/output types were displayed when using certain WSDLs.

737146 – Automatic mapping when migrating from iBOLT V2.5x to iBOLT V3.2x deleted connections for unmapped parent nodes when there were database tables with a field name greater than 30 characters (table.<field name>).

769862 – When upgrading from iBOLT V3.2 SP2 to iBOLT V3.2 SP2a, Dynamics CRM resource parameters were not added to iBOLT V3.2 SP2a projects.

775155 – The migration process from iBOLT V2.5x to iBOLT V3x resulted in SQL statements being cut.

727244 – Columns containing Memo data types were displayed as BLOBs, but Insert or Update statements failed when data included more than 27 characters. A runtime error signalling string data truncation appeared.


720138 – When there were multiple mappings, and the Always Create Nodes check box was selected, the thread would crash.

981027 – When a schema entry name was the same as one of the child complex nodes, the XSD tree was not opened correctly in the Data Mapper.

724540 – XSD generation was invalid for certain SAP R/3 RFCs.

732206 – The wrong picture appeared in the generated XSD for SAP A1 packed variables.

784856 – Using an Invoke Flow service with empty UDS variables as an argument caused iBOLT to crash.

730137 – The Data Mapper returned incorrect output when an XML Source had more than one single instance filter.

924836 – When using the Salesforce connector’s Date, DateTime, and Logical data types, the Bulk Create, Update, and Upsert operations did not work.

981689 – The Salesforce connector’s Query by SOQL operation caused a crash if the query size was greater than 1000 characters.

587956 – When receiving emails with inline attachments, only one attachment was received.

792639 – Modifications to a Directory Scanner trigger were lost after modifying an upgraded project from iBOLT V3.2 SP2.

797302 – Querying a large number of Contacts from the Exchange 2007 server resulted in failure. See the Exchange 2007 Connector Enhancements topic in the New Features section (above).

929755 – After restarting the server when working with a Directory Scanner trigger, the new log was written in small sections. These were split between all existing files, instead of in a new log file, if the size of the original log files was 1MB per file.

942125 – If there were three files in the Directory Scanner’s Exclude filter, the last file was not excluded if the file names exceeded a certain length.

999794 – The Email component could not create an XML attachment tag when an email was sent from the Exchange 2007 server, or when an email carried an attachment but no body.

728110 –The HL7 component’s Send Message method did not support extended characters.

518558 – When logging in to Oracle as Scott/Tiger with Scott as the starting owner and selecting the system owner table from the Data Mapper Destination’s DB wizard, clicking Map resulted in an error message about missing permissions.

715576 – If a flow contained a Data Mapper step with an ODBC or MSSQL DB Destination, followed by a Data Mapper step with an Oracle DB Destination, an “out of memory” message was generated in the second step.


787262 – An error was generated when converting a UTF-8 HL7 message to XML. The conversion did not work for all of the objects, and the message was cut.

916621 – When a user did not have permission to delete from an FTP source, iBOLT entered an endless loop of getting requests from the FTP and then freezing.

585055 – An item attachment could not be queried using the GetByID operation.

993495 – When new errors were added in an existing Java component, the new errors were not used. Only existing errors were referred to.

933536 – The File Management component’s Copy Folder method did not allow folder content to be copied to an existing folder.

754628 – The StrTokenCnt function displayed the wrong structure in the Expression Editor.

980915 – The iBOLT Studio sometimes did not respond after using the Build or Rebuild All options.

913617 – Calculated values for nodes were deleted in certain projects.

914617 – When using flat files as Data Mapper Destinations, and the Header Line check box was selected, headers were not displayed in the correct new order when defined fields were moved up and down from their original location, even though the headers’ data was shown in the correct position.

940555 – When using AppendXML in the Data Mapper, two different executions displayed different results.

931826 – If the MSMQ component’s Advanced Quick Send and Advanced Send methods’ Label field contained a string with a comma, the message was not sent correctly and an error was generated.

984561 – The instructions for manually installing an MSSQL internal DB were incorrect.

712970 – Some Data Mapper settings were cleared when building certain projects.

929833 – The WebSphere MQ component’s MQ DLL log did not have a date indication.

938510 – When using the WebSphere MQ component as a trigger, it did not return messages whose size was greater than 32K.

984835 – The Email resource’s User field was limited to 30 characters.

923227 – A Data Mapper with a Database Source generated an error at runtime when a numeric flow variable with a value greater or equal to 13 was used in a WHERE clause in a DSQL Statement.

913889 – When iBOLT was installed as a service and the server was started from the Monitor after a TCP/IP connection reset, the connection was lost and the project would not run.

738194 – The Abort flow’s Cleanup Recovery Flow recovery policy was not executed when a thread crashed.


918099 – When running a certain project several times, a "Recover flow" message appeared in the Monitor for no apparent reason.

977020 – When using a “max instance” definition with the Stand Alone processing mode, iBOLT froze. The removal of the “max instance” definition resulted in the process working correctly.

984008 – Opening a Salesforce resource from the Monitor caused an error when trying to validate the resource and when trying to open any project.

973021 – iBOLT was unable to work with the TFS version control.

993205 – The Component Model SDK’s uniPaaS component could not load an ECI or an ECF if they contained a vector.

805321 – The SpecialPrice object was not exposed for update in the SAPB1 2007 and SAPB1 8.8 connectors.

940141 – The Microsoft Word component’s WinWord.exe file was not closed from the Task Manager when the project was executed via iBOLT as a service.

782274 – The SAPB1 trigger ignored Disable and Enable commands.

998662 – When generating a Web Service Consumer, the request to the WSDL URL was pre-emptively sent with authentication even when no user or password were configured for the WSDL.

923336 – When using the JD Edwards Enterprise One connector, null characters returned from a BSFN resulted in an invalid XML.

784498 – When adding an Exchange 2007 connector in an upgraded project, the connector’s error 1150 was missing from the errors list.

764492 – The JD Edwards Enterprise One connector generated a schema with no root for some of the BSFNs.

781911 – Flows with a Hebrew name could not be imported.



Copyright © Magic Software Enterprises, December 2011

June 2012 1




General Information


When installing iBOLT V3.3, the new Systinet installation upgrades the existing Systinet installation to version 6.6 if the existing installation of Systinet is version 6.5.2 (any iBOLT version before V3.2 SP2). If an earlier version of iBOLT was already installed on this machine, there is a specific procedure that you need to follow if you want to use iBOLT V3.3 and iBOLT up to V3.2 SP1b on the same machine. For detailed information on this issue, see the Options section in Chapter One of the iBOLT Installation Guide.pdf file.

If you are using System i servers in any of your iBOLT projects, you can download a host library installation from the Magic Software Download area.



http://devnet.magicsoftware.com/en/library?book=en/iBOLT/&page=iBOLT_Certification/iBOLT_Compatibility.htm�

iBOLT V3.3 Release Notes June 2012 2

Migrating from iBOLT V2.5 to iBOLT V3.3 iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.3. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT V2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.





Upgrading from iBOLT V3.2 SP3 to iBOLT V3.3

iBOLT will automatically upgrade a project developed in iBOLT V3.2 SP3 to iBOLT V3.3. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.














• MySQL 5.x

• DB2 UDB 8

• DB2/400 OS/400 V5R4 and V6R1

Behavior Changes

System i Host Library The System i host library has been removed from the iBOLT installation. If required, you can download a host library installation from the Magic Software Download area.

Data Mapper When working with the Data Mapper, the Node Properties dialog box’s Always Use The New Picture check box can now be used with Database Source types.

SharePoint Connector When the SharePoint connector is configured as an XML interface, and you select the Add operation, you only need to enter the folder name in the Folder text area.

SAP R/3 Connector The SAP R/3 connector’s log display format has been changed. The new format is:

ProcessId;ThreadID;Timestamp;ExecutionPath;Module;Level;Description

The content itself has not been changed.

















New Features

XML Streaming Parser iBOLT’s Data Mapper now has an XML streaming parser, which can be enabled in the XML Properties dialog box. This allows the Data Mapper to handle large XML documents. The streaming parser is useful in scenarios where a certain compound repeats many times.

Salesforce Connector Enhancements iBOLT’s Salesforce connector now lets you perform Query operations on parent objects and their child objects.

Also, you can now use the Create operation to create parent objects along with their child objects.

In addition, the Salesforce connector’s XML configuration screen has a new Batch Size parameter, which controls the maximum number of objects sent in each request to Salesforce.

SAPB1 8.8 Connector Enhancement The PurchaseQuotations object has been added to the SAPB1 8.8 connector’s object list.

NullifyXMLSourceNonExistentTagValue= Flag A new flag named NullifyXMLSourceNonExistentTagValue= has been added to the [MAGIC_IBOLT] section of iBOLT’s Magic.ini file. If an element does not exist in an XML Source, this flag lets you determine whether the value that is passed to the Destination is the default value of the data type, or whether it will instead be null.

JMS Component Custom Properties Support To allow the JMS component to handle custom messages, the Message Properties parameter was added to the component’s Get and Quick Get methods. In addition, the JMS trigger’s result XML can now hold message properties.

SAP R/3 Connector Trigger Enhancement The SAP R/3 service has a new Connection Count parameter. This lets you define the number of RFC connections that will be used for parallel processing.

Data Mapper Flat File Enhancement The Data Mapper can now work with UTF-8 encoded flat files.


iBOLT V3.3 Fixed Problems 941571 – The JMS trigger failed to receive files with a size greater than 40MB.

512527 – XMLs received from the SAP R/3 trigger when IDocs were sent in a batch (for example, 50 IDocs under one batch/transaction) were not structured properly.

707520 – When using the SAP R/3 router (by defining the SAP R/3 resource’s SAP Router String parameter), a SAP R/3 trigger using this resource rejected all IDocs sent to it.

737064 – IDoc text elements with leading blanks were trimmed when received by the SAP R/3 trigger.

978203 – In some cases, the transaction ID was not returned from the SAP R/3 trigger.

993924 – The SAP R/3 connector (using JCO) created invalid XMLs in the trigger.

752710 – The SapJco3.dll file was missing in the Server Only installation.

799607 – When using an environment variable to set the FTP resource password, and the password was invalid, a general IO error message appeared in the Monitor.

719010 – In certain projects, the settings of arguments that were passed to the called flow were sometimes lost when opening the Invoke Flow steps.

795909 – When working with the Data Mapper, mapping a null value to an XML decimal element with a Nillable = true value created a result XML with a value of 0.0 instead of null.

786860 – After upgrading iBOLT from V3.2 SP2 to V3.2 SP3, the Salesforce connector’s Bulk operations did not work and the following error was generated:

”Error 1203: Salesforce call error: com.magicsoftware.ibolt.salesforce.IBSalesforceException: Salesforce call error (Exception): ClientInputError : Failed to create job.”

728922 – Oracle's CLOB type was shown as ZString size, while in Oracle this type can be up to a maximum of 2GB.

939444 – When connecting to a database via ODBC, and trying to work with a Float field type, iBOLT recognized the value as N15 (in both Source and Destination nodes). See the Behavior Changes - Data Mapper section (above).

921791 – When running a certain project with a Data Mapper Destination set to Call Flow, the called flow would run even though the element and its compound element did not exist in the Source XML.

797566 – When using a DIIOP resource to insert a large amount of source data into Notes DB, the following error was generated:

”Thread-337 java.lang.OutOfMemoryError: unable to create new native thread”


998580 – When the Data Mapper’s Append Data check box was selected, the following error was generated even though the Data Mapper step’s compound node was mapped:

”You must map at least one compound node when you select the 'Append Data' check box”

934962 – When two iBOLT Server processes used the same resource, and each process was filtered for a different IDoc type, the SAP R/3 trigger did not filter out different IDoc types.

513744 – The GetValue action in the Excel component’s Cell method did not work.

932972 – When running projects using the floating license mechanism, a project that was assigned the value of -1 would not be released if it started before a project with threads assigned to it (set to the value of 0). This resulted in no other project being able to start.

777291 – The FTP component’s Delete File and Directory Listing methods did not work.

981210 – The documentation for the Result field in the LDAP component’s LDAP Get method implied that binary objects could be retrieved, and not just strings.

724192 – The Email component’s trigger and step Receive method returned the date/time of a message without an AM/PM designation and not in 24-hour format.

980374 – A UTF-16 project with a Salesforce step using the Bulk Create operation with a Unicode flat file source containing Russian characters, and with the Unicode Support check box selected, resulted in the Salesforce records being created with ???? instead of the required characters.

982350 – In a specific Data Mapper XML to Flat File step, the source elements were not available in Record element destination computation expressions. The <> button was disabled.

995074 – The XML Handling component’s Insert Element Blob method failed to insert certain BLOBs correctly.

722774 – The iBOLT Monitor allowed multiple instances of an iBOLT Server to start.

716020 – In cases where a Notes DB component was executed twice in parallel mode (the flow was invoked twice), and the component was used to query a Notes DB object, one execution retrieved an XML and the other did not (the BLOB remained empty).

728970 – The Salesforce trigger ignored flows’ Enable and Disable settings and invoked the trigger anyway.

783780 – When an element was defined as a ZString in SAP R/3, the schema was created with a limitation of 8 characters.


941991 – When working with the MDM_EQUIPMENT_SAVEREPLICA01 (message type: MDM_EQUIPMENT_SAVEREPLICA) IDoc type in step mode, an error that the schema cannot be created was generated. In trigger mode, there was no error but the schema was not created. When adding a trigger for this IDoc, no XSD was created. In the step mode, the following error was given: "SEGMENT_UNKNOWN"

943015 – There was a memory increase when using the Directory Scanner component as a trigger with many rows.

944629 – The Salesforce connector’s Update field with a DateTime value containing a TimeZone value did not work. The values of the time zone were ignored.

726595 – An iBOLT project generated a "Save RCV Data FileOut of memory. while trying to allocate ...." error, even through the file being processed was less than 500 KB.

785028 – The Salesforce Bulk operation did not process Line Feed and Carriage Return characters properly if the Bulk operation involved more than 10,000 records and the 10,000th record had a Carriage Return field. This resulted in the 10,000th record being “cut” after the Carriage Return, and a new batch was created.

793491 – After adding a project to the Source Control, and closing and reopening the iBOLT Studio, the project could no longer be opened.

726329 – When working with TFS Source Safe, an option exists to perform a Get operation on a specific check in. This lets you see the flow change back to its previous form. However, in the iBOLT Version Control screen, an error appeared next to the flow that was just changed, and it was not possible to fix the error.




June 2012 1




General Information


When installing iBOLT V3.3, the new Systinet installation upgrades the existing Systinet installation to version 6.6 if the existing installation of Systinet is version 6.5.2 (any iBOLT version before V3.2 SP2). If an earlier version of iBOLT was already installed on this machine, there is a specific procedure that you need to follow if you want to use iBOLT V3.3 and iBOLT up to V3.2 SP1b on the same machine. For detailed information on this issue, see the Options section in Chapter One of the iBOLT Installation Guide.pdf file.

If you are using System i servers in any of your iBOLT projects, you can download a host library installation from the Magic Software Download area.



http://devnet.magicsoftware.com/en/library?book=en/iBOLT/&page=iBOLT_Certification/iBOLT_Compatibility.htm�


Migrating from iBOLT V2.5 to iBOLT V3.3 iBOLT provides a wizard to easily migrate your project from iBOLT V2.5 to iBOLT V3.3. This wizard is available through a shortcut in the iBOLT installation’s Start menu. The Migration utility supports projects that were developed in iBOLT V2.5 SP8b or later. If you developed your project in a prior version, you need to upgrade your project's current iBOLT version before you attempt to migrate the project.





Upgrading from iBOLT V3.2 SP3 to iBOLT V3.3

iBOLT will automatically upgrade a project developed in iBOLT V3.2 SP3 to iBOLT V3.3. Make sure to manually copy your <Project> sub-directory to the new installation’s projects directory.














• MySQL 5.x

• DB2 UDB 8

• DB2/400 OS/400 V5R4 and V6R1

Behavior Changes

System i Host Library The System i host library has been removed from the iBOLT installation. If required, you can download a host library installation from the Magic Software Download area.

Data Mapper When working with the Data Mapper, the Node Properties dialog box’s Always Use The New Picture check box can now be used with Database Source types.

SharePoint Connector When the SharePoint connector is configured as an XML interface, and you select the Add operation, you only need to enter the folder name in the Folder text area.

SAP R/3 Connector The SAP R/3 connector’s log display format has been changed. The new format is:

ProcessId;ThreadID;Timestamp;ExecutionPath;Module;Level;Description

The content itself has not been changed.

















New Features

XML Streaming Parser iBOLT’s Data Mapper now has an XML streaming parser, which can be enabled in the XML Properties dialog box. This allows the Data Mapper to handle large XML documents. The streaming parser is useful in scenarios where a certain compound repeats many times.

Salesforce Connector Enhancements iBOLT’s Salesforce connector now lets you perform Query operations on parent objects and their child objects.

Also, you can now use the Create operation to create parent objects along with their child objects.

In addition, the Salesforce connector’s XML configuration screen has a new Batch Size parameter, which controls the maximum number of objects sent in each request to Salesforce.

SAPB1 8.8 Connector Enhancement The PurchaseQuotations object has been added to the SAPB1 8.8 connector’s object list.

NullifyXMLSourceNonExistentTagValue= Flag A new flag named NullifyXMLSourceNonExistentTagValue= has been added to the [MAGIC_IBOLT] section of iBOLT’s Magic.ini file. If an element does not exist in an XML Source, this flag lets you determine whether the value that is passed to the Destination is the default value of the data type, or whether it will instead be null.

JMS Component Custom Properties Support To allow the JMS component to handle custom messages, the Message Properties parameter was added to the component’s Get and Quick Get methods. In addition, the JMS trigger’s result XML can now hold message properties.

SAP R/3 Connector Trigger Enhancement The SAP R/3 service has a new Connection Count parameter. This lets you define the number of RFC connections that will be used for parallel processing.

Data Mapper Flat File Enhancement The Data Mapper can now work with UTF-8 encoded flat files.


iBOLT V3.3 Fixed Problems 941571 – The JMS trigger failed to receive files with a size greater than 40MB.

512527 – XMLs received from the SAP R/3 trigger when IDocs were sent in a batch (for example, 50 IDocs under one batch/transaction) were not structured properly.

707520 – When using the SAP R/3 router (by defining the SAP R/3 resource’s SAP Router String parameter), a SAP R/3 trigger using this resource rejected all IDocs sent to it.

737064 – IDoc text elements with leading blanks were trimmed when received by the SAP R/3 trigger.

978203 – In some cases, the transaction ID was not returned from the SAP R/3 trigger.

993924 – The SAP R/3 connector (using JCO) created invalid XMLs in the trigger.

752710 – The SapJco3.dll file was missing in the Server Only installation.

799607 – When using an environment variable to set the FTP resource password, and the password was invalid, a general IO error message appeared in the Monitor.

719010 – In certain projects, the settings of arguments that were passed to the called flow were sometimes lost when opening the Invoke Flow steps.

795909 – When working with the Data Mapper, mapping a null value to an XML decimal element with a Nillable = true value created a result XML with a value of 0.0 instead of null.

786860 – After upgrading iBOLT from V3.2 SP2 to V3.2 SP3, the Salesforce connector’s Bulk operations did not work and the following error was generated:

”Error 1203: Salesforce call error: com.magicsoftware.ibolt.salesforce.IBSalesforceException: Salesforce call error (Exception): ClientInputError : Failed to create job.”

728922 – Oracle's CLOB type was shown as ZString size, while in Oracle this type can be up to a maximum of 2GB.

939444 – When connecting to a database via ODBC, and trying to work with a Float field type, iBOLT recognized the value as N15 (in both Source and Destination nodes). See the Behavior Changes - Data Mapper section (above).

921791 – When running a certain project with a Data Mapper Destination set to Call Flow, the called flow would run even though the element and its compound element did not exist in the Source XML.

797566 – When using a DIIOP resource to insert a large amount of source data into Notes DB, the following error was generated:

”Thread-337 java.lang.OutOfMemoryError: unable to create new native thread”


998580 – When the Data Mapper’s Append Data check box was selected, the following error was generated even though the Data Mapper step’s compound node was mapped:

”You must map at least one compound node when you select the 'Append Data' check box”

934962 – When two iBOLT Server processes used the same resource, and each process was filtered for a different IDoc type, the SAP R/3 trigger did not filter out different IDoc types.

513744 – The GetValue action in the Excel component’s Cell method did not work.

932972 – When running projects using the floating license mechanism, a project that was assigned the value of -1 would not be released if it started before a project with threads assigned to it (set to the value of 0). This resulted in no other project being able to start.

777291 – The FTP component’s Delete File and Directory Listing methods did not work.

981210 – The documentation for the Result field in the LDAP component’s LDAP Get method implied that binary objects could be retrieved, and not just strings.

724192 – The Email component’s trigger and step Receive method returned the date/time of a message without an AM/PM designation and not in 24-hour format.

980374 – A UTF-16 project with a Salesforce step using the Bulk Create operation with a Unicode flat file source containing Russian characters, and with the Unicode Support check box selected, resulted in the Salesforce records being created with ???? instead of the required characters.

982350 – In a specific Data Mapper XML to Flat File step, the source elements were not available in Record element destination computation expressions. The <> button was disabled.

995074 – The XML Handling component’s Insert Element Blob method failed to insert certain BLOBs correctly.

722774 – The iBOLT Monitor allowed multiple instances of an iBOLT Server to start.

716020 – In cases where a Notes DB component was executed twice in parallel mode (the flow was invoked twice), and the component was used to query a Notes DB object, one execution retrieved an XML and the other did not (the BLOB remained empty).

728970 – The Salesforce trigger ignored flows’ Enable and Disable settings and invoked the trigger anyway.

783780 – When an element was defined as a ZString in SAP R/3, the schema was created with a limitation of 8 characters.


941991 – When working with the MDM_EQUIPMENT_SAVEREPLICA01 (message type: MDM_EQUIPMENT_SAVEREPLICA) IDoc type in step mode, an error that the schema cannot be created was generated. In trigger mode, there was no error but the schema was not created. When adding a trigger for this IDoc, no XSD was created. In the step mode, the following error was given: "SEGMENT_UNKNOWN"

943015 – There was a memory increase when using the Directory Scanner component as a trigger with many rows.

944629 – The Salesforce connector’s Update field with a DateTime value containing a TimeZone value did not work. The values of the time zone were ignored.

726595 – An iBOLT project generated a "Save RCV Data FileOut of memory. while trying to allocate ...." error, even through the file being processed was less than 500 KB.

785028 – The Salesforce Bulk operation did not process Line Feed and Carriage Return characters properly if the Bulk operation involved more than 10,000 records and the 10,000th record had a Carriage Return field. This resulted in the 10,000th record being “cut” after the Carriage Return, and a new batch was created.

793491 – After adding a project to the Source Control, and closing and reopening the iBOLT Studio, the project could no longer be opened.

726329 – When working with TFS Source Safe, an option exists to perform a Get operation on a specific check in. This lets you see the flow change back to its previous form. However, in the iBOLT Version Control screen, an error appeared next to the flow that was just changed, and it was not possible to fix the error.


