PURCHASE Homepage CONTACT US ASK THE EXPERT Homepage
Home
About bTalk
Who uses bTalk?
Case Studies
Product Tour
Screen Shots
Screencam
Features
Requirements
Technical Items
bTalk and Java
bTalk and ASP
bTalk and CFML
bTalk and XML
bTalk vs. EAI
Interactive Items
Ask the Expert
Download
Support

Computer Associates Smart Partner

Using bTalk for Java

The diagram above shows all components built using bTalk to facilitate a request and response into SAP using Java (JSP). bTalk generates the following:

  1. The Java Proxy Bean (handles the transaction between app server and SAP R/3 through the BAPI/RFC.
  2. The Java Server Pages (which acts as a handler and display templates)
  3. The HTML form (the HTML form for entering input parameters)

Frequently Asked Questions

What do you mean bTalk is J2EE compliant?
bTalk generates Java Proxy Beans and Java Server Pages that can run on any J2EE compliant application servier. The code generated from bTalk is pure Java and open source. Nothing proprietary, no restrictions.

What does bTalk use to connect to SAP - JRFC or JCO?
bTalk now allows the developer to choose which interface to use into SAP. The JRFC has been around for over 2 years, and the JCO is the new interface recommended by SAP. bTalk is the first commercial product to support the new JCO interface.

Does bTalk allow for connection pooling?
Yes, now with JCO - bTalk allows for connection pooling.

How does bTalk support XML?
bTalk allows for the request and response to the Java bean to be in XML format. It operates like a 'web service', using XML to request the function, and then returns the data real-time back to the requestor as XML. Unlike EAI applications, bTalk is real-time.

Why would I buy bTalk when I can download the SAP JCO?
Understand, the SAP JCO is simply the interface to communicating to SAP. bTalk generates both the proxy beans and the interface (HTML and JSP). bTalk allows the developer to instantly generate all the code needed to build the application. bTalk saves time, and reduces risk. There is no reason to hand-code the beans and JSP pages, when you can generate them in seconds.

Where does bTalk sit at run-time?
bTalk-generated Java Code (proxy beans and JSP pages) are installed in the web application server. (see illustration above). Just like any Java Bean or JSP page, bTalk requires the application server. bTalk supports all leading J2EE compliant application servers on the market.

Does bTalk work with SAP Java application server - InQMy?
Yes. You are able to deploy bTalk-generated code on the InQMy application server.

If you have any other questions, please Ask the Expert.


bTalk Web Service Components
©1998-2008 Pipeline Software, Inc. All rights reserved.
Contact us | Legal Notice and Copyrights