Infor Integration 6.2

Release Notes

Copyright © 2007 Infor Global Technology Solutions GmbH and/or its affiliates and subsidiaries All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Infor Global Solutions Technology GmbH and/or its affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respective owners.

Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor Global Solutions.

By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor Global Solutions and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor Global Solutions pursuant to a separate agreement (“Purpose”).

In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above.

Although Infor Global Solutions has taken due care to ensure that the material included in this publication is accurate and complete, Infor Global Solutions cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor Global Solutions does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause.

Trademark Acknowledgements

Microsoft®, and SQL Server® are registered trademarks of Microsoft Corporation

HTML,DHTML,XML,XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

All other company, product, trade or service names referenced may be registered trademarks or trademarks of their respective owners.

Publication Information

Document code: U9019E US

Release: Infor Integration 6.2

Publication date: July 07

Table of Contents

Chapter 1 Introduction............................................................................................................. 1-1 Scope and objective................................................................................................................... 1-1 Intended audience...................................................................................................................... 1-1 Summary.................................................................................................................................... 1-2 Acronyms ................................................................................................................................... 1-2

Chapter 2 Enhancements ........................................................................................................ 2-1 BDE support............................................................................................................................... 2-1

BDE runtime support............................................................................................................ 2-2 BDE development support ................................................................................................... 2-2

Delivery ...................................................................................................................................... 2-4 Installation.................................................................................................................................. 2-5 Version information .................................................................................................................... 2-6 Performance of Connectors for ODBC and JDBC ..................................................................... 2-6 Support for Windows Vista......................................................................................................... 2-6 Support for Java 6...................................................................................................................... 2-7 Extended .NET Client API.......................................................................................................... 2-7

Chapter 3 Modifications........................................................................................................... 3-1 Removed components ............................................................................................................... 3-1 Bug fixes .................................................................................................................................... 3-2

Version 6.1........................................................................................................................... 3-2 Version 6.2........................................................................................................................... 3-2

Changed runtime functionality.................................................................................................... 3-3 LDAP directory support .............................................................................................................. 3-4 .NET 2.0 requirement................................................................................................................. 3-4

ii | Table of Contents

Chapter 4 Installation............................................................................................................... 4-1 Server-side adapters.................................................................................................................. 4-2

Adapters for ERP BaanIV, ERP Baan5, and ERP LN.......................................................... 4-2 Windows-only installer ............................................................................................................... 4-3 Manual installation ..................................................................................................................... 4-4 Integration Studio installation ..................................................................................................... 4-4

Chapter 5 Documentation........................................................................................................ 5-1

Chapter 6 Troubleshooting...................................................................................................... 6-1 Adapters on ERP Baan and ERP LN back ends........................................................................ 6-1 Integration Studio ....................................................................................................................... 6-1 Configuration directory ............................................................................................................... 6-2

About this Guide

This document provides the Release Notes for the 6.0, 6.1 and 6.2 releases of Infor Integration. This document includes a high-level summary of the enhancements and modifications of the Infor Integration software with respect to the previous major release, which was released as Adapter Suite 2.7 of SSA Open Architecture 5.1. The document also reports all known issues.

Infor Integration releases 6.0 and 6.1 do not differ significantly and apart form an extended and improved documentation the two releases are more or less the same. Infor Integration 6.2 can be considered to be a maintenance release, in which the previous SSA product is renamed into Infor Integration. This version also includes some additional bug fixes, extended platform support and updates for the latest version of third party software.

The Release Notes also include the latest information on Infor Integration 6.2. For the most current news on this Infor Integration release, such as fixes for reported defects, refer to solution 221761 at:

http://onepoint.infor.com/Solutions/SearchBaanKB.aspx

You require an account for Infor Global Support Online to access this solution.

Notes

These Release Notes treat releases 6.0, 6.1 and 6.2 as a single release.

The current product was previous released as SSA Integration and is rebranded under the name of Infor Integration. All occurrences of SSA are replaced with Infor. However, to keep the programming interfaces backward compatible, class names, package names and namespaces in these interfaces did not change.

The document contains the following chapters:

iv | Table of Contents

Chapter 1, “Introduction,” provides a general introduction to Infor Integration and to this document.

Chapter 2, “Enhancements,” lists the improved and extended features of Infor Integration.

Chapter 3, “Modifications,” summarizes all other changes to Infor Integration, such as removal of rarely-used, obsolete, or trivial components, as well as software fixes and changes in runtime functionality.

Chapter 4, “Installation,” describes how Infor Integration simplifies the installation procedure. Rather than use diverse installers to install the various components, you now use a single installer to install one client-side software bundle.

Chapter 5, “Documentation,” provides an overview of the released Infor Integration documentation.

Chapter 6, "Troubleshooting" describes all known issues.

Send us your comments

We continually review and improve our documentation. Any remarks/requests for information concerning this document or topic are appreciated. Please e-mail your comments to documentation@infor.com.

In your e-mail, refer to the document code and title. More specific information will enable us to process feedback efficiently.

Table of Contents | v

1 Chapter 1 Introduction

Scope and objective

The Infor Integration 6.2 Release Notes provide a high-level summary of the enhancements and modifications of the Infor Integration software with respect to the previous major release, which was released as the Adapter Suite 2.7 of SSA Open Architecture 5.1. This document does not describe these changes in detail. For detailed information, refer to the documentation of the relevant feature.

This document also includes a troubleshooting chapter that describes all known issues.

Intended audience

The Infor Integration 6.2 Release Notes provide information to existing users of the integration software of Infor about changes to the software since the previous release. Users who work directly with the software, as well as individuals who are indirectly involved, must read this document carefully.

1-2 | Introduction

Summary

Infor Integration 6.2, which is the successor to the Adapter Suite 2.7, changed significantly. As compared to the Adapter Suite, the Infor Integration software is enhanced to provide full support for the Business Data Entity (BDE) interface, both runtime and development time. In addition, rarely used and trivial components have been removed and the installation procedure is now much simpler, which makes Infor Integration more user-friendly.

Acronyms

Acronym Description

BDE Business Data Entity

BOI Business Object Interface

ERP Enterprise Resource Planning

ODBC Open Database Connectivity

JDBC Java Database Connectivity

SOAP Simple Object Access Protocol

WMS Warehouse Management System

WSDL Web Service Description Language

2 Chapter 2 Enhancements

Infor Integration releases 6.0 - 6.2 contain the following enhancements:

Full support for BDEs, both runtime and development time (6.0)

Renovated product delivery (6.0)

Simplified installation procedure (6.0)

Indicative and consistent version information (6.0)

Improved performance of Connectors for ODBC and JDBC (6.1)

Support for Windows Vista platforms (6.2)

Support for Java 6 (6.2)

Extended .NET Client API (6.2)

The following sections describe each of these enhancements in more detail.

BDE support

Business Data Entities (BDEs) are the new business interfaces through which business data from an Infor enterprise application server are exposed to the outside world. The current release of Infor Integration fully supports these new BDE business interfaces, both runtime and development time.

2-2 | Enhancements

BDE runtime support

The supported BDE runtime functionality includes two types of business data exposure:

Server call requests

Event notification

In the case of a server call request, a client invokes a method or requests data about a BDE implemented on an Infor enterprise application server. To carry out the request, you can send a SOAP message to the server or call type-safe BDE proxies on the client.

In the case of event notification, a BDE on an Infor application server publishes messages about events that occur to instances of this BDE. To subscribe to these event messages, other applications can submit a subscription to the Infor application server, which specifies the BDE, the type of event, and the BDE attributes of interest. To accomplish BDE event notification, an IBM WebSphere Business Integration Server acts as a broker between the event publisher and the event subscriber.

In the previous release, Adapter Suite 2.7, the BDE runtime functionality was not generally available, because this functionality was expected to change and backward compatibility in future releases could not be guaranteed. In the current release, the BDE functionality changed significantly and is now generally available.

BDE development support

Infor Integration 6.1 introduced the Integration Studio, which is the modeling and development environment for BDEs. This environment is implemented as a feature in the Eclipse framework.

You can use Integration Studio to perform the following tasks:

Define new BDE interfaces.

View and edit existing BDE interfaces.

Define a BDE implementation for a particular Infor enterprise application.

Enhancements | 2-3

Generate, from a BDE implementation, the BDE runtime code or a particular Infor enterprise application. The currently supported Infor application servers are:

Infor ERP LX

Infor ERP LN

Infor WMS

Generate a proxy or WSDL definition for a BDE interface through which a client can access a BDE on a server.

For more information on this functionality, refer to the Infor Integration Studio online Help and to the Developer's Guide for BDEs for Infor ERP LN.

Integration Studio is released in three editions: an ASFU Edition (Application-Specific Full Use), an Express Edition, and an Enterprise Edition. These three editions of Integration Studio offer the following functionality:

ASFU Edition:

Create an interface project.

Import an interface definition.

Generate documentation.

Use all editors in read-only mode.

Express Edition:

All ASFU functionality

Generate BDE proxies in Java and .NET.

Generate BDE definitions in WSDL.

Export interface definitions.

Enterprise Edition:

The full Integration Studio functionality, including all importers, generators, exporters, and wizards, and with full authorization to modify metadata in all editors.

For the ASFU edition, you do not require a license. To run the additional functionality of the Express Edition and the Enterprise Edition, you must have client-side licensing through the Infor Solution License Manager. For more information, refer to the Integration Studio update site at www.studio.ssaglobal.com and to Infor OnePoint Online support services at www.onepoint.infor.com/.

2-4 | Enhancements

Delivery

In Infor Integration, the various loose components of the Adapter Suite are now a more coherent integrity, and rarely used or trivial components have been removed. However, Infor Integration still supports Business Object Interfaces (BOIs) used in previous integrations with ERP BaanIV and ERP Baan5 back ends.

With respect to Adapter Suite 2.7, the following components have been removed:

Connector for SOAP, for Web-enabled BOIs access

Connector for CORBA

Connector for OLE DB

The API of the Connector for JDBC used for back end access through the Adapter for ERP BaanIV or ERP Baan5

The currently released Connector for JDBC only supports back end access through the Adapter for Baan DB Driver (released with the back-end porting set or delivered as a PMC solution).

Note

The Adapter for Baan DB Driver is also known as Enterprise Server DB Library.

The current release only provides the client-side components of Infor Integration. The application-specific server-side components that are based on the BDE business interfaces are incorporated in the relevant Infor enterprise application server.

The BDE-based adapters, which connect the server application to the Infor Integration framework, are shipped, documented, and maintained in the context of the application for which the adapters are used. Although the same applies for BOI-based integration, you can still continue to use the adapters released with the Adapter Suite 2.7, such as Adapter 2.7 for Baan IV or Adapter 2.7 for Baan ERP.

This following table lists the client-side runtime features of the Infor Integration release:

Client runtime features

Business interface Connector

SOAP Java binding BDEs Connector for Web services

Enhancements | 2-5

Client runtime features

Business interface Connector

SOAP HTTP binding BDEs Connector for Web services

API for Java BDEs or BOIs Connector for Java

API for .NET BDEs or BOIs Connector for .NET

API for XML BOIs Connector for XML

ODBC driver N/A Connector for ODBC

JDBC driver N/A Connector for JDBC

Tools N/A N/A

For BDEs, the Connector for WBI consists not only of a client API, but also includes a listener for receiving BDE Event messages.

The following table lists the development environments for Infor business interfaces of the release:

Development time features

Business interface Framework

BOI Studio BOIs Microsoft.NET

Integration Studio BDEs Eclipse

Note

This release does not include the application-specific server adapters, such as the Adapter for ERP LN, Adapter for ERP LX, or Adapter for WMS. These adapters will be released in the context of the involved Infor enterprise application.

Installation

The installation procedure of Infor Integration is now more simple and straightforward. For more information, refer to the “Installation” chapter.

2-6 | Enhancements

Version information

In Infor Integration 6.1, we changed the version information. Infor introduces indicative version information that is used consistently throughout Infor Integration. The syntax of the version information is as follows:

<version number> <patch level> <build number>

In the previous release, Adapter Suite 2.7, for each build, a GUID was generated that identified the build, but it did not hold any sequential information. In the current release of Infor Integration, every new build increases the build number by one. Therefore, the first (beta) build carried build number 1, and the number of the build that will be released is, for example, 56.

Performance of Connectors for ODBC and JDBC

In Infor Integration version 6.1, performance of the Connector for ODBC and JDBC has been improved in several ways. One of these performance improvements consists of the option to run the Baan DB Driver (also known as the Enterprise Server DB Library) locally on the client. This option requires a client installation of a current ERP Baan/LN porting set.

If you use the Connector for ODBC or JDBC, you are recommended to use the option to run the Baan DB Driver locally on the client. For more information on this subject and for configuration details, refer to the Connector for ODBC online Help and the following installation guides:

Installation Guide for Connector for JDBC for Infor ERP LN (U9197C US)

Installation Guide for Connector for ODBC for Infor ERP LN (U9173C US)

Note

Outside the context of an Infor reporting solution, Infor does not support the use of a Connector for ODBC or Connector for JDBC anymore.

Support for Windows Vista

You can now install and run the software of Infor Integration 6.2 on Window Vista platforms.

Enhancements | 2-7

Support for Java 6

You can now run the software of Infor Integration 6.2 using JavaTM Platform, Standard Edition 6 (version number 1.6.x).

Extended .NET Client API The Audit functionality is ported to the .NET Client API of Infor Integration 6.2. The client software now is extended with a .NET wrapper interface for the Audit function on Infor ERP Baan back ends. The Audit function traces all activities that affect the specified database records from the time the record is entered into the database until the time the record is removed.

3 Chapter 3 Modifications

This chapter describes all of the changes, other than software improvements, described in the previous chapter. The enhancements include the removal of rarely used, obsolete, or insignificant components, as well as bug fixes and changes to the runtime functionality.

Removed components

With respect to Adapter Suite 2.7, the following components have been removed:

Connector for SOAP, for Web-enabled BOIs access

Connector for CORBA

Connector for OLE DB

For XML-based access to BOIs, use the Connector for XML. For SOAP-based, Web-enabled access to BOIs, use the previous Connector for SOAP of Adapter Suite 2.7. For SOAP-based, Web-enabled access to BDEs, use the current release of the Connector for Web Services.

3-2 | Modifications

Bug fixes

Infor Integration, version 6.1 and version 6.2, contain all of the bug fixes carried through in Adapter Suite 2.7.1 and 2.7.2.

Version 6.1

The bug fixes in release 6.1 solve the following problems:

Incorrect handling of double and datetime in the Connector for .NET

For optional fields, the getDouble() method returns an exception instead of the value 0.0. The getDateTime() method gives an exception when the datetime string ends with Z to indicate UTC.

Incorrect installation of shortcuts

The Start menu shortcuts are only installed for the current user. Other users cannot access these shortcuts.

Incorrect RequestProcessor object in Connector for XML

Calling the execute method on a RequestProcessor object does not work as expected.

Incorrect Logical Expression in .NET BDE Proxies runtime

A comparison expression and a logical expression cannot be combined in a logical expression.

Incorrect behavior of ODBC API in combination with MS Access

Using the ODBC API in combination with MS Access causes various types of errors.

Incorrect SOAP HTTP binding

The Connector for Web Services does not work through HTTP binding due to unmatched dependencies.

Version 6.2

The bug fixes in release 6.2 solve the following problems:

Modifications | 3-3

Open connections to MQ Series queues

If you use the JMS protocol from a Baan 4GL client, too many connections to MQ Series queues remain open, because they are not properly closed after a synchronize command.

.NET Client API generates OutOfMemoryError

When you use the Connector for .NET to transfer many objects, in some occasions, the Java VM can run out of memory.

.NET Client API fails to access a file-based configuration directory

A .NET client application with threads has problems accessing a file-based directory, which results in the following error: Initializing/loading of the directory failed. The logfile reports the following exception: ClassNotFoundException for class XmlCtxFactory.

No logging of very large XML documents

Infor Integration exchanges data between distributed enterprise application by sending XML documents back and forth. You can choose to include these XML documents (Bus Documents) in your logging file. When the XML documents become very large, Infor Integration runs out of memory and fails to log the XML documents.

This problem is fixed in the sense that very large XML documents are now logged until the moment that Infor Integration runs out of memory.

Multithreaded client applications using bidisockets

Multithreaded client applications that use bidirectional socket transport (bidisockets) can cause deadlocks or errors.

Activation instability

When a client application connects from multiple threads to Bus Component that is enabled for an activation service (for example APS activation) and closes the connection, this client application can experience NullPointerException errors.

Changed runtime functionality

With respect to the previous release, Adapter Suite 2.7, the BDE functionality changed significantly.

3-4 | Modifications

LDAP directory support

Infor Integration uses a central directory to store most of the runtime configuration data. This directory can be a flat data file or an LDAP-compliant directory service.

In previous versions (Adapter Suite 2.5 and earlier) a central directory was only used to store Bus Component properties. With respect to Adapter Suite 2.5, the configuration for the LDAP directory is now much simpler due to the representation of the configuration data as Java objects.

Infor Integration supports all LDAP-compliant directory services that can handle Java objects. This applies to Infor Integration 6.0 and later and Adapter Suite 2.6 and 2.7.

Note

Without extra adjustments, Microsoft Active Directory Service (ADS) cannot handle Java objects and can therefore no longer be used for storage of configuration data.

.NET 2.0 requirement

The .NET Client API (Connector for .NET) of Infor Integration 6.2 is based on .NET Framework 2.0. To use the API, you require this .NET version.

The .NET Client API of previous releases (Infor Integration 6.1 and earlier) were based on .NET Framework 1.1.

The Infor Integration 6.2 installer for Windows platforms automatically installs .NET Framework 2.0 if this software is not installed on your computer.

4 Chapter 4 Installation

This chapter describes the ways in which the installation procedure has been simplified.

Infor Integration simplified the installation procedure. Rather than use diverse installers to install various components, you can now simply use a single installer to install a single client-side software bundle. All server-side components of Infor Integration are shipped with the relevant Infor enterprise applications. The previous connectors and adapters are now represented as various features of Infor Integration.

For more information on how the software has been consolidated into a single, coherent package, refer to “Delivery” in the “Enhancements” chapter.

In the current release, you are not required to install various separate products in a specific order, each with unique peculiarities. You now install the client software of Infor Integration as a whole, with all of the functionality of Infor Integration. Which features are actually used is of later concern. If you install the client software with the installer, only one choice remains: you must either install the client runtime software and the BOI development software or install only the client runtime software.

For BDE-based integrations, the Infor Integration server-side software ships with the Infor enterprise application. This software will be available when you install a new Feature Pack and porting set for the relevant application.

For BOI-based integrations, you can obtain the Infor Integration software through a new porting set, Tools version, or PMC solution. However, you can also continue to use the application-specific adapters of Adapter Suite 2.7, such as Adapter 2.7 for Baan IV or Adapter 2.7 for Baan ERP.

4-2 | Installation

Server-side adapters

From Infor Integration 6.0 onwards, the application-specific adapters of Infor Integration are delivered as part of the Infor application to which they apply, including Infor ERP BaanIV, Infor ERP Baan5, Infor ERP LN, Infor ERP LX, and Infor WMS.

Adapters for ERP BaanIV, ERP Baan5, and ERP LN

The Adapters for ERP BaanIV, ERP Baan5, and ERP LN are delivered as part of the Infor Baan applications. The generic Java part of the adapter is included in the porting set or can be obtained through a PMC solution, and the application-specific part (tm package) is included in the Tools Module or in a PMC solution as well.

The following table shows how the adapters of Infor Integration will be released on Infor ERP BaanIV, Infor ERP Baan5 and Infor ERP LN application servers:

Infor Baan application

Generic Java part of Infor Integration Core

Application-specific Adapter

ERP BaanIVc Solution 212655 Solution 212655

ERP Baan5.0b, 5.0c

Porting set 7.1d + solution 212655 or Porting set 8.2b or later

Solution 212655

ERP Baan5.2a Porting set 8.2b or later

solution 212655 or Enterprise Server 8.3 + AddOn

ERP LN 6.1 FP2 and earlier Porting set 8.2b or later

solution 211731 or Enterprise Server 8.3 + AddOn

ERP LN 6.1 FP3 Porting set 8.3a or later Enterprise Server 8.3 or

8.4 + AddOn

ERP LN 6.1 FP4 Porting set 8.4b or later Enterprise Server 8.4 +

AddOn

This new delivery can lead to conflicts with existing installations of the adapter (version 2.6 and 2.7). An upgrade of Infor ERP Baan/LN to a porting set or PCM solution that contains Infor Integration 6.0 or later delivers ow.jar,

Installation | 4-3

ow3p.jar, and owconfig.properties files. These files are incompatible with pre-existing b3.jar and owxml.jar files of a previously installed adapter. Therefore, before you upgrade to Infor Integration 6.0 or later, you must remove the b3.jar and owxml.jar files from your ERP system.

Upgrades of Infor ERP LN to Enterprise Server AddOn version 8.3 or 8.4, delivers all of the Baan sessions and API of the adapter, such as tmboaserver and tmbdeserver.

Windows-only installer

Infor Integration has a single installer that you can use only for client Windows systems. The installer installs all of the client runtime features and BOI development features described previously. To install the software, simply follow the instructions on the install wizard. The only required input, if any, consists of the URL address of the directory that stores the runtime configuration data.

Important: The Infor Integration installer does not install Integration Studio (the Eclipse-based development environment for BDEs). To install Integration Studio you must retrieve the software from the Integration Studio update site at www.studio.ssaglobal.com.

On Windows platforms, the installer adds the following shortcuts to your Start menu:

BOI Test Tool

Central Configuration Console

Domain Explorer

Support Information Tool

Documentation (program folder)

Servers (program folder)

BOI Studio

4-4 | Installation

The Documentation program folder contains the following entries:

.NET Connector

BOI Test Tool

Java Connector

ODBC Connector

BOI Studio

The Servers program folder contains shortcuts to the following servers:

Server for .NET

Server for Java

Server for Baan DB

Manual installation

To install the client runtime software manually on non-Windows platforms, you must copy the Infor Integration software and add the relevant files to the classpath you use to run the software.

Integration Studio installation

To install Integration Studio, you must retrieve the software from the Integration Studio update site. You can download the required software from the following site:

www.studio.ssaglobal.com

The installation procedure consists of the following steps:

1 Install Eclipse and the add-on features. Prerequisites for Integration Studio include:

Eclipse Platform

Graphical Editing Framework

Eclipse Modeling Framework

2 Install the features on which the Integration Studio depends, which are:

SSA Framework License plug-in

SSA Framework Connectivity plug-in

Installation | 4-5

3 Install Integration Studio 6.1

The installation of all previous components conforms to the standard Eclipse feature installation. To update the Integration Studio features, in the Eclipse framework, on the Help menu, click Software Updates Find and Install, and follow the instructions of the Install/Update wizard.

For detailed information, refer to the Integration Studio's Installation page on the previous update site.

5 Chapter 5 Documentation

This chapter lists the current documentation of Infor Integration.

In the current release of Infor Integration, the documentation consists of online Help and the following guides on the media:

Administrator's and User's Guide for the Connector for Web Services (U9054 US)

Administrator's and User's Guide for Connector for XML (U9157 US)

Developer's Guide for BDEs for Infor ERP LN (U9066 US)

Developer's Guide for BOIs for Infor ERP BaanIV and Infor ERP Baan5 (U9165 US)

Installation Guide (U9018 US)

Installation Guide for Connector for JDBC for Infor ERP LN (U9197 US)

Installation Guide for Connector for ODBC for Infor ERP LN (U9173 US)

Integration Guide for BDE Clients (U9051 US)

Integration Guide for BOI Clients (U9145 US)

Release Notes (U9019 US)

System Administrator's Guide for Adapter for ERP LN (U9044 US)

System Administrator's Guide for Generic Runtime Components (U9042 US)

System Administrator's Guide for Java Message Services (U9050 US)

User's Guide for Connector for .NET (U9053 US)

5-2 | Documentation

User's Guide for Infor Integration Tools (U9052 US)

For reading guidelines and a summary of the content of each guide, refer to the Infor Integration Installation Guide.

The Infor Integration 6.2 Release Notes include the last-minute notes on Infor Integration 6.2. For the most current news on this Infor Integration release, such as fixes for reported defects, refer to solution 221761 at: http://onepoint.infor.com/Solutions/SearchBaanKB.aspx

The Infor Integration documentation has been reorganized. A concise Installation Guide describes the installation procedure of the client software. Most of the remaining documents are specific to a particular feature of Infor Integration. The System Administrator's Guides describe the configuration, management, and logging of the runtime components. User’s Guides describe how to use the various Infor Integration features.

6 Chapter 6 Troubleshooting

This chapter describes all of the known problems that relate to the Infor Integration software.

Adapters on ERP Baan and ERP LN back ends

If you encounter any problems running the java code of an adapter on an Infor ERP BaanIV, Infor ERP Baan5, or Infor ERP LN back end, refer to the technical notes of the involved porting set.

Integration Studio

In Integration Studio 6.1, all Interface resources are XML files that contain several ID attributes. These ID attributes represent identifiers. To prevent problems, these identifiers must be unique in the context of the entire Interface Project.

Problems can arise when you use multiple Interface Implementations (BIIs) that carry identical ID attributes. You will obtain two BIIs with distinct names but with identical IDs if you export a BII, rename the original BII, and import the same BII again. Therefore, if you want two similar BIIs, do not duplicate a BII by using this previous procedure. Instead, create both BIIs from scratch in the Interface Implementation editor.

6-2 | Troubleshooting

The identical BII IDs are caused by the following mechanism: if you rename an object in the Interface Explorer (by right-clicking Refactor and clicking Rename on the shortcut menu), the IDs used internally are not changed and still contain the former name. These earlier IDs are preserved during export and import operations.

Configuration directory

Infor Integration uses Java objects to store and manage the runtime configuration data of Infor Integration in a central LDAP-compliant directory. To store and manage the configuration data, Infor Integration uses (serialized) Java objects.

Without extra adjustments, Microsoft Active Directory Service (ADS) does not support Java objects and therefore cannot be used to store the configuration data of Infor Integration.