Tag: biztalk

February 10, 2010 Dev

BizTalk Port Changer


Last month i was assigned to find a solution to move our Database to new DB Server. And we use BizTalk 2004 to do some part of my applicaton.

In normal method we must export binding files in every Dll and change its configuration to new DB Server. But I have over 40 Dll with so many ports with SQL Adapter Type. It take time and easy to miss somewhere in binding file Then someone in twitter suggest me to play with ExplorerOM Libary  (Microsoft.BizTalk.ExplorerOM.dll)


And i make little app to do this for me  :  “BizTalk Port Changer”

Feature :

  • Show All Port in this Server (Refer to same BizTalk Management DB)  (Now Support only SQL,  FILE,  MQ Series and FTP ) with criteria
  • Show Port Username and Password (hope this feature don’t make u into darkside ^^”) i make it for check current of username and password of SQL and FTP port
  • Change Username , Password and Address of SQL Port
  • Export Port Configuration (to text file)


Hope this can help someone who must do something like me. Try this and make it better !!


Run on Win XP


Run on Win 2003


Note :

  • User will run this app must has authorize to access BizTalk Management DB (BizTalkMgmtDb) with Windows Authen Mode
  • At first Select Server Address and BizTalk Management DB and press Set Connection

Download here : BizTalk Port Changer

Source :  BizTalk Port Changer Source

September 23, 2009 Tech

A4SWIFT Message Pack 2009 Trailer Problem

I’m working with the Microsoft BizTalk Accelerator for SWIFT (A4SWIFT) for Biztalk 2004. And now it’s time to upgrade our A4SWIFT to version of Message Pack 2009 which announce by SWIFT.

 

Since I downloaded the Message Pack 2009 from Microsoft and start to migrate with my App.I found something abnormal with the Trailer of the message.

 

In Trailer Part of All Schema (MTxxx.xsd) and The External Trailer Schema (SWIFT Trailer.xsd) Tag MAC and PAC was removed by A4SWIFT but i can’t find this change in SWIFT Standard Release Guide 2009

{5:
  {MAC:MessageAuthenticationCode}
  {PAC:ProprietaryAuthenticationCode}
  {CHK:Checksum}
  {SYS:SystemOrientedMessage}
  {TNG:}Training
  {PDE:PossibleDuplicationEmission}
  {DLM:}DelayedMessage
  ...
}
{S:
  {AllianceTrailerData }
}


Now i try to ask this to MS Support and If anybody know about this issue please let me know and if have more progress  i’ll update later.


======== 25/09/2009  Updated =========

After my team call support from decillion (SWIFT Support in Thailand) and search from User Handbook in swift.com

found that SWIFT removed MAC and PAC Tag after lunch RMA (SWIFTNET Phase II) because MAC and PAC Tag use for PKI signatures and now they don’t use it anymore

but SWIFT Alliance Gateway still  generate MAC tag  like  {MAC:000000} for Application use. We can configuration at interface of SWIFT Alliance Gateway for remove  this tag and it will not send MAC and PAC to our application.


Summary : We’ll change configuration  at interface of SWIFT Alliance Gateway for remove MAC Tag and then Apply our application Schema follow the A4SWIFT Schema from Microsoft.


Attach : A practical guide to SWIFTNet Phase 2




A practical guide to SWIFTNet Phase 2 –

Scroll to top