Don Andrews Ne

Greenhorn
+ Follow
since May 01, 2009
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Don Andrews Ne

You need to define a resource reference (using the resource-ref tag) in web.xml and then figure out how to map that resource to a real resource in the web server. If you're using WebSphere app server then the deployment step will take care of that for you (you'll be prompted to map the webapp resource to a server resource). I don't know how other servers handle the deployment mapping. In your case you would specify <res-ref-name>ws/MyConfigedWorkManager</res-ref-name> as the resource reference name. Then your JNDI call would be context.lookup("java:comp/env/ws/MyConfigedWorkManager").
14 years ago
Your best bet is probably to include it in the enterprise application or web application you're working with. That way it won't interfere with other applications and you'll have better control over the logging options.
14 years ago
IBM Http Server is Apache Http Server plus some additional platform-specific directives. If you know Apache Http Server you know almost all there is to know about IBM Http Server. I know that on i5/OS (aka OS/400) there are several directives dealing specifically with OS/400 entities. Another subtlety about i5/OS is that the configuration file is stored in EBCDIC so you can't just edit it with a Ascii editor. I imagine on z/OS the situation is similar.

WebSphere Application Server is a J2EE- or JEE-compliant Java Application Server and is a completely different product. Think of it as a Java plugin for Apache Http Server equivalent to any other language plugin (CGI script, PHP, Ruby, Cobol, etc.). Http Server (Apache/IBM) doesn't understand how to run a Java program but the Application Server plugin does. Http Server passes the entire HTTP request to the plugin to process; Application Server processes the request and passes the HTTP response back to Http Server which in turn passes it to the TCP/IP stack for serializing back to the browser.
14 years ago
Go to your favorite search engine and type where # is the Java version (5, 6, etc.) and class_name is the class you're interested in. Pick the result that links to java.sun.com. (On Google you can use site:java.sun.com in the query and it will only return hits on that site. It's usually unnecessary though since the Sun site usually comes up in the first page.) It should take you to the JavaDoc page for that class. If what you really want is sample code, just add to the query.
14 years ago