Deployment of J2EE appln

Hi,
I developed a small j2ee appln. But when I tried to deploy the .ear file in to WebAS, it is asking SDM passowrd. Can anybody help me by telling why it is so and what is the soln.

Hi Prajesh,
Are you able to login to Visual Administrator.
Open the following file with wordpad(Take a copy of the file and proceed)
\usr\sap\<SID>\DVEBMGS20\SDM\program\config\sdmrepository.sdc. Find for "PW". which will go to the <PW>XXXXXX</PW>(where XXXXXX is the password). Check XXXXXX is the correct password or not. if not, type the password in <PW> </PW>. Now try to connect. Give the password that you had given while installation. 
regards
Anand.M

Similar Messages

  • 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.

  • Trouble deploying a J2EE application using the J2EE 6.20 Deploy Tool

    I am having trouble deploying a J2EE application using the J2EE 6.20 Deploy Tool.
    I successfully create the WAR/EAR files, I then select deploy and the deploy process gets to 100% before displaying an error message.
    Can anybody help?
    Please see Deploy Tool log entry:
    01:39 -  **********************************************************
    05/01/17 10:19:16 -  Applying user role management mappings.
    05/01/17 10:19:16 -  Start updating EAR-file...D:\SAP_J2EEngine6.20_Cluster\deploying\carmodeller\carmodeller.ear
    05/01/17 10:19:27 -  Temp files deleted...
    05/01/17 10:19:27 -  Ear-file updated successfully for 11375ms.
    05/01/17 10:19:27 -  Start deploying ...
    05/01/17 10:20:15 -  Ear-file uploaded to server for 47297ms.
    05/01/17 10:21:47 -  ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
                         com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
                              at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.deploy(ServletsAndJspImpl.java:482)
                              at com.inqmy.services.servlets_jsp.server.WebContainer.commitDeploy(WebContainer.java:256)
                              at com.inqmy.services.deploy.server.DeployServiceImpl.commit(DeployServiceImpl.java:2848)
                              at com.inqmy.services.deploy.server.DeployServiceImpl.deploy1(DeployServiceImpl.java:512)
                              at com.inqmy.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:140)
                              at com.inqmy.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:184)
                              at com.inqmy.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:157)
                              at com.inqmy.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:108)
                              at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
                              at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
                              at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:153)
    05/01/17 10:21:47 -  **********************************************************

    Hi, it looks like the app has trouble starting up:
    05/01/17 10:21:47 - ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
    com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
    Did you have any errors on the compile of the code?
    You also want to check if the app is deployed (if so you may want to remove it before re-deploying it)

  • Stateless bean giving error when deployed through j2ee 1.3RI

    I have written a simple stateless bean and deployed through j2ee 1.3 RI
    Context initial = new InitialContext(h);
    Object obj = initial.lookup("SampleObject"); // SampleObject -jndi name
    SampleHome home = (SampleHome)PortableRemoteObject.narrow(obj, SampleHome.class);
    But when running the Client , getting the error
    java.lang.ClassCastException
    at com.sun.corba.se.internal.javax.rmi.PoartableRemoteObject.narrow(Unknown Source)
    at javax.rmi.PortableRemoteObject.narrow(Unknown Source)     at SampleClient.main(SampleClient.java:27)
    Is it a system error or what

    Hi sessionbean,
    The most common cause of this exception is when the RMI-IIOP stubs are not found within the client's classpath. The client stubs are returned from the deployment step.
    Also, it's better to use the no-arg initial context constructor "new InitialContext()" and let the J2EE 1.3 RI code bootstrap the correct naming service.
    --ken                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Deploy a web service with the deploy tool (J2EE)

    Hi!
    I want to deploy a web service with the Deploy Tool (J2EE 1.4).
    (For info, I'm working on Win 2000.)
    I have the following error when I'm trying to deploy:
    distribute: C:\monHello2\monApp.ear
    Deploy action running...
    Deployment failed on target localhost:4848_server : Fatal Error from EJB Compiler -- jaxrpc compilation exception
    !!! Operation Failed !!!
    Someone can help me, please? What's the problem?
    Other question: when I create the WAR file, I have to add : my interface class, my implementation class, my others java classes, my WSDL file and my mapping.xml file.
    Should I add the .jar that is used by one of my class???? I think yes, but...
    thank you and excuse me for my english... ;o)

    Only primitive types can be returned? Is thatcorrect????
    true - for more details check out section 3.4.1.3 of
    this book which is available for purchase or online
    http://java.sun.com/blueprints/guidelines/designing_w
    ebservices/I meant to say primitive type and "special POJOs" called "JAXRPC Value Types" - check out the reference I listed

  • 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

  • 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

  • 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

  • EJB Deployment in J2EE Apps Server

    Hi,
    Can any one please help me in deploying EJB in J2EE Apps server?I have installed J2EE Apps Server 9 in my machine.Can any one please suggest me a document regarding EJB deployment in J2EE apps server or help me regarding this?
    Thanks in advance,
    Aravindhan.C

    Go to https://j2ee-sdk.dev.java.net/ and checkout "Methods of deploying applications" under the recent articles section; The tutorial link present in this page (under the references section) will also be useful. The samples bundle has reference samples which will also be useful

  • Deploying a J2EE web application in Oracle 10g

    Hi friends,
    <br>
    I had worked with Oracle9i 9.0.3 . But it's my first experience with Oracle 10g . I have installed Oracle 10g Infrastructure , Metadata Repository and one Middle tier - Forms and i hope i have followed The Oracle 10g installation guide Properly. Anyway installation is successful.
    The problem is a J2EE web application which is deployed properly on Oracle9i 9.0.3 doesn't get deployed in Oracle 10g. The following is the exception :
    <br>
    Deployment failed: Nested exception
    Root Cause: deploy failed!: ; nested exception is:
    oracle.oc4j.admin.internal.DeployerException: Error initializing ejb-module; Exception Error in application Spom_Apps: Error loading package at file:/C:/Oracle/Ora9iASForms/j2ee/home/applications/Spom_Apps/JmsSubscriberMdb.jar, Error deploying file:/C:/Oracle/Ora9iASForms/j2ee/home/applications/Spom_Apps/JmsSubscriberMdb.jar homes: No location set for Topic resource MessageDrivenBean JmsReceiverMdb
    <br>
    <br>
    where JmsReceiverMdb is the deployment file containing the message driven beans.
    <br>
    Thanks in advance,
    paskal

    Hi,
    Thanks for responding . I am sending the file contents of ejb-jar.xml, orion-ejb-jar.xml, jms.xml.
    Could you also check whether dtds versions of 10g and 9i in these xmls are conflicting? If you can specify your email-id i can send these file as attachments.
    Hope you could strike the right spot.
    ejb-jar.xml
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <enterprise-beans>
    <session>
    <description>Session Bean ( Stateless )</description>
    <display-name>spomPmConfigSSB</display-name>
    <ejb-name>spomPmConfigSSB</ejb-name>
    <home>jnipackage.spomPmConfigSSBHome</home>
    <remote>jnipackage.spomPmConfigSSB</remote>
    <ejb-class>jnipackage.impl.spomPmConfigSSBBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    <message-driven>
    <description>Message Driven Bean</description>
    <display-name>JmsReceiverMdb</display-name>
    <ejb-name>JmsReceiverMdb</ejb-name>
    <ejb-class>jnipackage.impl.JmsReceiverMdbBean</ejb-class>
    <transaction-type>Container</transaction-type>
    <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
    <resource-ref>
    <res-ref-name>jms/alarmTopicConnectionFactory</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    <res-sharing-scope>Shareable</res-sharing-scope>
    </resource-ref>
    <resource-env-ref>
    <resource-env-ref-name>jms/alarmTopic</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
    </resource-env-ref>
    </message-driven>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>JmsReceiverMdb</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>spomPmConfigSSB</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Supports</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    Orion-ejb-jar.xml
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
    <orion-ejb-jar>
    <enterprise-beans>
    <message-driven-deployment name="JmsReceiverMdb" max-instances="100" min-instances="0">
    <resource-ref-mapping name="jms/alarmTopicConnectionFactory"/>
    </message-driven-deployment>
    <session-deployment name="spomPmConfigSSB"/>
    </enterprise-beans>
    <assembly-descriptor>
    <default-method-access>
    <security-role-mapping impliesAll="true" name="&lt;default-ejb-caller-role>"/>
    </default-method-access>
    </assembly-descriptor>
    </orion-ejb-jar>
    jms.xml
    <?xml version="1.0" standalone='yes'?>
    <!DOCTYPE jms-server PUBLIC "OC4J JMS server" "http://xmlns.oracle.com/ias/dtds/jms-server-9_04.dtd">
    <jms-server port="9127">
    <!-- Queue bindings, these queues will be bound to their respective
    JNDI path for later retrieval -->
    <queue name="Demo Queue" location="jms/demoQueue">
    <description>A dummy queue</description>
    </queue>
    <!-- Topic bindings, these topic will be bound to their respective
    JNDI path for later retrieval -->
    <topic name="Demo Topic" location="jms/demoTopic">
    <description>A dummy topic</description>
    </topic>
    <!-- Topic bindings, these topic will be bound to their respective
    JNDI path for later retrieval -->
    <topic name="AlarmQueue" location="jms/alarmTopic">
    <description>A topic</description>
    </topic>
    <topic name="FaultTextQueue" location="jms/faultTextTopic">
    <description>A topic</description>
    </topic>
    <topic name="FaultTopologyQueue" location="jms/faultTopologyTopic">
    <description>A topic</description>
    </topic>
    <!-- path to the log-file where JMS-events/errors are stored -->
    <log>
    <file path="../log/jms.log"/>
    <!-- Uncomment this if you want to use ODL logging capabilities
    <odl path="../log/jms/" max-file-size="1000" max-directory-size="10000"/>
    -->
    </log>
    <queue name="jms/OracleSyndicateQueue" location="jms/OracleSyndicateQueue">
    <description>Oracle Syndication Services Queue</description>
    </queue>
    <!--
    <queue-connection-factory name="jms/OracleSyndicateQueueConnectionFactory"
    location="jms/OracleSyndicateQueueConnectionFactory"/>
    -->
    <queue-connection-factory location="jms/OracleSyndicateQueueConnectionFactory"/>
    <queue name="jms/OracleUddiReplicationQueue"
    location="jms/OracleUddiReplicationQueue">
    <description>Queue for replication scheduler</description>
    </queue>
    <!--
    <queue-connection-factory
    name="jms/OracleUddiReplicationQueueConnectionFactory"
    location="jms/OracleUddiReplicationQueueConnectionFactory"/>
    -->
    <queue-connection-factory location="jms/OracleUddiReplicationQueueConnectionFactory"/>
    <queue name="jms/OracleWebClippingQueue"
    location="jms/OracleWebClippingQueue">
    <description>Queue for Web Clipping</description>
    </queue>
    <!--
    <queue-connection-factory
    name="jms/OracleWebClippingQueueConnectionFactory"
    location="jms/OracleWebClippingQueueConnectionFactory"/>
    -->
    <queue-connection-factory location="jms/OracleWebClippingQueueConnectionFactory"/>
    </jms-server>

  • 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.

  • Error in using Jaxm provider deployed in j2ee 1.3.1 (RI)

    We were able to successfully deploy/test all JWSDP v1.0 samples into the
    J2ee 1.3.1 (RI) in preparation for our next projects.
    We have problems, however, in deploying the JAXM-provider and
    JAXM-providerAdmin samples. Please, help us.
    We followed the procedures defined in your article; we even re-deployed the
    same war files that came out of running jwsdponj2ee.bat.
    We always get the same errors. We even switch back and forth the port for
    webservices in our desperation; but to no avail. THe scenarion went like this:
    After deployment of the modified jaxm-provider.war and
    jaxm-provideradmin.war, we then point our browser to
    http://127.0.0.1:8080/jaxm-provideradmin. We then enter "j2ee" as user and
    password. So, far so good and we get to the next page that has the frame
    (http://127.0.0.1:8080/jaxm-provideradmin/index.jsp). So far so good at this
    point. But when we click on the "HTTP" icon under ebXML profile, we get some of
    these error messages:
    "Internal server error"
    javax.servlet.ServletException
         at
    org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:463)
         at org.apache.jsp.ebxml_0005fhttp$jsp._jspService(ebxml_0005fhttp$jsp.java:941)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at
    org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    root cause
    java.lang.NoClassDefFoundError
         at org.apache.jsp.ebxml_0005fhttp$jsp._jspService(ebxml_0005fhttp$jsp.java:149)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at
    org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    And if we click on the "HTTP" icon of SOAPRP, we get these messages:
    Internal Server Error
    javax.servlet.ServletException
         at
    org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:463)
         at
    org.apache.jsp.soaprp_0005fhttp$jsp._jspService(soaprp_0005fhttp$jsp.java:941)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    Root Cause
    java.lang.NoClassDefFoundError
         at
    org.apache.jsp.soaprp_0005fhttp$jsp._jspService(soaprp_0005fhttp$jsp.java:149)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    Although our setup of J2EE 1.3.1 (R.I.) is able to successfully run all the
    other JWSDP v1.0 Samples, we are obviously missing something in deploying the
    JAXM-provider and provider admin samples.
    Any ideas to help us, Please...
    Thanks in advance for your possible time and effort....
    adler

    I was really hoping someone could/would answer your question, I have having the exact same issues. After looking through release notes for J2SE 1.4.0_01, J2EE 1.3.1, and JWSDP 1.0, the only thing I can come up with is that there is a conflict between the JAXM version that the JWSDP installer and the XML packages included with J2SE. This is purely conjecture, but it's all I have to go on right now. If you figure out or find the solution please post it.
    Thanks,
    tc

  • Problem deploying web service with the deploy tool (J2EE)

    Hello,
    I am trying to deploy a sample Web Service on the Sun Java System Application Server Platform Edition 8.1 2005Q1.
    I run into a deployment problem ("jaxrpc compilation exception") when I have one of the web methods declared (in the endpoint interface) to throw a service-specific exception. The problem disappears when I change the declaration to throw an Exception.
    Here is the exception class:
    public class StockNotFoundException extends Exception {
    private String message;
    public StockNotFoundException(String message) {
    super(message);
    this.message = message;
    public String getMessage() {
    return message;
    the endpoint interface:
    public interface StockServiceIF extends Remote {
    // the service methods
    public boolean sellStocks(String ticker, int quantity)
    throws RemoteException, StockNotFoundException;
    and here are the error messages I am seeing:
    in the deploy tool dialog:
    distribute: C:\Beginning J2EE 1.4\Ch13\StockServiceApp\StockServiceApp.ear
    deployment started : 0%
    Deploying application in domain failed; Fatal Error from EJB Compiler -- jaxrpc compilation exception
    ; requested operation cannot be completed
    !!! Operation Failed !!!
    !!! With The Following Failure Messages !!!
    Deploying application in domain failed; Fatal Error from EJB Compiler -- jaxrpc compilation exception
    ; requested operation cannot be completed
    Fatal Error from EJB Compiler -- jaxrpc compilation exception
    and in the server log:
    [#|2005-02-01T18:30:47.856-0600|INFO|sun-appserver-pe8.1|javax.enterprise.system.tools.deployment|_ThreadID=12;|DPL5109: EJBC - START of EJBC for [StockServiceApp]|#]
    [#|2005-02-01T18:30:47.856-0600|INFO|sun-appserver-pe8.1|javax.enterprise.system.tools.deployment|_ThreadID=12;|Processing beans ...|#]
    [#|2005-02-01T18:30:47.936-0600|INFO|sun-appserver-pe8.1|javax.enterprise.system.stream.out|_ThreadID=12;|
    error: incorrect fault part name for fault "StockNotFoundException" of operation "sellStocks": "StockNotFoundException"|#]
    [#|2005-02-01T18:30:47.966-0600|INFO|sun-appserver-pe8.1|javax.enterprise.system.tools.deployment|_ThreadID=12;|Total Deployment Time: 1001 msec, Total EJB Compiler Module Time: 0 msec, Portion spent EJB Compiling: 0%|#]
    [#|2005-02-01T18:30:47.966-0600|SEVERE|sun-appserver-pe8.1|javax.enterprise.system.tools.deployment|_ThreadID=12;|Exception occured in J2EEC Phase
    com.sun.enterprise.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- jaxrpc compilation exception
         at com.sun.enterprise.webservice.codegen.JaxRpcRICodegen.accept(JaxRpcRICodegen.java:206)
         at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:584)
         at com.sun.enterprise.deployment.Application.visit(Application.java:1333)
         at com.sun.enterprise.webservice.codegen.JaxRpcRICodegen.run(JaxRpcRICodegen.java:103)
         at com.sun.ejb.codegen.IASEJBC.doCompile(IASEJBC.java:785)
         at com.sun.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:563)
         at com.sun.enterprise.deployment.backend.EJBCompiler.preDeployApp(EJBCompiler.java:340)
         at com.sun.enterprise.deployment.backend.EJBCompiler.compile(EJBCompiler.java:209)
         at com.sun.enterprise.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:284)
         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:176)
         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:107)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:146)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:633)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:188)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:520)
         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:143)
         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:171)
    |#]
    I would appreciate any pointers to resolving this issue.
    Thanks,
    Satyen

    Can you post the WSDL that was generated by the tool
    for this interface ?I generate the WSDL using "wscompile -define -nd . -classpath ..\build\classes -f:wsi service-config.xml", and here it is:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="StockService" targetNamespace="urn:stockService" xmlns:tns="urn:stockService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <types>
    <schema targetNamespace="urn:stockService" xmlns:tns="urn:stockService" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
    <complexType name="StockNotFoundException">
    <sequence>
    <element name="message" type="string" nillable="true"/></sequence></complexType>
    <element name="StockNotFoundException" type="tns:StockNotFoundException"/></schema></types>
    <message name="StockServiceIF_sellStocks">
    <part name="String_1" type="xsd:string"/>
    <part name="int_2" type="xsd:int"/></message>
    <message name="StockServiceIF_sellStocksResponse">
    <part name="result" type="xsd:boolean"/></message>
    <message name="StockNotFoundException">
    <part name="StockNotFoundException" element="tns:StockNotFoundException"/></message>
    <portType name="StockServiceIF">
    <operation name="sellStocks" parameterOrder="String_1 int_2">
    <input message="tns:StockServiceIF_sellStocks"/>
    <output message="tns:StockServiceIF_sellStocksResponse"/>
    <fault name="StockNotFoundException" message="tns:StockNotFoundException"/></operation></portType>
    <binding name="StockServiceIFBinding" type="tns:StockServiceIF">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
    <operation name="sellStocks">
    <soap:operation soapAction=""/>
    <input>
    <soap:body use="literal" namespace="urn:stockService"/></input>
    <output>
    <soap:body use="literal" namespace="urn:stockService"/></output>
    <fault name="StockNotFoundException">
    <soap:fault name="StockNotFoundException" use="literal"/></fault></operation></binding>
    <service name="StockService">
    <port name="StockServiceIFPort" binding="tns:StockServiceIFBinding">
    <soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
    ---------------------------------------------------------------------------------------------------------

  • 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

  • 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

Maybe you are looking for