Configure Weblogic-specific settings using annotations in EJB3?

Hello.
Something that really bothers me about using EJB3 in Weblogic is that, in our projects (running in Weblogic 10.0), we need to configure Weblogic-specific settings in weblogic-ejb-jar.xml anyway. Things like work managers, JNDI names and security (the latter doesn't work if we just declare it in a spec annotation, we need to also define it in weblogic-ejb-jar.xml).
It's hard to understand the point of migrating to EJB3 when you can just do half the things using annotations.
Does Weblogic have extensions to help on that? I never found anything related to this for Weblogic 10.0.
Thanks.

The link is interesting, thanks. There are only a few weblogic-specific annotations, but at least it's a start. Unfortunately, it seems to only be available in 10.3.
About EJBGen, from what I investigated in the past, it would only work well with EJB2 (to generate the weblogic-ejb-jar content, you also have to use EJB2 annotations that were deprecated by EJB3 annotations - if you do this, you will end up with spaghetti code, in my humble opinion).
Regards,

Similar Messages

How to configure weblogic 451 to use Nes 4.1

Am trying to use iPlanet 4.1(NES as webserver) and redirect all the
          request to weblogic(451), am using solaris 7, service pack 13.
          i have configured a servlet to respond requests in port 80 in
          weblogic, and in iPlanet(NES) have configured, in a server instance the
          file obj.conf to use the NSAPI plug in .
          ··························obj.conf·····················································································
          Init fn="load-modules" funcs="wl-proxy,wl-init"\
          shlib=/opt/Weblogic/libsp13/libproxy.so
          Init fn="wl-init"
          <Object name="weblogic" ppath="*/myservlet/*">
          Service fn=wl-proxy WebLogicHost=xxx.xxx.xxx.xxx WebLogicPort=80
          </Object>
          this server instance is listening for request in port 8080.
          htpp://xxx.xxx.xxx.xxx:8080/myservlet
          Some fails in NSAPI plug-in configuration on NES, because the request
          never obtain a retrieve.
          NES never send the request to weblogic.
          Need i configure another file that obj.conf?
          Any suggestion to fix this problem?
          Thanks in advance.


Hi
1. You do NOT write any code for Session Replication. Its not worth trying also though possible in extreme ways.
2. Session Replication means, I guess if you have more then one server like a Clustered Domain. For this you just create a Clustered Domain with one Admin Server and more then one managed servers. Then you add some load balancer infront of this cluster like Apache HTTP Server. All your requests go to apache which redirects to back end weblogic server. It will do load balancing, failover, session replication. There is absolutely nothing to do or configure. By default session should be replicated across all the servers in the cluster.
Thanks
Ravi Jegga

Configuring Weblogic server to use HTTP protocol instead of T3

It is posible to set two Weblogic servers to communicate using the HTTP protocol instead of the T3 protocol? We are able to communicate between servers using the T3 protocol. We were also able to set a server to communicate to a client using the HTTP protocol. We can not configure two servers to communicate using the HTTP protocol. Any advise how to configure the servers to work this way?
thanks,
R.

"There was a problem with your request,please contact your administrator."
"Error details:Error building pipeline.Failed to instantiate ExtensionRuntime"Check the CAS logs to see if there are any further details or a stack-trace for the error.
-->When I tried in browser it says
"The address wasn't understood
Firefox doesn't know how to open this address, because the protocol (idc) isn't associated with any program.
You might need to install other software to open this address."Expected.
URL format is like
idc://<server_name>:<port>/folderPath/I think that only proto/hostname/port is required - you could try without the folder path. Which port are you actually using, and can you confirm that Intradoc is running on that port?
Best
Brett

Weblogic 10 MDB using Websphere MQ 6.1

I am trying to configure weblogic server to use an MQ queue to trigger an MDB.
I have setup the JNDI foreign provider with the links between the local and remote JNDI names. I have also placed the relevant MQ jars into the classpath.
However when I startup the server I get the following problem:
Error getting JMSServer member info NestedException Message is :com.ibm.mq.jms.MQQueue
Has anyone successfully integrated these versions of weblogic and websphere MQ? From a search of relevant docs, it appears the weblogic approach has changed in recent versions from defining 'foreign JMS providers' to JNDI providers - however the documentation related to MQ integration all users the old approach - is there any more uptodate documents anywhere?
Full exception is:
Error getting JMSServer member info
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:440
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(Mod
uleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(Depl
oymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(De
ploymentCallbackFlow.java:71)
Truncated. see log file for complete stacktrace
Error getting JMSServer member info NestedException Message is :com.ibm.mq.jms.MQQueue
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDMan
agers(MessageDrivenBeanInfoImpl.java:1293)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(Me
ssageDrivenBeanInfoImpl.java:1058)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java
:1322)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:423
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(Mod
uleListenerInvoker.java:107)
Truncated. see log file for complete stacktrace
>
Thanks in advance.

I've got the same error running WLS 9.2MP2 against a Tibco foreign provider dying at the same spot ModuleListenerInvoker.java:107:
          Error getting JMSServer member info
          at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:422)
          at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
          at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
          at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
          at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
          Truncated. see log file for complete stacktrace
          Error getting JMSServer member info NestedException Message is :com.tibco.tibjms.naming.TibjmsFederatedTopic
          at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:12$
          at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1050)
          at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1270)
          at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:405)
          at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
          Truncated. see log file for complete stacktrace

Configuring kodo-jdo-2.5.3 with weblogic 8.1 using JCA

Hi there.
I am trying to configure kodo-jdo-2.5.3 in WebLogic 8.1 using JCA method.
The issue I got was that I got DB authentication failed. I have tested my
JDBC connect -- working fine, I have turned on JDBC log in WL, it looks
fine.
It looks like that KODO was still trying to create its own JDBC connection
even I have specified
<config-property>
<description>The JNDI name of the connection factory to use for
obtaining connections.</description>
<config-property-name>ConnectionFactoryName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>datasource.oracle9</config-property-value>
</config-property>
"datasource.oracle9" is the JNDI name of my data source.
The error message is the following. I will really appreciate your help.
Melvin
Oct 19, 2003 4:20:53 AM com.solarmetric.kodo.impl.jdbc.RegisterListener
registerClass
SEVERE: com.solarmetric.kodo.runtime.FatalDataStoreException:
java.sql.SQLException: User: melvin, f
ailed to be authenticated. [code=0;state=null]
NestedThrowables:
java.sql.SQLException: User: melvin, failed to be authenticated.
com.solarmetric.kodo.runtime.FatalDataStoreException:
java.sql.SQLException: User: melvin, failed to
be authenticated. [code=0;state=null]
NestedThrowables:
java.sql.SQLException: User: melvin, failed to be authenticated.
at
com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwFatal(SQLExceptions.java:58)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFacto
ry.java:212)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfigurat
ion.java:370)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassInternal(JDBCPe
rsistenceManagerFactory.java:455)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(JDBCPersistenc
eManagerFactory.java:338)
at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListener.java:53)
at
javax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
at samples.j2ee.Car.<clinit>(Car.java)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at samples.j2ee.ejb.CarBean.class$(CarBean.java:11)
at samples.j2ee.ejb.CarBean.list(CarBean.java:136)
at
samples.j2ee.ejb.CarEJB_pgfrtx_EOImpl.list(CarEJB_pgfrtx_EOImpl.java:201)
at jsp_servlet.__index._jspService(__index.java:170)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:431)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:36
22)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
NestedThrowablesStackTrace:
java.sql.SQLException: User: melvin, failed to be authenticated.
at
weblogic.jdbc.common.internal.RmiDataSource.getSubject(RmiDataSource.java:257)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:188)
at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(DataSourceConnec
tor.java:63)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFacto
ry.java:179)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfigurat
ion.java:370)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClassInternal(JDBCPe
rsistenceManagerFactory.java:455)
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.registerClass(JDBCPersistenc
eManagerFactory.java:338)
at
com.solarmetric.kodo.impl.jdbc.RegisterListener.registerClass(RegisterListener.java:53)
at
javax.jdo.spi.JDOImplHelper.registerClass(JDOImplHelper.java:269)
at samples.j2ee.Car.<clinit>(Car.java)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at samples.j2ee.ejb.CarBean.class$(CarBean.java:11)
at samples.j2ee.ejb.CarBean.list(CarBean.java:136)
at
samples.j2ee.ejb.CarEJB_pgfrtx_EOImpl.list(CarEJB_pgfrtx_EOImpl.java:201)
at jsp_servlet.__index._jspService(__index.java:170)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:431)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:36
22)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
<Oct 19, 2003 4:20:53 AM CDT> <Info> <EJB> <BEA-010051> <EJB Exception
occurred during invocation fr
om home: samples.j2ee.ejb.CarEJB_pgfrtx_HomeImpl@1c059f6 threw exception:
com.solarmetric.kodo.runti
me.FatalDataStoreException: java.sql.SQLException: User: melvin, failed to
be authenticated. [code=0
;state=null]
NestedThrowables:
java.sql.SQLException: User: melvin, failed to be authenticated.
com.solarmetric.kodo.runtime.FatalDataStoreException:
java.sql.SQLException: User: melvin, failed to
be authenticated. [code=0;state=null]
NestedThrowables:
java.sql.SQLException: User: melvin, failed to be authenticated.
at
com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwFatal(SQLExceptions.java:58)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFacto
ry.java:212)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfigurat
ion.java:370)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCStoreManager.ja
va:753)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.
java:1023)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.
java:1037)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCExtent.getResultList(JDBCExtent.java:71)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCExtent.getIterator(JDBCExtent.java:47)
at
com.solarmetric.kodo.runtime.ExtentImpl$MultipleSubclassIterator.newIterator(ExtentImpl.j
ava:344)
at serp.util.MultiIterator.setIterator(MultiIterator.java:74)
at serp.util.MultiIterator.hasNext(MultiIterator.java:29)
at serp.util.LookaheadIterator.setNext(LookaheadIterator.java:133)
at
serp.util.LookaheadIterator.initialize(LookaheadIterator.java:118)
at serp.util.LookaheadIterator.hasNext(LookaheadIterator.java:48)
at serp.util.MultiIterator.setIterator(MultiIterator.java:73)
at serp.util.MultiIterator.hasNext(MultiIterator.java:29)
at
com.solarmetric.kodo.runtime.ExtentImpl$TransactionAwareIterator.hasNext(ExtentImpl.java:
403)
at samples.j2ee.ejb.CarBean.list(CarBean.java:138)
at
samples.j2ee.ejb.CarEJB_pgfrtx_EOImpl.list(CarEJB_pgfrtx_EOImpl.java:201)
at jsp_servlet.__index._jspService(__index.java:170)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1053)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:431)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6310)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:36
22)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
NestedThrowablesStackTrace:
java.sql.SQLException: User: melvin, failed to be authenticated.
at
weblogic.jdbc.common.internal.RmiDataSource.getSubject(RmiDataSource.java:257)
at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:188)
at
com.solarmetric.kodo.impl.jdbc.runtime.DataSourceConnector.getConnection(DataSourceConnec
tor.java:63)
at
com.solarmetric.kodo.impl.jdbc.schema.DBDictionaryFactory.getDictionary(DBDictionaryFacto
ry.java:179)
at
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionary(JDBCSimpleConfigurat
ion.java:370)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getDictionary(JDBCStoreManager.ja
va:753)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.
java:1023)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.getClassMapping(JDBCStoreManager.
java:1037)

Alex Robbins wrote:
Try removing <authentication-mechanism> from the ra.xml file of the Kodo
JCA connector. Then it won't try to authenticate against the WL security
realm. (If you want connector-level authentication as well as DB-conn
authentication i think you'll have to configure WL security. I don't know
how). This worked for me.
Alex.Hi, The following is the ra.xml, please see any problem.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connector PUBLIC '-//Sun Microsystems, Inc.//DTD Connector
1.0//EN' 'http://java.sun.com/dtd/connector_1_0.dtd'>
<connector>
<display-name>KodoJDO</display-name>
<description>Resource Adapter for integration of the Kodo Java Data
Objects (JDO) implementation with J2EE 1.3 compliant managed
environments</description>
<icon>
<small-icon>kodo16.gif</small-icon>
<large-icon>kodo32.gif</large-icon>
</icon>
<vendor-name>Solarmetric, Inc.</vendor-name>
<spec-version>1.0</spec-version>
<eis-type>jdo</eis-type>
<version>1.0</version>
<license>
<description>See http://www.solarmetric.com for terms and license
conditions.</description>
<license-required>true</license-required>
</license>
<resourceadapter>
<managedconnectionfactory-class>com.solarmetric.kodo.impl.jdbc.ee.ManagedConnectionFactoryImpl</managedconnectionfactory-class>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
<connectionfactory-impl-class>com.solarmetric.kodo.impl.jdbc.ee.JDOConnectionFactory</connectionfactory-impl-class>
<connection-interface>javax.resource.cci.Connection</connection-interface>
<connection-impl-class>com.solarmetric.kodo.ee.EEPersistenceManager</connection-impl-class>
<transaction-support>XATransaction</transaction-support>
<config-property>
<description>The number of hard references to cached objects that the
PersistenceManager's cache will retain (in addition to the soft reference
cache that it maintains). Setting this to a higher value will result in
more objects being retained in the cache, at the cost of utilizing more
memory resources. Setting it to -1 will cause the PersistenceManager to
maintain hard references only. This will result in better performance, but
can have adverse effects on memory usage.</description>
<config-property-name>CacheReferenceSize</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>1000</config-property-value>
</config-property>
<config-property>
<description>The class name of ether the JDBC java.sql.Driver, or an
instance of a javax.sql.DataSource to use to connect to the data
source.</description>
<config-property-name>ConnectionDriverName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The JNDI name of the connection factory to use for
finding non-transactional connections. If specified, this is the
connection that will be used for access for obtaining sequence
numbers.</description>
<config-property-name>ConnectionFactory2Name</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>jdbc/petshop</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to be passed to
the JDBC Driver when obtaining a Connection for the ConnectionFactory2
(which will be used to obtain sequence numbers). Properties are of the
form "key=value". If a javax.sql.DataSource class is defined in the
javax.jdo.option.ConnectionDriverName property, then this property will be
used to set bean-like properties in the DataSource instance upon creation.
These properties vary depending on the DataSource in use: see the
documentation for your DataSource for details on the properties to
use.</description>
<config-property-name>ConnectionFactory2Properties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The JNDI name of the connection factory to use for
obtaining connections.</description>
<config-property-name>ConnectionFactoryName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>PetShopXADataSource</config-property-value>
</config-property>
<config-property>
<description>The password for the user specified in
ConnectionUserName</description>
<config-property-name>ConnectionPassword</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to be passed to
the JDBC Driver when obtaining a Connection. Properties are of the form
"key=value". If a javax.sql.DataSource class is defined in the
javax.jdo.option.ConnectionDriverName property, then this property will be
used to set bean-like properties in the DataSource instance upon creation.
These properties vary depending on the DataSource in use: see the
documentation for your DataSource for details on the properties to
use.</description>
<config-property-name>ConnectionProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The connection retain mode. Possible options are
"persistence-manager", "transaction", and "on-demand". Default value is
"on-demand".</description>
<config-property-name>ConnectionRetainMode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>on-demand</config-property-value>
</config-property>
<config-property>
<description>The number of seconds to wait between testing
connections retrieved from the connection pool. Only valid when using the
built-in Kodo connection pooling.</description>
<config-property-name>ConnectionTestTimeout</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>10</config-property-value>
</config-property>
<config-property>
<description>The URL for the data source.</description>
<config-property-name>ConnectionURL</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The username for the connection listed in
ConnectionURL.</description>
<config-property-name>ConnectionUserName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for caching of data loaded
from the data store. Must implement
com.solarmetric.kodo.runtime.datacache.DataCache.</description>
<config-property-name>DataCacheClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.DataCacheClass upon
initialization.</description>
<config-property-name>DataCacheProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the default class to use for mapping
persistent classes to the database. Must extend
com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.</description>
<config-property-name>DefaultClassMappingClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping</config-property-value>
</config-property>
<config-property>
<description>The number of seconds that data in the data cache is
valid for. A value of 0 or less means that by default, cached data does
not time out.</description>
<config-property-name>DefaultDataCacheTimeout</config-property-name>
<config-property-type>java.lang.Double</config-property-type>
<config-property-value>0.0</config-property-value>
</config-property>
<config-property>
<description>The number of rows that will be pre-fetched when an
element in a Query result is accessed.</description>
<config-property-name>DefaultFetchBatchSize</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>10</config-property-value>
</config-property>
<config-property>
<description>The threshold below which result lists will be
completely instantiated upon their creation. A value of -1 will always
force all results to be completely instantiated, thus disabling lazy
result loading.</description>
<config-property-name>DefaultFetchThreshold</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>30</config-property-value>
</config-property>
<config-property>
<description>The name of the default class to use for managing
subclass indicator columns. Must implement the
com.solarmetric.kodo.impl.jdbc.ormapping.SubclassProvider interface. See
custom class indicator documentation for more information about subclass
providers.</description>
<config-property-name>DefaultSubclassProviderClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in
com.solarmetric.kodo.impl.jdbc.DefaultSubclassProviderClass upon
initialization.</description>
<config-property-name>DefaultSubclassProviderProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The DBDictionary to use for this configuration. This is
auto-detected based on the setting of javax.jdo.option.ConnectionURL, so
you need only set this to override the default with your own custom
DBDictionary or if you are using an unrecognized driver.</description>
<config-property-name>DictionaryClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A space-separated list of name-value properties
settings to pass to the dictionary defined by
com.solarmetric.kodo.impl.jdbc.DictionaryClass. Many of the DBDictionary
options are automatically configured by concrete subclasses of
GenericDictionary. The defaults can, however, be overridden by using this
property.</description>
<config-property-name>DictionaryProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>If true, then Kodo JDO will allow the use of query
filter extensions. See the query extensions documentation for more
information.</description>
<config-property-name>EnableQueryExtensions</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of fetch group names that
PersistenceManagers will load by default when loading data from the
database.</description>
<config-property-name>FetchGroups</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>If true, then all fields of all classes in a given
inheritance hierarchy will by default map into the least-derived type's
default primary table. If false then a new default primary table will be
created for each class in the inheritance hierarchy, and each type's
declared fields will map to that table by default.</description>
<config-property-name>FlatInheritanceMapping</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>A String value indicating whether or not Kodo should
automatically flush modifications to the data store before executing
queries.</description>
<config-property-name>FlushBeforeQueries</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>with-connection</config-property-value>
</config-property>
<config-property>
<description>If false, then the JDO implementation must consider
modifications, deletions, and additions in the PersistenceManager
transaction cache when executing a query inside a transaction. Else, the
implementation is free to ignore the cache and execute the query directly
against the data store.</description>
<config-property-name>IgnoreCache</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>The license key provided to you by SolarMetric. Keys
are available at www.solarmetric.com</description>
<config-property-name>LicenseKey</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>xxxx</config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for obtaining a reference
to the transaction manager in an enterprise environment. Must implement
the com.solarmetric.kodo.ee.ManagedRuntime interface.</description>
<config-property-name>ManagedRuntimeClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.ee.AutomaticManagedRuntime</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.ManagedRuntimeClass upon
initialization.</description>
<config-property-name>ManagedRuntimeProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The maximum number of connections to pool. If all of
these are in use, then PersistenceManager instances must wait for a
connection to become available. This option has been removed from the
specification, but we still use the javax.jdo.option for backwards
compatibility.</description>
<config-property-name>MaxPool</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>200</config-property-value>
</config-property>
<config-property>
<description>The minimum number of connections to keep in the pool.
This option has been removed from the specification, but we still use the
javax.jdo.option for backwards compatibility.</description>
<config-property-name>MinPool</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>2</config-property-value>
</config-property>
<config-property>
<description>The number of milliseconds to wait for a pooled
connection before throwing an exception if the pool is empty. This option
has been removed from the specification, but we still use the
javax.jdo.option for backwards compatibility.</description>
<config-property-name>MsWait</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>30000</config-property-value>
</config-property>
<config-property>
<description>If true, then the application plans to have multiple
threads simultaneously accessing a single PersistenceManager, so measures
must be taken to ensure that the implementation is thread-safe. Otherwise,
the implementation need not address thread safety.</description>
<config-property-name>Multithreaded</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>If true, then it is possible to read persistent data
outside the context of a transaction. Otherwise, a transaction must be in
progress in order read data.</description>
<config-property-name>NontransactionalRead</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>If true, then it is possible to write to fields of a
persistent-nontransactional object when a transaction is not in progress.
If false, such a write will result in a JDOUserException.</description>
<config-property-name>NontransactionalWrite</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>Selects between optimistic and pessimistic (data store)
transactional modes.</description>
<config-property-name>Optimistic</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>The name of the class that the
PersistenceManagerFactory should create when creating a new
PersistenceManagerImpl. Must extend
com.solarmetric.kodo.runtime.PersistenceManagerImpl.</description>
<config-property-name>PersistenceManagerClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the concrete implementation of
javax.jdo.PersistenceManagerFactory that
javax.jdo.JDOHelper.getPersistenceManagerFactory () should create. For
Kodo JDO, this should be
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory or
com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory, or a custom
extension of one of these types.</description>
<config-property-name>PersistenceManagerFactoryClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.PersistenceManagerClass upon
initialization.</description>
<config-property-name>PersistenceManagerProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of classes that will be
initialized whenever a new PersistenceManager is instantiated. This can be
used to get around issues with application identity classes not being
associated with their respective persistent classes.</description>
<config-property-name>PersistentTypes</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the class to use to proxy second class
objects in managed instances. Must implement
com.solarmetric.kodo.util.ProxyManager.</description>
<config-property-name>ProxyManagerClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.util.SimpleProxyManager</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.ProxyManagerClass upon
initialization.</description>
<config-property-name>ProxyManagerProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for caching of queries
loaded from the data store. Must implement
com.solarmetric.kodo.runtime.datacache.QueryCache.</description>
<config-property-name>QueryCacheClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.runtime.datacache.query.QueryCacheImpl</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.QueryCacheClass upon
initialization.</description>
<config-property-name>QueryCacheProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A list of query filter listeners to add to the default
list of extensions. Ignored if com.solarmetric.kodo.EnableQueryExtensions
is false.</description>
<config-property-name>QueryFilterListeners</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for communicating commit
information among JVMs. Must implement
com.solarmetric.kodo.runtime.event.RemoteCommitProvider.</description>
<config-property-name>RemoteCommitProviderClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.RemoteCommitProviderClass upon
initialization.</description>
<config-property-name>RemoteCommitProviderProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>If true, then fields in a persistence-capable object
that have been changed during a transaction will be rolled back to their
original values upon a rollback. Otherwise, the values will not be changed
upon rollback.</description>
<config-property-name>RestoreValues</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>The name of the class that will be used as the
Collection implementation for returning ResultList instances. It must be
an instance of
com.solarmetric.kodo.runtime.objectprovider.ResultList.</description>
<config-property-name>ResultListClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The property string used to configure the instance of
the ResultListClass.</description>
<config-property-name>ResultListProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>If true, then fields in a persistence-capable object
that have been read during a transaction must be preserved in memory after
the transaction commits. Otherwise, persistence-capable objects must
transition to the hollow state upon commit, meaning that subsequent reads
will result in a database round-trip.</description>
<config-property-name>RetainValues</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>The name of the class to use for generating sequence
numbers when using data store identity. Must implement the
com.solarmetric.kodo.impl.jdbc.SequenceFactory interface.</description>
<config-property-name>SequenceFactoryClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.schema.DBSequenceFactory</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.impl.jdbc.SequenceFactoryClass upon
initialization.</description>
<config-property-name>SequenceFactoryProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The class names of a SQLExecutionListener
implementation to install on the SQLExecutionManager.</description>
<config-property-name>SQLExecutionListenerClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The name of a custom SQLExecutionManager to be used for
all issuance of SQL to the data store. Must implement
com.solarmetric.kodo.impl.jdbc.SQLExecutionManager.</description>
<config-property-name>SQLExecutionManagerClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl</config-property-value>
</config-property>
<config-property>
<description>The size of the PreparedStatement cache that is
maintained in the DataSource implementation.</description>
<config-property-name>StatementCacheMaxSize</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>70</config-property-value>
</config-property>
<config-property>
<description>The time, in seconds, after which a JDBC query will be
aborted if it has not yet returned any values. This value is simply passed
to the JDBC driver's Statement.setTimeout method; Kodo does not perform
any addition timeout actions. Note that many JDBC drivers either ignore
this request, or improperly handle it, which may result in application
deadlocks.</description>
<config-property-name>StatementExecutionTimeout</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>-1</config-property-value>
</config-property>
<config-property>
<description>If true, the Kodo runtime will automatically attempt to
refresh the database schema when persistent classes are referenced,
allowing the developer to bypass the schematool step. This property is
only intended to be used for development. As automatic schema migration
can result in data loss, this feature should never be enabled on a
production system. Furthermore, this feature has serious adverse affects
on Kodo's runtime performace. Ensure that it is disabled before doing any
performance analysis.</description>
<config-property-name>SynchronizeSchema</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>The name of the class to use to store
persistence-capable objects involved in a PM's transaction cache. Must
implement com.solarmetric.kodo.runtime.StateManagerSet.</description>
<config-property-name>TransactionCacheClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.solarmetric.kodo.runtime.FifoStateManagerSet</config-property-value>
</config-property>
<config-property>
<description>A space-separated list of properties to pass to the
class defined in com.solarmetric.kodo.TransactionCacheClass upon
initialization.</description>
<config-property-name>TransactionCacheProperties</config-property-name>
<config-property-type>java.lang.String</config-property

Weblogic specific annotations and features

Hello everyone, I'm considering the use of the WebLogic Server on my environment so I started reading some of it's documentation. I've not seen a lot but something that I've noticed immediately was the heavy use of proprietary annotations like @Policy, @WLHttpTransport and classes like weblogic.xml.crypto.wss.WSSecurityContext. I've liked lots of Weblogic features I'm not interested in getting specific with any vendor. I've seen some other Application servers and although they don't have many of the features Weblogic does they let you program the application in an agnostic manner. Obviously all of them have specific files to cover configuration which is not part of the Java EE 5 specification (like keystores locations, data sources, etc) but they don't impose you to use specific classes or annotations in code.
So I would like to know, is it possible to develop productively without specific elements in the source code (for example, using deployment descriptors for configuration) ?
Thank you !

As David mentions, usually the WebLogic proprietary annotations and features are there to address functionality not available by using standards, in your example the JAX-WS annotations don't have a standard annotation similar to @WLHttpTransport to my knowledge. Some of the time what is happening is that the annotations are used when deployment descriptors could be used instead. If that is the case, you can always keep your EAR / WAR clean of proprietary deployment descriptors and use a deployment plan (JSR-88) to keep that external to your application. There is a picture in my recent blog post illustrating this approach. http://blogs.oracle.com/jamesbayer/2009/07/11gr1_update_and_a_deployment.html
When talking about proprietary classes like weblogic.xml.crypto.wss.WSSecurityContext that becomes a little tougher and if you really want to keep your code clean of proprietary extensions, you might have to use dependency injection techniques or similar and have implementations for each vendor you need to deploy to.

How to install and configure WebLogic 10.3 to use 64-bit JDK?

Hi,
Is there a preferred/supported way to configure WebLogic to use the 64-bit JRockit that comes with JRockit Mission Control?
I can't find any official documentation about how to configure WebLogic to use a 64-bit JDK. From other forum posts I can tell we need to use the 64-bit JRockit that is bundled with JRockit Mission Control (available at [http://www.oracle.com/technology/software/products/jrockit/index.html]) but then we are kind of stuck - the configure script which let me select a JDK for a domain doesn't seem to let me re-configure an existing domain, and I can't find anything within the admin console that would let me set the JDK to use.
I was able to rename the existing jrockit_160_05 directory to e.g. jrockit_160_05_original and then rename the jrmc directory to "jrockit_160_05", effectively taking the place of the JDK being used but this seemed like a bad way to do it. I also found via Google this page: [http://java.sodeso.nl/application-servers/bea-weblogic/how-can-i-change-the-jdk-installation-that-weblogic-uses] which basically says to modify the JAVA_HOME environment variable in the start scripts, but this seems like the same thing.
With the plethora of products and the different ways they are bundled, combined with all the documentation about everything, I thought I would find something but I keep coming up blank. Does anyone have suggestions or pointers?
Thanks,
KaJun

Make sure your environment configuration is supported here:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
Then, you need to have the correct 64bit JDK installed. Sounds like you have done that.
Then download and run the generic platform installer as described here with your 64bit supported JDK:
http://download.oracle.com/docs/cd/E12839_01/doc.1111/e14142/start.htm#i1077535
Notice how the link you post has the generic installer for all the 64bit JVM rows, but the other installer for the 32bit JVMs on the 64bit OS?

How to access CQ configuration settings using CQ HTTP client?

Hi,
I am trying to access CQ configuration in my application using CQ HTTP client. I am able to access through ConfigAdmin, but not directly.
Please suggest a way to access the configuration directly by CQ HTTP client.
Is CQ proxy settings directly available to CQ HTTP client? if so, how do we access it?
Thanks

Yes it is directly available. The proxy does not need to be explicitly configured for each HttpClient since it is done automatically when the com.day.commons.osgi.wrapper.commons-httpclient gets activated. Make sure your bundle imports [1] and call as HttpClient client = new HttpClient();
[1]
org.apache.commons.httpclient,version=3.1.0 from com.day.commons.osgi.wrapper.commons-httpclient (xx)
org.apache.commons.httpclient.methods,version=3.1.0 from com.day.commons.osgi.wrapper.commons-httpclient (xx)

How does one delete VPN configurations in the settings list not used any more?

How does one delete VPN configurations in the settings list not used any more?

Sorted found profiles and delete from there

How do i configure telnet service to use a specific port number

How do I configure a specific port number to the telnet service other than the default port number. I opened /System/Library/LaunchDaemon/telnet.plist with XCode but it won't let me modify the port number. Is there another place / item that I need to go to?

Telnet is obsolete and insecure. Use ssh instead.

Reg : Error While Configuring Weblogic Using :11.1.1.6 for SOA

Hi team,
following is the error iam getting while configuring weblogic server for SOA
OS : Win XP SP3 : SOA Version : 11.1.1.6
Component Schema=SOA Infrastructure
Driver=oracle.jdbc.xa.client.OracleXADataSource
URL=jdbc:oracle:thin:@localhost:1521/xe
User=DEV_SOAINFRA
Password=***
SQL Test=select 1 from schema_version_registry where owner=(select user from dual) and mr_type='SOAINFRA' and version='11.1.1.6.0'
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
CFGFWK-60850: Test Failed!
Component Schema=User Messaging Service
Driver=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@localhost:1521/xe
User=DEV_ORASDPM
Password=***
SQL Test=select 1 from schema_version_registry where owner=(select user from dual) and mr_type='ORASDPM' and version='11.1.1.6.0'
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
CFGFWK-60850: Test Failed!
Component Schema=OWSM MDS Schema
Driver=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@localhost:1521/xe
User=DEV_MDS
Password=***
SQL Test=select 1 from schema_version_registry where
                    owner=(select user from
                    dual) and mr_type='MDS' and
                    version='11.1.1.6.0'
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
CFGFWK-60850: Test Failed!
Component Schema=SOA MDS Schema
Driver=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@localhost:1521/xe
User=DEV_MDS
Password=***
SQL Test=select 1 from schema_version_registry where owner=(select user from dual) and mr_type='MDS' and version='11.1.1.6.0'
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
CFGFWK-60850: Test Failed!
Please provide your comments.
Sridhar

Have a look at this...
http://www.smartmarmot.com/2011/10/workaround-to-the-issue-ora-01882-timezone-region-not-found-when-connection-to-oracle/
In your case your still running the installer... So you'll probably have to set the option on your JVM directly...
Cheers,
Vlad

You may need to configure the connection settings in the deployment descrip

Hi All
I am new to BPEL and going through Order Booking Tutorial (using 10.1.3.4 version of opmn ) .
I have a problem in 'Designing the Database Adapter to Insert Data' Chapter.
I have installed Oracle 10g Express Edition and BPEL Process Manager on my local system.
In the Example it has been asked to create a daabase connection with Third Party JDBC Driver. Instead I have created a database connection with Oracle(JDBC) Driver.So i didnt have to register any third party driver.
I cud access the Order/OrderItems table as well .
I Deployed the same on the server.But while running the process I get following error--
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
nested exception is:
     ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore. [Caused by: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
The Connection descriptor used by the client was:
localhost:1521:XE
See root exception for the specific exception. You may need to configure the connection settings in the deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the server. Caused by Exception [TOPLINK-4002] (Oracle TopLink - 10g Release 3 (10.1.3.4.0) (Build 080602)): oracle.toplink.exceptions.DatabaseException
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I have checked several post on this error but every post talks about third party database.I have used Oracle Database only so why/What shud I change anything in oc4j-ra.xml?? This is my doubt .
Pls help me on this .Also Let me knowe in my case is there any need to create the datasource.?I am low at concept of database.
Pls help
Regards
Naveen

Hi
I am trying to insert orader and order Items as given in the Order booking tutorial..
Here are the files description
.wsdl file looks like
<service name="DBInsert">
<port name="DBInsert_pt" binding="tns:DBInsert_binding">
<jca:address location="eis/DB/MyConnection"
UIConnectionName="MyConnection"
ManagedConnectionFactory="oracle.tip.adapter.db.DBManagedConnectionFactory"
mcf.DriverClassName="oracle.jdbc.OracleDriver"
mcf.PlatformClassName="oracle.toplink.platform.database.oracle.OraclePlatform"
mcf.ConnectionString="jdbc:oracle:thin:@localhost:1521:XE"
mcf.UserName="system"
mcf.Password="6672B62098892995C8B651EFDF798A59"
/>
</port>
</service>
data source file looks like
<connection-pool name="MyConnection">

<connection-factory factory-class="oracle.jdbc.OracleDriver" user="orabpel" password="->pwForOrabpel" url="jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=tcp)(HOST=nakhanna)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=XE)))"/>
</connection-pool>
<managed-data-source name="MyConnection" connection-pool-name="MyConnection" jndi-name="jdbc/MyConnectionDS"/>
</data-sources>
oc4j-ra.xml looks like
<connector-factory location="eis/DB/MyConnection" connector-name="Database Adapter">
          <config-property name="xADataSourceName" value="jdbc/MyConnectionDS"/>
          <config-property name="dataSourceName" value=""/>
          <config-property name="platformClassName" value="oracle.toplink.platform.database.Oracle9Platform"/>
          <config-property name="usesNativeSequencing" value="true"/>
          <config-property name="sequencePreallocationSize" value="50"/>
          <config-property name="defaultNChar" value="false"/>
          <config-property name="usesBatchWriting" value="true"/>
          <connection-pooling use="none">
          </connection-pooling>
          <security-config use="none">
          </security-config>
     </connector-factory>
##################################################################3
Still I get the same error .
<bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
</part><part name="summary"><summary>file:/C:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_FulfillOrder_4.0_e77c64251e45eb4711a3a093f92e6a86.tmp/DBInsert.wsdl [ DBInsert_ptt::merge(OrdersCollection) ] - WSIF JCA Execute of operation 'merge' failed due to: java.util.MissingResourceException
java.util.MissingResourceException
; nested exception is:
     ORABPEL-00001
java.util.MissingResourceException
java.util.MissingResourceException
java.util.MissingResourceException
</summary>
</part><part name="detail"><detail>null</detail>
</part></bindingFault>
Pls let me know if something looks wrong in the above files
Thanks
naveen

Soap handler configuration weblogic v9.2

All the doc. on soap handlers for weblogic version 9x i could find describes using annotations. This works fine when you have the source but not in the case where i only have a "black box" web service in a WAR file.
I want to configure a soap handler in xml config. files but i can only find this kind of configuration doc. for version 8.x. Can anyone point me to doc on how th do this in version 9.x?
Ideally i think it should be possible to configure a handler in webservices.xml. Soap handlers should be configurable for any deployed web service i think? I also tried to use the admin. console but as far as i can see this only gives administration control over already configured handlers - not the functionality to add handlers.
Regards,
Ole Bech Mogensen, 7N

Manish,
Thanks for the reply. Yes I did. I keep getting the following error:
XML Parsing Error: no element found
Location: http://192.168.198.129:7001/Sample_App/Sample_Config.xml
Line Number 1, Column 1:
I even copied one of the actual WebLogic OOTB (out of the box) config files (i.e. WebLogic Platform9.2.3.0_chmods.xml) and I still get the same error from WebLogic when directly trying to invoke the Sample_Config.xml file. The actual contents of the Sample_Config.xml are as follows:
<?xml version="1.0" encoding="UTF-8" ?>
<Boot_test>
<URLContextPath>Sample_App</URLContextPath>
<ConfigFilePath>C:\Temp\Another_Config_File.xml</ConfigFilePath>
<ConfigPassword>admin</ConfigPassword>
</Boot_test>
So, I am still unresolved in getting the three(3) parms loaded via a config file in BEA WebLogic v9.2. Any other suggestions/thoughts on getting this loaded via a config file?
Thanks.
/workingtohard

How to configure weblogic as a SAML2 Service Provider

Hi,
I have to configure weblogic 11g to work with an external IdP, which is in fact the Dutch SurfConext for the Dutch Education Sector, so I used their metadata (https://wiki.surfnet.nl/display/surfconextdev/Connection+metadata)
I configured the weblogic server mainly following https://blogs.oracle.com/blogbypuneeth/entry/steps_to_configure_saml_2.
I have configured a SAML2 Authenticator (Sufficient) and SAM2 Identity Asserter (in that order). Then on the machine I configured the Service Provider tab under Federation Services and the SAML2 Services tab.
But although I turned on the debug for saml2 at the configured managed server, I don't see any logging when I tried to reach the webapplication. I used the sample destination app from the blog. The application that I have to secure this way has an own login-page. When trying the sample dest webapplication URL I get the 403 forbidden error, but no logging on saml2.
I search google around several times, and I feel that I should configure something in the web.xml and/or weblogic.xml. But I actually can't find the settings. I assumed that the web.xml of the sampl dest app (where auth-method is set to BASIC and realm-name myrealm) would do. And if that works that the actual application should be configured the same.
What needs to happen is that when I try to reach the base URL of the web app, the browser gets rerouted to the IdP-'Where are you from" page, where the user can choose his/her college/university/organization and then login. After logging the Idp (SurfConext) should route the browser together with the SAML token to weblogic where the user gets routed to the actual main page of the webapp.
So I feel that there is some configuration to do to get the webapplication secured via the SAML2 Identity Asserter. Either in weblogic (correct URL) and/or in the web.xml.
Can anyone help me on the steps I apparently missed? And maybe ask me the correct questions to get me on the right track?
Thanks in advance.
Regards,
Martien

Apparently I wrongly repackaged the zip from the blog into a war file. There was an faulty extra level of directory structure in the zip.
I created a new war file from the bottom up, with own jsp's. And that worked.

Configuring Weblogic 9.x as both webserver and appserver

Hi,
How can one configure weblogic to host static content on weblogic web server and application/business logic on application server.
Regards
Raju

We have upgraded our WebLogic from 8.1 to 9.2 along with our PeopleSoft 9.0 upgrade and boy-oh-boy, has the WebLogicAdmin console slowed down.
It used to open in about 10 seconds.
Now it opens in roughly 1 minute and 30 seconds.
The heap size settings are the same as they were in the WebLogic 8.1
Even restarting the WebLogicAdmin and associated PeopleSoft PIA's is the worst I have ever seen.
Windows 2003 SP3
Here's the startup command line;
-Xms256m -Xmx256m -XX:MaxPermSize=128m -classpath ";D:/psft/hr849\webserv\hdev\lib\ps_patch.jar;D:/psft/hr849\webserv\hdev\applications\peoplesoft\PSIGW\WEB-INF\lib\mail.jar;D:/psft/hr849\webserv\hdev\lib\portlet-api-1.0.jar;D:/psft/hr849\webserv\hdev\lib\pluto-1.0.1.jar;D:/psft/hr849\webserv\hdev\applications\peoplesoft\PORTAL\WEB-INF\lib\saaj.jar;D:/psft/hr849\webserv\hdev\applications\peoplesoft\PORTAL\WEB-INF\lib\xml-apis.jar;D:/psft/hr849\webserv\hdev\applications\peoplesoft\PORTAL\WEB-INF\lib\xercesImpl.jar;;d:\bea\patch_weblogic923\profiles\default\sys_manifest_classpath\weblogic_patch.jar;d:\bea\jdk150_12\lib\tools.jar;d:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\bea\WEBLOG~1\server\lib\weblogic.jar" -Djava.util.logging.config.file=D:\psft\hr849\webserv\hdev\applications\peoplesoft\logging.properties -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Dweblogic.Name=WebLogicAdmin -Dweblogic.management.username=operator -Dweblogic.ProductionModeEnabled=true -Dps_vault=D:\psft\hr849\webserv\hdev\psvault -Djava.security.policy="d:\bea\WEBLOG~1\server\lib\weblogic.policy" -Dssl.debug=false -Dps_home=D:/psft/hr849 weblogic.Server
Regards,
Tom

Configure Weblogic-specific settings using annotations in EJB3?

Similar Messages

Maybe you are looking for