ibolt V2.5 SP8a Release Notes

Transcription

1 ibolt V2.5 SP8a Release Notes We are pleased to present the release of ibolt Version 2.5 SP8a. ibolt V2.5 SP8a includes new features and enhancements. This document provides information about this latest ibolt version. For information about previous ibolt versions, see the PastReleaseNotes.pdf file provided with this installation. General Information Installing ibolt You can find information about installing ibolt in the ibolt Installation Guide.pdf. The guide also contains information about ibolt environment settings and 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 with the other ibolt technical documentation available on the Web, including ibolt How Tos. Click here to access the Technical Notes and other Web-based documentation. ibolt V2.5 Certification For information about the various platforms on which ibolt V2.5 has been certified for operation by Magic Software Enterprises refer to the ibolt V2.5 Certification document. Project Migration If you are migrating a project from an older version, you should complete the following steps: 1. Save your project in MDD format and open it in the new Studio. To use the latest version s components, copy the components that are used in your project from the /IFCLIB directory into the project directory. Reconfigure the components if necessary. ibolt V2.5 SP8a Release Notes March

2 2. To upgrade your SAP Business One components, do the following: Copy only the SAPB1ifc.mff and SAPB1Metadata2 files from the component s /IFCLIB folder into the project directory. Note: Do not overwrite the SAPB1Defaults2.xml file. To keep your project s connection definitions, copy your SAPB1Defaults2.xml file from the project directory back into either the /IFCLIB/SAPB1_2004 or /IFCLIB/SAPB1_2005 directory. 3. Your Data Mapper definitions are usually updated automatically upon upgrading the component. To manually update the project s Data Mapper, you should: a) Open each project in ibolt V2.5 SP8a. b) Go to the Data Mapper screen to view your mapping definitions. c) In the Data Mapper screen, click OK. ibolt reconfigures the mappings to conform to ibolt V2.5 SP8a configurations. Behavior Changes ItemField CM V4.3 Support ibolt s ItemField Connector now supports CM (Content Master) Version 4.3. HTTP Trigger Enhancements The HTTP trigger can receive BLOBs from HTML pages and pass them to the flow. When the trigger receives a BLOB, it updates the UserBLOB of the invoked flow with the value of that BLOB. For more information, see the HTTP component section of the ibolt Help. Component The User Name and Password properties field length now handles up to 100 characters. MonitorMode Flag Default Value To improve Server performance, the MonitorMode flag s default value has been changed from Both to Activity. This means that statistics will not be logged unless specifically requested by the user. ibolt V2.5 SP8a Release Notes March

3 Web Services Step Endpoint URL It is now possible, by using a Logical Name, to control the service endpoint URL that the Web Service step calls without modifying the project. For more information, see the Web Services component section of the ibolt Help. Additional SAPB1 Trigger UserString Value When a SAPB1 trigger invokes a flow, the UserString now contains the Object Key Values as the last item in the UserString. ibolt V2.5 SP8a Fixed Problems Installing a Broker as a Service (QCR ) When the ibolt Server was installed on its own, the broker could not be installed as a service under some circumstances. iseries Connector Spool File Retrieval Problem (QCR ) Retrieving a spool file of around 500 pages took a long time. Data Mapper Node Properties Problem (QCR ) The Data Mapper s Node Properties screen showed Data type and Internal Attribute as (0) when a query was generated with Order by clause. Pervasive Database Issue (QCR ) When using Pervasive SQL, there was a problem retrieving the first record from a Select statement when using the Top command. Problem with Importing Japanese Projects (QCR ) Importing a project in Japanese caused a numbering mismatch in the Data Mapper schema. Problem with the Data Mapper and CSV Files (QCR ) When a csv file was used as a Data Mapper Source, there was no output to the last Destination field. ibolt V2.5 SP8a Release Notes March

4 Trigger Component Properties Description (QCR ) The trigger component description was not updated, even though it was modified across the whole ibolt session. Problem with Web Services Trigger (QCR ) When using Web Services with a running Server, ibolt did not inform the user that the mff is locked when trying to add an operation to an existing service. Incorrect Time Displays (QCR ) Times were not displayed correctly in both the ibolt Monitor and the ibolt Studio s project properties. Problem with Using the Data Mapper with DB2 (QCR ) When using the Data Mapper with DB2 (on Windows), if the gateway was not loaded there was no error shown in the Monitor. Oracle Installation Issue (QCR ) When installing ibolt with Oracle as the internal database, there was no option to select Oracle 10g, even though it was supported. Error Flow Problem (QCR ) There was a problem displaying Error Flow components in the Studio. Routing Problem (QCR ) When working with two different ibolt Servers, the UserXML was not updated in the second Server. Call Flow Problem (QCR ) When the Data Mapper was used to call a flow twice, in two different steps, and a variable was updated in the called flow, only the value of the first called flow was shown. SAPB1 Error Flow Problem (QCR ) When an Error Flow was set and executed through the Emulator, the SAPB1 component did not display an error message. ibolt V2.5 SP8a Release Notes March

5 Schedule Flow Service Problem (QCR ) ibolt updated the Scheduler table with non-existent times. Problem with Updating JVM Settings (QCR ) The ibolt Studio would crash when the magic.ini was updated to enlarge the JVM Memory to 256mb. 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, March, 2007 ibolt V2.5 SP8a Release Notes March