Utils folder in BEA WebLogic

          Folks,
          When I install weblogic in machine, it has a folder called /utils under /bea folder
          with bsu.jar,appboot.jar etc...I don't think, we are using these .jar's anywhere.
          Anyone can help me to understand the /utils folder?
          Thanks
          - Spider
          

I dealt with this a couple of years ago when I was using BEA Weblogic 5.1.
WLS 5.1 didn't come with native XML Parsers at the time, and the ones that
Sun produced "blew chunks."
You can download the latest xerces and xalan open source parsers and use
them in WLS 5.1. All you have to do is get the classpath correct, and that
might be a little challenging.
I don't remember how I adjusted the classpath, I think it was ok to put the
path to the XML parsers at the end ... this will be trial and error. But,
once you adjust the classpath correctly, you'll be able to have to have your
EJB's, JSP's, and Servlets utilizing XML.
Hope this helps.
Tom
"Alvin" <[email protected]> wrote in message
news:3d6de299$[email protected]..
>
Hi,
I'm currently using BEA Weblogic 5.1. Is it possible to use XML with sucha version?
How? Do I just download the necessary APIs and put in my own applicationdirectory
to use the XML parser?
Thanks for any help.
Regards,
Alvin

Similar Messages

  • How to install Oracle BPEL Process Manager with the BEA WebLogic

    Hi ,
    I will install Oracle BPEL Process Manager with BEA WebLogic 9.2(MP2). I have download orabpel_10133_WebLogic.zip ,then Modify the following mandatory installation properties in the orabpel_10133_WebLogic\bpelDomain.properties file:
    # BEA_HOME is the path where Weblogic is Installed
    BEA_HOME=/opt/bea
    # JAVA_HOME is the path of jdk folder inside your weblogic
    JAVA_HOME=/opt/bea/jrockit90_150_10
    # DOMAIN_HOME is the path where you wish to create your domain called BPELDomain
    DOMAIN_HOME=/opt/bea/user_projects/domains
    # APPS_HOME is the path where you wish to copy your applications and adapters that are required for oracleBPELServer
    APPS_HOME=/opt/bea/user_projects/apps
    # BEA_HOME is the path where BPEL PM is Installed
    BPEL_HOME=/home/oracle/bpel/product/10.1.3.1/OraBPEL_1/bpel
    # DRIVER_TYPE is the datasource class that installable use to create a datasources for oracleBPELServer
    DRIVER_TYPE=oracle.jdbc.xa.client.OracleXADataSource
    # DB_URL is the url to connect to orabpel schema
    DB_URL=jdbc:oracle:thin:@16.157.134.17:1521:orcl
    # DB_USER is the user Id for orabpel shema in database
    DB_USER=ORABPEL
    #DB_PASSWORD is the password for orabpel schema in database
    DB_PASSWORD=bpel
    #BPEL_SERVER_NAME is the server i.e. to be created under BPELDomain
    BPEL_SERVER_NAME=oracleBPELServer
    #PROXY_HOST is the Host name of the proxy server
    PROXY_HOST=www-proxy.us.oracle.com
    #PROXY_HOST=
    #PROXY_PORT is the Port where the proxy server is running
    PROXY_PORT=80
    #PROXY_PORT=
    #NON_PROXY_HOST is the list of non proxy hosts that are divided by a | symbol
    #NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com
    NON_PROXY_HOST=*.oracle.com|*.oraclecorp.com|localhost|127.0.0.1|stbbn10|stbbn10.us.oracle.com|16.157.134.135
    When I run the setup.sh , it will report
    BUILD FAILED
    /opt/software/WL_Installables/build.xml:131: Traceback (innermost last):
    File "./wl_scripts/bpelDomain.py", line 22, in ?
    File "./wl_scripts/createGroupsAndUsers.py", line 4, in ?
    weblogic.management.utils.AlreadyExistsException: [Security:090267]Group BpelGroup
    Actully ,there is no BpelGroup in Weblogic. Does anybody know how to solve it ?

    MAke sure you have not set ANY environment variable related to Oracle / BEA / Java / LD_library path. Use the following script to unset / set the initial settings:
    #!/bin/sh
    unset ORACLE_BASE ORACLE_HOME ORACLE_SID ORACLE_TERM
    unset LD_LIBRARY_PATH LD_LIBRARY_PATH_64
    unset CLASSPATH JAVA_HOME
    export PATH=.:/usr/sbin:/usr/bin:/usr/local/bin:/opt/VRTS/bin
    export BEA_HOME=/appl/oracle/products/9.2/weblogic
    Marc
    http://orasoa.blogspot.com

  • Problem in calling a web service hosted on tomcat from BEA WebLogic portal

    Hi,
    I have a wsdl file for my web service which is hosted on apache tomcat 5.5(running on port : 8080). The contents of the wsdl file are-
    *<?xml version="1.0" encoding="UTF-8"?>*
    *<wsdl:definitions targetNamespace="http://soa.tutorials.serg.edu" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://soa.tutorials.serg.edu" xmlns:intf="http://soa.tutorials.serg.edu" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">*
    *<!--WSDL created by Apache Axis version: 1.4*
    Built on Apr 22, 2006 (06:55:48 PDT)-->
    *<wsdl:types>*
    *<schema elementFormDefault="qualified" targetNamespace="http://soa.tutorials.serg.edu" xmlns="http://www.w3.org/2001/XMLSchema">*
    *<element name="getNums">*
    *<complexType>*
    *<sequence>*
    *<element name="n" type="xsd:int"/>*
    *<element name="m" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNumsResponse">*
    *<complexType>*
    *<sequence>*
    *<element maxOccurs="unbounded" name="getNumsReturn" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNums2">*
    *<complexType>*
    *<sequence>*
    *<element name="n" type="xsd:int"/>*
    *<element name="m" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *<element name="getNums2Response">*
    *<complexType>*
    *<sequence>*
    *<element maxOccurs="unbounded" name="getNums2Return" type="xsd:int"/>*
    *</sequence>*
    *</complexType>*
    *</element>*
    *</schema>*
    *</wsdl:types>*
    *<wsdl:message name="getNums2Request">*
    *<wsdl:part element="impl:getNums2" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNumsRequest">*
    *<wsdl:part element="impl:getNums" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNums2Response">*
    *<wsdl:part element="impl:getNums2Response" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:message name="getNumsResponse">*
    *<wsdl:part element="impl:getNumsResponse" name="parameters"/>*
    *</wsdl:message>*
    *<wsdl:portType name="Echo">*
    *<wsdl:operation name="getNums">*
    *<wsdl:input message="impl:getNumsRequest" name="getNumsRequest"/>*
    *<wsdl:output message="impl:getNumsResponse" name="getNumsResponse"/>*
    *</wsdl:operation>*
    *<wsdl:operation name="getNums2">*
    *<wsdl:input message="impl:getNums2Request" name="getNums2Request"/>*
    *<wsdl:output message="impl:getNums2Response" name="getNums2Response"/>*
    *</wsdl:operation>*
    *</wsdl:portType>*
    *<wsdl:binding name="EchoSoapBinding" type="impl:Echo">*
    *<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>*
    *<wsdl:operation name="getNums">*
    *<wsdlsoap:operation soapAction=""/>*
    *<wsdl:input name="getNumsRequest">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:input>*
    *<wsdl:output name="getNumsResponse">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:output>*
    *</wsdl:operation>*
    *<wsdl:operation name="getNums2">*
    *<wsdlsoap:operation soapAction=""/>*
    *<wsdl:input name="getNums2Request">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:input>*
    *<wsdl:output name="getNums2Response">*
    *<wsdlsoap:body use="literal"/>*
    *</wsdl:output>*
    *</wsdl:operation>*
    *</wsdl:binding>*
    *<wsdl:service name="EchoService">*
    *<wsdl:port binding="impl:EchoSoapBinding" name="Echo">*
    *<wsdlsoap:address location="http://localhost:8080/SOATest/services/Echo"/>*
    *</wsdl:port>*
    *</wsdl:service>*
    *</wsdl:definitions>*
    I created a client from the above wsdl file using ClientGen wizard in WebLogic. This client contains the follwoing classes-
    Echo.java
    EchoService.java
    EchoService_Impl.java
    Echo_Stub.java
    I created a JSP portlet and the jsp content of it is-
    String url = "http://localhost:8080/SOATest/services/Echo";
    Echo echo = new EchoService_Impl(url).getEcho();
    getNumsResponse = echo.getNums(getNums);
    I tried to call that web service from BEA weblogic portal through a JSP potlet. I got an error saying -
    *<An exception [javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element] was thrown while rendering the content at [TestEcho.jsp].*
    *javax.servlet.ServletException: javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.servlet.jsp.PageContextImpl.handlePageException(PageContextImpl.java:420)*
    *     at jsp_servlet.__testecho._jspService(__testecho.java:112)*
    *     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)*
    *     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)*
    *     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)*
    *     Truncated. see log file for complete stacktrace*
    *javax.xml.rpc.ServiceException: Failed to parse WSDL http://localhost:8080/SOATest/services/Echo weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:174)*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.loadWsdlDefinition(ServiceImpl.java:485)*
    *     at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:119)*
    *     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
    *     at edu.serg.tutorials.soa.EchoService_Impl.<init>(Unknown Source)*
    *     Truncated. see log file for complete stacktrace*
    *weblogic.wsee.wsdl.WsdlException: Failed to read wsdl file from url due to -- java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:313)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:391)*
    *     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:79)*
    *     at weblogic.wsee.wsdl.WsdlFactory.parse(WsdlFactory.java:66)*
    *     Truncated. see log file for complete stacktrace*
    *java.io.IOException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:38)*
    *     at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:122)*
    *     at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)*
    *     at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)*
    *     at weblogic.wsee.wsdl.WsdlDefinitions.parse(WsdlDefinitions.java:405)*
    *     Truncated. see log file for complete stacktrace*
    *javax.xml.stream.XMLStreamException: Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:206)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:73)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:35)*
    *     Truncated. see log file for complete stacktrace*
    *Error at Line:2, token:[OPENTAGBEGIN]All tags must be contained within a single element*
    *     at weblogic.xml.babel.baseparser.BaseParser.parseProlog(BaseParser.java:417)*
    *     at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:328)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:195)*
    *     at weblogic.xml.stax.XMLStreamReaderBase.next(XMLStreamReaderBase.java:237)*
    *     at weblogic.xml.domimpl.Loader.load(Loader.java:112)*
    *     Truncated. see log file for complete stacktrace*
    My web service is using soap binding. I have tested it with eclipse and other tools also. It is working well and good. But when I tried to call a web service which is created and hosted on WebLogic server(running on port : 7001), I got the correct output.
    Can anyone help me out in calling a web service hosted on different server from WebLogic server.
    Thanks in advance,
    Tiijnar
    Edited by: user8715057 on Aug 13, 2009 1:11 AM

    Hi
    1. The way you are invoking the WebService deployed on Tomcat server is looks suspicious. It may be valid by adding extra ?wsdl etc into the url, but still I have not seen this way to invoke the webservice.
    2. So you used Weblogic ant task to generate client JARs by giving this WSDL. So looks like it generated the 4 classes (.java) and in addition any other classes for Request/Response xml objects.
    3. Look at the source code of EchoService.java. It should have one default empty constructor. Internally it uses the default wsdl defined in this class. You will see another constructor that takes WSDL URL as one of the parameters (QName) etc. Echo.java is the class corresponding to the Port. In the same EchoService you should see an instance method like getEcho() something like that. This Echo.java class will have methods for all the Operations defined on this Port. So the standard code snippet we use most of the times will be like this:
    EchoService myEchoService = new EchoService(); // Default it uses WSDL deployed on Tomcat at localhost:8080
    Echo myEchoPort = myEchoService.getEchoPort(); // Something along these lines.
    myEchoPort.xxxYYY(); // NOW this is the operation name that takes the input parameters and returns outputs defined as per the WSDL defintions. If the Input and Outputs are complex xml types, it will have corresponing .JAVA files with setters and getters.
    Now if this WebService is deployed on same Tomcat but on different machine or different port, you just give the full WSDL URL with that host and port in the constructor for new EchoService(...). You may need to instantiate QName object. But look at the methods generated in EchoService.java class.
    The way you are using with Impl and Stubs class may also work. I am not much famiiar with this APIs apporach. Still look at the methods generated in these classes.
    Also if you latest Sun JDK 1.6, it also has one command like wsimport. Infact if you install WLS 10.3 with Sun JDK, it should have C:\beawlp103\jdk160_05\bin\wsimport command. This will also generate client jar given a WSDL URL.
    Thanks
    Ravi Jegga

  • Cannot run BEA WebLogic 8.1 SP 3 with JDK 1.6

    Hi,
    Im using BEA Weblogic 8.1 SP3 trying to run a sample where a Robot from Kapow Mashup Server is called from a WebService hosted in the server.
    The thing is that I keep getting a EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder (I attach the full exception below). I realised that by default the server uses the JDK which comes with the software (version 1.4) and that the class java.lang.StringBuilder is only available from JDK 1.5 onwards.
    I have JDK 1.6 in my system, so in WebLogic -> Tools -> Application Properties -> JDK Home, I set that folder but still same exception occurs.
    Through the Configuration Wizard I create a new “Basic WebLogic Server Domain” and in the step to configure the Java SDK I set the JDK 1.6 folder. However, when I try to start that server I get this error.
    JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=;C:\bea\WEBLOG~1\server\lib\weblogic_knex_patch.jar;C:\bea\WEBLOG~1\common\lib\log4j.jar;C:\bea\WEBLOG~1\server\lib\debugging.jar;C:\bea\WEBLOG~1\server\lib\knex.jar;C:\bea\WEBLOG~1\javelin\lib\javelin.jar;C:\bea\WEBLOG~1\server\lib\wlw-lang.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\ant\ant.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\lib\rt.jar;;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient+ssl.jar;C:\bea\WEBLOG~1\server\lib\xbean.jar;C:\bea\WEBLOG~1\server\lib\wlxbean.jar;C:\bea\WEBLOG~1\server\lib\xqrl.jar;C:\bea\WEBLOG~1\server\lib\netui\netui-compiler.jar;C:\bea\WEBLOG~1\server\lib\wli.jar;C:\bea\WEBLOG~1\server\lib\fop.jar;C:\bea\WEBLOG~1\integration\adapters\sample\lib\sample-eis.jar;
    PATH=C:\bea\WEBLOG~1\server\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\bin;C:\Archivos de programa\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\Archivos de programa\Archivos comunes\Adobe\AGL;c:\Archivos de programa\Microsoft SQL Server\90\Tools\binn\;c:\matlab6p5\bin\win32;C:\Nokia\Update_Manager\bin;C:\Archivos de programa\QuickTime\QTSystem\;C:\Sun\jwsdp-2.0\jwsdp-shared\bin;C:\Archivos de programa\Kapow Mashup Server 6.3\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\bea\WEBLOG~1\server\bin\oci920_8
    * To start WebLogic Server, use a username and *
    === Debugging ===
    This window is necessary for debugging code using WebLogic Workshop
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    Listening for transport dt_socket at address: 8453
    Starting WLS with line:
    C:\ARCHIV~1\Java\JDK16~1.0_1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
    Listening for transport dt_socket at address: 8453
    <27-abr-2009 11H22' CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 11.0-b15 from Sun Microsystems Inc.>
    <27-abr-2009 11H22' CEST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
    <27-abr-2009 11H22' CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Integration 8.1 SP3 Wed Jun 30 14:05:38 PDT 2004 405464>
    Stopping the Weblogic Workshop debugger...
    Debugger Stopped.
    Stopping Pointbase server...
    Pointbase server stopped.
    If I modify the settings of this new domain an pick a BEA Supplied SDKs, everything works just fine.
    Someone can give a hand on that? It seems like Bea WebLogic 8.1 and JDK 1.6 are not compatible. Completely stacked here.
    Regards.
    Full Exception
    EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder
    at robosuite.wizard.jws5a1dbbea00000001.ApiKapowIN.toString(ApiKapowIN.java:141)
    at java.lang.String.valueOf(String.java:2131)
    at java.lang.StringBuffer.append(StringBuffer.java:370)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.logInvoke(WlwThreadContext.java:363)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.startInvocation(WlwThreadContext.java:608)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:414)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:153)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:49)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executePostRequest(HttpServerHelper.java:713)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doPost(HttpServer.java:49)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6456)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    Even if it is a very naive question but I just cannot get it worked, what do you mean by using jdk 1.5 on client side?
    I guess client side is completely out of WLS so the jdk to be used on the client side is not set in the environment.
    However, the Exception Im getting is on the server side, when it tries to run the code automatically generated from Kapow Mashup Server 6.3. That code is embedded in a jar file, but it seems it makes a call to the java.lang.StringBuilder class which as said before, it is only available from jdk 1.5 onwards.
    Should I contact Kapow Mashup Server support to see how the sample code is generated or I am missing something?
    Regards.

  • Memory leak in a client using EJBs deployed in a Bea Weblogic 10.0.0 cluste

    Hi all,
    We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
    calls to an EJB deployed in cluster that has two instances installed in two different machines.
    The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
    Resuming the environment:
    Client Side:
    1 HP-Itanium machine with HP-UX.
    1 Tomcat 6 with java 6 (reproduced with java 5)
    Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
    Server Side:
    2 HP-Itanium machines with HP-UX
    Bea Weblogic Server 10.0.0 installed in both machines
    An unique domain
    Two Bea instances (one per machines) associated to a Bea Cluster
    EJBs deployed in both instances
    We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
    the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
    doesn't accept more http petitions and must be restarted.
    Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
    under data structures in the package com.sun.corba:
    com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
    |
    -> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
    |
    -> java.util.Hashtable
    |
    -> java.util.Hashtable$Entry
    |
    -> java.util.Hashtable$Entry
    -> java.util.Hashtable$Entry
    -> java.util.Hashtable$Entry
    Has anybody any idea about this problem?
    Thanks in advance.

    Hi all,
    We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
    calls to an EJB deployed in cluster that has two instances installed in two different machines.
    The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
    Resuming the environment:
    Client Side:
    1 HP-Itanium machine with HP-UX.
    1 Tomcat 6 with java 6 (reproduced with java 5)
    Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
    Server Side:
    2 HP-Itanium machines with HP-UX
    Bea Weblogic Server 10.0.0 installed in both machines
    An unique domain
    Two Bea instances (one per machines) associated to a Bea Cluster
    EJBs deployed in both instances
    We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
    the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
    doesn't accept more http petitions and must be restarted.
    Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
    under data structures in the package com.sun.corba:
    com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
    |
    -> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
    |
    -> java.util.Hashtable
    |
    -> java.util.Hashtable$Entry
    |
    -> java.util.Hashtable$Entry
    -> java.util.Hashtable$Entry
    -> java.util.Hashtable$Entry
    Has anybody any idea about this problem?
    Thanks in advance.

  • How to start weblogic in debug mode from BEA WebLogic Eclipse plugin

    I have a problem making weblogic work with eclipse3.1. I am using a BEA WebLogic plugin to handle weblogic (start/stop) from eclipse. However I want to debug my application and I am unable to figure out a way to start my weblogic in debug mode like we do in WSAD. I tried using some other plugins also but no luck. Please suggest me a plugin to handle this or any other way of debugging my application from eclipse. I am using weblogic 8.1.

    Hi,
    Dev Environment
    weblogic eclipse plugin 2.0 beta
    weblogic server 8.1
    eclipse 3.1.1
    Created a server that i would like to deploy my EJB so that i can put break points on my EJB in eclipse.
    How do i do it?
    I managed to deploy an ear (containing the ejb) directly to the weblogic installed folder and it deployed the ejb. But the breakpoint set in eclipse is not triggered. Of course in this case as weblogic server is running the .ear file deployed manually in the file system.
    Any help is appreciated.
    Mel

  • BEA Weblogic error......

    I'm running WL 6.1-SP2, petstore 1.1.2 deployathon, oracle 9i.
    When I start the "StartExampesServer" script this is the error.
    <Aug 6, 2002 5:54:47 PM CDT> <Notice> <Management> <Loading configuration file
    .\config\examples\config.xml ...>
    <Aug 6, 2002 5:54:53 PM CDT> <Notice> <WebLogicServer> <Starting WebLogic Admin
    Server "examplesServer" for domain "exam
    ples">
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Couldn't find a WLBean
    called "TheMailer" ]
    at weblogic.utils.Debug.assert(Debug.java:84)
    at weblogic.ejb20.deployer.CompositeMBeanDescriptor.initialize60(CompositeMBeanDescriptor.java:218)
    at weblogic.ejb20.deployer.CompositeMBeanDescriptor.init(CompositeMBeanDescriptor.java:159)
    at weblogic.ejb20.deployer.CompositeMBeanDescriptor.<init>(CompositeMBeanDescriptor.java:152)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:393)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:126)
    at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:128)
    at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:295)
    at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
    at weblogic.j2ee.Application.addComponent(Application.java:163)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
    at weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
    at weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy10.addTarget(Unknown Source)
    at weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
    at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
    at weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
    at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
    at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
    at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
    at weblogic.management.mbeans.custom.ApplicationManager.startAdminManager(ApplicationManager.java:278)
    at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy5.start(Unknown Source)
    at weblogic.management.Admin.startApplicationManager(Admin.java:1184)
    at weblogic.management.Admin.finish(Admin.java:590)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
    at weblogic.Server.main(Server.java:35)

    Thank you!
    But I've used the built-in plugin and it apperas when I try to do a "Add" for the BEA Weblogic App Server.
    The problem is that it does not know the state of the App Server, so the error i've copied is what I get.
    Any Idea on how to solve this?
    Greetings,
    HeCSa.

  • How to speed up the BEA weblogic workshop perforkmance?

    Hi,
    Does anybody knows how to speed up the BEA weblogic workshop,as it consumes heavy memory.
    I've configured the settings in workshop.cfg file and set the maximum memory size as 1024m midium size 516m and minimum size as 256m
    and deleted all the files from .workshop directory before open up the workshop file.
    But it hanging up the system when i opened the worshop file after some time. what could be the problem . i am using 2GB ram size

    Hi Vishnu,
    I agree this can also be one of the reason for the performance. There is Trend Micro Office Scan client installed on my system, but i couldn't not do any settings ,as it is disabled by sys admin .
    however, i removed all the scanning processes from task manager and set the high priority for the java process! still, no improvement. There are only few jpd files not even 500kb size, but when i open them, weblogic cried and utilized lots lots of memory! :-(
    I am afraid to open the weblogic which had jpd files,as it hanged my whole system, unable to perform any other tasks!

  • Configuring Workspace to Application Server (BEA Weblogic)

    Hiello,
    I am in the processing of installing and configuring System 11.1.1.1 and I have run into an issue with configuring Worksapce. I have successfully installed and configured Shared Services on (server1) using BEA Weblogic 9.2 MP3 but when I go to configure Worksapce (on the same server) the Deploy to Application Server FAILS. I have uninstalled and re-installed the software 6+ times with the same results. I would think since Shared Services works using Weblogic 9.2 MP3, Workspace would also work.
    When the configruation FAILS while deploying to the Applicaton Server this is the error that is generated in the config log file:
    "(Jan 16, 2009, 08:11:11 AM), com.hyperion.hit.registry.utils.RegistryLogger, ERROR, Component type name null is not valid INVOKER IS com.hyperion.hit.registry.LogicalWebAppComponentImpl.getWebAppType
    (Jan 16, 2009, 08:11:11 AM), com.hyperion.hit.registry.LogicalWebAppComponentImpl, ERROR,"
    Any help would be appreciated.
    Thanks

    Hi Jimit,
    Please download : Oracle WebLogic Server 11gR1 (10.3.2) - Package Installer from the below link: http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
    Once you click on *"Accept"* radio button then after *"Sign in"* you will be able to download it for Linux.
    Installation is very easy ...just run the installer ...it will ask for the Installation Directory...and once you provide it...it should do every thing for you.
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

  • Integrating WebSphere MQ 5.3 with BEA Weblogic Server 9.2 3M

    I am trying to integrate WebSphere MQ 5.3 with BEA WebLogic Server 9.2 3M. I have found the guide:
    Integrating WebSphere MQ 6 with BEA Weblogic Server 10 using Weblogic Server's Foreign (JMS) Server feature [http://ibswings.blogspot.com/]. I have done all steps according this guidance.
    I have made modification since, WebLogic Server 9.2 3M does not support EJB 3.0, I am using EJB 2.1, any changes that have been made is create ejb-jar.xml file and configure it according next guide
    At the final step when I am deploying service-jar-files (for ex. ejb.jar), I am able to complete this procedure.
    When I am starting service (for ex. ejb.jar) from Deployments I am facing a wall: exception appears
    weblogic.application.ModuleException: Exception starting module: EJBModule(EJB)
    Unable to deploy EJB: EJB.jar from EJB.jar:
    com/ibm/mq/jmqi/system/JmqiComponent
    at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:505)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:18
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.lang.NoClassDefFoundError: com/ibm/mq/jmqi/system/JmqiComponent
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at com.ibm.msg.client.wmq.factories.WMQFactoryFactory.createProviderXAConnectionFactory(WMQFactoryFactory.java:388)
    at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.setProviderFactory(JmsConnectionFactoryImpl.java:170)
    at com.ibm.mq.jms.MQConnectionFactory.&lt;init&gt;(MQConnectionFactory.java:240)
    at com.ibm.mq.jms.MQQueueConnectionFactory.&lt;init&gt;(MQQueueConnectionFactory.java:76)
    at com.ibm.mq.jms.MQXAQueueConnectionFactory.&lt;init&gt;(MQXAQueueConnectionFactory.java:69)
    at com.ibm.mq.jms.MQXAQueueConnectionFactoryFactory.getObjectInstance(MQXAQueueConnectionFactoryFactory.java:77)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
    As you can see weblogic complains about com.ibm.mq.jmqi.system.JmqiComponent, I googled JmqiComponent but dose not exists which is strange :P. Has anybody what is a reason for such a behaviour.

    Hello.
    I would ditch the foreign JMS approach. There is a detailed example of how to use the resource adapter for the same goal here:
    WebSphere MQ resource adapter  and Weblogic - how?
    While Oracle supports foreign JMS, IBM won't. The only pattern that both IBM and Oracle support is resource adapter.
    Let me know, if you need more guidance.
    -Adrian

  • How to setup and run JSP project in BEA Weblogic

    i am trying to run my JSP project located in c:\project. i am actually running it in Tomcat webserver, this time i wanna test it in bea weblogic server, i have downloaded a version 8.1, before purchasing the software for development use, i wanna know and test first BEA's integrity and use... my question is how can i set up the base document path that i have in tomcat in bea, so i can just point it to such directory and run it directly using port 7001 for bea weblogic server..
    can anybody help me get tru it step-by-step??
    help please...

    Jason Combras napisa?(a):
    how can i set up the base document path that i have in tomcat in bea, so i can just point it to such directory and run it directly using port 7001 for bea weblogic server..
    can anybody help me get tru it step-by-step??
    help please...Jason,
    Simplest way "in my opinion":
    1. start weblogic Server. You can use Server with examples. This domain
    is already configured, so You will not need any domain configuration tasks.
    2. open weblogic administration console using browser
    http://localhost:7001/console/. Log in.
    3. On the left side choose Deployments -> Web Application Modules
    4. Click "Deploy a new Web Application Module"
    5. Find folder with Your application. Mark it and click Target Module.
    6. Define Application name and click Deploy
    7. If deployed successfully, Your application should be accessible at
    http://localhost:7001/YourApplicationContextRoot
    Best Regards,
    KArol Muszynski

  • Build and run Sun's PetStore1.3.1_02 application with BEA WebLogic Server 8.1.

    build and run Sun's PetStore
    1.3.1_02 application with BEA WebLogic Server 8.1.
    5) In the same Command Prompt, compile PetStore using the commands:
    cd c:\bea\user_projects\domains\petstore
    setPetStoreEnv.cmd
    cd c:\petstore1.3.1_02\src
    ant
    buildfile:build.xml does not exist!
    build failed
    could you tell me how ?
    thank you

    What we, BEA, provides is a patch to allow you to compile Pet Store for
    WebLogic Server. It does not contain the source code.
    Sun's Pet Store source code can be found at
    http://developer.java.sun.com/developer/releases/petstore/petstore1_3_1_02.h
    tml. See the requirements section of README.TXT
    You need both in order to make it work.
    "Ankur" <[email protected]> wrote in message
    news:3fa9f2d9$[email protected]..
    Hi Nick,
    I tried building the petstore1.3.1_02 application following theinstructions in the readme. But I got an error as the buil.xml file is
    missing in the directory.....\petstore1.3.1_02\src.
    >
    I tried unzipping the downloaded again and for a petstore.domain.jar alongwith the readme. This jar does not contain the build.xml file.
    >
    Then I tried compiling one by one the component folder and found that the../xmldocuments/src folder has only a build.xml file but no source file...
    >
    Kinldy suggest what to do? Can you send me the zip via email?
    P.S: I have checked the zip and the files are missing.

  • DSN-less connection,BEA weblogic

    Hi , I have a .war file which I deploy into a BEA Weblogic server.
    Now, the .war file contains a ms-access file which is required in a JDBC-ODBC module in the .war file. What I find is that BEA doesn't extract the ms-access file to any temporary folder, and hence I am finding it hard to read the file in my JDBC-ODBC module. What I want is to know the path which I mention in the DSN-less conection if the ms-access file resides inside the .war file?
    con = DriverManager.getConnection("jdbc:odbc:;DRIVER=Microsoft Access Driver (*.mdb);DBQ=c:/databases/StockPrices.mdb");
    Sudhakar

    That's right, WebLogic does not extract WAR file on disk (extracts it just in memory) and why it should do that. WAR files are very convenient and compact format for web application deployment. But if you do want to have directory structure on your disk you can manually extract WAR file using jar tool into applications directory and this web application should work as well as in WAR form (that's so called "exploded form" of web application). WAR file is standard JAR file with some special directory organization according to web application deployment file structure specification having WAR extension!
    Furthermore, try to use some System properties like System.getProperty("user.dir") to get path for your Access MDB file: http://java.sun.com/docs/books/tutorial/essential/system/properties.html
    Finally, my suggestion is to use another type of database having real JDBC driver like freeware MySQL or PostgreSQL.

  • Error while creating a new Domain in BEA Weblogic

    I am getting the below mentioned error while creating a new Domain in BEA Weblogic
    Preparing...
    Extracting Domain Contents...
    Creating Domain Security Information...
    Saving the Domain Information...
    Storing Domain Information...
    String Substituting Domain Files...
    Performing OS Specific Tasks...
    Performing Post Domain Creation Tasks...
    Domain Creation Failed!
    Domain Location: C:\bea\user_projects\domains\base_domain_1
    Reason: Got error in writing the node manager C:\bea\wlserver_10.0\common\nodemanager\nodemanager.domains property file!
    Exception:
    java.lang.Exception: Got error in writing the node manager C:\bea\wlserver_10.0\common\nodemanager\nodemanager.domains property file!
         at com.bea.plateng.domain.DomainNodeManagerHelper.registerDomainToNodeManager(DomainNodeManagerHelper.java:138)
         at com.bea.plateng.domain.DomainNodeManagerHelper.registerDomainToNodeManager(DomainNodeManagerHelper.java:170)
         at com.bea.plateng.domain.DomainGenerator.generate(DomainGenerator.java:435)
         at com.bea.plateng.wizard.domain.gui.tasks.DomainCreationGUITask$1.run(DomainCreationGUITask.java:232)

    Hi,
    It look two ways either you dont have permission to write any new thing to that domain.properties file or might file is got corrupted.
    Please check for the permission to that file.
    Regards,
    Kal.

  • Oracle ifs and BEA weblogic

    Oracle ifs and BEA weblogic
    We have one application server with weblogic and and ifs 1.0.9 , and one db server with Oracle 8.1.7.
    with the following configuration:
    Web server
    appl server with weblogic 6.0 and ifs 1.1.9
    Oracle 8i Enterprise with interMedia text
    We need to use the iFS API call for our application.
    As I know, weblogic 6.0 support JDK1.3 but ifs 1.1.9 supports up to JDK1.2.
    Is this configuration possible?
    Any conflict if two version JDK co-exist inside same machine?
    Any suggestion?
    If I separate the appl. server into two machines, that is,
    one server installed with weblogic, the other one installed with ifs.
    How could I make use the ifs API call from appl. server?
    Is there any configuration guides for this setting?
    Thanks a lot.
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Luis:
    The iFS API is 100% pure Java. You can use it from any other Java application, be it JSP, EJB, or a standalone application.
    So it really comes down to the CLASSPATH. The iFS API is split among a set of .jar files, and some of the configuration information is stored in .properties files that are outside of these .jar files. All of this stuff needs to be in the CLASSPATH of whatever JVM is calling the iFS API.
    The iFS API uses the Oracle JDBC driver to communicate with the Oracle database. This is another requirement. You can't use another JDBC driver; you have to use ours.
    So again, it's all about configuration.<HR></BLOCKQUOTE>
    Would you mind to share more detail on configurating weblogic to integrate the iFS API?
    null

Maybe you are looking for