The BizTalk Service explorer offers the following features:
- Browsing artifacts in you BizTalk Service
- Explore tracked events within your bridge
- Upload and download artifacts
- Restarting the BizTalk service
- Test and debug bridges
You can now add a BizTalk Service(s) you have provisioned in Windows Azure. By simple right clicking the Windows Azure BizTalk Services you can select Add BizTalk Service … A dialog will appear where you have to fill in service name of your BizTalk Service, the namespace and issuer secret (obtained through Access Control Services).
After clicking OK you will see the specified BizTalk Service appear in the BizTalk Service Explorer.
Browsing artifactsThe BizTalk Service Explorer offers the ability to browse through the BizTalk Service. You can see the assemblies, bridges, certificates, schemas and transforms that have been deployed to your BizTalk Service.
By expanding the artifact nodes you can browse through them.
paragraph showed how to browse through the BizTalk Service artifacts. In case messages are send to a bridge than these will be tracked that is metadata like tracking id, track point and timestamps are always tracked. This also accounts for fault information of failed messages. The level of tracking can be specified in the bridge with Visual Studio. You can either track message processing events and/or all message properties.
By selecting a Bridge you can expand the tracking events to browse through tracked events.
In case you want to download an artifact then you have to select a certain artifact within Assemblies, Bridges, Certificates, Schemas or Transforms.
A dialog will appear. Here you can load a test message.
Subsequently you hit the Send button and the message will be send to the bridge endpoint:
The response will be appear in the right pane.
As you can also see the tracking id is presented. This id can be used to browse in tracked events and access the particular event.
To debug a bridge you select the bridge you want to debug. You right click the bridge and choose the option Debug. A dialog will appear.
You load a test message similar to send a test message to a bridge and click Send Message.
You can now step through the process by clicking Continue.
You can continue doing this examining each step until the end.
Like sending a test message you see an id i.e. request id that you can use to browse through the tracked events.
Debugging a bridge gives the developer the ability to have a clear view on what is happening inside the bridge. When a bridge is in debug mode all messages going through the bridge can be viewed. Therefore debugging bridges in production environment is not advisable (Sam Vanhoutte - Introduction Step by step debugging of bridges in Windows Azure BizTalk Services ).