This article uses the latest version 5. To learn more about the installation of the btdf and step by step guide for configuring the BTDF, refer following link. The link discusses the steps taken for BizTalk and Visual Studio , but same can be followed for other versions of BizTalk. Following are various steps that are involved in setting up complete logging utility for a BizTalk application using log4net and BTDF. It can be included in the solution Items using the solution folder as shown in sample screen shot below.
Following is a sample configuration file that is shown in the above screenshot. The comments in the config file explain the important concepts. Following are the settings that need to be done. This can be done by adding following line in the PropertyGroup Defining the deployment conditions.
A typical Property Group defining the deployment conditions would look as follows. The BTDF installation process is a 32 bit process and when the btdf configures the log4net for the application, it creates the registry key in the Registry corresponding to the 32 bit process SYSWOW64 32 but if the host instances processing the orchestration are 64 bit, then a registry key need to be created which corresponds to the 64 bit host instances.
A custom post deployment target needs to be created for this task. It can be created as a sample shown below. The registry entries created by the BTDF in both the 32 bit and the 64 bit registry folders are shown below.
The best way to accomplish is using a PowerShell script. The PowerShell Script to create and register the event log and the app source is as follows.
This will create a custom event log and write the entries to it. For Example, the above script was used to create a custom event Log and to register the app source as per the provided config file as above. So when a call to write entry to the event log is made as shown below,. The entry will get written to the custom event log "BizCustomLog. Once this is done, all the entries viz. Information, Errors and Warnings pertaining to this source will get written to the custom log.
Once the Custom event log is created, source registered and the BizTalk app is deployed to the production environment, then it becomes the duty of the DevOps team to monitor the app behavior if it throws any errors or warnings as such.
These warnings Custom errors caught in the exception Handling or Warnings in functional validation failure should be sent to the DevOps team for an analysis. Again Powershell Script plays an important role in setting up this notification system.
You need to manually schrink or truncate them, see this post by Dave Pinal. Finally I also suggest to review this kb article How to maintain and troubleshoot BizTalk Server databases. Following code always shrinks the Truncated Log File to minimum size possible. The content you requested has been removed. Ask a question. Quick access. The following figure indicates the state of the solution before the user does a redeployment.
The relationships among the artifacts are as follows:. If the user redeploys the Maps project using the default Visual Studio project settings, the Orch1, Orch2, and Pipeline artifacts vanish, as shown in the following figure. Redeploying Maps is a two-step process of undeploying the currently deployed Maps. Visual Studio performs these steps automatically as part of the redeployment process. The preceding sentence is not strictly correct because these are steps that Visual Studio always does so there is no notion of it being the proper way.
The key point is that in order to undeploy a BizTalk Server assembly, Visual Studio has to undeploy all assemblies that are dependent upon that assembly that have the deploy flag set. In our example, to perform the first undeployment step of the redeployment, BizTalk Server needs to undeploy Orch1. During the undeployment of Maps. In order to undeploy Schemas. A problem exists in that Visual Studio redeploys only Maps.
Click Properties to open the Solution Property Pages dialog box. In Solution Explorer, execute a new solution-level deployment. To do this, right-click the solution node and then click Deploy Solution. These two types are the ones typically seen in the metabase hierarchy to describe folders.
0コメント