This is part 2 of the logging features. If I want to log data mid itinerary, buy cialis I want to use the Orchestration Logging Step
I drag the Itinerary Service onto the Itinerary Design surface and choose Logging Orchestration Extender
Since I am not going to log anything after this I am not enabling the Continuation
I want the step to show up on the portal, decease so I choose to have Tracking Enabled, and I for at least development, I want to see what data is being passed through the bus at this step so I set Storage to True
I connect the other shapes, and part of the product is the ability to create the Activities:
I choose one of the following Exporters:
If I choose the XML Itinerary Exporter, it places a series of defaults, to be discussed further in a later post
However, what I am most interested in is the BAM Activity XML file. This is the name of the Itinerary saved in your Documents folder.
If I choose Database Itinerary Exporter I have a few additional settings.
- Activity Overwrite: should it remove the currently deployed activity and re-deploy
- BAM Primary Import Database: the default BAM Primary Import DB
If I export the Tracking File Exporter, I get the itinerary and all of the items for caching, but I also get the Activity for me to deploy to other environments