EJB Modul: SAP Enterprise Connector, configuring build path

Hello,
first of all I'm using SAP NW CE.
I created an 2 Development Components, an EJB Module and a Enterprise Application(EAR). In the EJB Module I use the SAP Enterprise Connector to generate Java Proxy Classes to do RFC calls.
In the EAR-DC I add in Properties-->J2EE Module Dependencies the needed jar-files. And in the EJB-DC I reference this.
When I don't work with DCs and I create a "normal" EJB and EAR project that is the way it works.
But with DCs I have a problem when I want to build the DC. I have this error:
package com.sap.aii.proxy.framework.core does not exist
So the build-process don't realize the J2EE Module Dependencies. How can I solve this problem?
Regards,
Armin

Did you mean the Development Infrastructure Perspective? If yes I don't find DC -> DC Metadata -> DC Definitino -> Right-click Used DCs -> Add Used DC... if I browse through my DC.
Apart from that I don't want to reference DCs as I write above. I want to reference only jar-files. Because the DCs com.sap.aii.proxy.framework, com.sap.aii.util..misc and com.sap.mw.jco are deprecated. And if I reference DCs I have to use this DCs to use the proxy classes made by the SAP Enterprise Connector. So I want to reference the jar-files where the needed source isn't deprecated.
By the way I use SAP NW CE.

Similar Messages

  • Runtime error while using SAP Enterprise Connector in a J2EE Web Servlet

    Hello,
    I'm facing problems while trying to do a RFC call out of a Servlet.
    I'm using Development Components (DCs) and my project setup is as follows:
    Firstly I've created a DC of type J2EE/Web Module. This DC implements an absolutly simple servlet which has to do the RFC-Call.
    The relevant code is:
    protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
       JCO.Client jcoclient = JCO.createClient("010", "DV*****", "***", "DE", "ovd***", "01");
       jcoclient.connect();
       Bapi_Flight_Getlist_Input input = new Bapi_Flight_Getlist_Input();
       input.setAirline("LH");
       SAPProxies_PortType myproxy = new SAPProxies_PortType();
       myproxy.messageSpecifier.setJcoClient(jcoclient);
       try {
          Bapi_Flight_Getlist_Output output = myproxy.bapi_Flight_Getlist(input);
          BapisfldatType_List list = output.get_as_listFlight_List();
          int listsize = list.size();
          for (int i = 0; i < listsize; i++) {
             BapisfldatType elem = list.getBapisfldatType(i);
             response.getWriter().print("Date: " + elem.getArrdate() + '\t' + "Arrive: " + elem.getArrtime());
       } catch (Exception e) {
          response.getWriter().print(e.toString());
       jcoclient.disconnect();
    The proxy for the RFC Module "BAPI_FLIGHT_GETLIST" - in this case the classes around "SAPProxies_PortType" were generated by NWDS ("SAP Enterprise Connector" Wizard).
    I had to manually add following DCs as "Used DCs" to get my DC built:
    com.sap.aii.proxy.framework (default)
    com.sap.aii.util.misc (default)
    com.sap.mw.jco (default)
    So far, so good...
    As a J2EE/Web module DC can't be deployed I've created a second DC of type J2EE/Enterprise Application and referenced the first DC. This DC is also built fine and can be deployed.
    But... When I call my servlet I get following Error Message on the web browser:
    The request cannot be processed.
      Details:      
      com.sap.engine.services.servlets_jsp.server.exceptions.ServletNotFoundException: Cannot load the requested servlet [LocalDevelopmentservletxxx.com/servlet/TestServlet].
    Exception id: [000C295D60FB006F0000003600000EA8000461A05860B4BA]
    I also had a look in the trace files:
    Vollstu00E4ndiger Nachrichtentext
    application [LocalDevelopmentservletxxx.com] Processing HTTP request to servlet [TestServlet] finished with error. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.ServletNotFoundException: Cannot load the requested servlet [LocalDevelopmentservletxxx.com/servlet/TestServlet].
    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.getServlet(WebComponents.java:330)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:354)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoClassDefFoundError: com/sap/aii/proxy/framework/core/AbstractType
    Loader Info -
    ClassLoader name: [xxx.com/testear]
    Parent loader name: [Frame ClassLoader]
    References:
       common:service:http;service:servlet_jsp
       service:ejb
       common:service:iiop;service:naming;service:p4;service:ts
       service:jmsconnector
       library:jsse
       library:servlet
       common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
       library:ejb20
       library:j2eeca
       library:jms
       library:opensql
       common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
       interface:resourcecontext_api
       interface:webservices
       interface:cross
       interface:ejbserialization
    Resources:
       C:\usr\sap\J2E\JC00\j2ee\cluster\server0\apps\ibm.com\testear\servlet_jsp\LocalDevelopmentservletxxx.com\work
       C:\usr\sap\J2E\JC00\j2ee\cluster\server0\apps\ibm.com\testear\servlet_jsp\LocalDevelopmentservletxxx.com\root\WEB-INF\classes
       C:\usr\sap\J2E\JC00\j2ee\cluster\server0\apps\ibm.com\testear\src.zip
    Loading model: {parent,references,local}
    The error occurred while trying to load "com.xxx.test.sap.connector.Bapi_Flight_Getlist_Output".
    at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.getDeclaredConstructors0(Native Method)
    at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
    at java.lang.Class.getConstructor0(Class.java:1930)
    at java.lang.Class.newInstance0(Class.java:278)
    at java.lang.Class.newInstance(Class.java:261)
    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.getServlet(WebComponents.java:319)
    ... 14 more
    I think it has something to do with the used DCs... but I don't know why the classes are not found after deployment. I also tried
    to package the relevant jar-files from the used DCs into the EAR-File - but the I faced problems with the JCo
    Thank you for any help.
    Osman

    Hi,
    One thing that can be helpful is to add the references of the JAR files that you are adding as Used DC in the EAR.
    This can be done by adding Library type References in the application-j2ee-engine.xml Deployment descriptor in the EAR project.
    Following link will be helpful: http://help.sap.com/saphelp_nw70/helpdata/EN/83/82814282cfc153e10000000a1550b0/content.htm
    Regards,
    Alka.

  • ABAP Sneak Preview SP11 - NWDS:SAP Enterprise Connector error

    Hello
    I have installed the ABAP 6.4 Sneak Preview SP11 (It works fine with the SAP GUI). I am trying to call Bapis from Java with the help of the proxies generated by "SAP Enterprise Connector". But the problem is that the "SAP Connection Wizard" does not progress any further after providing the R/3 system details(like hostname, sys number, client) and username/pasword. When I click the "Next Button" after providing the correct connection parameters it just stays there.
    -->Would the license be a problem. I did not apply for the 90 day license yet, I wanted to do that once everything is working fine.
    --> Should I do any additional configuration on the R/3 side.
    --> Should I add any extra setting to the environment variable path.
    Your help will be greatly apprecaited!!!
    Thanks
    Yasu

    Hello some more information....
    I have installed the ABAP 6.4 Sneak Preview SP11 (It works fine with the SAP GUI). I am trying to call Bapis from Java with the help of the proxies generated by "SAP Enterprise Connector". But the problem is that the "SAP Connection Wizard" does not progress any further after providing the R/3 system details(like hostname, sys number, client) and username/pasword. When I click the "Next Button" after providing the correct connection parameters it just stays there.
    -->Would the license be a problem. I did not apply for the 90 day license yet, I wanted to do that once everything is working fine.
    --> Should I do any additional configuration on the R/3 side.
    --> Should I add any extra setting to the environment variable path.
    Your help will be greatly apprecaited!!!
    Thanks
    Yasu

  • SAP Enterprise Connector Error - NWDS

    Hello I have the following issue, I found the same problem in the eariler forums(no solution though) and pasting it here...
    the content is copied from /thread/9971 [original link is broken]
    Hi
    I've installed the sneak edition of the NDS which is a part of the WAS 6.40 sneak preview. Everything seams to work just fine except for the proxy generation in a portal application using the SAP Enterprise Connector tool.(choose new>other>SAP connectivity-->SAP Enterprise Connector) I get to the point where I have to enter connection information's for a single server like Host name, system nr, client, etc...However when everything i filled out and I push next nothing happens. The process line in the bottom shortly fills but the same screen is shown.
    Have anyone run into the same problem?
    Best Regards
    Ole Mose Nielsen
    the problem I have is exactly the same. But say if I change the system number to '04' than I get an error - "connect to sap gateway failed".
    Thanks,
    Yasu

    Hello some more information....
    I have installed the ABAP 6.4 Sneak Preview SP11 (It works fine with the SAP GUI). I am trying to call Bapis from Java with the help of the proxies generated by "SAP Enterprise Connector". But the problem is that the "SAP Connection Wizard" does not progress any further after providing the R/3 system details(like hostname, sys number, client) and username/pasword. When I click the "Next Button" after providing the correct connection parameters it just stays there.
    -->Would the license be a problem. I did not apply for the 90 day license yet, I wanted to do that once everything is working fine.
    --> Should I do any additional configuration on the R/3 side.
    --> Should I add any extra setting to the environment variable path.
    Your help will be greatly apprecaited!!!
    Thanks
    Yasu

  • SAP Enterprise Connector and JCo

    Hello All,
          I have a question.
    I wánt to know regarding -->
    SAP Connector  &
    JCo.
    Are both of them same ?
    Regards,
    Deepu.K

    hi,
    <b>They are different:</b>
    SAP Connector : A development tool, that helps classes and RFC function module method calls in Java application.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ed/897483ea5011d6b2e800508b6b8a93/frameset.htm
    JCO : They are often called as JCO RFC provider service. They offer two types of connection a)TCP/IP b)Through shared memory
    http://help.sap.com/saphelp_nw2004s/helpdata/en/83/85343e8c7f6329e10000000a114084/frameset.htm
    (soon my blog on SAP Enterprise connector will be published)
    hope it helps'
    regards

  • SAP Enterprise Connector

    Hi Experts
    I tried generating Proxy classes for first time for FlightAppList using SAP Enterprise connector by selecting Single Server option, I have installed SAP Management Console on the system having host name 'sap-server', the details i provided was as follows:
    HostName:'sap-server'
    System Number: 00
    SAP Router:
    User Account
    Client : 001
    LogonName: pradeep
    Password: password
    Language:ENG
    but i get the error as
    Connect to SAP failed
    Error: Partner not reached
    Do i need to do any settings on SAP Netweaver console.
    Kindly let me know.

    Configuring webasabap needs SAP security library which can be downloaded at sap market place, but it needs a license username password which i dont have.
    I have only downloaded the trial version "SAPNW2004sJavaSP9_Trial"  is there a way i can connect my java program to SAP database without having any license?

  • SAP Enterprise Connector and service....

    Hi everyone,
    After creating, via the plugin "SAP Enterprise Connector", a proxy pointing on a BAPI, how can I create a service for this (and a web service).
    I know that you can create a web service directly using ABAP transaction se37. But our SAP version is quite old and we haven't this option.
    Thanks for the help.
    Message was edited by: David Fryda

    HI Jerin,
    Can be please little bit elaborate ur scenario.Because Enterprise Connector is deprecated in NWCE 7.1 onwards...

  • Creating a WEB Service for SAP enterprise connector

    Hi,
    I am using the SAP enterprise connector plugin for Netweaver 04.
    It generated me all the classes that I need for the BAPI.
    It also generated me a Proxy class.
    I want to create a service.
    This is what I've done :
    1) create a portal service.
    2) create a methode in the service :
    public Bapi_Companycode_Getdetail_Output execute_BAPI_COMPANYCODE_GETDETAIL(
    Bapi_Companycode_Getdetail_Input arg1)
    try {
    return new MyProxy_PortType().bapi_Companycode_Getdetail (arg1);
    } catch (Exception e) {
    return null;
    3) after I created a web service from the portal service.
    Is it the right way ?
    Thanks a lot.

    Hi Marcin and everyone,
    Thanks for the precious explanations.
    I created a client and I have an exception.
    1) I made a portal service from wsdl - client side.
    2) I created a DynPage.
    3) Here is the code :
    IMyBAPI4Service client = (IMyBAPI4Service) PortalRuntime.getRuntimeResources().getService(
    IMyBAPI4Service.KEY);
    IMyBAPI4Service securedClient = (IMyBAPI4Service) client.getSecurisedServiceConnection(                 request.getUser());
    //this is null.
    if (securedClient.getURLEndPoint().getURL() == null) {      
    securedClient.setURLEndPoint(new URLEndpoint("http://<server>:<port>/irj/servlet/prt/soap/com.sap.portal.prt.soap.MyBAPI4Service?style=doc_lit"));
    Bapi_Companycode_Getdetail_Input importParams =     new Bapi_Companycode_Getdetail_Input();
    importParams.setCompanycodeid("0500");
    Bapi_Companycode_Getdetail_Output exportParams = null;
    securedClient.execute_BAPI_COMPANYCODE_GETDETAIL(importParams);                         
    Do I have to use a secured client ? What is it ?
    The exception is :
    Problem at execution: SOAP Fault Error (java.lang.NoClassDefFoundError) : java.lang.NoClassDefFoundError
    Thanks Marcin....
    Message was edited by: David Fryda

  • Need help with the SAP Enterprise connector wizard at the NWDS

    Hello,
    I am trying to create new proxy using the SAP Enterprise connector at the Netweaver Developer Studio.
    The problem is that at the 2nd stage I am unable to connect to the server. Can someone please explain me in details:
    1. Which tab should I chose there: Load balancing server or single server?
    2. Which parameters should I enter there and from where can I take them (uch as System number...)
    I tried to enter my server's parameters but I couldn't connect.

    Hi Roy,
         It depends on what type of R/3 server you are connecting. Usually development & Quality assurance systems for R/3 are not load balanced. You can find it out from your Basis people that server you are connecting is load balanced.
    If it is not load balanced  then the select the single server and enter the following parameters.
    1. Host Name: Server Name (or ip address)
    2. System Number: (00)
    If it is load balanced then fill out all the information on load balancing tab.
    You only need to fill one of the tabs. thank you.

  • SAP Enterprise Connector: omitting parameters like ParameterList.setActive

    Hello,
    I use the SAP Enterprise Connector and i've got a question:
    how can i avoid that the unnecessary optional parameters are requestet during the call, as i could do it with pure JCO.ParameterList.setActive(false).
    Thanks,
    Gena

    Hello,
    I use the SAP Enterprise Connector and i've got a question:
    how can i avoid that the unnecessary optional parameters are requestet during the call, as i could do it with pure JCO.ParameterList.setActive(false).
    Thanks,
    Gena

  • Adapter module:: JAR file in the build path of EJB project

    Hi Experts,
    I have created one adapter module, for this I have created one EJB project and also associated one EAR project to that.
    I have completed my coding and changes in the xml files.
    I have followed this -
    http://www.sdn.sap.com/irj/scn/index;jsessionid=(J2EE3417500)ID1494558950DB01504425675464955468End?rid=/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa&overridelayout=true
    while creating the module.
    but after finishing this , I can not see the ejb.jar file corresponding to the ejb project, I can see the class file generated in the build path.
    but I can not see the ejb.jar in the EJB project after build.
    When I checked the EAR project I found under Deployment descriptor there is a folder called module and there is  a jar file named as -
    EJB<my ejb project name>.jar
    when I am about to deploy this EAR  in the server it is showing  me to choose the file from EAR project and this EAR project contain the EJB Project .
    Request you to please let me know is everything ok with my project ? or please let me know how can I see the  ejb.jar  file corresponding to the ejb project below the build path.
    Thanks
    Vinny

    Hi Experts,
    I have created one adapter module, for this I have created one EJB project and also associated one EAR project to that.
    I have completed my coding and changes in the xml files.
    I have followed this -
    http://www.sdn.sap.com/irj/scn/index;jsessionid=(J2EE3417500)ID1494558950DB01504425675464955468End?rid=/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa&overridelayout=true
    while creating the module.
    but after finishing this , I can not see the ejb.jar file corresponding to the ejb project, I can see the class file generated in the build path.
    but I can not see the ejb.jar in the EJB project after build.
    When I checked the EAR project I found under Deployment descriptor there is a folder called module and there is  a jar file named as -
    EJB<my ejb project name>.jar
    when I am about to deploy this EAR  in the server it is showing  me to choose the file from EAR project and this EAR project contain the EJB Project .
    Request you to please let me know is everything ok with my project ? or please let me know how can I see the  ejb.jar  file corresponding to the ejb project below the build path.
    Thanks
    Vinny

  • Calling an RFC from an EJB over an Enterprise Connector

    Hi all,
    I would like to call an RFC enabled Function Modul (FuBa) from a BW-System over an EJB in a Web AS environment bei  passing SAP Logon Ticket.
    To achive this goal, i've generated proxy classes (Enterprise Connector) via NWDS .
    If i call enterprise connector localy from an example class (See attachment), it works.
    BUT
    if I use the same Code within an EJB, bei correct deployment , it doesn't work. I become an exception, during to establish a connection
    What is wrong here ?
    What do i have to do in an a EJB-Environment to use an Enterprise Connector ?
    Best Regards
    A. Büyükyilmaz
    ATTACHMENT
    Created on 13.02.2007
    To change the template for this generated file go to
    Window>Preferences>Java>Code Generation>Code and Comments
    package de.xxx.test.ep.main;
    import java.sql.Date;
    import java.text.ParseException;
    import java.text.SimpleDateFormat;
    import com.sap.aii.proxy.framework.core.ApplicationFaultException;
    import com.sap.aii.proxy.framework.core.SystemFaultException;
    import com.sap.mw.jco.JCO;
    import de.xxx.yyy.zzz.connectivity.fuba.Anlage_PortType;
    import de.xxx.yyy.zzz.connectivity.fuba.Zge_Gerel_Data_For_Kne_Kn_Input;
    import de.xxx.yyy.zzz.connectivity.fuba.Zge_Gerel_Data_For_Kne_Kn_Output;
    @author pg4011
    To change the template for this generated type comment go to
    Window>Preferences>Java>Code Generation>Code and Comments
    public class GetAnlage {
    private JCO.Client mConnection = null;
    public boolean connectToSAP(
    String client,
    String user,
    String passwd,
    String lang,
    String appServer,
    String sysNo) {
    try {
    mConnection =
    JCO.createClient(client, user, passwd, lang, appServer, sysNo);
    mConnection.connect();
    } catch (Exception e) {
    e.printStackTrace();
    return false;
    return true;
    public static void main(String[] args) {
    GetAnlage anlage = new GetAnlage();
    if (anlage.connectToSAP ("50", "abc", "pwd", "DE", "system", "00")) {
    System.out.println("Anlage wird erstellt");
    anlage.getData();
    System.out.println("");
    System.exit(0);
    private void getData() {
    // ImportParameter
    Zge_Gerel_Data_For_Kne_Kn_Input input = new Zge_Gerel_Data_For_Kne_Kn_Input();
    // Hole proxy Instance mit JCO.Client instance
    Anlage_PortType proxy = new Anlage_PortType();
    proxy.messageSpecifier.setJcoClient(mConnection);
    Zge_Gerel_Data_For_Kne_Kn_Output output = new Zge_Gerel_Data_For_Kne_Kn_Output();
    input.setI_Bp_Nr("7901514764");
    input.setI_View("03");
    input.setI_Spras("DE");
    Date stichtag = new Date(2006, 9, 22);
    input.setI_Stichtag(stichtag);
    //Rufe RFC auf
    try {
    output = proxy.zge_Gerel_Data_For_Kne_Kn(input);
    String s = "";
    System.out.println(s);
    } catch (SystemFaultException e) {
    e.printStackTrace();
    } catch (ApplicationFaultException e) {
    e.printStackTrace();

    Hi Rajesh,
    it's realy funny.  Although, i inserted som trace outputs behind of catch-statement, i do not see any information about exception in application log.
    but i see, that the method becomes correct inputparameters and i see it try to make a connection. After that, it end without a trace.
    Best Regards
    Ahmet

  • Stand-alone JNDI lookup of an EJB in an Enterprise Application (EAR) build

    Hi All,
    I am having some difficulty doing JNDI look up an EJB 3.0 Bean that is part of an Enterprise Application (EAR) build. Below are all the related codes:
    package ejb;
    import javax.ejb.Local;
    @Local
    public interface Hello1Local {
        public String getHello1();
    package ejb;
    import javax.ejb.Stateless;
    @Stateless
    public class Hello1Bean implements Hello1Local {
        public String getHello1() {
            return "I am Hello1 Bean!";
    package ejb;
    import javax.ejb.Remote;
    @Remote
    public interface Hello2Remote {
        public String getHello2();
    package ejb;
    import javax.ejb.Stateless;
    import javax.ejb.EJB;
    @Stateless
    @EJB(name="ejb/Hello1",
         beanInterface=Hello1Local.class,
         beanName="Hello1Bean")
    public class Hello2Bean implements Hello2Remote {
        @EJB private Hello1Local hello1bean;
        public String getHello2() {
            return hello1bean.getHello1();
    There is no problem looking up Hello2 Bean using an Application Client such as the following:
    public class LocalHelloApplicationClient {
        @EJB(name="Hello2")
        private static Hello2Remote hello2Bean;
        public static void main(String[] args) {
            System.out.println("hello2Bean.getHello2(): " + hello2Bean.getHello2());
    }There is also no problem doing JNDI lookup (from a Stand-Alone Client the same bean if both Hello1 and Hello2 were created by themselves. ie not part of an Enterprise Application (EAR) build. However, I am wondering whether it is possible to do JNDI lookup of the same bean (Hello2) that is part of an Enterprise Application (EAR) built. Below are the type of JNDI lookup entries that I have tried without success:
    public class StandalonePojoCallHelloWorld {
        public static void main(String [] args)
            try
                InitialContext jndiContext = new InitialContext();
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("ejb.Hello2Remote");
                                                                     or
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("LocalHelloEnterpriseApplication.Hello2.remote");
                                                                     or
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("LocalHelloEnterpriseApplication.ejb.Hello2Remote");
                                                                     or
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("LocalHelloEnterpriseApplication.Hello2Remote");
                                                                     or
                Hello2Remote hello2Bean =  (Hello2Remote) jndiContext.lookup("LocalHelloEnterpriseApplication.LocalHelloEnterpriseApplication-ejb.Hello2Remote");
                System.out.println("hello2Bean.getHello2(): " + hello2Bean.getHello2());
            catch (javax.naming.NamingException ne)
             ne.printStackTrace();
    They all came up with the same error message:
    javax.naming.NameNotFoundException: LocalHelloEnterpriseApplication.LocalHelloEnterpriseApplication-ejb.Hello2Remote not found
            at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
            at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
            at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:74)
            at com.sun.enterprise.naming.RemoteSerialContextProviderImpl.lookup(RemoteSerialContextProviderImpl.java:129)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)Any suggestion would be appreciated.
    Thanks,
    Jack

    Hello
    I've somme problems to get access to ejb interface from remote stand-alone client.
    Here is my EJB code :
    package stateless;
    import javax.ejb.Stateless;
    @Stateless(name = "TestSB", mappedName = "ejb/stateless/TestSB")
    public class TestEJBBean implements TestEJBRemote {
        public String getMessage() {
           return "Hello EJB World";
    }And the remote interface :
    package stateless;
    import javax.ejb.Remote;
    @Remote
    public interface TestEJBRemote {
        String getMessage();
    } In client side, i just edit main.java like this :
    package testclient;
    import java.io.FileInputStream;
    import java.util.Properties;
    import javax.naming.InitialContext;
    import stateless.TestEJBRemote;
    public class Main {
        public static void main(String[] args) throws Exception {
            Properties props = new Properties();
            props.load(new FileInputStream("jndi.properties"));
            InitialContext ctx = new InitialContext(props);
            TestEJBRemote testEJB = (TestEJBRemote) ctx.lookup("ejb/stateless/TestSB");
            System.out.println(testEJB.getMessage());
    }here is my jndi.properties file (my glassfish server IP is 192.168.0.10) :
    java.naming.factory.initial = com.sun.enterprise.naming.SerialInitContextFactory
    java.naming.factory.url.pkgs = com.sun.enterprise.naming
    java.naming.factory.state = com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl
    org.omg.CORBA.ORBInitialHost = 192.168.0.10
    org.omg.CORBA.ORBInitialPort = 3918when i run client on the same machine than the glassfish app server, it works fine.
    But i run it on the different machine than the glassfish app server (on the same LAN without firewall), it fails with this error message :
    eclan@eclan-laptop:~/NetBeansProjects/TestClient$ java -jar dist/TestClient.jar
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 3918"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 4038"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 4138"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 3918"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 4038"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    24 ao&ucirc;t 2008 09:53:05 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
    ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: 127.0.1.1; port: 4138"
    org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 201  completed: No
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
         at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
         at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
         at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
         at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
         at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
         at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
         at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:131)
         at com.sun.enterprise.naming.SerialContext.getRemoteProvider(SerialContext.java:220)
         at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:160)
         at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at testclient.Main.main(Main.java:14)
    Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
         at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
         ... 13 more
    Caused by: java.net.ConnectException: Connection refused
         at sun.nio.ch.Net.connect(Native Method)
         at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
         at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
         at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
         ... 14 more
    eclan@eclan-laptop:~/NetBeansProjects/TestClient$ THANKS YOU FOR YOUR HELP
    Justin

  • SAP Enterprise Services: Configuration Date

    I need the configuration dates for SAP Enterprise Services.
    Case: my team of APO BPXs has done an analysis of available SAP Enterprise Services using ES Workplace on March 4th. and 5th. But there was the update of APO from 5.0 to 7.0. Therefore I need the following information:
    - Did my APO group use APO/SCM 5.0 or 7.0 on March 4th. and 5th.? (Where is the history of updates on SAP Servers, in particular on HU08).
    - Where can I find a comprehensive list of the available SAP Enterprise Web Services with:
    Date WS Configured (so my BPX can review and check only the new WSs. This is a paramount in order to recommend updates on existing SOA applications that use "home made" web services?)
    Thanks a lot,
    Hugo

    Hi Henry,
    no problem. for a step by step approach. see this link
    https://www.sdn.sap.com/irj/sdn/soa-modeling?rid=/library/uuid/10cacdca-b0bb-2a10-77be-d600de4658b7
    Enterprise Services Repository&Registry - 60k
    https://boc.sdn.sap.com/node/18912
    http://blogs.microsoft.co.il/blogs/tamir/archive/tags/download/default.aspx
    thanks
    sagar
    reward me points if usefull

  • Integrate Standalone Proxy into EJB-Module

    Hello,
    I want to integrate a webservice-call into a standalone EJB-Method.
    Therefore I have created a standalone proxy DC and added public parts of type "assembly" and of type "compilation".
    After creating a DC of type EJB-Module I reference the standalone proxy as used dc in my new EJB-Module project.
    I CAN build the new EJB-Module DC. However when I look at the generated jar-file, the classes of the standalone proxy ARE NOT included.
    Therefore (after generating a DC of Type EAR-Project) the deployment process returns with an error as referenced classes of the webservice proxy cannot be loaded. All EJB-Classes are included
    in the EAR-File, but classes of the standalone proxy are missing.
    Does anybody know in which way have to reference the webservice libraries (=the webservice standalone-proxy) so that they are included in my EJB-JAR-File?
    PS: I don't want to replace the standalone proxy by a deployable proxy, if that is possible!
    Thanks for your help!
    Andreas

    Hi Andreas,
    here a link for more information:
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/87/5305adc23540b8ac7bce08dbe96bd5/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/87/5305adc23540b8ac7bce08dbe96bd5/frameset.htm</a>
    Regards,
    Boris

Maybe you are looking for