Skip to Content

Overview

ABAP Connectivity & Integration Tools aims at providing the following:

  • Enhance your integration experience by bringing together all the essential pieces (ABAP, Proxy, Enterprise Services Repository (ESR), Services Registry, Test & Debug environment) of integration development in one place
  • Build & deploy complex business integration scenarios with ease using a new set of simple yet powerful concepts and toolsets shipped with ABAP in Eclipse (AiE)

Typically, for an application, integration development is a three-staged process and ABAP Connectivity & Integration Tools brings in ease to all of them:

  • Define required enterprise artifacts/objects (Inbound Service Interface, Outbound Service Interface, Message Type, Data Type) in Enterprise Services Repository in a programming language independent format using Enterprise Service Development Tools.
  • Implement the interface definition as a Web Service (Service Provider or Service Consumer – known as Provider or Consumer Proxy respectively) in ABAP using ABAP Web Service Development Tools. However, this step is independent of ESR. You can create Web Services in ABAP directly from a WSDL file
  • Define abstract Integration Scenarios and link them with the generated/implemented ABAP Web Services artifacts using Scenario based Connectivity & Integration Tools.

ACIT Perspective.jpg

Figure: ABAP Connectivity & Integration Perspective is a set of tools for Enterprise Service Development, ABAP Web Service Development and Scenario based Connectivity & Integration Development

Technical Usecases

The following picture shows how these tools are interwoven to provide an end to end integration experience:

Technical Usecases.png

Enterprise Service Development Tools

Enterprise Service development tools (popularly known as Enterprise Services Repository Browser from the world of NetWeaver Developer Studio – Java) enables a developer define and store language independent enterprise objects in a central repository known as Enterprise Services Repository.

Enterprise Service Development Tools now are fully integrated within ABAP Development Tools for SAP NetWeaver, which means, you would now be able to create and manage your enterprise objects in Enterprise Services Repository straight from within your ABAP Development environment in Eclipse (ADT).

Service Interface Overview in ESR.jpg

Figure: Service Interface Overview in ESR from within ADT

Service Interface Definition in ESR.jpg

Figure: Service Interface Definition in ESR from within ADT

Message Type and Data Type Definition in ESR.jpg

Figure:Define Message Types and Data Types in ESR

Some of the activities performed by the developer using the Enterprise Service Development Tools are:

  • Create/Manage Inbound and Outbound Service Interfaces
  • Create/Manage Message Types
  • Create/Manage Data Types
  • Activate enterprise objects

ABAP Web Service Development Tools

  • Enterprise Service definition in ESR (Enterprise Services Repository) and its implementation in ABAP using ABAP Web Services artifacts – all in a single development environment
  • End-to-end ABAP Web Service development/implementation environment in AiE (from providing and configuring a service till consumption)
  • Test/Debug Web Services implementation instantly within the tool as you run through develop-test-fix-retest-deploy cycle
  • Quick configuration with integrated SOA Manager    
  • Integrated ESR & ABAP Services Registry

Service Provider.jpg

Figure:Service Provider

Service Consumer.jpg

Figure: Service Consumer

Some of the activities performed by the developer using the ABAP Web Service Development Tools are:

  • Generate Service Provider/Service Consumer artifacts (known as proxy objects) from various sources (ESR, Services Registry, WSDL, RFC)
  • Implement business logic in Service Provider proxy
  • Implement consumption logic in Service Consumer proxy
  • Test/Debug Service logic using in-built test cockpit and debugger
  • Configure service using integrated SOA Manager

Scenario based Connectivity & Integration Tools

  • Easy to use drag & drop based graphical tools to define integration scenario
  • Pure business semantics – defining an integration scenario and its configuration is completely abstracted from the scenario’s technical realization
  • Consistent configuration of complete scenario in one step
  • Business Administrator needs only to know business relevant information to setup a scenario
  • Business scenario configuration is unaffected by the changes in the underlying physical systems

At configuration time, the administrator will select an integration scenario definition and assign business entities to the semantically described interacting parties to get a fully automatic configuration of all of the involved connections.

Integration Scenario Definition.jpg

Figure: A hypothetical Integration Scenario Definition

  

References

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Kristian Weissmann

    Very Nice! This is a feature It think many of us were waiting for. The tool hopping from ESR-Builder to SPROXY to SOAMANAGER really has an end! Still can’t believe it ๐Ÿ™‚

    Can you please tell what are the system requirements for:

    * ESR providing system (will be a PO installation for us).

    * Proxy implementing system (erp etc)

    * else?

    Compared to the SIW precedure – what does

    Implement business logic in Service Provider proxy

    mean? Is there an automated mapping from Service Interface to the “Implementation Destination” (e.g. RFC) like with SIW or is this task a manual one like the ABAP-Proxy – Contract First approach?

    Thanks!

    Kristian

    (0) 

Leave a Reply