ibolt V2.5 SP9 Release Notes

Transcription

1 ibolt V2.5 SP9 Release Notes We are pleased to present the release of ibolt Version 2.5 SP9. ibolt V2.5 SP9 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 SP9 Release Notes November

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: New Features Open each project in ibolt V2.5 SP9. Go to the Data Mapper screen to view your mapping definitions. In the Data Mapper screen, click OK. ibolt reconfigures the mappings to conform to ibolt V2.5 SP9 configurations. UPS Component ibolt V2.5 SP9 includes a new UPS component. The UPS component facilitates connection to United Parcel Service (UPS) applications via the Internet, enabling you to initiate and track package deliveries. The UPS component interacts with the UPS OnLine Shipping Tool Server. Please check which prerequisites are required before you attempt to use this component. For more information see the UPS section of the ibolt Help. New SAP Business One Component Method In ibolt V2.5 SP9, a new method was added to the Method interface of the SAPB and SAPB components. The Delete Document Line method allows you to delete a specific line in a document. For more information see the SAP Business One section of the ibolt Help. ibolt V2.5 SP9 Release Notes November

3 Behavior Changes Domino Component ibolt V2.5 SP9 includes an enhanced Domino component. The Domino component lets you work with the Domino server, to integrate Lotus Notes into your ibolt projects. Parameters have been added to several methods, enabling filtering capability with wildcard support. For more information see the Domino section of the ibolt Help. Removal of the Pervasive Database From this version onwards, ibolt no longer includes the Pervasive database in its installation. This means that new installations of ibolt, where Pervasive is not installed, should follow these guidelines: 1. Use the magic.ini configuration file s Default Database entry to point to an alternative database. This entry is used by ibolt to store user-defined edeveloper components. 2. Do not use the ibolt internal database as a placeholder for these components, as this is deleted during uninstall. 3. The Create As field in the Component Repository s New Component dialog box is disabled if Pervasive is not installed on your machine. 4. Clicking the Get Definition button in the New Components dialog box lets you retrieve an existing component's definition. To use this option, you must first manually create the edeveloper component application within the database that is used to store user-defined edeveloper components. 5. If you are using generated Data Mapper steps, the Default Database entry must point to MSSQL, Oracle, or DB2. It must not point to DB2/400 or ODBC. iseries Component The capacity of the Send Data to Queue method s Input Data parameter, and the Receive Queue Data method s Output Data parameter, has been increased to 32k characters. SAP Business One Connection Screen A new field called DB Server Type has been added to the SAPB and SAP 2005 components connection definitions screen. In this parameter, you select the database type that your system uses. ibolt V2.5 SP9 Release Notes November

4 ibolt V2.5 SP9 Fixed Problems Call Flow Performance Issues (QCR ) The Call Flow operation caused a gradual increase in processing time. Memory Leak (QCR ) When using MSSQL as the internal database, a project with a Scheduler Service trigger caused big rises in the consumption of virtual memory. iseries Database Connection Problem (QCR ) When a connection with a database was successfully established, the tables could not be seen in the Filters for the Database screen. Data Mapper Wizard Performance Issues (QCR ) When working with a table containing a large number of records, Data Mapper wizards would freeze. ibolt Studio Performance Issues (QCR ) Projects that contained Data Mappers took a long time to open in the ibolt Studio. W4 Component Error (QCR ) When the W4 component s Alarm Override and Overdue Override parameters were left blank, the default date value was returned as Microsoft Excel Component Update Failure (QCR ) The GetValue action in the Microsoft Excel component s Cell method did not update the model variable if the cell contained an apostrophe. SAP R/3 Component Trigger Problem (QCR ) When working with certain IDoc invoices, the XML generated by the trigger contained an element that was not located at the correct level. SAPB1 Component Trigger Problem (QCR ) When used as a trigger, the SAPB1 component processed the same record many times. ibolt V2.5 SP9 Release Notes November

5 Data Mapper Error (QCR ) An error occurred when trying to map data from an XML-type Source to a Template-type Destination. Data Type Error (QCR ) The wrong data type was shown for the NVARCHAR2 database field type. ibolt V2.5 SP9 Release Notes November

6 ibolt V2.5 Known Issues Handling XML Documents XML documents are not handled properly if the documents are based on schemas that define simple elements with attributes that have names identical to the simple element (case sensitive). Some XML documents are not handled properly if the documents are based on schemas in which the default namespace is defined, but the target namespace is not defined. When using the Data Mapper to define XML Sources or Destinations, invalid schemas may be only partially processed. If this happens, an error log file, which is called _ERR.txt, will be generated in the ibolt temp directory..net Framework If you run a project with.net framework support, and you receive the Error in.net invocation:ifc1.ifc1 Code: Set Property: iboltframework.dll location error, you should unregister and then reregister the Iboltinvoker.dll file by using this command: RegAsm iboltinvoker.dll /tlb:iboltinvoker.tlb Internal Database Issues If you do not use MSSQL, DB2, or Oracle as ibolt s Internal database, and in the Database Repository you select at least one table for one of these databases, you cannot run a project that uses one of these database tables. This is because the database entry in the [MAGIC_GATEWAYS] section of the Magic.ini file is shown in remark form with semicolons. To solve this, you should manually change the gateway entry, MGDB20, by removing the semicolons. ODBC Limitations When using ibolt s ODBC support, you should be aware that some ODBC drivers are limited to read only, such as XLS drivers. Each ODBC driver will have its own set of limitations. Directory Scanner The Directory Scanner is unable to process read-only files, and does not write to the log file in this situation. ibolt V2.5 SP9 Release Notes November

7 Security Enhancement A security enhancement for Internet Information Services (IIS) 6.0 on Windows 2003 restricts DLL files and executables from working, unless they are explicitly allowed. Therefore, some security settings in the IIS need to be changed to allow the ISAPI/CGI requester to work. For more information, please click here to access the ibolt WebHelp, where you can find a technical note entitled Allowing ISAPI of Magic on Windows Installation Issues When installing ibolt with the Windows 2000 operating system, the following warning message may appear: "The installation package cannot be installed by the Windows installer service. You must install a Windows service pack that contains a newer version of Windows installer service." You need to install Windows Installer 3.1 before installing ibolt. Please use the following link: 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, November, 2007 ibolt V2.5 SP9 Release Notes November