Ready or not, here comes another installment in my gripping series on how to create a WebCenter 11g R1 Patch Set 1 VM.
In the last part, I went over the last few steps of the 11g install. This part focuses on WebLogic, which is the preferred application server for WebCenter. I don’t know if it works on other apps servers, and I’m not about to experiment, at least not now.
First, I downloaded the latest version, WebLogic 10.3.2, which is part of the Fusion Middleware 11g R1 suite. It’s worth noting that the download is a network install, which is awesome for my purposes, but might not be for yours.
The download is a .bin file, and as previously noted, I am a n00b. So, I asked Google what to do with a .bin file and found a quick answer here.
I used the WebLogic installation guide, which oddly shows screenshots of a Windows install. Maybe that’s not odd, but I thought so.
The rest of the process is pretty straightforward, simply walking through wizards, which I’ve partially documented here. Just find runInstaller and away you go:
Not much to see here.
I chose Custom here because I know I won’t be needing the Oracle Enterprise Pack for Eclipse. Because this is a VM, I want to keep it as small as possible.
Hmm, not sure about stuff like JDBC drivers, but you never know.
The option to install two JDKs seems a bit odd. After I finished the install process, I found an interesting note in the WebCenter installation documentation about which JDK to install and why:
Oracle recommends that you use the Sun SDK if you are installing in a development environment. Typically, this environment provides a more relaxed security configuration and enables you to auto-deploy applications. In a development environment, boot.properties is used for user names and passwords and polling is used for application deployment. If you are installing in a production environment, Oracle recommends that you use the Oracle JRockit SDK. Production environments are for applications running in their final form. Full security is enabled and applications may be clustered or use other advanced features. In this mode, user names and passwords are required and polling is not used for application deployment.
I installed both, just in case. The same information is included for each JDK in a later step in the Quickstart wizard.
W00t for net install, which even cleaned up after itself, very tidy.
Nice summary page right before the install begins.
Good old progress bar. Everything needs a progress bar. I heard at one point that some developers manipulate the percentages in progress bars to make them appear faster, e.g. ramping up to 90% in what actually represents a lower completion percentage.
Found that interesting. It makes good psychological sense, maybe I’ll dig into that at a later date. Anyway, back to the install.
And voila, installation complete, but still no balloons, although this was easier for me than 11g install because I didn’t bork it up along the way.
I decided to run the Quickstart, which sounded useful.
I wonder why only Windows users get “useful shortcuts”? Maybe the assumption is that Linux users don’t want shortcuts, probably correct.
And what is it with Windows and WebLogic? Maybe I mistakenly assumed it was more likely that apps servers were installed on Linux than on Windows. Hmm.
Anyway, here’s another wizard for your enjoyment.
Obviously, this is a new WebLogic domain.
I can’t find any reason why I would need the Advanced Web Services Extension. Hope not.
Name of the domain? Dunno, webcenter seems good. I hope I can change these settings later . . .
Ah yes, the good old admin user “weblogic”.
Now, the whole idea of multiple JDKs makes more sense. I’m not sure which one to choose, but production sounds fine, crossing fingers.
More configuration? I hope I don’t need it, at least not now.
Another nice summary of what I’ve chosen, along with some useful information I should write down, but didn’t because it’s preserved in this post . . .
And we’re done. I’m glad to be finished, but a bit worried all this software I’ve installed, i.e. 11g and WebLogic, still needs to be configured. Maybe I should have installed the 11g Enterprise Edition to get Enterprise Manager.
Oh well, I guess we’ll see. As far as I can tell, the next step is the WebCenter install, but if history is a guide, I’ll have some interim steps to complete first. Stay tuned for more.
If you’re wondering, the VM is now 23.7 GB.
Find the comments.
