Interacting with my development environment

Question

The basics of Java programming I understand. I've created the first phase of a large intranet app using JSPs, EJBs, etc. But now I need to create an automated daemon to spit out large batches of Excel files, the data for which is (or will be) stored in an Oracle database.
I've gotten to the point where I've discovered Apache Jakarta POI, an API which would probably help meet my objectives.
The problem: I don't know where to begin importing these jar files into my environment. Mostly because it isn't MY environment. I sit at my computer and go through the company network to reach the development box, which is running JRun. I have absolutely no understanding of where to put files, what files these files are, and what changes I need to make to be able to import whatever classes/packages I will end up needing.
Furthermore, there is no particular person at my company who can answer these questions for me, at least not w/out submitting a formal request for help, waiting until their next project meeting, and then another three+ weeks to get assigned to a web developer downstairs. This project is "due" in about a week and a half.
Can someone recommend a tutorial, book, alternate message board, ANYTHING to get me started -- preferably in plain English because I tend to zone out when reading long technical descriptions with excessive acronyms (I was a terrible student...)

Answer 1

I would suggest two things
1 - get along with developing it locally, and worry about deploying it later
2 - shake a tree further up and say if they want it next week, then you will need some answers this week. Document your questions in an email/formal request, and leave it to someone else
I need to create an automated daemon to spit out large batches of Excel files, How is this daemon being executed?
What are you using for scheduling?
Is it running on the JRun server?
How do you trigger its startup/shutdown?
This will affect how the classpath is defined. If it is deployed inside JRUN, there is one definition of classpath, if it is independant, then you can have another.
If you are executing the daemon process from a command line/batch file evoking "java", then you have full control over the classpath settings, and can include any jars you want.
Adding libraries to the JRUN (as with any J2EE server) is relatively easy
- drop the jar files into the WEB-INF/lib directory of your web app.
- restart the server.
Hope this helps some,
evnafets