Willeam's Blog

November 2, 2009

如何將匯入RN DTD檔所產生的xsd schema,可以只顯示一個Root節點

willeam 在天空部落發表於01:15:01 | BizTalk Server

當我們在開發RosettaNet專案時,第一個步驟就是需要從www.rosettanet.org的站台上去下載PIP(Partner Interface Process)的定義檔,此定義檔是以DTD的格式記錄,因此我們需要透過BizTalk的Generate Schema功能將DTD匯入成xsd檔.
當你匯入DTD檔案成xsd schema檔後,你會發現schema的長相有點奇怪,為何會有許多根節點.

查看BizTalk Accelerator for Rosettanet的Help後,裡面有提到要設定Schema的Root Reference屬性,但是在設定過Root Reference屬性成Pip3A4PurchaseOrderRequest節點後,schema仍然跟之前一樣,還是許多根節點並列,只不過在xsd的內容多了一段root_reference="Pip3A4PurchaseOrderRequest"宣告.

雖然我們已經明確的宣告根節點是Pip3A4PurchaseOrderRequest,但是Visual Studio還是一樣顯示多個節點,原因是因為root_reference宣告並不會影響Visual Studio的顯示方式,需要在加上一個displayroot_reference才可以,只不過此屬性並無法透過Visual Studio的屬性畫面來設定,因此需要透過notepad或其他文字編輯工具直接對xsd檔案進行修改. 加入後可以在Visual Studio畫面上看到多了一個displayroot_reference的屬性.

重新載入xsd schema後,即可看到只有一個Root節點了,這樣是不是好看多了.

人氣 () | 回應 (1) | 引用 (0)

October 20, 2009

如何動態設定EDIFACT的UNB區段

willeam 在天空部落發表於00:35:45 | BizTalk Server

在EDIFACT的UNB 7 是代表Application Reference ID,通常都會填入該訊息的名稱,如:ORDERS,ORDRSP,INOVIC...等.但是因為該屬性是在EDI的表頭區,因此是在Party裡面設定,這樣就造成若想在不同的message type給不同值的問題.

以前在BizTalk 2006 R2時, 除了客製send pipeline將EDI Header硬塞進去外,可能就要寫一些額外的元件去處理,但是在BizTalk 2009因為增加了一個EDIOverride的context,讓此目的可以輕鬆達到.
做法如下:
1. 在biztalk專案加入C:\Program Files\Microsoft BizTalk Server 2009\Microsoft.BizTalk.Edi.BaseArtifacts.dll

2.開啟Orchestration,並且透過Assigment shape對EDI Message進行以下設定.
Msg_ORDRSP(EdiOverride.OverrideEDIHeader) = true;
Msg_ORDRSP(EdiOverride.UNB7) = "ORDRSP";

這樣就可以在EDI訊息上面動態加上需要的Application Reference ID了.

人氣 () | 回應 (2) | 引用 (0)

July 25, 2009

記得清除BizTalk Tracking資料庫BizTalkDTADb資料

willeam 在天空部落發表於22:21:57 | BizTalk Server

最近在幫一個biztalk 2004的客戶修改專案時,發現在undeploy專案時,在unenlist都會timeout,因此開啟HAT來查看一下是否還有instance正在跑還是怎樣,結果用HAT在查詢時也一樣會發生timeout.
所以就打開資料庫BizTalkDTADb一看,夭壽喔~空間居然15GB之大,難怪查一個資料都會timeout,當下就查看SQL Agent裡面是否有啟動DTA Purge and Archive這個job,一看之下果然沒有,因此在這裡提醒一下各位,請注意要將BizTalk相關的sql job給啟動,這樣才不會留一堆garbage在資料庫裡面.
後來我就自己手動執行了這個store procedure
exec dtasp_PurgeAllCompletedTrackingData

並且在將資料庫作一下Shrink
DBCC SHRINKDATABASE (BizTalkDTADb,10)

結果發現原來15GB的資料庫,裡面資料只有500MB而已,真是恐怖.
清完了之後,再去開HAT就可以正常開的起來,且unenlist流程也都可以成功了.

人氣 () | 回應 (0) | 引用 (0)

June 29, 2009

透過WCF Service model連接OracleDB出現password錯誤問題

willeam 在天空部落發表於17:12:20 | BizTalk Server

最近在使用BizTalk Adapter Pack 2.0連接Oracle Database時,在設定帳號密碼之後,進行connect時出現以下錯誤訊息.

但是我確定你輸入的帳號密碼是正確的,因為在ODBC使用原來的帳號密碼時,是可以登入成功的.
後來透過Google搜尋了一下,才知道這個地方輸入的帳號密碼大小寫是有分別的,後來將帳號全部改成大寫後,果然就真的過了,真是虛驚一場.

人氣 () | 回應 (0) | 引用 (0)

June 18, 2009

BizTalk 2009安裝--無法載入檔案或組件Microsoft.SqlServer.ManagedDTS

willeam 在天空部落發表於22:50:29 | BizTalk Server

當BizTalk 2009在安裝時，若與SQL Server 2008是不同台，則在安裝完後進行configuration時可能會遇到這個錯誤畫面.

看起來似乎是因為BizTalk BAM Archiving的功能需要用到SQL Server的Integration Services功能，導致BizTalk機器上需要安裝此元件才行。
解決的方法主要是在BizTalk主機上安裝SQL Server的Management Tools元件.
The workaround is to install the SQL Server Management Tools component.

· For SQL Server 2008, run setup and choose the Management Tools: Basic and Management Tools: Complete options.

· For SQL Server 2005, run setup and chose the Management Tools option under SQL Server 2005 Client Tools.

在微軟的Troubleshooting BizTalk Server 2009 Setup.docx文件中有說明.
http://www.microsoft.com/downloads/details.aspx?displaylang=zh-tw&FamilyID=9c697e02-d1bc-4684-8748-28b3a292d5bf

人氣 () | 回應 (2) | 引用 (0)

May 1, 2009

BizTalk 2009一定要安裝BAM Tools功能了

willeam 在天空部落發表於17:24:20 | BizTalk Server

在安裝BizTalk 2009後,進行Configuration時須注意一定要勾選BAM Tools,否則BizTalk 2009會裝不起來.
原因是因為BizTalk 2009的AS2有個新功能是可以做到當沒有收到MDN時,可以自動Resend.而這個Resend的功能是去針測BAMPrimaryImport的資料庫,而BAMPrimaxImport資料庫一定要裝BAMTool才要產生,所以,若你想裝BizTalk 2009的EDI/AS2功能的話,記得要連BAM Tools也一起裝.

人氣 () | 回應 (0) | 引用 (0)

April 28, 2009

如何移除biztalk產生XML的ns0前置字串

willeam 在天空部落發表於13:42:25 | BizTalk Server

1. Validate Map取得Xsl檔案

2. 用文字編輯器開啟xsl檔案,移除裡面ns0的字眼,若想連root節點namespace的ns0都移除的話也可以.

3.建立一新Map,此Map的Source與Destination都與原始一模一樣,但是不需要拉線.設定此map的Custom XSL Path屬性,指向上一步驟所修改過的XSL檔案.

4. 再次Test Map即可得到完全不含ns0的XML.

原來含有ns0的輸出XML.

人氣 () | 回應 (0) | 引用 (0)

March 19, 2009

一些BizTalk的免費元件

willeam 在天空部落發表於18:05:06 | BizTalk Server

裡面可以找到許多BizTalk元件啦,Adapter啦,工具等等,最重要的是一切都是免費的喔.
http://www.codeplex.com/

人氣 () | 回應 (0) | 引用 (0)

February 27, 2009

BizTalk 2006 R2不支援AS2自動重送功能,當沒收到MDN時

willeam 在天空部落發表於11:04:54 | BizTalk Server

目前BizTalk 2006 R2的AS2功能尚未支援自動重送的功能,也就是說,當你透過AS2正確的送出檔案後,若沒有收到正確的MDN時,BizTalk 2006 R2不會自動幫你重送該筆資料,這個功能需要到BizTalk 2009才會加入,底下是摘錄自BizTalk Server 2009 - EDI Product Team Blog.的新功能說明.
http://blogs.msdn.com/biztalkb2b/archive/2009/02/19/what-is-new-for-edi-as2-in-biztalk-2009.aspx

what is new for EDI/AS2 in BizTalk 2009

Below is excerpts from BizTalk 2009 documentation about new features in BizTalk EDI /AS2 (BizTalk 2009):

EDI Enhancements

Electronic Data Interchange (EDI) is one of the most prevalent means by which businesses exchange data electronically. It represents approximately 75 percent of all business-to-business electronic transactions and grows at about 5 to 7 percent per year. EDI usage entails message syntax and standards (including ANSI X12 and UN/EDIFACT), messaging protocols, and transports.

BizTalk Server 2006 R2 introduced the ability to process EDI messages using EDI pipeline components, as well as AS2 support. BizTalk Server 2009 improves EDI support with the following features:

Dynamic EDI Envelope Generation:

· Override EDI envelope settings at runtime by setting context properties.

· Values configured in party resolution are used unless the specific value is overridden.

Multiple Batches

· Multiple batch configurations can be created for each party.

· Batch lifecycle can be managed individually.

HIPAA

· HIPAA schemas now support equivalent segments.

AS2 Enhancements

Transmitting EDI transactions over the Internet is an increasingly popular alternative to sending and receiving EDI using value-added networks (VANs). Using the Internet for data exchange reduces costs, increases efficiency, and has advantages in terms of redundancy and scalability.

To support this growing trend, BizTalk Server 2006 R2 introduced support for EDIINT AS/2 (Applicability Statement 2). AS/2 is a specification that enables transport of business data over the Internet in a safe and reliable manner. BizTalk Server uses AS/2-defined methods to send, receive, encrypt, decrypt, decompress, sign, and verify signatures between partners using HTTP over the Internet. BizTalk Server helps ensure the security of messages through the use of encryption keys, digital signatures, certificates, and non-repudiation.

BizTalk Server 2009 introduces the following AS/2 features:

· Drummond Group certified for multi-file attachment support, file name preservation support and interoperability.

· Resend messages if an MDN has not been received within a specified time frame.

· Send and receive multiple file attachments.

· Preserve attachment file names.

人氣 () | 回應 (0) | 引用 (0)

February 27, 2009

BizTalk AS2憑證存放地方

willeam 在天空部落發表於00:27:15 | BizTalk Server

在開發BizTalk AS2專案時,因為通常需要做signing與Encryption,所以需要在BizTalk的主機上註冊Certificate,不同的Certificate需要放到不同的地方,比如:自己的private Key與客戶的public key所放置的地方就不一樣.
下列表格摘錄自微軟網站,主要是說明Certificate的存放地點,還有當需要用來做signing與encrypt時,需要在BizTalk的哪個地方做設定,我個人是覺得滿清楚的啦.
http://msdn.microsoft.com/en-us/library/bb728096.aspx

Certificate Usage	Certificate Type	Pipeline Component	User Context	Certificate Store	Where Defined
Signature (outbound)	Own private key (.pfx)	MIME/SMIME encoder	Account used by the host instance associated with the send handler.	Current User\ Personal store of each BizTalk server that hosts a MIME/SMIME encoder pipeline as each host instance service account	Certificate page of the Group Properties dialog box
Signature verification (inbound)	Trading partner's public key (.cer)	MIME/SMIME decoder	Account used by the host instance associated with the receive handler.	Local computer\Other People store of each BizTalk server that hosts a MIME/SMIME decoder pipeline as each host instance service account	Certificate page of the Party Properties dialog box Note: The certificate used to verify a signature for a party must be unique from the certificates used to verify signatures for other parties.
Encryption (outbound)	Trading partner's public key (.cer)	MIME/SMIME encoder	Account used by the host instance associated with the send handler.	Local computer\Other People store of each BizTalk server that hosts a MIME/SMIME encoder pipeline	Certificate page of the Send Port Properties dialog box
Decryption (inbound)	Own private key (.pfx)	MIME/SMIME decoder	Account used by the host instance associated with the receive handler.	Current User\Personal store of each BizTalk server that hosts a MIME/SMIME decoder pipeline as each host instance service account	The AS2 Decoder will determine the certificate based upon certificate information in the message. For the BizTalk MIME Decoder, the certificate must be in the Certificate page of the host used for receiving the message. This is not necessary for the AS2 Decoder.

人氣 () | 回應 (0) | 引用 (0)

BizTalk Server,ASP.NET,SQL Server心得分享日誌(技術來自)

what is new for EDI/AS2 in BizTalk 2009