There is a long process that a programmer who is in-charge
of developing and debugging a specific BizTalk solution, according to the needs
of the business organization, for deploying BizTalk assemblies from Visual
Studio into that solution, effecting the application, and organizing it for BizTalk
deployment to the test environment.
First step is to develop and create the BizTalk assemblies. This
is done by building this software solution in Visual Studio by making use of
the schemas, orchestrations, pipelines and maps. After having built the BizTalk
assemblies, the deployment properties are activated on every Visual Studio
project in the business solution. Besides setting the BizTalk training Server properties including Server, Database, Configuration,
Redeploy, Install to Global Assembly Cache and Restart Host Instances, The
Application Name is property can also be set. The non-BizTalk .NET assemblies
can be deployed by adding them to the software application.
Subsequently BizTalk assemblies are deployed to the BizTalk
Server operating on the local computer. This can be done using the menu option
that appears when a Video Studio solution is right-clicked and Deploy command
is selected. The artifacts, which is a name taken as a combination of assemblies
with their resources, are deployed into the Management database of the server
for the group, and you can analyze and handle them via the Server
Administration console or other means.
During the BizTalk development process, the assemblies may be deployed for the single
application for ease, but these can be factored into multiple applications if
needed. Then, .msi files are created for each application and are installed
locally. If there is need, BizTalk assemblies are redeployed. The binding files
are exported and added back to the installed applications. Lastly, these files
are handed off to the team engaged in testing.
No comments:
Post a Comment