Very Tasty BizTalk Dishes

Creating EDI Parties and Agreements in BizTalk 2010

2012-07-05T21:29:00.004-07:00

Creating EDI Parties and Agreement in BizTalk 2010

1. Create EDI Parties and Business Profiles / Scenario

1.1 Customer Party

1.1.1 Sender of Purchase Order 850 V4010

1.1.2 Receiver of Invoice 810 V4010

1.1.3 Receiver of Acknowledgments 997 V4010

Step 1. Add new Party

Step 2. Add new Business Profile and enter the Business Identities

1.2 Home Role Party

1.2.1 Receiver of Purchase Order 850 V4010

1.2.2 Sender of Invoice 810 V4010

Step a. Add new Party

Step b. Add new Business Profile and enter the Business Identities

2. Create Agreement * Make sure to right click on the Business Profile for the customer and select new Agreement. Follow the screen shots

2.1For TestParty--> Home Party

2.1For TestParty--> Home Party ... continued

2.2 For Home Party--> TestParty

2.2 For Home Party--> TestParty ... continued

3. Other EDI Settings

Turn Off the Global Party / Fallback Property by un-checking the box under General Settings.

Created by: Amit Kumar
contact: technoamit@gmail.com
web-site: http://quicksolutionsinc.us/

Guidance / Setup : EDI over AS2 in BizTalk

2012-07-05T20:34:00.005-07:00

EDI over AS2 using BizTalk Server 2009/2010

v IIS 7 Configuration for BizTalk AS2

o Keys Components

- ISAPI Filters & Handler Mappings

- AS2 Web-Site and BizTalk App Pool

- Test the AS2 Web-site is reachable

- Step 1. ----------- ISAPI Filters & Handler Mappings

1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Select the root Web server entry and in the Features View, double-click Handler Mappings and then in the Actions pane, click Add Script Map.

Note

Configuring the script mapping at the Web server level will cause this mapping to apply to all child Web sites. Remove this mapping from the AS2 specific Web site or virtual folder under Default Web-Site

3.       In the Add Script Map dialog box, enter BtsHttpReceive.dll in the Request path field.
4.       In the Executable field, click the ellipsis (…) button and browse to drive:\Program Files\Microsoft BizTalk Server 2009\HttpReceive. Select BtsHttpReceive.dll, and then click OK.
5.       Enter BizTalk HTTP Receive in the Name field, and then click Request Restrictions.
6.       In the Request Restrictions dialog box, select the Verbs tab and then select One of the following verbs. Enter POST as the verb.
7.       On the Access tab, select Script, and then click OK.
8.       Click OK and when prompted to allow the ISAPI extension, click Yes.
9.       Right-click the BTSHttpReceive.dll entry, and then select Edit Feature Permissions.
10.    Ensure that Read, Script and Execute are selected, and then click OK.
11.    Click Features View, and then double-click ISAPI and CGI Restrictions.
12.    Ensure that an entry for BTSHTTPReceive.dll exists, and that Restriction is set to Allowed.

- Step 2. ----------- AS2 Web-Site and BizTalk App Pool

1. In IIS Manager, right-click Application Pools and select Add Application Pool.
2. In the Add Application Pool dialog box, enter BizTalkAppPool in Name, and then select .NET Framework V2.0.50727 in the .NET Framework version drop-down list.

Click OK.

Note

The version number may vary depending on the version of .NET Framework 2.0 installed on the machine.

3.       Select Application Pools, in the Features View select BizTalkApplicationPool, and then click Advanced Settings in the Actions pane.
4.       In the Advanced Settings dialog box, set Enable 32-Bit Applications to True.
5.       Select Identity and then click the ellipsis (…) button.
6.       In the Application Pool Identity dialog box, select Custom account and then click Set.
7.       Enter the User name and Password for a user account that is a member of the administrators group an is the BizTalk Service Account for the host that is running Receive and Send Handler Host for AS2 Ports/Adapter, enter the password in Confirm password and then click OK three times to return to the IIS Manager.
8.       In IIS Manager, open the Sites folder. Right-click the Default Web Site, and then select Add Application.
9.       In the Add Application dialog box, enter AS2Test in Alias, and then click Select.
10.    In the Select Application Pool dialog box, select BizTalkAppPool and click OK.
11.    Click the ellipsis (…) button and browse to drive:\Program Files\Microsoft BizTalk Server 2009\HTTPReceive for the Physical path.
12.    Click Test Settings and verify that there are no errors displayed in the Test Connection dialog box. Click Close, and then click OK.
13.    In IIS Manager, select the AS2Test virtual directory and in Features View, double-click Authentication.
14.    In Authentication, select Anonymous Authentication and verify that the Status is Enabled. If the Status is Disabled, click Enable in the Actions pane.

- Step 3. ----------- Test the AS2 Web-site is reachable

1. Create a default.htm in the HTTPReceive Folder under BizTalk Install directory

2. In IIS Manager right click the AS2 application and browse

3. The default browser should open and show the default.htm

v Certificates

1. Install Certificate Services on Windows Server 2008 by adding Certificates to the Server Roles

2. Generate a CSR from the Certificate Manager

3. Generate the Private certificate on the server

Note

Alternatively, a certificate can be purchased from VeriSign® or other providers so that the CA Root Authority is more standard and available when dealing with outside Trading Partners. Especially when Servers are not exposed to the Internet.

4. Install the Private Key on the BizTalk Server Certificate Store under Personal

5. Generate a Public key and send this off to the External Trading Partners

6. Install External TP’s Public Certificate under Other People and Trusted People

7. Select the Private certificate under BizTalk Server Group
8. Select TP’s Public Certificate under Send Port

9. Select self Public Certificate under Party

Note

All Certificate related activities and configuration above should be performed as BizTalk Service Account

v EDI Approach/Considerations for AS2

o To Receive EDI over AS2 communication:

There will be one URL given to Trading Partners to send the AS2 communications to HOME ROLE (SELF). The URL is public facing on the HOME ROLE (SELF) DMZ. After the message is received, the URL will be NAT’ed to the IIS Server inside HOME ROLE (SELF) Firewall which is hosted on local BizTalk Server (AS2 Web-Site).

A Request-Response Type (2-Way) BizTalk Receive Port is setup to listen to the local IIS URL. The Receive Location will use AS2EDIReceive Pipeline for receive side and use AS2Send Pipeline on the send.

The Receive side does AS2 and EDI resolution. The send side is non-EDI AS2 pipeline to send MDN back to the sender

Once the message is received successfully, send ports for each respective party can be created to perform mapping functions to the canonical etc…. Alternatively if Orchestrations are used, direct binding can be done using similar or additional set of Context Properties from the BizTalkMsgBox. Context properties to be used:

a. BTS.MessageType

b. BTS.ReceivePortName

c. EDI.ISA06

d. EDI.ISA08

o To Send EDI over AS2 communication:
Once a message is ready to be sent out over AS2, a One Way Solicit Response Send Port is required which will use AS2EDISend Pipeline for send side and AS2Receive for the receive side of the Send Port

The send side will assemble EDI, encrypt and sign the message with customer public key and receive side will be used to AS2 received the MDN sent by the customer

v Setting up Ports and AS2 Party

o Receive Port – this should be a “Request-Response” Receive Port

§ This is a common port that is created keeping in mind that all customer communications will come to the same port as explained in the approach above

· ReceivePort All AS2

o RecevieLocation All AS2

Adapter Used: HTTP | URI: /{IIS Virtual Dir. Name under Default Web Site}
Receive Pipeline: AS2EDIReceive
Send Pipieline: ASSend

o AS2 Send Port for Trading Partner

Create a new Send Port which is one Way Solicit Response Port. Create Configuration as follows:

· SP.CustomerName.All.AS2.Out

-Adapter Used: HTTP | URI: http://PartnerURL}
-Send Pipieline: AS2EDISend
-Receive Pipeline: AS2Receive
-Select the Partner Certificate under Certificates for this Send Port

o AS2 Party

· Create new Party. Right Click on the properties and then follow the screen shot below: Select the Send Port for AS2 Outbound created above under this party Send Ports.

· Also Select the Trading Partner Certificate under Party Properties-Certificates ection

v Certificate Setup

Message or MDN	Direction	Certificate Type	Certificate Owner	Public or Private	Certificate Location	Where to configure
Message	Outbound	Signing	Home Org	Private	Personal certificate store of in-proc host user	BizTalk Group / Properties / Certificate
Message	Outbound	Encryption	Partner	Public	Other People certificate store of local computer	Send port / Certificate
Message	Inbound	Signing	Partner	Public	Other People certificate store of local computer	Party / Certificate
Message	Inbound	Encryption	Home Org	Private	Personal certificate store of in-proc host user	Isolated Host / Certificates
MDN	Outbound	Signing	Home Org	Private	Synch MDN: Personal certificate store of isolated host user Asynch MDN: Personal certificate store of in-proc host user	BizTalk Group / Properties / Certificate
MDN	Inbound	Signing	Partner	Public	Other People certificate store of local computer	Party / Certificate

Created by: Amit Kumar
contact: technoamit@gmail.com
web-site: http://quicksolutionsinc.us/

Reference: MSDN.com

Convert / Migrate BizTalk 2002 Maps

2012-06-05T14:29:00.004-07:00

Convert BizTalk 2002 Maps to new versions of BizTalk.

Tested in BizTalk 2006R2, 2009 and 2010

Firstly the BizTalk 2002 map is in XML format.
Copy the map xml file and then rename that to .btm (this is the extension of the map file in new BizTalk versions)
Create a new BizTalk Project in Visual Studio of new BizTalk version environment
In Solution Explorer, right click on the project and select “Add Existing Item”
Add the renamed file in step # 2
After the {file}.btm appears in Solution Explorer, you can simply double click to open the map.
This action created the Source (_src) and Target (_trg) schemas and a map is now migrated to the new version.
After migration, you will have to change a few things from traditional VB Script to VB .NET and possibly remove custom functoids if any and replace with something more out of box

** Remember not to judge the mapping. After all it is a historical artifact J and people did their best to use the tool with limited knowledgebase compared to present times.
(And no Google/Bing to rescue)

Also, if you are reading this and have to do this migration task at present time (Year 2012) there is someone else trying to save their sweet spot job and know nothing beyond BizTalk 2002? Watch Out and good luck with politics!

Enjoy! Hope this is still useful to someone!

Created by: Amit Kumar
contact: technoamit@gmail.com
web-site: http://quicksolutionsinc.us/

WCF Adapter Action Issue

2012-06-04T11:09:00.002-07:00

Issue with WCF.Action or other WCF properties at Run-Time

I am postign this article for a very specific purpose. After I posted the topic on dynamically setting the WCF Action for the Custom WCF Adapter based Send Port, some folks running BizTalk 2009 or older reported that they faced the following issue:

1. Even though the WCF.Action property is promoted, at run time the Adapter fails to read the promoted property from the message context. They get an error message stating the Action is not in the specified Action. Look at the screen shot below.

Error when WCF.Action is not passed or read by the WCF Adapter

Error Description from event Log:

The adapter failed to transmit message going to send port "Send_to_SAP_Generic_ODX" with URL "sap://CLIENT=100;LANG=EN;@a/SERVERNAME/99?&RfcSdkTrace=False&AbapDebug=False". It will be retransmitted after the retry interval specified for this Send Port. Details:"Microsoft.ServiceModel.Channels.Common.UnsupportedOperationException: Incorrect Action <BtsActionMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

</BtsActionMapping>. Correct the specified Action, or refer to the documentation on the allowed formats for the Actions. Note that Actions are case-sensitive.

Before I dive into the possible solutions, let me share what I learnt while troubleshooting this issue. First I was able to reproduce it by starting with a vanilla (run-time) only BizTalk 2009 Environment with NO Visual Studio (actually Visual Studio presence is really irrelevant), but nevertheless.

Ø Solution(s):

o Download and install the Cumulative Update 5 or 6 for BizTalk Server 2009, 2006 R2 (remember WCF adapter stuff does not apply to BizTalk versions prior to R2 release)

Cumulative Update 5

http://support.microsoft.com/kb/2649852

Cumulative Update 6

http://support.microsoft.com/kb/2689457

Recommended Fix for Production or QA environment:

Although the best practice states that install the latest updates instead of the following short-cut. However read on…

Now the cumulative update installation might warrant an outage. So, if a temporary fix is required for critical run-time environments, it will probably make sense to fix the problem at hand only. This also applies to situations where there are complex integration services hosted on BizTalk and a planned outage is required and waiting for a longer time to get the Cumulative Updates is inevitable.
In that case, the culprit dll is Microsoft.BizTalk.Adapter.Wcf.Runtime.dll
Get the newer Microsoft.BizTalk.Adapter.Wcf.Runtime.dll from the dev environment where Cumulative Patch is applied and install to GAC on the target computer

Gacutil –if “{path\ Microsoft.BizTalk.Adapter.Wcf.Runtime.dll} à New dll

No need to restart host instances
Also, you can resume the suspended instances they should read the property and move on!

Created by: Amit Kumar
contact: technoamit@gmail.com
web-site: http://quicksolutionsinc.us/

Generic Process to Send Any IDOC’s to SAP via WCF SAP Adapter

2012-05-18T15:09:00.000-07:00

Dynamic WCF Action Assignment

Generic Process to Send Any IDOC’s to SAP via WCF SAP Adapter

Ø Subject: Setting the WCF Action dynamically in a BizTalk Application

Ø Applies to: BizTalk 2006 R2 and up

Ø Recipe: BizTalk Send Port, BizTalk Orchestration

Ø Example Participants: WCF-SAP Adapter

Ø Overview:

This example focuses on sending multiple IDOC messages to SAP, all using one Send Port. Often times there is a need to limit the number of LOB ports that can be created as it necessitates giving usernames and passwords to multiple people or when password changes there are multiple places to change which can be cumbersome and also error-prone.

By having one point of entry to a LOB system (SAP) in this case enables to have more control and management over the entry points. Specifically, I have found this useful when there are planned outages or maintenance on the LOB systems. In other words there is one place to look from support perspective when something happens.

Ø Logistical Setup of this Orchestration:

1. Create a BizTalk Project and Add New Item…..and select Orchestration. (not getting into the naming conventions etc…maybe another blog idea)

2. Add the following shapes in top-down sequence

a. Receive

b. Expression

c. Message Assignment

d. Send

3. On the Port Surface, add 2 Logical ports:

a. Always Receive messages and Specify Later

b. Always Send messages and Specify Later

4. Add 2 Message Type:

a. Incoming Message:

i. Name: msg_AnyIdocXML_In

ii. Type: System.Xml.XmlDocument

b. Outgoing Message

i. Name: msg_AnyIdocXML_Out

ii. Type: System.Xml.XmlDocument

5. Add one variable

a. Name: MsgNS

b. Type: System.String

6. Add one Correlation Set and Correlation Type. Steps:

a. Right click Correlation Set and Select New

b. Under properties change name if required

c. From Correlation Type Drop-down select “Create new Correlation Set”

d. The screen jumps to the Correlation Set Property….look for “Correlation Properties”

e. Click the … and it will bring up the following screen.

f. Expand the “WCF” section and Add “Action”

i. This is the property which is equal to the Namespace of the IDOC Schema that was generated using the Consume Web Service option (another blog on this)

ii. This property can be different depending on which WCF end-point we need to send these messages to.

Ø At the end of this you should see the Orchestration in the following order and similar properties etc…I am putting certain screen shots but you get the idea (naming convention excluded).

Ø Now we need to button up the Orchestration in the following order (not necessary however, it’s a good development practice so we don’t miss something)

A. Receive Shape:

a. Select the message “msg_AnyIdocXML_In” created before from the drop down

B. In the Get Vars Expression Shape put the following one line code:

MsgNS = xpath(msg_AnyIdocXML_In, "string(namespace-uri(/*))");

· This is assigning the variable “MsgNS”the namespace of the received IDOC XML message as in my example IDOC Namespace is the same as the WCF Action needed by the Send Port to send this message to SAP using WCF SAP Adapter

C. On the Message Assignment Shape set

a. Select Message Constructed property = “msg_AnyIdocXML_Out” created before from the drop down

b. Double Click the Message Assignment inside the Construct Message and enter the following code:

msg_AnyIdocXML_Out = msg_AnyIdocXML_In;

msg_AnyIdocXML_Out(WCF.Action)=MsgNS;

· This is passing the incoming message and assigning it to the outgoing message type

· Then it is setting the WCF Action and assigning the Namespace value captured before

D. Send Shape:

a. Select the message “msg_AnyIdocXML_Out” created before from the drop down

b. From the drop down for Initializing Correlation Sets, select the Correlation set created before (Step # 6)

E. Drag the Receive Logical Port to the Receive Shape.

F. Then Activate the Receive Shape

G. Drag the Send Shape to the Send Logical Port

Ø Sign and set the deployment for the project and deploy. Right Click Project – Deploy

Ø Run Time Setup after deployment.

A. Open BizTalk Administration Console and expand to the application where the Orchestration is deployed.

B. Created a Physical Receive Port to pick up any SAP IDOC XML Files.

§ This is important to note as this will be the generic location that all the other processes (post-mapping etc…) will submit files to

C. Create a Send Port with WCF-Custom Adapter

§ Select WCF-Custom on the Adapter list drop down

§ Click Configure …

§ For the Address URI (address for WCF Endpoint) SAP in this case enter the following: (again this is the basic connection string, which you may need to change based on your requirement)

sap://CLIENT=100;LANG=EN;@a/{SAP Server Address/IP}/{Client ID}?&RfcSdkTrace=False&AbapDebug=False

** Note the underline text between curly brackets is the environment specific value.

§ Under Binding Tab Select the Binding Type = “sapBinding”

§ Under Credentials Tab select the appropriate option and enter the details. Usually there is a user assigned by SAP Team with a password
§ Go back to the General Tab and here is the Fun Part:

· Under SOAP Action Header put the following

</BtsActionMapping>

§ Pay attention to the text in RED above.

§ The Operation Name should be the same as set in the Orchestration

§ By Default this name is “Operation_1” like it adds in Orchestration when you first create it. Until you purpose fully change it which you should to make it more tuned to what it is.

§ Secondly, the Action is supposed to be blank as this is what the Orchestration is actually setting and promoting as a Context property

§ If this Action element has an value, then it simply overrides the value coming from Orchestration making the orchestration use pretty much useless.

D. After all the above setup

§ Go to the Orchestration and bind the orchestration with:

· Host

· File based Receive Port created in Step B

· WCF-Custom based Send Port created in Step C

E. Start the Ports and Orchestration

F. You are ready to test and implement this Generic IDOC loader process.

Ø Other Considerations:

1. In this example I needed the WCF.Action property to be dynamic for SAP Adapter /Send Port Setting.

2. However this can be used to dynamically assign other properties like:

a. Target LOB Server Address

b. User ID and Password

3. These values can of-course be read from SSO DB or some other secured way (Enterprise Library?) – Complicated ways or

4. Simply these values can be read from a standard XML config File like BTSNTSvc.exe.config

Created by: Amit Kumar
contact: technoamit@gmail.com
web-site: http://quicksolutionsinc.us

Starting ...finally Introductions...

2012-05-11T09:37:00.000-07:00

Dear Reader,
I have been writing technical articles for so many years for my customers and partners. However, I could never get to sharing my learnings via a blog of some sort. I have been preparing so many tasty dishes using BizTalk which I have served my customers over these years...when I look back I can't help think and go..."Really I did that..WOW"

Anyhow...I always wanted to share the Integration lessons I learnt over the years doing BizTalk and EDI. Needless to say I am still learning some new things which you will see in the upcoming blogs.

So I made a schedule where I will post atleast one Topic per week. that should get me 52 posts a year. I think it is a decent start considering my schedule.

Hopefully someone benefits from all this. After all that is the purpose of sharing the knowledge.

-amit
http://quicksolutionsinc.us/