iWay .NET Technology Adapter User's Guide > Introducing the iWay .NET Technology Adapter > Overview

Overview

Topics:

The iWay .NET Technology Adapter enables .NET developers to create integration endpoints using their familiar design language or to reuse existing endpoints. Code written in a source language, such as Visual C# or Visual Basic .NET, that complies into Common Language Infrastructure (CLI) code can be interpreted and the methods invoked from Java executables. The CLI code runs in an instance of the Common Language Runtime (CLR) and data can be passed through the adapter in either direction (inbound or outbound.

This version of the adapter introduces support for constructors, sessions, and database connections. In addition, enhanced metadata capabilities are provided.

iWay .NET Technology Adapter is designed to work with method calls contained in .NET assemblies. The source code input is not used only the Common Intermediate Language (CIL).

The adapter has been tested with .NET framework runtime 3.5, 4.0 and 4.5 on Windows client and server machines. No other platforms are currently supported.

While the new enhancements open new areas of the .NET framework to use with the adapter, some parts of the framework remain out of scope and are explicitly not supported:

Do not use any class types that attempt to use Application environment variables. They will return the iway_home directory and not the expected assembly. All Assembly environment variables function as documented.

Known Issues and Limitations

For more information on supported functionality, usage considerations, known issues and limitations, see Known Issues and Limitations.

Defining and Understanding User Proficiency Levels

There are three different user levels that should be considered when using the iWay .NET Technology Adapter:

  • Basic User. Performs beginner-level tasks and runs (explores) only specific Assemblies. Basic user tasks include locating Assemblies through iWay Explorer, creating XML schemas, retrieving data, creating XML instances, and executing XML request documents. The types of tasks that can be expected from a basic user are described in Design Time Concepts and Configuration Tasks.
  • Development User. Creates integration based on existing Assemblies. Explores multiple Assemblies, understands parameters, return types, connections, and is comfortable using these objects without a guide. This user has a more detailed understanding of parameter types and how they appear in iWay Explorer, what objects can be exposed through XML, and what can be exposed only by a program (writing an agent). The types of tasks that can be expected from a basic user are described in Design Time Concepts and Configuration Tasks and Run Time Concepts and Configuration Tasks.
  • Professional Developer. Creates new code and develops integration. Develops .NET programs or Java programs and understands more about how to design for the adapter. Usage and knowledge of terms such as protected, private, public, declarations, and other terms are mandatory for this type of user. All of the topics and tasks in this documentation would be applicable to a professional developer.

Understanding these types of users and their specific roles can help define the expected usage scope for the iWay .NET Technology Adapter and its implementation in your organization.