Overview

OAM installation follows the standard Fusion Middleware installation pattern, which is:

  • Create database objects by running the RCU
  • Install the binaries
  • Configure WebLogic domain
  • Configure product

While most products follow this template, each will have it’s own slight variations. For example, OAM does not have a product configuration, so the last step is not needed when installing just OAM and there are a few scripts that need to be executed.

Once you’ve done a few of these installs, you can probably fly through each actual step, but having an outline of the process always helps me, especially as different versions sometimes differ as well. The list on the right will provide the highlights.

Installation

There are tons of installation guides out on the internet that will give you a nice screenshots at each step of the process, so I’m not going to redo what’s already out there. Instead, I want to focus on understanding the installation process and in the next section, provide some ready-to-go commands.

RCU

The Repository Creation Utility, aka RCU, is used to create the database objects (schemas, table spaces, tables, etc…) that will be used by the products. The RCU allows you to create or delete these objects and also prefix them with a name, “DEV_” being the default.

The prefix is used purely to separate multiple instances of a schema. For example, if you are using one database for Development and Test environments for OAM, you would separate them with the prefixes, so DEV_OAM and TEST_OAM could co-exist without conflict.

OID will not allow you to set a prefix because you can only have one OID schema per database

Always pay attention to the prefix if you come back to add another product later. If you create an OAM schema under DEV_OAM, and later re-run the RCU to add OIM, the installer will default the prefix to “DEV1”. If you’re not careful you can miss the option to select an existing prefix at the top.

Installers (WebLogic and OAM)

The WebLogic server installation is very straightforward. When you install, make sure you pass the “-d64” parameter to the installer if you are on a 64bit machine:

java -jar -d64 wls1036_generic.jar

This installer simply puts the WebLogic binaries in your MiddleWare home ($MW_HOME). You will not have any WebLogic components that you can run after this (excluding Nodemanager). If you’re looking for the AdminServer, you won’t find it; that comes after you create the WebLogic domain. The same thing is true for the OAM Installer. It simply extracts the files needed by OAM to function into your MiddleWare home directory. Nothing is functional or executable at this point.

Domain Configuration

This is where you can either Create or Extend a WebLogic domain. When you create a WebLogic domain, it will have the following affect:

  • You will see a “user_projects” folder in your MiddleWare home. In here, you will will have a /domains/[YOUR DOMAIN NAME] folder. This is called the Domain Home ($DOMAIN_HOME)
  • There will be a managed server called “AdminServer”
  • There will be a managed server called “oam_server1” (if you are installing just OAM)

Whether you are creating a new domain or extending an existing one, you will be prompted to select what components the domain will support (for example OAM). Whatever you select here, the tool will add the necessary managed servers, deployments or libraries to the domain to make the applications you are selecting functional. In the case of OAM, it creates a managed server called oam_server1, deploys the OAM server application to this new managed server. It also deploys the OAMConsole application to the AdminServer, which makes it available on http://host:7001/oamconsole.

If you select a component that requires a database, you will be prompted to specify where that database is. This is where you would point it to schemas that were created by the RCU. This creates jndi data sources in WebLogic, which the components can use.

There’s a lot of other options you can configure during Domain creation, such as clustering, deployment targets, etc… but I may cover those in another post.

Quick Commands

Run RCU in Silent Mode (OAM Only)

./rcu -silent -createRepository -connectString localhost:1521:ORCL -dbUser sys -dbRole sysdba -schemaPrefix DEV -component MDS  -component IAU -component OPSS -component OAM

Configure Domain

$MW_HOME/oracle_common/common/bin/config.sh

Configure Database Security Store

$MW_HOME/oracle_common/common/bin/wlst.sh $ORACLE_HOME/common/tools/configureSecurityStore.py -d $DOMAIN_HOME -c IAM -p %OPSS_SCHEMA_PWD% -m create

Upgrade OPSS Schema using Patch Set Assistant

$MW_HOME/oracle_common/bin/psa

High Level Steps

  • Install Java
  • RCU
  • Install WebLogic
  • Run OAM Installer
  • Config WL Domain
  • Upgrade OPSS
  • Configure DB Security Store
  • Install Java
  • RCU
  • Install WebLogic
  • Run OAM Installer
  • Config WL Domain
  • Configure DB Security Store
  • Install Java
  • RCU
  • Install WebLogic
  • Run OAM Installer
  • Config WL Domain