Biztalk hands-on Experiment (16) EDI-AS2 solution copywriting Development Configuration

1 course Introduction

This course is familiar with the development and configuration of EDI and as2 solutions. This hands-on experiment steps and content are completed using the Microsoft official SDK. The trainees complete this experiment with the official tutorials during the experiment.

This experiment is based on BizTalk 2013 (Windows Server 2012 64bit + SQL Server 2012 + BizTalk 2013 + Visual Studio 2012) and is also applicable to the BizTalk 2010 environment. As2 demo Folder: C: \ Program Files (x86) \ Microsoft BizTalk Server 2013 \ SDK \ as2 tutorial

2 Preparation 3 demonstration 3.1 deploy schema3.1.1 open the solution under the as demo \ schema folder and configure the BizTalk Application name as2demo. Confirm that the signature is correct.

3.1.2 deployment solution. The name of the deployed application is displayed in the BizTalk console.

3.2 configure partner 3.2.1 right-click and choose new partner

3.2.2 enter contoso in the name

3.2.3 create a partner in the same steps as 3.2.1-3.2.2: fabrikam

3.3 configure the IIS environment 3.3.1 open the IIS function view and click "handler mappings"

3.3.2 click Add script ing on the right of the window. In the Add script ing window, enter

Request Path: btshttpreceive. dll

Select c: \ Program Files (x86) \ Microsoft BizTalk Server 2013 \ httpreceive \ btshttpreceive. dll as the execution Program (note that you should select a 32-bit receiver)

Name: biztalkhttpreceive

3.3.3 click "request restriction" and click the verbs option page, as shown in, select one of the following verbs and enter post

3.3.4 Click OK to save. Select the newly created BizTalk HTTP receive processing ing. In the window on the right, select Edit feature permissions. In the displayed permission options, select execute.

3.3.5 return to feature view and click ISAPI and CGI restrictions

3.3.6 you can view the newly created constraint in the list. Click the row record to add remarks for it.

3.3.7 click OK save 3.4 configure the application pool and web application 3.4.1 click Add application pool in the IIS application pool and click OK save.

Name: biztalkapppool,. NET Framework Version: 4.0

3.4.2 select the application pool and click Advanced options, set to enable 32-bit applications to true, set the Application ID to administrator

3.4.3 right-click the default site and select create a new application.

3.4.4 In the displayed application configuration window, click OK to save the configuration.

Alias: fabrikam

Application pool: biztalkapppool

Physical path: as2 demo Folder \ fabrikam

3.4.5 create a contoso application in the same way as 3.4.3. Shows the application configuration. Click OK to save the configuration.

Application name: contoso

Application pool: biztalkapppool

Physical path: C: \ Program Files (x86) \ Microsoft BizTalk sever 2013 \ httpreceiver

3.5 configure BizTalk application 3.5.1 right-click as2demo and add its reference to BizTalk EDI application in reference to application property Configuration

3.5.2 create a one-way receiving port named receive_as2

3.5.3 create the receive_as2_http receiving location in Port receive_as2, select HTTP as the adapter, and click Configure. Go to HTTP adapter configuration, as shown in

3.5.4 select as2edireceive for the receiving position pipeline and click OK to save

3.5.5 create a dynamic one-way transmission port (send MDN messages)

3.5.6 enter send_async_mdn in the name

3.5.7 configure the expression in the filter as follows:

Ediintas. isas2asynchronousmdn = true

3.5.8 create a one-way sending port (send 997 messages)

Name: send_async_997

Adapter: HTTP

3.5.9 configuration shown in HTTP adapter attribute Configuration

Target URL: http: // localhost/fabrikam/default. aspx? Destination = _ 997 tofabrikam

3.5.10 click "OK" and select "as2edisend" for the sending queue.

3.5.11 configure the following conditions in the filter of the sending port and click OK to save

BTS. messagetype = http://schemas.microsoft.com/Edi/X12#X12_997_Root

 

Create a one-way sending port, send an edi xml message, the adapter is a file adapter, and the receiving channel is passthrutransmit.

Target Folder: C: \ Program Files (x86) \ Microsoft BizTalk Server 2013 \ SDK \ as2 tutorial \ _ edixmltocontoso \

The file name is % messageid %. xml.

3.5.12 configure the following subscription conditions in the Send Port filter and click OK to save

BTS. messagetype = http://schemas.microsoft.com/BizTalk/Edi/X12/2006#X12_00401_864

3.5.13 start the as2demo Application

3.6 configure as2 protocol 3.6.1 Right-click fabrikam_profile in the Partner List to create a protocol

3.6.2 configure general attributes as shown in

3.6.3 click the fabrikam-> contoso option page at the top and enter fabrikam, as-to in the AS2-From.

3.6.4 in the verification window, select "Use Agreement settings for validation and MDN instead of Message Header"

3.6.5 In acknowledgements (mdns), select reqeust MDN and request asynchronous MDN, and enter http: // localhost/fabrikam/default. aspx? Destination = _ mdntofabrikam

3.6.6 click the fabrikam option page and enter fabrikam in the AS2-From, contoso, as-

3.6.7 in send ports, select send_async_9973.6.8 and click OK to save and complete as2 Protocol configuration.

3.7 configure X12 protocol 3.7.1 right-click fabrikam_profile in the Partner List to create a protocol

3.7.2 configure general attributes as shown in

Name: x12agreement

Protocol: X12

Party: contoso

Business: contoso_profile

Select turn on reporting

Select store message payload for reporting

3.7.3 click the fabrikam-> contoso option page and configure in the identification window as shown in

Send ID qualifier (isa5): ZZ value (isa6): 7654321

Cycler ID qualifier (isa7): ZZ value (isa8): 1234567

3.7.4 select 997/999 expected in the acknowledgements window

3.7.5 clear the route ack to send pipeline on request-response receive port in the local host settings window

3.7.6 click the contoso-> fabrikam option page and configure in the identification window as shown in

Send ID qualifier (isa5): ZZ value (isa6): 1234567

Cycler ID qualifier (isa7): ZZ value (isa8): 7654321

3.7.7 in the character and separators window, select suffix as CR LF

3.7.8 configure the envelope in the transaction settings as follows:

Items used	Operation
Transaction type	Select the Message Type of your test message, such as "864-text message ".
Version/release	Enter 00401.
Target namespace	Select http://schemas.microsoft.com/biztalk/edi/x12/2006 ".
GS1	Verify the Message Type of the selected test message, such as "TX-text message (864 )".
Gs2	Enter "01 ".
GS3	Enter "7654321 ".
Gs5	Select the required time format. Select "hhmmssdd ".
Gs7	Select "T-transport data Coordination Committee (tdcc )".
Gs8	Verify that the EDI version is entered as 00401.

3.7.9 Click OK to save and restart the BizTalk host instance.

3.8 test 3.8.1 open the sender solution under the as2 demo folder and use the X12_00401_864-Sync.edi file for testing.

Start the program and you can view the received messages in the _ 997 tofabrikam, _ edixmltocontoso, and _ mdntofabrikam folders.

3.8.2 different test files can be used for testing at the same time to verify the corresponding business configuration.

Biztalk hands-on Experiment (16) EDI-AS2 solution copywriting Development Configuration