One BizTalk 2006 for many Commerce Gateways

toor

Hi folks,

I've a BTS2006 with CGRS installed. I want to use that server for different NAV databases. So I decide to create an BizTalk application for every NAV DB. The Problem is that I don't know, how to set up different CG Receive Locations.

In the CGRS there must be hard coded the uri [url=CG://Navision_To_CommerceGateway]CG://Navision_To_CommerceGateway[/url], so I only can set up one receive location for this uri. But I need to have an own cg receive location for each application.

In the other direction (BTS to NAV) I don't have any problems because I just need to setup different NAS with different TCP ports.

Any ideas how to solve this?

rg
tobias

rsebsa

Tobias

If you can provide a little more information I may be able to help ...

Are you running seperate physical Nav databases, each with it's own NAS instance?

What version of Nav are you running?

All the same versions for each database?

Are you using the latest Biztalk binaries provided by MS?

Are you dealing with multiple companies in a single database?

Regards

Rob

mandyk

toor wrote:

Hi folks,

I've a BTS2006 with CGRS installed. I want to use that server for different NAV databases. So I decide to create an BizTalk application for every NAV DB. The Problem is that I don't know, how to set up different CG Receive Locations.

In the CGRS there must be hard coded the uri [url=CG://Navision_To_CommerceGateway]CG://Navision_To_CommerceGateway[/url], so I only can set up one receive location for this uri. But I need to have an own cg receive location for each application.

In the other direction (BTS to NAV) I don't have any problems because I just need to setup different NAS with different TCP ports.

Any ideas how to solve this?

rg
tobias

Hi Tobias,
I guess it is alright if you use the same CG receive port from many NAV database. The pipeline for it must be XML Receive, and as long as the message type is unique within many NAV databases, the biztalk orchestration capable to route the message correctly.

The only issue perhaps because of some of your NAV database could sending the same message type, ALAS, then you should create an orchestration that checking certain xml node by promoting them, then put a condition functoid and branching the process and the send it thru different sending port if necessary.

I hope you got the picture and help you

8)
Mandyk