BW Web Service J2EE Engine

Hello,
Please can anyone tell me,
1. if the J2EE Engine must be installed to send XML data to BW using the HTTP port provided under the WAS soap service?
I am new working with XML data for BW and we do not have the engine installed. I have followed the 'How to send XML data to BW' but it is not clear on my question.  We are using BW 3.5.
Thank you for any advise

Hello Teresa,
it is not necessary to run an J2EE engine to send XML data to BW.
Then you craete an DataSource based on a WebService Source System we generate a WebService / WSDL in background. You can find this WebService in Transaction WSADMIN. This WebService can be used in any other development tools which can handle WSDL or can send data to the http protocoll to the WebApplications Server (ABAP).
Best,
Michael
ps. The Howto paper is very old and not released for NetWeaver 2004s.

Similar Messages

  • SAP WEBAS 640 J2EE Engine Instalation

    Hi All,
    This is Clark, We are trying to configure ADS. We already installed ECC 5.0,(oracle database) on windows server. We are trying to install J2EE engine. kindly let me know from where to download and how to install.
    Thanks,
    Clark

    Hi Abhishek,
    I was trying to install java components in ECC 5.0 IDES Server. it showing an error " This Installation requires an SAP J2EE Engine version 6.30 or higher"
    and then i gave NEXT then it gave another error message " No instance found for the central instance. Check your file system. Install Web AS 6.30 and restart this deployment afterwards".
    Kindly let me know how to find which version of Web AS now i am using and how to upgrade to higher version.
    Thanks,
    Clark

  • Web services: j2ee 1.4 vs weblogic

    hi.
    i have been an enterprise java developer for some years now but have not
    stepped into web services realm until very recently. one of the reasons
    for me holding back was due to this piece of news that i stumbled upon
    about 4 months ago. it stated that Sun's implementation of web services
    will not be fully functional until its ee 1.4 release. it claimed that
    due to this lag, many app server vendors (BEA being one of them) are not
    waiting for Sun, but instead developing their own versions of web
    service imlementation which are specific to their respective enterprise
    environments.. as a result, this would lead away from a standardized
    implementation of web services within the java world. what is your take
    on this?
    thanks!!!

    Hi Mikhail,
    IMHO, Sun absolutely "drug its feet" with the JSRs that eventually resulted in
    the "Java Web Services Developer Pack" (JWSDP)! See http://java.sun.com/webservices/downloads/webservicespack.html.
    By the time they came up with suitable APIs, all the vendors creating Java-based
    implementations of the XML grammars that underly Web services, already had shipping
    product ;-) Naturally, they (Sun) would like to see all these vendors move there
    product's code-base onto the API in the JWSDP, and I presume some will. The problem
    I see with JWSDP is that it doesn't truly address what is still the biggest issue:
    interoperability between Microsoft's Web Services tools (.NET, ASP.NET, or whatever)
    and the Java-basd Web Services tools. A lot of vendors have already made "substantial
    headway" in resolving this problem, and I doubt if they are willing to give this
    up ;-)
    That said, I think you will find that most J2EE-vendors (can't really speak for
    WebLogic, of course) will wait until JWSDP becomes part of a J2EE specification,
    before they expend a lot of effort "porting" their Web Service platforms to its
    APIs ;-) You should probably pose your question to folks like Graham Glass (from
    MindElectric, creators of GLUE) and Anne Thomas Mannes (CTO of Systinet, creators
    of WASP). I'm sure they will be forthright and candid with their reply.
    Regards,
    Mike Wooten
    mikhail perelman <[email protected]> wrote:
    hi.
    i have been an enterprise java developer for some years now but have
    not
    stepped into web services realm until very recently. one of the reasons
    for me holding back was due to this piece of news that i stumbled upon
    about 4 months ago. it stated that Sun's implementation of web services
    will not be fully functional until its ee 1.4 release. it claimed that
    due to this lag, many app server vendors (BEA being one of them) are
    not
    waiting for Sun, but instead developing their own versions of web
    service imlementation which are specific to their respective enterprise
    environments.. as a result, this would lead away from a standardized
    implementation of web services within the java world. what is your take
    on this?
    thanks!!!

  • Restricting HTTP Port on J2EE Engine

    I have to disable the HTTP Port on Web AS J2EE Engine and allow connections only through https.
    Is it possible to do so ? If yes, how ?
    Thanks for the help in advance.

    Yes, It is definitely possible.
    You will have to login to Visual Administrator, and then under Service, go to the HTTP Provider details. You will find a value specifying both http and https values (if already configured). You can remove the http part, which will allow you to remove the http access.
    Let me know if you face problems with this.

  • SAP J2EE Engine 6.40 Web Services Documentation & Samples

    Where can we find the J2EE Engine 6.40 as well as ABAP Web services documentation as well as the sample applications?
    Thanks in advance

    Hi Vladimir
    Please check the following links
    J2ee engine webservices
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f76f9f90-0201-0010-bf84-d0409ea425f1
    ABAP webservices
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/244e7923-0a01-0010-5887-fe0b0c6dbb8d
    /people/thomas.jung3/blog/2004/11/15/bsp-150-a-developer146s-journal-part-xiii-developing-abap-webservices
    /people/durairaj.athavanraja/blog/2004/09/20/consuming-web-service-from-abap
    /people/thomas.jung3/blog/2005/05/09/abap-webservices-logon-language-processing
    Hope it helps
    Regards

  • J2EE Engine service Web Services Security

    Hi,
    My Web Services Security in J2EE Visual Administrator does not show anything in Runtime tab. I want to see Web Services Client as per ADS Config guide documentation. Please help!!!
    QT

    QT,
    Please check this document:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1b651014-0301-0010-c39a-98d7cd057847
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e08627de-9816-2a10-02b7-cbd60f7e4b2c
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/92914af6-0d01-0010-3081-ded3a41be8f2
    Hope it helps.
    Thanks
    Mona

  • Is J2EE engine a must for Web Services?

    Hi Folks,
    When I installed mySAP (version 6.4) on our test system, I don't recall installing the J2EE server. Things were working fine until today when I decided to experiment with Web Services.
    When you run transaction WSADMIN, the list of Web Services shows two Web services by default:
    SRT_TESTS_FB_ADD_WSD
    SRT_TESTS_FB_SUM_WSD
    When I select any one and click on "Web Services Home Page", I get an error "Settings for J2EE Server do not exist."
    My understanding is that J2EE server would be needed only if I wish to develop a Web Service in Java. To develop a Web Service in ABAP (which is our case), I do not really need this.
    What am I missing? Is it that these two Web services that show up by default written in Java? How can I verify this?
    Also, is there any "Hello World!" ABAP Web Service article out there that I can peruse?
    Thank you in advance for your help.
    Pradeep

    Hi Ingo,
    There is no "Reply" button available on your message. I am using this message to reply to you.
    Thank you for your help. I actually found a tutorial on running Web Services wizard for ABAP RFC. I managed to create a "Hello World!" example, generate its WSD and release the Web Service. Now, in transaction "WSADMIN," it shows my Web service as:
    > Z_HW_WSD
      - My HW WSD  default_host/sap/bc/srt/rfc/sap/Z_HW_WSD
    Here is what I do next:
    1. Select "My HW WSD" and click on "Web Services Homepage" icon.
    2. Check "Include SAP Features in WSDL" and "Document Style." Hit OK.
    I get the same error: "Setting for J2EE Server do not exist."
    When I click on the error to get help, the message number I get is SRT_REG042. Diagnosis: The J2EE Server provides the Web Service Home Page with test functions. To use these test functions, the address of the J2EE server must be defined. This can be done from transaction WSADMIN to define the addresss.
    I followed the instructions and chose Goto->Administrative Settings. However, I don't know what to put in for J2EE server (especially given that I don't think I chose to install J2EE server). For testing, I tried putting http://localhost:8000. However, now I get a different error - could not determine WSDL address (ICF_ERROR).
    I appreciate any advise you may have.
    Thank you,
    Pradeep

  • Calling a Web Service from J2EE application running on WebSphere

    This may have been answered before, but could not find using multiple searches that I did on this forum.
    We are just in the process of using the newly installed SAP WAS 6.40 with J2EE engine and I understand from SAP's documentation that all BAPIs and remotely callable RFCs should be invokable via a Web Service call from remote applications. Couple of questions on this:
    1. Is there a documentaion that describes steps to enable BAPIs or RFCs as web services?
    2. Is there a documentation that describes steps to invoke a web service that in turn uses BAPI or RFC (code sample).
    We are J2EE literates but not familiar with SAP WAS, and not sure if calling/invoking the WS would be similar to calling any other WS from other WS Containers.
    Appreciate a response or suggestions.

    Hi Bharat,
    see this weblog , where it gives the steps to create a RFC and convert it into web service.
    /people/thomas.jung3/blog/2005/01/05/develop-a-web-service-that-sends-an-email--in-abap
    Invoking WS is similar to calling any other WS from other containers. Either you have to give the WSDL file location or the external UDDI Server address in WebService creation wizard.
    The WebService exapmles is also avaliable in help.sap.com

  • (Basis)Unable to start some XI services in the J2EE Engine

    Hello,
    Our XI system was up & running Fine, however suddenly the
    J2EE engine  is unable to start some XI services like XI.Repository,XI directory,
    XI RWB etc .. However the Adapter Framework services are up & running fine .
    The Application startup fails to start even when we manually start through Visual
    Admin tool . (cluster ->server->services->Deploy) .
    We had many times stopped & started the J2EE Engine also . ABAP Stack works fine .
    We get the Class not found exception error .
    Start application
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/UploadService.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/MapServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/CrossTransport.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepSpecMiscServicesBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/ConnTestServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepLoginServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepObjectAccessBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepObjectAccessBeanSwcv.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepHmiBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepPvcMigrationBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepDiagBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepQueryServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepRoaBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepTransformationServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepEOAServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepTransportServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepChangeListMgmtBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepConflictResolutionBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepPrintViewServiceBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepMiscServicesBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepVersionHistoryBean.
    Warning occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : ORB is not bound in JNDI. It is impossible to lookup org.omg.CORBA.ORB from EJBean sap.com/com.sap.xi.repository/RepAuthorizationBean.
    Error occurred on server 9573750 during startApp sap.com/com.sap.xi.repository : com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error in starting application [sap.com/com.sap.xi.repository].
         at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:118)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainer.prepareStart(WebContainer.java:398)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:89)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:233)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.servlets_jsp.server.exceptions.WebDeploymentException: Error while deploying web application [rep].
         at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.init(ApplicationContext.java:630)
         at com.sap.engine.services.servlets_jsp.server.container.WebContainerHelper.createContext(WebContainerHelper.java:540)
         at com.sap.engine.services.servlets_jsp.server.container.StartAction.prepareStart(StartAction.java:51)
         ... 10 more
    Caused by: org.omg.CORBA.INITIALIZE: can't instantiate default ORB implementation com.sun.enterprise.iiop.POAEJBORB  vmcid: 0x0  minor code: 0  completed: No
         at org.omg.CORBA.ORB.create_impl(ORB.java:297)
         at org.omg.CORBA.ORB.init(ORB.java:336)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.WebApplicationConfig.parse(WebApplicationConfig.java:116)
         at com.sap.engine.services.servlets_jsp.server.runtime.context.ApplicationContext.init(ApplicationContext.java:617)
         ... 12 more
    Caused by: java.lang.ClassNotFoundException: com.sun.enterprise.iiop.POAEJBORB
    Loader Info -
    ClassLoader name: [sap.com/com.sap.xi.repository]
    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
       interface:resourcecontext_api
       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:webservices
       interface:cross
       interface:ejbserialization
       library:tc~jmx
       library:opensqlextensions
       service:applocking
       interface:keystore_api
       library:com.sap.exception
       library:com.sap.guid
       library:sapxmltoolkit
       library:com.sap.tc.Logging
       library:com.sap.mw.jco
       library:com.sap.mdi
       library:com.sap.lcr.api.cimclient
       library:com.sap.rprof.dbprofiles
       library:compilation_lib
       service:tcsecsecurestorage~service
       library:tci18ns2x
       library:com.sap.xi.jnlp.servlet
       library:com.sap.util.monitor.jarm
       sap.com/com.sap.aii.security.ws.proxy
       service:tcsecwssec~service
       library:tc.httpclient
       library:tcSLCMS~IDEClient
       library:tcSLCMS~Util
       library:com.sapportals.htmlb
       service:com.sap.aii.af.svc
       library:tcsldsldclient_sda
    Resources:
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ib_core.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_map_api.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\sap.comtcdtrcsimpl.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ibrep_core.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\sap.comtcdtrutilbasic~impl.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ib_rb.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_xml.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\EJBContainer\clientjars\clientaii_ibrep_sbeans.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ib_server.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\EJBContainer\applicationjars\aii_ib_sbeans.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_rb.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_mt_rb.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ibrep_rb.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_utilxi_misc.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\EJBContainer\applicationjars\aii_ibrep_sbeans.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_cimaccess.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\sap.comtcdtrpvcimpl.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\sap.comtcdtrutilimpl.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\servlet_jsp\rep\work
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_upload_sap.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_ibrep_server.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_sql.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_mt_rt.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\EJBContainer\clientjars\clientaii_ib_sbeans.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_upload_core.jar
       C:\usr\sap\XI3\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.xi.repository\aii_util_xsd.jar
    Loading model: {parent,references,local}
         at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:219)
         at org.omg.CORBA.ORB.create_impl(ORB.java:295)
         ... 15 more
    We had referered to notes 803145 & 753567 , but could find much help .
    Please Help .
    Regards
    Kumar

    Hi
    Refer to the link
    See the troble shooting guide
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
    Regards,
    Kumar

  • How to refer to J2EE library server component from a web service?

    Hi,
    I need help!  I created a web service and it worked fine.  However, I started having problems when I tried to use java classes from my deployable J2EE library server component.  I got the NoClassDefFound error.
    I tried to include the library DC in the Used DC list and put the reference of it in the web service deployment descriptor xml (application.xml and application-j2ee-engine.xml), but it did not work.
    How do I refer and use java classes from my deployable J2EE library at run time from my web service application?  What should I do?
    Thanks,
    Giavinh Pham

    I would like to clarify more about the web service project.  I created a Java DC project and converted it into a web service as the SAP manual instructions.  It worked fine by itself, but I now want to use some of my classes that I deployed as a J2EE library server component. 
    It was compiled and built when I refer to my J2EE library server component DC in the UsedDC.  It was deployed fine as well.  However, it broke when I tested the web service calls.  The class declarations and usage from the J2EE server component could not be found (NoClassDefFound error.) 
    I thought it was because I did not have an application-j2ee-engine.xml in my META-INF folder so I created one and referred to the library in xml as type library and reference 'strong'.  I built and deployed again.  It still did not work. 
    I examined the EAR and noticed that there were two parts of the EAR.  One is the WSAR archive file that contains the META-INF folder from my project and other web service assemblies.  The other part is the META-INF folder generated by the SAP NetWeaver IDE. 
    The strange thing was that SAP NetWeaver IDE generated an application-j2ee-engine.xml without any reference to my J2EE library server component.  However, the nested application-j2ee-engine.xml in the WSAR archive file did contain the info. 
    Since I cannot control the application-j2ee-engine.xml generated by SAP NetWeaver IDE, what should I do?  Is it the cause for my problem?
    Please advice, anyone?
    Giavinh

  • J2EE engine was always down when I accessed it in the web browser!

    Hi,gurus:
    Having installed netweaver 7.0 SR3 and made the post-installation of xi with nwa, I accessed the j2ee engine with the URL "http://<hostname>:50100/sld or http://<hostname>:50100/irj".Sometimes the webpage could be accessed,but other times the webpage was blank,and after I refreshed the webpage again,it displayed the error like "503 service unavailable".Then I found the color of disp+work.exe and server0 in MMC was yellow.After several minutes,it turned green again.Then I could access the j2ee engine successfully.However,it stopped again after I accessed some webpages.
    This problem has embarassed me several weeks,could you help me?Any help would be appreciated,tks in advance.
    I picked up some related message which may be helpful to resolve the problem:
    *defaultTrace0.trc: *
    1.Cannot lock configuration;it is already locked.
    Caused by :com.sap...LockException:.........J2EE_CONFIGURATION_MANAGER.....it is in use by another owner.The lock collision occurred with user <internal>
    2.java.security.keyStoreException: cannot get root keystore view configuration; A configuration with the path "keystore" does not exist.
    dev_server0.xml:*
    1.com.sap.secruity.api.NoSuchRoleException:Role with uniqueName system_admin_role not found!
    com.sap.secruity.api.NoSuchRoleException:Role with uniqueName content_admin_role not found! 2.com.sap.security.api.NoSuchGroupException:Group "Administrators" does not exist.
    3.password logon no longer possible - too many failed attempts.

    Hi,
    Please have a look at this below snote which is actually a
    correction note for sp14 sap web as java 7.0
    1020365
    Could find below information within the same.
    Locking
    - Configuration Editor does not close files after upload, i.e. those files cannot be deleted unless the Configuration Editor was closed.
    which may correspond to you below problem
    1.Cannot lock configuration;it is already locked.
    Caused by :com.sap...LockException:.........J2EE_CONFIGURATION_MANAGER.....it is in use by another owner.The lock collision occurred with user <internal>
    I hope this will help you out.
    Rgds
    Radhakrishna D S

  • Web service via integration engine - integration directory tasks

    Hello,
    I am new to PI and need help concerning the configuration of web service communication. A new enterprise service shall be exposed to the web. So, service provider is an ABAP AS, consumer is a unknown 3rd party system. Communication should be via the integration server. I have created the data types, message types, interface (query/response) in the enterprise service repository, and the proxy and proxy class in the backend.The corresponding client is already defined as a business system in the integration directory. There are also communication channels of type xi assigned to that business system. I am not sure about the next steps. My assumption:
    1) create the 3rd party system as a business component
    2) add the new interface to the receiver/sender (where?) tabs of the business component
    3) create a communication channel of type SOA and assign it to the new business component  (to receiver or sender?)
    4) ...enough for now
    Probably I forgot something important, but I am not sure... I appreciate any help.
    KR
    Felix

    Here my own "answer" after trying several things.
    The reason for the errors above are the namespaces. My incoming message contains some external namespaces which disturb the Integration Engine SOAP processing, but not the J2EE SOAP Adapter.
    So I skipped the IE SOAP way, receive the SOAP data via plain HTTP adapter, and remove the SOAP header data in an XSL-Mapping. This gave also some trouble with the namespaces, but after some adaptions finally works fine now.
    CSY

  • Adding servlet entry in web.xml of j2ee engine

    Hi ,
    I want a servlet to be loaded on startup of the j2ee engine SAP WAS which is basically flex based (MessageBrokerServlet). 
    The init param for the servlet is not accessible or cannot be initialized in init method of the servlet using the servletconfig object.
    This is when the servlet is used as a portal component of type servlet.
    So as to load the servlet and the servlet being able to access the init param i would be changing the web.xml of the sap j2ee engine (NW CE 7.1). are there any other effects of the same or is it fine if i just add this param in the web.xml
        <servlet>
            <servlet-name>MessageBrokerServlet</servlet-name>
            <display-name>MessageBrokerServlet</display-name>
            <servlet-class>flex.messaging.MessageBrokerServlet</servlet-class>
            <init-param>
                <param-name>services.configuration.file</param-name>
                <param-value>/WEB-INF/flex/services-config.xml</param-value>
           </init-param>
            <load-on-startup>1</load-on-startup>
        </servlet>

    Hi ,
    Vivek in case my servlet is part of the Portal Application as PortalComponent how do i define init parameters  that can be accessed in the servlet.
    The config file would be accessed in the init method of the servlet how do i do that when the servlet is added as PortalComponent in PortalApplication. The servlet config file needs to accessed in t he init method.
    The load on startup thing would be taken care of by setting parameter startup = true of application properties.
    Regards
    Srikumar V

  • Timeout error at J2EE Web Service client

    i have a .NET web service. a J2EE web service client deployed on Websphere application server 5.1 is invoking it. some services on .NET end take a long time to return a value. in such cases, the following error occurs on J2EE end. please suggest a solution.
    faultCode: Server.generalException
    faultString: java.net.SocketTimeoutException: Read timed out
    faultActor: null
    faultDetail:
    java.net.SocketTimeoutException: Read timed out
    at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:150)
    at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:200)
    at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:212)
    at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:255)
    at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:685)
    at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:611)
    at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:441)
    at com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.java:662)

    Hi, am also getting time out .. excepiton in client
    i added the following code inside stub class constructer...
    System.out.println("GET TIME OUT ::::"+super.getTimeout());
    super.setTimeout(77777);
    System.out.println("GET TIME OUT AFTER SET::"+super.getTimeout());
    compilation success. However am getting runtime exception after the sop.
    GET TIME OUT ::::0
    javax.xml.rpc.ServiceException: WSWS5014E: Error instantiating generated Stub class.
    can you please tell me how u solved the issue.
    Thanks
    Bogi

  • J2EE Engine - Restart necessary after changing web.xml?

    Hi people,
    do I have to restart the whole J2EE Engine after changing the <max-sessions> parameter of my J2EE-App? Or is a restart of the app via the deploy service also sufficient?
    This parameter change is done in web.xml on 620 and web-j2ee-engine.xml in 640.
    Thanks!
    Bjoern
    Message was edited by: Bjoern Altmannsberger

    restart only the application via deploy service
    regards,
    Violeta

Maybe you are looking for