BizTalk PowerShell Urls

BizTalk Server Applications: Get/Start/Stop
https://blogs.msdn.microsoft.com/powershell/2006/09/02/biztalk-server-applications-getstartstop/



ApplicationManager (BizTalk Server Sample)
https://msdn.microsoft.com/en-us/library/dd257074.aspx

Logic App PowerShell: Login to Azure Integration Services by powershell GUI

Login-AzureRmAccount

Get-AzureRmSubscription –SubscriptionName "RG-Name" | Select-AzureRmSubscription

GAC DLL BY power shell script.

Open Powershell script ISE window as Admin credentials.


[string] $location = "D:\personal\BRE\BRE.Project\BRE.ProjectCL\bin\Debug\"
[string] $dllName = "BRE.ProjectCL.dll"

Set-location $location

[string] $dlllocation =  [string]::Format("{0}{1}",$location,$dllName)


[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")
          
$publish = New-Object System.EnterpriseServices.Internal.Publish  
       
$publish.GacInstall($dlllocation)

LIST OF EDIFACT URLS

EDIFACT URLS

LIST OF TRANSACTION TYPES
http://redtailsolutions.com/products-and-services/included-edi-services/transaction-types/

https://www.stylusstudio.com/edifact/

Difference between EDI FACT  and X12

UNITED NATIONS

Agreements from a BizTalk perspective

850 EDIFACT DETAILS 

http://www.truugo.com/edifact/d96a/orders/
http://www.truugo.com/edifact/d98b/

GAC ASSEMBLY IN POST BUILD EVENT COMMAND LINE

"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\gacutil.exe" /i $(TargetPath)

C:\Windows\Microsoft.NET\assembly\GAC_MSIL

Biztalk Acid Properties

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.

Atomicity

A transaction represents an atomic unit of work. Either all modifications within a transaction are performed, or none of the modifications are performed.

Consistency

When committed, a transaction must preserve the integrity of the data within the system. If a transaction performs a data modification on a database that was internally consistent before the transaction started, the database must still be internally consistent when the transaction is committed. Ensuring this property is largely the responsibility of the application developer.

Isolation

Modifications made by concurrent transactions must be isolated from the modifications made by other concurrent transactions. Isolated transactions that run concurrently perform modifications that preserve internal database consistency exactly as they would if the transactions were run serially.

Durability

After a transaction is committed, all modifications are permanently in place in the system by default. The modifications persist even if a system failure occurs.

If you absolutely must call a non-Serializable class, and can only do

it in an atomic scope, try to combine this with other operations to make the most of

the trip to the message box; like a send shape as shown in the following figure:

XLANG Message.

If you need to pass non-XML messages through an orchestration, you should really use XLANGMessage to do this.

Represents a message instance that is declared with an XLANG service.

All public members of this type are safe for multithreaded operations.

Better to read xml body part by using XMLReader rather than as XMLDocument.


public XmlReader func(XLANGMessage message)
{
message[0].RetrieveAs(typeof(XmlReader)) as XmlReader;
}