Ums Adapter

3/8/12
O acle Re ie
UMS Adapter : Functional Specification Review

Document: UMSAdapterFunctionalSpec.odt
Documents
Properties
Show : Open/Fixed
Members
Options
search
Wednesday, March 7, 2012 10:23:56 PM PST
1 - 36
Functional Specification for Oracle UMS Adapter,

SOA 12C
37
Project ID: UMS Adapter

Version: 18 Ma 2009
Status: Review Draft
Author: Sagar Shirguppi
Project Manager: Srimant.Misra@oracle.com
Document Control
Document Change History

Date
Author
Version Change Description
23-M ay-09
Sagar Shirguppi
0.2
Initial Draft
03-Jun-09
Sagar Shirguppi
0.4
Added UM S related details.
04-Jun-09
Sagar Shirguppi
0.6
User Interface details to design the Adapter service.
30-Jun-09
Sagar Shirguppi
0.7
Incorporated Srimant's feedback
07/13/09
Sagar Shirguppi
0.8
Incorporated Kalpak s feedback
10/11/10
Sagar Shirguppi
0.9
David Li Feedback
Contributors
Name
Organization
Title
Kalpak Kothari
UM S
Development M anager
Patrick Vinograd
UM S
PM TS
Srimant M isra
ST
Development M anager
Reviewers
Name
e ie .
Role
.o acle.com/ e ie /p in able- ie .do
Title
Date Reviewed
1/47
3/8/12
O acle Re ie
Vikas Anand
PM
Principal Product M anager
Kalpak Kothari
Dev M anager
Srimant M isra
Dev M anager
David Li
PM TS
Document References
Document Title
Type of Reference
Document Location
Bugs: 8213748
Bugs
here
Table of Contents
Document Control 1
Document Change History 1
Contributors 1
Reviewers 1
Document References 2
1 Project Overview 3
1.1 Problem/Need Statement 3
1.2 High Level Requirements 3
1.3 Assumptions and Constraints 4
1.4 Features Scoped Out or Deferred to a Future Release. 4
2 Concepts & Terminology 4
3 Requirements 4
3.1 Functionality 5
3.1.1 Inbound Receive Notification (Email, SMS, IM) - Polling or through a Listener. 5
.
.
3.1.1.1 Email Driver Configuration on UMS side. 6

3.1.1.2 Design Adapter Service and the BPEL Process. 6
3.1.1.3 Message Mapping 17

3.1.1.4 Connection Factory Properties 19
3.1.1.5 Activation Specification Properties 19
3.1.1.6 Endpoint Properties 20
3.1.1.7 Normalized Message Properties 20
3.1.1.8 Receive Mode Polling Vs Listener 23
3.1.1.9 Inbound Polling Semantics 23
3.1.1.10 Inbound Listener Semantics 24
3.1.1.11 Transaction Semantics 24
3.1.1.12 Inbound Error Handling 26
3.1.1.13 Attachment Handling 26
3.1.2 Inbound Receive Notification in a Cluster (Polling or through a Listener) 27
3.1.3 Inbound In with SSL to communicate with IMAP/POP3 server 27
3.1.4 Outbound Send Notification (Email, SMS, IM, Voice) 28
.
.
3.1.4.1 Email Driver Configuration on UMS side. 28

3.1.4.2 Design the Adapter Service and BPEL Process. 28
3.1.4.3 Message Mapping 37
3.1.4.4 Interaction Specification Properties 39
3.1.4.5 Normalized Message Properties Outbound 40
3.1.4.6 Endpoint Properties 40
3.1.4.7 Connection Factory Properties 40
3.1.4.8 Transaction Semantics on the Outbound 40

3.1.4.9 Outbound Error Handling 41
3.1.4.10 Retry Mechanism for Failed Outgoing Notifications with status reporting 41
3.1.5 Outbound Send with TLS (SSL) to communicate with the SMTP server 41
e ie .
2/47
3/8/12
O acle Re ie
4 Client Interfaces 42
4.1 Task Analysis, Roles, and Use Cases 42
4.1.1 HP 42
4.1.2 Rabobank 43
4.1.3 B2B Requirements 45
5 Other Design Considerations 46
5.1 Scalability/Availability 46
5.2 Deployment and Life Cycle 46
5.3 API & Libraries 46
5.4 Extensibility 46
Project Overview
This document captures the requirements/functionality for a JCA compliant UMS (User Messaging Service) Adapter.
Adapter will wrap User Messaging Service allowing business workflow to subscribe to different delivery channels as
Email, SMS and IM. Adapter will act as a proxy between SOA Suite and the external world and will be capable of acting
as a Provider or as a Consumer.
1.1
Problem/Need Statement
In the enterprise world, Email is the main communication option between Business to Business and it is very
important to have this along with other messaging channels like SMS, IM and Voice integrated into the SOA suite.
UMS (User Messaging Service) is a Fusion Middleware component, which provides services to send/receive
notifications/alerts through various messaging channels as Email, SMS, IM, and Voice.
Currently under SOA suite we have Human Workflow and notification agents, which use UMS to send/receive
notifications. But apparently these use cases are more human centric. There is a need for a JCA Adapter that can be
used to realize some of the use cases, which are more data centric. For example kicking a workflow with a new mail
in the inbox, along with filtering, transforming or formatting based on certain business requirements.
Again, main advantages with JCA based adapter are,
1.
Being part of the adapter stack, UMS Adapter will by default be available to the Mediator service engine
too. Currently there is no way under Mediator to consume or reference messaging channels such as Email,
SMS etc.
2.
With standard life cycle and work management contracts, adapter will be able to provide a controlled runtime environment along with monitoring capabilities.
3.
4.
Standard Error handling capabilities like rejection handling and fault policies for exception conditions.
With well defined transaction contract for JCA adapters, adapter would be able to participate in the
distributed transactions.
1.2
High Level Requirements

1.
The requirement is to have a generic, comprehensive JCA based UMS Adapter.
2.
The Adapter should act as a Service Consumer as well as Provider.
3.
The Adapter should provide support for different messaging channels such Email, Voice, IM, SMS etc.
Should be supporting popular protocols such as SMTP, IMAP, POP, SMPP and XMPP.
4.
5.
The Adapter Should support SSL for Email channel.

The Adapter should implement JCA Interface and thus be able to seamlessly integrate with SOA
Applications.
6.
7.
The Adapter should be integrated with Translator Infrastructure (NXSD).

The Adapter should be able to send/receive notifications/alerts with message bodies of multiple parts,
format of which might be described by different MIME types.
8.
The Adapter should be able to provide status information from messaging gateways along with retrying
capabilities for failed messages.
9.
The Adapter should be able to participate in the global transactions with various participants, for inbound
and outbound scenarios.
e ie .
3/47
3/8/12
O acle Re ie
1.3
Assumptions and Constraints

1.
.
UMS POJO Client API. We have it starting from PS2.

XA Transaction support from UMS (This has been added as a requirement for 12c. A360 requirement
557827: Ability for UMS to participate in an XA transaction)
Parameterized synchronous receive call in case of synchronous receiving of messages from UMS. Note A360 requirement 557688: Throttling to control the number of inbound messages to be delivered.
1.4
Features Scoped Out or Deferred to a Future Release.

1.
Multiple Payload Support - Delivery Channel Specific Payload in single message for recipients with different
delivery types, available under UMS.
2.
Translation support for more than one body parts, in case of a Multipart message.
3.
Support for specifying the body part index to carry out translation on that particular body part, in case of a
Multipart message.
Concepts & Terminology

1.
JCA Java Connector Architecture
2.
SMTP Simple Mail Transfer Protocol is an Internet Standard for electronic mail (email) transmission across
Internet Protocol (IP) networks.
3.
IMAP Internet Message Access Protocol is one of the most prevalent Internet Standard protocol for e-mail
retrieval from a remote mail server.
4.
POP Post Office Protocol is too a well known Internet Standard protocol used by email clients to access
email from mail server.
5.
SMPP Short Message Peer-To-Peer protocol is a telecommunication protocol for exchanging SMS messages
between peer entities such as Short Message Service Centers and/or External Short Messaging Entities.
6.
XMPP Extensible Messaging and Presence Protocol is an open standard communication protocol for
message-oriented middleware based on XML.
7.
8.
SSL Secure Socket Layer

S/MIME Secure/Multipurpose Internet Mail Extensions is a standard for public key encryption and signing
of MIME data.
Requirements
1.
Support for Inbound Communication

1.
JCA 1-way Inbound Interaction Asynchronous publishing of message notifications from UMS(Email, SMS
and IM Channel)
2.
Adapter should be able to asynchronously receive messages/notifications from UMS. In this case the
adapter will register a POJO listener with UMS for callbacks. User should be able to specify number of listener
threads.
3.
Adapter should also be able to poll UMS for any messages/notifications with a predefined polling interval to
retrieve available messages. For example poll for any new messages on a certain email inbox and fetch them
as and when available. User should be able to specify the polling interval and number of polling threads.
4.
5.
A single adapter endpoint should be able to receive messages from one or more inboxes.
With synchronous receive (polling mode), adapter should be able to receive and acknowledge received
messages, thus should make use of reliable messaging support from UMS to ensure no message loss.
6.
Adapter should be able to receive messages with subject, body and one or more attachments (multipart
messages with different mime types) if available.
7.
If the user chooses Email as the message delivery channel, the adapter should be able to retrieve emails
from IMAP/POP3 servers supporting SSL. (This support is already available with UMS)
8.
Adapter should make use of Message Filtering Support given by UMS for selective receive of incoming
messages. This also involves user preference based messaging support given by UMS, where user can pass
business terms along with facts or values for the same as message metadata. The same can then be used
afterwards for the message filtering.
9.
Adapter should give a Java Callout Option to the user, to execute certain custom logic before processing
the message (this would be after receiving the message from UMS).
2.
Support for Outbound Communication

1.
e ie .
JCA 2-way outbound interaction with message notification as request and response as a unique message id
4/47
3/8/12
O acle Re ie
received from UMS server after accepting the notification.

2.
User optionally should be able to opt for JCA 1-way outbound interaction, when he is not interested in
getting the message id from UMS.
3.
Adapter should be able to send messages/notifications to the external world through Email, IM, SMS and
Voice messaging channel.
4.
Adapter should be able to send notifications/alerts with subject, body and one or more attachments
(multipart messages with different mime types) if available.
5.
Adapter should give an option to send email as an attachment.
6.
SSL support while sending emails. (This support is already available with UMS)
7.
Adapter should be able to send notification to multiple recipients.
8.
User should be able to add proprietary mail headers to an outgoing message.
9.
User should be able to set message metadata (user preference based messaging support from UMS) for
outgoing messages.
3.
Fault Handling/Error Hospital

1.
Support for fault-policy/fault-bindings for inbound and outbound.

i.
Message Rejection
1.
For any errors in translation the adapter should use Rejection Mechanism.
2.
Rejection Mechanism also should be used for bad messages; that is, incoming messages
which fail on Java Callout check. This will work as an error hospital for bad messages.
2.
Outbound Retries
i.
Support for retry logic for outbound interactions through fault-policies.
ii.
3.
Retry logic for outbound interactions through JCA retry mechanism.
Status reporting (get status information from the messaging gateways) and automatic retries, depending
on the status received.
4.
Transaction Support
1.
Adapter should be capable of taking part in the distributed transactions for both inbound and outbound
scenarios.
5.
Translation Support
1.
Adapter should be able to translate between XML and native forms of messages according the predefined
message schema.
2.
Translation support for only one body part of the message. For a Multipart/alternative message, it always
will be the first body part with inline disposition.
3.1
Functionality
3.1.1
Inbound Receive Notification (Email, SMS, IM) - Polling or through a Listener.

In this scenario, as part of inbound activation, UMS Adapter will register an access point on the UMS Server to
consume incoming notifications. Adapter will either poll or register a listener with UMS to get notifications. With a
notification received, adapter will pick up the message and will publish it to Adapter Binding Component (first inline
body part translated as per the schema defined), which will kick-start the composite scenario. This is a one-way
operation.
Designing this service involves two main parts
3.1.1.1
Configuration on the UMS Server side to setup access points for receiving notifications.
Designing the Adapter Service and BPEL process.
Email Driver Configuration on UMS side.
On the UMS side, administrator needs to configure the Email driver from Enterprise Manager (EM) Fusion Middleware
Console, as below.
e ie .
5/47
3/8/12
O acle Re ie
Following are some of the custom email driver properties user needs to configure under Driver-Specific Configuration
for UMS.
1
IncomingMailServer - Host Name of incoming mail server - stbeehive.oracle.com
IncomingMailServerPort - Port Number of IMAP4
IncomingMailIDs - The e-mail addresses corresponding to the user names. - first.last@oracle.com
IncomingUserIDs - user names of the mail accounts the driver instance is polling from UserName
IncomingUserPasswords - passwords corresponding to the user names.
ReceiveFolder - The name of the folder drive should poll messages for INBOX Email Driver Configuration on
UMS side.
For details on configuring SMPP, XMPP driver, please check UMS Admin Guide.
3.1.1.2
Design Adapter Service and the BPEL Process.

38
User would be using UMS Adapter Configuration wizard under JDeveloper to design the inbound adapter service
as shown below.
1.
e ie .
User enters ReceiveNotification in the Service Name Field as shown below.
6/47
3/8/12
O acle Re ie
2.
User enters the JNDI name for the UMS Adapter Connection.
3.
Selects Inbound Receive Notification as the operation type.

a.
39
Depending on how he wants receive messages from UMS, user selects either Polling Mode or
Listener Mode
e ie .
7/47
3/8/12
O acle Re ie
b.
Operation mode details like polling frequency would be displayed only when user selects inbound
operation.
c.
Polling frequency units would be seconds, minutes, hours, days and weeks. Units other than seconds
will be converted into seconds by the UI wizard while setting value for the polling frequency activation
spec property value.
4.
Configures the end point attributes after selecting the type of Notification as Email, SMS, Or IM.
40
For
instance, selecting Email, users enters other attribute details as one or more incoming mail addresses.
In case of SMS, recipient address would be a mobile number. User also can specify a mobile number
range, e.g. 16501230000, 16501234999 means all numbers from 16501230000 to 16501234999 (inclusive).
In case of IM, it would be instant messaging ids e.g. jabber| rita.miller@oracle.com.
e ie .
8/47
3/8/12
O acle Re ie
5.
On the Messages Page, user enters message related details.

a.
If user needs the message payload (first body part of a multipart message with inline disposition)
to be translated as per certain schema, user enters the schema details, which defines the incoming
notification body content, as shown below. He can use the Native Format builder to define the
Schema for native formats. Note that the message schema specified here just defines the body
content.
e ie .
b.
For simple text type payload, user can check the option Message is String type .
c.
If message payload is opaque, user can opt for Message is Opaque (Base64Binary) option.
d.
For above two options, user need not specify any schema details.
9/47
3/8/12
O acle Re ie
e.
Unlike other adapters, UMS Adapter will use a predefined Message Schema to represent the
message. Check out the predefined message schema for UMS Adapter under Appendix section.
f.
The schema defined by user according to his translation requirement (on the message page above,
for the message body content) would be imported into the predefined message schema used by the
UMS Adapter. Check out the schema snippet shown below where the user defined schema
singleString.xsd is imported and it refers to the element singleString, which is defined under
singleString.xsd.
Content Type defined under UMS.xsd
<
:
<
T
:
="ContentType">
>
<
<
:
<
="impl:singleString"/>
="attachment">
:
<
:
<
>
>
="Attachment"
="AttachmentType"
O
="0"
="unbounded"/>
</
</
</
</
</
>
T
>
>
>
>
Singletring.xsd which defines native schema
<
F
F
N
="unqualified"
="qualified"
="http://xmlns.oracle.com/singleString"
="http://www.w3.org/2001/XMLSchema">
<
e ie .
="singleString">
10/47
3/8/12
O acle Re ie
<
>
<
>
<
</
</
</
</
="input"
="string"/>
>
T
>
>
>
g.
If user opts for Message is opaque (Base64Binary) option, wizard will directly add an element of
type base64Binary (payload definition) to the static schema as shown below.
Message is Opaque (Base 4Binary)
<
:
<
T
:
="MessageType">
>
<
<
:
<
="payload"
="base64Binary"/>
="attachment">
:
<
:
<
>
>
="Attachment"
="AttachmentType"
O
O
="0"
="unbounded"/>
</
</
</
</
</
h.
>
T
>
>
>
T
>
If user opts for Message is String Type option, wizard will add an element of type xsd: string
(payload definition) to the static schema as shown below.
Message is String Type
<
T
<
="MessageType">
>
<
<
:
<
="payload"
="xsd:string"/>
="attachment">
:
<
:
<
>
>
="Attachment"
="AttachmentType"
O
O
="unbounded"/>
</
</
</
</
</
6.
41 - 43
="0"
>
T
>
>
>
>
On the Filters page, user specifies filter expressions to filter out incoming messages. A Message
Filter contains a matching criterion and an action. User can register a series of message filters. They will be
applied in order against an incoming (received) message; if the criterion matches the message, the action is
taken. For example, user can use Message Filters to implement necessary blacklists, by rejecting all
messages from a given sender address. User can specify three different types of filters.
a.
Blacklist Filter blacklist filters match against an incoming message's sender address, and rejects
the message if the sender address matches the given pattern. A pattern is a Java Pattern. (A regular
expression)
e ie .
11/47
3/8/12
O acle Re ie
b.
Whitelist Filter Whitelist filters match against an incoming message's sender address and
accepts the message if the sender address matches the given pattern (Java Pattern).
c.
Message Filter A message filters matches against any of the given fields below with a given
pattern and accepts or rejects the messages depending upon the action specified by the user.
i.
CONTENT
ii.
HEADER
iii.
iv.
e.
METADATA
v.
REPLYTO
vi.
SENDER
vii.
d.
44
RECIPIENT
SUBJECT
There are only two types of Actions, ACCEPT or REJECT the message.
Message Filters are applied in the same order in which user defines them on the Message Filter
page, as shown below.
[Note: If field value is HEADER or METADATA, field name will determine which header or meta data entry
to match against. In case of HEADER, field name will be any of the header field name defined by RFC 5322
Internet Message Format. Please check Table I Message Headers for exact header names. UI screen should
by default show all of these names in the Field Name combo box, if user selects field type as HEADER.
Now regarding METADATA, UMS allows sending facts (values) for various business terms as message
metadata (Please check Chapter 64, "User Messaging Preferences." ). This metadata can be used to filter
out messages through message filters. Please check Table V - Message Metadata for exact metadata names.
UI screen should by default show all of these names in the Field Name combo box, if user selects field type
as METADATA.
For example, METADATA field name is Customer Name value specified is ACME . This can be set while
sending out the message through UMS API as shown below.
message.setMetaData (Message.NAMESPACE_NOTIFICATION_PREFERENCES, Customer
Name , ACME );
f.
Adapter UI wizard will try to compile the regular expression specified by user and will report any
errors immediately. This will provide early validation and help avoid later errors.
e ie .
12/47
3/8/12
O acle Re ie
g.
Message filters defined by user on Message Filter page above will be added as an activation
specification property, as explained below. While endpoint activation, adapter run-time will apply
these filters using UMS API.
Message Filters One or more message filters (message filters, blacklist or Whitelist, in the
same order in which user defined them) separate by a semicolon. Each message filter type,
FieldType, FieldName, Pattern and Action; these fields will be separated by a comma. In the
example below first message filter is to match the sub-string Purchase Order anywhere in the
SUBJECT field and accept the message if it finds one. Second message filter will match the 'From'
Email Header field to check if starting with 'foo'. If the header value starts with foo, action will
be REJECT.
<
="MessageFilters"
="MessageFilter,SUBJECT,.*PurchaseOrder.*,ACCEPT;HEADER,From,^foo.*,REJECT;Blacklist
john.paul@spam.com ;Whitelist,
one.two@three.com;Whitelist,four.five@six.com"/>
7.
On the Java Call
45
out page, user will be able to specify a Custom Java Class which will take the incoming
SDP message and process it to decide on whether to process the message or reject. One simple example
would be matching the sender address with one in the LDAP or some staging area recorded earlier. Interface
would look like as shown below.
I
IC
{
(M
);
Message being the Message class from UMS SDP Java API, well defined Java API given by UMS. Boolean value
returned would decide on whether to accept and process the message or reject the message.
User has to bundle this and other required custom classes as jar and place it in lib directory, located under
domain directory. This will add this jar file to the Weblogic Server System Classpath when server starts up.
Check the example JavaCallout code snippet below.

Use Case A particular user with email id john.paul@hotmail.com registers through internet store website.
This user would be recorded under a staging area by creating a file name john.paul@hotmail.com.usr. An
email is sent to him to verify his email id which asks him to reply to the sent email. Now if user replies to the
e ie .
13/47
3/8/12
O acle Re ie
email, UMS Adapter will pick the email. Now we want to check if this user has registered already through the
website. This can be done very well through Java Callout way. Please check the code snippet below.
Java callout example code
.
import
. .F
import
import
. .
UMSA
.M
.
_C
.IC
implements IC
()[0]
@O
(M
S
F
.
){
N
(
F
if(
= new F
.
();
F
(
= "/
/O
).
(".
/".
");
);
()) {
return true;
return false;
8.
e ie .
46
User clicks Finish on the final page to finish defining the Adapter Service.
14/47
3/8/12
O acle Re ie
The corresponding BPEL process would look like below.

Sample BPEL Process
3.1.1.3
Message Mapping
The following snippets illustrate the message mapping in context of WSDL operation and the schema definition.
Sample WSDL File
<
="ReceiveEmail"
="http://xmlns.oracle.com/pcbpel/adapter/ums/
UMSAdapter_In_SinglePart_Xlation/
SOAComposite_email_poller_bpel/ReceiveEmail"
:
="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
="http://schemas.xmlsoap.org/wsdl/"
UMSAdapter_In_SinglePart_Xlation/
SOAComposite_email_poller_bpel/ReceiveEmail"
: ="http://xmlns.oracle.com/pcbpel/"
:
1="http://platform.integration.oracle/blocks/adapter/
fw/metadata/UMSAdapter"
:
="http://schemas.xmlsoap.org/ws/2003/05
/partner-link/">
<
<
:
<
</
</
<
="ReceiveEmail_plt">
="ReceiveEmail_role">
="tns:ReceiveEmail_ptt"/>
>
L
>
>
<
="http://www.w3.org/2001/XMLSchema">
<
="http://platform.integration.oracle/blocks/adapter
/fw/metadata/UMSAdapter"
L
</
</
<
</
e ie .
>
>
:
<
="xsd/UMS.xsd"/>
="ReceiveEmail_msg">
:
="body"
="imp1:Email"/>
>
15/47
3/8/12
O acle Re ie
<
:
<
="ReceiveEmail_ptt">
="ReceiveEmail">
<
</
</
</
="tns:ReceiveEmail_msg"/>
>
>
>
Message Schema
<?
<
= '1.0'
:
= 'UTF-8' ?>
="http://www.w3.org/2001/XMLSchema"
="http://platform.integration.oracle/blocks/adapter/fw/
metadata/UMSAdapter"
N
="http://platform.integration.oracle/blocks/adapter/
:
F
F
<
<
="qualified"
="unqualified">
L
<
="singleString.xsd"/>
="MessageType">
>
<
<
="impl:payload"/>
="attachment">
<
<
:
<
>
>
="Attachment"
O
</
</
</
</
</
<
<
</
<
<
</
<
</
="AttachmentType">
="href"
="ResponseType">
>
:
="MessageId"
="xsd:string"/>
>
T
="xsd:string"/>
>
T
<
</
>
>
>
="unbounded"/>
>
T
="AttachmentType"
>
T
="0"
>
="message"
="MessageType"/>
>
Native Schema defined by the user singleString.xsd
<?
<
= '1.0'
:
= 'UTF-8' ?>
F
="unqualified"
="qualified"
:
:
="http://xmlns.oracle.com/pcbpel/nxsd"
="US-ASCII"
:
<
:
<
e ie .
="chars"
T
:
="true"
="NXSD">
="singleString">
>
16/47
3/8/12
O acle Re ie
<
:
="input"
:
</
</
<
</
="xsd:string"
="terminated"
:
B =";"/>
>
>
="payload"
="singleString"/>
>
The following snippet shows sample activation binding configuration file.

Binding Configuration
<
="ReceiveEmail"
L
="UMS Adapter"
="ReceiveEmail.wsdl"
="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<
<
<
="ReceiveEmail_ptt"
="c"/>
="ReceiveEmail">
="oracle.tip.adapter.ums.inbound.UmsActivationSpec">
<
="ConsumeMode"
<
="PollingInterval"
<
="DeliveryType"
<
="To"
</
</
3.1.1.4
</
="eis/ums/UMSAdapter" UI
="poller"/>
="15"/>
="Email"/>
="bpeladapter@umsdemo.us.oracle.com"/>
>
>
>
Connection Factory Properties
Table below describes Connection Factory Properties for the UMS Adapter.
Property Name
Description
XATransaction
Specify it with value 'false' to disable XA Transaction

support on inbound. Default value is 'true'
3.1.1.5
Activation Specification Properties
Table below describes Activation Properties available for the UMS Adapter.
Property Name
Description
JavaCalloutImpl
Name of the java class which defines custom logic for a message filtering or
any other check. It's a concrete implementation of ICustomCallout interface.
ConsumeMode
Specifies how the adapter will receive messages from UMS. Set to poller for
polling mode Or set to listener for listener mode.
To
Address from which to receive incoming messages. One or more comma

separated email address for delivery type Email or mobile number when
delivery type is SMS.
DeliveryType
Specify the message channel to receive/send messages. Email, SMS, IM in

case of receiving. Email, SMS, IM, Voice for sending outgoing message.
PollingInterval
Polling interval in seconds for poller consume mode.
MessageFilters
Specify one or more message filters. A single filter would comprise of a Java
Pattern String to match the incoming message against, along with the field
type and the action (Accept or reject) to be taken.
e ie .
17/47
3/8/12
O acle Re ie
InboundThreadCount
3.1.1.6
Specify the number of inbound poller or listener threads.
Endpoint Properties
Table below describes the endpoint properties for the UMS Adapter inbound scenario.
Property Name
Description
Jca.retry.count
Indicates the maximum number of retries before rejection.
Jca.retry.interval
Indicates the time interval between retries (measured in seconds).
Jca.retry.backoff
Indicates the retry interval growth factor (positive integer).
Jca.retry.maxInterval
Indicates the maximum value of retry interval; that is, a cap if back-off
is greater than 1.
3.1.1.7
Normalized Message Properties
UMS Adapter will expose all applicable internet messages headers (defined under RFC 5322) along with mime message
headers (defined by RFC 822) and mime part headers (within a multipart construct. Note that it s applicable only for the first
body part that is adapter payload. Mime headers for attachment are stored along with attachment) as normalized message
properties which can be manipulated from within a BPEL process.
Table below describes all the applicable headers defined by internet message format along with mapping with corresponding
adapter header.
Table I Message Headers

Header Field Name
Min Occurrence
Max Occurrence
Mapped Adapter Header

Field Name
Return-Path
jca.ums.return-path
Received
unlimited
jca.ums.received
Resent-Date
unlimited
jca.ums.resent-date
Resent-From
unlimited
jca.ums.resent-from
Resent-Sender
unlimited
jca.ums.resent-sender
Resent-To
unlimited
jca.ums.resent-to
Resent-Cc
unlimited
jca.ums.resent-cc
Resent-Bcc
unlimited
jca.ums.resent-bcc
Resent-Message-ID 0
unlimited
jca.ums.resent-messageid
e ie .
Date
jca.ums.date
From
jca.ums.from
Sender
jca.ums.sender
Reply-To
jca.ums.reply-to
To
jca.ums.to
Cc
jca.ums.cc
Bcc
jca.ums.bcc
Message-ID
jca.ums.message-id
In-Reply-To
jca.ums.in-reply-to
18/47
3/8/12
O acle Re ie
References
jca.ums.references
Subject
jca.ums.subject
Comments
unlimited
jca.ums.comments
Keywords
unlimited
jca.ums.keywords
Note: that some of the above headers might appear more than once in a single message, multiple values of which will be set
to the same adapter header property, only to separate them with CRLF character sequence.
Table below describes all applicable Mime message headers.
Table II MIME-message headers

Header Field Name
Mapped Adapter Header Field Name
MIME-Version
jca.ums.mime-version
Content-Type
jca.ums.msg.content-type
Notes
Content-Transfer-Encoding jca.ums.msg.content-transferencoding
Content-ID
jca.ums.msg.content-id
Content-Description
jca.ums.msg.content-description
Content-Disposition
jca.ums.msg.content-disposition
Content-Language
jca.ums.msg.content-language
Mime-Extension-field
jca.ums.msg.mime-extension-
Any other mime header field (might be
headers
added in future) which begins with

string Content-. User can add more
than one headers as Content-* : value
CRLF Content*- : value
CRLF - \r\n
Table below describes all applicable MIME part headers.
Table III MIME-part headers

Header Field Name
Mapped Adapter Header Field
Notes
Name
Content-Type
jca.ums.part.content-type
Content-Transfer-Encoding
jca.ums.part.contenttransfer-encoding
Content-ID
jca.ums.part.content-id
Content-Description
jca.ums.part.contentdescription
Content-Disposition
jca.ums.part.contentdisposition
Content-Language
jca.ums.part.contentlanguage
Mime-Extension-field
jca.ums.part.mime-
Any other mime header field (might be
extension-headers
added in future) which begins with string

Content-. User can add more than one
headers as Content-* : value CRLF Content*-
e ie .
19/47
3/8/12
O acle Re ie
: value
CRLF - \r\n
Adapter should allow user to add any proprietary headers. Table below describes the mechanism.
Table IV - Proprietary Headers

Header Name
Notes
jca.ums.msg.proprietary-
More than one proprietary header
headers
can be added as
Header Name : value CRLF Header
Name : value
(Header Name should be like
ums.adapter.xxxxx
CRLF - \r\n)
3.1.1.8
Receive Mode Polling Vs Listener
UMS has given both poller and listener option for applications to retrieve messages and adapter will be providing the same.
Adapter allows choosing between polling or listener mode to receive inbound messages. Polling can be used to process
messages in a batch with defined wait period in-between each poll, while listener mode can be used to receive and process a
message as and when available.
3.1.1.9
Inbound Polling Semantics

UMS d
47
oes not provide any formal JTA transaction support on inbound but relies solely on reliable messaging
through message acknowledgments for synchronous receive or polling way of message retrieval. UMS Adapter will make use
of this reliable messaging feature to avoid any message loss.
1.
UMS API provides a synchronous receive () call.
48
In a reliable mode, if application calls receive (), but
then fails to call acknowledge () (both methods in the UMS client API), then the message will be put back in
the JMS queue (UMS uses JMS underneath) for later redelivery.
2.
Adapter will use parametrized synchronous receive to get one message at a time, process it and
acknowledge it duly, which will help avoid any message loss. Note: Parametrized synchronous receive call in
case of synchronous receiving of messages from UMS. Note - A360 requirement 557688: Throttling to
control the number of inbound messages to be delivered.
3.
User can specify more than one polling threads for an activation using InboundThreadCount activation spec
property, each one of them will receive one message at a time, will process and publish it and then will
acknowledge. Note that polling thread is same as the processing thread. Default value for this property is
one.
4.
49
Adapter will keep receiving message until messages are available in the INBOX. When there are no
more messages, only then, adapter will sleep for the polling interval specified by the user. This will avoid
mounting up large number of messages in the inbox, under high incoming message volume scenarios.
5.
Each endpoint will have one UMS Connection (Messaging client instance) and all threads will use the same
UMS Connection (Messaging Client Instance) to receive messages. An instance of Messaging Client is not
thread-safe and adapter will synchronize the access.
3.1.1.10
Inbound Listener Semantics
For asynchronous receiving of messages, user will opt for the listener mode. UMS Adapter will register a message listener
object. When incoming message arrives at the specified access point address, UMS infrastructure will invoke listener's
onMessage callback. Below are some important points on listener semantics.
1.
User can specify adapter listener thread count by specifying an activation property, InboundThreadCount,
same as in polling case. This property value will be used by the adapter to set the property
MessageListenerThreads on UMS side. This property controls the number of listener worker threads on
UMS server side. Default value is one. Specifying this property means multi-threaded asynchronous receiving
of messages and for this case adapter has to handle multi-threaded access to the listener object that is
e ie .
20/47
3/8/12
O acle Re ie
simultaneous calls to onMessage on the same message listener.

2.
3.
UMS Infrastructure will deliver one message per listener event.

For asynchronous receiving via onMessage callback the UMS library takes care of the acknowledgment. The
default is client_acknowledge, which means, it will acknowledge only after completion of the onMessage ()
method. Any exception thrown during the callback results in no acknowledgment and message is redelivered
later. This is the reliable mode.
4.
3.1.1.11
Listener thread will be the processing thread.
Transaction Semantics
UMS does not offer any XA support on inbound and there is little chance of getting it in 12g time frame.
One of the important requirements for the adapter is to participate in the global transactions. To achieve this, adapter will
make use of LRC kind of optimization provided by the Weblogic server under JCA Resource Adapter Transaction
Management. Important points are below.
1.
No XA transaction support for inbound listener mode of receiving messages. XA is applicable only for polling
way of receives.
2.
By default, for inbound, adapter will always work in XA mode. This although can be changed by setting the
Connection Factory property 'XATransaction' to false.
3.
Adapter will make use of JCA Resource Adapter, transaction management contract, under which Weblogic
server allows one (and only one) local transaction resource to be part of a 2PC that is XA transaction protocol.
Here the Weblogic server Connector Container uses a Last Resource Commit Optimization whereby the
outcome of the transaction is governed by the resource adapter s local transaction.
4.
The connection factory for the resource adapter is configured to use local transaction, this will make
application server to start a local transaction when the connection is created.
5.
Along with above connection factory setting, a connection factory property named XATransaction is
required to be set to true. By default value of XATransaction property is true. This ensures that adapter
will always use XA on inbound.
6.
7.
With each receive of a message from UMS; adapter will start a global transaction.
A local transaction is started by the application server automatically when the resource adapter connection
that is configured to use local transaction is created and used within the context of XA. When the XA
transaction completes and is ready to commit, prepare is first called on the XA resources that are part of the
XA transaction. Next the local transaction is committed.
8.
If the commit fails on the local transaction, the XA transaction and all the XA resources are rolled back. If
the commit succeeds, all the XA resource for the XA transaction are committed. When the adapter closes the
connection, Weblogic server cleans the connection once the transaction has completed.
9.
Sequence of events are as below
10.
The sequence of events:

1.
Adapter start JTA
2.
Gets hold of the CCI connection from the connection factory

1.
Application servers gets hold of the SPI local transaction from the managed connection (within the
CCI connection)
Registers a Synchronization for JTA completion
3.
Calls begin on the local transaction
3.
the adapter does its business
4.
Calls close() on the CCI connection
5.
e ie .
2.
1.
The application server receives a Connection Close event from the adapter
2.
Checks to see if there is a transaction (either local or JTA) in progress
3.
If it is in progress, then it does not release the connection back to the pool
Adapter commits JTA
21/47
3/8/12
O acle Re ie
11.
1.
SPI local transaction is committed
2.
Rest of the 2pc resources commit
3.
The Synchronization gets the notification

1.
Notifies the connection pool that the transaction has completed
2.
The managed connection is released
Processing, publish of the message to the composite and removal of the message from UMS by will be part
of the transaction.
12.
This is an asynchronous service entry and successful commit on the adapter side will only start the
composite execution (Bpel/mediator use database for scheduling of composite execution).
13.
In case somebody wants to use a synchronous way, there will be restriction of only one non-XA resource
imposed by the Transaction Manager. User should keep this in mind while designing his composite
application.
14.
Considering XA and rejection handling, please note that the existing JTA transaction will always be marked
for the rollback before rejecting the message.
3.1.1.12
Inbound Error Handling
Rejection Handlers
UMS Adapter as all other technology adapters will use the default rejection handling mechanism on the inbound side for
rejecting bad messages. For example, any translation related error will result into rejecting the message. This will work as an
Error Hospital to analyze errors.
1
Inbound Retryable Error Conditions

With retriable error conditions and when retry related endpoint properties are specified, adapter will try republishing the inbound message for configured number of retries before rejecting the message. In case of
XA, transaction will be set for the rollback.
Inbound Non-retryable Error Conditions

For non-retriable error conditions, the message will be immediately rejected, with transaction set for the
rollback in case of XA.
3.1.1.13
Attachment Handling
Adapter will use the Fabric Attachment Manager to store and retrieve attachments.
UMS Message schema defines Attachment element with a href attribute as shown below.
Message Schema for Attachment
UMS Message XML can have list of Attachment elements with a href attribute. Attachment manager stores other mime
details associated with attachment as MimeType; Content ID etc. along with a stream object (attachment content).
On the inbound side, adapter will set all mime details before passing attachment to Attachment Manager, while on the
outbound; adapter will extract any mime details received along with attachment object and will use them while creating the
outgoing SDP message notification.
e ie .
22/47
3/8/12
O acle Re ie
Fabric Attachment Manager will update the href attribute with a key after storing the attachment to the database. This key
later can be used to retrieve attachment content.
Please check below the sample Normalized Message payload map with XML structure having attachment element, passed from
UMS Adapter to BPEL service engine.
Sample XML Message with attachment element
<R
1_R
<
_I
>
="body" >
<E
>
<
>This is a test mail.-Sagar</
<
<A
="0DF86C104BF511EoAF5977BAA7C7CFD9"/>
</
</E
</
</R
>
>
>
>
>
1_R
_I
>
The snippet below shows how attachments can be retrieved in BPEL

Getting Attachment in BPEL
And the snippet below shows how attachments can be set in BPEL.
Setting Attachment in BPEL
3.1.2
Inbound Receive Notification in a Cluster (Polling or through a Listener)
The same scenario as in 3.1.1 only targeted to a cluster environment for deployment.
UMS Adapter should support high availability in an active-active setup.
UMS API supports an environment where UMS server along with clients is deployed in a cluster environment. Below are
configuration details for UMS Adapter to work properly in a cluster environment.
1.
All UMS Adapter activations of same composite will use the same unique ApplicationName configuration
parameters. Adapter will synthesize the application name parameter from inbox addresses on which the
particular endpoint is supposed to listen. This will allow all activations of a particular composite in a cluster to
share all configuration and artifacts such as Access Points and Message Filters etc.
2.
ApplicationInstanceName configuration parameter is synthesized automatically by UMS the API

implementation and adapter will depend on the same.
3.
UMS Adapter API implementation guarantees that in a cluster environment no two applications will receive
the same message.
4.
Listener and Polling semantics should be same even while using adapter in a cluster environment.
Note - UMS Adapter also should support active fail-over of inbound service that is active-passive setup in a
cluster environment. This can be enabled through a JCA service binding property (composite.xml), singleton,
set to true.
3.1.3
Inbound In with SSL to communicate with IMAP/POP3 server
In this scenario, the adapter would function the same way as Inbound Receive scenario, described under 3.1.1. Design part
e ie .
23/47
3/8/12
O acle Re ie
for Adapter Service as well as BPEL would be same. There would just be only additional configuration effort on the UMS side.
Enabling SSL would be the configuration on the UMS Server side for the Email driver.
User need to set the IncomingMailServerSSL property on the email driver to true. IncomingMailServerPort property value
should be changed accordingly to use the correct port in case of SSL.
3.1.4
Outbound Send Notification (Email, SMS, IM, Voice)

A synchronous request response or one way invoke scenario, where adapter client would request to send the
notification. The Underlying adapter prepares the message notification (message body translated as per the schema)
and sends it to UMS server using UMS API. UMS server will return a message identifier after accepting the send
request. Adapter will return back the same as a response in case of synchronous request reply case. User can opt to
receive the message id, which will make it a synchronous request response call or just one way invoke without any
kind of response from the adapter.
Designing this service involves two main parts
3.1.4.1
1.
Configuration on the UMS Server side to send outbound notifications.
2.
Designing the Adapter Service and BPEL process.
Email Driver Configuration on UMS side.
On the UMS Side, for outbound scenario following are some of the email driver properties administrator need to
configure from the Enterprise Manager Console.
OutgoingMailServer - The name of the SMTP server
OutgoingMailServerPort - The port number of SMTP server
50
OutgoingUsername - The username used for SMTP authentication.
OutgoingPassword - The password used for SMTP authentication

For details on configuring SMPP, XMPP and VoiceXML driver, please check UMS Admin Guide.
3.1.4.2
Design the Adapter Service and BPEL Process.
User would be using UMS Adapter Configuration wizard under JDeveloper to design the outbound adapter reference as
shown below.
1.
e ie .
User enters the SendEmail in the Service Name field as shown below.
24/47
3/8/12
O acle Re ie
2.
Selects Outbound Send Notification as the operation type.
51 - 52
User also specifies the type of
notification that is Email, SMS, Instant Message or Voice (text to speech). If user is interested in the
receiving the message id from the UMS server (to check message delivery status information), he can choose
a synchronous request-reply operation by selecting the Receive message id as a reply check box. In other
case, it would be a one-way invoke operation, which will just send a message notification.
3.
53
Notification Details Page.

User configures the Notification Message Details after selecting the type of Notification as Email, SMS,
IM or Voice.
1.1
For instance, selecting Email as the notification type, users enters other details as one or more email:
From addresses, one or more email: To addresses, one or more email: CC & BCC addresses, one or
more email: BCC addresses.
1.2
1.3
User can specify a ReplyTo address.

User also can specify a failover address for any primary address like primary address: failover
address. For example
Joe.demagio@sport.com:failover-id@sport.com
In case of email this would be applicable for to, cc and bcc addresses.
1.4
User can choose to browse identity service using 'Identity Look-up Dialog' to search and fill address
attributes.
1.5
For all of the messaging channels, user can opt to specify a user or a group instead of a device
address. For example, USER:weblogic Or GROUP:admins.
e ie .
25/47
3/8/12
e ie .
O acle Re ie
Screen below shows endpoint attributes for SMS type
Screen below shows endpoint attributes for IM type.
26/47
3/8/12
O acle Re ie
4.
e ie .
Screen below shows endpoint attributes for Voice type.
One the Message Page, User enters schema details, which defines the outgoing notification payload.
27/47
3/8/12
O acle Re ie
5.
Finally user clicks Finish on the final page to finish adapter wizard.
The corresponding BPEL process would look like below.

Sample BPEL Process
e ie .
28/47
3/8/12
O acle Re ie
3.1.4.3
Message Mapping
The following snippet illustrates the message mapping in context of WSDL operation and the schema definition.
Sample WSDL File
<?
<
= '1.0'
= 'UTF-8' ?>
:
="SendEmail"
N
UMSAdapter_Out_Multipart_Noxlation/SOAComposite_Email/SendEmail"
:
:
:
1="http://platform.integration.oracle/blocks/adapter/fw/metadata
/UMSAdapter"
:
="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
>
e ie .
29/47
3/8/12
O acle Re ie
<
<
:
<
</
</
<
="SendEmail_plt">
="SendEmail_role">
="tns:SendEmail_ptt"/>
>
L
>
>
<
N
:
:
:
1="http://platform.integration.oracle/blocks/adapter/
:
="http://schemas.xmlsoap.org/ws/2003/05/partner-
link/">
<
="http://platform.integration.oracle/blocks/
adapter/fw/metadata/UMSAdapter"
L
</
</
<
>
>
:
<
</
<
="SendEmail_msg">
:
="body"
:
T
="SendEmail_ptt">
="SendEmail">
<
</
</
</
="imp1:EmailPayload"/>
>
:
<
="xsd/UMS.xsd"/>
="tns:SendEmail_msg"/>
>
>
>
Message Schema Definition
<?
<
= '1.0'
:
= 'UTF-8' ?>
="http://platform.integration.oracle/blocks/adapter/fw/
metadata/UMSAdapter"
N
="http://platform.integration.oracle/blocks/adapter/
:
F
F
<
="qualified"
="unqualified">
L
<
:
<
T
:
="MessageType">
>
<
<
:
<
="impl:payload"/>
="attachment">
:
<
e ie .
="singleString.xsd"/>
T
:
>
>
30/47
3/8/12
O acle Re ie
<
="Attachment"
="AttachmentType"
O
</
</
</
</
</
</
="href"
="ResponseType">
:
<
</
>
:
="MessageId"
="xsd:string"/>
>
T
>
<
="Email"
<
="IM"
<
="Voice"
<
="SMS"
<
="Response"
="xsd:string"/>
>
<
</
="AttachmentType">
</
>
<
>
>
<
="unbounded"/>
>
T
>
<
="0"
="MessageType"/>
="MessageType"/>
="MessageType"/>
="MessageType"/>
="ResponseType"/>
>
Native Schema defined by the user singleString.xsd
<?
<
= '1.0'
:
= 'UTF-8' ?>
F
="unqualified"
="qualified"
N
:
="http://xmlns.oracle.com/pcbpel/nxsd"
="US-ASCII"
:
<
<
:
<
="chars"
="true"
="NXSD">
="singleString">
>
="input"
="xsd:string"
="terminated"
:
</
</
<
</
>
T
B =";"/>
>
="payload"
="singleString"/>
>
And the following snippet illustrates the sample interaction Specification Properties.
Sample Interaction Specification Properties
<
="SendEmail"
L
="UMS Adapter"
="SendEmail.wsdl"
="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<
<
<
="SendEmail_ptt"
="SendEmail">
="oracle.tip.adapter.ums.outbound.UmsInteractionSpec">
<
e ie .
="eis/ums/UMSAdapter"/>
="DeliveryType"
="Email"/>
31/47
3/8/12
O acle Re ie
<
="From"
<
="To"
<
="ReplyTo"
=" johny.deep@oracle.com"/>
<
="Subject"
="Test Email"/>
</
</
</
3.1.4.4
>
="johny.deep@oracle.com"/>
="peter.parker@oracle.com"/>
>
>
Interaction Specification Properties

Table below describes the interaction properties available for the UMS Adapter.
Property Name
Description
DeliveryType
Specify the message channel to receive/send messages. Email, SMS,

IM in case of receiving. Email, SMS, IM, Voice for sending outgoing
message.
3.1.4.5
Subject
Subject of outgoing message.
From
Sender addresses of outgoing message
To
One or more recipient addresses
ReplyTo
Reply-To address
Cc
One or more cc addresses for email delivery.
Bcc
One or more bcc addresses for email delivery.
Failover
Fail-over address for outgoing message.
SendEmailAsAttachment
True to send email as an attachment.
Normalized Message Properties
Outbound
Please check 3.1.1.7 above to see applicable normalized message properties in relation with MIME and Internet
Message Headers.
Message Metadata headers defined below are only applicable on the outbound side.
Message metadata that is keywords defined and used under user preference based messaging will also be exposed by
the adapter as message headers. Table below describes adapter headers mapped with the metadata keywords.
Table V - Message Metadata

Business Term
e ie .
Mapped adapter header field name
Service Name
jca.ums.metadata.service-name
Process Name
jca.ums.metadata.process-name
System Code
jca.ums.metadata.sysetm-code
Error Code
jca.ums.metadata.error-code
Occurrence Count (*)
jca.ums.metadata.occurence-count
Organization
jca.ums.metadata.organization
Time (**)
jca.ums.metadata.time
Priority
jca.ums.metadata.priority
Application
jca.ums.metadata.application
Application Type
jca.ums.metadata.application-type
Expiration Date
jca.ums.metadata.expiration-data
From
jca.ums.metadata.from
32/47
3/8/12
O acle Re ie
To
Customer Name
jca.ums.metadata.to
jca.ums.metadata.customer-name
Customer Type
jca.ums.metadata.customer-type
Status
jca.ums.metadata.status
Amount (*)
jca.ums.metadata.amount
Due Date
jca.ums.metadata.due-date
Process Type
jca.ums.metadata.process-type
Expense Type
jca.ums.metadata.expense-type
Total Cost (*)
jca.ums.metadata.total-cost
Processing Time (*)
jca.ums.metadata.processing-time
Order Type
jca.ums.metadata.order-type
Service Request Type
jca.ums.metadata.service-request-type
Group Name
jca.ums.metadata.group-name
Source
jca.ums.metadata.source
Classification
jca.ums.metadata.classification
Duration (*)
jca.ums.metadata.duration
User
jca.ums.metadata.user
Role
jca.ums.metadata.role
(*) - A string representing a floating decimal point number with double precision.
(**) A string representing time in HHMM format. HH is in 24 hour format. MM minutes.
3.1.4.6
Endpoint Properties
Table below describes the endpoint properties available for the UMS Adapter outbound scenario.
Property Name
Description
jca.retry.count
Indicates the maximum number of retries before throwing retryable

error condition back to invoking service engine.
jca.retry.interval
Indicates the time interval between retries (measured in seconds).
jca.retry.backoff
Indicates the retry interval growth factor (positive integer).
jca.retry.maxInterval
Indicates the maximum value of retry interval; that is, a cap if the
backoff is greater than 1.
jca.retry.maxPeriod
Indicates the maximum total retry period. Retries do not occur longer
than the value specified in this parameter.
3.1.4.7
Connection Factory Properties
None defined for an outbound scenario.

3.1.4.8
Transaction Semantics on the Outbound
UMS would be providing XA capabilities on outbound for 12c release. A360 requirement 557827: Ability for UMS to
participate in an XA transaction.
Below are some important points about transaction semantics on outbound.
1.
e ie .
Outbound JCA interaction are scoped with the global JTA transaction(adapter does not control any
33/47
3/8/12
O acle Re ie
transaction boundaries but would just participate in one).

2.
UMS makes use of JMS underneath. Given the transaction fails, outbound send message delivered to the
queue would be rolled back. This will ensure that no false notification/alert would be sent by UMS.
3.
The adapter defines the type of transaction support by specifying the transaction-support element in the
weblogic-ra.xml file. It can be XA, local or No transaction.
4.
In case of XA, all composite activities along with UMS adapter invocation would be part of a global
transaction. All activities are either committed or rolled back if an error occurs.
5.
One example would be a BPEL process inserting data into more than one tables along with sending an email
through UMS Adapter invocation. When the BPEL process is about to finish the JTA transaction is committed.
Only at that point, database inserts and email send invocation would be committed. If any error occurs
during BPEL instance execution, all activities (including email send invocation) would be rolled back to the
last dehydration point.
6.
Considering XA and fault policy, please note that it's not advisable to use fault policy with XA as fault policy
runs in its own transaction and does not participate in the global transaction. This means that fault policy will
commit any existing JTA transaction before it starts executing the reference to which fault policy is bound.
7.
In case of Local Transaction (SPI Local Transaction management contract), application server will start a
local transaction with a connection request and will commit the local transaction when global transaction is
about to be committed. Any exception conditions in-between, will result in the rollback. Adapter will
implement ConnectionEventListener to notify transaction related events.
3.1.4.9
Outbound Error Handling

1.
Retriable Exceptions (Exact error conditions : TBD)

UMS Adapter like all other adapters will throw PCRetriableResourceException for transient error
conditions or in other words recoverable error conditions. For example connection errors.
For retriable errors, user can use retry policy supported by adapter framework, that is setting binding
property jca.retry.count. If you do not set jca.retry.count property then the retry is carried out through
fault policy, if fault policy is defined for the composite.
2.
Non-retriable Exceptions (Exact error conditions
TBD)
Non-retriable connection errors for outbound interactions can be handled by defining a fault-policy. The
maximum number of reconnection attempts can be defined through fault-policy.xml
3.
Data Errors
translation errors
One of the key features of Adapters is to translate the data from Native representation to standard
XML format and back based on the metadata captured at design time. A translation error aka
ResourceException is thrown when there is an exception thrown while carrying out translation. A
corresponding Binding Fault would be thrown which need to be captured for error recovery and repair.
This behavior is common across all adapters.
3.1.4.10
Retry Mechanism for Failed Outgoing Notifications with status reporting

1.
UMS Adapter will make use of existing infrastructure given UMS itself for retrying failed outgoing
notifications.
2.
Currently UMS only supports viewing of failed notifications along with manual send from Enterprise
Manager. For 12c, UMS will be giving support to configure the number of automatic retries upon message
delivery failure. (A360 requirement: 557822: Configurable automatic retries for message delivery - Ability to
configure the number of automatic retries upon message delivery failure for outbound messaging - this is a
domain-wide setting, applicable to all channels. On a per message basis, consumers should be able to
override the default setting. Upon manual resend of a message by an administrator (an action which is
already supported today), the number of automatic retries should still be applicable for the resend)
3.1.5
Outbound Send with TLS (SSL) to communicate with the SMTP server
In this scenario, the adapter would function the same way as described under 3.1.4. Design part for the Adapter
service along with BPEL part would be the same. There would be additional configuration effort on the UMS server
side.
e ie .
34/47
3/8/12
O acle Re ie
User needs to set the OutgoingMailServerTLS property on the email driver to true (default is false). This will enable
TLS encryption to communicate with the SMTP server.
Client Interfaces
4.1
Task Analysis, Roles, and Use Cases
4.1.1
HP
HP has the JCA adapter to integrate with the UMS to allow business processes to subscribe to multiple delivery
channels e.g. Email (POP and IMAP), SMS, Voice, and IM etc.
- Key requirement is to kick a BPEL process through emails.
- They need SSL support: that is enabling SSL while connecting to the Email Server.
No Requirement
1
Analysis
Feasibility Release
Connect to Exchange mailbox via IMAP or POP3 UMS default email driver is compatible Yes
on SSL port (preferably IMAP as it offers
with POP3 and IMAP4 protocol.
greater capability for manipulating messages
Microsoft Exchange 2003 has been
across mailboxes)
verified.
Poll various mailboxes for incoming email on
Using more than one polling threads
various schedules both sequential and parallel.
ensures parallel processing while using
Some emails may need to be processed in
a single thread ensures sequential or
order, while others can be processed in any
in order processing.
12c
Yes
12c
Yes
12c
Yes
12c
Yes
12c
Yes
12c
Yes
12c
1. Yes
12c
order
3
From the time a message is received in a
This totally will depend on the input
mailbox to the time when it is visible in or to a volume of messages and cannot be

user task should not exceed 5 minutes on
guaranteed. Although user can opt to
average
increase poller threads to reduce the

time lag.
Allow for throttling to control the number of
Adapter should provide this using
messages to be processed from a given mailbox Polling mechanism along with polling
with a given time period.
5
interval.
Upon receiving an email,

1. Parse the email into component parts
(including attachments)
2. Properly handle content in various languages
including Chinese, Japanese, and the various
European languages
3. Properly handle different content types
including text, HTML, rich text, etc.
Determine if email received is correlated with
Adapter should give user an option to
running composite instance (BPEL) - this would add proprietary mail headers for an
determine whether the email is processed by a outgoing message.
running instance, or whether a new instance is
created to process the email message
7
Deliver parsed and properly encoded email
This should be possible with
component parts to a target which could be a
Bpel/Mediator along with email
queue (AQ/JMS), or a SOAP target to invoke
activation. See 5 above.
the appropriate process

8
The adapter should handle errors in a way that More details required on the use case
allows for either automatic recovery or some
form of automated handling
The adapter should have optimizations built in 1. Attachment Store - In the current
for large-file handling since we can't predict
what size of attachments customers might
design, adapter will save all attachment 2. No

under Fabric Attachment Store.
send. Note that we would prefer not to handle
2. This support has to come from fabric
attachments in SOA at all. We have a separate

e ie .
35/47
3/8/12
O acle Re ie
document management asset based on HP Trim itself, plugging in external attachment

which is where all documents are stored and
stores.
eventually archived. Ideally, we would like to

post all attachments to HP Trim, and only
include returned references from Trim into the
process payload. I recognize that this poses a
challenge, but I also recognize that attempting
to handle unpredictably large documents in the
SOA Suite is probably just as challenging if not
more so.
10 The adapter should expose some run time
This might be just beyond adapter s
configuration capabilities including, for
usual functionality that is what adapter
example:
is supposed to do. Moreover, UMS
1. Ability to update account/password to be
Adapter never is directly dealing with
used for polling any specific mailbox
any particular mail box on the email
2. Ability to schedule a purge of a particular
server so carrying out admin tasks
mailbox folder for all mail beyond a particular
related to mail box are out of scope.
No
age, or above a particular size, or containing a

particular subject, or sent from a particular
email address
4.1.2
Rabobank
No Requirement
Analysis
Feasibility Release
SMTP support is available with UMS
Yes
12c
Mail Filtering
1/2/3 - UMS does allow specifying Java
Yes
12c
1. Adapter can filter incoming messages
patterns while adding message filters.
based on SMTP from and to addresses, e.g.
User should be able to specify complex
*.rabomail.nl
filters for selectively receiving mails.
Yes
12c
Business case SMTP Vs POP

1. For inbound e-mail, POP as protocol is not
sufficient because it requires connections for
each separate e-mail address, whereas SMTP
can handle multiple e-mail addresses
simultaneously.
2. Adapter can filter incoming messages

based on e-mail to address, from address, cc 4 Support for adding proprietary
address, subject, and mail headers
headers to outgoing mails.
(header/regexp)
3. Mails can be ignored based on mime to
5 Adapter will not directly generate
address, from address, cc address, subject,
auto replies. Although user can use
and mail headers (header/regexp).
adapter with the workflow for auto
4. Business case: identify bounced replies,
replies.
e.g. through proprietary mail headers that

were added to the originating outgoing
6 Java Callout option can be used to

message (such end-to-end functionality that filter and move bad messages to error
is based on proprietary headers cannot be
hospital.
guaranteed for 110%. Nevertheless, it can be
expected that it will cover 90+ %)
5. The adapter can generate auto replies
6. The filter can also block messages, i.e.
ignore them or move them to error hospital
or forward them to another location
3
e ie .
Mail Routing
Routing messages to an external SMTP
1. The system will be an MTA. Incoming
server user should be able to achieve
36/47
3/8/12
O acle Re ie
messages that do not match a filter of an
this using adapter and workflow
SMTP adapter will be either relayed to an
together.
external SMTP Server, or put into the error

hospital, or
2. Avoid implementing an 'open relay' - add
4
security
Mail handling - attachment store
Attachment Store The adapter should
1. Incoming mails are received in an XML
save attachments under Fabric
structure that reflects the structure of the
Attachment Store. We do have XSLT
multipart mime format: no information will
functions under BPEL/Mediator to access
be lost
attachment content.
Yes
12c
Yes
12c
2. Incoming attachments are stored in the

attachment store; in the mail they are
Claim-check pattern????
replaced with identifiers

3. Attachment store based on file, DB,
WebDAV, Stellent
4. Access to the attachments through a
special xslt look-up function
5. Optionally, this attachment store could
also be used by outgoing adapters: specially
formatted identifiers are replaced with the
content in the attachment store.
6. The attachment store implements the
claim-check pattern
5
Error handling
As all other adapters under adapter
1. Error handling: retry policies for outgoing stack, UMS Adapter should be supporting
fault-bindings and fault-policies for
mails that cannot be sent
2. Error handling: policies on incoming mails, rejection handling and retries.
combined with above filter functionalities,
combined with Workflow Hospital
4.1.3
B2B Requirements
No Requirement
Analysis
Do we have to work with the UMS API to

1
User would not be dealing with UMS API
Feasibility Release
create message or it is going to be like

any other adapter for sending message?
If t here is an option to initiate email, like
2
Sending email as an attachment
invoking any other interaction is
requirement is added under outbound
available. We have few questions,
functionality.
Yes
12c
Yes
12c
Yes
12c
Can we send the content as body or

attachment and both?
We have a requirement to send even
simple single content as
attachment but not as body. Can
this be done?
Can we send multiple attachments?
As part of our notification requirement, we
3
may need to notify customers over
54
Support for Email, SMS, IM & Voice.
Currently no support for Pager.
EMAIL, SMS and pager message etc. Do

we have support for all these messaging
platforms?
W e may need SSL support over EMAIL as
4
well.
e ie .
37/47
3/8/12
O acle Re ie
Need an option on the adapter side to
This support has to be given by UMS Team
configure all UMS related metadata. This first. The requirement has been given to
Not
12c
decided.
would help us to capture endpoint details UMS by B2B team, but still hasn t received
in B2B console itself and
any commitment for the same. If UMS
Initiate the adapter with required
agrees to give it, adapter will give support.
information to send notification over

Email and/or other supported channels.
5
5.1
Other Design Considerations

Scalability/Availability
1. Adapter should be designed to use multi-threading/multiplexing wherever possible.
2. Should support Horizontal Scalability by distributing load across various nodes deployed.
3. Adapter should support dynamic fail over by seamlessly failing over to other available node in case one particular
node goes down.

4. UMS API supports an environment where UMS server along with client applications is deployed in a clustered
environment. More details are under functionality above.
5.2
Deployment and Life Cycle

J2EE applications are expected to follow the standard J2EE deployment model and its life cycle. Some projects may
involve components or sub-components with a different life cycle, e.g. BPEL business processes.
If there is a deployment step involved, describe what needs to be done at that stage and what tools or user interfaces
support it.
Describe the run time configuration of the product after deployment, e.g. the processes that will run and the data
stores or services that will be accessed.
5.3
5.4
API & Libraries

1.
UMS API SDP libraries
2.
Java Mail API
3.
Oracle XDK
Extensibility
S/MIME support There are plans to support S/MIME by UMS.
Support for Fax & Pager UMS does not support this right now, but user can opt for writing custom drivers for the
same.
e ie .
38/47
3/8/12
O acle Re ie
Subject
Author
Status
Assignee
Modified
Priorit
This section
seems to be
ver...
Siqun Li (siqli, siqun.li@oracle.com)
Open
Sagar Shirguppi (sshirgup,

sagar.shirguppi@oracle.com)
Mar 21,
2011
10:13:42
AM
Siqun Li (siqli, siqun.li@oracle.com ): This section seems to be very much UI driven. There should be functions section describes the
adapter inbound functionalities. The information I'd like to see in this section are: 1. Activation Spec Properties definition. 2. Inbound Message
mapping from UMS to Normalized Message for each messaging type Email, SMS, IM. Simply referring to predefined schema in the appendix is
not enough. You indicated polling is a synchronous receive. What is the message pattern for polling? What w ould be the expected reply? 3.
How is attachment handled. Is Fabric attachment store required? Can attachment be streamed to adapter inbound endpoints like OSB proxy.
4. Semantics for applying Filters. 5. Semantics for Listener mode. How many listener thread w ill each endpoint have? How many message
does each listener event deliver? Will the listener thread be the processing thread? 6. Semantics for polling mode should be moved to this
section as w ell for inbound functions. Will poller thread be processing thread? 6. What is the semantics in cluster? Is it a singleton? Is it
deployed as active/passive or active/active? How does listener and polling mode w ork in a cluster? 7. Comparison betw een listener and
polling mode, advantage and disadvantage? Why w ould a user choose one vs. the other. This w ill be very useful information. This w ill
answ er my question on w hy w e need tw o different mode for inbound. 8. Is there any binding properties? 9. Is there any Normalized
Message Properties? 10. (Feb 22, 2011 11:57:43 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 1. I have removed ActivationSpec properties from the end of the document
and added it under Inbound Receive Notification functionality. (Mar 10, 2011 4:48:58 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 2. Are you asking message pattern betw een adapter and Service
Engine(BPEL/Mediator) or betw een UMS server and UMS Adapter? synchronous receive, I mentioned is betw een UMS and adapter. It's a
synchronous call and returns a message(oracle.sdp.messaging.Message) if available. (Mar 10, 2011 5:15:21 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 3. Can you pls elaborate a little on how OSB proxy is used to stream
attachments into an endpoint? I am not sure, but I am suspecting that this might not be feasible. (Mar 11, 2011 5:11:44 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 4. I have added details on how filters w ill be applied. (Mar 12, 2011 9:30:29
PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 5. semantics for listener mode is added. (Mar 13, 2011 1:25:47 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 6. I have moved semantics for polling/listener mode and other details to the
first section. (Mar 13, 2011 1:26:22 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 7. We have a requirement for polling mode from a customer, but there is
not any requirement yet for listener mode, though UMS supports these both modes of message retrieval and it's better to support both modes
as there might be some special use case for listener mode. (Mar 13, 2011 9:05:39 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 8. Retry related binding properties w hich are same for all adapters. I
already have added them to the spec. (Mar 13, 2011 9:08:32 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 9. I have added normalized message properties details. (Mar 13, 2011 7:04:54
PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Assignee changed from 'sshirgup' to 'siqli' (Mar 16, 2011 1:08:39 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Status changed from 'Open' to 'Fi ed' (Mar 16, 2011 1:08:39 AM)
Siqun Li (siqli, siqun.li@oracle.com ): In general, w e should have UI feature separated from runtime feature in the spec. I'm looking for
message pattern for each operation betw een adapter and service engine. When you say a specific operation is sync request/reply or
request only, you w ould need to clearly specify the message pattern for these operations, otherw ise people w ould have no w ay of
know ing how the messages are mapped. This w ill be very important for customer as w ell as our QA, doc. Like I mentioned in the attachment
section comment, OSB receives attachment from JCA framew ork as part of the NormalizedMessage. In Normalized message, attachment is
presented as a map of contentID as key and JCA framew ork Attachment object as value w hich include attachment headers and attachment
InputStream. (Mar 21, 2011 9:52:42 AM)
Siqun Li (siqli, siqun.li@oracle.com ): Assignee changed from 'siqli' to 'sshirgup' (Mar 21, 2011 9:52:42 AM)
Siqun Li (siqli, siqun.li@oracle.com ): Status changed from 'Fi ed' to 'Open' (Mar 21, 2011 10:13:42 AM)
Suggest w e use
the same term...
Fixed
Mar 21,
2011
7:15:44 AM
Siqun Li (siqli, siqun.li@oracle.com ): Suggest w e use the same term for attachment attribute as SOAP Message w ith Attachment spec
to reduce confusion, e.g. ContentType instead of MimeType, ContentTransferEncoding instead of ContentEncoding. (Feb 28, 2011 1:31:51 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Let me see, w e can change ContentEncoding to
ContentTransferEncoding, but I feel MimeType should be kept as it is, as it's in accordance w ith Internet Mail Message vocab. (Mar 21, 2011
7:15:44 AM)
So w hat is the
transaction s...
3
e ie .
Fixed
Mar 21,
2011
2:48:13 AM
Siqun Li (siqli, siqun.li@oracle.com ): So w hat is the transaction semantics for inbound then? (Feb 22, 2011 2:54:56 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): There is slight change in the transaction semantics on inbound. I w ill add
details to the new version. (Mar 14, 2011 8:34:09 PM)
Can you
elaborate on this
id...
Open

Mar 21,
2011
10:22:49
AM
Siqun Li (siqli, siqun.li@oracle.com ): Can you elaborate on this identity look-up? (Feb 22, 2011 2:36:51 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): This is a identity look-up dialog available under jdeveloper w hich enables
lookup of users, roles etc. from an Identity Service. This w ill facilitate looking up users in the corporate directory and find out details such as
39/47
3/8/12
O acle Re ie
email/telephone/cell no. etc. Notification service already is using this dialog. You can check it under JDeveloper 11g. (Mar 14, 2011 7:29:29 AM)
Siqun Li (siqli, siqun.li@oracle.com ): Will be good to elaborate that. Especially for OSB dev, QA, doc people w ho are not familiar w ith
this feature. Thanks. (Mar 21, 2011 10:22:49 AM)
Does UMS
adapter support
lar...
Open

Mar 21,
2011
9:27:22 AM
Siqun Li (siqli, siqun.li@oracle.com ): Does UMS adapter support large message using SDOM? (Feb 22, 2011 11:15:19 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): We have not receive any requirement for large payload support as of
now . As of now w e just have a requirement of large attachments, but attachments w ill be handled through fabric attachment store. I alw ays
have seen that there is a size restriction in case of emails, posed by email servers...so I am not sure if w e should add large message using
SDOM. (Mar 9, 2011 10:08:52 PM)
Siqun Li (siqli, siqun.li@oracle.com ): So w hat is the message size limit for the email servers w e support? If large message is not
supported, w e should have a section for Non-Feature to indicate this limitation. It w ould help to specify that size limit imposed by email
servers, and state that UMS adapter does not impose message payload size limit and it w ill not support the PayloadSizeTheshold property.
(Mar 21, 2011 9:27:22 AM)
If this is similar
to the "N...
SUJAY BANDYOPADHYAY (sbandyop,

sujay.bandyopadhyay@oracle.com)
Fixed
SUJAY BANDYOPADHYAY
(sbandyop,
May 8,
2011
6:30:05 AM
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): If this is similar to the "No native schema translation
required" checkbox on the adapter Schema Page, w e could use that instead of this. (Feb 22, 2011 9:17:39 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Yes. I w ill remove it from this screen so that there w ill be no confusion.
(Mar 14, 2011 7:35:06 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Assignee changed from 'sshirgup' to 'sband op' (Mar 14, 2011 7:35:06 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Status changed from 'Open' to 'Fi ed' (May 8, 2011 6:30:05 AM)
We need a
section here to
de...
7
Fixed
Mar 14,
2011
6:29:42 AM
Siqun Li (siqli, siqun.li@oracle.com ): We need a section here to describe how inbound w orks in cluster. (Feb 22, 2011 3:15:32 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): section has been added. (Mar 9, 2011 9:55:02 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Status changed from 'Open' to 'Fi ed' (Mar 9, 2011 9:55:02 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I w ill publish the corrected version. (Mar 14, 2011 6:29:16 AM)
What if
outbound
invocation ...
Open

Mar 21,
2011
10:26:26
AM
Siqun Li (siqli, siqun.li@oracle.com ): What if outbound invocation is not in global transaction? What happens then? (Feb 22, 2011 2:57:14
PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Outbound XA mainly solves the problem of false notification. If any of the
participating party fails, the notification w hich is sent to the UMS server w ill be rolled back. Without transaction this w on't be possible. I w ill
add these details to the spec. (Mar 14, 2011 8:59:53 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Assignee changed from 'sshirgup' to 'siqli' (Mar 14, 2011 8:59:53 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): In case of BPEL at least, I believe it alw ays starts a transaction if there is
not a JTA transaction existing and adapter just participates. Now if there is no transaction and if user opts for XA on outbound, then it
should fail w hile enlisting the XAResource. (Mar 21, 2011 3:07:00 AM)
Siqun Li (siqli, siqun.li@oracle.com ): I hope you have capture all this information in the transaction semantics section. If not, please do in
the next version. Thanks. (Mar 21, 2011 10:26:26 AM)
Please define
transaction bo...
Fixed

Mar 14,
2011
8:56:25 PM
Siqun Li (siqli, siqun.li@oracle.com ): Please define transaction boundaries. (Feb 22, 2011 2:56:20 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Added to the new version of spec. (Mar 14, 2011 8:56:25 PM)
I think I had the
question o...
Open
Mar 14,
2011
7:34:14 AM
Siqun Li (siqli, siqun.li@oracle.com ): I think I had the question of w hy payload is entered here. I'm not sure it w as addressed or not. (Feb
10
22, 2011 2:40:10 PM)
Siqun Li (siqli, siqun.li@oracle.com ): Attachment handling semantics should be clearly defined. (Feb 22, 2011 2:40:46 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I w ill remove the payload part from this screen as now w e w ill alw ays be
using a schema to define the payload. Either user defined or opaque as defined on the Message page. I have added the attachment handling
part. I w ill post the update version of the spec. (Mar 14, 2011 7:34:14 AM)
Does attachment
e ie .
Mar 21,
40/47
3/8/12
O acle Re ie
make sense f...
11
Open
2011
6:17:19 AM
Siqun Li (siqli, siqun.li@oracle.com ): Does attachment make sense for IM, SMS, voice? (Feb 28, 2011 1:29:29 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): It's adhering to the Internet Message Format, that used by the Java Mail
API and again by UMS. It might not make sense for some of the channels. (Mar 21, 2011 6:17:19 AM)
Need for details
about this ...
12

Fixed
SUJAY BANDYOPADHYAY
(sbandyop,
May 8,
2011
6:29:52 AM
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): Need for details about this lookup. (Feb 22, 2011 9:15:17 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I have seen this identity lookup w hile using Notificaiton Service under
JDeveloper. You can check it out and see if it's possible or not. (Mar 14, 2011 6:36:14 AM)
If attachment
can be text, t...
Open

Mar 1, 2011
1:22:11 PM
13
Siqun Li (siqli, siqun.li@oracle.com ): If attachment can be text, then there w ill be charset parameter in content type. The
AttachmentType should accommodate that. (Mar 1, 2011 1:22:11 PM)
You mention
VoiceXML here,
b...
14
Mar 13,
2011
7:10:02 PM

Fixed

May 7,
2011
11:16:19
PM
Open

Apr 8, 2011
11:06:59
AM
Siqun Li (siqli, siqun.li@oracle.com ): So here's w hat I gathered from RFC5322. Is this the list of headers adapter is going to support for
filtering? Some of the headers can occur more than once in a message. Is that going to be supported as w ell? * trace * resent-date * resentfrom * resent-sender * resent-to * resent-cc * resent-bcc * resent-msg-id * orig-date * from * sender * reply-to * to * cc * bcc * message-id *
in-reply-to * references * subject * comments * keyw ords * optional-field (Apr 8, 2011 11:06:59 AM)
XA inbound is
very important...
17

SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): Sagar, do w e need to capture the nxsd schema path and
element as jca properties? Other jca adapters do not do this. (Feb 22, 2011 9:10:46 AM)
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): Is this for B2B? (Feb 22, 2011 9:27:56 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Yes, w e need to capture this, as other adapters do not use a fixed
schema like UMS. They alw ays use the same schema defined on the message page. For UMS Adapter, w e w ill be importing the schema
defined on the message page into the static UMS schema. Please check the UMS static schema defined in Appendix section of the spec.
This is not for B2B. (Mar 14, 2011 7:37:44 AM)
SRIMANT MISRA (srm isra, srim ant.m isra@oracle.com ): Why is the path to schema required. Can't this be in the WSDL itself (similar to
attachment schema) (Apr 12, 2011 8:16:43 AM)
SRIMANT MISRA (srm isra, srim ant.m isra@oracle.com ): Assignee changed from 'sband op' to 'sshirgup' (Apr 12, 2011 8:16:43 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): schema path and element information w ill not be captured as
interaction/activation spec properties. (May 7, 2011 11:16:19 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Status changed from 'Open' to 'Fi ed' (May 7, 2011 11:16:19 PM)
So here's w hat I
gathered fr...
16
Fixed
Siqun Li (siqli, siqun.li@oracle.com ): You mention VoiceXML here, but Voice is not one of the the supported inbound messaging types
as you specified in the title for 3.1.1. (Feb 22, 2011 11:23:57 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): removed (Mar 13, 2011 7:09:21 PM)
Sagar, do w e
need to
capture...
15
Open
Mar 14,
2011
8:37:12 PM
Siqun Li (siqli, siqun.li@oracle.com ): XA inbound is very important for OSB. Not sure w hy this is no justifiable use case for BPEL. (Feb
22, 2011 2:54:35 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): We are planning to support LRC type of optimization on inbound. I am little
confused here, as I remember you saying that OSB do not use transactions. (Mar 14, 2011 8:37:12 PM)
We might have
to implement a...
18
e ie .

Fixed
SUJAY BANDYOPADHYAY
(sbandyop,
May 8,
2011
6:29:34 AM
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): We might have to implement a tabular format here w ith the
ability to add/delete endpoint attributes and their values (Feb 22, 2011 9:15:03 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I guess you are right. Again, you can take a call here. I have added this
screen just to give an idea of the w izard. (Mar 14, 2011 6:34:56 AM)
41/47
3/8/12
O acle Re ie
I now have
doubt in the
Atta...
19
Mar 21,
2011
9:18:03 AM
Fixed
Mar 14,
2011
6:28:42 AM
Fixed
Mar 14,
2011
7:38:49 AM
Siqun Li (siqli, siqun.li@oracle.com ): Again, this is only talking about polling mode. Need to describe listening mode. This should be
moved into inbound section. (Feb 22, 2011 2:52:58 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I have moved it in the latest version of spec. (Mar 14, 2011 7:38:49 AM)
Are there jca
properties dif...
22

Siqun Li (siqli, siqun.li@oracle.com ): Please define connection factory properties. (Feb 22, 2011 2:20:18 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Connection Factory for UMS Adapter doesn't hold any properties except a
dummy one. All required properties are defined at the activation level itself. I w ill add this information to the spec. (Feb 28, 2011 12:09:44 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Status changed from 'Open' to 'Fi ed' (Feb 28, 2011 12:09:44 AM)
Again, this is
only talking ...
21
Open
Siqun Li (siqli, siqun.li@oracle.com ): I now have doubt in the AttachmentType definition. If seems you are capturing all the attachment
headers in the message itself. I'm not sure that's the right thing to do. (Mar 2, 2011 4:06:26 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Can you please elaborate a little on your doubt? (Mar 21, 2011 7:26:14 AM)
Siqun Li (siqli, siqun.li@oracle.com ): Tw o things, first attachment headers should stay w ith attachment themselves, please see SOAP
w ith attachment packaging as a reference. Having attachment headers in message body w ould require user to look deep in the body w hen
receiving message, and they w ould have to modify the body a lot to set the attachment header info w hen building the message to send.
Second, JCA framew ork provides attachment to OSB as a map. The key is the contentID for the attachment, the value is the JCA framew ork
Attachment interface. This interface contains all attachment headers as w ell as attachment itself. If you have attachment headers in the
message body, w hen OSB receives the message, w e w ill end up having attachment headers in both message body and message
attachment. (Mar 21, 2011 9:17:45 AM)
Please define
connection fac...
20

Fixed
SUJAY BANDYOPADHYAY
(sbandyop,
Mar 14,
2011
9:04:47 PM
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): Are there jca properties differentiating betw een
decoupling and no-decoupling? (Feb 22, 2011 9:27:08 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Adapter w on't be using Decoupling on inbound. I have removed this in the
updated version of spec. (Mar 14, 2011 9:04:47 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Assignee changed from 'sshirgup' to 'sband op' (Mar 14, 2011 9:04:47 PM)
Please define
message
mappin...
Fixed
Mar 21,
2011
2:39:29 AM
Siqun Li (siqli, siqun.li@oracle.com ): Please define message mapping for Email, SMS, IM, and voice just like inbound. (Feb 22, 2011 2:29:29
PM)
23
Siqun Li (siqli, siqun.li@oracle.com ): The message pattern definition should be in the context of WSDL operation and then schema
definition for message types. (Feb 22, 2011 2:34:09 PM)
Siqun Li (siqli, siqun.li@oracle.com ): The message pattern definition should be in the context of WSDL operation and then schema
definition for message types. (Feb 22, 2011 2:34:11 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Done. (Mar 21, 2011 2:39:29 AM)
I thought w e
have discussed
...
24
Fixed

Mar 14,
2011
6:19:03 AM
Siqun Li (siqli, siqun.li@oracle.com ): I thought w e have discussed the possibility of adapter directly interfacing UMS rather than going
through notification service. What is the conclusion? What's the rationale? (Feb 22, 2011 2:30:44 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Yes, adapter w ill be using UMS directly now . I w ill remove this part. (Mar
14, 2011 6:19:03 AM)
This seems very
BPEL and Fab...
25
e ie .
Open
Mar 21,
2011
6:13:26 AM
Siqun Li (siqli, siqun.li@oracle.com ): This seems very BPEL and Fabric centric. So now you have jca framew ork retry, notification
service retry, and transaction retry. How are these interating w ith each other. Will be good to describe them clearly here. The fact that
notification service is used is w orrisome for OSB. I w ould suggest w e look into the possibility of interfacing w ith the UMS server directly
from adapter. (Feb 22, 2011 3:13:45 PM)
42/47
3/8/12
O acle Re ie
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I have removed notification service related part in the new spec version.
(Mar 21, 2011 6:13:26 AM)
What w ill be the
attachment ...
26
Open
Mar 21,
2011
7:24:05 AM
Siqun Li (siqli, siqun.li@oracle.com ): What w ill be the attachment format in Normalized Message? Will it be a list of javax.mail.Part? (Feb
28, 2011 3:39:21 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): attachments are alw ays handled through fabric attachment manager. We
w ill have an href attribute and bpel/mediator has extension functions to get the content using the key given in the href attribute. (Mar 21, 2011
7:24:05 AM)
Please define: 1.
interacti...
27
Fixed
Mar 21,
2011
1:37:04 AM
Siqun Li (siqli, siqun.li@oracle.com ): Please define: 1. interaction spec properties. 2. Outbound error conditions. 3. binding properties 4.
normalized message properties. (Feb 22, 2011 2:42:10 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I have added necessary details. (Mar 21, 2011 1:37:04 AM)
Sagar, currently
in the adap...
28

Fixed
SUJAY BANDYOPADHYAY
(sbandyop,
Mar 14,
2011
6:25:46 AM
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): Sagar, currently in the adapter schema page, w e use the
checkbox "Native schema translation is not required" to denote w hether native schema translation w ill take place or not. Can w e use this for
this adapter? In this case, the message page w ill alw ays be displayed. (Feb 22, 2011 9:02:10 AM)
Siqun Li (siqli, siqun.li@oracle.com ): I have the same question here. What's the difference betw een "No Translation Required" and
"Native format translation is not required (Schema is Opaque)" option on the messages page? Why do w e need a separate option for this?
(Feb 22, 2011 12:00:16 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I guess, w hen w e select no translation required, opaque schema is used
and w hatever payload, w ould be base64 encoded...right? Do you think it makes sense to just get/set the payload as it is? I w as thinking that
this w ill be very useful, at least on the outbound, w here user just types some message text and the same text w ill be used as a string to set
the email message content.. Then again, your option also makes sense...supposing w e are getting a text, it can be a UTF16 or UTF8 or some
other type encoded... and setting it directly into some XML document might not help if w e need to preserve encoding etc.. And then as you
said, w e might have to go w ith opaque schema. (Mar 10, 2011 1:59:13 AM)
How come the
list of support...
29
e ie .
Mar 21,
2011
6:16:12 AM
Open
Mar 21,
2011
6:11:42 AM
Open
Mar 21,
2011
7:22:15 AM
Siqun Li (siqli, siqun.li@oracle.com ): What does the attachment look like w hen w e received a Normalized Message from UMS adapter
inbound? Does it contain Content ID, Content Type, and Content Encoding just like MIME parts? (Feb 28, 2011 1:44:15 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Yes. (Mar 21, 2011 7:22:15 AM)
I'm assuming the
Message fil...
32
Siqun Li (siqli, siqun.li@oracle.com ): It w ill be good to describe inbound retry and message rejection in the same context along w ith
transaction or reliable message semantics. Basically w e need to understand w here w ill the messages go w hen error occurs in these
cases. (Feb 22, 2011 3:00:06 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I w ill add necessary details. (Mar 21, 2011 6:11:42 AM)
What does the
attachment loo...
31
Open
Siqun Li (siqli, siqun.li@oracle.com ): How come the list of supported content encoding for attachment are limited to just 7bit and
base64? If Disposition is set to w hat w ill be the type for ContentBody? 7bit? base64? If Disposition is attachment, w hat w ould be in
ContentBody element? Will it just have href attribute? (Feb 25, 2011 4:34:34 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 1. I have removed the enumeration type to defined the content encoding.
Instead, I have made is just a string type. 2. Only href attribute for attachment type. No content body. (Mar 21, 2011 6:16:12 AM)
It w ill be good to
describe ...
30

Fixed
SUJAY BANDYOPADHYAY
(sbandyop,
Mar 14,
2011
6:26:50 AM
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): I'm assuming the Message filter properties, java callout
w ill also be added as properties to the inbound jca file. (Feb 22, 2011 9:08:48 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Yes, property name is JavaCalloutImpl. It's a java class name. (Mar 14, 2011
43/47
3/8/12
O acle Re ie
3:12:14 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I have added details on how exactly message filters w ill be added as
activation properties. I w ill soon publish the new version. (Mar 14, 2011 6:26:50 AM)
Notification
naturally is on...
33
Fixed
Mar 16,
2011
1:18:51 AM
Siqun Li (siqli, siqun.li@oracle.com ): Notification naturally is one w ay operation, but you are calling this a sync request response
scenario. (Feb 22, 2011 2:28:42 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I guess, I missed to mention the response part here. UMS server returns a
message identifier after accepting send request. Adapter w ill return this message identifier as a response. This is w hy I am calling it as a
synchronous request. (Mar 14, 2011 6:17:14 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I w ill update the spec accordingly. (Mar 16, 2011 1:18:51 AM)
Can you explain
w hat is Body...
34
Open

Apr 5, 2011
3:59:15 AM
Siqun Li (siqli, siqun.li@oracle.com ): Can you explain w hat is BodyPartIndex and FileName in AttachmentType? (Feb 28, 2011 1:32:55 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): It's the file name associated w ith the body part. Content-Disposition
header field holds this value. If not available, w e w ill get null. (Mar 21, 2011 7:19:28 AM)
Siqun Li (siqli, siqun.li@oracle.com ): Not sure I understand this, w hy do you need bodypartindex, are you trying to keep the order of
attachment? Is that really necessary? What is this filename for? Are you saying there is option to store attachment in a file? If yes, w here
does user specify that option? (Mar 21, 2011 9:22:02 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Status changed from 'Fi ed' to 'Open' (Apr 5, 2011 2:42:00 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): 1. I added body part index considering that in future w e might w ant to give
support to give translation option to any of the inline body part, but I guess, it's increasing the confusion. I w ill remove it altogether. (Apr 5,
2011 3:59:15 AM)
What is the unit

for this Po...
Fixed
Mar 16,
2011
1:18:07 AM
Siqun Li (siqli, siqun.li@oracle.com ): What is the unit for this PollingFrequency here? Is it minutes, seconds? How can I tell? (Feb 22, 2011
35
2:26:38 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): It's alw ays seconds. User w ill specify this value from UI w izard w hile
designing the adapter service. There w ill be different units like seconds, minutes...w eeks. Adapter UI w izard w ill convert the value into
seconds and then specify it in the .jca file. (Mar 14, 2011 3:14:26 AM)
It looks like you
have exclu...
36
Open

Mar 21,
2011
9:44:20 AM
Siqun Li (siqli, siqun.li@oracle.com ): It looks like you have excluded Voice for inbound. What's the reason? (Feb 22, 2011 11:18:45 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Voice is text to speech service and I think this makes sense only on
outbound. Can there be any use case for voice channel on inbound? (Mar 10, 2011 12:42:34 AM)
Siqun Li (siqli, siqun.li@oracle.com ): I'm not familiar w ith UMS service, does it support voice inbound at all? If yes, then I think it w ould
make sense to support it in adapter as w ell. (Mar 21, 2011 9:44:20 AM)
A general
comment, I
w ould l...
37
Fixed
Mar 14,
2011
6:28:32 AM
Siqun Li (siqli, siqun.li@oracle.com ): A general comment, I w ould like to see older version of the spec w ith comments preserved
somehow . This w ill help us to see if all the open issues are resolved or not. Right now , I basically lost all my previous comment and having a
hard time to figure out w hether all my comments have bee addressed or not. (Feb 22, 2011 11:06:36 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): After republishing the doc, all comments kinda get scattered and for that
reason, I again posted a new version. May be I w ill restore the old document and w ill send you the link to check earlier comments. (Feb 24,
2011 7:47:24 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Status changed from 'Open' to 'Fi ed' (Feb 27, 2011 11:58:51 PM)
Should be
outbound
instead o...
Fixed

Mar 14,
2011
6:23:08 AM
38
Siqun Li (siqli, siqun.li@oracle.com ): Should be outbound instead of inbound. (Feb 22, 2011 2:32:56 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Will take care of it. Thanks. (Mar 14, 2011 6:23:08 AM)
e ie .
44/47
3/8/12
O acle Re ie
Please define
w hether
Operat...
39
Fixed
Mar 16,
2011
1:09:07 AM
Siqun Li (siqli, siqun.li@oracle.com ): Please define w hether Operation Mode options "Polling" and "Listener" along w ith polling
frequency w ill be displayed w hen user select outbound send notification, or w ill it be grey'd out. It seems to me, the operation mode
selection should be rendered in the next page. Will Polling Frequency control be grey'd out if user select listener mode? Please define. What
are the unit for Polling Frequency? You show ed minutes, w ill seconds be available also? Please define. (Feb 22, 2011 2:10:47 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Yes, polling and listener details w ill not be show n w hen user selects
outbound operation. About exact UI sequence, final call w ill be w ith UI team. These are just mock up screens given to UI team for they get
the feel. Again, as you said, yes, polling details w ill be grey'd out w hen user selects listener mode Units for polling w ould be seconds,
minutes, hours, days and w eeks. I w ill add these details to the spec. (Mar 13, 2011 7:15:55 PM)
Will endpoint
configuration ...
40
Fixed
Mar 16,
2011
1:09:22 AM
Siqun Li (siqli, siqun.li@oracle.com ): Will endpoint configuration section display different items depending on notification type selection?
Please define w hat w ill be available for SMS and IM. (Feb 22, 2011 2:13:42 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I w ill add these details. (Mar 14, 2011 1:36:07 AM)
Are Filters
stored as
activa...
Fixed
Mar 15,
2011
12:20:32
AM
41
Siqun Li (siqli, siqun.li@oracle.com ): Are Filters stored as activation spec properties? (Feb 22, 2011 2:19:12 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Yes. (Mar 14, 2011 2:00:52 AM)
What happens
to the
messages...
42
Open

Mar 14,
2011
2:03:09 AM
Siqun Li (siqli, siqun.li@oracle.com ): What happens to the messages that are filtered out? Are they dropped? Are they logged? (Feb 22,
2011 2:22:03 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): The filtering happens at UMS level itself. I am not sure if they w ill be
dropped or how and w hen they w ill be dropped. I w ill find exact details on this from UMS team. Adapter w ill not be logging anything as
adapter w on't be aw are of it. (Mar 14, 2011 2:03:09 AM)
Will there be
validation for...
43
Fixed
Mar 16,
2011
1:09:29 AM
Siqun Li (siqli, siqun.li@oracle.com ): Will there be validation for Filters? (Feb 22, 2011 2:15:45 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): We can add a primitive validation at the UI level. I w ill add it to the spec so
that w e don't miss it. (Mar 14, 2011 2:00:39 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): As it's a Java Pattern, w e can try to compile and check for syntax error at
the UI level itself. (Mar 14, 2011 2:10:11 AM)
What are the
available "Fiel...
44
Fixed
Mar 16,
2011
1:17:10 AM
Siqun Li (siqli, siqun.li@oracle.com ): What are the available "Field Name"s for HEADER and METADATA? (Feb 22, 2011 2:16:59 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Header field names w ould be all fields w hich are defined under RFC 5322
- Internet Message Format. About metadata field, please check the link below .
http://dow nload.oracle.com/docs/cd/E17904_01/integration.1111/e10224/ns_rulebasednotification.htm#BACMKROF By the w ay, I have
added this details to the spec now . (Mar 16, 2011 1:17:10 AM)
It w ould be good
to provide ...
Fixed

Mar 16,
2011
1:17:43 AM
45
Siqun Li (siqli, siqun.li@oracle.com ): It w ould be good to provide an example for java callout. (Feb 22, 2011 2:21:15 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I w ill add an example code snippet. (Mar 14, 2011 3:00:31 AM)
Will the message

be removed ...
e ie .
Open

Mar 21,
2011
10:18:43
AM
45/47
3/8/12
O acle Re ie
46
Siqun Li (siqli, siqun.li@oracle.com ): Will the message be removed from server w hen the message is retrieved? (Feb 22, 2011 2:24:51 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Yes, once w e acknow ledge, message w ill be removed. (Mar 14, 2011
3:01:07 AM)
Siqun Li (siqli, siqun.li@oracle.com ): Is this UMS behavior? Is there an configurable option to leave message on server? (Mar 21, 2011
10:18:43 AM)
In previous
version of the
s...
47
Open
Mar 14,
2011
7:42:21 AM
Siqun Li (siqli, siqun.li@oracle.com ): In previous version of the spec, you have mentioned accept 360 project for UMS inbound XA
support. What happened to that? Isn't UMS going to support XA inbound in 12g? If so adapter should take advantage of that. (Feb 22, 2011
2:45:37 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Well, last I heard from them is that they are doing the feasibility study, but I
think it's 90 % confirmed that they w ill not be supporting XA on inbound. We are thinking of giving a LRC kind of optimization on inbound
w hich obviously can be disabled to No Transaction. Please check the latest version of the spec for details, w hich I w ill be posting soon. (Mar
14, 2011 7:42:21 AM)
When does
adapter
acknow ledg...
48
Mar 14,
2011
7:26:30 PM
Open
Mar 14,
2011
7:34:13 PM
Siqun Li (siqli, siqun.li@oracle.com ): Do you mean unavailable? (Feb 22, 2011 2:51:53 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Adapter w ill keep reading messages as long as there are messages
available in the inbox. (Mar 14, 2011 7:34:13 PM)
Will UMS adapter

support con...
50
Open
Siqun Li (siqli, siqun.li@oracle.com ): When does adapter acknow ledge the receive? (Feb 22, 2011 2:53:25 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): Adapter w ill be using the same polling thread as a processing thread.
Adapter w ill acknow ledge only after successful publish to the fabric layer. I w ill add this information. (Mar 14, 2011 7:26:30 PM)
Do you mean
unavailable?
49
Open

Mar 21,
2011
10:13:28
AM
Siqun Li (siqli, siqun.li@oracle.com ): Will UMS adapter support container managed sign-on? (Feb 22, 2011 2:32:34 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): No there is no concept of container managed sign-on. user
name,passw ord mentioned here is the static configuration part that to be carried out on the UMS side. (Mar 14, 2011 6:22:44 AM)
Siqun Li (siqli, siqun.li@oracle.com ): Is there a w ay to pass credential through UMS API? If yes, then w e should consider supporting
container managed signon. This is a very useful feature for system to system integration. (Mar 21, 2011 10:13:21 AM)
This is
inconsistent
w ith in...
Fixed

Mar 14,
2011
6:28:08 AM
51
Siqun Li (siqli, siqun.li@oracle.com ): This is inconsistent w ith inbound operations page. For inbound, the notification type selection are
on a separate page. I think it should be on a separate page. (Feb 22, 2011 2:35:48 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): You right. (Mar 14, 2011 6:28:08 AM)
Sagar, for
consistency
w ith ...
52
Fixed
SUJAY BANDYOPADHYAY
(sbandyop,
Mar 14,
2011
6:25:26 AM
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): Sagar, for consistency w ith the inbound operation, w e
should move the "Type of Notification" to the next page. (Feb 22, 2011 9:05:12 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): okay..I guess this w ould be your call any w ay. (Mar 14, 2011 6:24:09 AM)
Again, this is
inconsistent ...
e ie .

Open
Mar 21,
2011
10:21:38
AM
46/47
3/8/12
O acle Re ie
53
Siqun Li (siqli, siqun.li@oracle.com ): Again, this is inconsistent w ith inbound in w hich you had endpoint configuration on the same page
as operations selection. I think endpoint attributes configuration should be on a separate page. (Feb 22, 2011 2:38:30 PM)
Siqun Li (siqli, siqun.li@oracle.com ): Again, same question for "Payload Translation Required" option. (Feb 22, 2011 2:38:59 PM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I w ill be removing Payload Translation Required option altogether. Again,
this is just a mock up UI and UI team w ill make the final call on w here to put w hat. (Mar 14, 2011 6:33:16 AM)
Siqun Li (siqli, siqun.li@oracle.com ): Will there be a UMS adapter UI functional spec then? Or w ill UI team just decide the UI look and feel
w ithout your input? I hope you'll have a say in that. (Mar 21, 2011 10:21:38 AM)
Need to capture
attributes i...
54

Fixed
SUJAY BANDYOPADHYAY
(sbandyop,
May 8,
2011
6:29:03 AM
SUJAY BANDYOPADHYAY (sband op, suja .band opadh a @oracle.com ): Need to capture attributes in the adapter w izard related to
SMS, IM & Voice. (Feb 22, 2011 9:23:52 AM)
Sagar Shirguppi (sshirgup, sagar.shirguppi@oracle.com ): I have added necessary details to the new version of spec. (Mar 21, 2011
6:14:16 AM)
e ie .
47/47

Ums Adapter

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Ums Adapter

Enviado por

Direitos autorais:

Formatos disponíveis

3/8/12

UMS Adapter : Functional Specification Review

Wednesday, March 7, 2012 10:23:56 PM PST

Functional Specification for Oracle UMS Adapter,

Project ID: UMS Adapter

Document Change History

Version Change Description

Added UM S related details.

User Interface details to design the Adapter service.

Incorporated Srimant's feedback

Incorporated Kalpak s feedback

.o acle.com/ e ie /p in able- ie .do

Principal Product M anager

3.1.1.1 Email Driver Configuration on UMS side. 6

3.1.1.3 Message Mapping 17

3.1.4.1 Email Driver Configuration on UMS side. 28

3.1.4.8 Transaction Semantics on the Outbound 40

.o acle.com/ e ie /p in able- ie .do

High Level Requirements

The requirement is to have a generic, comprehensive JCA based UMS Adapter.

The Adapter should act as a Service Consumer as well as Provider.

The Adapter Should support SSL for Email channel.

The Adapter should be integrated with Translator Infrastructure (NXSD).

.o acle.com/ e ie /p in able- ie .do

Assumptions and Constraints

UMS POJO Client API. We have it starting from PS2.

Features Scoped Out or Deferred to a Future Release.

Concepts & Terminology

JCA Java Connector Architecture

SSL Secure Socket Layer

Support for Inbound Communication

Support for Outbound Communication

.o acle.com/ e ie /p in able- ie .do

received from UMS server after accepting the notification.

Adapter should give an option to send email as an attachment.

Adapter should be able to send notification to multiple recipients.

User should be able to add proprietary mail headers to an outgoing message.

Fault Handling/Error Hospital

Support for fault-policy/fault-bindings for inbound and outbound.

Support for retry logic for outbound interactions through fault-policies.

Retry logic for outbound interactions through JCA retry mechanism.

Inbound Receive Notification (Email, SMS, IM) - Polling or through a Listener.

Designing the Adapter Service and BPEL process.

Email Driver Configuration on UMS side.

.o acle.com/ e ie /p in able- ie .do

IncomingMailServer - Host Name of incoming mail server - stbeehive.oracle.com

IncomingMailServerPort - Port Number of IMAP4

IncomingMailIDs - The e-mail addresses corresponding to the user names. - first.last@oracle.com

IncomingUserPasswords - passwords corresponding to the user names.

Design Adapter Service and the BPEL Process.

User enters ReceiveNotification in the Service Name Field as shown below.

.o acle.com/ e ie /p in able- ie .do

Selects Inbound Receive Notification as the operation type.

.o acle.com/ e ie /p in able- ie .do

.o acle.com/ e ie /p in able- ie .do

On the Messages Page, user enters message related details.

.o acle.com/ e ie /p in able- ie .do

.o acle.com/ e ie /p in able- ie .do

.o acle.com/ e ie /p in able- ie .do

.o acle.com/ e ie /p in able- ie .do

On the Java Call

Check the example JavaCallout code snippet below.

.o acle.com/ e ie /p in able- ie .do