Important information I gathered from Logic Apps on the documentation found at https://azure.microsoft.com/en-us/services/logic-apps/ and will be adding a Logic App walk-through.
What are Logic Apps?
- Part of iPaaS (integration Platform as a Service), which allow them to scale automatically on demand
- Help simplify scalable integrations and workflow in the cloud, like BizTalk server does for on premise solutions.
- Use visual workflows and connectors to create integrations
- Can be used with custom APIs, code, and actions
- Provides Managed Connectors for fast and consistent integration.
Connectors supported – https://azure.microsoft.com/en-us/documentation/articles/apis-list/
Logic App Uses
- Provide a variety of triggers and actions with management tools to help centralize your API development.
- Workflows – graphical way to model your business processes as a series of steps or a workflow.
- Managed Connectors – Managed connectors are created specifically to aid you when you are connecting to and working with your data.
- Triggers – Some Managed Connectors can also act as a trigger. A trigger starts a new instance of a workflow based on a specific event, like the arrival of an e-mail or a change in your Azure Storage account.
- Actions – Each step after the trigger in a workflow is called an action. Each action typically maps to an operation on your managed connector or custom API apps.
- Enterprise Integration Pack – For more advanced integration scenarios, Logic Apps includes capabilities from BizTalk. BizTalk is Microsoft’s industry leading integration platform. The Enterprise Integration Pack connectors allow you to easily include validation, transformation, and more in to your Logic App workflows.
- Single Http request and/or Connector call limits
- Request Timeout is 1 minute
- Message size is limit is 50mb, with request trigger support for up to 25MB
- Expression evaluation is limited to 131,072 character meaning @cancat(), @base64(), string cannot be longer
- Retry policy is max delay is 1 hour with a min of 20 minutes with a max of 4 retry attempts
- Run duration and retention is limited to a run duration of 90 day with a storage retention of 90 days with min recurrence intervals of 15 sec and max recurrence interval of 500 days.
- Looping and debatching limits for ForEach items, SplitOn item, Until iterations to 10,000 and ForEach Parallelism to 20.
- Throughput limits for a single app instance are 100 triggers per second.
- Definition limits Actions in ForEach to 1 with Action per workflow to 60 and action nesting depth to 5. Triggers per workflow are limited to 10 with a max character per expression to 8192. Action/Trigger names are limited to 80 characters with a description length to 256. Parameters are limited to 50 and outputs are limited to 10.
Three different trigger statuses:
- Skipped. It polled the endpoint to check for data and received a response that no data was available.
- Succeeded. The trigger received a response that data was available. This could be from a manual trigger, a recurrence trigger, or a polling trigger. This likely will be accompanied with a status of Fired.
- Failed. An error was generated.
A run displays one of the following statuses:
- Succeeded. All actions succeeded, or, if there was a failure, it was handled by an action that occurred later in the workflow. That is, it was handled by an action that was set to run after a failed action.
- Failed. At least one action had a failure that was not handled by an action later in the workflow.
- Cancelled. The workflow was running but received a cancel request.
- Running. The workflow is currently running.
Unfortunately you are not able to run both side by side; so I would suggest you run 2009 in a VM and test your 2010 project in that if you need downward compatibility.
Remember, BizTalk 2010 is the only version of BizTalk compatible with R2 version of the Microsoft Server 2008 and SQL 2008. Setup is still roughly the same.
I have not been able to find a post or get a true explanation on “reserved words” in BizTalk; however there are a few you should stay away from. I have personally tested these.
You should refrain from using “BTS” or “EDI” anywhere in your namespace to avoid namespace property look-up issues.
I will be posting more about this as I work through the public version of BizTalk 2010 on Oct. 1, 2010.
Public production date announced was Oct. 1, 2010.
Free Developer Version Available
BizTalk 2009 is a message broker SOA tool. It is used to connect disparate systems and provided an entry point for connecting to your customers. BizTalk does come at a cost; however with the “built-in” functionality it can cut development costs.
- Retry Capabilities
- Transaction Traceability
- BAM (Business Activity Monitoring
- Reliable (durable) messages
- LOB (Line of Business) Adapters to fit most integration points (Siebel, Oracle, HiPPA)
What’s New in BizTalk 2009 (Captured from http://www.microsoft.com/biztalk/en/us/whats-new.aspx)
BizTalk Server 2009 introduces enhancements and new features in four main areas:
- Support for the latest platforms from Microsoft including server, database and development environment.
- Enhanced developer productivity and new application life cycle management experience for development teams.
- New capabilities for implementing agile SOA integration solutions across heterogeneous technologies and Line of Business systems.
- Enhanced B2B and RFID capabilities to allow the implementation of flexible end-to-end supply chain management and asset tracking solutions.
Top New Features
BizTalk Server 2009 introduces enhancements and new features in four main areas:
Updated Platform Support
- Support for Visual Studio 2008 SP1
- Support for .NET Framework 3.5 SP1
- Support for Windows Server 2008
- Virtualization support with Hyper-V
- Support for SQL Server 2008
Developer & Team Productivity
- New Application Lifecycle Management (ALM) experience – with Support for TFS – integrated source control, bug tracking, unit testing, MSBuild automation
- Enhanced Developer Productivity with Visual Studio project system updates & Map Debugging
SOA and Web Services
- ESB Toolkit 2.0
- New UDDI v3 Web Services Registry
- New and enhanced LOB adapters (Oracle eBusiness Suite, SQL Server)
- Enhanced host systems integration (WebSphere MQ, CICS, IMS)
- Enhanced BAM support
Business to Business Integration
- New Mobile RFID Platform
- New RFID device management and industry standards support
- Enhanced Support for EDI and AS2 Protocols and Drummond certification
- Updated SWIFT Support and SWIFTReady Financial EAI Gold certification
Enough on the sales pitch, my next post will dive into the factoids and creating your first BizTalk application.
At Tampa Code Camp 2009 I did 3 sessions, one on Linq 4.0, one on WCF 4.0, and an impromptu discussion on TDD. Here are the presentations on Linq 4.0 and WCF 4.0.
In one of my current projects I used Datagrid’s with RowDetail forms for editing the ItemSource collection. This created a unique issue with exception throwing from the entities so the form will provide immediate response to the user. This became very difficult to accomplish with the fact that the entities were provided by WCF (the Domain Service – we are not using RIA). Now the issue is that the WCF ONLY provides the implementation of the entity and not the entity itself, so in short terms no exception is thrown to the UI; however we would receive the general service fault exception from the service.
To overcome this I used the shared entity model and included them in both the Silverlight frontend and WCF backend. Now this is great solution; however if the user does not enter the form field well no instant feedback.
So for this opportunity, I created a .Validate method on the object and had it produce an error collection as well as return a true/false.
This option now allowed me to validate the object in ItemSource collection, so now the application can bulk save and evaluate the collection of data rather than one field at a time.
I will post an example of this process in the near future as well as how to do it.