Re: WebLogic Server 7.0 is compatible with Portal4.0?

Hi.
This is not yet supported: http://edocs.bea.com/wlp/docs40/install/platforms.htm
WLS 6.1 is what you need to use.
Regards,
Michael
srikanth wrote:
Hi Everyone,
We are planning to use WebLogic Portal4.0 for our personalized portal for our clients.
As per our design and analysis, we are planning to install Portal4.0 over WebLogic
Server6.1.
But, as WebLogic Server 7.0 version is the most recent version available in the market,
we would like to take into consideration whether this version supports portal 4.0.
I greatly appreciate your help.
Regards,
Srikanth.--
Michael Young
Developer Relations Engineer
BEA Support

I am running into issues with WLp4.0 running on wls7.0. I cannot boot the server.
Would you mind sharing feedback.
Thanks
Manoj

Similar Messages

  • WebLogic Server 7.0 is compatible with Portal4.0?

    Hi Everyone,
    We are planning to use WebLogic Portal4.0 for our personalized portal for our clients.
    As per our design and analysis, we are planning to install Portal4.0 over WebLogic
    Server6.1.
    But, as WebLogic Server 7.0 version is the most recent version available in the market,
    we would like to take into consideration whether this version supports portal 4.0.
    I greatly appreciate your help.
    Regards,
    Srikanth.

    I am running into issues with WLp4.0 running on wls7.0. I cannot boot the server.
    Would you mind sharing feedback.
    Thanks
    Manoj

  • What are the SQL server versions those are compatible with XI 3.0.

    Hi All,
    Please suggest,
    what are the SQL server versions those are compatible with XI 3.0.
    or with which SQL server versions XI 3.0 will interact using JDBC Adapter.

    Check in the [Product Availability Matrix |https://websmp201.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200314690900000192]in market place for more information on this
    Thanks
    SaNv...

  • WebLogic Server 9.2 MP3 compatibility with WLS 9.2

    My companies product currently supports WebLogic Server 9.2.x.
    Is WebLogic Server 9.2 fully compatibile with WebLogic Server 9.2 MP3?
    And, what does the MP3 acronym stand for, please.
    Edited by: [email protected] on Feb 6, 2009 2:01 PM

    When your product is certified on Weblogic Server 9.2.x, it means it supports WLS 9.2.3(9.2 MP3). As David says MP3 is the Maintenance Pack Release(Bug fix).
    Generally companies would test their products on a particular weblogic version before certifying it as supported for their product.

  • Microsoft SQL Server 2012 Performance Dashboard compatible with windows server 2012?

    Is Microsoft SQL Server 2012 Performance Dashboard compatible with Windows Server 2012? I only see Windows Server 2008r2 as the most recent version in the System Requirements list. Thanks!

    Is Microsoft SQL Server 2012 Performance Dashboard compatible with Windows Server 2012? I only see Windows Server 2008r2 as the most recent version in the System Requirements list. Thanks!
    As per download documents supported windows versions are
    Windows 7, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2.
    I cannot see any mention of Windows server 2012 in system requirements
    See System Requirements 
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Is WebLogic JMS C API backwards compatible with 8.1

    I need to be able to send a JMS message from a C++ legacy application, so I am looking at using the JMS C API to do this. However, I am stuck with using WebLogic Server version 8.1. The JMS C API came out with version 9, so I am wondering if it would be possible to use it with 8.1?
              Can this be done? Thanks in advance.

    I've shot off an internal email to see if I can get an answer - I'll post again if I get one. Some notes:
              - Prior to 9.0, there was a separate C-API kit available on dev2dev which is supported (via this newsgroup only), I don't know where it is now.
              - I think its likely the 9.0 C-API will work with an 8.1 client (or 7.0 for that matter), I just don't know if this usage supported.
              - You could use the 9.2 C-API with a 9.2 client to communicate with an 8.1 server. This is definitely supported.
              Tom, BEA

  • Can weblogic server 5.1 version work with Oracle 9.2.0 thin JDBC driver?

    we have an applicaiton using weblogic 5.1 and Oracle database 8.1.6. Is that possible
    to upgrade databse version to Oracle 9i without weblogic upgrade? If yes, what
    JDBC driver should be used? Oracle 9.2.0 thin JDBC driver or weblogic jDriver?
    Is there any known issue with the JDBC driver under that architecture?
    Please help.

    Lei Zeng wrote:
    we have an applicaiton using weblogic 5.1 and Oracle database 8.1.6. Is that possible
    to upgrade databse version to Oracle 9i without weblogic upgrade? If yes, what
    JDBC driver should be used? Oracle 9.2.0 thin JDBC driver or weblogic jDriver?
    Is there any known issue with the JDBC driver under that architecture?
    Please help.Hi. Any weblogic server can be used with any JDBC driver. Just upgrade the
    JDBC driver to the latest/best one for Oracle9i, and make sure it's the first
    thing in the server's weblogic.classpath (not the java.classpath). I recommend the
    thin driver. Because it's all java, it is much more reliable. There is no known
    issue with standard JDBC with that or any other driver. Some non-standard Oracle
    calls which arer available from Oracle's driver classes are available through
    weblogic, and some are not.
    Joe Weinstein

  • Server 9.0.1 compatible with 9iR2 client?

    We plan a production environment where Oracle 9i R2 clients talk to an Oracle server 9.0.1 on VMS 7.3. However, Oracle server for VMS lacks the oramtsadmin.sql script. We consider to copy this script from a Windows distribution to VMS. Since this script is related to transaction management, we've been recommended to copy it from a 9.0.1 version on Windows.
    But: The architecture for Oracle-MTS integration has been changed from 9i R1 to 9i R2. Instead of a single recovery service in the network, a local recovery service is created on each client.
    My question: Is the script oramtsadmin.sql for 9.0.1 compatible with 9i R2 clients?
    Regards,
    Armin Seidel

    Perform the suggestions mentioned in the following articles:
    * [https://support.mozilla.com/en-US/kb/Template:clearCookiesCache/ Clear Cookies & Cache]
    * [[How to clear the cache#w_clear-the-cache|Clear the Network Cache]]
    * [[Troubleshooting extensions and themes]]
    Check and tell if its working.
    -> Update All your Firefox Plugins
    * https://www.mozilla.org/en-US/plugincheck/
    * '''When Downloading Plugins Update setup files, Remove Checkmark from Downloading other Optional Softwares with your Plugins (e.g. Toolbars, McAfee, Google Chrome, etc.)'''
    * Restart Firefox

  • How to use Weblogic Server 6.1 build.xml with ant

    Hi Java's
    I have downloaded the latest version of BEA Weblogic server 6.1,they have changed the build.cmd to build.xml for compiling and building the ejb applications.they are telling that we have use $ant to run the build.xml but i couldn't able to do that.i'm getting "command not found error"..i'm using winnt.please help me how to use $ ant.Is it a seperate exe or batch file that i have to download ?if so where to download it.how to use it.please help.
    Regards
    Balaji

    To use it after installation, set your path to your
    <ant_installation_dir>\bin, then navigate to the diectory containing the build.xml. then follow the instructions in the weblogic documentation for running ant.

  • How to Configure the Weblogic Server 6.0 Beta version with Solaris 8

    Hello,
    I have problem in starting the weblogic server 6.0 beta version.
    It is occupying hell of space and running very slow. When I try
    to deploy the bean it is throwing exception like timeout.
    Plese do suggest me what to do. and how to configure properly.
    Thank you,

    That typically happens when you have your database connections configured
    incorrectly. WebLogic is timing out on accessing the database.
    Michael Girdley
    BEA Systems Inc
    "Laxmikanth" <[email protected]> wrote in message
    news:3a35523c$[email protected]..
    >
    Hello,
    I have problem in starting the weblogic server 6.0 beta version.
    It is occupying hell of space and running very slow. When I try
    to deploy the bean it is throwing exception like timeout.
    Plese do suggest me what to do. and how to configure properly.
    Thank you,

  • Error in Weblogic Server 8.1, Works fine with 7.0

              I have an application running fine on WLS 7.0, After migration to Weblogic 8.1,
              the first page itself throws the following error: p_servlet/__home.java:18: '.'
              expected
              import DataBaseManager; //[ /home.jsp; Line: 3]
              There is a statement in home.jsp file
              <%@ page import = "DataBaseManager" %>
              This works fine for WLS7.0
              But in WLS8.1 it gives the following error
              /opt/bea/wls811/domains/devl/./server-a/.wlnotdelete/extract/server-a_fac_fac/jsp_servlet/__home.java:18:
              '.' expected
              probably occurred due to an error in /home.jsp line 3:
              <%@ page import = "DataBaseManager" %>
              If I put this class DataBaseManager in a folder "com", then I gave
              <%@ page import = "com.DataBaseManager" %>
              This works fine in 8.1.
              So whats the problem. IS Package Structure mandatory.
              PLs. Help
              

    From http://java.sun.com/j2se/1.4/compatibility.html:
              The compiler now rejects import statements that import a type from the unnamed
              namespace. Previous versions of the compiler would accept such import
              declarations, even though they were arguably not allowed by the language
              (because the type name appearing in the import clause is not in scope). The
              specification is being clarified to state clearly that you cannot have a simple
              name in an import statement, nor can you import from the unnamed namespace.
              To summarize, the syntax
              import SimpleName;
              is no longer legal. Nor is the syntax
              import ClassInUnnamedNamespace.Nested;
              which would import a nested class from the unnamed namespace. To fix such
              problems in your code, move all of the classes from the unnamed namespace into a
              named namespace.
              Rajesh Chande wrote:
              > Hi Nagesh,
              >
              > If this is the case, then that requires a lot of recoding for developers that
              > developed application on JDK Version less than 1.4, So I would strongly request
              > you to give me the source of your statement in java language specification or
              > on Java Sun Site.
              >
              > Thanks.
              >
              > Rajesh.
              >
              > "Rajesh Chande" <[email protected]> wrote:
              >
              >>Thanks a lot, Nagesh for this valuable input, where can i get this information
              >>documented in jdk1.4, that would be very helpful, if u provide me with
              >>this info.
              >>
              >>Thanks once again.
              >>
              >>Regards,
              >>
              >>Rajesh.
              >>
              >>"Nagesh Susarla" <[email protected]> wrote:
              >>
              >>>This actually has to do with javac's behavior in 1.4.x. Javac (jdk1.4.x
              >>>onwards) doesnt support the dependencies of a default packaged class
              >>>in a
              >>>packaged class. (This was supposedly a bug in the earlier versions and
              >>>against the jls i think)
              >>>Since 8.1 uses 1.4 you see it only in 81. So any class w/o a package
              >>>cannot
              >>>be used in a jsp (which is compiled into a package jsp_servlet by default)
              >>>
              >>>--Nagesh
              >>>
              >>>
              >>>"Rajesh Chande" <[email protected]> wrote in message
              >>>news:[email protected]...
              >>>
              >>>>I have an application running fine on WLS 7.0, After migration to
              >>
              >>Weblogic
              >>
              >>>8.1,
              >>>
              >>>>the first page itself throws the following error:
              >>>
              >>>p_servlet/__home.java:18: '.'
              >>>
              >>>>expected
              >>>>import DataBaseManager; //[ /home.jsp; Line: 3]
              >>>>
              >>>>There is a statement in home.jsp file
              >>>>
              >>>><%@ page import = "DataBaseManager" %>
              >>>>
              >>>>This works fine for WLS7.0
              >>>>
              >>>>But in WLS8.1 it gives the following error
              >>>>
              >>>>
              >>>
              >>>/opt/bea/wls811/domains/devl/./server-a/.wlnotdelete/extract/server-a_fac_fa
              >>>c/jsp_servlet/__home.java:18:
              >>>
              >>>>'.' expected
              >>>>probably occurred due to an error in /home.jsp line 3:
              >>>><%@ page import = "DataBaseManager" %>
              >>>>
              >>>>If I put this class DataBaseManager in a folder "com", then I gave
              >>>><%@ page import = "com.DataBaseManager" %>
              >>>>
              >>>>This works fine in 8.1.
              >>>>
              >>>>So whats the problem. IS Package Structure mandatory.
              >>>>
              >>>>PLs. Help
              >>>
              >>>
              >
              scott dunbar
              bea systems, inc.
              boulder, co, usa
              

  • Is Netscape Enterprise Server 3.5.1 compatible with the SunOne Application Server 7.0 ?

    I want to use NES 3.5.1 instead of the IPlanet web server that comes with SunOne App Server. Will the two work together? If yes are there documentations somewhere?

    Hi,
    I beleive that there is no concept seperate webserver getting configured with App server. Appserver 7.0 comes with a builtin webservices as like weblogic and wesphere.
    Regards,
    Dakshin.
    Developer Technical Support
    Sun Microsystems
    http://www.sun.com/developers/support.

  • SQL Server 2008/2008 R2 compatiblity with Cold Fusion 5.0

    Our Cold Fusion Server is on Version 5.0 and database server is running SQL 2000. DBA's like to upgrade SQL Server to 2008/ R2. Is there any known issues in running or upgrading from Cold Fusion 5.0 with SQL Server 2008/R2 ?
    Please let me know.
    Thanks
    Suresh Kumar

    If you're looking at spending thousands on a SQL licence, has no-one considered buying a CF9 license? You'd save yourself a whole world of pain, and could then have a full 64-bit environment for your application which is tried and tested.

  • Inqmy resource adapter for SAP with Bea Weblogic Server

              Hi everybody,
              Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic server
              It works well with INQMY server, but with BEA I'm getting a lot of problems creating
              the connections.
              Thanks in advance.
              Xavi.
              

    All,
              Here are the steps we (used for internal testing) had to perform to get
              IN-Q-MY adapter for SAP to work with WebLogic:
              The wli.adapter.inqmy.sapr3.spi package contains extensions to the
              In-Q-My J2EE Connector Architecture classes to overcome some limitations
              in the base implementation classes. To get around these issues, we had
              to extend their R3ManagedConnectionFactory, R3ConnectionManager, and
              R3ConnectionFactory classes.
              * The javax.resource.spi.ManagedConnectionFactory implementation
              does not over-ride the equals and hashCode methods correctly. This
              causes problems with WLS 6.1.
              * There is a bug in their javax.resource.spi.ConnectionManager
              implementation for non-managed uses of the adapter. Consequently, their
              adapter cannot be used in a non-managed scenario.
              * The javax.resource.cci.ConnectionFactory class does not support
              the getConnection() method that does not take any arguments (it throws a
              null pointer exception).
              I am attaching the classes discussed above.
              Cheers,
              Chris
              Torsten Friebe wrote:
              > Hi,
              >
              > does anybody know where to get a trail version - if one exists - of IN-Q-MY
              > application server or the resource adapter?
              >
              > Thanks, regards
              > Torsten
              >
              > "Xavi" <[email protected]> schrieb im Newsbeitrag
              > news:[email protected]...
              >
              >>Hi everybody,
              >>
              >>Anybody have tried to use INQMY resource adapter for SAP with Bea weblogic
              >>
              > server
              >
              >>?
              >>
              >>It works well with INQMY server, but with BEA I'm getting a lot of
              >>
              > problems creating
              >
              >>the connections.
              >>
              >>Thanks in advance.
              >>Xavi.
              >>
              >>
              >
              >
              package wli.adapter.inqmy.sapr3.spi;
              import java.io.Serializable;
              import javax.resource.ResourceException;
              import javax.resource.cci.Connection;
              import javax.resource.cci.ConnectionSpec;
              import javax.resource.spi.ConnectionManager;
              import javax.resource.spi.ConnectionRequestInfo;
              import javax.resource.spi.ManagedConnection;
              import javax.resource.spi.ManagedConnectionFactory;
              import com.inqmy.r3adapter.R3ConnectionSpec;
              import com.inqmy.r3adapter.R3ManagedConnectionFactory;
              * Extends the In-Q-My implementation to allow for getConnection() with no
              * connection spec, i.e. use the default configured connection parameters.
              public class R3ConnectionFactory
              extends com.inqmy.r3adapter.R3ConnectionFactory
              implements com.bea.connector.IProxyMarker {
              private R3ConnectionSpec m_cspec;
              public R3ConnectionFactory(ConnectionManager cm, R3ManagedConnectionFactory mcf)
              throws ResourceException {
              super(cm, mcf);
              String strClientNumber = mcf.getClientNumber();
              if (strClientNumber == null) {
              throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+mcf);
              String strLanguage = mcf.getLanguage();
              if (strLanguage == null) {
              throw new javax.resource.spi.IllegalStateException("Language not set for "+mcf);
              String strUserName = mcf.getUserName();
              if (strUserName == null) {
              throw new javax.resource.spi.IllegalStateException("UserName not set for "+mcf);
              String strPassword = mcf.getPassword();
              if (strPassword == null) {
              throw new javax.resource.spi.IllegalStateException("Password not set for "+mcf);
              m_cspec = new R3ConnectionSpec(strClientNumber, strLanguage, strUserName, strPassword);
              public Connection getConnection(ConnectionSpec connectionSpec)
              throws ResourceException {
              if (connectionSpec == null) connectionSpec = m_cspec;
              return super.getConnection(connectionSpec);
              package wli.adapter.inqmy.sapr3.spi;
              import java.io.Serializable;
              import javax.resource.ResourceException;
              import javax.resource.spi.ConnectionManager;
              import javax.resource.spi.ConnectionRequestInfo;
              import javax.resource.spi.ManagedConnection;
              import javax.resource.spi.ManagedConnectionFactory;
              * Extends the In-Q-My implementation to over-ride the
              * allocateConnection method to return a CCI connection vs. a ManagedConnection
              public class R3DefaultConnectionManager
              implements ConnectionManager, Serializable {
              public R3DefaultConnectionManager() {}
              public Object
              allocateConnection(ManagedConnectionFactory mcf, ConnectionRequestInfo cri)
              throws ResourceException {
              ManagedConnection mc = mcf.createManagedConnection(null, cri);
              return mc.getConnection(null, cri);
              package wli.adapter.inqmy.sapr3.spi;
              import javax.resource.spi.ConnectionManager;
              import javax.resource.spi.ConnectionRequestInfo;
              import javax.resource.spi.ManagedConnection;
              import javax.security.auth.Subject;
              * Extends the In-Q-My implementation to get around some problems encountered
              * while running on WebLogic:
              * <ul>
              * <li>Must over-ride default implementation of equals and hashCode method</li>
              * <li>Needed to provide my version of the CCI ConnectionFactory</li>
              * <li>Needed to provide my version of the default ConnectionManager for the
              * non-managed scenario use case</li>
              * </ul>
              public class R3ManagedConnectionFactory
              extends com.inqmy.r3adapter.R3ManagedConnectionFactory {
              private int m_iHashCode;
              transient private com.inqmy.r3adapter.R3ConnectionRequestInfo t_cri = null;
              public R3ManagedConnectionFactory() {
              super();
              java.rmi.server.UID uid = new java.rmi.server.UID();
              m_iHashCode = uid.hashCode();
              public Object createConnectionFactory() {
              // need to install our own default connection manager because In-Q-My
              // version causes a ClassCastException in CCI ConnectionFactory
              // getConnection
              return createConnectionFactory(new R3DefaultConnectionManager());
              public ManagedConnection createManagedConnection(Subject subject, ConnectionRequestInfo cri)
              throws javax.resource.ResourceException {
              // need to check for null on the ConnectionRequestInfo object because the
              // In-Q-My R3ManagedConnection ctor does not check for null
              if (cri == null) cri = getDefaultConnectionRequestInfo();
              return new com.inqmy.r3adapter.R3ManagedConnection(this, subject, cri);
              public Object createConnectionFactory(ConnectionManager connectionManager) {
              // need to supply a connection factory that can deal with getConnection
              // that does not take a ConnectionSpec
              try {
              return new R3ConnectionFactory(connectionManager, this);      
              } catch (javax.resource.ResourceException re) {
              re.printStackTrace();
              throw new java.lang.IllegalStateException(re.getMessage());
              com.inqmy.r3adapter.R3ConnectionRequestInfo getDefaultConnectionRequestInfo()
              throws javax.resource.spi.IllegalStateException {
              if (t_cri == null) {
              String strClientNumber = this.getClientNumber();
              if (strClientNumber == null) {
              throw new javax.resource.spi.IllegalStateException("ClientNumber not set for "+this);
              String strLanguage = this.getLanguage();
              if (strLanguage == null) {
              throw new javax.resource.spi.IllegalStateException("Language not set for "+this);
              String strUserName = this.getUserName();
              if (strUserName == null) {
              throw new javax.resource.spi.IllegalStateException("UserName not set for "+this);
              String strPassword = this.getPassword();
              if (strPassword == null) {
              throw new javax.resource.spi.IllegalStateException("Password not set for "+this);
              t_cri = new com.inqmy.r3adapter.R3ConnectionRequestInfo(strClientNumber, strLanguage, strUserName, strPassword);
              return t_cri;
              public boolean equals(Object obj) {
              if (obj == null) return false;
              if (obj == this) return true;
              if (!this.getClass().isInstance(obj)) return false;
              R3ManagedConnectionFactory mcf = (R3ManagedConnectionFactory)obj;
              return compare(getClientNumber(), mcf.getClientNumber()) &&
              compare(getLanguage(), mcf.getLanguage()) &&
              compare(getUserName(), mcf.getUserName()) &&
              compare(getPassword(), mcf.getPassword()) &&
              compare(getServerName(), mcf.getServerName()) &&
              compare(getSystemNumber(), mcf.getSystemNumber());
              protected final boolean compare(final Object obj1, final Object obj2) {
              if (obj1 == obj2) return true;
              if (obj1 != null) {
              return obj1.equals(obj2);
              } else {
              if (obj2 == null) {
              return true;
              } else {
              return false;
              public int hashCode() { return m_iHashCode; }
              

  • Is Sun Java Web Server 6.1 compatible with RedHat 5.5

    Hi,
    Sun Java web Server 6.1 installed on Red Hat 5.1 and Opertaing System is going to be upgraded to Red Hat 5.5. Can any one tell me whether Sun Java Web Server 6.1 is compatible with Red Hat Linux 5.5

    If you want the internal server to service requests for /admin, you should teach the internal server to service requests for /admin.
    It is possible -- but complicated -- to configure Web Server 6.1 to rewrite request URIs before proxying requests to the internal server. However, unless you rewrite all the HTML generated by the internal server, the results probably won't be what you want. Consider, for example, what happens if the internal server's HTML references /foo.gif. Does that mean the web browser should ask for /admin/foo.gif or /foo.gif?
    Rewriting request URIs is much simpler in Web Server 7.0, but it's still probably not the right tool.

Maybe you are looking for