Forum Replies Created
-
AuthorPosts
-
November 4, 2008 at 4:25 AM in reply to: The Messaging Engine encountered an error during the processing of one or more inbound messages. #21142
what is the solution
I did the change to use WCF-Custom now. When I try to set security, I get tricky. Not to know how to set up them, since I canot find out the same field for WCF-WSHttp security setting.
can you let me where “security mode” and “Message Client Credential type” setting.
The service is expecting Soap 1.1 (Content Type: text\xml), where the WsHttp binding uses Soap 1.2 (Content Type application/soap+xml)
You may like to use the customBinding, instead of WsHttp
On Binding Tab, Binding Type = customBinding, textMessageEncoding -> messageVersion = Soap11A big gotcha will be the message level security, you will need to right click CustomBindingElement -> Add extension -> security. This is where it gets tricky. You are dealing directly with the security extension ( the WsHttp binding hides most of this).
Might be easier if you ask the service provider to support Soap1.2
Sorry, my VS did not have SvcConfigEditor. what i did is to check the event log of BizTalk as following.
There is a warning message as following:
======
The adapter failed to transmit message going to send port “GXS_WebService_MailList_1.0.0.0_Test_GXS_WebService.Orchestration_Port_GXS_WebService_1abe5266517474a2” with URL “https://ws.betagrid.gxs.com:443/smg/ws_comm/mailboxList“. It will be retransmitted after the retry interval specified for this Send Port. Details:”System.ServiceModel.ProtocolException: Content Type application/soap+xml; charset=utf-8 was not supported by service https://ws.betagrid.gxs.com/smg/ws_comm/mailboxList. The client and service bindings may be mismatched. —> System.Net.WebException: The remote server returned an error: (415) Unsupported Media Type.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
— End of inner exception stack trace —Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.DoOperation(SecuritySessionOperation operation, EndpointAddress target, Uri via, SecurityToken currentToken, TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionSecurityTokenProvider.GetTokenCore(TimeSpan timeout)
at System.IdentityModel.Selectors.SecurityTokenProvider.GetToken(TimeSpan timeout)
at System.ServiceModel.Security.SecuritySessionClientSettings`1.ClientSecuritySessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open()Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open()
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.GetChannel[TChannel](IBaseMessage bizTalkMessage, ChannelFactory`1& cachedFactory)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.SendMessage(IBaseMessage bizTalkMessage)”.======
What error are you getting? The way to debug this is to use a tracing tool to view the SOAP envelope that BizTalk is sending. You might be able to use Fiddler for this, or you could enable WCF tracing. Check out this link for some instructions on WCF tracing: http://blogs.msdn.com/madhuponduru/archive/2006/05/18/601458.aspx. You would need to enable the tracing in the BizTalk config file (BTSNTSVC.exe.config).
November 3, 2008 at 7:22 PM in reply to: question with windows authentication with BTS server #21135Yes, BizTalk has a provision for carrying the original user account context along with the message (kind of). It is called single sign-on (SSO). It is designed to allow you to store mappings between AD accounts and other system accounts, such as databases or mainframes. Many BizTalk adapters support SSO and will automatically look up the sign-on credentials from SSO and use them to call out to external systems. In an SSO scenario, when BizTalk receives a message it attaches an SSO ticket to the message that outbound adapters can use to perform SSO lookups. You might be able to use this SSO ticket to flow the original user credentials along with the message. Unfortunately, this is pretty complicated to set up, but it is probably your best bet to get your scenaio working. I’ve never had this specific requirement, so I don’t know exactly how to do it. This link would be a good place to begin research: http://msdn.microsoft.com/en-us/library/ms942599.aspx
A good workaround might be to stand up a WCF service in front of (or instead of) BizTalk and do the lookup there where user impersonation is easy.
The official way to add conditional logic to an orchestration is to use a decide shape. However, you can add an if/else statement to an expression shape, you just don’t get intellisense for it. The if/else code would be exactly like it would in C#. For some reason this doesn’t work in a message assignment shape though.
Did you install WSE SP 1 & 2? (Not the adapter, just WSE) I think you need to install both of these.
Thank you very much for your great help.
I have tried on WSHttp setting. Howver it still not working now. What I set is following
1. Gerneral tab: Address https://ws.betagrid.gxs.com:443/smg/ws_comm/mailboxList
2. Security tab:
Security Mode = TransportWithMesssageCredental
Message Client Credential type = user name
Alogorithm suit = Basic256
user name=[email protected]
password = password
Sample of SOAP is expected as following:
[SOAP] request to https://ws.tradinggrid.gxs.com:443/smg/ws_comm/getLogEntries
<?xml version=”1.0″ encoding=”UTF-8″?>
<soap:Envelope xmlns:n=’http://icslinux7/gxs.ws.docManagement’
xmlns:soap=’http://schemas.xmlsoap.org/soap/envelope/’>
<soap:Header>
<wsse:Security xmlns:ds=’http://www.w3.org/2000/09/xmldsig#’
xmlns:wsse=’http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd’
xmlns:wsu=’http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd’
xmlns:xenc=’http://www.w3.org/2001/04/xmlenc#’>
<wsse:UsernameToken>
<wsse:Username>[email protected]</wsse:Username>
<wsse:Password>gxsadmin</wsse:Password></wsse:UsernameToken>
</wsse:Security>
</soap:Header>
<soap:Body soap:encodingStyle=’http://schemas.xmlsoap.org/soap/encoding/’>
<n:getLogEntries>
<docID>36sec1003thq73bv0000d0ye</docID>
</n:getLogEntries></soap:Body>
</soap:Envelope>
Did I set the right parameter?
There is no guarantee when the second message will receive a message, but the atomic scope definitely doesn’t have to finish immediately. It even has a timeout property!
The engine doesn’t dehydrate the orchestration while within the atomic scope, and this eats some resources.
Otherwise, I also don’t understand why this restriction on atomic scopes exists.
Regards,
Igor
Russell,
Thanks for the reply.
Yes. I have that kind of set up. followed Richard’s blog (http://seroter.wordpress.com/2007/01/03/debatching-inbound-messages-from-biztalk-sql-adapter/)
In the document schema, I quick promote the field element (Code) which creates the PropertySchema with that field
When I deploy and run and look at the supended messages the Code property is not there (not promoted).
Cheers,
Walid
November 2, 2008 at 9:28 PM in reply to: question with windows authentication with BTS server #21126Thanks for the reply Ruselw, so you said BizTalk does have a provision for passing the user account context along with the message,can you please tell me how to do this
Thanks
November 2, 2008 at 6:20 PM in reply to: question with windows authentication with BTS server #21124No, BizTalk will use the BizTalk service account context. You can specify a SQL login in the connection string if you want. BizTalk does have a provision for passing the user account context along with the message: Single Sign-On (SSO). Many BizTalk adapters have SSO support, although maps and functoids do not. Another option might be to use the SQL adapter instead of a map to access SQL Server. The SQL adapter and SSO might be a solution for you. (I don’t know whether the SQL adapter supports SSO, you would need to do some research)
November 2, 2008 at 6:08 PM in reply to: BizTalk Server WCF Receive Port (WCF-Custom) – usupported operation #21123Russell,
I was able to create a recieve location (with single operation SendMessage) using Microsoft.BizTalk.XLANGs.BaseTypes.Any using the WCF service publish wizard. In the proxy the service operation is exposed as SendMessage(object part) and when I call the operation get an serialization exception – looks like I am not passing in the parameters correctly to the operation.
XmlDocument
doc = new XmlDocument
();doc.Load(
“c:\\mydoc.xml”);
Message newMsg = Message.CreateMessage(MessageVersion.Default,“SendMessage”, new XmlNodeReader(doc));
client.SendMessage(newMsg);
I get an “Error processing request:Type ‘System.ServiceModel.Channerls.BodyWriterMessage’ cannot be serialized. Consider marking it with the DataContractAttribute attribute, and marking all of its mermbers you want seralized with the DataMemberAttribute attribute…
Any help is appreciated. I am at a standstill as I am still new to BizTalk and the WCF integration with BizTalk.
Sarah
I don’t know about msmqtlarge.dll. I usually try to steer away from using MSMQ because of the 4MB size limit and also because BizTalk’s large message queueing functionality seems cumbersome. I would probably look at compression or chunking before I went the MSMQT route. Compression would be simpler than chunking, but it would not eliminate the size limit, only increase it. You could use the System.IO.Compression.GZipStream class to compress the message on the client side, and then write a custom receive pipeline on the BizTalk side that uses GZipStream to decompress it. Chunking would be more complicated but it would allow you to handle much bigger messages. You would need to write a debatching orchestration to reconstruct the message from the chunks. The tricky part would be identifying the chunks that make up a message. You have to find a way to correlate the chunks. The client app will probably need to set some kind of batch ID. Tricky!
-
AuthorPosts