ANNOUNCE: BEA WLS 6.0 Beta available

ANNOUNCE: BEA WLS 6.0 Beta available
We are proud to announce that the BEA WebLogic Server version 6.0 public
beta has begun. You can download the Beta at http://commerce.BEA.com. The
Beta is free and open to anyone.
More information can be found at the above URL.
Thanks,
Michael
Michael Girdley
BEA Systems Inc

Hi,
          why wasn't that email sent to weblogic.announce??
          I'm starting to believe weblogic.annouce is truly useless since neither
          service packs nor betas are announced there. What is the official way of
          monitoring releases of SP,etc. from bea?
          Mathieu
          Michael Girdley wrote:
          >
          > ANNOUNCE: BEA WLS 6.0 Beta available
          >
          > We are proud to announce that the BEA WebLogic Server version 6.0 public
          > beta has begun. You can download the Beta at http://commerce.BEA.com. The
          > Beta is free and open to anyone.
          >
          > More information can be found at the above URL.
          >
          > Thanks,
          > Michael
          >
          > --
          > ----
          > Michael Girdley
          > BEA Systems Inc

Similar Messages

Announcement: BEA WLS 6.1 available for download; beta complete

The beta program is now over. BEA WebLogic Server 6.1 is available for download
from BEA's web site:
http://commerce.bea.com/downloads/products.jsp
Thank you for your participation in the beta program. Your input helps BEA improve
their products.
Lauren Wright
Product Manager
BEA

In article <174_3b672c9e$[email protected]>, [email protected]
says...
>
The beta program is now over. BEA WebLogic Server 6.1 is available for download
from BEA's web site:
http://commerce.bea.com/downloads/products.jsp
Thank you for your participation in the beta program. Your input helps BEA improve
their products.
Lauren Wright WLS Product Manager
When will WLS v6.1 GA be available for Redhat Linux v7.1?
Many thanks,
mark
"We want a few mad people now. See where the sane ones have landed us!"
George Bernard Shaw (1856-1950)

[announce] DataDirect XQuery� Beta Available

XQuery offers SOA archiectures a unique ability to leverage relational database deployments to aggregate a distributed data sources that are needed to elevate an application to the requirements of Services based applications. To this end, the XQJ API enables the Java platform to query XML datasources, in concert with the JBI specification to bring all resources to bear for a successful SOA deployment.
The first XQuery component to implement the XQuery API for Java� (XQJ), DataDirect XQuery�, is now available in beta. DataDirect XQuery allows you to query XML, relational databases, or a combination of the two and integrate the results for any XML you need. It does not require any other product or application server, and has no server of its own � making it easily embeddable into your applications. You can use the beta to process XQuery expressions against Oracle, Microsoft SQL Server and IBM DB2, directly from within your Java applications. Get started today with XQuery and XQJ using the beta release of DataDirect XQuery. Register and learn more about the beta program at
http://www.datadirect.com/products/xquery/xquerybetahome/
XQuery Developer Resources
http://www.datadirect.com/developer/xquery/index.ssp
Blogs: XQuery Adoption Central
http://blogs.datadirect.com

I found it, never mind...
Jason
Jason Rosenberg <[email protected]> wrote in message news:8i3ha1$cam$[email protected]..
I can't seem to find the download from the link provided...
Can you clarify the url?
Thanks,
Jason
Michael Girdley <[email protected]> wrote in message news:8htsbt$jaf$[email protected]..
VisualAge WebLogic Integration Beta Available
Download today at commerce.beasys.com
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc

WTC Beta available

Hello all,
WTC, which is product that connects Weblogic Server to Tuxedo via the
domains protocol is now available for evaluation in Beta mode.
This product has the following features:
1. Supports Tuxedo 6.5 and Tuxedo 8.0 (which is also available for Beta)
2. Runs on WLS 6.0 SP1
3. Has an ATMI java interface (jatmi). Yes, tpcall, tpacall, tpenqueue,
tpdequeue etc. from java
4. Tuxedo clients can invoke WLS EJB's (bi-directional)
5. Transaction support if the transaction is started in WLS (This is a
real, ACID transaction where WLS is the coordinator...)
6. Many of the domains failover features and connection policies are
supported.
If you are interested, you must contact your BEA reprentative because the
Beta is only available on a password protected newsgroup. (You'll have to
sign a Beta agreement - not for use in production, support only on the
newsgroup, blah, blah, blah...)
John Wells (Aziz)
[email protected]

It will eventually, but you will need a patch for TUXEDO 7.1, and that
is in the process of being finalized. If you sign up for the beta, you
can get the details.
[email protected] wrote:
>
So it doesn't work with 7.1 ?!?

How to setup IBM Trade2 on WLS 6.1 Beta???

Hi all,
I'm currently trying to deploy the IBM Trade2 benchmark application
on WLS 6.1 Beta following the instructions published by BEA.
Unfortunately I still get some error messages and Trade2 does not
work.
Therefore, I would like to know if someone has successfully
deployed Trade2. If yes, could you please send me your EAR file,
the config.xml and the WebLogic start script, so that I can use
it for my tests?
Many thanks for your help and best regards,
Erwin

Looking through the WLS log, notice that the run-time parameter is set with
a Run-Time-Mode of "EJB". This uses IBM's VAJ access beans and does not
work with WLS.
To change:
1. Go to "Configure Trade run-time parameters" page at
http://localhost:7001/WebSphereSamples/TradeSample/servlet/TradeConfigServlet.
There is a link to this page under the "Configuration" section.
2. Set Run-Time Mode to "EJB_ALT".
3. Update Config.
Also, remember to populate the Trade Database.
==============================================
Erwin Tenhumberg wrote:
Hello Srikant,
here is an extract from the WLS log.
Many thanks and best regards,
Erwin
^C# ./startWebLogic.sh
LD_LIBRARY_PATH=/usr/oracle/product/8.1.6/lib:/usr/java/jre/lib::/usr/iplanet/ias6/ias/gxlib:/bea/wlserver6.1_beta/lib/solaris:/bea/wlserver6.1_beta/lib/solaris/oci816_8
* Starting Server *
* To start the server, use the password assigned *
* to the "system" user *
* When accessing the WebLogic Server console *
* from the browser, use the same password when *
* prompted. The username is "system". *
<Jul 23, 2001 2:08:30 PM PDT> <Info> <Security> <Getting boot password
from user.>
Enter password to boot WebLogic server:weblogic
Starting WebLogic Server ....
<Jul 23, 2001 2:08:37 PM PDT> <Notice> <Management> <Loading
configuration file
./config/mydomain/config.xml ...>
<Jul 23, 2001 2:08:42 PM PDT> <Info> <Logging> <Only log messages of
severity "Error" or worse
will be displayed in this window. This can be changed at Admin
Console> mydomain> Servers>
myserver> Logging> General> Stdout severity threshold>
New Trade Log
InitTime Mon Jul 23 14:10:08 PDT 2001
Current Time Mon Jul 23 14:10:08 PDT 2001
Severity Level 0
Reporting Level 4
PrintMessages false
MESSAGE
TradeConfig setting parameter:
JDBC_PWD
=
MESSAGE
TradeConfig setting parameter:
RunTimeMode
=
EJB
MESSAGE
Clearing Quote Cache
MESSAGE
TradeConfig setting parameter:
JDBC_UID
=
MESSAGE
TradeConfig setting parameter:
MaxQuotes
=
500
MESSAGE
TradeConfig setting parameter:
MaxUsers
=
500
MESSAGE
TradeConfig setting parameter:
WorkLoadMix
=
Standard
MESSAGE
TradeConfig setting parameter:
WebInterface
=
JSP
<Jul 23, 2001 2:10:08 PM PDT> <Notice> <WebLogicServer> <ListenThread
listening on port 7001>
<Jul 23, 2001 2:10:08 PM PDT> <Notice> <WebLogicServer>
<SSLListenThread listening on port
7002>
<Jul 23, 2001 2:10:08 PM PDT> <Notice> <WebLogicServer> <WebLogic
Server started>
MESSAGE
trade_client.TradeAction.doRegister(..): using TradeExceptionWrapper
to wrap and thow an
exception
EXCEPTION
**DATE:
Mon Jul 23 14:11:27 PDT 2001
**COMMENTS:
[trade_client.TradeServletAction.doRegister(...), Error registering
userIDtestfowarding to an
error page, severity of exception = 10: Fatal Server Exceptions only]
**MESSAGE:
trade_client.TradeAction.doRegister(..)--trade_client.TradeAction.doRegister(..)--PARAMETERS:*userIDtest--passwd:test--fullname:Erwin
Tenhumberg--*smail:555 Middelfield
Road--email:[email protected]:123-fake-ccnum-456--*money:
10000.0--trade_client.TradeAction.doRegister(..)--trade_client.TradeAction.doRegister(..)--PARAMETERS:*userIDtest--passwd:test--fullname:Erwin
Tenhumberg--*smail:555 Middelfield
Road--email:[email protected]:123-fake-ccnum-456--*money:
10000.0--
**LOCALMESSAGE:
trade_client.TradeAction.doRegister(..)--trade_client.TradeAction.doRegister(..)--PARAMETERS:*userIDtest--passwd:test--fullname:Erwin
Tenhumberg--*smail:555 Middelfield
Road--email:[email protected]:123-fake-ccnum-456--*money:
10000.0--
**STACKTRACE:
javax.naming.InvalidNameException: url does not contain a port
at trade.TradeExceptionWrapper.<init>(TradeExceptionWrapper.java:24)
at trade_client.TradeAction.doRegister(TradeAction.java:427)
at trade_client.TradeAction.doRegister(TradeAction.java:484)
at trade_client.TradeServletAction.doRegister(TradeServletAction.java:1138)
at trade_client.TradeAppServlet.performTask(TradeAppServlet.java:125)
at trade_client.TradeAppServlet.doGet(TradeAppServlet.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:245)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2279)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1923)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Srikant Subramaniam <[email protected]> wrote in message news:<[email protected]>...
What error messages are you seeing? Can you pl post them here?
Srikant.
Erwin Tenhumberg wrote:
Hi all,
I'm currently trying to deploy the IBM Trade2 benchmark application
on WLS 6.1 Beta following the instructions published by BEA.
Unfortunately I still get some error messages and Trade2 does not
work.
Therefore, I would like to know if someone has successfully
deployed Trade2. If yes, could you please send me your EAR file,
the config.xml and the WebLogic start script, so that I can use
it for my tests?
Many thanks for your help and best regards,
Erwin
Srikant, [email protected], http://weblogic.bea.com/, etc.

JAX-WS SOAPHandler can not deployed in BEA WLS 10.0 - Bug?

Hi,
currently I'm trying tp deploy a simple JAX-WS webservice with JAX-WS SOAPHandler in BEA WLS 10.0.
Therefore I provide a WAR file with the webservice and handler classes.
The SOAP Handler is defined in the webservice via the @HandlerChain(file="handler.xml")
My handler.xml looks as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<javaee:handler-chains xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<javaee:handler-chain>
<javaee:handler> <javaee:handler-class>com.bmw.wss.server.handler.AuthenticationHandler</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
</javaee:handler-chains>
This handlers.xml is in the classpath within the WAR file.
If i trying to deploy this WAR file I always get the following exception from BEA WLS 10:
weblogic.application.ModuleException: [HTTP:101216]Servlet: "WSAATestService" failed to preload on startup in Web application: "wsaa-jaxwshandlertest.war".
java.lang.NullPointerException
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsHandlers(WseeRuntimeMBeanManager.java:108)
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsPort(WseeRuntimeMBeanManager.java:80)
at weblogic.wsee.monitoring.WseeRuntimeMBeanManager.createJaxWsMBean(WseeRuntimeMBeanManager.java:57)
I seems BEA WLS 10 has some problems with the JAX-WS SOAPHandler. I've deployed the same WAR-file on a Glassfish v2 server... without any problems!
Does anyone already used the JAX-WS handler mechanism in BEA WLS 10? Any ideas?
Thx.

Hi,
thx for your answer. Now I've found the problem. The BEA WLS don't accept null return value of the SOAPHandler method getHeaders(). If I return a dummy object everything wotks fine:
public Set<QName> getHeaders() {
return new TreeSet<QName>();
However I think this behaviour of the BEA WLS 10 is some kind of strange. Why do I have to implement the method getHeaders() if I don't want to use it.
Sun's Glassfish allows a null return value like expected.

What BEA WLS for Oracle 10.2.0.4?

Hi,
I'm going migration DB from 9.2.0.6 with BEA WLS 8.1 SP2 to 10.2.0.4 and I would like what's the certificate version of BEA WLS target.
Thanks!

You have already posted this in the correct forum - Upgrade Oracle DB from 9.2.0.6 to 10.2..0.4
This forum is meant for issues related to database upgrades - pl clarify your question in your other post. AFAIK, there is no co-relation between database upgrades and WLS upgrades - but I have no expertise in WLS
HTH
Srini

BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

Hello anybody,
learnt XA being necessary if more than one sql command in transaction, so I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now I receive the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
start() failed on resource 'OracleDB' Unexpected error during start for XAResource
'OracleDB': null
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.deploy(Application.java:247)
     at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
     at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
     at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

Hi Klaus,
if you want to implement a global transaction over two different JDBC Resource Managers
(update on both + 2PC) they have to be both XA compliant.
Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
and configuring a TXDataSource with "enable two-phase commit" = true (but only one
non-XA JDBC driver at a time can participate in a distributed transaction).
Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
transactions or distributed transactions without XA drivers as well (using a single
resource manager).
But if you want to update multiple resource managers in the same transaction using
EJBs, this is a "global" transaction, and WL server fully supports it.
But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
Sergi
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
>
Hi Sergi, hello world,
thanks a lot for this message. So the conclusion is that I hava no chance
at all
to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
a prerequisite
for EJB are XA-transactions.
Is this conclusion correct.
Many thanks again
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
distributed transaction (XA) features require version
Oracle8i release 8.1.6 or later of the Oracle server.
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hi Sergi,
1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
2.) I didn´t use a special driver but that that was delivered with thewls
server
in the package "weblogic.jar".
Could I enable you helping me with this information?
Best wishes
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
which
1) Oracle server version (I don't think it's a 8.3.2.)
2) Oracle JDBC driver version
are you you using ?
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hello anybody,
learnt XA being necessary if more than one sql command in transaction,so
I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now
I
receive
the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating itsSQL
Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction
branch
start() failed on resource 'OracleDB' Unexpected error during start
for
XAResource
'OracleDB': null
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.deploy(Application.java:247)
     at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
     at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
     at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?

Hello
Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?
Thanks

Hi a,
The short answer is no B or R yet, but stay tuned.
The somewhat longer story is that we are very much engaged with this
emerging binding standard to be used inconjuction with and beyond the
built-in types specified in JAX-RPC 1.1, it should be seen as a
compelling story for J2EE if JAXB could be used as a mechanism for
extending type mapping and offer a vendor neutral way to deal with user
defined types and to easily utilize user types that are developed for
XML applications in web services.
Concerning JAXR, I've experimented with SUN's RI using our UDDI server
and it works fine. As to the arguable merits of JAXR, all I can say is
that it is part of J2EE 1.4.
HTHs,
Bruce
a wrote:
>
Hello
Does BEA WLS 7.0 or 8.1 support JAXB and JAXR?
Thanks

Autonomy integration in BEA WLS 9.2

I am trying to use the Autonomy portlets with BEA WLS 9.2. To do so I have followed the instructions at
http://edocs.bea.com/wlp/docs92/search/searchdev.html.
After successfully going through the indicated steps, the portlets do not deploy because of unmet dependencies for the following packages:
* com.autonomy.client
* com.autonomy.portlet
* com.autonomy.APSL
Where can I find the jar file that contains these packages?

Seems like you might have missed step 4 in the Autonomy Portlet installation instructions at http://edocs.bea.com/wlp/docs92/search/searchdev.html#wp1026209
These classes are found in AutonomyPiB.jar, which inside of the AutonomyPortlets.zip file. This jar file should be placed in your EAR's APP-INF/lib directory.
I hope this helps.

Which BEA WLS version (+ service packs) used which JDK/JRockit-JDK version

Hello,
I'm looking for an overview about the JDK and JRockit JDK versions which are used in the different BEA WLS versions.
Specialy im interested on all BEA WLS server versions (incl. the different Service Packs) starting with version 7.0.
The overview should contain the following information if possible:
- BEA WLS Version Number including SP
- Plattform (Windows, HPUX, Solaris, ...)
- JDK version
- JRockit JDK version
Here is an example (??? = I do not know currently):
WLS vers. (incl. SP)|Plattf.|JDK vers.|JRockit vers.
7.0.1 |Solaris|??? |???
8.1.5 |Windows|1.4.2_08 |rockit81sp5_142_08
9.2 MP1 |HPUX |??? |???
Thanks a million if somebody could provide me those information. :-x
Cheers,
Markus Jessl

Please check :
http://edocs.bea.com/platform/suppconfigs/index.html
Jin

BEA WLS 6.0 Install Error

Thanks Charlie,
I hadn't subscribed to the 'install' group and therefore didn't know it
existed.
Mica
"Charlie Therit" <[email protected]> wrote in message
news:[email protected]..
It seems like this problem would be better addressed under the "install"
newsgroup as it doesn't seem to pertain to our Enterprise product.
We'll see what happens.
-Charlie
Mica Cooper wrote:
I am trying to install the WLS 6.0 Beta on a test machine and it fails.
As
soon as InstallAnywhere is done doing its 'preparing to install', the
install completely disappears. What should I do? I tried running the
install.exe but that fails also.
The test machine is a dual 500 NT4sp6 machine. It has a running copy of4.52
on it that I am going to transfer over.
Thanks,
Mica Cooper

BEA-473013: Aggregation Server Not Available

Can anyone tell the reason for these messages that I observe (every 60 seconds) in the stdout logs?
<Dec 29, 2010 9:08:00 AM CST> <Error> <ALSB Statistics Manager> <BEA-473013> <Aggregation Server Not Available>
<Dec 29, 2010 9:09:00 AM CST> <Error> <ALSB Statistics Manager> <BEA-473013> <Aggregation Server Not Available>
The server is part a Weblogic 10.3.x cluster. Unfortunately, the documentation online does not provide a cause for this BEA error code - http://download.oracle.com/docs/cd/E15523_01/apirefs.1111/e14397/Statistics.html

May be this can help you
http://prabodh-mitra.blogspot.com/2011/02/aggregation-server-not-available.html

BEA WLS and OraclePoolConnection

Hi,
Using the Oracle (9i) JDBC OCI driver, i am trying to get a proxy
connection going in BEA WLS.
If i define the connection pool using the Oracle classes in my program
everything is fine (i can get a connection and then proxy as as another
user). But if I define the pool using the Weblogic console then I have a
ClassCastException after doing a the lookup().
InitialContext initial = new InitialContext();
// HERE the classcastexception :
OracleOCIConnectionPool ds =
(OracleOCIConnectionPool) initial.lookup("jdbc/OracleOciDS");
oracle.jdbc.OracleConnection conn = null;
Properties p = new Properties();
p.setProperty(PROXY_USER_NAME, username);
conn = ds.getProxyConnection( PROXYTYPE_USER_NAME, p);
OracleOciDS is an OCI Connection pool (defined via the WLS console) and it's
working ok if I don't try to use the ProxyConnection mechanism of the JDBC
OCI.
If I do everything "by hand" without defining the Datasource in the BEA WLS console (using Oracle example), it's ok but the best would be to use the BEA console to do the administration and monitoring of the pool.
Thanks.
Real Gagnon from Quebec, Canada
* Looking for Java or PowerBuilder snippets ? Visit Real's How-to
* http://www.rgagnon.com/howto.html
* http://www.rgagnon.com/bigindex.html

Hi,
I am facing the same problem. Any luck on this?

Why "Announcement: iPhoto update 7.0.1 available now" in iPhoto '08 forum?

Why is the "Announcement: iPhoto update 7.0.1 available now" in iPhoto '08 forum?

good question.
Here we have the iPhoto 08 forum. But if you look at the About iPhoto listing (iPhoto Menu -> About iPhoto), you'll see that what we have is iPhoto 08 (version 7).
Clear? How about, iPhoto 08 is version 7 of iPhoto. See? That's not confusing in the least.
But that's why the announcement is there.
Regards
TD

ANNOUNCE: BEA WLS 6.0 Beta available

Similar Messages

Maybe you are looking for