Skip to Content
author's profile photo
Former Member

R/3 connection using JCA For Ep 6.0 SP2 !!

Posted on Jul 20, 2004 at 07:20 PM 11 Views

I am able to connect to R3 system from the Ep 6.0 Sp2 portal using IConnectorService (JCA).

I am trying to find a solution where I can generate java proxy for BAPI's so that I can eliminate data mapping between R3 and Java in EP 6.0 SP2 environment.

In EP 6.0 Sp4, the Netweaver Developer Studio provides a "SAP Enterprise Connector" wizard which generates proxy classes for java but uses JCO to connect to R/3 system. It is very usefull since the mapping of data types can be done in one place for all BAPI's which needs to be called from the portal and also I do not need to constatly look at the SAP GUI for BAPI definitions and return types. I can look at the java proxies to know exactly what I need to pass to invoke a BAPI and what I am getting back. I really like these connector wizard.

Is there a way to generate proxies using some tool for EP 6.0 sp2 using JCA as the mechanism since it is recommended to use JCA from EP 6.0 onward instead of JCO for better performance and management of R/3 connection ??

I appreciate your help !!

PORTAL Administration and Development
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • author's profile photo
    Former Member
    Posted on Jul 20, 2004 at 08:41 PM

    No. At least not with tools that SAP provides.

    Vendors may provide other tools to integrate with JCA compliant resource adapters.

    Things get much better with WebAS 6.30+ using WebDynpro for your UI and Data binding.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Jul 20, 2004 at 09:15 PM

    Thanks Will.

    I have two choices to connect to R/3 system from EP 6.0 Sp2 ...

    1) JCA : If I use JCA, I may have to write the layer of

    mapping the data and calling the BAPI's from R/3

    system to java.

    2) JCO : I can use the "SAP Enterprise Connector" wizard.

    The only thing I have to make sure is R/3

    connection management using IJCOClientService

    and JCOClientPoolEntry.

    I am also aware that the iView's I am writing will be used by lot of users since we are migrating an existing applications functionality to SAP Portal.

    So my question is, Which way should I implement the connection to R/3 so that I can achieve better performance and scalability ??

    Thanks again for your help !!

    Add comment
    10|10000 characters needed characters exceeded