The mobile terminated and originated message flows may use the OneAPI.
A Web application may access common telecom functionalities using OneAPI. For example, a OneAPI call can be made from a Dojo widget. The address and message fields are sent as part of the HTTPHeader. Two new export components have been introduced for each of the supported interfaces, one for the XML content-type and another for JSON.
A custom handler configured in the export component converts the message from native HTTP form data into an SDO for handling a request. Likewise, it is converted from an SDO into a minimal XML string (as specified by the OneAPI specification v0.9) for handling the response. The SCA HTTP binding was introduced in WebSphere® Integration Developer version 6.1.
A function selector determines what operation to call on an export interface. When the HTTP export receives a request message, it uses the function selector to determine the method name that it needs to invoke on the interface based on the HTTP request information.
Notification type operations, such as notifySmsReception, are implemented on the application side. In this case, the notification message passes through the import component SMS_OneAPIImport. An SCA HTTP import binding enables SCA applications (that is, Access Gateway flows), to invoke external services directly over HTTP. This import component is responsible for transforming the data from SDO to the native HTTP formatted message at the application side, implemented as per OneAPI specifications.
Since there are now two new import components implementing the same interface, a routing decision must be made in case the message is intended for the OneAPI import. Therefore, if either of the two new Notification flow imports is used, you must configure a new policy in the Policy Manager. This policy, notification.Endpoint.Type, accepts the string value.
If the string value is set to OneAPI, the message is routed to the callout corresponding to the SMS_OneAPIImport. If the value is set to JSON, the message is routed to the callout corresponding to SMS_JSONImport. If this policy is not set or if the value does not correspond to either of the above two values, the message routing defaults to the existing Web service import.