|After extraction the welcome screen appears|
Click on Next.
|Enter the base directory used as "Middleware Home".|
Click on Next
|Because the Oracle Enterprise Manager 11g is tightly linked to Oracle Support site, we select to enter credentials here.|
Click in Next
|Confirm the selected Java installation to use for weblogic.|
It should state the installation directory copied above in section 2.1.
Click on Next
|The installer now shows the installation homes of the two weblogic parts:|
Weblogic server and Oracle Coherence.
Leave the given directories as is and click on Next.
|After confirming the installation summary, the installation progress screen is displayed.|
After the intallation completes, unselect "Quick Start" and press Done.
Patching WebLogic Server
Before the patching of the Weblogic server can be started, make sure you have:
- Access to the Internet from the server you are installing
- Added the following hosts to /etc/hosts
Start the patch installer, using:
$ bsu.sh -log=/tmp/bsu.log
The file /tmp/bsu.log can be optionally used for detailed logging of the actions the program takes.
It is possible that the installer first is going to update itself. You will be prompted for that.
In the below table the update walkthrough is displayed:
|Afterwards it downloads the available Weblogic updates will be downloaded.|
First you need to enter the credentials to access Oracle Support like shown in the figure.
|After supplying the login credentials and having verified them the update installer appears.|
Again the login credentials for Oracle Support are asked, as shown here.
We choose here to not enter the credentials, as:
• We don't need any Emails about updates
• There seems to be some kind of problem with the connection. It keeps returning asking for the credentials.
In the "Get Patches" Tab the Weblogic patch "WDJ7" is shown.
Select that patch and click download.
After a couple of seconds the download finishes and the patch dissappears from the screen.
|Select the tab "Manage Patches".|
In the lower part of the screen the downloaded patch "WDJ7" is shown.
Select the patch and click the "Apply" button.
|The installer checks for any conflicts. If correct, no conflicts should be found.|
Click OK to start the update
|After the patch is installed it will appear in the upper part of the screen. This concludes the patch installations.|
Select File, Exit to leave the patch installer.
|In the first screen you're able to enter you 'My Oracle Support' Credentials. It is recommended to do so, enabling the installer to check and download available updates.|
Possible screen if Check for "Download and install updates" is selected
Select Installation Type:
Select "Install a new Enterprise Manager System" as the server in this installation does not have an OEM installed.
The installer will list all failed prerequisite checks. If needed solve the given problem and confirm if the check runs OK afterwards
Enter the installation directory of the Oracle Enterprise manager installation and the 'Middleware Home' location ( the location where Weblogic is installed)
The installer determines the given entries and they are correct most of the time.
Weblogic Server Domain.
Since Oracle Enterprise Manager 11g runs on a Weblogic environment, a weblogic domain will be created.
Specify passwords for the given Weblogic user and Node manager.
Enter the database servername, Listener Port, SID and SYS password for access to the database created for this purpose.
Setup the Management repository.
Enter a password for the to be created SYSMAN user.
Confirm the file locations of the to be created tablespaces.
Enter passwords for the Management Agent registration.
Keep this password somewhere safe, as it is needed later when installing/configuring the clients
The port numbers to be used.
It is smart to keep a print of the screen, or write down the port numbers.
Although the manual states that 400Mb of temp space in /tmp is needed, the installer actually needs 936Mb (or more), as stated on the screen from which the installer started:
/tmp/ Required 936MB (only as temporary space) : Available 781MB
Increase space in /tmp and afterwards continue the installation by clicking 'Yes'.
Execution of allroot.sh script
After running a root-script for which a dialog box appears, the configuration of the product starts.
If the configuration of OMS fails ( step 5) and the logfile shows:
FINE: Cleaning the OMS from the repository
Sep 22, 2010 11:17:34 AM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterCleanup
FINE: Got the Host URL as: null
Sep 22, 2010 11:17:34 AM oracle.sysman.omsca.framework.OMSGenericAdapter postDeployAndReposSetup
SEVERE: OMSCA-ERR:Securing of OMS failed. Check the trace file:/opt/oemprd/ora/middleware/weblogic/oms11g/cfgtoollogs/omsca/omsca_20
Sep 22, 2010 11:17:34 AM oracle.sysman.omsca.framework.OMSCAFreshInstall execute
SEVERE: Securing of OMS failed.
Sep 22, 2010 11:17:34 AM oracle.sysman.omsca.framework.OMSConfigAssistantDriver main
FINE: Got resultfalse
then the an unsupported version of WebLogic is installed .
Only version 10.3.2 is supported for Oracle Enterprise Manager 11g ( see Note: 1096766.1)
If the configuration fails at Add-on OMS side configuration, a manual fix needs to be applied to addonca.pl, as described here: http://arjunraja.wordpress.com/
This page says:
While installing Oracle 11g on AIX you could hit this failure
Do not CANCEL or EXIT the installation from the GUI mode.
A check of the logfile reveals this error -
11g Grid Control installation fails at ‘ Add-on OMS Side Configuration ‘ with following error message in
Caused by: java.lang.RuntimeException: Can’t recognise platform – Unix
The following file needs to be backed up and edited as follows
Go to the newly installed Oracle Management server HOME/bin folder -
cp addonca.pl addonca.pl.org
Edit the file -
Look for Unix under osname and change it to AIX -
$osname = “Unix” ;
$osname = “AIX” ;
Click on RETRY and the installation completes.