Show TOC

Function documentationOData

 

You use this action to call Odata service from SAP MII.

Features

The properties for this action are listed in the following table:

Property

Data Type

Access

Description

URL

String

In and Out

The URL for the OData service to be called.

Base URL

String

In and Out

Used to get XSRF id.

Document to Post

String

In and Out

The document to be posted. You load the document or retrieve it from another location, link it to the property through the Link Editor screen, and then post it.

Method

String

In and Out

Choose any HTTP method from the value help.

Content Type

String

In and Out

Dependent on the document and what the receiving URL expects. The default is application/x-www-form-urlencoded.

Encoding

String

In and Out

The default value is UTF-8.

Response Timeout in Seconds

Integer

Controls the amount of time (in seconds) the action waits for a response from the load request.

Use Destination Services

Boolean

In

Forces post calls to use the destination service. The Http destination with the name XMIISSO configured in Netweaver Java server is used to make the connection. This configures the action for basic authentication and HTTPS. However, the destination service may have problems connecting to servers through proxy.

For more details, see Maintaining HTTP Destinations in the SAP Help Portal at Start of the navigation path http://help.sap.comInformation published on SAP site Next navigation step Technology Platform Next navigation step SAP NetWeaver Next navigation step SAP NetWeaver 7.3 Including Enhancement Package 1 Next navigation step Application Help End of the navigation path.

Posting to PI

Boolean

In

Indicates that the destination is a PI server and checks if you are posting data to a PI server. If true, you can send empty URL parameters.

OData Service Type

String

In and Out

Choose one of the following service:

  • MII Service

  • NetWeaver Gateway Service

    For the above services, if the HTTP method is POST, PUT, or DELETE, the CSRF token is first retrieved using the base URL, then used in the actual Odata request.

  • Other

    On selecting this service, you can retrieve the CSRF token and provide additional configuration to get the token from response header or cookie. The checkbox Check Cross Site Forgery is enabled which gets the CSRF token before calling the Odata service.

CSRF URL Parameter

String

In and Out

Gets CSRF token parameter and value and is appended to base URL

Check CSRF Token In

String

In and Out

Retrieves CSRF token from response header or cookie

Response Token ID

String

In and Out

Retrieves name of the CSRF response token from response header or cookie