WS addressing inside OSB Message Flow

Hi There,
We are trying to work with the ws-addressing structure inside the Message Flow of a Proxy Service, but i don't know how to define in the wsdl to see the structure of the ws-addresing in the Header, i need to see it to obtain some values in the "Assign" task of a Message Flow.
Can you help me in this issue?
Regards
Yuri

ws-addressing is supported in conjunction with WS transport.You should attach a required policy
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/security/ws_policy.html
Manoj

Similar Messages

How to convert XML to Binary in OSB Message flow

Dear All,
Can you please help me in converting XML to Binary in OSB Message flow.
Please help.
Thanks,

ah ok, then you have to apply a transformation from XML to some fixed length format, EDI style
probably you have 2 options: the traditional MFL
http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/consolehelp/mfls.html
or the (probably) more supported nXSD with a JCA adapter
http://docs.oracle.com/cd/E23943_01/integration.1111/e10231/nfb.htm
I will let you digest this info and then we can continue.
There are a number of threads in this forum on whether one technology is better than the other (as usual, google can assist you)

Functionality of IF in OSB message flow

Hi Team,
am just confused about the functionality of IF in OSB message flow, either in a proxy or in a split-join.
for example consider the following scenarios in if-then stage,
1. I write the condition as status="yes", then some process will be done.
2. but what if I write just status? what can be the functionality of IF here?
Please suggest the needful thanks in advance.
-Pruthvi Raj.

but what if I write just status? what can be the functionality of IF here?
Then the $status variable is evaluated. If it is not an empty sequence (), it is considered true (AKA exists).
In other words, if there is anything in the $status variable, it is true. Unless it is a boolean false, of course, but all variables in OSB are strings, so that is not going to happen.
Please note that Split-Join AKA Flow is a different codebase. Its variables are typed (vs strings in OSB), and hence if will behave differently for false value.
Vlad @ genericparallel.com

Replacing default namespace in OSB message flow

I'm in the process of setting up a simple OSB proxy and could use some help figuring out how to change a default namespace in the response from the business service.
The proxy and business service use different namespaces which we'll call "http://foo.com/namespace/proxy" and "http://foo.com/namespace/business". In my routing request message flow, the contents of $body look like this and I'm able to use a Rename action with XQuery expression "./sof:*" to change "http://foo.com/namespace/proxy" to "http://foo.com/namespace/business":
<sof:Execute xmlns:sof="http://foo.com/namespace/proxy">
<sof:adminName>MyAdaptor</sof:adminName>
<sof:request>
[escaped payload omitted]
</sof:request>
</sof:Execute>
This works fine, but in the response message flow, I need to revert the namespace and am having difficulty because the response uses a default namespace instead of using a prefix:
<ExecuteResponse xmlns="http://foo.com/namespace/business">
<ExecuteResult>
[escaped payload omitted]
</ExecuteResult>
</ExecuteResponse>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
Can anyone tell me what I'm doing wrong, or suggest a different approach? Assume that changing the calling application or business service is not an option.
Thanks!

>
If I define a prefix P2L in the expression editor to correspond to "http://foo.com/namespace/business", I'm able to reference the ExecuteResponse element as "./P2L:ExecuteResponse", but then I get stuck.
If I try use a Rename action to change the namespace for "./P2L:*", only the ExecuteResponse element is renamed to <sof:ExecutResponse xmlns:sof="http://foo.com/namespace/proxy">. Upstream in the calling application, there's an XML stream reader exception because (I assume) ExecuteResult is not found and parsed.
>
You pattern "./P2L:\*" matches just one element so it's ok that the payload's namespace wasn't touched. If you want to rename namespace for all elements try "//P2L:*". However, I'm not sure whether this is what you want. Try do describe what you do, what you want and what you get instead.
>
I also tried using a Replace action against "./P2L:ExecuteResponse/@xmlns" to replace its contents with "http://foo.com/namespace/proxy". I also tried "./P2L:ExecuteResponse/@P2L:xmlns". Neither worked.
>
I think it's not a good approach to replace content of xmlns as this attribute is not a common xml attribute.

Adding alert activity in OSB message flow urgent

hi,
i added an alert activity in my OSB proj message flow to monitor the process . after deploying the proj in console, i gave inputs. but i am not able to see the alert in operations>dashboard>pipeline alerts . no alert has been written in dashboard.
i have mentioned the alert destination, for alert logging option i have selected yes. can anyone pls hlep he in this issue.
thanks

Did you enable Pipeline Alerts in the Operational Settings tab of the Proxy? If yes, also select the appropriate level based on the Alert level you had set within the message flow.
Also check the in the SB Console > Operations > Global Settings , that the Enable Pipeline Alerting is selected.
Thanks,
Patrick

How to retrieve MQMD Header in OSB Message Flow Pipeline

Hi ,
My Proxy Service is reading a non-xml message from MQ-Queue . The format of the message can be different , which is recognized by a MQMD header : applicationType . Putting application populates this header .
I want to get the value of this MQMD header , in message flow ,to decide which MFL file needs to be applied . But the problem is that "Transport Headers" Action header gives only option to add new headers , not to retrieve the existing ones . Please help me.

You can access the MQ transport headers in the assign/replace actions using the relative xpath of the $inbound variable. This is available for any transport.
Please find a snapshot @ https://dl.dropboxusercontent.com/u/19901533/access_inbound_mqheaders.JPG
Also ensure that you configure the Get All Headers property+ to yes on the Transport Configuration of your proxy.
Thanks,
Patrick

How to do Async call in OSB message flow

I am calling a service from OSB layer synchronously and when this service gives a response, I am forming another request with this response and storing it in a variable now I want to call another service asynchronously by using this variable. Service call out is not supporting one way call.
Please suggest a suitable way to do this.

Use publish action. It is designed fire and forget type of use-cases
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html
Manoj

OSB: How to get stored in sbconsole xml document in message flow

Hi
I created a xml document (say ram.xml) as a XML document utility resource in OSB sbconsole.
I want to refer this in message flow with fn:doc. Unlike xquery i can't assign ram.xml to a variable.
I tried fn:doc("/home/osbuser/user_projects/domains/domain_name/osb/config/core/ram.xml") and fn:doc("file:////home/osbuser/user_projects/domains/domain_name/osb/config/core/ram.xml") it didn't work!
I know if i store this xml as a xquery, it will get assigned to a variable. But i am just curious to see how fn:doc works!
Any light !

The reason for this is to eliminitate each assign action for each of XMLs that I use. Each assign gets converted into a xml bean and thats overhead.
If this fn:doc() works, what i am planning is to use fn:doc() inside my xquery transformations directly, without using assign action to load XML.
Also message flow will become somewhat cleaner.
fn:doc() has to be used in a way that it uses relative path to access xml and not complete path (starting from /home/user_doamains/..) because development and production environment domain names are different. Using relative path, code can migrate without any change across environments.

How to return "HTTP/1.0 401 Authorization Required" from OSB's Message Flow

How can I return "HTTP/1.0 401 Authorization Required" header from OSB's Message Flow?
Using of "HTTP Transport -> Authentification" is not possible, because I need flow condition. Transports Headers activity from design palette doesn't allow to send such headers.
Practical usage: request for kerberos ticket by sending two headers: 401 and WWW-Authenticate: Negotiate...

Can you briefly expand the use case for better understanding?
HTTP Client---> Hand Shakes or what ever ----> HTTP Proxy (OSB )---> Pipeline----
Philosophy behind pipeline is that it is designed to work on the request. Correct me if I'm wrong.
What you are asking is ability to control the hand shake either in Pipeline or some way during proxy configuration. Unfortunately there is no configuration that is exposed for HTTP proxies in OSB to control that behavior.
Manoj

OSB:Publish to business service with for each in osb proxy message flow

Hi,
I have an external application that will make a call to my web-service and post a message to my queue "A" and i need to model my osb component such that it picks the message from that queue " A"and posts it to another queue "B". All this is done without any BPEL involved.
for publishing the message i have created a business service that publishes a msg to the queue A and my proxy service is modelled such that it subscribes to this same queue A and publishes the msg to another business service (that posts it to a queue B).
Everything is working fine but i have an issue in modelling my proxy message flow. If an external application sends a bulk msg i need to post the message one by one to my queue B. I have used for-each and Publish to BS but the msg doesn't get posted one by one. i know i am missing something please help me out.
SOA Suite Version - 11.1.1.3

Are you sure that your for-each definition is correct? Does the flow within the for-each get executed multiple times?
You can check this by logging the variable to which you assign the message in the for-each. Don't forget to put the log level to Error, so you're sure that it's logged.
Let's say you get a list of persons like the following xml in a variable personList
<Persons>
<Person>Glenn</Person>
<Person>Prasanth</Person>
</Persons>
Your for-each definition should be the following.
For each variable: person
XPath: +./Person+
In Variable: personList
You don't mention the Persons element in the XPath expression since it is the root element of the XML. The root element is represented by . (dot).
In the for-each, the variable person can be used like any other variable.

ON PREM Outbound emails showing in dummy non-configured office 365 account message flow trace

Dear Community,
We have an on-prem exchange 2013 server and an office 365 account which is completly standalone.
Whilst the office 365 account is standalone, it does feature the email address we use for on-prem (Ie. the domain name in office 365 account is not active for any office 365 services however has passed ownership verification thus it's just sitting there)
We DON'T use EOP nor do we have any connector rules on our on-prem system that go to office 365 however when I randomly went into the 'Message Flow Trace' section in our office 365 account, there is recorded outbound mail which was sent from our On-prem
server.
The ONLY mail that was recorded in the message Trace in Office 365 was emails we had sent from On-prem to other office 365 accounts (For example btconnect.com, and some of our clients whom also use office 365) .
How is office 365 picking up mail we've sent from our On-Prem server? Is there integration out of the box in exchange 2013 which auto interfaces with office 365? What on earth has happened here?
I'm really confused.
-------- For troubleshooting purposes...
Headers in the email which arrived in my personal office 365 account from the ON-PREM SERVER
Received: from AMSPR05MB065.eurprd05.prod.outlook.com (10.242.89.142) by
DBXPR05MB079.eurprd05.prod.outlook.com (10.242.138.22) with Microsoft SMTP
Server (TLS) id 15.1.93.16 via Mailbox Transport; Thu, 5 Mar 2015 16:16:31
+0000
Received: from DBXPR05CA0014.eurprd05.prod.outlook.com (10.255.178.14) by
AMSPR05MB065.eurprd05.prod.outlook.com (10.242.89.142) with Microsoft SMTP
Server (TLS) id 15.1.99.14; Thu, 5 Mar 2015 16:16:30 +0000
Received: from DB3FFO11FD028.protection.gbl (2a01:111:f400:7e04::145) by
DBXPR05CA0014.outlook.office365.com (2a01:111:e400:9434::14) with Microsoft
SMTP Server (TLS) id 15.1.106.15 via Frontend Transport; Thu, 5 Mar 2015
16:16:29 +0000
Received: from emea01-am1-obe.outbound.protection.outlook.com (157.56.112.128)
by DB3FFO11FD028.mail.protection.outlook.com (10.47.217.59) with Microsoft
SMTP Server (TLS) id 15.1.99.6 via Frontend Transport; Thu, 5 Mar 2015
16:16:28 +0000
Received: from DB4PR04CA0010.eurprd04.prod.outlook.com (25.160.41.20) by
DB3PR04MB236.eurprd04.prod.outlook.com (10.242.130.24) with Microsoft SMTP
Server (TLS) id 15.1.99.14; Thu, 5 Mar 2015 16:16:26 +0000
Received: from DB3FFO11FD040.protection.gbl (2a01:111:f400:7e04::184) by
DB4PR04CA0010.outlook.office365.com (2a01:111:e400:9852::20) with Microsoft
SMTP Server (TLS) id 15.1.106.15 via Frontend Transport; Thu, 5 Mar 2015
16:16:26 +0000
Received: from mail.localdomainhere (<IP OF OUR ON-PREM SERVER GOES HERE>) by
DB3FFO11FD040.mail.protection.outlook.com (10.47.217.71) with Microsoft SMTP
Server (TLS) id 15.1.99.6 via Frontend Transport; Thu, 5 Mar 2015 16:16:25
+0000
Received: from INT-EX-01.localdomainhere (192.168.142.20) by
INT-EX-01.localdomainhere (192.168.142.20) with Microsoft SMTP Server (TLS) id
15.0.913.22; Thu, 5 Mar 2015 16:15:55 +0000
Received: from INT-EX-01.localdomainhere ([fe80::aca4:88cf:3eaf:57dc]) by
INT-EX-01.localdomainhere ([fe80::aca4:88cf:3eaf:57dc%12]) with mapi id
15.00.0913.011; Thu, 5 Mar 2015 16:15:55 +0000
From: Jake Ives <[email protected]>
To: Jake Ives <[email protected]>
Subject: Test01
Thread-Topic: Test01
Thread-Index: AdBXX6dyI5u99OGoSKmXroKKyMA3Tg==
Date: Thu, 5 Mar 2015 16:15:54 +0000
Message-ID: <[email protected]>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.142.73]
Content-Type: multipart/related;
boundary="_004_081f834d85b7436193fa887613b9dac7INTEX01localdomainhere_";
type="multipart/alternative"
MIME-Version: 1.0
Return-Path:
[email protected]
X-EOPAttributedMessage: 1
Received-SPF: Pass (protection.outlook.com: domain of domain.com
designates <IP OF ONPREM SERVER HERE> as permitted sender)
receiver=protection.outlook.com; client-ip=<IP OF OUR ON-PREM SERVER GOES HERE;
helo=mail.domain.co.uk;
Authentication-Results: spf=pass (sender IP is <IP OF OUR ON-PREM SERVER GOES HERE>)
[email protected]; ives.gb.net; dkim=none (message not
signed) header.d=none;ives.gb.net; dkim=none (message not signed)
header.d=none;ives.gb.net; dmarc=none action=none header.from=domain.com;
X-Forefront-Antispam-Report-Untrusted: CIP:<IP OF ON PREM SERVER HERE>;CTRY:GB;IPV:NLI;EFV:NLI;BMV:0;SFV:NSPM;SFS:(10019020)(438002)(189002)(199003)(71364002)(87936001)(2656002)(98436002)(92726002)(102836002)(108616004)(19625215002)(19618635001)(512954002)(92566002)(229853001)(107886001)(66926002)(18206015028)(84326002)(16796002)(19300405004)(450100001)(19580395003)(2900100001)(77156002)(15974865002)(62966003)(5250100002)(5310100001)(99936001)(15395725005)(16236675004)(110136001)(17760045003)(67866002)(86362001)(19617315012)(19627595001)(15975445007)(19580405001)(54356999)(22756005)(50986999)(6806004)(46102003)(74482002)(106466001)(33646002)(7099025)(24736002)(15669805003);DIR:OUT;SFP:1102;SCL:1;SRVR:DB3PR04MB236;H:mail.domain.co.uk;FPR:;SPF:Pass;MLV:ovrnspm;MX:1;A:1;PTR:mail.domain.co.uk;LANG:en;
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DB3PR04MB236;UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB065;
X-Microsoft-Antispam-PRVS: <[email protected]outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(601004)(5001007)(5005006);SRVR:DB3PR04MB236;BCL:0;PCL:0;RULEID:;SRVR:DB3PR04MB236;BCL:0;PCL:0;RULEID:(601004);SRVR:AMSPR05MB065;BCL:0;PCL:0;RULEID:;SRVR:AMSPR05MB065;
X-Forefront-PRVS: 05066DEDBB
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR04MB236
X-MS-Exchange-Organization-MessageDirectionality: Incoming
Received-SPF: Fail (protection.outlook.com: domain of domain.com does not
designate 157.56.112.128 as permitted sender)
receiver=protection.outlook.com; client-ip=157.56.112.128;
helo=emea01-am1-obe.outbound.protection.outlook.com;
Authentication-Results: spf=fail (sender IP is 157.56.112.128)
[email protected];
X-Forefront-Antispam-Report: CIP:157.56.112.128;CTRY:US;IPV:NLI;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(339900001)(489007)(189002)(71364002)(199003)(102836002)(92726002)(15975445007)(92566002)(17760045003)(62966003)(106466001)(15395725005)(16236675004)(77156002)(110136001)(107886001)(450100001)(5310100001)(229853001)(22756005)(98436002)(2900100001)(5250100002)(19625215002)(66926002)(99936001)(33646002)(15974865002)(19617315012)(19627595001)(67866002)(54356999)(108616004)(19300405004)(19618635001)(87836001)(2656002)(18206015028)(85426001)(512954002)(86362001)(6806004)(46102003)(74482002)(84326002)(19580395003)(50986999)(19580405001)(7099025)(24736002)(15669805003);DIR:INB;SFP:;SCL:1;SRVR:AMSPR05MB065;H:emea01-am1-obe.outbound.protection.outlook.com;FPR:;SPF:Fail;MLV:ovrnspm;MX:1;A:1;PTR:mail-am1on0128.outbound.protection.outlook.com;LANG:en;
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB3FFO11FD028.protection.gbl
X-MS-Exchange-Transport-CrossTenantHeadersPromoted: DB3FFO11FD028.protection.gbl
X-MS-Exchange-Organization-Network-Message-Id: 927151e3-02c4-4c46-5539-08d22576df82
X-MS-Exchange-Organization-AVStamp-Service: 1.0
X-MS-Exchange-Organization-SCL: 1
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Mar 2015 16:16:28.9728
(UTC)
X-MS-Exchange-CrossTenant-Id: cd52bfe2-da2e-446d-b8f1-e78db861d489
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bfa61dad-1543-4f3b-8075-03498e9f4fcb;Ip=[IP OF ON PREM SERVER HERE]
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR05MB065
X-MS-Exchange-Organization-AuthSource: DB3FFO11FD028.protection.gbl
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Transport-EndToEndLatency: 00:00:03.5565465

MX records are not set to office 365, the MX is pointing directly to the on-prem exchange server.
The problem is; Office 365 Mail Delivery Trace is displaying mail we've sent via our On-Prem server - We are having trouble understanding why this is happening.
To clarify, the message tracer in Office 365 is displaying outbound mail (Which for example, a user has sent out from their outlook) BUT only outbound mail which is being sent to other office 365 users.
We do not have mail on office 365, only on-premise hence the reason why we are flabbergasted to why the mail we are sending out would be displaying on the office 365 message tracer.
To further clarify, we are only seeing addresses in the office 365 message trace which belong to recipients whom use office 365 for their mail.
Hope this makes sense.
getting messy O365 users to another O365 you mean?
You mentioned if they send email using their MS Outlook Client.
I'd suggest you to send another email to the same recipient but using OWA
There may have been an office 365 connector in Outlook.
Where Technology Meets Talent

Regarding Message Flow in XI

Hi Experts,
I was go through the Blog given by Siva Maranani
/people/siva.maranani/blog/2005/05/25/understanding-message-flow-in-xi
But in this After sending the Xi Message from send Queue to Integration Engine...
What wi be the process inside this IE.
Please let me know
Regards
Khanna

But as per my knowledge in the IS the Pipeline services wil be done( Includes Receiver det, Interface Det, Mapping, Logical rout, Tech. routing, Call Adapter, Message Split )
It means there is no further process inside the IE??????????
Messages received at the Integration Server are processed through a defined series of steps called Pipeline Services. These pipeline services are part of Integration Engine which in turn is a part of Integration Server
Only the XI Adapter wil pick the Xi msg from Send Queue to IE.......Thats it?????/
Yes. Thats the main task of XI Adapter. It also does the SLD lookup.

then this IE wil pass this XI Msg to the IS ..... Right????????
As mentioned, IE is part of IS
Regards,
Prateek

Message flow in XI

Hi all,
pls can anybody send me the link or documents for message flow in XI....and also it will be helpful if u send me some faqs and answers on XI..
thanks & regards,
Santosh

Hi Santosh,
The message flow is like below
1. From sender it reached Sender Adapter ( Communication
channel ).
2. From AE it goes to IE , inside IE it go through Pipeline steps.
3. From IE it will go to recievr side AE.
4. From reciever's AE it goes to Reciever's system.
- Satish

Use logging action in message flow

Hi,
I have created a log action in my message flow. By default all my log messages goes to AdminServer.log.
Instead, i want the messages to be logged into a different file using log4j.
How do i achieve this?
Thanks.

Re: OSB Log file
Re: Using Log4J with OSB to Store Audit Information
Regards,
Anuj

Getting servername or hostname in the proxy service message flow

Is there a way to get the hostname in the OSB proxy service message flow without doing a java call out calling a POJO class?

Thanks for the reply!
I do not see any element in the inbound variable representing hostname
Here is how the inbound variable looks like
<con:endpoint name="ProxyService$GatewaySecurity$ProxyService$GatewayProxy" xmlns:con="http://www.bea.com/wli/sb/context">
<con:service>
<con:providerName>GatewaySecurity/resources/X509v3ServiceKeyProvider</con:providerName>
</con:service>
<con:transport>
<con:uri>/GatewaySecurirty/ProxyService/GatewayProxy</con:uri>
<con:mode>request-response</con:mode>
<con:qualityOfService>best-effort</con:qualityOfService>
<con:request xsi:type="http:HttpRequestMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<tran:headers xsi:type="http:HttpRequestHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
<http:Content-Type>application/soap+xml; charset=utf-8</http:Content-Type>
</tran:headers>
<tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">utf-8</tran:encoding>
<http:query-parameters/>
</con:request>
<con:response xsi:type="http:HttpResponseMetaData" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<tran:headers xsi:type="http:HttpResponseHeaders" xmlns:tran="http://www.bea.com/wli/sb/transports">
<http:Content-Type>application/soap+xml</http:Content-Type>
</tran:headers>
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">0</tran:response-code>
</con:response>
</con:transport>
<con:security>
<con:transportClient>
<con:username><anonymous></con:username>
</con:transportClient>
</con:security>
</con:endpoint>>

WS addressing inside OSB Message Flow

Similar Messages

Maybe you are looking for