Home » iWay OAGIS XML eBusiness Adapter

iWay OAGIS XML eBusiness Adapter

The Open Applications Group Integration Specification (OAGIS) includes a broad set of Business Object Documents (BODs) and integration scenarios that can be used in different business environments. BODs are message definitions that can be used broadly across many different industries (e.g., telecommunications and automotive) and aspects of Supply Chain Automation (Ordering, Catalog Exchange, Quotes, etc.). OAGI also defines the OAMAS (Open Application Middleware API Specification), which is an application programming interface (API) for application integration that provides an abstraction from specific vendor solutions. Like ebXML, this standard covers many areas and appears to be one of the most widely adopted and supported standards. The OAGIS is developed independently of the underlying technical framework used to route and deliver the information. The messages defined as a part of the Open Applications Group content are designed for use by business applications. OAG BODs are incorporated into B2B frameworks such as ebXML and BizTalk Framework.

How It Works

iWay provides support for over 200 OAG BODs in the iWay Service Manager. These XML templates provide automated pre-built transforms from OAG BODs to Oracle Applications interface tables, SAP IDocs, PeopleSoft Component Interfaces, and other non XML formats. The iWay Service Manager provides formatting from OAG BOD XML applications into a iWay XML format allowing OAG BOD interfaces on remote platforms (e.g., SAP Procurement running on OS/390) to be easily integrated into application servers and message brokers. Once the iWay Service Manager formats the interface as iWay XML, the developer can use message brokers without having to write any custom mapping code. Supported environments include IBM WebSphere, IBM WebSphere MQ Integrator, Microsoft BizTalk Server, Microsoft Commerce Server, Oracle 9iAS, and Oracle 9iAS InterConnect.

Adapter Benefits

The iWay Adapter technologies offer developers these advantages:

  • Rapid creation and integration of B2B transactions using XML or non-XML EDI formats such as ANSI X.12, UN/EDIFACT, and SWIFT
  • Extend packaged and e-business applications systems based on Java, XML, SOAP, and Web Services without requiring any custom coding
  • Reduce the cost in extending packaged applications into a B2B trading partner management based on standards such as ebXML and Web Services
  • Provide a common development environment integrated inside of multiple message brokers and application servers
  • Uniform XML Interface for all packaged applications, thus reducing the requirement for specific packaged applications native API knowledge
  • Bidirectional adapter functionality to automate integrated event-driven input capability to integrate real-time transactions
  • Document conversion from proprietary XML to standard XML, EDI formats, SQL, and RPCs to other application systems
  • Protects investment in legacy databases, ERP, CRM, SCM, and homegrown "legacy" applications modules