|
Home > Archive > BizTalk Server Orchestration > November 2005 > Create a new istance of Bizztalk Orchestration
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Create a new istance of Bizztalk Orchestration
|
|
| Francesco 2005-11-28, 7:49 am |
| Hello,
I have an orchestration in Biztalk that works fine!
I want to make a copy of this Application, creating a new istance of Bizztalk.
- First, I have create a new Virtual directory in IIS.
- Second I have copy my Biztalk project and renaming this last!
- I have changed the url on receive Port, giving the new Virtual directory
name.
- Then what can I do?
(if i deploy the project, biztalk tells me that there is just another
istance of Orchestration!!)
thanks,
Francesco
| |
| Marian Drumea 2005-11-28, 6:02 pm |
| Hi Francesco,
Please explain what are trying to accomplish, because I am sure you
will find that BizTalk works a little different than what you think
right now. I understand that you are actually trying to deploy the same
assembly on the same BizTalk installation.
If your goal is to have the same orchestration triggered by another
location, you can "play" with receive locations. The nice concept is
that you can abstract the physical location(s) when you deal with the
business process (orchestration) and you don't really care which
orchestration subscribes to any incoming message when you srtup the
receive port/location.
Anyways, the idea is to share with us what you are trying to do and we
should be able to help, no matter the problem.
Thanks,
Marian
http://www.MarianDrumea.com/BizTalk
| |
| Francesco 2005-11-29, 2:48 am |
| Yes,
I want to have the same orchestration triggered by another location.
How can I do?!
How can I play with the receive port?
I must do a copy of Biztalk project and change the url on the receive port,
only??
Thanks,
Francesco
"Marian Drumea" wrote:
> Hi Francesco,
>
> Please explain what are trying to accomplish, because I am sure you
> will find that BizTalk works a little different than what you think
> right now. I understand that you are actually trying to deploy the same
> assembly on the same BizTalk installation.
>
> If your goal is to have the same orchestration triggered by another
> location, you can "play" with receive locations. The nice concept is
> that you can abstract the physical location(s) when you deal with the
> business process (orchestration) and you don't really care which
> orchestration subscribes to any incoming message when you srtup the
> receive port/location.
>
> Anyways, the idea is to share with us what you are trying to do and we
> should be able to help, no matter the problem.
>
> Thanks,
>
> Marian
> http://www.MarianDrumea.com/BizTalk
>
>
| |
| Marian Drumea 2005-11-29, 5:55 pm |
| Hi Francesco,
Perfect. BizTalk is good with this. When you bind an orchestration to
receive elements, you are binding to the port, not to the location.
Now, a port can have multiple locations and it will be enough for you
to create alternate locations under that initial port for where you
want to receive the messages from (not necessarily files). I would
restart BTS after this. Use a .bat file including these lines for
restart or restart the service directly:
net stop "BizTalk Service BizTalk Group : BizTalkServerApplication"
net start "BizTalk Service BizTalk Group : BizTalkServerApplication"
Let me know if this is solving your problem, but it is a nice
demonstration of BizTalk's powerful features. Therefore, you reuse
exactly the same business process (orchestration). Creating another
project or orchestration to do exactly the same would be redundant and
inefficient.
Thanks,
Marian
http://www.MarianDrumea.com/BizTalk
| |
| Francesco 2005-11-29, 5:55 pm |
| Hi,
ok, the problem is that I want have a Biztalk application of test.
The second istance of Biztalk is different from the first.
the second servs me to test new operations!
All the two Biztalk application, uses the same WebServices!
How can I do?
Thanks,
Francesco
"Marian Drumea" wrote:
> Hi Francesco,
>
> Perfect. BizTalk is good with this. When you bind an orchestration to
> receive elements, you are binding to the port, not to the location.
> Now, a port can have multiple locations and it will be enough for you
> to create alternate locations under that initial port for where you
> want to receive the messages from (not necessarily files). I would
> restart BTS after this. Use a .bat file including these lines for
> restart or restart the service directly:
>
> net stop "BizTalk Service BizTalk Group : BizTalkServerApplication"
> net start "BizTalk Service BizTalk Group : BizTalkServerApplication"
>
> Let me know if this is solving your problem, but it is a nice
> demonstration of BizTalk's powerful features. Therefore, you reuse
> exactly the same business process (orchestration). Creating another
> project or orchestration to do exactly the same would be redundant and
> inefficient.
>
> Thanks,
>
> Marian
> http://www.MarianDrumea.com/BizTalk
>
>
| |
| Marian Drumea 2005-11-30, 2:48 am |
| If you want distinct assemblies that you can deploy and undeploy
independently, then you can do what you mentioned in your first
message, but change the assembly name, namespace, and/or type name for
the orchestration, so it will not collide with the existing one.
Anyways, the clarification on your last message contradicts a previous
one, because of: "I want to have the same orchestration triggered by
another location."
With a new assembly you get a distinct orchestration.
Of course, you can also create a copy of the same orchestration within
the same assembly and give it a new name.
I hope I got it right this time  , but don't hesitate to contradict me
if not.
Thanks,
Marian
http://www.MarianDrumea.com/BizTalk
|
|
|
|
|