U3's Couch

Web service clients may encounter an error with the exception text "Internal SOAP Processing Failure" when consuming (calling) published BizTalk Web services.
Published Web services return the following generic exception when the Web service client encounters an error:

System.Web.Services.Protocols.SoapException:
System.Web.Services.Protocols.SoapException: Internal SOAP Processing Failure at
Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.Invoke....

If you are trying to receive the same message type ( using the same schema with different message) using a receive port different from the initial one, and If you tried to mark the first Receive shape with “Initializing Correlation Sets“ and the second one with “Following Correlation Sets ” , you will receive this error, so what is the Solution ?
You have more than one solution

1) Receive the same message with the same type to several Receive shapes
2) Send the different messages with the same type to several Send ports

However I had tried to follow the installation guidelines as close as possible,An error occurred while installing Microsoft ESB CTP3 using the “1.CORE_CreateBizTalkApplication.cmd” script

“Error: Failed to update binding information. Cannot update send port" ALL.Exceptions.”Cannot set send port "ALL.Exceptions" send pipeline.Sendpipeline
"Microsoft.Practices.ESB.ExceptionHandling.Pipelines.ESBFaultProcessor,
Microsoft.Practices.ESB.ExceptionHandling.Pipelines, Version=1.0.0.1, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a" not found.”

I had sent an email to Ahmed Farrag (my ex-Manager at ITWorx , now he is working as Biztalk Consultant at Microsoft Middle East Good luck there) ,He said ," this error means that the pipline was not deployed, make sure the pipeline is deployed first. use the deployment from the VS studio to do this" , Thank You Farrag it's working , thank you and Good Luck

When someone ask me what is Microsoft ESB, I told him the usual definition and I explain it using the terms of SOA and SOI. His face had been changed to this:

So before taking about what is ESB lets explain some important definitions :

What is Infrastructure?
The fundamental structure of a system or organization. The basic, fundamental architecture of any system (electronic, mechanical, social, political, etc.) determines how it functions and how flexible it is to meet future requirements.

So what is the Service Orientation in general?
Service-orientation is a service paradigm that specifies the creation of automation logic in the form of services. It is applied as a strategic goal in developing a service-oriented architecture (SOA). Like other design paradigms, service-orientation provides a means of achieving a separation of concerns.

Okay what is Service Oriented Infrastructure?
Essentially, an SOI is a set of physical and system software level IT resources, which are geared to meeting the demands of an SOA-defined application environment, and in many ways mirrors the attributes that are commonly associated with SOA environments.

Ummmmmmm… Is there is a different between Service Oriented and Object Oriented design?
First lets define what is Object Oriented Design is part of OO methodology and it forces programmers to think in terms of objects, rather than procedures, when they plan their code. An object contains encapsulated data and procedures grouped together to represent an entity.

So Service-oriented programming (SOP) builds on top of OOP, allowing services to be built using OO techniques. These services themselves provide increased reuse of the business logic, by allowing the service to be used in diverse applications. OOP focuses on what objects an application consists of, while an SOP approach focuses on the application's functionality, or in other words, what the application does.

then the term of ESB is:

the context of implementing an infrastructure for enabling a Service-Oriented Architecture (SOA). However, real-world experience with the deployment of SOAs has shown that an ESB is only one of many building blocks that make up a comprehensive Service-Oriented Infrastructure (SOI). The term ESB has morphed in a number of different directions, and its definition depends on the interpretation of individual ESB and integration platform vendors, and on the requirements of particular SOA initiatives.

Based on the experience Microsoft has gathered from many successful real-world SOI implementations, you can think of an Enterprise Service Bus as a collection of architectural patterns based on traditional enterprise application integration (EAI), message-oriented middleware, Web services, .NET and Java interoperability, host system integration, and interoperability with service registries and asset repositories.

Okai , So What ?!

Check this :

http://www.soanowjournal.com/bestpractices.html

Do you want to save the SOAP request to your webservice!!!
And you don’t want to write a huge lines of code to do that process!!!

Download this dll , and just add the following attribute before your method:
[WebMethod, SoapLogger("C:\\soap.log")]

* WebMethod attribute: Attaching the WebMethod attribute to a Public method indicates that you want the method exposed as part of the XML Web service

*SoapLogger("C:\\soap.log"): Attaching the SoapLogger attribute to a Public method indicates that you want the monitor the SOAP request to that method and you want to save this request in that path : 'C:\\soap.log'

don’t care about the code just use the dll , and enjoy soaping... :D

Now we are go to create an Orchestration that can send a request to a Web Service that can process a SOAP Header "see Creating SOAP Header Schemas in BizTalk 2006 (Part 2) ":

1) You have to define a schema , the schema type of it is Property and the target namespace is http://schemas.microsoft.com/BizTalk/2003/SOAPHeader "see Creating SOAP Header Schemas in BizTalk 2006 Article Part(1)" , but you have to add a Child Field Element its name exactly the name of SOAP header class in the web service that will Process the SOAP Header

2)Now put your send , receive , assignment , and send-receive port to the web service that process the SOAP Header , as shown in the below image :

First, we have to know, how to Build a web service That Processes SOAP Headers:

---Define and Process SOAP Headers:

1. To define a class representing a SOAP header
-Create a class deriving from the Soap Header class with a name matching the root element for the SOAP header. Then Add public fields or properties, matching the names and their respective data types for each element in the SOAP header. For instance, given the following SOAP header, the class following it defines a class representing the SOAP header.

public class mySoapHeader : SoapHeader
{
public string HeaderValue;
}
2. To process SOAP headers within a Web service
-Add a public member to the class implementing the Web service of the type representing the SOAP header.

[WebService(Namespace = "http://ITWorx/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
public class Service : System.Web.Services.WebService
{
public mySoapHeader MyHeaderValue;

}
- Apply a SoapHeader attribute to each Web service method that intends to process the SOAP header. Set the MemberName property of the SoapHeader attribute to the name of the member variable created in the first step.

[SoapHeader("MyHeaderValue",Direction=SoapHeaderDirection.In)]
public string GetString()
{
}

-Within each Web service method that the SoapHeader attribute is applied to, access the member variable created in the first step to process the data sent in the SOAP header.

[SoapHeader("MyHeaderValue",Direction=SoapHeaderDirection.In)]
public string GetString()
{
if (MyHeaderValue != null){
return MyHeaderValue.HeaderValue;
}
else
return "Invalid information in SOAP Header";

In the Next article in sha'a ALLAH, I will explain how the orchestration could send a request includes a custom value in the SOAP Header

The steps for creating a SOAPHeader property schema are as follows:

1. Add a new schema to the project.
2. In the Properties window of the schema, set the Target Namespace to the BizTalk
SOAPHeader namespace which is : http://schemas.microsoft.com/BizTalk/2003/SOAPHeader
and the Schema Type to Property, as shown in the below Figure:


3. Add the desired elements to the schema. There is no root node on a SOAPHeader property
schema; it has only elements. In this example, there would be two elements added
to the schema: MessageId and TraceFlag.
4. On each element created, set the Property Schema Base in the Properties window to MessageContextPropertyBase, as shown in the below Figure :


In the next article, I will show you how to send a request includes data in the SOAP header to a web service, and how the web service will parse the SOAP header

The solution of this exception is very simple : View the property settings for the first Receive Shapeand change the [Activate] property to True ,

BizTalk Server provides many features that enable organizations to continuously improve their business processes, their level of customer service and their bottom line; however, most .NET developers and architects have never examined the product. This article will introduce the reader to many of BizTalk's features and discuss their benefits :
http://dotnet.sys-con.com/read/275464_1.htm

This is what I heard from someone when I told him the famous definition of BizTalk which is "BizTalk is a business process management (BPM) server that enables companies to automate and optimize business processes. This includes powerful and, familiar tools to design, develop, deploy, and manage business processes."