Hi ,

I have created a new send port in my orchestration along with other logic changes. Now in order to deploy the new changes to live I can only put the new DLL onto live server and restart the BizTalk services in order to check if the changes are working fine? because the new Send port is a Direct Bound Self Correlating port so no physical port is created in console. will copying of just the DLL doesn't help ?

OR

do I need to create a msi package by exporting and then import in live server along with copying the DLL . please suggest.

Hi Lathaa,

If your application is not referenced to other one then you can do deployment with new DLL only. But if it refereed to other application then you need perform deployment with new orchestration dll as well as refereed dll.

Note: Please restart your host instance once deployment done.

When Deploying BizTalk apps, you must always follow the correct procedure which includes Import and Install.

In you case, it's the Import process that registers all the necessary Ports and Subscriptions so you cannot skip that step no matter what.

• Marked as answer by Lathaa 15 hours 55 minutes ago

Hi Lathaa,

It is always a good practice to deploy the packages instead of individual dll  . TO register proper biztalk artifacts its necessary to have MSI installed in proper way instead of manually adding assemblies to the resource folder of BizTalk admin console .

Hope this help you in future .

Thanks

Abhishek

• Marked as answer by Lathaa 15 hours 55 minutes ago

Hi Lathaa,

I also suggest to follow normal procedure ie.. MSI Import and Install To avoid some other issues.

It will work by adding DLL also, with the below option selected.

- with an option Add resource with Overwrite all property, 
- Add to the global assembly cache on add resource (gacutil)
- Restart Host instances

Thanks, SMSVikasK

• Marked as answer by Lathaa 15 hours 55 minutes ago

When Deploying BizTalk apps, you must always follow the correct procedure which includes Import and Install.

In you case, it's the Import process that registers all the necessary Ports and Subscriptions so you cannot skip that step no matter what.

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

When Deploying BizTalk apps, you must always follow the correct procedure which includes Import and Install.

In you case, it's the Import process that registers all the necessary Ports and Subscriptions so you cannot skip that step no matter what.

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

When Deploying BizTalk apps, you must always follow the correct procedure which includes Import and Install.

In you case, it's the Import process that registers all the necessary Ports and Subscriptions so you cannot skip that step no matter what.

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

Hi there,

just in case if my installation seems to be not working then in order to roll back changes what quick steps to perform? can anyone suggest the steps please?

Hi there,

just in case if my installation seems to be not working then in order to roll back changes what quick steps to perform? can anyone suggest the steps please?

Lathaa,

Before doing deployment on production please take backup of your application. You can simply Export your MSI and bindings. If in case your new deployment not work then you can roll back your code. In that case you can import your old MSI and bindings.

Please read below article before doing deployment,

https://msdn.microsoft.com/en-us/library/aa559168.aspx

https://msdn.microsoft.com/en-us/library/aa560565.aspx

https://msdn.microsoft.com/en-us/library/aa578011.aspx

Deploy BizTalk Applications using MSI files Concept and Best practices

Hi Lathaa,

It is always a good practice to deploy the packages instead of individual dll  . TO register proper biztalk artifacts its necessary to have MSI installed in proper way instead of manually adding assemblies to the resource folder of BizTalk admin console .

Hope this help you in future .

Thanks

Abhishek

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

Hi Lathaa,

It is always a good practice to deploy the packages instead of individual dll  . TO register proper biztalk artifacts its necessary to have MSI installed in proper way instead of manually adding assemblies to the resource folder of BizTalk admin console .

Hope this help you in future .

Thanks

Abhishek

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

Hi Lathaa,

It is always a good practice to deploy the packages instead of individual dll  . TO register proper biztalk artifacts its necessary to have MSI installed in proper way instead of manually adding assemblies to the resource folder of BizTalk admin console .

Hope this help you in future .

Thanks

Abhishek

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

Hi Lathaa,

I also suggest to follow normal procedure ie.. MSI Import and Install To avoid some other issues.

It will work by adding DLL also, with the below option selected.

- with an option Add resource with Overwrite all property, 
- Add to the global assembly cache on add resource (gacutil)
- Restart Host instances

Thanks, SMSVikasK

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

Hi Lathaa,

I also suggest to follow normal procedure ie.. MSI Import and Install To avoid some other issues.

It will work by adding DLL also, with the below option selected.

- with an option Add resource with Overwrite all property, 
- Add to the global assembly cache on add resource (gacutil)
- Restart Host instances

Thanks, SMSVikasK

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

Hi Lathaa,

I also suggest to follow normal procedure ie.. MSI Import and Install To avoid some other issues.

It will work by adding DLL also, with the below option selected.

- with an option Add resource with Overwrite all property, 
- Add to the global assembly cache on add resource (gacutil)
- Restart Host instances

Thanks, SMSVikasK

• Marked as answer by Lathaa Wednesday, August 26, 2015 3:08 PM

Hi Lathaa,

Adding some more points.

- if you are doing Re-Deployment

  - Better option is to take all the dlls from the assembly also (wrt MSI Artifacts that you are going to update to the existing ones).

Note Example: have faced issue while exporting the MSI from prod, ie sometimes people will do only gac to update simple changes, exporting MSI will not be helpful in this kind of scenario (assembly's in assembly will be the latest code).

If you do normal MSI Import and install deployment, then the BizTalk DB will be having latest assembly stored in DB, Exporting MSI will be Ok.

Thanks, SMSVikasK

Hi Lathaa,

Adding some more points.

- if you are doing Re-Deployment

  - Better option is to take all the dlls from the assembly also (wrt MSI Artifacts that you are going to update to the existing ones).

Note Example: have faced issue while exporting the MSI from prod, ie sometimes people will do only gac to update simple changes, exporting MSI will not be helpful in this kind of scenario (assembly's in assembly will be the latest code).

If you do normal MSI Import and install deployment, then the BizTalk DB will be having latest assembly stored in DB, Exporting MSI will be Ok.

Thanks, SMSVikasK

• Marked as answer by Lathaa 20 hours 12 minutes ago

Hi Lathaa,

Adding some more points.

- if you are doing Re-Deployment

  - Better option is to take all the dlls from the assembly also (wrt MSI Artifacts that you are going to update to the existing ones).

Note Example: have faced issue while exporting the MSI from prod, ie sometimes people will do only gac to update simple changes, exporting MSI will not be helpful in this kind of scenario (assembly's in assembly will be the latest code).

If you do normal MSI Import and install deployment, then the BizTalk DB will be having latest assembly stored in DB, Exporting MSI will be Ok.

Thanks, SMSVikasK

• Marked as answer by Lathaa Thursday, August 27, 2015 10:51 AM

Hi Lathaa,

Adding some more points.

- if you are doing Re-Deployment

  - Better option is to take all the dlls from the assembly also (wrt MSI Artifacts that you are going to update to the existing ones).

Note Example: have faced issue while exporting the MSI from prod, ie sometimes people will do only gac to update simple changes, exporting MSI will not be helpful in this kind of scenario (assembly's in assembly will be the latest code).

If you do normal MSI Import and install deployment, then the BizTalk DB will be having latest assembly stored in DB, Exporting MSI will be Ok.

Thanks, SMSVikasK

• Marked as answer by Lathaa Thursday, August 27, 2015 10:51 AM

Hi Lathaa,

Adding some more points.

- if you are doing Re-Deployment

  - Better option is to take all the dlls from the assembly also (wrt MSI Artifacts that you are going to update to the existing ones).

Note Example: have faced issue while exporting the MSI from prod, ie sometimes people will do only gac to update simple changes, exporting MSI will not be helpful in this kind of scenario (assembly's in assembly will be the latest code).

If you do normal MSI Import and install deployment, then the BizTalk DB will be having latest assembly stored in DB, Exporting MSI will be Ok.

Thanks, SMSVikasK

• Marked as answer by Lathaa Thursday, August 27, 2015 10:51 AM

Hi All,

thanks for the suggestions and help. I could successfully deploy the application on production server with initial concerns but managed to get rid off :)

Hoping application works as expected :) thanks