I believe I can fly,I believe I can touch the sky!

Issue:

There was a failure executing the receive pipeline: "Microsoft.Solutions.BTARN.Pipelines.Receive, Microsoft.Solutions.BTARN.PipelineReceive, Version=3.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "Pipeline " Receive Port: "RNIF_Async_Receive" URI: "/BTARNHttpReceive/BTSHTTPReceive.dll?xRNResponseType=async" Reason: Party with DUNS "544623812" was not found in BizTalk Explorer.

Solution:

Check your DUNS(GBI),this error occurs when you type one wrong DUNS in the HOME/Partner configuration.

How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server 2005

1. For a renamed default instance, run the following procedures:
Get SQL SERVER NAME: select @@servername
sp_dropserver <old_name>
GO
sp_addserver <new_name>, local
GO
Restart the SQL Server instance.

2. For a renamed named instance, run the following procedures:
sp_dropserver <old_name\instancename>
GO
sp_addserver <new_name\instancename>, local
GO

Restart the SQL Server instance.

URL: http://msdn2.microsoft.com/en-us/library/ms143799.aspx

One-way web service call in BizTalk Orchestration

The default ASP.NET web service behavior is to return a response even if a method returns void, to allow the service to return a fault message. BizTalk Server creates a response message part for the void return. If you are in control of the Web service and it is a .NET Web service, you can specify that a response should not be returned by using the [SoapDocumentMethod(OneWay=true)] attribute, making it truly fire-and-forget.

Sample code looks like this:

[WebMethod]

[SoapDocumentMethod(OneWay=true)]

public void OneWayService ()

{

}

When you add a web reference to your Orchestration project BizTalk now configures the port type to be one-way and the port shape reflects this.

The adapter failed to transmit message going to send port "UWSHandling_WS_Intel" with URL "wse://http://10.33.49.14/KWEIntelIntegration/ServiceToIntel.asmx". It will be retransmitted after the retry interval specified for this Send Port. Details:"There was an exception running the extensions specified in the config file. ---> Maximum request length exceeded.".

Solution:

在web.config 里system.web下加入下面一行

    <system.web>
    <httpRuntime maxRequestLength="102400"  executionTimeout="3600"/>

Notes:

httpRuntime maxRequestLength:单位 K

Optional Int32 attribute.

Specifies the limit for the input stream buffering threshold, in KB. This limit can be used to prevent denial of service attacks that are caused, for example, by users posting large files to the server.

The default is 4096 (4 MB).

 

httpRuntime executionTimeout    

executionTimeout

Optional TimeSpan attribute.

Specifies the maximum number of seconds that a request is allowed to execute before being automatically shut down by ASP.NET.

This time-out applies only if the debug attribute in the compilation element is False. To help to prevent shutting down the application while you are debugging, do not set this time-out to a large value.

The default is "00:01:50" (110 seconds).

查阅了MSDN,其实很简单

sp_xml_preparedocument
hdoc 
OUTPUT
[ , xmltext ]
[ , xpath_namespaces ] 

You can specify ns using the third parameter.

declare @MailContent as nvarchar(max)
select @MailContent=MessageBody from MailStorer where ID=2

--print @MailContent

DECLARE @XmlHandler int
--Create an internal representation of the XML document.
EXEC sp_xml_preparedocument @XmlHandler OUTPUT, @MailContent,'<ns0:RN_4C1_OUT xmlns:ns0="http://_4C1_InventoryHold_Intel.MailMessage"/>'

SELECT  '4C1 Inventory Hold On/Off' as Header,*
FROM       OPENXML (@XmlHandler, '/ns0:RN_4C1_OUT/InventoryLine',1)
with
(
    Status nvarchar(50) 'Status',
    Date nvarchar(50) 'DocDate',
    IDocNo nvarchar(50) 'IDocNo',
    SKU nvarchar(50) 'SKU',
    Quantity nvarchar(50) 'Qty',
    RequestBy nvarchar(50) 'RequestBy'
)

-- 清除xml文件句柄，释放内存
exec sp_xml_removedocument @XmlHandler

Refer to the fourmain types of BizTalk projects—workflow automation, legacy application integration, trading partner exchange, and organizational message broker scenarios. If your application has any of these types of pieces, BizTalk may be a fit. If not, you need to examine where and why BizTalk is being evaluated.

The key thing to remember in this type of situation is to define early in the solution’s design phase what data will be exchanged with BizTalk, what the schema definitions are, and how data will be returned to the calling application. Another key decision is to decide whether the main application requires a synchronous or an asynchronous response from BizTalk and what the threshold values are for an acceptable transaction. If the calling application needs a subsecond synchronous response from BizTalk to process the message, it is imperative that the system be sized properly to ensure that response times are acceptable. If the communication can be asyn- chronous, it is easier to restrict the flow of messages to an acceptable level either by using a queuing mechanism or some sort of batch processing.

Note: The SQL Agent job MessageBox_Message_Cleanup_<BizTalkMsgBoxDb> is disabled by default. It is not supported to enable this job or run it manually. This SQL Agent job is managed by the MessageBox_Message_ManageRefCountLog_<BiztalkMsgBoxDb> SQL Agent job.

CREATE PROCEDURE PipAutomationGetAction
AS
 SET TRANSACTION ISOLATION LEVEL READ COMMITTED
BEGIN TRANSACTION
DECLARE @tempGUID nvarchar(36)
SELECT TOP 1 @tempGUID = MessageID FROM MessagesToLOB WITH (READPAST,UPDLOCK,ROWLOCK)
   WHERE Delivered = 0 AND MessageCategory = 10
  ORDER BY TimeCreated
  SELECT PIPInstanceID,DestinationPartyName,SourcePartyName,PIPCode,PIPVersion, ServiceContent FROM MessagesToLOB
   WHERE MessageID = @tempGUID
For xml auto
UPDATE MessagesToLOB SET Delivered = 1 WHERE MessageID = @tempGUID
COMMIT TRANSACTION
GO

设置SQL Adapter pollWhileDataFound = true

(Specify whether to submit additional batches until the stored procedure or query returns no results, or submit a single stored procedure or query result for each polling interval.)

Note:

If you create two or more SQL adapter receive locations against the same SQL database, BizTalk Server will generate the same URI property for both. Because BizTalk Server does not allow for duplicate URI properties, you must manually change the properties so that they are unique. For example, if you have two receive locations that each have a URI value of SQL://./Northwind/, leave one of them as SQL://./Northwind/ and change the other to SQL://./Northwind/Secondary/. This value appears in the SQL Transport Properties dialog box, when configuring a receive location in the BizTalk Server Administration Console.

<xsl:call-template name="ClassRule">
        <xsl:with-param name="vClass" select="ns1:Class"/>
 </xsl:call-template>

-----------------------

  <xsl:template name="ClassRule">
    <xsl:param name="vClass" select="''"/>
   
    <xsl:if test="$vClass and string-length($vClass)>0">
      <class rule="中图分类">
        <xsl:choose>
          <xsl:when  test="contains($vClass,'%')">
            <xsl:value-of select="substring-before($vClass,'%')"/>
          </xsl:when>
          <xsl:otherwise>
            <xsl:value-of select="$vClass"/>
          </xsl:otherwise>
        </xsl:choose>
      </class>
      <xsl:if  test="contains($vClass,'%')">
        <xsl:variable name="vClass2" select="substring-after($vClass,'%')"/>
        <xsl:call-template name="ClassRule">
          <xsl:with-param name="vClass" select="$vClass2"/>
        </xsl:call-template>
      </xsl:if>
    </xsl:if>
  </xsl:template>