Learn, Troubleshoot BizTalk with Ashok Rajpurohit

BizTalk WCF : BizTalk System.ServiceModel.AddressAccessDeniedException

2016-01-06T06:58:00.000-08:00

BizTalk System.ServiceModel.AddressAccessDeniedException

You configure a self-hosted service at a BizTalk receive location using a localhost address, and when you try to enable the service (receive location) you get the above error with the details 'HTTP could not register URL http://+:80/Service.CreateService.FirstService.v1/. Your process does not have access rights to this namespace'

I was getting above error when trying to Enable WCF receive location.

To overcome this issue, you need to

Solution

1. Open the Visual studio command prompt (using the run as administrator option)

2. Type in the command netsh http add urlacl url=http://+:80/<the rest of the address that comes after localhost/> user=DOMAIN\username (So, if your full address ishttp://localhost/company.bookings.carbookingservice, you type inhttp://+:80/company.bookings.carbookingservice)

User Name should be same under which your host is running.

3. Enter to run the command

4. reset IIS - optional

5. Enable the receive location. It should start successfully now

Orchestration :The xpath expression selected a node which is not valid for property or distinguished field retrieval

2016-01-06T06:53:00.001-08:00

Error : Orchestration :The xpath expression selected a node which is not valid for property or distinguished field retrieval

Solution:

I got above error while setting message attribute value in orchestration using Xpath:

I was assigning value to response message attribute after the executing Map. the Map was not creating any node for that attribute and when I was trying to set values in orchestration it was throwing error.

1. Check if the transform is producing the node during the runtime. Please also test the field value by writing the map's output to event log

2. Make sure your Xpath is valid. You may use xpath tester tool to test xpath configured is correct.

BizTalk Map incoming Message to Single Output field - XSLT template

2015-10-12T08:00:00.001-07:00

BizTalk Transformation : Map Incoming XML Message to Single output field as string

To map incoming message to single out field, we will use xstl template in map.

1. Drag and drop Custom Scripting Functoid on your Map

2.Select Inline XSLT Call Template.

3. Copy and Paste the following xslt code in "Inline Script" Section

<xsl:template name="called-template">
  <xsl:param name="param1" />
  <xsl:element name="DestinationField" namespace="http://myschema.namespace.com/">
    <xsl:text disable-output-escaping="yes">&lt;![CDATA[</xsl:text>
    <xsl:call-template name="identity" />
    <xsl:text disable-output-escaping="yes">]]&gt;</xsl:text>
  </xsl:element>
</xsl:template>


<xsl:template name="identity" match="@*|node()">
  <xsl:copy>
    <xsl:apply-templates select="@*|node()" />
  </xsl:copy>
</xsl:template>

4. Map your root node name of source schema and destination field to this scripting Functoid.

5. Validate and Test your Map.

BizTalk : Design Patterns in Orchestrations

2015-04-17T07:15:00.000-07:00

Design Patterns in Orchestrations : BizTalk

A good article on BizTalk design pattern can be found on msdn link @ https://msdn.microsoft.com/en-us/library/aa561967.aspx

Source code related this article can be found in your local BizTalk installation folder

C:\Program Files (x86)\Microsoft BizTalk Server 2010\SDK\Samples

Optimizing Pipeline Performance - Biztalk Pipeline

2015-01-15T04:23:00.002-08:00

Optimizing Pipeline Performance - Biztalk Pipeline

A really helpful artical on improving BizTalk Pipeline component performance

http://msdn.microsoft.com/en-us/library/ee377071(v=bts.70).aspx

What to use inside the pipelne component
Should we use XMLDocument or XMLReader in the pipeline component.
working with Virtual Stream.
Using AddResourceTracker

pContext.ResourceTracker.AddResource(messageData);

http://msdn.microsoft.com/en-us/library/ee377071(v=bts.70).aspx

Overriding ConnectionString in Machine.config with web.config ConnectionString.

2014-10-01T03:02:00.000-07:00

Overriding ConnectionString in Machine.config with web.config connectionstring.

If I have following connectionstring in my machine.config (Machine level value)

</connectionStrings>

Now for specific web application I want a different connection string value then we need to override the value in machine.config.

So we need to add the required connectionstring value in web.config

</connectionStrings>

But with this, it will give an error in browser that

Parser Error Message: The entry 'TestConfigConnection' has already been added.

Means when you already have this key connectionstring in machine.config then why are you storing this value again in web.config file.

To overcome this error we need to remove the key in web.config and then need to add it again. So my Web.Config file will have following entry

</connectionStrings>

This will work J

Why can't we have send and receive within an atomic scope

2014-09-21T06:24:00.003-07:00

Why can't we have send and receive within an atomic scope?

The atomic scope was designed to handle Atomicity, Consistency,
Isolation, and Durability (ACID) compliant operations that must either all succeed or
all fail as a group.

This is a classic database transaction style. It is designed to carry
an orchestration from one stable state to another. This is why you cannot both
send and receive from an atomic scope, because by design the message box is not
a lockable resource.

To accomplish this atomicity, the orchestration engine persists
the entire orchestration state to the message box before the atomic scope begins; it
subsequently persists the orchestration again when the atomic scope completes.

BizTalk : Defining multiple database ReceiveLocation with same db connection string

2014-03-05T05:30:00.002-08:00

BizTalk : Defining multiple database ReceiveLocation with same db connection string

BizTalk does not allow us to create the multiple receive location with Same URI, At design time it validate the URI and if it matches with any receive location then it throw Validation error.

But there may be some requirement where we might need multiple receive location with same URI like multiple database receive location with same database URI and each polling to different set of data (different stored procedure/package.)

So for this requirement, we can implement the multiple receive location with different pollingid. So at design/run time it won’t throw any validation error as the URI is different. The connectionstring with PollingID really doesn’t make any difference and it won’t create any issue while connecting database.

Ex . If I have two receive location polling database

ReceiveLocation1 -> URI -> oracledb://goDEV1/?PolllingID=1111

ReceiveLocation2 -> URI -> oracledb://goDEV1/?PolllingID=2222

ReceiveLocation3 -> URI -> oracledb://goDEV1/?PolllingID=3333

BizTalk Oracle/SQL execution error on ReceiveLocation : Action http://Microsoft.LobServices.OracleDB

2014-03-05T05:20:00.001-08:00

BizTalk Oracle/SQL execution error on ReceiveLocation

When we try to call SQL/Oracle StoredProcedure/package from the ReceiveLocation with Default PollingAction generated then it might give error as we need to add “Polling” in the name of package or stored procedure.

The Messaging Engine failed to add a receive location "Zim.EAI.Framework.RL_ReTestGet" with URL "oracledb://goDEV1/?PolllingID=1111" to the adapter "WCF-Custom". Reason: "System.NotSupportedException: Action "http://Microsoft.LobServices.OracleDB/2007/03/EBT/Package/BL_GO_PCK/GETDATA_XML" is invalid.

at Microsoft.Adapters.OracleDB.OracleDBInboundContract..ctor(OracleDBConnection connection, IOracleCommonUDTHelper oracleUdtHelper, MetadataLookup metadataLookup)

Auto Generated Action :

http://Microsoft.LobServices.OracleDB/2007/03/EBT/Package/BL_GO_PCK/GETDATA_XML

http://Microsoft.LobServices.OracleDB/2007/03/EBT/Procedure/BL_GO_PCK/GETDATA_XML

Correct Action :

http://Microsoft.LobServices.OracleDB/2007/03/EBT/PollingPackage/BL_GO_PCK/GETDATA_XML

http://Microsoft.LobServices.OracleDB/2007/03/EBT/PollingProcedure/BL_GO_PCK/GETDATA_XML

ASP.NET Clear the GridView data on specific condition

2014-02-20T05:37:00.000-08:00

ASP.NET Clear the GridView data on specific condition

When there are no data found for user search criteria then we want to clear the previous gridview data and display "No record found" message to user.

This can be achieved by following line of code:
Set the DataSource = null and bind this to your gridview.

if (lblError.Visible == false)

{

if (dvCustomerRecords.Count > 0)

{

gvCustomer.DataSource = dvCustomerRecords;

}

else

{

gvCustomer.DataSource = null;

lblError.Visible = true;

lblError.Text = "No Record : No record found for specified search criteria!";

}

gvCustomer.DataBind();

Creating & Configuring Application pool for Website/WCF service in IIS

2014-02-13T07:41:00.001-08:00

Creating & Configuring a new Application pool for Website/WCF service in IIS

1. Create and Deploy your web application/WCf service to IIS.

2. Click “Application Pools” à right Click mouse, select “Add Application Pool”

3. Type the name of Application pool, Select the required framework version and Managed Pipeline Mode.

Click OK. This will create a new application pool.

4.For performance and timeout related setting, please go to “Advance Setting” option of Application pool. It’s recommended to update advance setting of application pool carefully. As there are many setting which can affect performance of your application.

5. Once you create the application pool as per your requirement. Then go to WCF/Web Application which need to be configured to run under this application pool.

6. Go to “Manage Application” à “Advance setting”

7. Go to “Application Pool”. Click Browse option next to current application pool name. It will open a new popup window. Select the required application pool. For this demo I am selecting the newly created application pool “WCFWebAppPool”.

8. Click “OK”. Now your application will run under newly created application pool.

WCF throttling (Resource Utilization/ Load Balance) configuration

2014-02-12T02:02:00.002-08:00

WCF throttling (Resource Utilization/ Load Balance) :

Limit how many instances or sessions are created at the application level for better utilization of resource and memory.

Resource Utilization : With the implementation of throttling, we can properly utilize the available resource like Memory, threads. Each resource could be managed at its reasonable limit to avoid very high utilization of any specific resource.

Load Balance : Application should work under balanced load. If we execute anything concurrently then there could lot of performance and load balancing related problem will occur.

WCF throttling allow us to manage our resource utilization and balancing the load as per our processor/RAM availability.

We have following three property which allow us to control WCF service behavior:

WCF throttling -WCF behavior setting config level

a. maxConcurrentCalls - number of messages that currently process across a ServiceHost (Default: (depends on Framework version) * processor count)

b. maxConcurrentSessions - number of sessions a ServiceHost object can accept, only the channels below the limit are active (Default: 16 * processor count)

c. maxConcurrentInstances - number of InstanceContext objects that execute at one time across a ServiceHost (Default: maxConcurrentSessions + MaxConcurrentCalls)

Default settings in 3.0:

· MaxConcurrentSessions (default: 10)

· MaxConcurrentCalls (default: 16)

· MaxConcurrentInstances (default: 26)

Default setting for WCF 4.O for scalability according to the Web Server:

MaxConcurrentSessions: default is 100 * ProcessorCount
MaxConcurrentCalls: default is 16 * ProcessorCount
MaxConcurrentInstances: default is the total of the above two, which follows the same pattern as before. (Default: maxConcurrentSessions + MaxConcurrentCalls)

This setting can be defined at config file @ service Behaviors level

<serviceThrottling

maxConcurrentCalls="1"

maxConcurrentSessions="1"

maxConcurrentInstances="1"

<serviceMetadata

httpGetEnabled="true"

httpGetUrl=""

</behavior>

</serviceBehaviors>

BizTalk Error: “Loading property information list by namespace failed or property not found in the list”

2014-02-06T05:40:00.000-08:00

BizTalk side-by-side versioning error: “Loading property information list by namespace failed or property not found in the list”

Cause for this error is deploying same schema with different version, One deployed version of schema allow other schema to be Inactive.

exec bt_LoadPropertyInfoByNamespace @nvcNamespace=N'http://Domain.EAI.Solution'

exec bt_LoadPropertyInfoByNamespace @nvcNamespace=N'http://Domain.EAI.Solution/009'

the above query should return the containing msgtyep and Property class,

select *

FROM bt_XMLShare

WHERE target_namespace like N'http://Domain.EAI.Solution' AND active = 1

Check if the Activate flag =1 or 0. 1- Means the schema is active

If it’s not active, Please redeploy the schema in correct order. This should resolve the ‘loading property error’

Deploying Custom Pipeline Component on BizTalk Server (PROD)

2014-01-15T04:51:00.000-08:00

Deploying Custom Pipeline Component on BizTalk Server:

· Deploying BizTalk Custom Pipeline Component on BizTalk Server 2006 or Older Version :

To deploy the custom Pipeline component on BizTalk server 2006 or older version. We need to add the Custom Pipeline component in GAC as well as “C:\Program Files (x86)\Microsoft BizTalk Server 2006\Pipeline Components” folder.

At design time it will access the Pipeline component dll located in “…..Microsoft BizTalk Server 2006\Pipeline Components” folder and show the component in pipeline toolbox.

At runtime the BizTalk will use the Custom Pipeline component from GAC.

· Deploying BizTalk Custom Pipeline Component on BizTalk Server 2006 R2 or New Version :

To deploy the custom Pipeline component on BizTalk server 2006 R2 or later version. We need to add the Custom Pipeline component only in “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components” folder. No need to GAC this component.

At design & Run time it will use the Pipeline component dll located in “…..Microsoft BizTalk Server 2010\Pipeline Components” folder .

Deployment On Production for BizTalk Server 2006 R2 or later version:

1. Case 1 : Custom Pipeline component dll added to GAC but not located in “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components”

At runtime the Biztalk process will first try to find the dll in “Pipeline Component” and if it does not find it in this folder then check the dll in GAC. Once it find the dll in GAC, it will use it. Process won’t give any error.

2. Case 2 : Custom Pipeline component dll added to folder “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components” but not in GAC

At runtime the Biztalk process will first try to find the dll in “Pipeline Component”. As it find the dll in ‘Pipeline Component’ folder won’t go to GAC, it will use the dll located in GAC. Process won’t give any error.

3. Case 3 : Custom Pipeline component dll neither added in GAC nor in folder “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components”

At runtime the Biztalk process will first try to find the dll in “Pipeline Component” and if it does not find it in this folder then check the dll in GAC. The process will also not able to find the Custom Pipeline component dll in GAC. This time the process will throw the error “ Custom Pipelince component ‘Assembly Name’ not found in C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components”

From BizTalk Server 2006 R2, we don't have add the Custom Pipeline component in GAC.

The Default expected location for this dll is “C:\Program Files (x86)\Microsoft BizTalk Server 2010\Pipeline Components”

And if it does not find the dll at this location then it will check assembly in GAC.

C# : check whether input string data is XML or NOT

2014-01-12T07:12:00.001-08:00

To check whether input string data is XML or NOT.

Simply copy and paste the following code. This code will throw an exception in case input string is not XML.

if (!String.IsNullOrEmpty(sXMLMessage))

{

try

{

System.Xml.Linq.XElement.Parse(sXMLMessage);

// Business Logic for XML string data here

}

catch (XmlException ex)

{

// Business Logic for non-xml string data here

}

BizTalk Error : Could not enlist send port 'portname': the property specified on the filter expression does not exist

2014-01-12T03:40:00.003-08:00

BizTalk Error :

Error message when you enlist a send port that has a port filter against a user-defined property in BizTalk Server: "Could not enlist send port 'portname': the property specified on the filter expression does not exist"

Cause :

When trying to start the SendPort configured with filter property, I was getting above error.

After analyzing I found that the cause for this error was namespace conflict. I have deployed the some schema in BizTalk system which has same target namespace as this schema.

I deployed Schema A for Project A and trying to use property of Schema A in filter expression.

Project A -> Schema A -> Target NameSpace = “ http://Microsoft.Test.Schema”

But this target namespace were already present under Project B

Project B -> Schema B -> Target NameSpace = “ http://Microsoft.Test.Schema”

This problem occurs when the property that is used in the port filter has a namespace conflict with the target namespace of another schema assembly.

Solution : Remove the Target Namespace conflict between schema. Then it will work without any error.

BizTalk Error The local, cached version of the BizTalk Server group configuration is out of date.

2014-01-07T07:44:00.002-08:00

When we try to delete BizTalk application or Map from BizTalk Admin console, we might get this type of error and this error might occur on every environment from development machines to production servers.

Error :

"Error while removing application "BT Project name".

Schema referenced by Map ‘BTProject’ has been deleted. The local, cached version of the BizTalk Server group configuration is out of date. You must refresh the BizTalk Server group configuration before making further changes."

By Mistake I deployed the BizTalk Map project before the BizTalk schema project. The BizTalk Map project were having reference to BizTalk Schema project. When I tried to delete the deployed BizTalk project it gave me above error.

And every time you refresh BizTalk Admin console you will get the above error.

Solution :

To fix the above error you need to manually delete entry from table bt_mapspec, this table is located inside BizTalkMgmtDB,

You can refer following queries to delete the map

-- Locate the itemId of the map

Select * from bt_mapspec

-- Using the itemId retrieved above delete the map

Delete from bt_mapspec Where itemid = 'itemId_of_map'

Delete from bt_mapspec Where assemblyid = ‘id’

After executing above SQL query, just refresh the BizTalk admin console. It should work now.

Love BizTalk, Think BizTalk!!!

CSS - To fix Gridview Header Position

2013-10-28T06:35:00.003-07:00

Following CSS can be used to fix the header position in gridview

.fixedHeader
{
font-weight:bold;
background-color: #006699;
position:relative ;
height: 25px;
top:expression(Sys.UI.DomElement.getBounds(document.getElementById("MainContent_dvGrid")).y-270);
z-index: 10;
}

MainContent_dvGrid - is div which contain the GridView.
y- 270 => 270 value can be adjusted as per your requirement and alignment of Grid & Div.

Use this CSS in HeaderStyle of your Grid,
<HeaderStyle CssClass="fixedHeader" ForeColor="White" Height="10px" />

Microsoft.ServiceModel.Channels.Common.ConnectionException: Due to an Oracle Client limitation, the adapter failed to open a connection.

2013-07-15T06:35:00.001-07:00

BizTalk Custom WCF Adapter Error :

Microsoft.ServiceModel.Channels.Common.ConnectionException: Due to an Oracle Client limitation, the adapter failed to open a connection. This is because either (a) ambient transaction is present and the TNS alias is longer than 39 characters, or (b) ambient transaction is present and a non-TNS based URI was used. To resolve this, use a TNS alias to connect to Oracle and make sure it is not more than 39 characters.

Solution :

In the Send Port configuration adapter I used a WCF-Custom transport type and used oracleDBbinding as binding type.
In the oracleDBbinding I changed the following propertys:

"enableBizTalkCompatibilityMode" = True (For some reasons this i set to false per default)
"useAmbientTransaction" = False

Jumped to the Message tab and uncheck the "Use Transaction" box under Transactions.

BizTalk : Runtime assembly loading issue , Could not load file or assembly

2013-07-12T02:56:00.001-07:00

BizTalk : Runtime assembly loading issue , Could not load file or assembly

If you require a specific version of assembly to be loaded at runtime when your BizTalk application run. This requirement could be implemented by adding a required assembly setting in BTSNTSvc.exe.config. In biztalk config file you need to specify the old and new version of assembly that need to be loaded at runtime.

Following setting could be added in your BTSNTSvc.exe.config file with proper assembly details.

Using this Binding Policy in config, we can load the any required assembly at runtime..

<runtime>

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

<dependentAssembly>

<assemblyIdentity name="BTSales.DataAccess" publicKeyToken="89b653f429c47342" culture="neutral" />

<bindingRedirect oldVersion="2.111.7.0" newVersion="4.112.1.2"/>

</dependentAssembly>

</assemblyBinding>

</runtime>

After implementing the above changes in BtsntSvc.exe.config file, if you are still getting this error while using BTAdmin console then update the BTSMMCLauncher.exe.config file same as above. This will resolve your design time assembly loading issue.

Added following thing in BTSMMCLauncher.exe.config , Reopen your BTS Admin console.

<runtime>

<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

<dependentAssembly>

<assemblyIdentity name="BTSales.DataAccess" publicKeyToken="89b653f429c47342" culture="neutral" />

<bindingRedirect oldVersion="2.111.7.0" newVersion="4.112.1.2"/>

</dependentAssembly>

</assemblyBinding>

</runtime>

BizTalk error : Attempted to access an unloaded AppDomain.

2013-07-11T02:43:00.004-07:00

BizTalk error : Reason: Attempted to access an unloaded AppDomain.

While accessing WCf service in one of my BizTalk application, I received the following error.

There was a failure executing the receive pipeline: "Unknown " Source: "Unknown " Receive Port: TwoWayLatencyService_RcvPort" URI: "/.svc" Reason: Attempted to access an unloaded AppDomain.

Cause : This happens when there are several Web Services with the same Application Pool, and the first is inactive for a long period of time, all the others are inactive.

Solution : after restarting the IIS server it worked.

WCF ERROR - An unsecured or incorrectly secured fault was received from the other party

2013-06-27T06:35:00.001-07:00

Error : “An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail”.

We got above security while accessing the WCF service deployed on our Development server

Cause : This type of error we normally receive because of a server time skew. The remote server and the client's system time must be within (typically) 5 minutes of each other. If they are not, security validation will fail and WCF service will throw security error. The Development serve and client time difference was 10mins and Hence the service was throwing an error related to security.

Solution :

We just have updated the server time same as client machine and then it started working.

Message security mechanism in WCF supports WS-SecurityConversation standard, which consists of establishing a session between client and server. A special request should be sent for a session to be established before any other calls. This results in getting a security token which will be used for subsequent calls. SecurityConversation mechanism has a very bad side effect - the success of conversation depends on difference between client and server system time. By default an acceptable skew between client and server is 5 minutes. If the skew is bigger than a call completes with an error. If system time on client isn't being synchronized with server then we can get (and actually get) a situation when our application stops working suddenly and start giving security related exception.

http://techblog.dorogin.com/2011/10/wcf-and-difference-of-time-of-client.html

http://msdn.microsoft.com/en-us/library/aa738468.aspx

Preserve whitespace in BizTalk Transform

2013-05-27T06:07:00.000-07:00

Preserving Whitespaces in BizTalk Transformation

Following property need to be set r_setting.IgnoreWhitespace = false;

Full Sample code

XsltSettings set = new XsltSettings(true, true);

XmlReader reader;

XmlWriter writer;

string xmlPath_out = "D:/" + "testWhiteSpace.xml";

//StreamWriter writer = File.CreateText(xmlPath_out);

try

{

string xml_p = "testWhite_P.xml";

string xslt_p = "xsltWhiteSpace.xsl";

string xmlPath = Server.MapPath(xml_p);

string xslPath = Server.MapPath(xslt_p);

//Instantiate the XslTransform Class

XslCompiledTransform transform = new XslCompiledTransform();

XmlResolver secureResolver = new XmlSecureResolver(new XmlUrlResolver(), xmlPath);

XmlReaderSettings r_setting = new XmlReaderSettings();

transform.Load(xslPath, set, secureResolver);

r_setting.IgnoreWhitespace = false;

reader = XmlReader.Create(xmlPath, r_setting);

XmlWriterSettings w_setting = new XmlWriterSettings();

writer = XmlWriter.Create(xmlPath_out, w_setting);

transform.Transform(reader, null, writer);

reader.Close();

writer.Close();

}

finally

{

}

Node that need to be added in custom XSLT file

<xsl:preserve-space elements="*"/>

http://www.w3.org/TR/xslt.html#strip Please refer section 3.4 for link

More detailed MSDN link http://blogs.msdn.com/b/xmlteam/archive/2005/11/16/introducing-xslcompiledtransform.aspx

BizTalk SendPort file name support/macro

2013-04-29T05:37:00.000-07:00

BizTalk Send Port with File Adapter supports the following formats (macros) for the file saved.

%MessageID%
%datetime%
%SourceFileName%
%time%

Difference between publishing schema and publishing an orchestration as a WCF Service

2013-04-25T06:09:00.001-07:00

Difference between publishing schema and publishing an orchestration as a WCF Service

Publishing Schema as Endpoint

Publishing Orchestration as Endpoint

Orchestration Completing not require - publishing Schema as service will enable your subscribers get your Data Contracts and they can begin their development. Your subscribers don’t have to wait till you complete your business logic.

Orchestration should be completed - Publishing an orchestration requires you to get ready with the Orchestration development at first place or let your subscribers wait till you finish your orchestration development.

Orchestration will be loosely coupled- you are free to update/add new orchestration subscribing to specified message contract

Orchestration will be tightly coupled – After updating/changing orchestration need republish the Endpoint.

During publishing wizard, we need to select the schema and need to specify the request/response message.

During Publishing wizard, we don’t have to specify the schema. The orchestration input/output message will be considered as Request/Response message contract for endpoint.

Publishing Schema as Endpoint	Publishing Orchestration as Endpoint
Orchestration Completing not require - publishing Schema as service will enable your subscribers get your Data Contracts and they can begin their development. Your subscribers don’t have to wait till you complete your business logic.	Orchestration should be completed - Publishing an orchestration requires you to get ready with the Orchestration development at first place or let your subscribers wait till you finish your orchestration development.
Orchestration will be loosely coupled- you are free to update/add new orchestration subscribing to specified message contract	Orchestration will be tightly coupled – After updating/changing orchestration need republish the Endpoint.
During publishing wizard, we need to select the schema and need to specify the request/response message.	During Publishing wizard, we don’t have to specify the schema. The orchestration input/output message will be considered as Request/Response message contract for endpoint.