3 Installing and Configuring JBoss Application Server for Oracle Identity Manager

This chapter explains how to set up JBoss Application Server before installing Oracle Identity Manager.

You must perform the following tasks described in this chapter:

Installing the Java JDK
Installing JBoss Application Server
Setting Memory Parameters

Note:

- See Chapter 9, "Deploying in a Clustered JBoss Application Server Configuration" for information about preparing to deploy Oracle Identity Manager in a JBoss Application Server cluster.

- JBoss Application Server clustered environments are not supported in Oracle Identity Manager release 9.1.0. See "Certified Components" in Oracle Identity Manager Release Notes for information about certified components

3.1 Installing the Java JDK

You must have a certified version of the Java JDK installed to deploy Oracle Identity Manager on JBoss Application Server. See Oracle Identity Manager Release Notes to learn the certified version of the Java JDK and then use the following steps to verify that the correct version of the Java JDK has been installed on the system:

Open a console window.

Enter java -version

The information that appears might look like the following:

C:\>java -version
java version "1.4.2_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)

3.2 Installing JBoss Application Server

Install JBoss Application Server on the computer on which you are going to install Oracle Identity Manager. See your JBoss Application Server documentation for detailed installation procedures.

Note:

You can obtain JBoss Application Server from: http://www.jboss.org

3.2.1 Setting Environment Variables

Perform the following procedures to set your environment variables:

For Microsoft Windows

To set environment variables on Microsoft windows:

From the Windows Start Menu, select Settings, select Control Panel, select System, select Advanced, then select Environment Variables.
In the System Variables list, select Path, then click Edit.

In the Variable Value field, add the location of your JDK to the beginning of the existing path. For example, if your existing path is the following:
```
%SystemRoot%\system32;%SystemRoot%;C:\Program Files;
```
Change it to the following:
```
c:\j2sdk1.4.2_15\bin;%SystemRoot%\system32;%SystemRoot%;C:\Program Files
```
Click OK to commit your change.
In the System Variables list, search for JAVA_HOME.

If JAVA_HOME does not exist, complete Step a. If JAVA_HOME exists, complete Step b.
1. Click New. In the Variable Name field, enter JAVA_HOME. In the Variable Value field, enter the path to the JDK. Click OK to commit your entries, then click OK twice more to close the Environment Variables and System Properties windows, respectively.
2. Click Edit. Verify that the path to the JDK exists in the Variable Value field. If it does not exist, enter the path in the Variable Value field. Click OK to commit your entry, then click OK twice more to close the Environment Variables and System Properties windows, respectively.
  
  For example: JAVA HOME=C:\j2sdk1.4.2_15
  
  Note:
  A window might appear displaying a message asking if you want to update the JDK. Close this window without updating the JDK.

For UNIX

To set environment variables on UNIX:

Set the JAVA HOME variable, for example:
```
export JAVA_HOME=/opt/j2sdk1.4.2_15
```
Export the path to the JAVA HOME variable, for example:
```
export PATH=$JAVA_HOME/bin:$PATH
```

3.3 Setting Memory Parameters

After installing JBoss Application Server, you must change the JVM memory settings for production environments or when you are processing large volumes in the nonproduction mode of the Oracle Identity Manager installation. The instructions for setting the memory parameters, which appear in the following sections, depend on whether the application server host is running on Microsoft Windows, or UNIX.

3.3.1 Setting Memory Allocation for Microsoft Windows

To set JBoss Application Server memory on a Microsoft Windows host:

Open the JBOSS_HOME\bin\run.bat file in a text editor.

Locate the line that contains the following:

set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m

Change the memory settings to the following values, which are recommended for production deployments:
```
set JAVA_OPTS=%JAVA_OPTS% -Xms1280m –Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m
```
Save and close the run.bat file.

3.3.2 Setting Memory Allocation for UNIX

To set the memory allocation for JBoss Application Server on UNIX:

Open the JBOSS_HOME/bin/run.conf file in a text editor.

Locate the following line:

JAVA_OPTS="-server -Xms128m -Xmx 128m"

Change the memory settings to the following values, which are recommended for production deployments:
```
JAVA_OPTS="-server -Xms1280m –Xmx1280m -XX:PermSize=128m -XX:MaxPermSize=256m"
```
Save and close the run.conf file.

3.4 Configuring JBoss Application Server

This section describes how to configure JBoss Application Server. It contains these topics:

Removing JBoss Application Server Components
Removing Files and Directories

3.4.1 Removing JBoss Application Server Components

For a JBoss Application Server installation, some JBoss components are not required by Oracle Identity Manager. These files vary for standalone and clustered installations.

You can remove the following components:

Cache invalidation service (keep for a clustered installation)
J2EE client deployer service
Integrated HAR deployer and Hibernate session Management services
JMX Console
Management console
Console/e-mail monitor alerts
UUID key Generation
JBoss scheduler manager
Scheduler service
Test queues and topics
Mail service
HTTP Invoker
CORBA/IIOP
AOP Application
Web services support

3.4.2 Removing Files and Directories

The following sections list the files and directories that you can remove after installing Oracle Identity Manager.

3.4.2.1 Non-Clustered Installations

Remove the following files from JBOSS_HOME/server/default/deploy/:

cache-invalidation-service.xml
client-deployer-service.xml
monitoring-service.xml
scheduler-service.xml
schedule-manager-service.xml
mail-service.xml
uuid-key-generator.sar

Remove the following directories from JBOSS_HOME/server/default/deploy/:

jboss-hibernate.deployer

Note:
Remove this directory only if it exists.
jmx-console.war
management
http-invoker.sar
jboss-aop.deployer
jboss-ws4ee.sar

Remove the following file:

JBOSS_HOME/server/default/deploy/jms/jbossmq-destinations-service.xml.

Open the JBOSS_HOME/server/default/conf/jboss-service.xml file and remove the following attribute:

<attribute name'"RMI_IIOPService">jboss:service=CorbaORB</attribute>

3.4.2.2 Clustered Installations

Remove the following files from JBOSS_HOME/server/all/deploy/:

client-deployer-service.xml
monitoring-service.xml
scheduler-service.xml
schedule-manager-service.xml
httpha-invoker.sar
mail-service.xml
jboss-aop.deployer
jboss-ws4ee.sar

Remove the following directories from the JBOSS_HOME/server/all/deploy/:

jboss-hibernate.deployer
jmx-console.war
management
uuid-key-generator.sar

Remove the following file:

JBOSS_HOME/server/all/deploy-hasingleton/jms/jbossmq-destinations-service.xml

Open the JBOSS_HOME/server/all/conf/jboss-service.xml file and remove the following attribute:

<attribute name'"RMI_IIOPService">jboss:service=CorbaORB</attribute>