cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple client RFC

Former Member
0 Kudos

Hi,

I work in an environment that stores data in two different SAP clients (client 700 and client 715).

In order to be able to call the Function Modules with different destinations we have duplicate models (the first set is configured to have client 700 as its destination, the other to have client 715). The destination is then determined at runtime, based on the user's input.

Unfortunately, this design is very inefficient because we have both the number of models and the number of data type classes doubled (and duplicated, since the FM are the same between 700 and 715).

Is there a smarter way to handle this scenario (to prevent model duplication)?

Thank you,

Pietro.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I decided not to use the RFC based webdynpro model for many reasons. Your example is one of them.

Here is what we normally do:

We create RFC proxy classes using SAP Enterprise Connector.

We call these RFC proxy classes in Session Beans. Here we have full control about how we would like to connect to a target ABAP system. Switch destinations is no problem here for example.

In WebDynpro we then use the EJB model to access the SessionBeans.

So we completely decouple RFC from WebDynpro but still use a webDnypro model approach.

Later you can easily switch from RFC to WebService if needed without changing the WebDynpro code.

Also a change in the called RFC function module will not break your WebDynpro model as it is decoupled.

By use of Mockup Classes in the SessionBeans you can start develop the WebDynpro Frontend in parallel to the backend development on ABAP side. If you use an RFC model this is not possible.

Former Member
0 Kudos

Hi Frank,

thank you for your reply.

Could you point me to some documentation or examples about your strategy/design?

Thanks,

Pietro

Former Member
0 Kudos

Hi Pietro,

well this is not the "official" SAP strategy/design. So there is no SAP documentation arround this.

The documentation I have however is owned by the customer I worked for, so I cannot share it.

So my highlevel post was meant to show you an idea on how to setup your environment in a different and in my eyes more efiicient way.

However I think about writing a blog about it discussed in the community.

Former Member
0 Kudos

Hi Frank,

if you'll ever make a blog about this, let me know!

I've found the way to make a new SAP Enterprise Connector (in File > New > Other...) but it is marked as Deprecate. I'm using Netweaver 7.1. I know you can't spill out details, but is the SAP Enterprise Connector that I've found the one that you meant?

Thank you,

Pietro

Former Member
0 Kudos

Yes the SAP Enterprise Connector is the tool you could use to start.

It is deprecated in 7.1 because it uses JCo 2 but it still works and makes live easier at the beginning.

We are still using it in our projects.

It lets you connect to your SAP APBAP system and browse RFC Function Modules. It then creates Java RFC Proxies.

7.1 comes with both JCO 2 and 3. For JCO 3 there are no generator tools available (so far).

Once you have created your RFC proxy, you can call it in a Session Bean.

To connect to SAP you will need a destination like you allready have for your RFC models.

You then create a JCO client on that destination.

Here is where you could implement your switch of destinations to multiple clients.

In WebDynpro you can generate a model upon the Session Bean.

Everything else works as you allready know.

Give it a try.

Cheers

Frank

Stefan-EA
Contributor
0 Kudos

> However I think about writing a blog about it discussed in the community.

Frank, please share this info with the community. Thanks.

Answers (0)