Tuesday 14 May 2013

Scenarios Where Artifacts Are Added in BizTalk Application


The feature of BizTalk application of these solutions is really helpful with of installation and deployment of BizTalk Server business solutions. In addition, it also helps in dealing with these solutions as well as troubleshooting the problems related with it by monitoring the BizTalk Server performance. This application is a methodical combination of several items, which are commonly referred to as the called "artifacts," used in the solution.
Let us know some more about the artifacts and what do they comprise of. Artifacts constitute BizTalk specific resources such as pipelines, orchestrations, maps and schemas and BizTalk assemblies. They also include .NET assemblies that do not incorporate BizTalk-specific resources. In addition, policies, send ports and send port groups as well as receive ports and receive locations are also part of the artifacts. Other things that are put to use for this solution are COM components, certificates and scripts.
When you get the latest versions of this server configured after getting them installed, you will find that a default application that will be named as BizTalk Application 1 is formed automatically. There are a number of settings, where the artifacts are automatically created in the default server application. You can ask for the addition of artifacts, when you employ the BTSTask without detailing the application name. Even if you are using the BTSTask for importing .msi file application, artifacts are added. Similar is the case when you decide to set up an assembly from Visual Studio into the business server solution without providing the application name. The requirements of your BizTalk Development for performance, security, operation and availability vary according the size of your business and its requirements. 

No comments:

Post a Comment