Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Apart from the BEA docs?


locked by HopelessN00b Dec 5 '14 at 11:41

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off topic by Bart De Vos, mdpc, voretaq7 Feb 15 '12 at 23:56

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

I'm not sure what we can help you with here -- The question you're asking is incredibly broad, and also a "learning materials recommendation" which is generally off-topic for StackExchange sites. I would suggest starting with the BEA docs, and then if you have specific questions about implementation definitely come back and ask them. – voretaq7 Feb 15 '12 at 23:56
up vote 3 down vote accepted

This one is very easy to answer.

Sam Alapti's Oracle WebLogic Server 11g Administration Handbook is the most detailed and up to date Weblogic book.


Moby-Disk. Brillant work.

Maybe you could narrow it down just a bit? Java book? Administration book?

That was supposed to be Moby-Dick but maybe I like Moby-Disk better. – Charlie Martin May 25 '09 at 19:30
I like "Moby-Disk" better. I'll give it +1 for that. – Curt Sampson May 25 '09 at 19:31
I may have to write Moby-Disk..... – Charlie Martin May 25 '09 at 19:43
@Charlie Martin Dint I mention for sysads? – Sharjeel Aug 19 '09 at 12:21

Err...How to Win Friends and Influence People? :-)

Honestly, a lot of this Enterprise Java stuff appears to have been designed to be extremely configurable by sysadmins so that the developer can pass off the blame for not getting it right to some guy "production engineer" whom they claim should have edited the XML files correctly. (I speak as a long-time developer and longer-time sysadmin; let's just say that these days all my developers are responsible for making sure that their sh*t gets rolled out correctly, and survives in production.)

So this is not exactly the answer you were looking for, in terms of listing books, but get to know your developers and your customers very well. Drinking together well. It will save you boatloads of misery.

And then, well, The Java Programming Language is a good start. If you can do sysadmin, there's a pretty decent chance you can learn to program. And you'll turn in to a boon to all the rest of the sysadmins out there, in that you'll actually be thinking about not just how to get some application passing tests, but also how to get it deployable with only reasonable effort.


Unfortunately, there's no good recent books for WebLogic administration. The Bea/Oracle J2EE admin space in general suffers from a dearth of good technical books aimed at administrators.

The admin docs for WebLogic server are pretty good, but they assume a working knowledge of J2EE.

To supplement the docs, If you're just getting started with J2EE administration, be sure to familiarize yourself with the core technologies of J2EE. JMS,JDBC, etc.

This doc is aimed at devs, but you can get a lot out of it as an admin. You'll find the J2EE world in general is highly developer centric. You really can't be a good J2EE admin without learning at least a tiny bit of Java.

As an admin, it is critical that you have a good understanding of the Java package structure. Unless you have the pleasure of working with a better than average team, the devs will give you broken packages to deploy.

When you tell them the package is broken, they will blame "your configuration". After all, it "works on my box" You will have to open up the j/e/war and diagnose the problem yourself. About half the time, the deployment descriptor will have some problem. The other half of the time, libraries will be missing from the package, or the package will contain versions of opensource libraries that conflict with the version WebLogic uses. Occasionally, the problem will actually be "your configuration"

You should know ant backwards and forwards. The O'Reilly Ant book is good.

WLST is vital. You'll get more out of it if you know some Python.


Not the answer you're looking for? Browse other questions tagged or ask your own question.