<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for iWUA - integration Working Under Architecture</title>
	<atom:link href="http://www.iwua.nl/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.iwua.nl</link>
	<description>the path to integration &#124; EAI, SOA, EDA, BPM&#039;</description>
	<lastBuildDate>Fri, 18 Mar 2011 10:48:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>Comment on SAP unveils new functionalities in SAP PI 7.3 by Roberto Viana</title>
		<link>http://www.iwua.nl/soa/sap-unveils-new-functionalities-in-sap-pi-7-3/#comment-92</link>
		<dc:creator>Roberto Viana</dc:creator>
		<pubDate>Fri, 18 Mar 2011 10:48:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.iwua.eu/?p=143#comment-92</guid>
		<description>The use of dual stack is generally speaking not a good practice. It means for instance, that you have to manage two different kind of application servers (ABAP en JAVA), you need both type of skills in your team, performance tuning and security is approached different for both platforms, twice databases to manage, etc, etc..

If in PI 7.3 SAP provides the choice to choose one of their two available stacks, then it will positive influence the adoption of SAP PI as full-blown ESB.</description>
		<content:encoded><![CDATA[<p>The use of dual stack is generally speaking not a good practice. It means for instance, that you have to manage two different kind of application servers (ABAP en JAVA), you need both type of skills in your team, performance tuning and security is approached different for both platforms, twice databases to manage, etc, etc..</p>
<p>If in PI 7.3 SAP provides the choice to choose one of their two available stacks, then it will positive influence the adoption of SAP PI as full-blown ESB.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SAP unveils new functionalities in SAP PI 7.3 by jvmz78</title>
		<link>http://www.iwua.nl/soa/sap-unveils-new-functionalities-in-sap-pi-7-3/#comment-63</link>
		<dc:creator>jvmz78</dc:creator>
		<pubDate>Mon, 28 Feb 2011 10:05:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.iwua.eu/?p=143#comment-63</guid>
		<description>Hi,

But what about performance using that temporary solution? Isn&#039;t better to use dual stack?

It appears that the only available method to take advantage of single stack performance improvements is migrate the ccBPM workflows.

Regards</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>But what about performance using that temporary solution? Isn&#8217;t better to use dual stack?</p>
<p>It appears that the only available method to take advantage of single stack performance improvements is migrate the ccBPM workflows.</p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SAP PI 7.11 &#8211; Paving the way to SOA &amp; Process-Driven IT &#8211; Part 2 of 2 by Andre Jansen</title>
		<link>http://www.iwua.nl/soa/sap-pi-711-paving-the-way-to-soa-process-driven-it-part-2-of-2/#comment-3</link>
		<dc:creator>Andre Jansen</dc:creator>
		<pubDate>Mon, 15 Mar 2010 22:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://iwua.eu/wp/?p=11#comment-3</guid>
		<description>Hi Roberto, 

I was triggered by your remark &quot;this new version of the product enforces the use of SOA&quot;. No doubt the new version provides a better basis for creating SOA based solutions, but the product is still based on this &#039;old&#039; XI point to point architecture. It is so easy just to continue creating old-fashioned point-to-point interfaces, or to migrate all your old interfaces from XI 3.0 or PI 7.0 to 7.1.  It&#039;s the mindset, the organisation, the architecture principles and all other things outside of SAP PI which enforce the use of SOA. SAP helps you in this direction, but it is not the tool which enforces SOA. 
(I&#039;m sorry for the late response, but better late than never).</description>
		<content:encoded><![CDATA[<p>Hi Roberto, </p>
<p>I was triggered by your remark &#8220;this new version of the product enforces the use of SOA&#8221;. No doubt the new version provides a better basis for creating SOA based solutions, but the product is still based on this &#8216;old&#8217; XI point to point architecture. It is so easy just to continue creating old-fashioned point-to-point interfaces, or to migrate all your old interfaces from XI 3.0 or PI 7.0 to 7.1.  It&#8217;s the mindset, the organisation, the architecture principles and all other things outside of SAP PI which enforce the use of SOA. SAP helps you in this direction, but it is not the tool which enforces SOA.<br />
(I&#8217;m sorry for the late response, but better late than never).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

