ibolt V3.2 Release Notes Welcome to ibolt V3.2, which has been designed to deliver an easy-touse, flexible, and cost-effective business integration solution. This document highlights the new and enhanced features that have been added to ibolt V3.2. For information about previous ibolt versions, see the Past Release Notes.pdf file provided with this installation. General Information Installing ibolt You can find information about installing ibolt in the ibolt Installation Guide.pdf. The guide also contains information about the prerequisites for using ibolt flow components. ibolt Technical Notes Magic s International Technical Support produces ibolt Technical Notes on a range of useful topics. You can find the Technical Notes in the ibolt Help and on Magic Software Enterprises Website. ibolt V3.2 Compatibility For information about the various platforms with which ibolt V3.2 is compatible, refer to the TTiBOLT V3 Compatibility Guide. This document replaces the previous version s Certification document. 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. January 2010 1
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. 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.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. Supported Internal Databases ibolt V3.2 supports the following internal databases: Oracle 9i (OCI 32-bit only) Oracle 10g (OCI 32-bit only) Oracle 11 (OCI 32-bit only) Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008 MySQL 5.x DB2 UDB 8 DB2/400 V4.4 and above Known Issues In some ibolt installations on Windows 2008, the ibolt services do not stop properly. 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. ibolt V3.2 Release Notes January 2010 2
When upgrading directly from ibolt V3.1 SP1a to ibolt V3.2, 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> 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. Unicode data cannot be mapped to XML nodes encoded as base64. If you run a project with.net framework support, and you receive the Error in.net invocation:ifc1.ifc1 Code: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. ibolt V3.2 Release Notes January 2010 3
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. ibolt V3.2 Release Notes January 2010 4
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. ibolt V3.2 Release Notes January 2010 5
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. ibolt V3.2 Release Notes January 2010 6
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. ibolt V3.2 Release Notes January 2010 7
969252 The Web services consumer did not work when a project was transferred to the deployment server. Magic Software Enterprises Ltd provides the information in this document as is and without any warranties, including merchantability and fitness for a particular purpose. In no event will Magic Software Enterprises Ltd be liable for any loss of profit, business, use, or data or for indirect, special, incidental or consequential damages of any kind whether based in contract, negligence, or other tort. Magic Software Enterprises Ltd may make changes to this document and the product information at any time without notice and without obligation to update the materials contained in this document. Magic is a trademark of Magic Software Enterprises Ltd. Copyright Magic Software Enterprises, January 2010 ibolt V3.2 Release Notes January 2010 8