Skip to Content
author's profile photo Former Member
0
Former Member

Business Objects, external services and application services in CAs

Posted on Apr 07, 2008 at 01:27 PM 21 Views

Hi All,

right now we are developing our first eSOA Composite Application with CE and I have some questions regarding Business Objects, the import of external services and the development of application services.

As I understood there are two ways to provide business functionality for composite applications:

a. Import backend functionality as an external service (e.g. BAPI, RFC) at the CAF, build the application service which can be used as a callable object for UIs or the GPs

b. Develop a local Business Object (in CAF) providing the business logic, create the application service which again can be used as a callable object. Furthermore the application service can be exposed as a Web Service (external service).

My questions:

1. When is it appropriate to to import external services in stead of developing local BOs?

2. Under what conditions is it advisable to (solely) develop local BOs?

3. What are the advantages / disadvantages regarding the reusability of the services (in option a and b)?

Note: We are developing on NetWeaver 2004s.

Please let me know, if you need more information to answer the questions!

Thanks for your advice in advance,

Regards,

Ivonne

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Christian Loos
    Christian Loos
    Posted on Apr 08, 2008 at 04:10 PM
    2

    Hi Ivonne,

    first of all, the CAF Business Objects (BOs) itself don't contain any business logic, they're basically just local database tables (with some CRUD services on top).

    Business logic is implemented in Application Services (AS).

    Now, regarding local BO's vs. external services, it depends on your use case. If the data is already available somewhere in your backend system it makes sense to use external services. For instance you wouldn't want to store business partners all over different composites. For data that is specific to your composite (in particular configuration, customizing etc.) and not likely to be reused by other applications you should use local BOs.

    Accessing local BO's is also much faster than calling external services.

    You can do reuse in both scenarios, since the CAF services can be exposed as web services.

    Regards,

    Christian

    Edited by: Christian Loos on Apr 8, 2008 6:11 PM

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.