BizTalk SendPort Macros

Today I needed to get an onverview of what macros that are available out-of-the-box wend sending a message to a filebased destination. These should work for FILE and FTP adapter.

  • %datetime% : Coordinated Universal Time (UTC) date time in the format YYYY-MM-DDThhmmss (for example, 1997-07-12T103508)
  • %datetime_bts2000% : UTC date time in the format YYYYMMDDhhmmsss, where sss means seconds and milliseconds (for example, 199707121035234 means 1997/07/12, 10:35:23 and 400 milliseconds).
  • %datetime.tz% : Local date time plus time zone from GMT in the format YYYY-MM-DDThhmmssTZD, (for example, 1997-07-12T103508+800).
  • %DestinationParty% : Name of the destination party. The value comes from message the context property BTS.DestinationParty.
  • %DestinationPartyID% : Identifier of the destination party (GUID). The value comes from the message context property BTS.DestinationPartyID.
  • %DestinationPartyQualifier% : Qualifier of the destination party. The value comes from the message context property BTS.DestinationPartyQualifier.
  • %MessageID% : Globally unique identifier (GUID) of the message in BizTalk Server. The value comes directly from the message context property BTS.MessageID.
  • %SourceFileName% : Name of the file from where the File adapter read the message. The file name includes extension and excludes the file path, for example, foo.xml.
  • %SourceParty% : Name of the source party from which the File adapter received the message.
  • %SourcePartyID% : Identifier of the source party (GUID). The value comes from the message context property BTS.SourcePartyID.
  • %SourcePartyQualifier% : Qualifier of the source party from which the File adapter received the message.
  • %time% : UTC time in the format hhmmss.
  • %time.tz% : Local time plus time zone from GMT in the format hhmmssTZD (for example, 124525+530)


 All these properties are in the message context and may be changed when createing a message in an orchestration like this for SourceFileName.

 I have created a new message called myNewMessasge in a MessageAssignment shape like this:
 myNewMessage = myOldMessage, 
coying the context : myNewMessage(*) = myOldMessage(*) 
and setting the new fileName : myNewMessage(FILE.ReceivedFielName) = myNewFilename.xml

Comments

Post a Comment

Popular posts from this blog

Illegal 'activate' predecate

Image
I am creating a orch that has filter on the initial receive shape. When building I got these error: Error 1 : identifier 'MySolutionname' does not exist in 'MyOrchName'; are you missing an assembly reference? Error 2: cannot find symbol 'MySolutionname' Error 3: an 'activate' predicate rvalue must be a string, character, boolean or numeric literal Error 4 : illegal 'activate' predicate The solution to this is to put the filter expression in sting literals (i.e. “double quotes”)
Read more

BizTalk Host "Stop Pending"

When restarting a BizTalk host I experiences that it would not restart. The service was stuck in a "Stop Pending" state. It seem that the only way to get the host back up, is to terminate the process and the start it. When i tried to restart fro BizTalk Administration Console nothing happen. I had to user the End Task function in Task Manager To get the correct instance i needed to find the correct instance. The only way to be sure to get the right one is to find the Process ID (PID) This might be found by using the command prompt using tasklist /SVC /fi "imagename eq btsntsvc.exe" This will list all BizTalk hosts like this Image Name              PID  Services ============= ================================ BTSNTSvc.exe            2376 BTSSvc$Rcv_x32_1_FTP_H BTSNTSvc.exe            2396 BTSSvc$Rcv_x32_1_JNBridge_H_ActiveMQ BTSNTSvc.exe            2416 BTSSvc$Rcv_x32_1_JNBridge_H_OracleAQ BTSNTSvc.exe            2436 BTSSvc$Rcv_x32_1_Random_H BTSNTSvc.ex
Read more

The Messaging Engine failed to register an adapter "WCF-BasicHttp". Details: "Registering multiple adapter types within the same process is not a supported configuration. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process

Image
When deploying a wcf service to biztalk the is a good chance you will run into: The Messaging Engine failed to register an adapter "WCF-BasicHttp". Details: "Registering multiple adapter types within the same process is not a supported configuration. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process" Solution When installting a SOAPm HTTP or WCF service on the same WebServer then seperate app pools must be created for each adapter. Using seperat app pools will solve the issue. Note the this is only a problem om win servers as desktop version of windows does not have an app pool concept.
Read more