Weblogic server 9.1 upgrade problem

We had our application running on WLS 8.1.
Trying to upgrade to 9.2 using teh upgrade.sh script ( which uses 'java weblogic.Upgrade' inside ).
Even after it has reported that it has successfully upgraded the domain, when I login using the admin console, I see that the managed servrs are missing. So are all the resources ( JMS, connectionpool etc ) and all our EJBs.
Essentially we end up with a new admin server with nothing in it.
Has somebody else experienced this problem ?
If yes, are there any work arounds.
--sony                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

This was fixed by removing everything except teh following files from the original ( 8.1 ) domain directory
1. config.xml
2. SerializedSystemIni.dat
3. *.ldift
4. applications directory
Is this a bug in the upgrade tool ? Or did I miss a part of the documentation ?
Thanks
--sony                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

Similar Messages

  • Weblogic server 6.1 upgrade options

    Does anyone have any experience yet with upgrading from 6.1 to 8.1? Have you seen any issues that you think it might be better to go to 7.0 first and wait for the first service pack on 8.1 to be sure it's stable? Is the upgrade from 6.1 to 7.0 or 8.1 fairly smooth? Any input you have would be greatly appreciated.
    thanks,

    I'm biased since I work on the product, but I'd highly recommend going
    straight to 8.1. We spent most of our time in WLS-land between 7.0 and
    8.1 working on usability and stability of the server. I think you'll
    find it's a very nice and solid upgrade, and it gets you to JDK 1.4.
    I migrated several customer applications during our beta period. The
    migration from 6.x or later to 8.1 is pretty straightforward.
    -- Rob
    mlap wrote:
    Is it better to upgrade from WebLogic server 6.1 to 7.0 first then go
    to 8.1 or just go straight to 8.1? Has anyone ran into issues with
    8.1 already and would have been better off staying with 7.0 until the
    service pack for 8.0 comes out this July?

  • JDeveloper to WebLogic Server 6.1 connectivity problem

    Hello,
    I am try to connect to WebLogic Server 6.1 from JDeveloper Version 9.0.3.9.93.
    The JDeveloper is installed in Windows XPe. The WebLogic Server is installed in a Sun Box.
    The weblogic.jar is already in the lib/ext directory in my local machine whether the JDeveloper runs. Any help in rectifying this is greatly appreciated.
    Below is the error :
    javax.naming.AuthenticationException [Root exception is java.lang.SecurityException:
    attempting to add an object which is not an instance o java.security.Principal to a Subject's Principal Set
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Take a look at this otn thread
    oracle9i3.0_prev /weblogic problem
    Seems that WebLogic has its own java.security.Principal Class. The only workaround is....
    Edit bin\jdev.conf and added the following line:
    AddJavaLibFile ../lib/ext/weblogic.jar
    Place this new line before any other AddJavaLibFile.
    This is a problem with only a specific version of WebLogic.

  • Jbuilder 6 enterprise and weblogic server 6.1 integration problem

    hello,
    i am using jbuilder 6 enterprise and weblogic server 6.1. i just got a new
    workstation and imported my old project from cvs into jbuilder and
    everything is fine up to this point.
    the application in question is using servlet filters, so i absolutely need
    web application version 2.3. it seems, though, that my jbuilder believes for
    some reason that only tomcat 4 and borland enterprise server are capable of
    using servlet filters. i cannot remember how i fixed this last time around,
    but i did somehow. i had a recollection that the jb6_all_001 patch did the
    trick, but obviously it didn't this time, at least. what is really annoying
    is that the wizard does not allow me to create servlet filters and the
    webapp dd editor does not allow me to configure filters, either. of course,
    i can edit web.xml manually, but starting the server changes the dtd back to
    2.2 and removes everything that is 2.3 specific.
    please help me fix this?

    at the moment it is possible for me to work, though. i worked around the
    problem and i set web.xml as a read only file. i still can't use wizards to
    create servlets and i can't edit web.xml with jbuilder.

  • Download weblogic server 6.1 upgrade from sp1 to sp2

    can u give me link to download the weblogic server 6.1 sp1 upgarde to sp2

    NSRao <[email protected]> wrote in message news:<[email protected]>...
    can u give me link to download the weblogic server 6.1 sp1 upgarde to sp2go to http://support.bea.com and login. then you will see a selection for
    service packs near the bottom of the center column. you must have an esupport
    account to get the service packs.
    Wayne

  • Weblogic Server 8.1 startup problem

    We are trying to install Weblogic 8.1 server in a isolated lab with no internet
    access. The opearting system is Solaris 8.
    The problem we are experiencing is that during start up it will attempts to contact
    jakarta.apache.org and time out after ~ 25 minutes. I am hoping someone can direct
    me to a web page with inforamtion on how to remove the need to contact the website
    or reduce the timeout period. I hae looked all over e-docs.bea.com for the information
    and I could not find an answer. Thanks in advance.
    Felix

    start ur admin first as ./startweblogic.sh or double click on startweblogic.cmd if in windows OS
    Then modify ur startmanagedweblogic file with admin url and port and also server name as ur managed servers name
    Save that file as (save as option) startManagedWeblogic_M1.cmd and startManagedWeblogic_M2.cmd to start them
    the admin url and port would be the same form M1 and M2
    only the server_name will be different, M1 for M1 and M2 for M2
    Next start ur managed servers and let me know

  • Lion server Websites and Upgrade problems

    Upgranding from Snow Leopard to Lion many bad surprise:
    - the upgrade tell me that it cannot migrate all (!?@) in fact :
    -- all user where lost
    -- web sites disappear.
    MY problem:
    I have to restart all my website (all sharing the same ip an port but different name)
    Whith Server.app/WEBServer I add the sites assignig to each the right  "store site files"
    but .. TaDa!  from the brouser I get always the DEFAULT.
    It seams the old asterix problem.
    Ps. Nat work only if in System Preferences/Sharing I enable "internet Sharing" but
    what happen if the server come up after a loss of power and nobody login ?
    Thank you

    Upgranding from Snow Leopard to Lion many bad surprise:
    - the upgrade tell me that it cannot migrate all (!?@) in fact :
    -- all user where lost
    -- web sites disappear.
    MY problem:
    I have to restart all my website (all sharing the same ip an port but different name)
    Whith Server.app/WEBServer I add the sites assignig to each the right  "store site files"
    but .. TaDa!  from the brouser I get always the DEFAULT.
    It seams the old asterix problem.
    Ps. Nat work only if in System Preferences/Sharing I enable "internet Sharing" but
    what happen if the server come up after a loss of power and nobody login ?
    Thank you

  • Error in adding package to WebLogic Server 7.0...

    Hi All,
    May I know how can I add a new package to the WebLogic Server ?
    I have attempted to do so but WebLogic Server failed to start up due to error
    in loading the package. The error message generated is
    Starting WebLogic Server...
    <Oct 21, 2002 11:43:50 AM SGT> <Notice> <Management> <140005> <Loading configura
    tion D:\bea\USER_P~1\APSWSV1\.\config.xml>
    <Oct 21, 2002 11:43:57 AM SGT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception
    Throwable: javax.xml.parsers.FactoryConfigurationError: weblogic.xml.jaxp.Regist
    rySAXParserFactory
    javax.xml.parsers.FactoryConfigurationError: weblogic.xml.jaxp.RegistrySAXParser
    Factory
    at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:
    157)
    at com.octetstring.vde.schema.InitSchema.init(InitSchema.java:50)
    at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:212)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    javax.xml.parsers.FactoryConfigurationError: weblogic.xml.jaxp.RegistrySAXParser
    Factory
    at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:
    157)
    at com.octetstring.vde.schema.InitSchema.init(InitSchema.java:50)
    at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:212)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Reason: Fatal initialization exception
    Throwable: javax.xml.parsers.FactoryConfigurationError: weblogic.xml.jaxp.Regist
    rySAXParserFactory
    javax.xml.parsers.FactoryConfigurationError: weblogic.xml.jaxp.RegistrySAXParser
    Factory
    at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:
    157)
    at com.octetstring.vde.schema.InitSchema.init(InitSchema.java:50)
    at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:212)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    D:\bea\USER_P~1\APSWSV1>ENDLOCAL
    D:\bea\USER_P~1\APSWSV1>popd
    D:\bea\user_projects\APSWSV1>ENDLOCAL
    D:\bea\USER_P~1\APSWSV1>exit
    Please advise and many thanks in advance.
    Regards,
    Boon Keong

    Thanks anyway. I have already solved the problem. Just need to add the path to
    the jar file in startWLS.cmd in addition to adding it to the workshop properties
    file.
    Boon Keong
    "Mark Griffith" <[email protected]> wrote:
    http://edocs.bea.com/wls/docs70/faq/xml.html
    Dont know about Workshop. Sorry, cc'ing their newsgroup.
    cheers
    mbg
    "Boon Keong" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    Sorry for not being clear in my question.
    Let me explain my situation:
    I was trying to use an XML parser from Apache (Packageorg.apache.xerces.* - xerces.jar)
    within the WebLogic Workshop environment. I have included to path tothis
    jar
    file in Workshop
    properties and do not have any problem importing the package in designenvironment.
    However, when I tried to compile the web service in Workshop, it generatesthe
    error message "Package org.apache.xerces".
    I am clueless of how to resolve the above problem and thought thatI might
    need
    to add xerces.jar to the directory "d:\bea\jdk131_03\jre\lib\ext" sothat
    it can
    be loaded by WebLogic Server and resolve my problem. However, by doingso,
    WebLogic
    Server generates the error message as mentioned in my previous posting.
    In conclusion, my problem is how can I resolve the compilation errorin
    Workshop.
    Thanks in advance.
    Regards,
    Boon Keong
    "Mark Griffith" <[email protected]> wrote:
    Boon:
    I am not sure what you mean when you say, "add a package"?
    Package of what?
    What is the entry in your server log that says: java.class.path
    D:\bea\USER_P~1\APSWSV1\$SERVER_NAME\$SERVER_NAME.log
    cheers
    mbg
    "Boon Keong" <[email protected]> wrote in message
    news:[email protected]...
    Hi All,
    May I know how can I add a new package to the WebLogic Server ?
    I have attempted to do so but WebLogic Server failed to start up
    due
    to
    error
    in loading the package. The error message generated is
    Starting WebLogic Server...
    <Oct 21, 2002 11:43:50 AM SGT> <Notice> <Management> <140005> <Loadingconfigura
    tion D:\bea\USER_P~1\APSWSV1\.\config.xml>
    <Oct 21, 2002 11:43:57 AM SGT> <Emergency> <WebLogicServer> <000342><Unable to
    initialize the server: Fatal initialization exception
    Throwable: javax.xml.parsers.FactoryConfigurationError:weblogic.xml.jaxp.Regist
    rySAXParserFactory
    javax.xml.parsers.FactoryConfigurationError:weblogic.xml.jaxp.RegistrySAXParser
    Factory
    atjavax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:
    157)
    at
    com.octetstring.vde.schema.InitSchema.init(InitSchema.java:50)
    at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:212)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    javax.xml.parsers.FactoryConfigurationError:weblogic.xml.jaxp.RegistrySAXParser
    Factory
    atjavax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:
    157)
    at
    com.octetstring.vde.schema.InitSchema.init(InitSchema.java:50)
    at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:212)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Reason: Fatal initialization exception
    Throwable: javax.xml.parsers.FactoryConfigurationError:weblogic.xml.jaxp.Regist
    rySAXParserFactory
    javax.xml.parsers.FactoryConfigurationError:weblogic.xml.jaxp.RegistrySAXParser
    Factory
    atjavax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:
    157)
    at
    com.octetstring.vde.schema.InitSchema.init(InitSchema.java:50)
    at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:212)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    D:\bea\USER_P~1\APSWSV1>ENDLOCAL
    D:\bea\USER_P~1\APSWSV1>popd
    D:\bea\user_projects\APSWSV1>ENDLOCAL
    D:\bea\USER_P~1\APSWSV1>exit
    Please advise and many thanks in advance.
    Regards,
    Boon Keong

  • Chinese in weblogic server 7.0

              A servlet cann't recieve chinese in weblogic server 7,but not problem in weblogic
              server 6.1,Why?
              

    As per the j2ee 1.2, jsp 1.2 specification mandates that the expressions
    default must be "null".
    We have introduced a new flag in weblogic.xml called printNulls which is
    true by default meaning that "null" will be the default.
    Setting this to false makes sure that expressions(<%=expr%> ) with "null"
    results are printed as "" (earlier behavior)
    Here is how to configure the printNulls from weblogic.xml :
    <weblogic-web-app>
    <jsp-param>
    <param-name>printNulls</param-name>
    <param-value>false</param-value>
    </jsp-param>
    </weblogic-web-app>
    Regards,
    Eric
    "taqdees malik" <[email protected]> wrote in message
    news:3daaff99$[email protected]..
    >
    Hi,
    I'm trying to port my web application from weblogic server 6.1 toweblogic
    7.0. I'm having a little problem with jsp pages in weblogic 7.0. Some ofthe text
    box controls which are populated dynamically in my jsp pages are gettingpopulated
    with
    "null" value in WL 7.0 e.g. in the following case
    <%
    String claim_id=null;
    %>
    <input type=text value=<%= claim_id %> >
    on weblogic 6.1 an empty string is printed but in wl 7.0 null is printedas the
    value for the text field.
    I used the domain configuration wizard in wl 7.0 to make a WLS Domain andthen
    deployed my application. If I deploy the same application in one of theexamples
    domain which is installed with Weblogic 7.0 then everything works fine. Soits
    definity a configuration issue.
    Could someone please help me with this.
    Thanks,
    -Taqdees.

  • Virtual Host on WebLogic Server 5.1

    I need to configure my weblogic server 5.1 on windows 2000 server to make a virtual
    host address.
    How I can do it ????
    Thanks a lot for any help.
    Bye

    Hi Andy,
    I think a good approach for you would be to use a proxy server --
    browser -> proxy that supports virtual hosting -> WebLogic
    Use a proxy which supports virtual hosting, and which can have a separate
    certificate bound to each virtual host.
    That way you can do SSL between the browser and the proxy, and you can
    have the proxy do cleartext to WebLogic.
    This situation gets around WebLogic's limitation of allowing only one
    certificate per instance of the server.
    You could also use 5.1 as the proxy in the following manner:
    Run 3 instances of Weblogic, each as a proxy server, each bound to a
    different IP address and DNS name, having its own certificate --
    one instance for aaa.com, another for bbb.com, and a third for ccc.com
    Then have each of these three instances of WebLogic proxy to your "app
    server" instance of WebLogic on the backend.
    Hope this makes sense.
    Joe Jerry
    Andy Walker wrote:
    Hello,
    I am tasked with implementing a virtual hosting situation that must
    use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
    and https://www.ccc.com all having separate IPs. These URLs must
    forward the request to the same WebLogic Server instance. The problem
    is each URL must have its own certificate while WLS 5.1 only uses one
    certificate per instance.
    I was thinking about using a proxy server such that all three Web
    servers that would host the URLs would be sent to a proxy server which
    would redirect to the WLS 5.1 instance.
    My questions are, would this be feasible using WLS 5.1 as the Web
    Server and again WLS as the App Server? How secure is this
    arrangement? Is it preferable to use another vendor's software as the
    WebServer(IPlanet, Apache)

  • Bug:WEB-INF/lib JARs not added to runtime classpath of WebLogic Server

    The JAR files packaged in the WEB-INF/lib directory of an application do not get installed to the runtime classpath of the Weblogic server.
    Edited by: dvohra16 on Feb 28, 2013 9:24 AM

    Some posts in which an external jar, usually a JDBC jar, had to be added to the startWebLogic script to be added to the runtime classpath of WebLogic server.
    Re: jdbc problem on MS SQL Server
    Re: MySQL JDBC driver w/11.1.2 where too now?
    Re: ADF Parameter form  - java.lang.NoClassDefFoundError: sqlj/runtime/ref/Defa
    Re: Cannot load driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver
    Re: deploy a shared library
    Re: Cannot load driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver
    Re: Help need in Adding External jar files.
    Re: NoClassDefFoundError  while Testing a JAX-WS Web Service
    Re: Unable to connect to SQL server 2008 from a deployed Weblogic application
    Re: Howo to add external jar - quick question
    Re: MySql connection with JDev 11.1.2.2 issues
    Re: Integration of MySQL with ADF application

  • Migrate a webservice built in WebLogic Server 8.1 to Oracle WLS 10.3

    Hi
    I have built a webservice in a application server BEA WebLogic Server 8.1 SP6
    Now I want to migrate it to a application server Oracle WebLogic Server 10.3
    My problem is the webservice uses a file build.xml that contains some commands that are deprecated in version 10.3
    These deprecated commands include in the file build.xml are :
    <target name="generate-autotype">
    <*autotype* wsdl="${CLIENT_BUILDER_RESOURCES}/${webservice}.wsdl"
    targetNamespace="http://webservices/${modulo}/${webservice}.wsdl"
    packageName="webservices.${modulo}"
    destDir="${CLIENT_BUILDER_OUTPUT_DIR}"
    keepGenerated="false"/>
    <move file="${CLIENT_BUILDER_OUTPUT_DIR}/types.xml" todir="${CLIENT_BUILDER_BUILD_DIR}"/>
    </target>
    <*source2wsdd* javaSource="${SICAS_SRC}/webservices/${modulo}/${clase}.java"
    sourcePath="${CLIENT_BUILDER_OUTPUT_DIR}"
    typesInfo="${CLIENT_BUILDER_BUILD_DIR}/types.xml"
    ddFile="${CLIENT_BUILDER_BUILD_DIR}/web-services.xml"
    mergeWithExistingWS="true"
    serviceURI="/${webservice}"
    targetNamespace="http://webservices/${modulo}/${webservice}.wsdl"
    classpathref="source2wsdd.class.path"/>
    </target>
    <target name="generate-ear">
    <*wspackage* output="${CLIENT_BUILDER_BUILD_DIR}/sicasws.ear"
    codecDir="${CLIENT_BUILDER_OUTPUT_DIR}"
    webAppClasses="webservices.${modulo}/${webservice}"
    overwrite="false"
    ddFile="${CLIENT_BUILDER_BUILD_DIR}/web-services.xml"
    warName="sicasws.war"/>
    </target>
    I need to compile my webservice in Oracle WebLogic 10.3
    Before compile it, I must change the file build.xml of the webservice
    Can anybody tell me how can migrate this webservice to Oracle WebLogic Server 10.3?
    Thanks a lot
    Josep Maria

    Hi Josep,
    WLS8.1 webservice needs to have all the WebService annotations when we migrate it to WLS9.x onwards.
    Here is a Simplest way which can be used....As you already have the WSDL generated from your WLS8.1 WebService ....So Use WSDLC Task to genarate the Annotated WebService from it ...and then Copy and paste the Method Implementations from your OLD Service to the Newly Generated Service....
    How to do it?
    Answer: Here is have developed a Step by Step procedure to do it...Please have a look...
    http://jaysensharma.wordpress.com/2009/12/18/how-to-build-a-webservice-from-a-wsdl/
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

  • SSL with virtual hosting in Weblogic Server 5.1(WLS5.1)

    Hello,
    I am tasked with implementing a virtual hosting situation that must
    use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
    and https://www.ccc.com all having separate IPs. These URLs must
    forward the request to the same WebLogic Server instance. The problem
    is each URL must have its own certificate while WLS 5.1 only uses one
    certificate per instance.
    I was thinking about using a proxy server such that all three Web
    servers that would host the URLs would be sent to a proxy server which
    would redirect to the WLS 5.1 instance.
    My questions are, would this be feasible using WLS 5.1 as the Web
    Server and again WLS as the App Server? How secure is this
    arrangement? Is it preferable to use another vendor's software as the
    WebServer(IPlanet, Apache)

    Hi Andy,
    I think a good approach for you would be to use a proxy server --
    browser -> proxy that supports virtual hosting -> WebLogic
    Use a proxy which supports virtual hosting, and which can have a separate
    certificate bound to each virtual host.
    That way you can do SSL between the browser and the proxy, and you can
    have the proxy do cleartext to WebLogic.
    This situation gets around WebLogic's limitation of allowing only one
    certificate per instance of the server.
    You could also use 5.1 as the proxy in the following manner:
    Run 3 instances of Weblogic, each as a proxy server, each bound to a
    different IP address and DNS name, having its own certificate --
    one instance for aaa.com, another for bbb.com, and a third for ccc.com
    Then have each of these three instances of WebLogic proxy to your "app
    server" instance of WebLogic on the backend.
    Hope this makes sense.
    Joe Jerry
    Andy Walker wrote:
    Hello,
    I am tasked with implementing a virtual hosting situation that must
    use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
    and https://www.ccc.com all having separate IPs. These URLs must
    forward the request to the same WebLogic Server instance. The problem
    is each URL must have its own certificate while WLS 5.1 only uses one
    certificate per instance.
    I was thinking about using a proxy server such that all three Web
    servers that would host the URLs would be sent to a proxy server which
    would redirect to the WLS 5.1 instance.
    My questions are, would this be feasible using WLS 5.1 as the Web
    Server and again WLS as the App Server? How secure is this
    arrangement? Is it preferable to use another vendor's software as the
    WebServer(IPlanet, Apache)

  • Query about the steps for Weblogic Server Upgrade from 8.1 to 10.3

    Hi!
    We have planned to upgrade our Weblogic Server from 8.1 to 10.3. Could anyone advise me:
    1. How to upgrade the Weblogic Server from 8.1 to 10.3? Can the Weblogic Server 10.3 coexist with the Weblogic Server 8.1 in one physical server?
    2. Where can the upgrade software be downloaded?
    3. We have a web service currently running under Weblogic Workshop as the Weblogic Server is started via the workshop. Can this web service be run under Weblogic Server 10.3?
    4. Are there any foreseeable issues/problems that will happen?
    Please kindly help me. Thanks a lot.
    Best Regards
    May

    Download location: http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
    You can upgrade the domain after you install wls 10.3 using QuickStart.
    When we migrated we have moved from windows to linux. We have installed, created domain, created managed servers, configured, etc. from scratch. We didn't face any 'show stopper' issues.

  • Problem in starting weblogic server as proxy

    I am using weblogic server as Proxy to forward the requests to weblogic cluster.
    When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
    I am Pasting my complete logs below.
    Setting JVM memory params for server IRISProxy
    Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
    WLS Production Mode=true
    ./startWebLogic.sh[68]: B: not found.
    maxfiles=8192
    CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
    PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
    * To start WebLogic Server, use a username and *
    * 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:
    java version "1.4.1.05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
    Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
    Starting WLS with line:
    /home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
    Bad level value for property: com.iplanet.services.debug.level
    Bad level value for property: com.sun.identity.agents.logging.level
    Bad level value for property: com.sun.am.policy.amFilter.audit.level
    <Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
    WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
    WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
    WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
    <Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
    <Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
    java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
         at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
         at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
         at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
    >
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
    Can someone help me in solving this problem
    Thanks
    Kris

    I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
    WebLogic Temporary Patch for CR211812
    WebLogic Temporary Patch for CR235145
    Once i commented the above patches in the CLASSPATH.
    The issue is resolved.

Maybe you are looking for