AZURE Adapter For SAP NetWeaver® PI/PO

 

 

AZURE Adapter - Overview

Microsoft Azure is a growing collection of integrated cloud services that developers and IT professionals use to build, deploy, and manage applications through our global network of datacenters.

The Advantco PI/PO AZURE Adapter is for business users looking for an out-of-the box, SAP integrated solution to connect with Microsoft Azure.

The adapter streamlines the exchange of data with the Integration Server or the PCK by means of Blob Storage, Queue Storage, File Storage, Service Bus Queue, Service Bus Topic, Data Lake Store, …

Contact us for more information and to arrange a demonstration or free trial here.  

AZURE Adapter – Key Features

Supported services:

-Blob Storage.

-Queue Storage.

-File Storage Service Bus Queue.

-Service Bus Topic.

-Data Lake Store

Support SSL/TLS authentication.

Duplicate handling to avoid duplicate message

Successfully Processed Message Handling.

Minimize cost while receiving new messages as quickly as possible through long polling.

Flexible Conversion between Plain, JSON and XML Formats.

Full Integration with Integration Platforms:

-SAP NetWeaver PI/PO.

AZURE Adapter – Summary of Features

01. Connection to Blob Storage via specific container using AZURE credential (Connection String or Define Explicit).

02. AZURE adapter supports SSL/TLS Authentication which is server side.

03. Query objects using prefix name.

04. Duplicate handling. In order to prevent the adapter from processing the same resource entities again.

05. Successfully Processed Message Handling. AZURE adapter can delete the message from the storage after receiving and processing it.

06. Retry Failed Block Operation to handle failed block during uploading to Microsoft Azure.

07. Adapter-specific message attributes (ASMAs) configuration is for creating dynamic configurations in PI message header.

08. Content conversion is for converting main message payload between Plain, JSON and XML formats.

09. Variable substitution is used to build dynamic request.

10. Standard Inbound Processing Options

- Quality of Service (Exactly Once, Exactly Once In Order, Best Effort).

- Polling Interval.

AZURE Adapter – Blob Storage

01. Connection to Queue Storage via specific queue using AZURE credential (Connection String or Define Explicit).

02. AZURE adapter supports SSL/TLS Authentication which is server side.

03. Duplicate handling. In order to prevent the adapter from processing the same resource entities again.

04. Successfully Processed Message Handling. AZURE adapter can delete the message from the storage after receiving and processing it.

05. Adapter-specific message attributes (ASMAs) configuration is for creating dynamic configurations in PI message header.

06. Content conversion is for converting main message payload between Plain, JSON and XML formats.

07. Variable substitution is used to build dynamic request.

08. Standard Inbound Processing Options

- Quality of Service (Exactly Once, Exactly Once In Order, Best Effort).

- Polling Interval.

AZURE Adapter – Queue Storage

01. Connection to File Storage via specific share using AZURE credential (Connection String or Define Explicit).

02. AZURE adapter supports SSL/TLS Authentication which is server side.

03. Query files using prefix name.

04. Duplicate handling. In order to prevent the adapter from processing the same resource entities again.

05. Successfully Processed Message Handling.AZURE adapter can delete/copy/cut the message from/to the storage after receiving and processing

06. Adapter-specific message attributes (ASMAs) configuration is for creating dynamic configurations in PI message header.

07. Content conversion is for converting main message payload between Plain, JSON and XML formats.

08. Variable substitution is used to build dynamic request.

09. Standard Inbound Processing Options

- Quality of Service (Exactly Once, Exactly Once In Order, Best Effort).

- Polling Interval.

AZURE Adapter – File Storage

01. Connection to Service Bus Queue via specific queue using AZURE credential (Connection String or Define Explicit).

02. AZURE adapter supports SSL/TLS Authentication which is server side.

03. Duplicate handling. In order to prevent the adapter from processing the same resource entities again.

04. Successfully Processed Message Handling. AZURE adapter can delete the message from the queue after receiving and processing it.

05. Adapter-specific message attributes (ASMAs) configuration is for creating dynamic configurations in PI message header.

06.Content conversion is for converting main message payload between Plain, JSON and XML formats.

07. Variable substitution is used to build dynamic request.

08. Standard Inbound Processing Options

- Quality of Service (Exactly Once, Exactly Once In Order, Best Effort).

- Polling Interval.

AZURE Adapter – Service Bus Queue

01. Connection to Service Bus Queue via specific queue using AZURE credential (Connection String or Define Explicit).

02. AZURE adapter supports SSL/TLS Authentication which is server side.

03. Duplicate handling. In order to prevent the adapter from processing the same resource entities again.

04. Successfully Processed Message Handling. AZURE adapter can delete the message from the queue after receiving and
processing it.

05. Adapter-specific message attributes (ASMAs) configuration is for creating dynamic configurations in PI message header.

06. Content conversion is for converting main message payload between Plain, JSON and XML formats.

07. Variable substitution is used to build dynamic request.

08. Standard Inbound Processing Options

- Quality of Service (Exactly Once, Exactly Once In Order, Best Effort).

- Polling Interval.

AZURE Adapter – Service Bus Topic

01. Connection to Service Bus Topic via specific topic/subscription using AZURE credential (Connection String or Define Explicit).

02. AZURE adapter supports SSL/TLS Authentication which is server side.

03. Duplicate handling. In order to prevent the adapter from processing the same resource entities again.

04. Successfully Processed Message Handling. AZURE adapter can delete the message from the topic after receiving and processing it.

05. Adapter-specific message attributes (ASMAs) configuration is for creating dynamic configurations in PI message header.

06. Content conversion is for converting main message payload between Plain, JSON and XML formats.

07. Variable substitution is used to build dynamic request.

08. Standard Inbound Processing Options

- Quality of Service (Exactly Once, Exactly Once In Order, Best Effort).

- Polling Interval.

AZURE Adapter – Data Lake Store

01. Connection to Data Lake Store via specific store using AZURE credential (OAuth 2.0).

02. AZURE adapter supports SSL/TLS Authentication which is server side.

03. List objects from source directory.

04. Duplicate handling. In order to prevent the adapter from processing the same resource entities again.

05. Successfully Processed Message Handling. AZURE adapter can delete the message from the data lake store after receiving and processing it.

06. Adapter-specific message attributes (ASMAs) configuration is for creating dynamic configurations in PI message header.

07. Content conversion is for converting main message payload between Plain, JSON and XML formats.

08. Variable substitution is used to build dynamic request.

09. Standard Inbound Processing Options

- Quality of Service (Exactly Once, Exactly Once In Order, Best Effort).

- Polling Interval.