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

SAP WAS ABAP+J2EE

We are trying to implement mobile solution. Can any body try to answer below question:

<b>Current Scenario:</b>

We have installed SAP Web AS 6.40 J2EE installed on a server. We have also installed SAP Portal on top of it.

We have SAP R/3 4.70 on a separate server which does not have WAS or ITS.

<b>Requirement:</b>

We want to install SAP Mobile Infrastructure 2.5 and create mobile application to synchonize data with R/3 system.

<b>Question:</b>

As per our knowledge to make R/3 application mobile (eg. Mobile Asset Management) we need WAS ABAP + J2EE on R/3. Can we install WAS ABAP + J2EE on a separate server and still connect to R/3 and implement mobile solution?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 03, 2005 at 11:51 AM

    Hi Bikram,

    Yes! you can install your WAS 6.40 in a seperate server, this will be your SAP MI Server and your SAP R/3 4.70 system will be your backend system.Also your backend system could be a non-sap system,this is not your requirement though.Your MI Server will talk to the 4.70 backend system via the RFC destination defined in your SyncBo of the MAM.

    Pl have a look at the MI Architecture - General Overview for better understanding.

    Hope this answers your question.

    Cheers

    Gisk

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 08, 2005 at 05:16 AM

    Bikram

    You can install WAS ABAP + J2EE on a separate server and still connect to R/3 and implement mobile solution

    This can be done my developing MI server(Synco BO's) and BAPI Wrappers in MI ABAP component and then inside your BAPI Wrapper you can call the BAPI of a remote R/3 system using RFC Destination.When you call a BAPI in ABAP you can give an extra parameter for R/3 to connect which is being specified by creating a RFC Destination that points to the remote R/3

    Hope this helps

    Regards

    Harsh Chauhan

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Bikram:

      Since you want to Install MI 2.5, After your installation when you create the SyncBo you define the RFC Destination and the BAPI Wrapper in the SyncBo for Smart Sync and in Generic Sync you will define the RFC Destination in the Table MEMAPPDEST. You donot have to call the BAPI with the RFC Destination if your BAPI Wrapper and the BAPI exists in the RFC Destination you have defined in the SyncBo.When you create the SyncBo this check is automatically made for the existence of the BAPI Wrapper in the Back End system defined with the RFC Destination.If the BAPI Wrapper doesnot exists in the RFC Destination specified, it throws an error upfront.Harsh is correct with versions prior to MI 2.5 where you have to call the BAPI with the RFC Destination inside your Wrapper.

      Gisk

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.