<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>danzrobok.com &#187; Design Decisions</title>
	<atom:link href="http://blog.danzrobok.com/category/soa/design-decisions/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.danzrobok.com</link>
	<description>Business Integration and SOA with an IBM WebSphere slant</description>
	<lastBuildDate>Thu, 24 Mar 2011 19:45:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>DataPower Architectural Design Patterns: Integrating and Securing Services Across Domains</title>
		<link>http://blog.danzrobok.com/2008/08/26/datapower-architectural-design-patterns-integrating-and-securing-services-across-domains/</link>
		<comments>http://blog.danzrobok.com/2008/08/26/datapower-architectural-design-patterns-integrating-and-securing-services-across-domains/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 13:00:00 +0000</pubDate>
		<dc:creator>syndication</dc:creator>
				<category><![CDATA[DataPower]]></category>
		<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[design pattern]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/08/26/datapower-architectural-design-patterns-integrating-and-securing-services-across-domains/</guid>
		<description><![CDATA[ <strong>Draft Redbook, last updated: Tue, 26 Aug 2008</strong><p>
- Introduction to DataPower Services<br />
- Integration Services<br />
- Security Services<p>
IBM® WebSphere® DataPower® SOA Appliances are purpose-built network devices that offer a wide variety of functionality such as the securing and management of SOA Applications, Enterprise Service Bus Integration, and high speed XSL execution.]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/08/26/datapower-architectural-design-patterns-integrating-and-securing-services-across-domains/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BPEL: Beware the use of nested loops in a short running process</title>
		<link>http://blog.danzrobok.com/2008/07/03/bpel-beware-the-use-of-nested-loops-in-a-short-running-process/</link>
		<comments>http://blog.danzrobok.com/2008/07/03/bpel-beware-the-use-of-nested-loops-in-a-short-running-process/#comments</comments>
		<pubDate>Thu, 03 Jul 2008 15:43:25 +0000</pubDate>
		<dc:creator>dan</dc:creator>
				<category><![CDATA[Business Integration Tips]]></category>
		<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[WebSphere Business Events]]></category>
		<category><![CDATA[WebSphere Integration Developer]]></category>
		<category><![CDATA[WebSphere Process Server]]></category>
		<category><![CDATA[BPEL]]></category>
		<category><![CDATA[Business Integration]]></category>
		<category><![CDATA[design decision]]></category>
		<category><![CDATA[tip]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/07/03/bpel-beware-the-use-of-nested-loops-in-a-short-running-process/</guid>
		<description><![CDATA[One of the restrictions when dealing with a short running process is that it must always run within a single transaction. The implication is that the process must complete within the default transaction timeout window. On an application server, this is 120s. We had an issue where our Process Server was creating a large number [...]]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/07/03/bpel-beware-the-use-of-nested-loops-in-a-short-running-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WebSphere Business Integration V6.1 Performance Tuning</title>
		<link>http://blog.danzrobok.com/2008/06/09/websphere-business-integration-v61-performance-tuning/</link>
		<comments>http://blog.danzrobok.com/2008/06/09/websphere-business-integration-v61-performance-tuning/#comments</comments>
		<pubDate>Mon, 09 Jun 2008 13:00:00 +0000</pubDate>
		<dc:creator>syndication</dc:creator>
				<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[DeveloperWorks]]></category>
		<category><![CDATA[WebSphere Enterprise Service Bus]]></category>
		<category><![CDATA[WebSphere Integration Developer]]></category>
		<category><![CDATA[WebSphere Process Server]]></category>
		<category><![CDATA[WebSphere Business Integration]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/06/09/websphere-business-integration-v61-performance-tuning/</guid>
		<description><![CDATA[ <strong>Draft Redpaper, last updated: Mon, 9 Jun 2008</strong><p>
- Learn valuable tips for tuning<br />
- Get the latest best practices<br />
- Try the example settings<p>
This IBM®  Redpaper was produced by the IBM WebSphere®  Process Server, WebSphere Enterprise Service Bus, WebSphere Adapters, and WebSphere Business Monitor performance teams in Austin Texas, Böblingen Germany, and Hursley England.]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/06/09/websphere-business-integration-v61-performance-tuning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WSDL Anti-Pattern: xsd:Any and xsd:AnyType To Encapsulate Future Changes</title>
		<link>http://blog.danzrobok.com/2008/04/24/wsdl-anti-pattern-xsdany-and-xsdanytype-to-encapsulate-future-changes/</link>
		<comments>http://blog.danzrobok.com/2008/04/24/wsdl-anti-pattern-xsdany-and-xsdanytype-to-encapsulate-future-changes/#comments</comments>
		<pubDate>Thu, 24 Apr 2008 16:54:44 +0000</pubDate>
		<dc:creator>dan</dc:creator>
				<category><![CDATA[Best Of DZ.com]]></category>
		<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[WebSphere Integration Developer]]></category>
		<category><![CDATA[WebSphere Process Server]]></category>
		<category><![CDATA[anti-pattern]]></category>
		<category><![CDATA[Service as a String]]></category>
		<category><![CDATA[WSDL]]></category>
		<category><![CDATA[xsd:any]]></category>
		<category><![CDATA[xsd:anyType]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/04/24/wsdl-anti-pattern-xsdany-and-xsdanytype-to-encapsulate-future-changes/</guid>
		<description><![CDATA[The cousin to yesterday&#8217;s WSDL Anti-Pattern: The &#8216;Single XML String&#8217; Service is the use of the XSD specification&#8217;s &#8216;any&#8217;. &#8216;Any&#8217; literally means &#8220;any well-formed XML contained in this section is valid&#8221;. &#8216;anyType&#8217; means &#8220;any valid XSD Type&#8221;. We can start to see the correlation between the Single XML String service and the use of these [...]]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/04/24/wsdl-anti-pattern-xsdany-and-xsdanytype-to-encapsulate-future-changes/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>WSDL Anti-Pattern: The &#8216;Single XML String&#8217; Service</title>
		<link>http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/</link>
		<comments>http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/#comments</comments>
		<pubDate>Wed, 23 Apr 2008 14:31:16 +0000</pubDate>
		<dc:creator>dan</dc:creator>
				<category><![CDATA[Best Of DZ.com]]></category>
		<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[WebSphere Integration Developer]]></category>
		<category><![CDATA[WebSphere Service Registry and Repository]]></category>
		<category><![CDATA[anti-pattern]]></category>
		<category><![CDATA[Service as a String]]></category>
		<category><![CDATA[WSDL]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/</guid>
		<description><![CDATA[WSDL is a very useful technology. It allows service providers and consumers to agree on namespaces, operation names, the data to be transmitted in a request and the data to expect in a response. All very good things to know, all in a platform neutral way. Now, WSDL tells us what all the elements and [...]]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/04/23/wsdl-anti-pattern-the-single-xml-string-service/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Tip: Agree To Concrete WSDL Definitions before Development Begins</title>
		<link>http://blog.danzrobok.com/2008/04/16/tip-agree-to-concrete-wsdl-definitions-before-development-begins/</link>
		<comments>http://blog.danzrobok.com/2008/04/16/tip-agree-to-concrete-wsdl-definitions-before-development-begins/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 17:17:24 +0000</pubDate>
		<dc:creator>dan</dc:creator>
				<category><![CDATA[Best Of DZ.com]]></category>
		<category><![CDATA[Business Integration Tips]]></category>
		<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[Antipattern]]></category>
		<category><![CDATA[Developer]]></category>
		<category><![CDATA[Service Oriented Architecture]]></category>
		<category><![CDATA[Web Services]]></category>
		<category><![CDATA[WSDL]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/04/16/tip-agree-to-concrete-wsdl-definitions-before-development-begins/</guid>
		<description><![CDATA[If you are a provider or a consumer about to enter development on a web service, you should have an understanding with your counterpart of the WSDL that defines the service. It should be very well &#8216;baked&#8217; and changes once development begins should be minimial. Major things like name spaces and object names should rarely [...]]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/04/16/tip-agree-to-concrete-wsdl-definitions-before-development-begins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Impact 2008: Impressions of Day 2</title>
		<link>http://blog.danzrobok.com/2008/04/09/impact-2008-impressions-of-day-2/</link>
		<comments>http://blog.danzrobok.com/2008/04/09/impact-2008-impressions-of-day-2/#comments</comments>
		<pubDate>Wed, 09 Apr 2008 15:06:13 +0000</pubDate>
		<dc:creator>dan</dc:creator>
				<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[Impact 2008]]></category>
		<category><![CDATA[Project Zero]]></category>
		<category><![CDATA[WebSphere Process Server]]></category>
		<category><![CDATA[B-52s]]></category>
		<category><![CDATA[Patterns]]></category>
		<category><![CDATA[TSP-2518]]></category>
		<category><![CDATA[WebSphere sMash]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/04/09/impact-2008-impressions-of-day-2/</guid>
		<description><![CDATA[Day two is in the bag, the B52&#8242;s are B-50-done. Perficient and MTS Allstream gave a session about SOA Patterns that I thought was today but was actually yesterday. Oops. Here&#8217;s the abstract if you have a time machine: TSP-2518 &#8211; Effectively selecting integration patterns Brent Legris, Perficient, Inc., Senior Technical Architect, Olivera Zatezalo, MTS [...]]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/04/09/impact-2008-impressions-of-day-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The VETO SOA Pattern</title>
		<link>http://blog.danzrobok.com/2008/04/01/the-veto-soa-pattern/</link>
		<comments>http://blog.danzrobok.com/2008/04/01/the-veto-soa-pattern/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 15:52:38 +0000</pubDate>
		<dc:creator>dan</dc:creator>
				<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[WebSphere Integration Developer]]></category>
		<category><![CDATA[WebSphere Process Server]]></category>
		<category><![CDATA[design decision]]></category>
		<category><![CDATA[Enterprise Service Bus]]></category>
		<category><![CDATA[SOA Pattern]]></category>
		<category><![CDATA[VETO Pattern]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/04/01/the-veto-soa-pattern/</guid>
		<description><![CDATA[I&#8217;ve never been much of a patterns guy. I kind of always have the ability to apply common sense to a system and turn up something that is straight forward and makes sense. Periodically I get asked about what set of patterns I used to decide how a system should behave. To answer this question [...]]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/04/01/the-veto-soa-pattern/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JDBC Adapter Export with events that comprise multiple rows</title>
		<link>http://blog.danzrobok.com/2008/02/28/jdbc-adapter-export-with-events-that-comprise-multiple-rows/</link>
		<comments>http://blog.danzrobok.com/2008/02/28/jdbc-adapter-export-with-events-that-comprise-multiple-rows/#comments</comments>
		<pubDate>Fri, 29 Feb 2008 03:08:33 +0000</pubDate>
		<dc:creator>dan</dc:creator>
				<category><![CDATA[Design Decisions]]></category>
		<category><![CDATA[WebSphere Process Server]]></category>
		<category><![CDATA[design pattern]]></category>
		<category><![CDATA[ingenious idea]]></category>
		<category><![CDATA[WebSphere Adapter for JDBC]]></category>

		<guid isPermaLink="false">http://blog.danzrobok.com/2008/02/28/jdbc-adapter-export-with-events-that-comprise-multiple-rows/</guid>
		<description><![CDATA[At my client, we had a unique situation occur when integrating a database and an export for the WebSphere Adapter for JDBC. In a &#8216;typical&#8217; scenario, a single row is written into a staging table, an SQL trigger writes this single row into the adapter&#8217;s event table, the adapter polls, converts the data into a [...]]]></description>
		<wfw:commentRss>http://blog.danzrobok.com/2008/02/28/jdbc-adapter-export-with-events-that-comprise-multiple-rows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

