JCA (Java Connector Architecture)

Hi All,
I would like to know if the introduction of JCA is Sun's attempt at derailing Web Services movement?
Please help me understand the big picture.
Thanks

Hi All,
I would like to know if the introduction of JCA is
Sun's attempt at derailing Web Services movement?
Please help me understand the big picture.
ThanksNope, its nothing to do with web services. JCA is so that you can integrate an enterprise's heterogeneous systems, including legacy systems, under J2EE - eg. have a J2EE application that calls SAP, CICs, databases etc using the same apis.
You could use web services for this, but it would be horribly inefficient having to convert everything to xml, parse it etc when all these systems are in your own company and under your control and there are java apis to connect to them. JCA is more likely to replace Corba calls to legacy systems and proprietry connections.

Similar Messages

  • Programming restrictions for JCA (Java Connector Architecture)

    I need to know programming restrictions for JCA (Java Connector Architecture) from a Client program's perspective. Could somebody help my?

    If you are on the client side of JCA you just have to use the resource adapter implementation. Therefore client code is limited to the package javax.resource.cci. So I think there are no restriction from JCA itself.
    What technique you use on client side to connect to the resource adapter is up to you and "just" have to follow the restriction in that area.

  • Java Connector Architecture?

    Does anyone know how the Java Connector Architecture (JCA) fits into the Web Services picture?
    Thanks,
    Justin McReynolds

    This is a pretty good article comparing/contrasting the two:
    http://www-106.ibm.com/developerworks/webservices/library/ws-jcajms.html

  • Java Connector Architecture (JCA)

    Hello there,
    Can any one help me with JCA. I have to present a seminar on this topic & am hunting for the material. If anybody has any material or links in this regard please let me know...
    Cheers,

    Hi All,
    I would like to know if the introduction of JCA is
    Sun's attempt at derailing Web Services movement?
    Please help me understand the big picture.
    ThanksNope, its nothing to do with web services. JCA is so that you can integrate an enterprise's heterogeneous systems, including legacy systems, under J2EE - eg. have a J2EE application that calls SAP, CICs, databases etc using the same apis.
    You could use web services for this, but it would be horribly inefficient having to convert everything to xml, parse it etc when all these systems are in your own company and under your control and there are java apis to connect to them. JCA is more likely to replace Corba calls to legacy systems and proprietry connections.

  • Name of Adapter JCA(J2EE CONNECTOR ARCHITECTURE)  for SAPNetWeaver

    hi
        i'm faceing problem with JCA adapters . i want to connect sap netweaver(km) from my java code for this i need one jca adapter which supports sap netweaver...... pls tell me which adapter supports this.... thanks in advance...

    Hi Rupesh,
    If you want to access your KM resources from your Java code then you can use the KM API.
    Here are some Blogs that you can refer to:
    Creating folders in KM dynamically
    Uploading files to KM repository using Webdynpro APIs
    Some Code Samples and Tutorials
    Knowledge Management Code Samples
    and the most important, KM API reference
    https://media.sdn.sap.com/javadocs/NW04/SPS15/km/index.html - 2004
    & https://media.sdn.sap.com/javadocs/NW04s/SPS7/km/index.html - 2004s

  • Standalone java connector architecture container

    Hi,
    please do you know about some standalone container (or framework) for JCA and it's connectors? My problem is that I'm facing here several integration problems and would like to use JCA but cannot utilize full JEE application server. I have here server application whose one of the modules is be responsible for interaction with EIS.
    Thanks for any ideas.
    Y

    This is a pretty good article comparing/contrasting the two:
    http://www-106.ibm.com/developerworks/webservices/library/ws-jcajms.html

  • Does iPlanet App Server 6.5 provide support for Java Connector Architecture resource adapters? If not will 7.0?

     

    6.5 does not support JCA. 7.0 is announced on 19th June
    when the official statement regarding support for JCA
    will be made.

  • Suitability of Java EE Connector Architecture

    Hi
    I'm designing the architecture for an enterprise system which will be essentially "information and control" in nature, in that it will be required to interact with a large number of external systems that will provide/accept information and/or accept control requests. For example, my system will be connected via TCP to a number of devices that are constantly feeding in realtime information, and will also be connected via UDP to a number of devices that can be controlled. For each interface, the message transfer/content protocol will generally be a proprietary format. There will be any number of such external systems using any number of different message protocols.
    My system will use Java EE technology. My understanding of the Java EE Connector Architecture (JCA) is that it is intended to support integration between Java EE app servers and EISs. What I'm wondering is whether in my environment, I could/should consider my "external systems" to be EISs. Looking at the JCA spec and elsewhere, a typical EIS is an ERP or a mainframe transaction processing system or a legacy database - whereas my external systems are just "things" with which my system will exchange messages. Are the two things the same? Is it practical to go for a JCA solution on the assumption that:
    - I'll have to write all of my own resource adaptors, one for each type of interface;
    - I can dispense with a lot of the 'fancy' JCA features such as transactions and security (if I can see no need for them).
    Any suggestions or guidance gratefully received.

    Yes, your architecture is well suited to the java connector approach. It doesn't really
    matter whether your backend external system is categorized as an "EIS". The fact
    that it communicates via a proprietary format means you don't want to have to
    write application code in a Java EE component that directly processes it. The
    advantage of the inbound portion of the Java Connector architecture is that it
    lets you plug in a piece of system code specifically tailored to communicate with
    your backend system. Because it's a piece of system code, you have access to
    many lower-level plumbing services such as threads that would not be available
    to application code.
    Likewise, once you process the appropriate lower-level communication details,
    it's much more desirable to delegate to an application component in the
    form of a Message-Driven bean that can then perform the business logic
    needed in the enterprise tier.
    --ken                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Connector Architecture

    HI all,We developed an Java Application which contacts SAP R/3 using some IBM packages.Now i want to develop an application which uses Java Connector Architecture .
    Please tell me ,where can i get the Java Connector API to start my work.i searched in sun,but unable to find the API.please tell me,How can I enhance my Application with Java Connector Architecture.
    thanks in advance.
    regards
    Nagesh

    barindesai
    I'm also gathering info in this topic. We develop an Java Application that connect to SAP. We beginning our tests with JCA and are happy about each help. If you could send us the ZIP-File with connection-example to r/3, we would thank you. here is our mail: [email protected]
    regards
    vladimir

  • Is this possible: SAP Java Connector - XI - R3 with XI RFC Adapter?

    Hi,
    I try to call a RFC on a remote R/3 System over the XI Server in a Java Application with SAP Java Connector.
    I have configured a RFC Sender Adapter in XI. I get the
    following Exception:
    "lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'SenderChannel_RFC"!
    Is this scenario possible? Or do the connection from
    a SAP Java Connector App to the XI RFC Adapter not work?
    You can't set the Client and System ID of a Third-Party or
    Standalone Java system in the SLD.
    Thanks for any help!
    Regards
    Wolfgang

    Hi,
    We use a JCO for directly connecting to sap systems.
    In that case we need not use any XI also.
    But if you want to use RFC adapter and java application the best way is to use java proxies as sender and reciever as RFC adapter.
    I donot think there is any  architectural significance in using rfc adapter of XI while using JCO.
    Let me know if I mis-understood the context.

  • Java connector calls against sap system with logon groups

    hi there.
    i want to use java connector to connect to a sap system and run a function. my problem: the sap system has more than one instance and i do not want to connect against the central instance. i want to use a logon group. does anyone have an idea how to handle this?
    thanks,
    martin

    hi,
    check this
    http://help.sap.com/saphelp_nw04/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
    http://nwadave.com/NwadExplorer/data/SAPDoc/architecture/SAP-Client_LogonAndCommunication.doc
    let me know  u need any further info
    bvr

  • J2EE Connector Architecture(Omni Portlet)

    Hello,
    In the Developer Guide ,(http://download-west.oracle.com/docs/cd/B14099_10/portal.1012/b14134/pdg_matrix.htm#CEGFBJEC)
    it is mentioned about J2EE Connector Architecture as a data source. In the omni portlet data source type it is not listed. How can I configure and use it for data source?
    I am using 9.0.4 version of Portal
    Any help is highly appreciable.
    Thanks

    We are trying to do a JCA Adapter and are running into the same type of questions as you. Clearly, no one is watching this topic. Have you found a reference application to test the RA against?
    Please feel free to contact me at [email protected]

  • WebDynpro with MDM Java Connector

    Hi,
    I'm trying to setup the JCA in MDM5.5 SP4 patch 3 in a Java Stack Engine 6.40.
    I'll be trying to access it from a standalone Webdynpro application.
    In the documentation I got it talks about setting a file:
    application-j2ee-engine.xml
    which only exist in J2EE apps, and not WebDynpro apps.
    Any ideas?
    Cheers,
    Michael

    If you are using the MDM Java Connector from Web Dynpro application, you have to set the properites accordingly.
    Go to <b>properties of Project</b> and there choose "<b>Webdynpro reference</b>". Here, choose <b>library reference</b> and there give your library reference.

  • Implementing a java connector

    Has anyone tried implementing a JCA Resource Manager the would integrate into a J2EE server for communication with a remote server?
    I'm thinking about implementing one for connectivity with an Http server....
    Has anyone tried something of this sort?

    mkx wrote:
    Hi,
    we are currently implementing a Java connector for the X11 windowing system and we're running into trouble with event handling.
    What we are doing is to fork a thread from the main application that will then invoke a native event handling loop that will listen for X11 events. Whenever such an event occurs, it will call back to a Java object to report that event.
    While receiving and reporting events works fine, any successive calls from the main thread to the native windowing functions will block the program.
    Let me outline the call order again:
    1. Java application is started, main thread created
    2. New Java thread is started that invokes a native method that itself runs in a while loop
    3. Normal program flow continues in the main Java thread
    4. Main Java thread now calls some native method, and locks up
    Any idea why this is happening? Is it not possible to invoke the same native code within two distinct Java threads? I have looked into the JNI functions AttachCurrentThread and DetachCurrentThread, but they only seem to handle the problem that two native threads share the same JVM, but that's not what we need. We have two Java threads that need to share the same native code.Are you sure its not a problem with the something in the X11 code being non-reentrant?
    http://www.gnu.org/software/libc/manual/html_node/Nonreentrancy.html#Nonreentrancy
    Jim S.

  • Error while deploying MDM Java Connector for EP

    Hi,
    i am a newbie to MDM.i am trying to develop a portal component with the blog "Using MDM5.5 Java Connector with SAP Enterprise Portal 6.0" as reference.
    i created an MDM system in portal and the connection tests passed.
    But when i deploy the code i get the following exception-
    java.lang.NullPointerException
         at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:170)
         at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:304)
         at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:258)
         at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:478)
         at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:85)
         at com.cts.mdm.MDMtestcomp.doContent(MDMtestcomp.java:36)(this points to the line <b>connection = cgService.getConnection("MDM_SYSTEM_ALIAS", prop);</b>)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    This is my code-
    IConnectorGatewayService cgService = (IConnectorGatewayService)
                   PortalRuntime.getRuntimeResources().getService(IConnectorService.KEY);
              ConnectionProperties prop =
              new ConnectionProperties(request.getLocale(), request.getUser());
                   IConnection connection = null;
                   connection = cgService.getConnection("MDM_SYSTEM_ALIAS", prop);
         INative nativeInterface = connection.retrieveNative();
                        CatalogData catalog = new CatalogData();
                             catalog = (CatalogData)
                   nativeInterface.getNative(CatalogData.class.getName());
                        ResultSetDefinition rsd = new ResultSetDefinition("Customers");
              rsd.AddField("Name");
              Search search = new Search("Customers");
              A2iResultSet rs = null;
                             rs = catalog.GetResultSet(search,rsd,"Name",true,0);
    response.write(rs.GetFields().toString());
    Have i missed anything?
    Should i deploy any .jar file? (i've already deployed MDM4J.jar) and referenced it in portalapp!
    Thanks in advance
    SwarnaDeepika

    Hello Swarna:
    I believe than rather than deploying the MDM4J.jar, you should deploy this components:
    com.sap.mdm.tech.mdm4j.sda
    com.sap.mdm.tech.connector.sda
    BPMDMTECHN00_0.sca
    BPMDMAPPLI00_0.sca
    Once you deploy those, you should have no problems. Another solution would be to take your MDM4J.jar and wrap it into an SDA, then deploy, but that would be pretty much the same.
    Those components are included on your MDM CD. Please ensure you use the same Version/support package/hotfix all over your landscape.
    I hope that helps
    Alejandro

Maybe you are looking for