WLS 10.3, JDeveloper 11- JDBC/JNDI

I've been looking for a couple days now, and i can't find a understandable answer.
I am trying to implement Security into my ADF application. I would like it to use Active Directory, (possibly from more than 1 AD server) or permissions based on there DB users/passwords and roles.
I am using JDeveloper 11g production release, and ADF faces. I am not sure if we can use LDAP as i am not sure if it is set up. If anyone can lend a helping hand and let me know if any of these are viable options that would be great!!
If these are not good/viable options, is there a easy way to add users/roles to a existing production application without access to Jdeveloper or having to re-deploy the application?
Thanks Everyone!
Edited by: Dan Surkan on 18-Nov-2008 11:49 AM - changed subject

So the above questions are still open and i have another,
I am trying to deploy my app to the WLS 10.3 server. I deploy through JDeveloper or through the server control panel (install the WAR file) and i get the same error for both:
<Nov 18, 2008 12:15:13 PM CST> <Error> <HTTP> <BEA-101371> <There was a failure when processing annotations for application ----directory----/LocalServer.war. Please make sure that
the annotations are valid. The error is javax.faces.webapp.FacesServlet>
<Nov 18, 2008 12:15:13 PM CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with
ID '1227032103734' for task '0'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'LocalServer.war'
weblogic.application.ModuleException: Failed to load webapp: 'LocalServer.war'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
Truncated. see log file for complete stacktrace
<Nov 18, 2008 12:15:14 PM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for app
lication 'Dashboard'.>
<Nov 18, 2008 12:15:14 PM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Failed to load webapp: 'LocalServer.war'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
Truncated. see log file for complete stacktrace
java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
Truncated. see log file for complete stacktrace
Anyone have any insight on this.
If you need me to post any of my xml files, just let me know which ones and i will put them up ASAP!
ps. Yes i did the ADF patch for the WLS server.
--Dan Surkan
Edited by: Dan Surkan on 18-Nov-2008 1:40 PM

Similar Messages

CR4E - New JDBC (JNDI) connection at runtime

Is it possible to create a new JDBC (JNDI) connection at runtime using the propertyBag to set the attributes? I tried this but received error message stating "error finding jndi name".

Are you specifying a JDBC or JNDI connection?
If JDBC, did you set the (Optional) JNDI Connection property?
If you set the JNDI property for the JDBC connection, it'll try connecting to the JNDI.
The JDBC has the optional JNDI property, so that you can design a report against JDBC, then use the JNDI when deployed to a J2EE.
Sincerely,
Ted Ueda

A bug in creator when creating jdbc jndi connection

Hi,
I am using sun java studio creator for jdbc jndi connection. The syntax is
Context ctx = new InitialContext();
DataSource ds = (DataSource)ctx.lookup("java:comp/env/jdbc/mydb");
conn = ds.getConnection();
It's failed. Once I change to ctx.lookup("jdbc/mydb") and the connection is created.
Once deployed to tomcat, it seems only java:comp/env/jdbc/mydb is working.
The full path(java:comp/env/jdbc/mydb) seems right from my google search.
Why creator using jdbc/mydb? Is it a bug to creator?
Thanks,
Jie

I mean a resource reference in web.xml file that looks like this:
     <resource-ref id="ResourceRef_1103225373500">
          <res-ref-name>DBConnection</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Application</res-auth>
          <res-sharing-scope>Shareable</res-sharing-scope>
     </resource-ref>
where DBConnection is the resource alias I mentioned before:
DataSource ds = (DataSource)ctx.lookup("java:comp/env/DBConnection");
Using WebSphere a binding between this above defined ResourceRef and JNDI mapping must be defined in a file called ibm-web-bnd.xmi. The content of this file will look like this:
<?xml version="1.0" encoding="UTF-8"?>
<webappbnd:WebAppBinding xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:webappbnd="webappbnd.xmi" xmi:id="WebAppBinding_1" virtualHostName="default_host">
<webapp href="WEB-INF/web.xml#WebApp"/>
<resRefBindings xmi:id="ResourceRefBinding_1103225373500" jndiName="jdbc/mydb">
<bindingResourceRef href="WEB-INF/web.xml#ResourceRef_1103225373500"/>
</resRefBindings>
</webappbnd:WebAppBinding>
Obviously using WSAD all of that could be done using IDE. In your case and using Sun IDE, I am not sure. But this is basically the concept of needed mapping in order to reference your JNDI without getting an error. At least this is how we resolved the error you are encountering.
Hope that helps!

How to configure jdbc/jndi connection in crystal report 10

Post Author: effy
CA Forum: Data Connectivity and SQL
i have tried to configure jdbc/jndi connection , i have both
drivers data base side and crystal report side but i
can't configure it. so please help if u know
something.

Sorry, but I'm not on a home pc, I'm working on a virtualized pc with a long chain of permissions ... so I cannot simply download and run an utility...
Instead... I think (I WAS thinking) someone from SAP can tell me this info ... Probably I'll buy a paid assistance ticket... But really it's a strange thing that a simply connection from a (so) paid software need a so difficult problem solving routine..
I edited my environment variales: JAVA, PATH; CLASSPATH; JAVA_DIR, and a long list of others ... to ALL point to ALL of directory containing used jars...
.. I asked my SysAdmin to edit CrConfig.xml and it's done ... classpath are rights, jdbc infos are also ok, ...
.. but none ...

WLS 8.1 Type 4 JDBC Driver SQL Server sp_prepare/sp_execute

Hello,
I have a question regarding performance troubleshooting in a production situation using the WLS 8.1 Type 4 JDBC Driver for SQL Server and SQL Server 2000.
This driver compiles a sql statement on the sql server using sp_prepare(), saving a handle to it. It will execute the statement using sp_execute(). Subsequent uses of the same statement will skip the sp_prepare(), and just call sp_execute(). So, ideally, for a particular statement, you should see one sp_prepare, and a lot of sp_execute's.
My WLS app is running along in production, and I detect a performance problem of some sort on the sql server, such as excessive IO, or blocking.
I turn on the sql server profiler, and I can see a bunch of
sp_execute 123, 'one', 'two'
sp_execute 123, 'foo', 'bar'
with bad IO. How do I determine what the original SQL was that was used in the sp_prepare?
The only way I can see to do this is to have the sql server profiler always running to catch every sp_prepare. I can't believe that this is a best practice.
How are you all handling this type of situation?
Thanks,
Dave

Dave Ballard wrote:
Hi Joe,
Thanks for the suggestions. The main issue I have with both is that they
require a server restart to enable. Can't do that on my production system.
The best I've come up with since I posted is to locate the poor
performer/blocker real-time via sysprocesses, then use the sqlhandle column
to call fn_get_sql to get at least some of the sql submitted with sp_prepare().
Not pretty and difficult to do on a busy system.
What's bugging me about the sp_prepare/sp_execute technique used by the driver is:
1) sp_prepare/sp_execute don't seem to be documented anywhereThey are internal to SQLServer, so it'd be MS to document them or not.
2) It is at best inconvenient to have to troubleshoot performance issues (requiring
a server config change, server restart, and manual reconcile of two different,
possibly very large, logs based on timestamp).
Your idea to disable the stored procedure cache is interesting, but still requires
a server restart to enable, and another to disable.
To me this is a large step backwards in manageability of my system. What I don't
understand is that I don't see much discussion about this topic on any forums,
so I wonder if I'm just missing something here (maybe everyone's using Oracle).No, the same sorts of issues would be needed with Oracle. DBMSes must make tradeoffs
between normal-case runtime performance, and the instrumentation that would be needed
to simultaneously monitor performance problems.
Joe
>
Thanks,
Dave

JDBC(JNDI):Connection dinamically managed

Hi all,
I'm using
1) Crystal Reports 2008 for the reports' design,
2) Java Reporting Component (version 18.8.4.1094) for the integration in java environment,
3) JBoss (version 4.2.3) as Application Server
4) Oracle 11 as DBMS
in a web application.
When I create a report using JDBC (JNDI) and specify as the "Connection Name (optional)" the following string "java:jdbc/name_data_source",
How is managed the connection of the report and any sottoreports? In other words are the connections dynamically managed by the container web or ejb?
Thank you very much.

Hi, Andrea,
I'm gonna' make a few guesses here:
2) Java Reporting Component (version 18.8.4.1094)
I think you mean Crystal Reports for Java (CRJ) 2.8 version 12.2.209.1094. Neither the JRC (the name for the 1.x series) nor the CRJ (the 2.x series) has any version number in the 18.x range.
sottoreports
I think that means "subreports."
are the connections dynamically managed by the container web or ejb?
There are two ways the connections can be managed. If you've created a JNDI connection (a named connection), then you can base a report off of it, then at a later date change where the JNDI connection itself points to and the report should still work correctly, as long as the new target database shares the same schema as the original.
The other way you can manage the connection is to use code to change the database connection information inside the report itself. In this way, you could change it from one JNDI connection to another or even to another type of connection altogether. Again, however, the schemas between the old and the new connections must match.
Regards,
Bryan

WLS logger in Jdeveloper

how I can set WLS logger in Jdeveloper embeded weblogic to get following informations:
<ViewObjectImpl> <getQueryHitCount> [###] ViewObject:[model.views.MyVO]MyVOName Estimated Row Count: NNN
I am looking to find number of records that are returned.

User, sorry to say that these kind of problems can't be easily diagnosed.
What I can say it's that 1000 records are not much as they are not normally loaded. Only if you load them all you can run into problems but this depends on other factor too.
Some general advice: try to find out what it's going on in your application before you see the increase in memory and application modules. I hope you have some log messages in your code to help you find this out. If not start adding them.
You should monitor the memory consumption on your server on
parallel to find out when you run low on resources.
Timo

Cannot connect MS SQL Server2005 by using JDBC(JNDI) connection

Hi all,
I met a problem when I was trying to create a JDBC(JNDI) connection in crystal report 2008, the following error dialog shows up, it said:
Database Connector Error: 'SQL Exceptions: [SQL State:] S1000 [Error Message:] [Microsoft][SQL Native Client]Connection is busy with results for another command'
here is the steps how to reproduce this problem:
1) create a DSN(Data source name) in ODBC Data Source Administrator dialog, suppose the DSN is test
    (and the DSN test show it works well)
2) start up Crystal Report 2008, click New to create a new report, the Standard Report Creation Wizard show up
3) expand Create New Connection node, then double click JDBC(JNDI) note
4) the JDBC (JNDI) dialog shows up, chooose JDBC Connection in the dialog, and fill the empty fields with:
   Connection URL: jdbc:odbc:test
   Database Classname:sun.jdbc.odbc.JdbcOdbcDriver
5) click next, it comes to the next pannel, and fill the empty fields with:
    Database: MyTestDB
    UserID: sa
    Password: sa
6) then click Finish buttion.
7) a new connection is created, but when I expand the new created connection, an error dialog shows up
Database Connector Error: 'SQL Exceptions: [SQL State:] S1000 [Error Message:] [Microsoft][SQL Native Client]Connection is busy with results for another command'
does anyone knows what's wrong with my setting? any help would be appreciated.
Best Regards
Tian-liang

Hi Tian-liang,
Try using Microsofts JDBC driver rather than Suns. Also search these forums, other have run into the same issue.
Thank you
Don

Problem using JDBC (JNDI) DataSource and data-sources.xml w/ OC4J

I have a JClient application developed in JDev X. It works fine when using a JDBC URL for the connection (which then writes the connection into the BC4J.xcfg files, one for each application module). However, I would like the app to retrieve the data source from the server's data-sources.xml file. However, when, on the configurations tab of the application module I set the connection type to JDBC DataSource, and give it the JNDI name, it does not work, either with the embedded OC4J or the stand-alone OC4J. Any suggestions???
In the stand alone OC4J I verified that the data source exists (using java -jar admin.jar ormi://nemethzoltan3 admin welcome -application adatklinika -testDataSource -location jdbc/adatklinikaCoreDS) ... so the data source is defined in the data-sources.xml. Of course the error I get is JBO-30003.
If I just try to "test" the data source in Jdeveloper (using the context menu of the app module, and setting it to use the adatklinikaCoreDS) I get a JNDI error: unable to lookup data source and at level 3 a "javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial". I checked, the data source is defined under tools->embedded OC4J properties->data sources.
If I try to run the main form, simply nothing happens.
Please help!!!

Ok, figured out why running from jdeveloper wasn't working: the embedded OC4J server wasn't started (start it by running an html page from your project or something...and make sure you don't have a stand-alone oc4j running). AND more importantly it didn't have the library "embedded oc4j client" library included (project properties -> profiles -> development -> libraries)...which is needed for whatever reason.
Now to try and get it working with the stand-alone OC4J...

WLS 10.3 ClassCastException obtaining JDBC connection

I have a problem obtaining a JDBC connection in a java client application, using a WLS Datasource.
- I've configured a JDBC datasource in a WLS 10.3 instance, using the Oracle thin driver (not the XA version) - and have successfully targetted this to my server and tested the connection via the console.
- When viewing the JNDI Tree for the server, the Datasource is visible as expected.
However, when I attempt to use a simple client program to obtain a datasource and JDBC connection I get the following error :
java.lang.ClassCastException : weblogic.jdbc.common.internal.ConnectionEnv cannot be cast to java.io.Serializable
Debugging shows a datasource is obtained and that the ClassCastException is thrown when an attempt is made to get a connection from the datasource. Note this code has been used successfully for previous WLS versions to obtain and test a connection (WLS 8.1 - WLS 10) and follows the expected steps :
Hashtable<String, String> ht = new Hashtable<String, String>();
ht.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
ht.put( Context.PROVIDER_URL, "t3://localhost:7001");
javax.naming.Context ctx = new InitialContext( ht );
ds = (javax.sql.DataSource) ctx.lookup( pDataSourceName );
Connection con = ds.getConnection();
The client app has the following Jars on the classpath :
wlclient.jar
jdk1.6.0_07 runtime jar
The client code has been built using jdk1.6.0_07
i) Can you confirm if any additional libraries are required on the classpath
ii) Please indicate if there are any special steps required to obtain a JDBC connection in WLS 10.3
Thanks for your help.
Edited by: user554713 on 23-Dec-2008 02:27

In a Java client the HashTable properties are required to be set.
Context ctx = null;
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL,         "t3://localhost:7001");
try {    ctx = new InitialContext(ht);
// Use the context in your program }
catch (NamingException e) {    // a failure occurred }
finally {    try {ctx.close();}    catch (Exception e)
{      // a failure occurred    } }Edited by: dvohra16 on Dec 10, 2009 5:39 PM

The mysteries of JDBC, JNDI, and Tomcat 5.5.4

Like thousands beforefore, I can't get connection pooling to work in Tomcat. I followed all the steps:
- put jar file for MySQL JDBC driver in TOMCAT_HOME/common/lib
- put the Jakarta Commons libs in the same location
- put resource declaration in META-INF/context.xml, per the Tomcat 5.5 docs like so:
<Context docbase="C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\commutercorps"
    path="\commutercorps" >
    <Resource name="jdbc/commutercorpsds"
        auth="Container"
        type="javax.sql.DataSource"
        maxActive="100"
        maxIdle="30"
        maxWait="10000"
        username="myusername"
        password="mypassword"
        driverClassName="com.mysql.jdbc.Driver"
        url="jdbc:mysql://localhost:3306/commuter_corps_signup"/>
</Context>- added resource ref in web.xml
    <resource-ref>
        <description>DB Connection</description>
        <res-ref-name>jdbc/commutercorpsds</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
    </resource-ref>I also double checked my connection URL and found that it does work fine when do this in my Java code:
Class.forName("com.mysql.jdbc.Driver");
Connection con =
    DriverManager.getConnection
    ("jdbc:mysql://localhost:3306/commuter_corps_signup", "...", "...");When I try to use Tomcat 5.5.4, JNDI like this...
                try
                    InitialContext initialContext = new InitialContext();
                    DataSource dataSource =
                            (DataSource) initialContext.lookup
                            ("java:comp/env/jdbc/commutercorpsds");
                    Connection con = dataSource.getConnection();
                    Statement stmt = con.createStatement();
                    stmt.executeUpdate(SQLMaker.getInsert(request,
                            request.getParameter("table")));
                    con.close();
                    stmt.close();
                } catch (NamingException e)
                    System.out.println(e.getMessage());
                    e.printStackTrace();
                }...I get...
Cannot create JDBC driver of class '' for connect URL 'null'
Caused by: java.sql.SQLException: No suitable driver
Any help would be greatly appreciated.
Thanks,
E

I used to get the message
Cannot create JDBC driver of class '' for
connect URL 'null'
No suitable driverError.
I was running, jakarta-tomcat-5.0.14.exe on windows.
I had it installed on a path without spaces
d:\tomcat5\Good.
I wanted to use Hibernate. So i used, extensiontools.What's that?
First create a env var: HIBERNATE_HOME pointing to
the hibernate extracted dir.No need for this.
Modify setenv.bat to correct %CP% for
commons-logging, commons-collection and anything
else: the version string at the end of the jar
changes.Wrong. You shouldn't be doing this.
Then run ddl2hbm, straightforward, fill info in all
tabs and hit generate. Will show some error message,
but still creates xmls.I don't see what any of this has to do with Tomcat deployment.
Then run hbm2java, and hand over each xml file as
parameter. Creates some java files in generated dir.
Modify the toString method to something simpler and
remove the import for apache class.All great, but still has nothing to do with Tomcat deployment.
move them over to webapp classes.You should create a WAR file or a separate context directory for your application under /webapps. If you're doing anything else, it's wrong.
Create JNDI in sever.xml as mentioned.Nope. Shouldn't be editing server.xml. Put that stuff in an application-specific context.xml, which goes in the META-INF of your WAR file.
Create reference in web.xml as mentioned.Good.
Goto conf/catalina/localhost/<webappname>.xmlNo need for this. Don't know what you're doing here.
add the line
<ResourceLink name="jdbc/Oracle"
type="javax.sql.DataSource" global="jdbc/Oracle"/>
replace Oracle with your datasource name.
and i got me workingMight be working, but it's not really correct.
%

JDBC JNDI INITIAL_CONTEXT_FACTORY

sigh
Still haven't gotten the hang of JNDI completely. Below's my code. I'm going to access a JDBC database. What INITIAL_CONTEXT_FACTORY should I use? The file system one seems to be the wrong one. Does it matter that it's an MS Access database? Isn't there just some generic INITIAL_CONTEXT_FACTORY for all JDBC databases?
<vent>
Why isn't there some handy list somewhere that shows the common INITIAL_CONTEXT_FACTORYs? Why do we have to hunt them down?
</vent>
Thanks,
Gary
public Connection getConnection(ClientSession clientSession) throws SQLException, NamingException, RemoteException
Properties env = new Properties();
InitialContext ic;
DataSource ds;
Connection connection;
env.setProperty(InitialContext.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.fscontext.RefFSContextFactory");
ic = new InitialContext(env);
ds = (DataSource)ic.lookup("java:comp/env/jdbc/"+getDataSourceName(clientSession));
connection = ds.getConnection();
return connection;

If you don't know what JNDI service you should be
using then you're in big trouble.
If you're developing code for a J2EE App Server or
Tomcat then the JNDI Service will already be running
in the Container and you need do no more than get the
env context and lookup the DataSource.
If you're developing a client app then you must know
the J2EE server that you're connecting to and so will
either be running in a ClientContainer or using a
jndi.properties file provided for you by the Server.
So what is it that you're trying to do?Write an RMI server that accesses a JDBC database. Instead of using DriverManager, I thought I'd give JNDI a whirl.
The client apps of my server might be servlets or a Swing app.

WLS Groups and JDeveloper Enterprise Roles

When there are roles (global, domain, etc.) in the WLS Console, they seem to not have any representation in JDeveloper. It seems that JDeveloper Enterprise Roles correspond to WLS Groups. When I add permissions in the jazn-data.xml, it is Groups that I have to grant to users in the WLS Console, not roles.
SecurityContext.getUserRoles() also returns a list of WLS Groups assigned to given user.
Is it some disarray in the terminology, or am I doing something wrong?

Hi,
The term "Enterprise Roles" match to WLS groups. Enterprise is a more genric synonym for user groups as on different servers these may have different names otherwise. Note that getUserRoles() shows the enterprise roles and the application roles a user is member of
Frank

How can we use Cloudscape and JDBC, JNDI

Hello all,
I was trying to install the example included in the J2EE called RMS but have problems to do that.
I got this message:
reference java:comp/env/CloudscapeDB is using a JNDI name that is not bound jdbc/CloudscapeDB
How can I edit in the default file in J2EE.
Please help.
Thank you

Please, help and reply

Jdeveloper and jdbc

Hi all
If I use jdeveloper 3.2 , does it include jdbc or where can I get a jdbc driver ?
And if I use jdeveloper 9 , does it contain a jdbc driver ?
Thanks

JDeveloper9i contains JDBC. If you browse your Windows Navigator and you go to the folder where you installed JDeveloper, you can see that. If there is a folder in the JDev directory with the name JDBC, than you've got it.

WLS 10.3, JDeveloper 11- JDBC/JNDI

Similar Messages

Maybe you are looking for