11g Fusion Middleware Install Walkthrough – Part 4 Portal and SOA Install

Part 4 describes the process to install and configure Portal and SOA on the application tier of the Fusion Middleware Environment.

Overview of the Installation Steps

1. Install Sun JDK
2. Install WebLogic Server
3. Install Portal
4. Install SOA

Step 1 and Step 2

This is identical to the procedure in Part 2. The Sun JDK and WebLogic server was installed as part of Identity Management on the database tier. Repeat these steps for the Application Tier.

Step 3 – Installing Portal

We created the repository for Portal back in Part 2 so we wouldn’t have to run the repository creation utility multiple times. Unzip the Portal installation media and launch the runInstaller:



Click on the Next button.



As with Identity Management, we are going to Install and Configure the Portal environment, so verify that its selected and click on the Next button.



If you are followed the steps from Part 1 and are using the same versions then the pre-requisite check should be ok. If there are issues here fix them before you proceed. Once everything is ok click on the Next button.





Select a username to administer the domain, a password and the domain name. Click Next when your finished entering this information.



If you would like Oracle Configuration Manager to be installed then enter your metalink email address and password. Click on Next to continue.



Unfortunately this is a bad screenshot as its not showing the end of the Instance Location field. Since we are install Portal and SOA on this tier I want the directory names to be representative. So the Oracle Home directory is preceded with PORTAL, as is the instance location and name. The Middleware Home Location is where you installed the WebLogic Server earlier. Click on Next when your finished.




If your not planning on using all of the components then de-select then ones not required. Here everything is being installed except for Discoverer. Click on Next when ready.



Since this is the first WebLogic domain on this server we can use the Auto Port Configuration option. However, during the SOA install we’ll need to do this differently. I’ll go into detail why at that point. Click on Next.



Click on the Next button.



Enter the connection details for the database and repository created in Step 2. When finished click on the Next button.



Enter the schema name and password for the PORTLET account created as part of the repository install in Step 2. Click on Next when finished.



Enter the details for Oracle Internet Directory created in Part 2. Be sure to use the SSL port. Click on Next when finished.



Save a copy of the response file. It may come in handy if need to reinstall or when creating a new environment. Click on Install when ready.



Once the install has finished it will ask you to run the oracleRoot.sh script:



Once you have executed the script as root click OK.




Save a copy of the Installation Summary, it will contain useful information such as where the location of various components on disk, URL’s and port numbers. Click on Finish when complete.

Step 4 – Installing SOA

Unzip the SOA media and change directory to Disk1. Before you start set your JAVA_HOME environment variable and launch the runInstaller with the –jreLoc parameter:

[oracle@vm7 Disk1]$ JAVA_HOME=/u01/app/oracle/product/jdk1.6.0_16; export JAVA_HOME

[oracle@vm7 Disk1]$ ./runInstaller -jreLoc $JAVA_HOME

Click on the Next button.




If you are followed the steps from Part 1 and are using the same versions then the pre-requisite check should be ok. If there are issues here fix them before you proceed. Once everything is ok click on the Next button.




Enter the Middleware Home directory, which is the same as the other products installed, and specify a directory name where SOA will be installed. Click on Next when ready.



As with the other products installed, save the response file in case you need to reinstall or setup a new environment. Click on Install when ready.



The installation details file contains some useful information so be sure to save a copy. Click on the Finish button.

Configuration

To configure SOA launch the configuration wizard:

/u01/app/oracle/product/mid11g/SOAHome_1/common/bin
[oracle@vm7 bin]$ ./config.sh



Each component of the Fusion Middleware stack has to be installed in its own domain. So at the end of this installation we’ll have 3 domains over two tiers. An Identity Management domain on the database tier and a Portal Domain and SOA domain on the application tier.

Verify Create a new WebLogic domain is selected and click on the Next button.



On this screen select only the SOA components which are easy to distinguish by the [SOAHome_1] at the end of each option. Click on Next once they have been selected.



Enter the domain information and click on Next.



Specify a username and password to administer this domain.



Select the appropriate startup mode depending on this is a DEV or PROD environment and click on the Next button.



Enter the connection details for the database created in Part 2. If you used the same password for all schemas then enter it in the Schema Password textbox at the top of the screen. If you created the repository with a different password for each schema then you will have to enter each on in the last column of the table. Click on the Next button once your finished.



The configuration utility quickly tests to see if it can connect to each of the schemas. If there are problems here verify the database connection information and passwords you entered are correct. Click on the Next button to continue.



We need to perform some addition configuration steps on this domain so check the first two options Administration Server and Managed Servers, Clusters and Machines and click on the Next button.



Back in Part 1 I listed a known issue where ports are not checke across multiple Oracle Home directories. If you blindly go through the install then the AdminServer for the SOA domain will use port 7001. This port is already in use by the Portal domain. We need to change the port on this screen so there is no conflict. To keep it simple I added 10 to the original port value to et 7011. Click on Next to continue.



As with the AdminServer, the default port for the bam managed server is being used WLS_PORTAL. To keep it consistent I changed both the bam and soa server by adding 10 to the original value to get 9011 and 8011 respectively. Once finished click on the Next button.



Click on Next.



Click on Next.



Click on the Next button.



Review the summary and click on the Create button.




Once the install completes click on the Done button.

If you have gotten this far you will have successfully installed Fusion Middleware 11g.

Fusion Middleware – PermGen memory issues

The other day a developer called me to say that the Fusion Middleware console was spinning.   A quick look at the the environment showed a java process consuming 100% of a cpu and in the AdminServer weblogic log there was the following error:

java.lang.OutOfMemoryError: PermGen space

To get the environment going again I had to kill the java process and restart the AdminServer.    I increased the amount of PermGen memory and so far it hasn’t happened again. 

To change the PermGen memory login to the WebLogic Administration Console:


After you login click on Lock & Edit, so you can make changes. Followed by Environment -> Servers under the Domain Structures widget. The right hand side of the screen will update. Click on the AdminServer(admin) link in the table:

Verify that the Configuration tab is selected and click on Server Start:

Scroll down until you see an Arguments text box and update the PermSize and MaxPermSize to the new values. In my example below I have already modified them to be twice their original value:

Once you have made the changes scroll back up to the top of the page and click on the Save button:

Click on the Activate Changes button:

As you can see below, the changes were saved successfully and it says no restarts are necessary. Since we updated the startup parameters tho, they will not come into affect until you perform a restart.

If you want to check out your changes on the server side, login to the server hosting your Portal domain. Change directory to your $PORTAL_DOMAIN/config directory and view the config.xml file. A backup of the config.xml file can be found at $PORTAL_DOMAIN/servers/domain_bak/config_prev/config.xml

From within the WebLogic console, the monitoring capabilities seem to be rather limited.

For example:
From the Fusion Middleware control console I see:

And from the WebLogic Administration Console (Server-> Monitoring -> Performance tab) I can see:

Now, I am very new to WebLogic, so there may be other areas to see more detailed information or a way to start recording it. I have it on my list to investigate further.

If you have Grid Control and the WebLogic management pack there are lots of performance metrics you can view and drill down into.

Lets say you don’t have Oracle Grid Control and would like to confirm the PermGen changes we made above or take a closer took at performance. There are a number of tools available and one of them, VisualVM is packaged with the Sun JDK.

To launch VisualVM go to your JDK_HOME/bin directory and launch jvisualvm. The first time you launch this tool there is a calibration that needs to occur.


When it finishes you’ll be presented with some statistics. After you click OK and the application starts you will see a screen similar to:

The tool automatically discovers the java processes. If you don’t see any here, or not as many as you expect there could be a number of reasons. From the VisualVM documentation:

The circumstances in which VisualVM will not automatically discover JMX agents, and thus the Java applications they expose, are the following:

• The target application is running on the J2SE 5.0 platform and the  -Dcom.sun.management.jmxremote* properties have not  been specified.
• The target application is running on the same host as VisualVM but was started by a different user than the one who started VisualVM. VisualVM discovers running applications using the jps tool, which can only discover Java applications started by  the same user as the one who starts the VisualVM tool.
• The target application is running on a remote host where jstatd is not running or is running but was started by a different user. The jstatd daemon provides an interface that allows remote monitoring applications to connect to Java applications on the host where it is running.

As you can see in my screenshot above, it automatically discovered quite a few WebLogic servers. I ran VisualVM on my application tier which contains Portal and SOA. As you can see next to each entry there is a process id. You can either double click on each one until you find the one your looking for, or say your looking for the Portal AdminServer you can grab it from your server. This screenshot is going to be a bit cluttered but basically i’m executing ps –ef, grepping for AdminServer and looking for a couple of key things in the output. The process id, that the process is for an AdminServer and the domain.


If I go back to VisualVM, find process id 32508 in the list and double click on it I see:

Take a look at the red circle. Wait?! It still says that the PermSize is 128 and MaxPermSize is 256m.

It turns out that the procedure I used above to change the PermSize settings, which modifies the config.xml file will only work if you are using a Node Manager to start the servers.

If you are using the startWebLogic.sh and startManagedWebLogic.sh scripts to start up the AdminServer and managed servers respectively, then you will need to modify those scripts.

Since I am modifying the Java parameters for the AdminServer the script we need to modify is startWebLogic.sh. However, startWebLogic.sh calls a script called setDomainEnv.sh. This script initializes a number of variables, but the one we are looking for is EXTRA_JAVA_PROPERTIES.
This parameter will be modified multiple times, so it can be confusing as to which one to modify. Here is a clip:

----[clip]----
EXTRA_JAVA_PROPERTIES=" -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m -Doracle.home=/u01/app/oracle/product/mid11g/PORTALas_1 -Ddomain.home=/u01/app/oracle/product/mid11g/user_projects/domains/PortalDomain ${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES

if [ "${SERVER_NAME}" = "WLS_REPORTS" ] ; then
EXTRA_JAVA_PROPERTIES="-Xms256m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m -Djava.library.path=/tmp/
---[clip]----

The parameter we want to modify is the first one. The second one is actually Java parameters for the Reports manager server. Further down in the file you will see sections for the other managed servers in the Portal environment, such as Forms and Portal. Modify the first EXTRA_JAVA_PROPERTIES PermSize settings:

EXTRA_JAVA_PROPERTIES=" -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m -Doracle.home=/u01/app/oracle/product/mid11g/PORTALas_1 -Ddomain.home=/u01/app/oracle/product/mid11g/user_projects/domains/PortalDomain ${EXTRA_JAVA_PROPERTIES}"

After a restart of the AdminServer and viewing the java process in VisualVM we see:


We have now confirmed the changes have been made successfully. If you notice 9 lines above my circle there is another MaxPermSize entry. I believe that one is being captured by the variable:

MEM_MAX_PERM_SIZE_32BIT="-XX:MaxPermSize=512m"
export MEM_MAX_PERM_SIZE_32BIT

I am not sure what happens in a case where a parameter is specified twice with different values. Does the second one override the first? Is it the one with the maximum value? I’ll tell you what I think in a second.
If you click on the Monitor tab->PermGen you will see the following:


This screen provides you with more information about the state of the java process such as the PermGen memory area. As you can see the size is around 256M and currently the WebLogic process is only using around 175M.

To test what happens when a parameter is specified twice, I put another –XXPermSize before the one in the JAVA_EXTRA_OPTIONS variable and tried a few test scenarios. I set the first to 128m and the second to 256m. When I looked at the PermGen memory in VisualVM the size was around 256. Then I swapped the parameters and restarted the server again. This time the PermGen size was 128m (the value of the second parameter). So it looks like if a parameter is specified twice the last occurrence is used.

11g Fusion Middleware Install Walkthrough – Part 3 Single Sign On

Part 3 describes the process to install and setup SSO on the application tier of my Fusion Middleware Environment. I had originally intended to talk about Portal and SOA here but I didn’t realize how long the SSO portion was.

Oracle Single Sign-On and Oracle Delegated Administration Services Release 10g are required components for Oracle Portal, Forms, Reports and Discoverer Release 10g and Release 11g.

Overview of the Installation Steps

1. Executing inspre11.pl
2. SSO Repository Creation
3. Install SSO 10.1.4.0.1 and upgrade it to 10.1.4.3

Executing inspre11.pl and SSO Repository Creation

More detail for the steps below can be found in Oracle’s documentation.

execute inspre11.pl with –op1. The –op1 flag will enable anonymous bind, disable entry cache and change the OID version from 11.1.1.1.0 to 10.1.4.0.1 so the SSO repository creation assistant will be able to load the schema.

On the database tier set your ORACLE_HOME environment variable to your IDM installation, and ORACLE_INSTANCE to the instance home location. Execute inspre11.pl with the –op1 parameter.
The syntax for inspre11.pl is:

$OID11gR1_ORACLE_HOME/perl/bin/perl \
$OID11gR1_ORACLE_HOME/ldap/bin/inspre11.pl OID_HOST OID_PORT {-ssl | -nonssl} \
OID_COMPONENT DB_CONNECT_STRING ODS_PASSWORD ORCLADMIN_PASSWORD \
{-op1 | -op2 | -op3}

In part 2, I used the same password for all of the accounts, so ODS_PASSWORD and ORCLADMIN_PASSWORD is the same. That’s why you will see password specified twice in my example below:

[oracle@vm2 Oracle_IDM1]$ ORACLE_HOME=/u01/app/oracle/product/mid11g/Oracle_IDM1; export ORACLE_HOME

[oracle@vm2 Oracle_IDM1]$ ORACLE_INSTANCE=/u01/app/oracle/product/mid11g/IDMasinst_1; export ORACLE_INSTANCE

[oracle@vm2 Oracle_IDM1]$ $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/ldap/bin/inspre11.pl vm2 3060 -nonssl oid1 vm2:1521:FMWD password password –op1

Use RepCA to load SSO and other schemas against DB before running -op2


SSO Repository Creation

In part 2 we used a repository creation utility to load the IDM, Portal and SOA 11g schemas. Since SSO is a previous version (10g), we need to use a different repository creation utility (RCU). The 11g RCU is much nicer because it doesn’t need to be installed before you can use it. The 10g SSO RCU needs to be installed like other Oracle products before it can be installed.

The 10g SSO RCU is 32bit, so if your trying to install this on a 64bit environment, you have to type linux32 bash before you launch the runInstaller. Even tho I ran it from a 32bit shell I still encountered issues. Since you don’t need the 10g SSO RCU after you load the SSO schema I decided to install it on an old 32bit server instead of trying to figure out what was wrong.

Unzip the 10g SSO RCU archive and launch the runInstaller:



Click on the Next button.



Verify the inventory directory and change it to suit your environment. Then click on the Next button.



Make sure you execute the orainstRoot.sh script before clicking on the Continue button.

[root@appTier oraInventory]# ./orainstRoot.sh
Creating the Oracle inventory pointer file (/etc/oraInst.loc)
Changing groupname of /home/oracle/oraInventory to oinstall.

Change if necessary and click on the Next button.




I hit this warning, I can’t remember which kernel parameter was at issue but after I reviewed the problem I determined it was ok to proceed. The next time I install it, I’ll take better notes. Click on the Yes button.



If you need other languages select them and click on the Next button.



Verify that Yes is selected so that the RCU assistant launches automatically after the installation is finished and click on the Next button.


Click on the Install button.



The RCU assistant will automatically start and show the screen below:



Click on the Next button:



Enter the path of the Oracle Home directory for the database installed in Part 2. As well, select a log file directory and click on the Next button
.


We need to load the schema and register it, so verify that the Load and Register option is selected and click on the Next button:



Enter the information for the database created in Part 2.



It appears that the SSO Repca utility ignores the SGA_TARGET parameter and looks explicitly for the various SGA parmeters to make sure your database is sized correctly and setup correctly. As long as your SGA_TARGET is set high enough you can quickly login to your database, execute the commands below and continue with the RCU assistant.

SQL> alter system set aq_tm_processes =1;
SQL> alter system set db_cache_size=200M;
SQL> alter system set shared_pool_size=200M;
SQL> alter system set java_pool_size=120M;



Click on Yes, this requirement is only for 10g databases and we are not using 10g Portal.



I am using an regular file system so I selected the first option and clicked on the Next button.



Since I am on a SAN I am using the same directory for all tablespaces but if you are using multiple directories you will need to manually enter the information for each tablespace. Click on the Next button when complete.




By default the system tablespace datafile should be in autoextend in 11g but verify.




Enter the hostname for the server in which you installed Identity Management on in Part 2. By default the SSL port is 3131 but if you are unsure you can look at the installation summary file you should have saved back in Part 2.



Enter the password for orcladmin which you specified while installing Oracle Identity Management in Part 2.




I choose the default and clicked on Next.



Once the SSO repository has been loaded into your database you will be presented with the following screen. Click OK and your finished.



The 10g SSO RCU changes the ODS password for some reason so you need to change it back to the one you used back in Part 2.

Login to your database via SQL*Plus and change the ODS password using alter user ods identified by PASSWORD, where PASSWORD represents the ODS schema password before running the 10g SSO RCU Assistant.

SQL> alter user ods identified by password;
User altered

Login to the server in which Oracle Identity Management was installed and set the ORACLE_HOME, ORACLE_INSTANCE and TNS_ADMIN environment variables to reflect the IDM install and create a wallet:

[oracle@vm2 ~]$ ORACLE_HOME=/u01/app/oracle/product/mid11g/Oracle_IDM1; export ORACLE_HOME
[oracle@vm2 ~]$ ORACLE_INSTANCE=/u01/app/oracle/product/mid11g/IDMasinst_1; export ORACLE_INSTANCE
[oracle@vm2 ~]$ TNS_ADMIN=$ORACLE_INSTANCE/config; export TNS_ADMIN
[oracle@vm2 ~]$ cat $TNS_ADMIN/tnsnames.ora
OIDDB=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=vm2)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=FMWD)))
[oracle@vm2 ~]$ $ORACLE_HOME/ldap/bin/oidpasswd connect=OIDDB create_wallet=true
password:
confirm password:
Replication password file exists
password set

Restart Oracle Internet Directory:

[oracle@vm2 bin]$ cd $ORACLE_INSTANCE/bin
[oracle@vm2 bin]$ pwd
/u01/app/oracle/product/mid11g/IDMasinst_1/bin
[oracle@vm2 bin]$ ./opmnctl stopall;
opmnctl stopall: stopping opmn and all managed processes...
[oracle@vm2 bin]$ ./opmnctl startall;
opmnctl startall: starting opmn and all managed processes...

Execute the inspre11.pl script with -op2, which resets the Oracle Internet Directory version and allows you to install Oracle Single Sign-On and Oracle Delegated Administration Services Release 10g (10.1.4.0.1). The -op2 option will also verify the orcldirectoryversion attribute has a value of OID 10.1.4.0.1.

[oracle@vm2 bin]$ $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/ldap/bin/inspre11.pl vm2 3060 -nonssl oid1 OIDDB password password -op2

Install SSO/DAS against 11g OID before running -op3

Above when we executed inspre11.pl with the –op1 flag we used vm2:1521:FMWD for the database information. For some reason, with the –op2 flag, you will get an error. See the following note for details. Since we set the TNS_ADMIN environment variable above, we can pass the tnsnames.ora entry, which is OIDDB.

Subject: Inspre11.Pl Fails With Error Message No Such File Or Directory At Line 310   Doc ID: 876623.1

Install Oracle Single Sign-On and Oracle Delegated Administration Services Release 10g (10.1.4.0.1) and Upgrade to 10.1.4.3

On your application their unzip the SSO media and launch the runInstaller.



Click on the Next button:



Specify the directory for the SSO Oracle Home and click on the Next button.



Select Oracle Application Server Infrastructure 10g for the Single Sign-On (SSO) component and click on the Next button.



We already created the SSO repository, so select the second option Identity Management and click on the Next button.



If you haven’t already review Note 465847.1, it lists the required packages for OEL 5 and if you made the OS changes listed in Part 1 then you should be fine. So I ignored this error and continued.. I’m pretty sure it was looking for packages I have installed but of a lower release level. Click on Next to continue.



You’ll need to execute the root.sh script as part of this install. Click on the Next button to continue.



We are only using SSO and Delegated Administration Services, so I de-selected the other options and clicked on the Next button.


Click on the Next button.



Enter the hostname and port number for your IDM install from Part 2.



Enter the password for the orcladmin account which you specified during the IDM install in Part 2.



Create an Instance Name, I put SSO in front of the instance name to keep it logical. After you enter a password click on the Next button.



Click on the Install button.




During the install you may see this error. It can be safely ignored as per note: 465847.1




Before you click on the OK button above you should download and apply patch patch 5649850 before running run the root.sh script.

To apply this patch set your ORACLE_HOME environment variable to your SSO Oracle Home, unzip the patch, change into the patch directory and execute $ORACLE_HOME/OPatch/opatch apply.

If you get an error:

The Oracle Home /u01/app/oracle/product/mid11g/SSOHome_1 is not registered with the Central Inventory. OPatch was not able to get details of the home from the inventory.

Try upgrading Opatch to OPatch Version: 1.0.0.0.60

Once you have applied the patch click on the OK button.



Once the install has finished the configuration assistants will run. Assuming no issues are encountered you will be presented with the End of Installation screen below:



SSO has been installed but now we need to upgrade it to 10.1.4.3.0:

Upgrade SSO to 10.1.4.3.0

Upgrade Oracle Single Sign-On and Oracle Delegated Administration Services to Release 10g (10.1.4.3.0) by applying the Oracle Identity Management 10g (10.1.4.3.0) Patch Set. You can get the Oracle Identity Management 10g (10.1.4.3.0) Patch Set from My Oracle Support (formerly MetaLink) by searching for Bug or Patch Number 7215628.

Stop SSO:

If you don’t stop it beforehand I believe the installer will stop it for you.

echo "Stopping SSO Components. . ."
cd $SSO_HOME/bin
./emctl stop iasconsole
sleep 5
cd $SSO_HOME/opmn/bin
./opmnctl stopall

Download patch 7215628, unzip it and launch the runInstaller:



Click on Next.



Select the SSO Home from the drop down list and click on Next.




Enter your Metalink credentials if you would like configuration manager installed. I opted not to install it.


Enter the ias_admin password you specified during the SSO install above. Click on Next to continue.



Enter the orcladmin password from the IDM install performed in Part 2. Click on Next to continue.



Enter SYS password for the database created in Step 2.



I shutdown SSO before but if you didn’t, the installer will do that now. Click on OK to continue.



Click the on the Install button.



Once the install finishes you’ll be prompted to run the root.sh script. Perform that task and click on the OK button.




After the configuration assistants execute successfully the patch will be completed:



Click on Exit.

On the IDM server execute the inspre11.pl script with -op3, which sets the Oracle Internet Directory version back to 11g Release 1 (11.1.1).

Set the environment variables setup the IDM environment:

oracle@vm2 ~]$ ORACLE_HOME=/u01/app/oracle/product/mid11g/Oracle_IDM1; export ORACLE_HOME
[oracle@vm2 ~]$ ORACLE_INSTANCE=/u01/app/oracle/product/mid11g/IDMasinst_1; export ORACLE_INSTANCE
[oracle@vm2 ~]$ TNS_ADMIN=$ORACLE_INSTANCE/config; export TNS_ADMIN

[oracle@vm2 ~]$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/ldap/bin/inspre11.pl vm2 3060 -nonssl oid1 OIDDB password password –op3

Change orcldirectoryversion to 11.1.1.1.0 and enable entrycache

Verify the install was successful by logging in to Oracle Delegated Administration Services. You should be redirected to Oracle Single Sign-On and if your able to login in successfully everything should be installed correctly.

The URL where vm7 is the server name for the application tier:

http://vm7:7777/oiddas/

Part 4 will cover the Portal and SOA Installation.

11G Fusion Middleware Install Walkthrough – Part 2 Database + Oracle Identity Management

Part 2 describes the process to install and setup the database (including the repository) and Oracle Internet Directory.

If you are not installing the software directly on the server and in an X Window session you will need to export your display to one you have access to.  Or if installing from your PC, you can use software such as Hummingbird Exceed or Cygwin. If your not sure how to do this let me know.

Overview of the Installation Steps:


1. Download and install 11gR1 (11.1.0.6), patch it to 11.1.0.7
2. Launch netca to create a listener.
3. Launch dbca to create a database.
4. Create the Fusion Middleware Repository.
5. Install Sun JDK
6. Install Weblogic Server
7. Install Oracle Identity Management.

Steps 1,2,3.


Installing 11gR1, creating a listener and database is very easy, so I don’t think I need to post a step-by-step screenshot of how its done. If you have difficulty patching it to 11.1.0.7 feel free to ask me some questions.
However, there are some repository requirements you should be aware of:

· processes: 500
· open_cursors: 500
· session_cached_cursors: 100
· Database character set must be AL32UTF8

The only parameter that you really need to set while your creating the database is the character set. The others can be easily changed after the database has been created. During database creation you should see a screen with 4 tabs at the top, Memory, Sizing, Character Sets and Connection Mode. Click on the Character Sets tab and select use Unicode (AL32UTF8)





On the sizing tab you can modify the processes parameter. You can set the others by clicking on the All Initialization Parameters button.

Step 4 – Repository Creation


After you download the repository creation media and unzip it, you should have a directory named rcuHome. Change directory to rchHome/bin and execute ./rcu




Click on Next.




Select Create and click on the Next button.




Enter your database details for the database you created above and click on the Next button.



The only time I have seen errors here was if the database initialization parameters I listed early weren’t changed and if the database wasn’t created with the proper characterset (AL32UTF8).



The repository creation utility is used to create the schemas for many components, including Identity Management, Portal and SOA. There is no reason why they all can’t be created at this time. Later we’ll have to use another repository creation utility for SSO. Since this is a DEV environment I used the prefix DEV, which as you can see, will be prefixed to each schema.

When finished selecting the options click on the Next button.



Another pre-req check, I haven’t seen any problems here. Click on the OK button if everything looks good.



Since this is a DEV environment I really don’t see the need for multiple passwords, so I’m using the same password for all schemas. Click on the Next button when ready.



By default the utility is going to create a temp tablespace for each component. Since I’m on a SAN and it just appears to be one big disk, there is really no point in separating them. So I changed the all of the temp tablespaces to use the same one.

When finished slick on the Next button.



Click the OK button.



Self explanatory, click on the OK button.



Once you have reviewed everything above and it looks ok click on the Create button.




If all was successful the repository was created successfully and you should see the above screen.

Step 5 – Install the Sun JDK


There is not much to this step. Download the Sun JDK version 1.6.0_11+ from Sun. The file you download is a self contained archive, which you need to execute and accept the license agreement. Once you do that it will create a directory in the same folder and extract all of the files. Once that was done I moved the directory to /u01/app/product.

Step 6 – Weblogic Installation


Since I am installing on a 64 bit platform I downloaded the generic version of Weblogic. If your using a 64 bit platform, then all of the components need to be 64 bit. See an earlier post of mine for details.

Set JAVA_HOME to the location of the Sun JDK from step 5 and launch the installer:

[oracle@dbtier STAGE]$ JAVA_HOME=/u01/app/oracle/product/jdk1.6.0_16; export JAVA_HOME
[oracle@dbtier STAGE]$ $JAVA_HOME/bin/java –jar wls1031_generic.jar




Click on the Next button.



This is a new install so you will only have the option to Create a new Middleware Home. Select that option, enter a middleware home directory path and click on the Next button.



I’ll probably install configuration manager at a later date.. Definitely for production but this is only a DEV environment.



A typical installation is fine. Make sure its selected and click on the Next button.



If should automatically pick up on the JDK we installed earlier. Verify its selected and click on the Next button.



Accept the default here and click on Next.



This is just a summary of the components being installed. Click on the Next button.



De-select Quickstart. We’ll be creating a domain as part of the Identity Management installation. Click on the Done button
.
Step 7 – Oracle Identity Management Installation


Down load the IDM media and unzip the archives. Once finished change directory to Disk1 and execute the runInstaller:



Click on the Next button.



We’ll be installing and configuration IDM, so verify Install and Configure is selected and click on the Next button.



If any of the pre-reqs fail review the documentation and resolve the problems before continuing. Click on the Next button.



We are creating a new domain so verify the Create New Domain option is selected. Enter a username you would like to use to administer the domain and a password. The password has to be 8+ digits if I recall correctly.



I changed a few of the defaults on this screen such as Oracle Home Directory, Instance Location and Name. The primary reason is just to make the structure a bit more logical and so that if someone sees IDMasinst_1 they will know its for IDM. If left the default of asinst_1 its not as clear.

Click on the Next button when done.



We have no plans to using Identity Federation or Oracle Virtual Directory so I deselected those options.

Click on the Next button.



Unless you need to change the ports for some reason keep the default of Auto Port Configuration and click on the Next button
.


Enter the connection string for the database created in step 3 and enter the password used while creating the repository in step 4. When finished click on the Next button.



Enter a Realm and create a password for the orcladmin account which you will use to initially administer the realm. Click on the Next button.



Just a summary of the installation. Click on the Install button to proceed.



Once the install finishes the next window will popup.



Don’t forget to Login as root and execute this script before you proceed.



If any errors appear here, try to resolve the issue and click on the Retry button. Otherwise when the configuration is completed the next screen will appear.



It’s a good idea to save the installation summary as it will contain information about the install such as the domain name, ports, URL’s to the WebLogic and Enterprise Manager consoles, etc.

Once you click on the Finish button the installation is complete. The next parts in the series will show you how to install SSO, SOA and Portal.

11gR2 (11.2.0.1+) now certified with Fusion Middleware 11g

I just noticed that 11gR2 (11.2.0.1+) is now certified for use with Oracle Fusion Middleware 11g.   A few weeks ago I tried to install Fusion on a 11gR2 database but I encountered issues.  Since it wasn't certified I rolled back and installed 11gR1. 

The problem I had at the time was that the Single-Signon Repository Creation Utility errored out with , "The database does not contain Ultra Search Schemas WKSYS and or WKPROXY. Please install them and try again."

It appears Ultra search has been desupported in 11gR2: http://download.oracle.com/docs/cd/E11882_01/readmes.112/e11015/toc.htm#BABBFCCH

I just did a quick search on Metalink and looked at the release notes but I don't see any updates as to how to get around this problem.   If  you have installed FMW11g on 11gR2 and you found a solution or if you didn't hit this problem please leave a comment.