J2EE replaces BEA Weblogic, IBM WebSphere, Orion or JRun

BEA Weblogic, IBM WebSphere absolutely provide stronger ability to support enterprise applications.
I want to know whether J2EE can be used in deploying a commercial web site with multi-tier architecture. For example, to handle hundreds concurrent requests, to balance work load to some extent.
Thanks.

J2EE is a platform specification. And WebLogic, WebSphere, JRun etc. are vendor specific products that implement APIs from that platform standard.
It seems you are talking about the refrence implementation of J2EE that comes with J2EE SDK.
See http://java.sun.com/j2ee/faq.html Especially the answers therein to the two questions...
1. What is the purpose of the Reference Implementation?
2. Why don't you allow the binary Reference Implementation to be deployed or redistributed?

Similar Messages

  • ANN: J2EE Applications & BEA WebLogic Hardcopies Available!

    ** J2EE Applications & BEA WebLogic Hardcopies Available! **
    The first hardcopies of the only programming book to cover J2EE & WebLogic 6
    are now available. For those of you that have already ordered, we thank you.
    In just a few short weeks we have moved up to the No. 42 spot on Amazon.
    If you have not ordered already, you can order now and copies will be
    shipped in just a few short days. The book can be located Amazon.com at the
    following URL:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
    5396741-5920623
    More information on this book can be located at:
    http://www.learnweblogic.com/.
    ** Overview **
    Building J2EE Applications & BEA WebLogic is targeted at Java programmers
    developing applications for the BEA WebLogic platform, the leading Web
    Application Server in the marketplace today. This book focuses on best
    practices for developing enterprise applications using the WebLogic APIs.
    After reading this book, intermediate or professional-level Java developers
    will possess the skills and knowledge required to develop scalable and
    robust applications on the WebLogic platform.
    The book combines reference and tutorial, taking a step-by-step approach
    that introduces each API and uses it to build a component of the WebAuction
    application, which supports on-line Auctioning on the Web. All software
    needed to build the sample application is included on a CD-ROM that
    accompanies the book. The WebAuction project gives users the opportunity to
    explore significant areas of building a distributed Enterprise Java
    application, including:
    · Planning in advance for scalability and deployment
    · Building presentation logic
    · Establishing database connectivity
    · Creating Enterprise Java Beans for the BEA WebLogic application server
    · Packaging the whole application so that it can be easily managed and
    maintained.
    ** About the Authors **
    Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
    the lead developer for the WebLogic Server EJB Container. Before joining
    BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
    Bachelors degree in Computer Science from Princeton University.
    Michael Girdley is the Director of Product Management for WebLogic Server at
    BEA, a role in which he acts as chief marketing liaison to over 200
    engineers. An experienced application developer in Java, HTML, C, and C++,
    Michael is a co-author of Web Programming with Java (Sams-net Publishing,
    1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
    Michael holds a Bachelors degree in Computer Science with Honors from
    Lafayette College.
    Sandra L. Emerson is a technical writer and consultant with 20 years'
    experience in the software industry. She is a co-author of four computer
    trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
    Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
    Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
    (Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
    is scheduled for Fall, 2000.

    ** J2EE Applications & BEA WebLogic Hardcopies Available! **
    The first hardcopies of the only programming book to cover J2EE & WebLogic 6
    are now available. For those of you that have already ordered, we thank you.
    In just a few short weeks we have moved up to the No. 42 spot on Amazon.
    If you have not ordered already, you can order now and copies will be
    shipped in just a few short days. The book can be located Amazon.com at the
    following URL:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
    5396741-5920623
    More information on this book can be located at:
    http://www.learnweblogic.com/.
    ** Overview **
    Building J2EE Applications & BEA WebLogic is targeted at Java programmers
    developing applications for the BEA WebLogic platform, the leading Web
    Application Server in the marketplace today. This book focuses on best
    practices for developing enterprise applications using the WebLogic APIs.
    After reading this book, intermediate or professional-level Java developers
    will possess the skills and knowledge required to develop scalable and
    robust applications on the WebLogic platform.
    The book combines reference and tutorial, taking a step-by-step approach
    that introduces each API and uses it to build a component of the WebAuction
    application, which supports on-line Auctioning on the Web. All software
    needed to build the sample application is included on a CD-ROM that
    accompanies the book. The WebAuction project gives users the opportunity to
    explore significant areas of building a distributed Enterprise Java
    application, including:
    · Planning in advance for scalability and deployment
    · Building presentation logic
    · Establishing database connectivity
    · Creating Enterprise Java Beans for the BEA WebLogic application server
    · Packaging the whole application so that it can be easily managed and
    maintained.
    ** About the Authors **
    Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
    the lead developer for the WebLogic Server EJB Container. Before joining
    BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
    Bachelors degree in Computer Science from Princeton University.
    Michael Girdley is the Director of Product Management for WebLogic Server at
    BEA, a role in which he acts as chief marketing liaison to over 200
    engineers. An experienced application developer in Java, HTML, C, and C++,
    Michael is a co-author of Web Programming with Java (Sams-net Publishing,
    1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
    Michael holds a Bachelors degree in Computer Science with Honors from
    Lafayette College.
    Sandra L. Emerson is a technical writer and consultant with 20 years'
    experience in the software industry. She is a co-author of four computer
    trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
    Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
    Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
    (Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
    is scheduled for Fall, 2000.

  • J2EE Applications & BEA WebLogic Hardcopies Available!

    ** J2EE Applications & BEA WebLogic Hardcopies Available! **
    The first hardcopies of the only programming book to cover J2EE & WebLogic 6
    are now available. For those of you that have already ordered, we thank you.
    In just a few short weeks we have moved up to the No. 42 spot on Amazon.
    If you have not ordered already, you can order now and copies will be
    shipped in just a few short days. The book can be located Amazon.com at the
    following URL:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
    5396741-5920623
    More information on this book can be located at:
    http://www.learnweblogic.com/.
    ** Overview **
    Building J2EE Applications & BEA WebLogic is targeted at Java programmers
    developing applications for the BEA WebLogic platform, the leading Web
    Application Server in the marketplace today. This book focuses on best
    practices for developing enterprise applications using the WebLogic APIs.
    After reading this book, intermediate or professional-level Java developers
    will possess the skills and knowledge required to develop scalable and
    robust applications on the WebLogic platform.
    The book combines reference and tutorial, taking a step-by-step approach
    that introduces each API and uses it to build a component of the WebAuction
    application, which supports on-line Auctioning on the Web. All software
    needed to build the sample application is included on a CD-ROM that
    accompanies the book. The WebAuction project gives users the opportunity to
    explore significant areas of building a distributed Enterprise Java
    application, including:
    · Planning in advance for scalability and deployment
    · Building presentation logic
    · Establishing database connectivity
    · Creating Enterprise Java Beans for the BEA WebLogic application server
    · Packaging the whole application so that it can be easily managed and
    maintained.
    ** About the Authors **
    Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
    the lead developer for the WebLogic Server EJB Container. Before joining
    BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
    Bachelors degree in Computer Science from Princeton University.
    Michael Girdley is the Director of Product Management for WebLogic Server at
    BEA, a role in which he acts as chief marketing liaison to over 200
    engineers. An experienced application developer in Java, HTML, C, and C++,
    Michael is a co-author of Web Programming with Java (Sams-net Publishing,
    1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
    Michael holds a Bachelors degree in Computer Science with Honors from
    Lafayette College.
    Sandra L. Emerson is a technical writer and consultant with 20 years'
    experience in the software industry. She is a co-author of four computer
    trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
    Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
    Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
    (Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
    is scheduled for Fall, 2000.

    ** J2EE Applications & BEA WebLogic Hardcopies Available! **
    The first hardcopies of the only programming book to cover J2EE & WebLogic 6
    are now available. For those of you that have already ordered, we thank you.
    In just a few short weeks we have moved up to the No. 42 spot on Amazon.
    If you have not ordered already, you can order now and copies will be
    shipped in just a few short days. The book can be located Amazon.com at the
    following URL:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
    5396741-5920623
    More information on this book can be located at:
    http://www.learnweblogic.com/.
    ** Overview **
    Building J2EE Applications & BEA WebLogic is targeted at Java programmers
    developing applications for the BEA WebLogic platform, the leading Web
    Application Server in the marketplace today. This book focuses on best
    practices for developing enterprise applications using the WebLogic APIs.
    After reading this book, intermediate or professional-level Java developers
    will possess the skills and knowledge required to develop scalable and
    robust applications on the WebLogic platform.
    The book combines reference and tutorial, taking a step-by-step approach
    that introduces each API and uses it to build a component of the WebAuction
    application, which supports on-line Auctioning on the Web. All software
    needed to build the sample application is included on a CD-ROM that
    accompanies the book. The WebAuction project gives users the opportunity to
    explore significant areas of building a distributed Enterprise Java
    application, including:
    · Planning in advance for scalability and deployment
    · Building presentation logic
    · Establishing database connectivity
    · Creating Enterprise Java Beans for the BEA WebLogic application server
    · Packaging the whole application so that it can be easily managed and
    maintained.
    ** About the Authors **
    Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
    the lead developer for the WebLogic Server EJB Container. Before joining
    BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
    Bachelors degree in Computer Science from Princeton University.
    Michael Girdley is the Director of Product Management for WebLogic Server at
    BEA, a role in which he acts as chief marketing liaison to over 200
    engineers. An experienced application developer in Java, HTML, C, and C++,
    Michael is a co-author of Web Programming with Java (Sams-net Publishing,
    1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
    Michael holds a Bachelors degree in Computer Science with Honors from
    Lafayette College.
    Sandra L. Emerson is a technical writer and consultant with 20 years'
    experience in the software industry. She is a co-author of four computer
    trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
    Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
    Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
    (Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
    is scheduled for Fall, 2000.

  • ** ANNOUNCE: J2EE Applications & BEA WebLogic Hardcopies Available! **

    ** ANNOUNCE: J2EE Applications & BEA WebLogic Hardcopies Available! **
    The first hardcopies of the only programming book to cover J2EE & WebLogic 6
    are now available. For those of you that have already ordered, we thank
    you.
    In just a few short weeks we have moved up to the No. 636 spot on Amazon.
    This is great interest in considering the official ship date is not until
    August 16!
    If you have not ordered already, you can order now and copies will be
    shipped in just a few short days. The book can be located Amazon.com at the
    following URL:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/learnweblogic/102-1778325-
    4765749
    More information on this book can be located at:
    http://www.learnweblogic.com/.
    ** Overview **
    Building J2EE Applications & BEA WebLogic is targeted at Java programmers
    developing applications for the BEA WebLogic platform, the leading Web
    Application Server in the marketplace today. This book focuses on best
    practices for developing enterprise applications using the WebLogic APIs.
    After reading this book, intermediate or professional-level Java developers
    will possess the skills and knowledge required to develop scalable and
    robust applications on the WebLogic platform.
    The book combines reference and tutorial, taking a step-by-step approach
    that introduces each API and uses it to build a component of the WebAuction
    application, which supports on-line Auctioning on the Web. All software
    needed to build the sample application is included on a CD-ROM that
    accompanies the book. The WebAuction project gives users the opportunity to
    explore significant areas of building a distributed Enterprise Java
    application, including:
    · Planning in advance for scalability and deployment
    · Building presentation logic
    · Establishing database connectivity
    · Creating Enterprise Java Beans for the BEA WebLogic application server
    · Packaging the whole application so that it can be easily managed and
    maintained.
    ** About the Authors **
    Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
    the lead developer for the WebLogic Server EJB Container. Before joining
    BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
    Bachelors degree in Computer Science from Princeton University.
    Michael Girdley is the Director of Product Management for WebLogic Server at
    BEA, a role in which he acts as chief marketing liaison to over 200
    engineers. An experienced application developer in Java, HTML, C, and C++,
    Michael is a co-author of Web Programming with Java (Sams-net Publishing,
    1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
    Michael holds a Bachelors degree in Computer Science with Honors from
    Lafayette College.
    Sandra L. Emerson is a technical writer and consultant with 20 years'
    experience in the software industry. She is a co-author of four computer
    trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
    Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
    Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
    (Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
    is scheduled for Fall, 2000.

    ** ANNOUNCE: J2EE Applications & BEA WebLogic Hardcopies Available! **
    The first hardcopies of the only programming book to cover J2EE & WebLogic 6
    are now available. For those of you that have already ordered, we thank
    you.
    In just a few short weeks we have moved up to the No. 636 spot on Amazon.
    This is great interest in considering the official ship date is not until
    August 16!
    If you have not ordered already, you can order now and copies will be
    shipped in just a few short days. The book can be located Amazon.com at the
    following URL:
    http://www.amazon.com/exec/obidos/ASIN/0130911119/learnweblogic/102-1778325-
    4765749
    More information on this book can be located at:
    http://www.learnweblogic.com/.
    ** Overview **
    Building J2EE Applications & BEA WebLogic is targeted at Java programmers
    developing applications for the BEA WebLogic platform, the leading Web
    Application Server in the marketplace today. This book focuses on best
    practices for developing enterprise applications using the WebLogic APIs.
    After reading this book, intermediate or professional-level Java developers
    will possess the skills and knowledge required to develop scalable and
    robust applications on the WebLogic platform.
    The book combines reference and tutorial, taking a step-by-step approach
    that introduces each API and uses it to build a component of the WebAuction
    application, which supports on-line Auctioning on the Web. All software
    needed to build the sample application is included on a CD-ROM that
    accompanies the book. The WebAuction project gives users the opportunity to
    explore significant areas of building a distributed Enterprise Java
    application, including:
    · Planning in advance for scalability and deployment
    · Building presentation logic
    · Establishing database connectivity
    · Creating Enterprise Java Beans for the BEA WebLogic application server
    · Packaging the whole application so that it can be easily managed and
    maintained.
    ** About the Authors **
    Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
    the lead developer for the WebLogic Server EJB Container. Before joining
    BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
    Bachelors degree in Computer Science from Princeton University.
    Michael Girdley is the Director of Product Management for WebLogic Server at
    BEA, a role in which he acts as chief marketing liaison to over 200
    engineers. An experienced application developer in Java, HTML, C, and C++,
    Michael is a co-author of Web Programming with Java (Sams-net Publishing,
    1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
    Michael holds a Bachelors degree in Computer Science with Honors from
    Lafayette College.
    Sandra L. Emerson is a technical writer and consultant with 20 years'
    experience in the software industry. She is a co-author of four computer
    trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
    Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
    Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
    (Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
    is scheduled for Fall, 2000.

  • Jms from sun j2ee to bea weblogic

    Hy,
              is there a easy way to connect a JmsFactory from an j2ee sun server to a
              bea weblogic server?
              JMS API Tutorial shows an example for connecting two j2ee Server:
              j2eeadmin --addJmsFactory MyFactory queue -props
              url=corbaname:iiop:remoteserver:1050:#remoteserver
              Weblogic 7 seems to support iiop (on Port 7001?) but
              something is missing ... no connection could be made to send Messages
              from j2ee (sun) to weblogic server?
              Any hint?
              Best Regards,
              Holger
              

    Hi Holger,
              The WL JMS client does not support iiop in 7.0,
              although it does in 8.1 (beta soon). Instead use t3, a much
              faster protocol, or, if you need to tunnel, use http.
              Note that BEA has a comprehensive white-paper on integrating
              "foreign" JMS providers on dev2dev.bea.com:
              "Using Foreign JMS Providers With WebLogic Server"
              Tom
              Holger von Rhein wrote:
              > Hy,
              >
              > is there a easy way to connect a JmsFactory from an j2ee sun server to a
              > bea weblogic server?
              >
              > JMS API Tutorial shows an example for connecting two j2ee Server:
              >
              > j2eeadmin --addJmsFactory MyFactory queue -props
              > url=corbaname:iiop:remoteserver:1050:#remoteserver
              >
              > Weblogic 7 seems to support iiop (on Port 7001?) but
              > something is missing ... no connection could be made to send Messages
              > from j2ee (sun) to weblogic server?
              >
              > Any hint?
              >
              >
              > Best Regards,
              >
              > Holger
              >
              

  • Xmlparserv2.jar cause IBM WebSphere v5.1 down.

    Anyone knows:
    I have a j2ee project based on IBM WebSphere v5.1 + Oracle DB 10g(XMLDB included).There's a big trouble bother me.
    My project used Oracle xml implemention,such as DOM parser included in xmlparserv2.jar.and when i deploy my project to WAS(WebSphere Application Server),it throws errors and can not startup normally.it's sounds that WAS cann't determine which xml implemention it should choose:
    Error message below:
    ==============================================
    *** 启动服务器 ***
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O java.net.MalformedURLException: unknown protocol: f
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java(Compiled Code))
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java(Compiled Code))
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at java.net.URL.<init>(URL.java:450)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:214)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:177)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.xml.BaseFactory.load(BaseFactory.java:191)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.xml.BaseFactory.load(BaseFactory.java:173)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.loadVersionInfo(WASProduct.java:1876)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.getVersionInfo(WASProduct.java:1829)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.websphere.product.WASProduct.getPlatform(WASProduct.java:845)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.TraceImpl.initialize(TraceImpl.java:59)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    [05-5-2 12:06:49:906 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at java.lang.reflect.Method.invoke(Method.java:386)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    [05-5-2 12:06:49:922 CST] 3d455614 SystemOut O at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    ************ Start Display Current Environment ************
    Host Operating System is Windows XP, version 5.1
    Java version = J2RE 1.4.1 IBM Windows 32 build cn1411-20031011 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
    was.install.root = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51
    user.install.root = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51
    Java Home = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre
    ws.ext.dirs = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/lib;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/classes;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/classes;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/ext;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/web/help;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;F:\document\musicool\CVS\libs\xsdbeans.jar;F:/Program_Files/IBM/SQLLIB/java/db2java.zip;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.webservice_5.1.1/runtime/worf.jar
    Classpath = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/properties;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/properties;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/bootstrap.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/j2ee.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/lmproxy.jar;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/lib/urlprotocols.jar;F:\document\musicool\CVS\libs\workflow.jar;F:\document\musicool\CVS\libs\DBClient.jar;F:\document\musicool\CVS\libs\log4j-1.2.8.jar;F:\document\musicool\CVS\libs\log.jar;F:\document\musicool\CVS\libs\utility.jar;F:\document\musicool\CVS\libs\webwork.jar;F:\document\musicool\CVS\libs\xdb.jar;F:\Oracle\product\10.1.0\Client_1\lib\xsu12.jar;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1/runtime/wteServers.jar;f:/Program_Files/IBM/WebSphere_Studio/wstools/eclipse/plugins/com.ibm.etools.websphere.tools.common_5.1.1/runtime/wasToolsCommon.jar
    Java Library path = f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51/java/jre/bin;F:\Program_Files\IBM\WebSphere_Studio\eclipse\jre\bin;.;F:\Program_Files\IBM\WebSphere_Studio\eclipse\jre\bin;F:\eclipse\301\bpelz_install\bin;f:\Oracle\product\10.1.0\Client_1\bin;f:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin\client;f:\Oracle\product\10.1.0\Client_1\jre\1.4.2\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;f:\Program_Files\IBM\WebSphere_Studio\extras\bin;f:\Program_Files\IBM\WebSphere_Studio\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre\bin;f:\Program_Files\IBM\WebSphere_Studio\runtimes\base_v51\java\jre\bin\classic;f:\Program_Files\UltraEdit;f:\Program_Files\SecureCRT;F:\PROGRA~1\IBM\SQLLIB\BIN;F:\PROGRA~1\IBM\SQLLIB\FUNCTION;F:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL;C:\Program Files\Common Files\Ulead Systems\MPEG;;;;;f:\Program_Files\Real\Helix_Producer_Plus;F:\Program_Files\Rational\common;F:\eclipse\301\bpelz_install\bin;f:\Program_Files\UltraEdit
    ************* End Display Current Environment *************
    [05-5-2 12:06:49:938 CST] 3d455614 ManagerAdmin I TRAS0017I: 启动跟踪状态是 *=all=disabled。
    [05-5-2 12:06:50:609 CST] 3d455614 AdminInitiali A ADMN0015I: AdminService 初始化
    [05-5-2 12:06:50:656 CST] 3d455614 MBeanDescript W ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    。
    [05-5-2 12:06:50:688 CST] 3d455614 WsServer E WSVR0003E: 服务器 server1 无法启动
    com.ibm.ws.exception.ConfigurationError: Problem initializing AdminImpl:
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:413)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    Caused by: com.ibm.ws.exception.ConfigurationWarning: Problem registering JVM MBean.
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:283)
    ... 11 more
    Caused by: com.ibm.websphere.management.exception.AdminException: ADMN0005E: 无法激活 MBean：类型 JVM、合作者 [email protected]c1619、配置标识 JVM 和描述符 null。
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    ... 11 more
    Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    ... 13 more
    ---- Begin backtrace for nested exception
    com.ibm.ws.exception.ConfigurationWarning: Problem registering JVM MBean.
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:283)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    Caused by: com.ibm.websphere.management.exception.AdminException: ADMN0005E: 无法激活 MBean：类型 JVM、合作者 [email protected]c1619、配置标识 JVM 和描述符 null。
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    ... 11 more
    Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    ... 13 more
    ---- Begin backtrace for nested exception
    com.ibm.websphere.management.exception.AdminException: ADMN0005E: 无法激活 MBean：类型 JVM、合作者 [email protected]c1619、配置标识 JVM 和描述符 null。
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:289)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    Caused by: com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    ... 13 more
    ---- Begin backtrace for nested exception
    com.ibm.websphere.management.exception.DescriptorParseException: ADMN0001W: 无法è¯æ³•åˆ†æž MBean 描述符文件 com/ibm/ws/management/descriptor/xml/JVM.xml。
    at com.ibm.ws.management.descriptor.MBeanDescriptorLoader.loadDescriptor(MBeanDescriptorLoader.java:106)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.loadDescriptorFile(MBeanDescriptorManager.java:260)
    at com.ibm.ws.management.descriptor.MBeanDescriptorManager.getDescriptor(MBeanDescriptorManager.java:118)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:250)
    at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactoryImpl.java:217)
    at com.ibm.ws.management.component.AdminImpl.initialize(AdminImpl.java:277)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:713)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:659)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:96)
    at com.ibm.ws.runtime.WsServer.start(WsServer.java:119)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
    at java.lang.reflect.Method.invoke(Method.java:386)
    at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
    at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
    [05-5-2 12:06:50:703 CST] 3d455614 WsServer E WSVR0009E: 启动期间发生错误
    =================================
    Best Regard.
    Musicool

    I had this issue too. I removed all non-Oracle classes (javax, org.w3c) from the jar file and things then worked as expected. Basically, these javax and w3c files were duplicating versions already existing in the WPS classpath (I presume) and were causing the failure.
    Hope this helps.
    -Tim

  • Supporting latest release of bea weblogic or ibm websphere

    Post Author: slack
    CA Forum: Migration to XI R2
    hi,
    Wondering when do you plan to plan to certified the latest release platform of BEA Weblogic 10.x or IBM WebSphere 6.1.  End of this year?
    thanks

    You can find the same under Oracle Access Manager - 3rd Party Integration.
    Linux CD2
    for Oracle_Access_Manager10_1_4_0_2_linux_BEA_WL_
    SSPI

  • J2EE APPLICATION ON OAS10G AND J2EE APPLICATION ON IBM Websphere

    Hi All,
    As you all know that there are many application servers in the market for deploying the application so I just want to know why we all choose Oracle Application Server 10g for deploying J2ee application and why some choose IBM Websphere for deploying J2ee application. Is there any doc which specifies that Deployng J2ee application on Websphere is better than OAS 10g.
    Regards
    Kumar

    If you have to choose an architecture now, I would advice not to choose Oracle Application Server, but BEA WebLogic. On Oracle Open World I learned that Oracle will stop developing on OC4J, so WebLogic seems the smarter choise.
    To either choose weblogic or websphere has to do with a lot more then just the J2EE specs. It also has to do with knowledge of your collegues (who have to support either of these products), company strategy, etc. Therefore this question cannot be answered that easy.
    Personally I think an all Oracle stack is just fine, WebLogic has a richer featureset then WebSphere (AFAIK). WebSphere is not a bad product though.

  • 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

  • * IBM Websphere Vs Oracle's Weblogic server *

    IBM Websphere Vs Oracle's Weblogic server
    Can ODI run on IBM Websphere?
    How feasible is it to shift ODI from Oracle Web logic to IBM Websphere?
    What challenges , efforts required in ODI code to do so?
    Please suggest.
    Thanks in Advance.
    Regards,
    Dinesh.

    1. Well for your 1st question I believe you can.
    2. I believe it will go fine because you just need one application server to deploy your ee agent.
    3. I have never tried IBM websphere as an application sewrver in ODI but it shouldnt be that much completed as you are thinking. Better you do R&D in your local system. Also I am not sure about the issues you will face in future. ( for ex maple PermGen errors, issues in clustering etc)
    Thanks

  • Apache Tomcat vs IBM Websphere

    Hi,
    In our current deployment, I am using Apache Tomcat as the Java Application Server that comes bundled with Hyperion Planning 9.3.1 suite of applications. The documentation also suggests Oracle Application Server, IBM Websphere and BEA WebLogic. Currently the application stack is Hyperion Planning only, with Financial Reporting for the reporting needs.
    For our current situation, we have shortlisted between using the bundled Apache Tomcat or IBM Websphere. For comparison I wanted to know how stable Apache Tomcat is in general compared to websphere? How many concurrent users can it handle? Are there any specific limitations of Apache Tomcat that I should consider? Can someone list the major pros and cons of each?
    Thanks in advance
    Shehzad

    I agree with Jake.. Tomcat can handle much more than a few users. Whether it can handle the load for your environment may depend on your usage pattern, size of forms, etc.
    We typically use Tomcat for our Dodeca product that uses the Java API to talk to Essbase. It doesn't product 'forms' but rather just transfers data via XML between the client and server. With that product, we do have one customer that is serving appx 7,000 users on a single Tomcat server. In that case, however, the usage pattern is that field users log in daily (or sometimes weekly) and run a few reports (that retrieve data via XML).
    Note that Tomcat has a configuration parameter in the server.xml file to set the max number of threads that can be spawned by the process. You may want to tune that parameter if you decide to run Tomcat in production (and absolutely be sure to give it more heapsize in the java options).
    Tim Tow
    Applied OLAP, Inc

  • Weblogic to websphere default bridge connection issues

    I have done a standalone message sender client to websphere and it is working fine. But when i use the same parameters in a destination target in a messaging bridge on weblogic I get the following error
    <1377118506218> <BEA-200043> <Bridge "Bridge-0" failed to connect to the target destination.
    I have added the following jars to the folder D:\Oracle\Middleware\user_projects\domains\base_domain\lib in my machine(which i assume is the classpath of managed server)
    1)sibc.jms.jar 2)sibc.jndi.jar 3)sibc.orb.jar
    Weblogic Destination details :
    <jms-bridge-destination>
      <name>JMS Bridge Destination-0</name>
      <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
      <classpath></classpath>
      <connection-factory-jndi-name>jms/queueConnectionFactory</connection-factory-jndi- name>
      <initial-context-factory>com.ibm.websphere.naming.WsnInitialContextFactory</initial-context-factory>
      <connection-url>iiop://192.168.56.1:2809</connection-url>
      <destination-jndi-name>jms/Queue1</destination-jndi-name>
      </jms-bridge-destination>
      <jms-bridge-destination>
      <name>JMS Source Destination-1</name>
      <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDINoTX</adapter-jndi-name>
      <classpath></classpath>
      <connection-factory-jndi-name>ConnectionFactory1</connection-factory-jndi-name>
      <connection-url>t3://localhost:7003</connection-url>
      <destination-jndi-name>Queue1</destination-jndi-name>
      </jms-bridge-destination>

    Can you please paste little more logs. Apart from what you have pasted.

  • WebLogic with WebSphere MQ as an XA resource

    I have been using WebLogic MDBs with WebSphere MQ as an external JMS provider. We just bought MQ Extended Client that would let external transaction managers do XA management with MQ. I have looked at IBM's document @
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf. This document indicates that Weblogic cannot be used to do XA with MQ; only three txn managers are mentioned - CICS, Encina, and Tuxedo.
              I don't believe that to be true because it says that it can be used with any XA compliant transaction manager. Is anyone aware of documents showing how to configure a WebLogic server (expecially MDBs) to use MQ extended client to do XA?

    WL is an XA compliant TM, and many customers use it with MQ. For more information, you can start with this FAQ:
              http://e-docs.bea.com/wls/docs81/faq/interop.html#268632
              Also see the notes I've appended below.
              Finally, you can search this newsgroup - you will see that your question comes up quite a bit.
              Tom, BEA
              JMS Integration of Foreign Vendors with BEA WebLogic Server
              The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
              For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
              JMS Integration Overview
              - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
              - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
              - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
              - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
              - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
              - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
              - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Integration with 8.1 Details
              A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
              http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
              This document refers to helpful new 8.1 features, which simplify integration. These include:
              http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
              http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
              And are also summarized here (under interoperability):
              http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Also read the MDB documentation, which extensively covers integrating foreign vendors:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
              Integration with 6.1 and 7.0 Details
              Read the "Using Foreign JMS Providers With WLS" white-paper:
              http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
              Note that this white-paper does not take into account 8.1 features.
              For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              Non-Java Integration Options
              - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs61/jcom.html
              http://e-docs.bea.com/wls/docs70/jcom/
              http://e-docs.bea.com/wls/docs81/jcom/
              - Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs81/rmi_iiop/
              http://e-docs.bea.com/wls/docs70/rmi_iiop/
              http://e-docs.bea.com/wls/docs61/rmi_iiop/
              Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
              - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
              - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
              http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
              - Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
              Notes on MQ Remote Capable XA Clients
              Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
              The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
              - Required on WLS where MQ objects are bound into JNDI:
              com.ibm.mq.jar, com.ibm.mqjms.jar
              - Required only if MQ objects are bound into JNDI on a different server:
              com.ibm.mq.jar
              If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
              Notes on Oracle AQ Integration
              If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
              http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
              Caveats:
              The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
              Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
              The solution doesn't seem to support transactions, it may be possible to extend it to do so.
              MDB Thread Pool Notes
              WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
              http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
              (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
              MDB Concurrency Notes
              Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
              Design Guide-Lines and Performance Tuning Notes
              The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
              http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp

  • WebLogic to Websphere migration issues

    Hi,
    We are migrating Java applications from BEA WebLogic 8.1 to WebSphere 6.1 as part of which we have come across few BEA WebLogice workshop specific files/features. It will be great if you could share your thoughts on possible solution/easy way of replacing these features also please share your opinin on the solutions we are thinking of.
    - Issue 1: Page Flows are being used (*.jpf file) which were generated using Weblogic Workshop which is Proprietary Tool of Bea.
    Soultion we are thinking of # 1: Page Flows can be replaced using Apache Beehive for page flows. As In this framework NETUI tags are being used so there will be only few changes in the jsps.
    Limitations/Issues: Design view of Page flows can�t be seen. Code modifications will be there as there are few changes in page flows in Beehive and page flows in Weblogic 8.1. and also It works with JDK 1.5 and our target environment Supports JDK 1.4.
    Soultion we are thinking of # 2: The other alternative can be replacing Page flows with struts.
    Limitations/Issues: Java Page Flows are built on top of Struts. If we change the page flows to struts, then there will be quite a few changes in the code as config files, action classes, formbeans need be created and also netui tags in jsp should be changed to some other taglibs in struts. And again the design view of it can�t be seen in RAD.
    Issue 2: There are few Control files like *.jcx, *.jcs, *.jws are being used in the code which are again Workshop generated. Class files will be generated if we build them in workshop but we need to migrate the development environment as well. We need to change it so that it can be compiled in RAD.
    Soultion we are thinking of # 2: These controls are being used different purposes like database controls, email controls etc.
    We are not able to find any proper way to directly create the same control in WebSphere. One way can be using Beehive controls and another way can be replacing it with Java code.
    Limitations/Issues: In both solutions there will be lots of code changes. And again design view cant be seen in RAD.
    Issue 3: There are few Process Definition (*.jpd) in the code. It�s again Bea Specific code.
    Soultion we are thinking of # 1: We searched for a same tool in WebSphere (WebSphere Business Modeler) to create process definition.
    Limitations/Issues: Learning it and recreating Process flows will again be same as rewriting of code.
    Issue 4:
    Message Broker Control are being used (created using Workshop). Based on the type of event generators used we are planning to recreate it.

    Nagaraj_Mudigal wrote:
    Hi,
    We are migrating Java applications from BEA WebLogic 8.1 to WebSphere 6.1 as part of which we have come across few BEA WebLogice workshop specific files/features. Good Lord, why would you do that? Websphere is a big step back, IMO. Why not move up to WebLogic 10.3?
    It will be great if you could share your thoughts on possible solution/easy way of replacing these features also please share your opinin on the solutions we are thinking of.Your instinct to get away from app server proprietary s/ware is a good one.
    - Issue 1: Page Flows are being used (*.jpf file) which were generated using Weblogic Workshop which is Proprietary Tool of Bea.
    Soultion we are thinking of # 1: Page Flows can be replaced using Apache Beehive for page flows. As In this framework NETUI tags are being used so there will be only few changes in the jsps.
    Limitations/Issues: Design view of Page flows can&#146;t be seen. Code modifications will be there as there are few changes in page flows in Beehive and page flows in Weblogic 8.1. and also It works with JDK 1.5 and our target environment Supports JDK 1.4.OMG. 1.4? We're up to 6 now, with 7 on the way.
    Soultion we are thinking of # 2: The other alternative can be replacing Page flows with struts.
    Limitations/Issues: Java Page Flows are built on top of Struts. If we change the page flows to struts, then there will be quite a few changes in the code as config files, action classes, formbeans need be created and also netui tags in jsp should be changed to some other taglibs in struts. And again the design view of it can&#146;t be seen in RAD.I'd recommend Spring before Struts, but Struts 2 will do.
    Issue 2: There are few Control files like *.jcx, *.jcs, *.jws are being used in the code which are again Workshop generated. Class files will be generated if we build them in workshop but we need to migrate the development environment as well. We need to change it so that it can be compiled in RAD.
    Soultion we are thinking of # 2: These controls are being used different purposes like database controls, email controls etc.
    We are not able to find any proper way to directly create the same control in WebSphere. One way can be using Beehive controls and another way can be replacing it with Java code.
    Limitations/Issues: In both solutions there will be lots of code changes. And again design view cant be seen in RAD.Code changes no matter what you do.
    Issue 3: There are few Process Definition (*.jpd) in the code. It&#146;s again Bea Specific code.
    Soultion we are thinking of # 1: We searched for a same tool in WebSphere (WebSphere Business Modeler) to create process definition.
    Limitations/Issues: Learning it and recreating Process flows will again be same as rewriting of code.I would prefer getting away from all these myself.
    Issue 4:
    Message Broker Control are being used (created using Workshop). Based on the type of event generators used we are planning to recreate it.I'd use JMS straight.
    %

  • Weblogic and Websphere IIS plugin coexistence

    Hi Folks,
    I have a customer who is planning to migrate part of their webapps from websphere to weblogic, however they would like to share the same IIS webfarm for the existing appservers farms ... I wonder if anyone know how the appservers plugins will behave if I have both BEA ISSProxy and IBM WebSphere IIS plugin on the same server ... anyone can share experience on this? Is it even supported?
    BTW ... Weblogic is 8.1SP4 and WebSphere is 5.1 ...
    Thanks,
    Juan Pablo Chen

    Sure.. why wouldn't it be?
    If you are using 1 IIS instance, which I am assuming you are, just make sure
    you load the iisproxy.dll in high isolation.
    Regards,
    Eric
    "Alan Bub" <[email protected]> wrote in message
    news:[email protected]..
    >
    I have a requirement that I run two weblogic servers on the same box. Theserver
    run the same applications except that they have different port numbers. Iwould
    like to run these both through a single IIS server. Is this possible?
    Thanks
    Alan

Maybe you are looking for

  • Photos app disappeared

    I restored my backup from 1g touch with 2.1 update onto my new 2g touch. seems okay but the photos app has disappeared. I looked back at the 1g model and it has disappeared from there too! Can anyone tell me how to get it back? I have latest firmware

  • Icloud dialogue box constantly pops up on mac air, mavericks

    This set of images is popping up every time I use my mac air.  this is a new devolpment. i am using my mac air in conjunction with ipads and an ipad mini and i do sync some things between them. i haven't made any recent changes to photos though and t

  • Itunes doesn't see pics in Aperture Folders

    When I try to sync photos from my Aperture library (on my MacBook) to my iPad, iTunes shows that some of the albums have one or zero photos in them. And when I sync, that's what I get: one or no photos from the albums. Yet these albums each have seve

  • HT201210 Iphone 6 can't complete the restore error code (56)

    I'm getting this msg : The iPhone "iPhone" could not be restored. An unknown error occurred (56). after I try all the steps in apple site to fix it but it still the same. after searching I found it stop in the last. Failed when trying to send the bas

  • Give color to canvas dynamically

    i have form and on that number os buttons calling different forms. suppose i have form aficd12.fmb and on that b1,b2,b3 buttons and they calling f1,f2,f3 forms respectively.i hane a List Items and i have given different color in that list.suppose i o