ADMINISTRATION AND OPERATIONS in Visual C#.NET

Maker PDF-417 2d barcode in Visual C#.NET ADMINISTRATION AND OPERATIONS

Figure 10 19. Configuring tracking within the BizTalk Administration Console 4. In the Tracking Options dialog box, set the desired options for tracking. The settings are generic across one-way and two-way ports. Request Message Before Port Processing: Request messages exist in one-way and two-way ports. Checking this value will track the message prior to being processed by the port (processing includes any pipelines or maps that may be on the port).

Note A message is a request if the message is initiated by the port/orchestration. A message is a response if the

Request Message After Port Processing: Checking this value will track the message after it is processed by the port (processing includes any pipelines or maps that may be on the port). Response Message Before Port Processing: Response messages exist on two-way ports only. Checking this value will track the message prior to being processed by the port (processing includes any pipelines or maps that may be on the port). Response Message After Port Processing: Checking this value will track the message after being processed by the port (processing includes any pipelines or maps that may be on the port).

If desired, configure tracking for send ports. Right-click the send port, select Tracking, and choose options in the Tracking Options dialog box.

Configure tracking on the appropriate orchestrations. In the left pane of the BizTalk Administration Console, click the Orchestrations folder. In the right pane, right-click the orchestration, and select Tracking. In the Orchestration Tracking Options dialog box, you can configure tracking on events and on messages within the orchestration, as shown in Figure 10 20.

After you have configured tracking through the BizTalk Administration Console, access the tracked messages as follows: 1. 2. Drop a message on the appropriate receive location to instantiate the orchestration. Open the Group Hub page, and run a query that will return message instances.

Right click the message, and select Save to File to select a folder to save to, as shown in Figure 10 21.

Figure 10 21. Saving tracked messages Depending on the complexity of the orchestration, the number of send and receive ports, and the level of tracking configured, there may be a few or a large number of messages written out to the directory specified. A combination of system messages and XML messages will have been tracked.

There is a direct relation between the level of tracking configured for a given solution and the size of the underlying BizTalk databases. For solutions with high levels of tracking and a high volume of message transactions, databases can grow quickly. An intelligent approach to traditional SQL database management is required, especially as it pertains to table truncation and data backups.

10 6. Restarting the BizTalk Host Instance(s)

You have a number of new configurations in your BizTalk applications. You want to refresh everything and make sure all configurations are acknowledged by BizTalk Server.

Refreshing BizTalk Server is quite simple restarting the BizTalk Host instance(s) essentially refreshes all of the configurations and running instances in the MessageBox. To perform the restart, take the following steps: 1. 2. 3. Open BizTalk Administration Console. Expand the BizTalk Group, expand the Platform Settings folder, and click Host Instances. Right-click the Host Instance that you want to restart, and select Restart (shown in Figure 10 22).

Occasionally, especially during development, you will need to restart the BizTalk host instances. When deploying new configurations, new referenced .NET assemblies, and new shared maps and schemas, it is

important to restart the host to ensure all of the new artifacts are referenced properly (and that old references are forgotten). It is also helpful to stop the whole BizTalk host instance when you want to turn off all processing to ensure that nothing is received or sent, regardless of the status of the send and receive ports.