JDBC Datasource problem in AM configrations

Hi,jhon
can u tell me the how to create the jdbcdatasource in WLS how we have to give the jndi name and i have changed in AM configration of JDBC Datasource but its not matching with jdbc datasource present in WLS can anyone tell me with the example how to create jdbc datasource
May 7, 2009 8:01:38 PM oracle.adf.share.security.providers.jps.CSFCredentialStor
e fetchCredential
WARNING: Unable to locate the credential for key FOD in C:\Oracle\Middleware\use
r_projects\domains\SFA\config\oracle.
May 7, 2009 8:01:38 PM oracle.adf.share.jndi.ReferenceStoreHelper throwPartialRe
sultException
WARNING: Incomplete connection information
May 7, 2009 8:01:38 PM oracle.adf.share.security.providers.jps.CSFCredentialStor
e fetchCredential
WARNING: Unable to locate the credential for key fod1 in C:\Oracle\Middleware\us
er_projects\domains\SFA\config\oracle.
May 7, 2009 8:01:38 PM oracle.adf.share.jndi.ReferenceStoreHelper throwPartialRe
sultException
WARNING: Incomplete connection information
May 7, 2009 8:01:46 PM com.sun.faces.lifecycle.Phase doPhase
SEVERE: jsf.lifecycle.phase.exception
<May 7, 2009 8:01:46 PM GMT+05:30> <Error> <HTTP> <BEA-101017> <[weblogic.servle
t.internal.WebAppServletContext@1d164ae - appName: 'application1', name: 'adfm',
context-path: '/adfm', spec-version: '2.5', request: weblogic.servlet.internal.
ServletRequestImpl@9a1336[
GET /adfm/faces/br-o.jspx?_adf.ctrl-state=41665048_3 HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shock
wave-flash, application/x-ms-application, application/x-ms-xbap, application/vnd
.ms-xpsdocument, application/xaml+xml, */*
Accept-Language: en-us
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.5072
7; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Connection: Keep-Alive
Cookie: oracle.uix=0^^GMT+5:30; JSESSIONID=QcJvKCwChv6V6Rx61T6hL1V7bvcbjGRtX9SCP
2ydnrTLKtTW05c6!-595734161
]] Root cause of ServletException.
oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection.
at oracle.jbo.server.ConnectionPool.createConnection(ConnectionPool.java
:253)
at oracle.jbo.server.ConnectionPool.instantiateResource(ConnectionPool.j
ava:168)
at oracle.jbo.pool.ResourcePool.createResource(ResourcePool.java:546)
at oracle.jbo.pool.ResourcePool.useResource(ResourcePool.java:327)
at oracle.jbo.server.ConnectionPool.getConnectionInternal(ConnectionPool
.java:104)
Truncated. see log file for complete stacktrace
java.sql.SQLException: ORA-01005: null password given; logon denied
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.ja
va:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:1
16)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java
:177)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:406)
Truncated. see log file for complete stacktrace
>

http://blogs.oracle.com/shay/2008/11/common_pitfalls_when_deploying.html

Similar Messages

Error in creating JDBC datasource

I would like to create a new JDBC datasource using WLST script.
There are 2 problems with it:
1. Running the script an error message will be displayed:
Creating JDBCSystemResource with name DBonHelium5
JDBCSystemResource with name 'DBonHelium5' has been created successfully.
Problem invoking WLST - Traceback (innermost last):
File "/opt/wls9/jdbc_data_source_creation.py", line 30, in ?
AttributeError: addJndiName
I donâ€™t understand why it is wrong and how could I fix the bug...
2. After running the script I looked at the current state on the console.
The datasource has been created but the target isnâ€™t set.
Could you help me whatâ€™s wrong?
Thanks in advice!
Zsigmond
The script:
connect("xxx","xxx")
edit()
startEdit()
# Change these names as necessary
dsname="DBonHelium5"
cd("Servers/AdminServer")
#target=getMBean("Servers/AdminServer")
target=cmo
cd("../..")
# start creation
print 'Creating JDBCSystemResource with name '+dsname
jdbcSR = create(dsname,"JDBCSystemResource")
theJDBCResource = jdbcSR.getJDBCResource()
theJDBCResource.setName("DBonHelium5")
connectionPoolParams = theJDBCResource.getJDBCConnectionPoolParams()
connectionPoolParams.setConnectionReserveTimeoutSeconds(25)
connectionPoolParams.setMaxCapacity(100)
connectionPoolParams.setTestTableName("SYSTABLES")
dsParams = theJDBCResource.getJDBCDataSourceParams()
<b>dsParams.addJndiName("DBonHelium5")</b>
driverParams = theJDBCResource.getJDBCDriverParams()
driverParams.setUrl("jdbc:bea:oracle://helium.lsy.bud.dlh.de:1521")
driverParams.setDriverName("weblogic.jdbcx.oracle.OracleDataSource")
driverParams.setPassword("LSY")
driverProperties = driverParams.getProperties()
proper = driverProperties.createProperty("user")
proper.setValue("LSY")
proper1 = driverProperties.createProperty("DatabaseName")
proper1.setValue("dbc:bea:oracle://helium.lsy.bud.dlh.de:1521")
<b>jdbcSR.addTarget(target)</b>
try:
save()
activate(block="true")
print "script returns SUCCESS"
except:
print "Error while trying to save and/or activate!!!"
dumpStack()
disconnect()
exit()

Hi Manfed,
I've got exactly the same problem mit j2sdkee 1.3.1. Have yor resolved the problem in the meantime?
If so, please post the solution. Thanks.
Helmut

JNDI lookup() for sql server jdbc datasource returns null

Hi,
I am trying to use a jdbc datasource in tomcat 5 to access a sql server 2000 database. I had many common problems and did found an answer to them in the forums but I'm having one last (I hope) problem. My program is also using a mySQL datasource and it works fine.
The problem is that my lookup returns null. No exception, just null. It seems that many people had this problem but I didn't found any answer to it.
This is the lookup code:
    Context ctx = new InitialContext();
    Context envCtx = (Context)ctx.lookup("java:comp/env");
    axaptaDS = (DataSource) envCtx.lookup("jdbc/axapta"); //returns null :(This my context.xml config:
<ResourceParams name="jdbc/axapta">
    <parameter>
      <name>factory</name>
      <value>com.microsoft.jdbcx.sqlserver.SQLServerDataSourceFactory</value>
    </parameter>
    <parameter>
      <name>url</name>
      <value>jdbc:microsoft:sqlserver://hostname:1433</value>
    </parameter>
    <parameter>
      <name>password</name>
      <value>password</value>
    </parameter>
    <parameter>
      <name>maxActive</name>
      <value>4</value>
    </parameter>
    <parameter>
      <name>maxWait</name>
      <value>5000</value>
    </parameter>
    <parameter>
      <name>driverClassName</name>
      <value>com.microsoft.jdbcx.sqlserver.SQLServerDataSource</value>
    </parameter>
    <parameter>
      <name>username</name>
      <value>username</value>
    </parameter>
    <parameter>
      <name>maxIdle</name>
      <value>2</value>
    </parameter>
</ResourceParams>And I also put these lines in my web.xml file:
<resource-ref id="ResourceRef_1092254277306">
     <res-ref-name>jdbc/axapta</res-ref-name>
     <res-type>javax.sql.DataSource</res-type>
     <res-auth>Container</res-auth>
     <res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>Thanks for helping!

I finally found a remedy to this problem:
specify this driver instead and remove the entry about the factory in the context's .xml file:
com.microsoft.jdbc.sqlserver.SQLServerDriver

JDBC Datasource creation via ANT doesn't expose the JNDI name

I'm using the wlconfig ANT task to create a Datasource (& JDBC connectionpool) on the weblogic server. The datasource is created fine, and I can test it using the console.
The problem is that the provided JNDI name isn't exposed in the JNDI tree. This seems to be related to the fact that the following element is generated in the config/jdbc/CP-PoolName-2164-jdbc.xml
<jdbc-data-source>
<name>PoolName</name>
<internal-properties>
*<property>*
*<name>LegacyType</name>*
*<value>1</value>*
*</property>*
When removing the LegacyType 1 property from the JDBC config xml, the JNDI name is exposed fine.
I've used the instructions located at [http://edocs.bea.com/wls/docs100/programming/ant_tasks.html] where an example of a JDBCConnectionPool creation is provided.
The 10.3 documentation doesn't include the example anymore, but I'm having the problem both on BEA Weblogic 10.0 and Oracle Weblogic 10.3
<wlconfig url="t3://localhost:7001" username="weblogic" password="weblogic">
bq. <query domain="base_domain" type="Server" name="AdminServer" property="adminserver"/>
bq. <create type="JDBCConnectionPool" name="MediumSecureOnlineNode1Pool" property="customPool1">
bq. bq. <set attribute="CapacityIncrement" value="1"/> \\ <set attribute="DriverName" value="oracle.jdbc.OracleDriver"/> \\ <set attribute="InitialCapacity" value="1"/> \\ <set attribute="MaxCapacity" value="10"/> \\ <set attribute="Password" value="pass"/> \\ <set attribute="Properties" value="user=username"/> \\ <set attribute="RefreshMinutes" value="0"/> \\ <set attribute="ShrinkPeriodMinutes" value="15"/> \\ <set attribute="ShrinkingEnabled" value="true"/> \\ <set attribute="TestConnectionsOnCreate" value="true"/> \\ <set attribute="TestConnectionsOnRelease" value="true"/> \\ <set attribute="TestConnectionsOnReserve" value="true"/> \\ <set attribute="TestTableName" value="SQL SELECT 1 FROM DUAL"/> \\ <set attribute="URL" value="jdbc:oracle:thin:@localhost:1521"/> \\ <set attribute="Targets" value="${adminserver}"/>
</create>
As we would like to automate the process of configuring our weblogic instances using ANT, is there a way to create JDBC datasources that don't have the LegacyType 1 element included in the config ?

Curious if you were ever able to find a resolution to this issue?
I am facing the same thing now with our Ant scripts and WL10.3 connection pools/datasources.
I would like to either specify a different LegacyType or suppress it altogether. Any help would be appreciated.
Many thanks,
Steve

Deployment using JDBC DataSource instead of JDBC URL

Hello,
I've noticed some strange behaviour when deploying an ADF application (11g, latest release) to a WLS (integrated or stand-alone), when using JDBC DataSource as a connection type for the application module.
Normally, when you create your Business Components, a Database Connection is added to the Application Resources panel, eg MyConnection. If you then set your AM to JDBC DataSource instead of JDBC URL, the default datasource would be jdbc/MyConnectionDS. To make the application use the DataSource defined on the WLS, I then uncheck "Auto Generate and Synchronize weblogic-jdbc.xml Descriptors during deployment" in the Application Properties > Deployment tab.
So far so good: after deployment to the WLS, the application uses the DataSource defined on the WLS server (jdbc/MyConnectionDS). When changing it on the server to another database, the application indeed uses this other database. Also, the following is automatically added to the web.xml during deployment to .ear file:
<resource-ref>
    <res-ref-name>jdbc/MyConnectionDS</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
</resource-ref>Now the part that doens't make sense to me: if I delete the password in the Database Connection under Application Resources, I can still deploy the application, but the jdbc/MyConnectionDS on the WLS is not found anymore. While it is still there. I get the following error message:
Unable to lookup Data Source at context java:comp/env/jdbc/MyConnectionDS
oracle.jbo.DMLException: JBO-27200: JNDI failure. Unable to lookup Data Source at context java:comp/env/jdbc/MyConnectionDS
I made the JDev connection (used at development) invalid, and the deployed application stops working (at runtime). While it should just be using the JDBC DataSource defined on the WLS, that is still there. The reason appears to be that when there is no password in the Database Connection in JDev, the entry in the web.xml (see above) is not made during deployment.
I am doing something wrong? Or is this "expected" behaviour?
The reason why it bothers me: I have made a reusable component (a Data Control, let's call it A) from a model project, by deploying it to a ADF library JAR. I've set the AM of this project to use a certain jdbc datasource, which will be defined on the WLS.
When importing the library JAR of A inside another application (B), the connection of the A is added to B. But ofcourse, without the password for security reasons, so we're in the situation described above: When I deploy the new application B, the web.xml is not updated with the DataSource of A, and the application doens't work. And what I would like to avoid, is that whenever someone uses component A, that they have to update the connection details of component A in application B. Because when I fill in the password of application A's Database Connection in application B, all works well again.
I hope this question makes sense. :-)
Thanks in advance,
Chris

Arun and Krithika,
Thanks for your replies. I have already done what both of you suggested:
Chris Schryvers wrote:
I then uncheck "Auto Generate and Synchronize weblogic-jdbc.xml Descriptors during deployment" in the Application Properties > Deployment tab.I can get it to work, both for deployment on the internal WLS as on a stand-alone WLS.
My only question is: why does a property at development time (the empty password of the JDev connection) influence the runtime behaviour (the JDBC DataSource not being found after deployment).
Ofcourse, setting the password for the connection in JDev "solves" the problem. But I want to avoid that everyone who uses the reusable component needs to fill in the password for its database connection. In my opinion, that's the whole point of using a JDBC datasource instead of a JDBC URL: the reusable component just states that there needs to be a jdbc/MyConnectionDS on the server and it can be used as is. Wihtout any modifications at development time.
What's more:
Suppose I import the reusable JAR and its connection is added to JDev, without password.
*) Leaving the password empty: DS not found after deployment (web.xml not adjusted, as mentioned in my original post)
*) Entering the correct password: DS found, web.xml adjusted at deploy time.
*) Entering an incorrect password: DS found, web.xml adjusted at deploy time.
It even works when I enter an incorrect password, which proves that the JDBC DataSource on the server is used, instead of the JDev connection. Then why is the web.xml not adjusted when the password remains empty?
Arun, I'll check the documention that you linked to, but this just seems like an weird decision in the implementation of JDev/ADF. :-)

Proxy Authentication with JDBC Datasource instead of JDBC URL?

Hello,
A requirement for my current project (ADF 10g) is that a user should be able to log in with his regular database account. For the moment, this is implemented using Proxy Authentication, as described in the following article:
http://blogs.oracle.com/jheadstart/2008/01/using_proxy_authentication.html
For now, we are using a JDBC URL defined in the application module config for the BC. In short: a ProxyAuthConnectionPoolManager class was created that overrides the default ConnectionPoolManagerImpl. The getConnection method has been overridden to create a standard connection (with the username/pw defined on the AM), and additionally, create a proxy connection within this connection with the specific user credentials. The (simplified) code:
    public Connection getConnection(String key, String url, Properties props, String username, String pwd) {
        // first fetch a default connection from the pool through the superclass
        Connection connection = super.getConnection(key, url, props, username, pwd);
        // cast into an OracleConnection
        OracleConnection oraConnection = (OracleConnection) connection;
            // close any proxy sessions that would still exist on the connection
            if (oraConnection.isProxySession()) oraConnection.close(OracleConnection.PROXY_SESSION);
            // get a handle on the session scope
            Map sessionScope = ADFContext.getCurrent().getSessionScope();
            if (sessionScope != null) {
                // find the user object in the session (the account the user logs in with)
                ProxyAuthUser user = (ProxyAuthUser) sessionScope.get(ProxyAuthUser.JHS_USER_KEY);
                if (user != null) {
                    // create a property map with the end user credentials
                    Properties proxyProps = new Properties();
                    proxyProps.put(OracleConnection.PROXY_USER_NAME, user.getDbUsername() + "/" + user.getDbPassword());
                    proxyProps.put(OracleConnection.PROXY_USER_PASSWORD, user.getDbPassword());
                    // open the proxy session
                    oraConnection.openProxySession(OracleConnection.PROXYTYPE_USER_NAME, proxyProps);
            return oraConnection;
    }Now, this works perfectly when using a JDBC URL. But when I switch the JDBC Datasource the ProxyAuthConnectionPoolManager class is not called anymore. This is all done in code in the Application Server. While using a JDBC Datasource is actually necessary: otherwise for each environment (dev, test, production,...) a different WAR file is needed.
What class can I override with code similar to the piece above, to open a proxy connection inside the existing connection, when using a JDBC Datasource?
Your help would be greatly appreciated!
Chris

Hello Krasimir,
Frank Nimphius gave me the solution to this problem. The prepareSession is indeed the best place to put the code:
   private OracleConnection oconn = null;
   public void prepareSession(SessionData SessionData) {
      super.prepareSession(SessionData);
      oconn = ((PrxyTransactionImpl)this.getDBTransaction()).getPrxyConnection();
      // Specify the user that connects through the proxy user and its roles
      Properties prop = new Properties();
      prop.put(OracleConnection.PROXY_USER_NAME,"hr");
      prop.put(OracleConnection.PROXY_USER_PASSWORD,"hr");
      //prop.put(OracleConnection.PROXY_ROLES, roles);
      // Open the proxy session (DB-authenticated users)
      try {
         oconn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME, prop);
      catch (SQLException e) {
         // Close the connection, to avoid connection to remain open after exception
         oconn.abort();
         e.printStackTrace();
   }But Frank also created the following helper classes to extend the ADF BC behavior:
   package oracle.sample.dbprxy.adfbc;
   import oracle.jbo.server.DBTransactionImpl2;
   import oracle.jbo.server.DatabaseTransactionFactory;
    * TransactionFactory that returns PrxTransactionImpl, which is a subclass of
    * DBTransactionImpl2
    * @author Frank Nimphius
   public class PrxyDatabaseTransactionFactory extends DatabaseTransactionFactory {
      public PrxyDatabaseTransactionFactory() {
         super();
       * Override the create method to return an instance of PrxyTransactionImpl instead
       * of DBTransactionImpl2
       * @return PrxyTransactionImpl
      public DBTransactionImpl2 create() {
         return new PrxyTransactionImpl();
   package oracle.sample.dbprxy.adfbc;
   import oracle.jbo.server.DBTransactionImpl2;
   import oracle.jdbc.internal.OracleConnection;
   public class PrxyTransactionImpl extends DBTransactionImpl2 {
      public PrxyTransactionImpl() {
         super();
       * The DBTransactionImpl2 does not expose the connection in a public
       * method. This class is a wrapper to expose the connection to the
       * BC app, so it can be accessed in the ApplicationModuleImpl class
       * @return OracleConnection - SQL Connection
      public OracleConnection getPrxyConnection() {
         return (OracleConnection) this.getJdbcConnection();
   }In the configuration of your Application Module, you have to set the property "TransactionFactory" (normally the last one in the list) to oracle.sample.dbprxy.adfbc.PrxyDatabaseTransactionFactory. This way, the DBTransaction() of your AM will have a getPrxyConnection() method and you will have the connection at your disposal. You won't need the createPreparedStatement in your code anymore.
To close the connection, this is the code behind my "logout button" on the backing bean. Application Module Pooling and Connection Pooling will take care of the rest for you!
   ExternalContext ectx = FacesContext.getCurrentInstance().getExternalContext();
   HttpSession session = (HttpSession)ectx.getSession(false);
   session.invalidate();Another thing: be sure to set the internalconnection property to a different JDBC Datasource (or file based) than the one you are using to connect to the database (the default value). Otherwise connection pooling will be confused and there will be too much pending database connections.
This works for me, all sessions are closed in time and logging out seems secure. I do not have my complete, adjusted code here at my disposal, but next week, when I'm back at work, I'll have a look to see if there is anything I forgot to mention. So this should get you started, but I'll keep you posted!
A huge thank you to Frank again for helping me (/us) out with this problem!! And sorry I forgot to post the answer here sooner. I was too busy with testing it. :-)
Regards,
Chris

Cannot deploy application because of JDBC datasource target misconfigured

--- environnement ---
Weblogic 10.3.2
Windows 2008 R2
Sun Java 6
Hello, I'd like to have your advices on my issue.
I tried to deploy an application in my weblogic domain but it kept on status deploy running
My domain is configured as follow
clusterA and clusterB
JDBC datasource targets on clusterA and clusterB
Today we had to rename clusterB to clusterC
and we cannot start the managed servers (they stayed in ADMIN state) so we tried to redeploy the application but the deployment process'status was deploy running
After investigating for a very long time, we finaly noticed that our JDBC datasource was misconfigured. After correcting this, the deployement was successfull.
now I'm wondering how a misconfigured JDBC datasource can prevent a deployement of an ear, maybe the code is requesting something during its deployement but I don't know the application and looking at the stacktrace didn't give me any clue except the hibernate message.
Thanks in advance for your advices.
For info here's the stacktrace:
####<Apr 13, 2011 5:32:24 PM CEST> <Error> <Deployer> <EQDG1UZSMRTD001> <SmartDispatcherNodeConsole1> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1302708744385> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1302708738983' for task '36'. Error is: 'weblogic.management.DeploymentException: '
weblogic.management.DeploymentException:
     at weblogic.application.internal.BaseDeployment.throwAppException(BaseDeployment.java:157)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:371)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: org.hibernate.HibernateException: 'hibernate.dialect' must be set when no Connection avalable
     at org.hibernate.dialect.resolver.DialectFactory.buildDialect(DialectFactory.java:107)
     at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:138)
     at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2119)
     at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2115)
     at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1339)
     at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)
     at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
     at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:132)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:343)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:323)
     at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:125)
     at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:336)
     at weblogic.deployment.EarPersistenceUnitRegistry.initialize(EarPersistenceUnitRegistry.java:75)
     at weblogic.application.internal.flow.InitJpaFlow.prepare(InitJpaFlow.java:38)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hello,
Here is the solution...
Solution 1:
Undeploy sap.com/cafUIservicebrowser from SP06 or SP07 before starting upgrade to SP11.
Solution 2:
Upgrade to SP08 first and than to SP11.
The Solution was discussed on NW04s STAB and accepted due to following reasons:
- There will be not much customers upgrading from SP06 or SP07 to SP11. The most of customers have already upgraded to SP08 and will not be affected by this issue.
- Unchecking the Web Dynpro check before upgrades from from SP06 or SP07 to SP11 is unacceptable.
For More info, check the SAP Note 1010640
Reward points of my reply was useful..

What is the method of getUserName() for JDBC DataSource in JDeveloper 11g.

Hi All,
I am facing a issue about getUserName() Method.
The below method
getDBTransaction().getConnectionMetadata().getUserName()
working fine for JDBC URL While the same method not working for JDBC DataSource.
So What is optional method for getUserName() for JDBC DataSource, I need JDBC DataSource because in Our Standalone weblogic server we using data source.
Maroof

Hi Vohar,
JNDI is there then how we can get user name you have any idea?
Our Connection.xml look like below
user oraJDBC 1500 192.168.0.0 user1 thin

JavaFX Composer and jdbc datasource

I'm trying to build a javafx application that is basically a CRUD interface for a Microsoft SQLServer DB. I can drag and drop the jdbc datasource into my scene, and I can execute the select query against the table. I have copied over the jar file containing the sqlserver driver (using the Project->Properties dialog). When I try to run the project, I get an error message that no suitable driver is found for the connection string that is being used.
The connection string for the sqlserver driver is: jdbc:sqlserver://DEVSQL-SERVER:1433;databaseName=User;
Does anyone know if it's not currently possible to use datasources other than the built-in derby db?
Seems like you should be able to use any datasource if you have the required jar file for the drivers.
TIA,
Kevin

Hi,
The JDBCDataSource is using JDBC API but it does not register/initialize any particular driver.
Therefore you should have the following line of code added at the beginning (right after the package statements) of the Main_run.fx file:
Class.forName ("jdbc.Driver");
where jdbc.Driver is a fully-qualified class name of your JDBC driver.
Regards,
David

Trying to switch from JDBC URL - JDBC DataSource

I have built and run a JHeadstart 10.1.2 application using JDBC URL defined database connections.
I am now trying to switch to use JDBC DataSource definitions to make the database connection independant from the application so that the same ear file can be deployed to different application servers (dev vs test environments).
I have tried changing the Connection Type of the Business Component:
Configurations > Edit > Connection Type
from the previously defined JDBC URL to a JDBC Datasource defined within the embedded OC4j Application server. After making the change, rebuilding and restarting the server it still retrieves information from the previously defined URL.
Is there something I need to regenerate/rebuild/reconfigure?
Thanks,
Kevin

Hi Steven,
I've seen that article. It's quite detailed and certainly helped until I ran into a VerifyError something like:
java.lang.VerifyError: (class: oracle/ord/im/OrdDocBase, method: create signature: (Loracle/ord/im/OrdDocBase;Loracle/sql/Datum;I)Loracle/sql/CustomDatum;) Incompatible object argument for function call at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:140) at oracle.jheadstart.util.BindingUtils.class$(BindingUtils.java:66) at oracle.jheadstart.util.BindingUtils.isIntermediaBinding(BindingUtils.java:169) at oracle.jheadstart.controller.strutsadf.action.JhsDataAction.setBindingInputHandlers(JhsDataAction.java:1159) at oracle.jheadstart.controller.strutsadf.action.JhsDataAction.processUpdateModel(JhsDataAction.java:622) at oracle.adf.controller.struts.actions.DataAction.processUpdateModel(DataAction.java:508) at oracle.adf.controller.lifecycle.PageLifecycle.handleLifecycle(PageLifecycle.java:112)
I found this forum posting helped me...
Re: JHeadstart Deployment Issue
I couldn't run the application in a standalone instance of oc4j 9.0.4 even after following the deployment instructions found in this and other posts. It wasn't until I came upon a JavaWorld article from 2001 about VerifyError...
http://www.javaworld.com/javaworld/jw-06-2001/jw-0615-howto.html
I added -noverify to the startup arguments and the application ran fine.
I admit I am a little concerned that I need to run without jar verification. Have you seen this before? Is there another way to deal with this?
thanks,
Kevin

Maximum Number of JDBC Datasources

Does anyone know if there is a limit or if there is a
recommended max to the number of JDBC datasources that a standard
version of CF8 can handle?
We have approx. 500 on our server and occasionally the server
restarts due to Out of Memory errors. This most recently happened
when adding a new datasource through the CF Admin, which is what
led me to asking this question.
Thanks, Chris

> Does anyone know if there is a limit or if there is a
recommended max to the
> number of JDBC datasources that a standard version of
CF8 can handle?
>
> We have approx. 500 on our server and occasionally the
server restarts due to
> Out of Memory errors. This most recently happened when
adding a new datasource
> through the CF Admin, which is what led me to asking
this question.
A datasource is just a bunch of setting which get stuck in an
XML file.
THey don't have any RAM footprint in and of themselves.
However, the more DSNs you have, it suggests the more DB
traffic you have,
and indeed probably more activity on the box.
How much RAM have you got allocated to the JVM?
Have you used FusionReactor or similar to monitor what's
going on with the
RAM the JVM has?
Adam

How to create a JDBC datasource thru script/xml?

Hello All,
Is there any way to create a JDBC datasource using some script or xml file that
can be deployed to WLS 7.x?
This feature is required for our J2EE application installation program.
rgds
MS

Hi
See this thread for connecting SQL Server
Re: what is the process to connect to database from webdynpro ?
For Oracle
try
{DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
Connection conn = DriverManager.getConnection("jdbc:oracle:thin:@Oracle_server_ip:Oracle port:SID of the Database","user_name","password");
Statement stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery("your query");
}catch(Exception e){
see this thread
Webdynpro and Oracle
Kind Regards
Mukesh

Creating JDBC datasource in Weblogic 10

I have a requirement to create JDBC datasource at runtime if necessary. Weblogic provides JMX services for creating datasource however this required credential of Admin Server (node manager).
As my application is deployed in one of the managed node and as per the security policies admin credential will not be available..
so how can I create a datasource at runtime on fly applicable only for my node.. this should not require admin credentials?
Edited by: user5798282 on Apr 28, 2010 12:50 PM

Thanks for your reply. However both seems to be way of creating datasource in weblogic 8 . The first one is deprecated in Weblogic 10, the 2nd one requires weblogic admin username and password

Changing JDBC Datasource Configuration for Report with Sub reports at once

The Env details are as follows
CR Developer
Version 14.0.2.364 RTM
We are using JDBC Connection Datasource for our CR2011 report which contains 30+ sub reports. Each of the sub report uses a JDBC Datasource to connect to Postgres database and Since the JDBC connection string changes on each environment we need to edit each sub report every time we switch environments.
Is there a easy way to accomplish this on all sub reports at one shot?
I am aware that if we use ODBC connection it would be easy since we can just change the DSN config and it will start working. But we are not using ODBC connection since We are seeing that our report (with too many sub reports) crashes when we use ODBC driver for Postgres.
Any help/suggestion would be appreciated.

Hello,
CR also has a fully support Java Reporting Engine. If you have Java developers available check out this forum:
SAP Crystal Reports, version for Eclipse
You can find more info and samples from here:
http://wiki.sdn.sap.com/wiki/display/BOBJ/BusinessIntelligence%28BusinessObjects%29+Home
And help.sap.com for the SDK reference material.
Don

MSSQLServer jdbc connect problem on ODI 11G R2

I have a MS SQL Server jdbc connect problem on ODI 11G R2 / Windows server 2008 64 bits.
Tried, one by one, all versions of Microsoft drivers.
Sqljdbc4.jar copied to : %appdata%\odi\oracledi\userlib\
The Topology connect syntax is :
driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
URL : jdbc:sqlserver://<host>:1433
=> All the topology tests end with time-outs.
Installed 10G ODI.
Works with 1.4 java and sqljdbc.jar version 2 jdbc driver.
Times out with version 3 and/or Sqljdbc4.jar + JAVA_HOME & ODI_JAVA_HOME set to 1.6 path.
also tried, with no success (time-outs) on either 10g or 11g :
com.inet.tds.TdsDriver
jdbc:inetdae7://<host>:1433?database=<DB>
same results for :
net.sourceforge.jtds.jdbc.Driver
jdbc:jtds:sqlserver://<host>:1433
Any suggestions for a fix?
Many thanks in advance.

Hello,
ODI (11g) Studio is certified on Windows 32 bit only, not on 64bit.
However you may still install it and configure ODI Studio to run with a 32 bit java.
Details pls see Master Note For ODI 11g Install Issues And Questions (Doc ID 1214428.1).
To connect to SQL Server:
# Check and make sure the authentication mode of your Microsoft SQL Server Server is set to "SQL Server and Windows" or "Mixed", otherwise Oracle Data Integrator (ODI) is unable to connect to the database.
# Before you create the Oracle Data Integrator (ODI) Dataserver in Topology Manager > Physical Architecture, stop all ODI processes, and place the JDBC Driver file in the ODI's userlib and "/drivers" folder.
For ODI Studio (Local No Agent)
%APPDATA%\odi\oracledi\userlib
%APPDATA% is the Windows Application Data directory for the user (usually C:\Documents and Settings\<user>\Application Data).
Standalone Agent
ODI_HOME\oracledi\agent\drivers
Note: If you decide to use the DataDirect driver that comes with ODI 11g install/ embedded in ODI 11g
weblogic.jdbc.sqlserver.SQLServerDriver
Then you don't need to worry about this step.
# Make sure that the database is the default database of the user account employed by ODI for connection, and that the password is correct.
# Verify (in your Microsoft SQL Server Server network configuration) that TCP/IP has been enabled on port 1433.
For more details see How To Set Up JDBC Driver Connections For The Microsoft SQL Server For ODI (Doc ID 423914.1)
If you try sqljdbc.jar, you need to configure ODI_JAVA_HOME to jdk1.5
sqljdbc4.jar, jdk1.6 (since ODI 11g requires jdk1.6, I'd suggest sqljdbc4.jar)
More see Compatibility Matrix For Java Machines And JDBC Drivers Used With ODI (Doc ID 807235.1)
Hope that helps other people who run into this,
Edited by: user742480 on Apr 4, 2011 12:06 PM

JDBC Datasource problem in AM configrations

Similar Messages

Maybe you are looking for