EJB lookup from Tomcat deployed on J2ee Engine

Hello  All,
                        I have a jsf application which runs on tomcat, Now I developed a EJB (stateless) in NWDS and deployed on SAP j2ee engine, when I run a plain java calss I am able to access it but not  through my web-app. Can anybody throw some light on why this is happening?
Thanks in Advance
Somil

Hello  All,
                        I have a jsf application which runs on tomcat, Now I developed a EJB (stateless) in NWDS and deployed on SAP j2ee engine, when I run a plain java calss I am able to access it but not  through my web-app. Can anybody throw some light on why this is happening?
Thanks in Advance
Somil

Similar Messages

  • Problem in Proxy call from an application deployed in J2EE engine

    Hi,
    I am trying Java Sender Proxy --> XI --> DB.
    I have generated o/b proxies using integration builder.
    <b>Following is the code that i am using for proxy call and it runs absolutely fine when runnning stand alone</b>
    <code Controller.java>
    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
    p.put(Context.PROVIDER_URL, "server:50004");
    p.put(Context.SECURITY_PRINCIPAL, "Administrator");
    p.put(Context.SECURITY_CREDENTIALS, "password");
    ctx = new InitialContext(p);
    ref = ctx.lookup("sap.com/ProxySenderEAR/UsersSyncMI_PortTypeBean");
    queryOutHome = (UsersSyncMI_PortTypeHome) PortableRemoteObject.narrow(ref, UsersSyncMI_PortTypeHome.class);
    queryOutRemote = queryOutHome.create();
    UserDT_Type reqtype =     new UserDT_Type();
    reqtype.setUsername(name);
    reqtype.setPassword(pwd);
    UsersDBMTResponse_Type response = queryOutRemote.usersSyncMI(reqtype);
    role = response.getRole();
    </code>
    I am including this java file(Controller.java) in the same EJB project ProxyEJB which includes
    my beans and home/local/remote interfaces.
    Then I have created a Web Module Project ProxyWeb, that includes Proxy.jsp.
    In proxy.jsp i am using the following code
    <%
    Controller obj = new Controller();
    String name = request.getParameter("uname");
    String password = request.getParameter("pwd");
    String role = obj.getRole(name,password);
    %>
    Then I have included both ProxyWeb and ProxyEJB in ProxyEAR file, created Enterprise Archive and Deployed in J2EE engine.
    and when I call the jsp...i am not getting expected result.
    When i am debugging the code using try catch blocks for the controller.java...I observed that
    Problem occured at :
    <code>
    queryOutHome = (UsersSyncMI_PortTypeHome) PortableRemoteObject.narrow(ref, UsersSyncMI_PortTypeHome.class);
    queryOutRemote = queryOutHome.create();
    </code>
    what i am not able to uderstand is that ...when it is working fine when calling from standalone ...then
    why it's giving me problems when deployed in j2ee engine...
    note: I am using all required jars for XI.(included in ProxyEJB).And I have used NetWeaver Developer Studio for the above EAR,WAR projects.
    Kindly suggest,
    Regards
    Vedavyas

    The JNDI call is different when you call an EJB from inside the J2EE.
    ctx = new InitialContext();
    ref = ctx.lookup("java:comp/env/<JNDI-Name>");
    Regards
    Stefan

  • How to create simple JSP and deploy to J2EE engine?

    Hi,
    I need to create simple JSP pages and deploy it to SAP J2EE engine.. what is the procedure?...I may later add some businness logic but not needed for now.
    Please help
    Thanks,
    Jai

    Gabrie,
    Here are Simple steps,
    In the NWDS
    1) create J2EE -> Web Module Project    (XYZ)
    2) create/add your JSP pages to the project
    3) Right click on your project root and click on 'Build Web Archive' from the context
    3) create J2EE -> Enterprise Application project(EAR)
    4) Right click on your Web Module Project root and click on 'Add to EAR Project' from the context, select the EAR you just created in step 3.
    5)Right click on your EAR project root and click on 'Build WebApplication Archive' from the context
    6)Expand the EAR project node, and right click on the *.ear file, click on 'Deploy to J2EE Engine'.
    7)Enter your SDM password  when prompted,
    You can access you JSP at this url
    http://server:port/xyz/a.jsp
    - Dileep

  • How to use external library in EAR deployed onto J2EE engine

    For certain reasons some classes in .jar file in operation system level should be used in the EAR project I've deployed onto J2EE Engine.
    Can some one tell me what steps I should perform to acheive this?

    hey there,
    Think im already late for this... but it may be useful to someone who reads this forum later.
    I am struggling with exactly the same problem for the past more than 24
    odd hours now. The sad part - Im sure I have seen this being done in a
    matter of a few minutes when my team mate had an older version on NWDS.
    (I am currently using SP16 NWDS). May be this indeed is a bug that SAP
    needs to fix in its SP16 NWDS release.
    I need to use the HSSF POI libraries for my webdynpro components and
    have been trying ALL possible options given out here on SDN. To mention a
    few, I have tried -
    1) Jarrod's method of making a Java DC and then declaring a usage
    dependency for it inside a J2EE Server (library) DC. It didnt work... it
    gave me a warning that an illegal reference has been made to the runtime
    public part. And the final SDA file generated in the J2EE server
    component DC DIDNOT contain the jar files that I had added to the public part
    of the Java DC. On investigating further, I found that there were NO
    entities present in BOTH the public parts of the Java DC, even though the
    folder actually contained all the required .jar files.
    2) Creating an External Library DC, adding the JAR files to the
    'libraries' folder. Creating two public parts, one for assembly and the second
    for compilation. Then adding this DC as a 'Used DC' into a J2EE Server
    (library) DC. Yet, the .sda file that is created on building the J2ee
    Server (library) DC DOESNOT contain the JAR files.
    3) Creating an external library DC, adding the JAR files to the
    'libraries' folder. Creating two public parts, one for assembly and the second
    for compilation. Then adding this DC as a 'Used  DC' into a webdynpro
    DC. On building this webdynpro DC, the .ear file DOESNOT contain the JAR
    files.
    4) Directly adding the JAR files to my own webdynpro component in the
    'src/packages' folder. This didnt work because on rebuilding the
    project, the JAR files get deleted on their own.
    5) Renaming my .JAR files to .ZIP, extracting the entire package
    structure into folders, copy pasting this entire folder structure along with
    its .class files into the src/packages folder. On rebuilding, the NWDS
    deletes these folders and files on its own / behaves erratically. Also
    copy pasted these .class files along with the proper package structure
    into the '/bin' directory of my webdynpro application, but it still
    didnt work.
    The only thing that I have to try yet is to shift to SP10 of NWDS,
    build this external library project and get the required JAR files put on
    the wendynpro server. After that I might choose to get back onto the
    SP16 version and hopefully continue productive work... !
    Regards,
    Navneet.

  • Error in Online Deployment patching J2EE Engine

    Hi,
    We are installing the J2EE engine in a BW server with Windows S.O. In step "Deploy Online" we obtain the following error:
    Sep 13, 2006 8:23:22 AM  Info: Start logging to console
    Sep 13, 2006 8:23:22 AM  Info:
    Sep 13, 2006 8:23:22 AM  Info: ============================================
    Sep 13, 2006 8:23:22 AM  Info: =   Starting to execute command 'deploy'   =
    Sep 13, 2006 8:23:22 AM  Info: ============================================
    Sep 13, 2006 8:23:22 AM  Info: Starting SDM - Software Deployment Manager...
    Sep 13, 2006 8:23:23 AM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
    Sep 13, 2006 8:23:24 AM  Info: SDM operation mode successfully set to: Standalone
    Sep 13, 2006 8:23:25 AM  Info: Initializing Network Manager (50017)
    Sep 13, 2006 8:23:25 AM  Info: Checking if another SDM is running on port 50018
    Sep 13, 2006 8:23:25 AM  Info: -
    Starting deployment -
    Sep 13, 2006 8:23:25 AM  Info: Error handling strategy: OnErrorStop
    Sep 13, 2006 8:23:25 AM  Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Sep 13, 2006 8:23:25 AM  Info: Update strategy: UpdateLowerVersions
    Sep 13, 2006 8:23:25 AM  Info: Starting deployment prerequisites:
    Sep 13, 2006 8:23:31 AM  Info: Loading selected archives...
    Sep 13, 2006 8:23:31 AM  Info: Loading archive 'E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
    Sep 13, 2006 8:23:38 AM  Info: Selected archives successfully loaded.
    Sep 13, 2006 8:23:39 AM  Info: Actions per selected component:
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'1' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060426183247.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'1' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172955.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818153022.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' will not update currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'1' updates currently deployed development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119145451.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'1' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101332.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'2' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027101045.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164207.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'1' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818152118.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'1' will not update currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'1' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050331133205.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'1' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100235.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'1' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818150135.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'1' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101350.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'1' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164103.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119123705.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: No action: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'1' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4017.00.0000.20041104140331.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:39 AM  Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
    Sep 13, 2006 8:23:40 AM  Info: Ending deployment prerequisites. All items are correct.
    Sep 13, 2006 8:23:41 AM  Info: Saved current Engine state.
    Sep 13, 2006 8:23:41 AM  Info: Starting: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
    Sep 13, 2006 8:23:41 AM  Info: SDA to be deployed: E:\usr\sap\SBD\DVEBMGS00\SDM\root\origin\sap.com\com.sap.lcr.saprfc\SAP AG\1\6.4018.00.0000.20060706111625.0000\lcrsaprfc.ear
    Sep 13, 2006 8:23:41 AM  Info: Software type of SDA: J2EE
    Sep 13, 2006 8:23:41 AM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 13, 2006 8:24:03 AM  Info: Begin of log messages of the target system:
    06/09/13 08:23:57 -  ***********************************************************
    06/09/13 08:23:59 -  References from application sap.com/com.sap.lcr.saprfc to its loaders done.
    06/09/13 08:23:59 -  Start updating EAR file...
    06/09/13 08:23:59 -  start-up mode is lazy
    06/09/13 08:23:59 -  EAR file updated successfully for 94ms.
    06/09/13 08:23:59 -  Start updating...
    06/09/13 08:24:00 -  EAR file uploaded to server for 719ms.
    06/09/13 08:24:03 -  ERROR: Not updated. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
                         Reason: com/sap/mw/jco/JCO$Function; nested exception is:
                              java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              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:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
                              at java.lang.Class.getDeclaredMethods0(Native Method)
                              at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
                              at java.lang.Class.privateGetPublicMethods(Class.java:1778)
                              at java.lang.Class.getMethods(Class.java:832)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:121)
                              at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
                              at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
                              at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
                              at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
                              at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:670)
                              ... 10 more
                         For detailed information see the log file of the Deploy Service.
    06/09/13 08:24:03 -  ***********************************************************
    Sep 13, 2006 8:24:03 AM  Info: End of log messages of the target system.
    Sep 13, 2006 8:24:03 AM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Sep 13, 2006 8:24:03 AM  Error: Aborted: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1', grouped by :
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
    Reason: com/sap/mw/jco/JCO$Function; nested exception is:
         java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Sep 13, 2006 8:24:03 AM  Info: Starting to save the repository
    Sep 13, 2006 8:24:04 AM  Info: Finished saving the repository
    Sep 13, 2006 8:24:04 AM  Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
    Sep 13, 2006 8:24:04 AM  Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1':
    Failed deployment of SDAs:
    development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' : aborted
    Please, look at error logs above for more information!
    Sep 13, 2006 8:24:04 AM  Info: Starting to save the repository
    Sep 13, 2006 8:24:04 AM  Info: Finished saving the repository
    Sep 13, 2006 8:24:04 AM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Sep 13, 2006 8:24:04 AM  Error: -
    At least one of the Deployments failed -
    Sep 13, 2006 8:24:05 AM  Info: Summarizing the deployment results:
    Sep 13, 2006 8:24:05 AM  Error: Aborted: E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA
    Sep 13, 2006 8:24:05 AM  Error: Processing error. Return code: 4
    Regards,

    Hi everybody,
    Well, after of the last post where it commented that the possible solution would be to update Java to version 12, the issue continues.
    Now, we have the following error after SAP recommended to deploy the file manually with SDM Tool, the file is lcrsaprfc.ear and show the following error:
    Manifest attributes are missing or have badly formatted value:
    attribute keylocation is missing
    attribute keyname is missing
    attribute keyvendor is missing
    attribute keycounter is missing
    Maybe can be a problem with the file?, format?, build?.
    Thanks for your help and patience.
    Regards,
    Rafa R.R.

  • CAF Services not deployed to J2EE engine

    HI @all,
    I desgined an application service in CAF and deployed it to my CE-systtem.
    Developer Studio doesn't display any errors.
    I'm using the user Administrator with the roles CAF_Admin and CAF_Developer
    But when I use the "test service" functionality I get the following message, when the testing windows in IE is loaded:
    German: "Service <<name>> nicht auf J2EE Engine bereitgestellt"
    So the service is not on the J2EE engine.
    Thus I can't map this service to a destination to use it in Visual Composer.
    What's wrong?
    Kiing regards and thanks in advice
    Manfred Pielmeier

    To my understanding the j2ee engine configured to ur NWDS should be the same as from where u r trying to run the "test service". So please do check that.
    As far as what error tells is that such a service is not deployed, it means that u should have deployed in a different server. Its just a check that i wnat u to make.
    Regards
    Ashok

  • SAP netweaver developer studio - deploying to j2ee engine - URGENT!!

    I am trying a deploy a j2ee application from SAP netweaver developer studio. It is asking for SAP J2EE engine's message server port. Do you know from where I can find that???

    Hi,
    the message server port is given in the profile file for the Central Services instance of the J2EE Engine. Here's the path to this file: \usr\sap\<SID>\SYS\profile directory. The file name is formed using the following scheme: <SID>_<Central_instance_name>_<hostname>.
    Open it with a text editor and have a look at the value of the rdisp/msserv property (this is the port of the message server you need to use).
    Regards,
    Ivo

  • EJB lookup from another EJB server

    Hi people,
    I have two application servers on two different computers. One
    of them contains an EJB, which I need to access from another EJB
    server. I know that I can achieve this using RMI, but will then
    security and transaction contexts be propagated to the called
    EJB?
    Sincerely,
    Sergei Batiuk.

    Here is the solution posted on another forum:
    [email protected] Dec 8, 6:03 am show options
    Newsgroups: ibm.software.websphere.studio
    From: [email protected]
    Date: 8 Dec 2004 06:03:04 -0800
    Local: Wed, Dec 8 2004 6:03 am
    Subject: Re: EJB lookup on from one server to another does not work
    Eric,
    I dealt with this same problem trying to run 2 local servers (websphere
    test servers), using 2 separate WSAD 5.1.2 workspaces. Running on 1
    server I have an application that contains an EJB, and running on the
    other server is an application that uses an access bean to make a
    remote call to my EJB, running on my other server. I too repeately
    received the "NameNotFoundException" when trying to lookup my EJB home
    reference.
    What you have to do to get around this is to modify the server
    configuration of the application that contains the EJB that you are
    attempting to call remotely. You must open the the server.wsi file for
    the server that is running the EJB and go to the "Configuration" tab.
    You must check the "Enable administrative console". Once this is
    complete, start your server. When it is started, right click on the
    server, and select "run administrative console". In the admin console,
    select
    servers -> application servers -> <your server> -> end points ->
    bootstrap address. For "host" you must change "localhost" to either
    your ip address or computer name (ive only tried my ip, but your
    computer name should work too). When building your properties to get
    the initial context, make sure you use
    "env.put(Context.PROVIDER_URL, "corbaloc:iiop:<the ip or computer name
    listed as the bootstrap host of server running ejb>:<the port listed as
    the bootstrap port of server running ejb, which is 2809 in your case>
    Restart your server and things should work.

  • JNDI lookup from Tomcat to EJB Container

    Hello!
    i am currently trying to use a combination of Catalina and an external EJB Server (running on another machine).
    i am really struggeling with doing the jndi lookup. i have no idea where and how to set the properties in the web server and do the mapping from the ejb-refs to the jndi name? (since tomcat doesnt seem to have a deploymentplan?!)
    maybe someone here knows the problem and can help, please?
    (i am not sure but this might also be the wrong discussion group for that??)
    thanks
    wolfgang

    Hello Wolfgang,
    I solved this problem by setting the proper jndi properties in the startup phase (MyInitServlet) by System.setProperty(...).
    This seems ugly, but it works.
    Tilo

  • I have problem in ejb 3 . i m run ejb 3 in weblogic 10.3 and struts in tomcat. i m call ejb remote from tomcat.

    Jul 2, 2013 1:24:14 PM org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet action threw exception
    java.lang.ClassNotFoundException: ejb3.onlyejb.Int6_cls
        at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.getClassBytes(RemoteBizIntfClassLoader.java:151)
        at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.loadClass(RemoteBizIntfClassLoader.java:96)
        at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:54)
        at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.readObject(RemoteBusinessIntfProxy.java:205)
        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)
        at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
        at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
        at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
        at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
        at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
        at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
        at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
        at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
        at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
        at weblogic.jndi.internal.ServerNamingNode_1030_WLStub.lookup(Unknown Source)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:392)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at ejb3.onlywed.Action_cls.execute(Action_cls.java:62)
        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
        at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
        at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
        at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)
    Jul 2, 2013 1:24:21 PM org.apache.catalina.core.ApplicationContext log
    INFO: HTMLManager: init: Associated with Deployer 'Catalina:type=Deployer,host=localhost'
    Jul 2, 2013 1:24:21 PM org.apache.catalina.core.ApplicationContext log
    INFO: HTMLManager: init: Global resources are available
    Jul 2, 2013 1:24:21 PM org.apache.catalina.core.ApplicationContext log
    INFO: HTMLManager: list: Listing contexts for virtual host 'localhost'
    accno=77
    na=nj
    bal=88.0
    enter in to if loop
    jndi properties nuderprocess
    jndi properties nuderprocess22
    loading p file={java.naming.provider.url=t3://localhost:7001, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}
    loading p file over=javax.naming.InitialContext@725967
    jndi file is  loaded
    entry in try block
    Jul 2, 2013 1:24:42 PM org.apache.catalina.core.StandardWrapperValve invoke
    SEVERE: Servlet.service() for servlet action threw exception
    java.lang.ClassNotFoundException: ejb3.onlyejb.Int6_cls
        at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.getClassBytes(RemoteBizIntfClassLoader.java:151)
        at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.loadClass(RemoteBizIntfClassLoader.java:96)
        at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:54)
        at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.readObject(RemoteBusinessIntfProxy.java:205)
        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)
        at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1846)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
        at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945)
        at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869)
        at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
        at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
        at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)
        at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:564)
        at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:193)
        at weblogic.rmi.internal.ObjectIO.readObject(ObjectIO.java:62)
        at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:240)
        at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
        at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
        at weblogic.jndi.internal.ServerNamingNode_1030_WLStub.lookup(Unknown Source)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:392)
        at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
        at javax.naming.InitialContext.lookup(InitialContext.java:392)
        at ejb3.onlywed.Action_cls.execute(Action_cls.java:62)
        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
        at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
        at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
        at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)

    Stop multiposting. Mod: locking

  • J2EE Engine Deployment Error

    I have written the betting pool applicaton for Soccer world Cup (/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-i)
    now i would like to deploy to j2ee Engine((/people/raphael.vogel/blog/2006/05/18/writing-a-betting-pool-application-for-the-soccer-world-cup-2006-part-ii), Deploy and test the Services)
    but i receive follow error:
    01.06.2006 14:57:28 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [029]Deployment aborted
    Settings
    SDM host : uxept01
    SDM port : 50118
    URL to deploy : file:/C:/DOKUME1/FICHTE1/LOKALE1/Temp/temp46974sap.comwc~metadata.ear
    Result
    => deployment aborted : file:/C:/DOKUME1/FICHTE1/LOKALE1/Temp/temp46974sap.comwc~metadata.ear
    Aborted: development component 'wc/metadata'/'sap.com'/'local'/'20060601143708':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/wc_metadata.ear. Reason: None of the available containers recognized the components of application sap.com/wc~metadata; it is not possible to make deploy. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Can anybody help me please
    Thanks
    Julia
    Message was edited by: Julia Fichtel
    Message was edited by: Julia Fichtel

    I also had this error and was solved with just uninstalling everything and reinstalling it again.
    I followed the following steps proposed in other forum:
    Regards,
    María Margarita Monteverde
    Hello Andre,
    It seems that you'd already an NWDS installation on your machine that wasn't de-installed completely. Before you install an new NWDS you must be sure that the following steps have been checked:
    1) Having completely run the de-installation routine of the NWDS
    2) It’s recommended to delete the directories “c:program filessapide” and “c:program filessapjdt” to be sure that there won’t stay any ‘old’ files.
    3) Furthermore you should delete the folder ‘workspace’ (including all files and subfolders) in the path ‘c:documents and settingsDocumentsSAP’ (where d012345 is your username). Or move this folder somewhere in the file system, afterwards you may re-import the 'old' projects.
    4) It's recommended to delete all .dtr/.dtc/.metadata directories in your personal folder (e.g. C:Documents and Settingsd0abcde).
    Please stop the IDE before you do all these steps.
    Regards,
    Jan
    Message was edited by:
            Maria Margarita Monteverde

  • Newbie - NoClassDefFound in J2EE engine

    We are having a classpath problem when deploying a simple EJB in a 6.30 SAP J2EE engine using NetWeaver.
    We are using an EJB that uses a connector via JCA. I am able to get a connection, but when I make a call to "getRecordFactory()" I get the following exception:
    java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Request
         at com.sap.mw.jco.jra.JRA$ManagedConnectionFactoryImpl.getRecordFactory(JRA.java:2332)
         at com.sap.mw.jco.jra.JRA$ConnectionFactoryImpl.getRecordFactory(JRA.java:3646)
         at com.hydroquebec.lsw.persistancesap.FacadeLswSAPBean.getConnection(FacadeLswSAPBean.java:58)
         at com.hydroquebec.lsw.persistancesap.FacadeLswSAPBean.authentifierClientAffaireAvecCodeActivation(FacadeLswSAPBean.java:89)
         at com.hydroquebec.lsw.persistancesap.FacadeLswSAPObjectImpl0.authentifierClientAffaireAvecCodeActivation(FacadeLswSAPObjectImpl0.java:119)
         at com.hydroquebec.lsw.persistancesap.FacadeLswSAP_Stub.authentifierClientAffaireAvecCodeActivation(FacadeLswSAP_Stub.java:56)
         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:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy91.authentifierClientAffaireAvecCodeActivation(Unknown Source)
         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:324)
         at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:146)
         at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:68)
         at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
         at SoapServlet.doPost(SoapServlet.java:51)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:337)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:315)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:815)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:238)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:151)
    Implied  stop : sap.com/tcwdcorecomp --> sap.com/tcwddispwda
    Implied  stop : sap.com/tcwdtools --> sap.com/tcwdcorecomp
    Implied  stop : sap.com/tcwdtools --> sap.com/tcwddispwda
    In NetWeaver (version 2.0.7), I have two projects: EJB and EAR. In the EJB project I have added the reference to the j2eeca library reference.
    I have done the same for the EAR project. It was my understanding that this was sufficient, for the JRA and JCO libraries already
    exist in the engine and were properly validated when creating the Resource definition in the J2EE engine. I tried simply adding sapjra.jar and
    sapjco.jar in both the ear and ejb jar files, but I still get the same exception.
    Has anyone had this problem, any ideas/recipes for correcting my classpath errors ?
    Thanks in advance,
    Mark

    Hi Mark,
    Re: SAP J2EE engine problem
    I guess the solution I have posted in this thread could help you out in solving your problem. No class def found error refers to not able to locate the correct jar files in the application.
    Ravi

  • J2EE Engine

    Hi,
    Explain me J2EE engine.If we deploy the Webdynpro-java application at the same time other one deploy the another application,which application take first and what is the procedure to deploy the applications,where we delete the deployed applications.If SDN shows red color what we do that and explain me SDN also and paths also.

    The J2EE engine is the Engine which is going to deploy and execute the webdynpro applications.If only server instance is present and  no child instance is available for the J2EE engine,with this scenario if 2 applications are depolyed at the same time then the J2EE engine is going to process the request which comes first to it.And you are going to get an error saying that 'There are already active session' for the other application is deployed.The child instances are created to balance the load on the server.
    IN J2EE ENGINE SDM is responsible for the deployment.It takes care of all the deployments from various NWDS.
    You can configure the J2EE engine from your NWDS - systempreferences---j2ee engine and provide the details
    SDN--system landscape directory is to list out all the systems implemented in the landscape.
    You can create various 'Techincal systems' to identify the various heterogeneous systems implemented in the landscape.
    WEBAS-ABAP--- to identify the sap systems(like ECC,R3,BW,CRM)
    WEBAS-JAVA---- to identify the j2ee engine.
    THIRDPARTY-----to identify the RDBMS sytem
    XI----
    to identify the XI system
    If any queries then reply to the thread.
    Edited by: cool dude on Jan 24, 2008 3:15 PM
    Edited by: cool dude on Jan 24, 2008 3:26 PM

  • Access EJB 3.0 (deployed on Glassfish v3) from Tomcat 6.0.20 (Netbeans 6.8)

    Hi all,
    I'm a newbie (of java EE and Sun forum).
    I have a problem.
    I followed this tutorial: http://technology.amis.nl/blog/1368/connecting-to-an-ejb-30-remote-sessionbean-from-tomcat
    using Netbeans 6.8, Tomcat 6.0.20, Glassfish v3.
    The deploy of EJB on Glassfish is OK.
    The deploy of WebApp on Tomcat is OK.
    But when I access to the servlet using the browser I receive this exception.
    javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.enterprise.naming.SerialInitContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.enterprise.naming.SerialInitContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at web.MyServlet.processRequest(MyServlet.java:51)
    at web.MyServlet.doGet(MyServlet.java:75)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:390)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
    at java.lang.Thread.run(Thread.java:619)
    I know that I must copy *.jar files in Tomcat dir and App libraries (https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#Step_3._Include_appserv-rt.jar_and), but it doesn't work.
    What are my mistakes?
    Thank you for your help.
    Servlet code:
    package web;
    import java.io.IOException;
    import java.io.PrintWriter;
    import javax.servlet.ServletException;
    import javax.servlet.http.HttpServlet;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
    import java.util.Properties;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import testbean.MySessionBeanRemote;
    * @author Stefano
    public class MyServlet extends HttpServlet {
    * Processes requests for both HTTP <code>GET</code> and <code>POST</code> methods.
    * @param request servlet request
    * @param response servlet response
    * @throws ServletException if a servlet-specific error occurs
    * @throws IOException if an I/O error occurs
    protected void processRequest(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException {
    response.setContentType("text/html;charset=UTF-8");
    PrintWriter out = response.getWriter();
    Properties props = new Properties();
    props.setProperty("java.naming.factory.initial", "com.sun.enterprise.naming.SerialInitContextFactory");
    props.setProperty("java.naming.factory.url.pkgs", "com.sun.enterprise.naming");
    props.setProperty("java.naming.factory.state", "com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");
    props.setProperty("org.omg.CORBA.ORBInitialHost", "localhost");
    props.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
    try {
    out.println("<html>");
    out.println("<head>");
    out.println("<title>Servlet MyServlet</title>");
    out.println("</head>");
    out.println("<body>");
    out.println(MySessionBeanRemote.class.getName());
    try {
    InitialContext ic = new InitialContext(props);
    MySessionBeanRemote mySessionRemote = (MySessionBeanRemote) ic.lookup("pippo");
    out.println(mySessionRemote.getOK());
    } catch (NamingException ex) {
    ex.printStackTrace();
    out.println("</body>");
    out.println("</html>");
    } finally {
    out.close();

    Yes, I did.
    I'm not sure about the right actions to do.
    For example: the Glassfish FAQ told me to add gf-client*.jar to the Tomcat folder, not appserv-rt.jar , with v3.
    I tried with both files. I restarted Tomcat, but nothing work :-(

  • Issues in looking up a ejb deployed on glassfish from tomcat.

    Hi all,
    I have followed the steps mentioned in the EJB FAQ in the glassfish site and was able to lookup a remote ejb deployed in glassfish from a standalone client.
    In case of standalone client, i set the appropriate jndi properties in the initial context as mentioned in the FAQ and added the 4 jars specified to the classpath of the application.
    It all worked perfectly well.
    But I attempted to do the same from a servlet running under tomcat.
    I set the appropriate jndi properties in the intial context and added 4 jars specified in the lib directory of the war file.
    But this did not turn out well and tomcat complained me with some servlet init errors.
    Then i searched through the web and found this posting from you:
    http://www.archivesat.com/GlassFish_Enterprise_JavaBeans_Developers/thread1399339.htm
    Then i created a folder called "shared/lib" under TOMCAT_HOME directory in my machine and ran the same example. Wow.....miraculously the application ran well.
    But i found that the "index.jsp" which i configured in the welcome file list does not appear now. But i was able to access the servlet without any problem. And the servlet was able to successfully lookup the ejb deployed in glassfish.
    Then i thought, let me try to access the ejb from a jsf application.
    Then i created a jsf application in netbeans 5.5.1 and tried to access the bean deployed in glassfish.
    (Note: the jsf application runs in tomcat 5.5.17 which is bundled with netbeans)
    OOPSS....
    Tomcat now complains me that it cannot compile the jsp page..
    This is the error i got...
    org.apache.jasper.JasperException: Unable to compile class for JSP
    Generated servlet error:
    C:\Documents and Settings\james\.netbeans\5.5.1\apache-tomcat-5.5.17_base\work\Catalina\localhost\CityExplorer-WebClient1\org\apache\jsp\index_jsp.java:7: org.apache.jsp.index_jsp is not abstract and does not override abstract method getDependants() in org.apache.jasper.runtime.JspSourceDependent
    public final class index_jsp extends org.apache.jasper.runtime.HttpJspBase
    ^
    Generated servlet error:
    C:\Documents and Settings\james\.netbeans\5.5.1\apache-tomcat-5.5.17_base\work\Catalina\localhost\CityExplorer-WebClient1\org\apache\jsp\index_jsp.java:12: getDependants() in org.apache.jsp.index_jsp cannot implement getDependants() in org.apache.jasper.runtime.JspSourceDependent; attempting to use incompatible return type
    found : java.lang.Object
    required: java.util.List
    public Object getDependants() {
    ^
    2 errors
    org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
    org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
    org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
    org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
    org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
    Any ideas...
    Can you please help me.
    I've noticed that you were eagerly answering questions related to ejb lookup in many places.
    I feel there is some potential compatability issue between tomcat and glassfish...
    I request you to investigate on this and clarify the community with your response.
    Thanks in advance,
    James Selvakumar

    Thank you guys!
    I've found the answer myself.

Maybe you are looking for