<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: APO in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/apo/m-p/1601746#M270163</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vamsee,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general, APO client always connects to single R/3 client. &lt;/P&gt;&lt;P&gt;For examples, DEV APO &amp;lt;-&amp;gt; DEV R/3 or QA APO &amp;lt;-&amp;gt; QA R/3 or PROD APO &amp;lt;-&amp;gt; PROD R/3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can not think any scenario that has multi R/3 clients connecting to single APO client. Do you have one?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ferry Lianto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Sep 2006 02:56:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-09-27T02:56:10Z</dc:date>
    <item>
      <title>APO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/apo/m-p/1601745#M270162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   I have a general question. Does anyone know what the advantages and disadvantages of connecting multiple r/3 clients to a single APO client? Is this approach reliable?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(or) do we need to have seperate APO client for each R/3 client and get it connected?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure where i am supposed to post this question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any feedback is highly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 02:46:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/apo/m-p/1601745#M270162</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-27T02:46:48Z</dc:date>
    </item>
    <item>
      <title>Re: APO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/apo/m-p/1601746#M270163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vamsee,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In general, APO client always connects to single R/3 client. &lt;/P&gt;&lt;P&gt;For examples, DEV APO &amp;lt;-&amp;gt; DEV R/3 or QA APO &amp;lt;-&amp;gt; QA R/3 or PROD APO &amp;lt;-&amp;gt; PROD R/3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can not think any scenario that has multi R/3 clients connecting to single APO client. Do you have one?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ferry Lianto&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 02:56:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/apo/m-p/1601746#M270163</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-27T02:56:10Z</dc:date>
    </item>
    <item>
      <title>Re: APO</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/apo/m-p/1601747#M270164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ferry,&lt;/P&gt;&lt;P&gt;    We are planning to connect two R/3 clients to a single APO Client, but before doing that we want to know the adv and disadv of it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Sep 2006 03:10:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/apo/m-p/1601747#M270164</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-09-27T03:10:50Z</dc:date>
    </item>
  </channel>
</rss>

