This post is the first in a series in which I will detail the steps needed to create an Oracle Documaker Enterprise Edition sandbox. This installation will be a "green field" install, which means that all the prerequisites will need to be located, installed, and configured. This includes the database, application server, and all ancillary components. The goal of this post series is to detail the steps required to get you up and running with a sandbox in as little time as possible.
Before we get started, a few housekeeping items. You should know that these instructions are presented for a Windows system that will use Oracle Database and Oracle WebLogic. These instructions should be considered as supplemental to the official product documentation, and the information herein is presented as-is, and I am not responsible should it not work for you, etc, etc, (more legalese here). So that said, let's get started!
If your goal is to have a sandbox, you're going to need a box! Almost quite literally - you'll need to acquire a machine, virtual or physical, and it needs to have a functional Windows operating system on it. You will need to have an appropriate amount of disk space as well. You can probably get by with 50GB, but you'll need to keep an eye on disk usage over time by pruning log files and trimming your database files. Go with as much space as you can get. A recommended system specification can be found in the ODEE 12.3 System Requirementsdocument. If you're installing all the sandbox components onto a single server be aware that you will need some stout hardware (Intel dual core i5 or i7) with at least 12GB of RAM, preferably 16GB.
Next you'll need to obtain the software. Oracle employees/partners have several options available; customers need to use MOS or eDelivery. Give yourself plenty of time to acquire the software, it's about 6.7 GB of stuff you'll need to download. The following items are required:
Once you've downloaded all this stuff, you'll need to stage it for installation. My recommendation is to create a directory for each component, and unzip the download files into the appropriate directories. This will keep everything organized and ready to install.
Next you need to do a little planning, but relax, it's not that hard. You're going to want to plan where everything will be installed, and we're going to refer to those directories with special names:
Now that we've established these defaults, let's review our installation process. We're going to do a very straight forward, all defaults installation in this order: database, application server, SOA components, and then ODEE. One final thing before we kick off the process - I recommend you follow these steps in order, however, if you're installing a multi-tier system you could do some of the components simultaneously, however, make sure you review all the steps before you embark in this fashion - you don't want to be half-way through the SOA Suite installation and find out that you need the database and application server components to continue! Also, make sure you execute all steps as an administrative user.
The first step if you haven't already done it, is to unzip the downloaded installation files into a single directory location. If you simply unzip both files into the current directory, you should have a single directory called database. Once extracted, navigate to the database directory and run setup.exe. Note: depending on your system's settings, you may need to approve the User Account Control dialog to continue.
Once the installer has initialized, you'll be faced with the option to sign up for critical update alerts. Normally this would be a good idea, however, for a sandbox system it's not a requirement. Uncheck the email options and click Next.
Click Yes because you really mean it!
On the following screen, select the "Create and Configure a Database option". If you're really into database creation, you could select the install only option, but really, you're on a fast-track right? We don't have the luxury of time for delving into the intricacies of Oracle database installation and configuration. That's another post.
On the next screen we need to determine the database class and that's Server class. This gives us access to options that aren't available in the desktop class so it's important to make the correct choice.
Choose the Single database instance. While RAC installs are supported, the installation and configuration of a RAC system is beyond the scope of this article.
While it would be nice to have a typical install, we must choose Advanced.
On the following screen, choose the language(s) you wish to install. This doesn't affect the system other than changing the languages that are present in the database web interfaces and tools.
Next we need to choose the appropriate database edition. We have several choices here, and I recommend using the top-most selection that your license can accommodate. The solution will work with any of the editions, however there are options such as compression and de-duplication that are supported only on the Enterprise or Standard edition. For our sandbox purposes, choose Enterprise.
Now we need to key in the location of ORACLE_HOME that we defined earlier. As you type, you'll see the value for the product location change accordingly. You can change the product location, but I would advise to leave it where it is by default.
Select the General Purpose database, and we'll be on our way.
Next, we need to name our database that we're going to create. You should provide a global database name as well as a SID (service identifier). In my example below, I've used idmaker.us.oracle.com as the global database name and IDMAKER as the SID.
We need to specify a few settings here. You can change the memory allocations as necessary but for sandbox purposes I'll be leaving my settings to be automatically managed. The important setting is on the Character Sets tab. You'll need to set the database to use the Unicode character set (AL32UTF8). This is very important, so double-check that you've set this appropriately before continuing.
We're going to use the Database Control for management. If your environment has other options (e.g. Grid Control) you can use that, or you can set up email notifications if you like but for the sandbox we won't enable either of those.
Our sandbox will use the standard File System for storing database files. Note the message about separating database files and software - you can do this if your system allows for this configuration.
If your sandbox will ultimately be used for a development system you might consider enabling automated backups, however, you can do this at a later time as well. For now we'll skip it.
For my sandbox system I will use the same password for all my database administration accounts. If your IT policies have greater restrictions you can choose a different option to suit your needs.
Finally, we have finished most of the pre-configuration work! If you think you might do this installation several more times, you may consider saving the response file. It's also a good idea if you want to keep a record of the settings you used when configuring the system. Once you're ready to conduct the installation, click Finish.
Now is a great time to get a coffee, catch up on email, read a book, or take a walk outside.
Once the files have been created on the file system, the database will be created. Go ahead and finish your coffee/email/book/walk.
Finally, we are complete! Take a look at your summary screen and take note of your database control URL - you'll want to know this for later use, so store this URL in your favorites.
This concludes Part 1 of our sandbox installation. We'll continue the next segment with installing WebLogic!