32
Chapter 3. JOnAS Configuration
driver installed. (Oracle JDBC drivers can be downloaded from Oracle’s web site:
http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html)
For example:
sqlplus
user/passwd
SQL
@Account.sql
SQL
quit
The JDBC driver classes must be accessible from the classpath. To do this, update the
config_env
file
$JONAS_ROOT/bin/unix/config_env
.
3.5.7.2. Configuring Other Databases
The same type of process can be used for other databases. A template of datasource for PostgreSQL
and for InterBase is supplied with JOnAS. Although many other databases are currently used by the
JOnAS users (for example, Informix, Sybase, SQL Server), not all JDBC drivers have been tested
against JOnAS.
3.5.8. Configuring the Security Service
The
Security service
is used by the
Container service
to provide security for EJB components. The
Container service
provides security in two forms: declarative security and programmatic secu-
rity. The Security service uses
security roles
and
method permissions
located in the EJB deployment
descriptor.
Note that:
•
JOnAS relies on Tomcat (http://jakarta.apache.org/tomcat) for the identification of the web clients.
The Java clients use the JAAS login modules for the identification. JOnAS performs the user au-
thentication.
In the
$JONAS_ROOT/conf/jonas-realm.xml
file you can define three types of Realm for
JOnAS:
•
Memory realm: users, groups, and roles are written in the file in the section
jonas-memoryrealm
of the
$JONAS_ROOT/conf/jonas-realm.xml
file.
•
Datasource realm: users, groups, and roles information is stored in a database; the configura-
tion for accessing a specific datasource is described in the section
jonas-dsrealm
of the
$JONAS_ROOT/conf/jonas-realm.xml
file.
The configuration requires the name of the datasource, the tables used, and the names of the
columns.
•
LDAP realm: users, groups, and roles information is stored in an LDAP directory. This is de-
scribed in the section
jonas-ldaprealm
of the
$JONAS_ROOT/conf/jonas-realm.xml
file.
There are some optional parameters. If they are not specified, some of the parameters are
set to a default value. That is, if the
providerUrl
element is not set, the default value is
ldap://localhost:389.
Edit the
jonas-realm_1_0.dtd
DTD file to see the default values.
For Tomcat, use the realm:
org.objectweb.jonas.security.realm.web.catalina50.JACC
These realms require as an argument the
name
of the resource to be used for the authentication.
This is the name that is in the
jonas-realm.xml
file.
Summary of Contents for Application Server
Page 1: ...Red Hat Application Server JOnAS User Guide ...
Page 8: ......
Page 22: ...14 Chapter 1 Java Open Application Server JOnAS a J2EE Platform ...
Page 58: ...50 Chapter 3 JOnAS Configuration ...
Page 66: ...58 Chapter 5 JOnAS Class Loader Hierarchy ...
Page 78: ...70 Chapter 6 JOnAS Command Reference ...
Page 80: ......
Page 86: ...78 Chapter 7 Developing Session Beans ...
Page 136: ...128 Chapter 9 Developing Message Driven Beans ...
Page 142: ...134 Chapter 10 Defining the Deployment Descriptor ...
Page 148: ...140 Chapter 11 Transactional Behavior of EJB Applications ...
Page 158: ...150 Chapter 14 EJB Packaging ...
Page 162: ...154 Chapter 15 Application Deployment and Installation Guide ...
Page 164: ......
Page 176: ...168 Chapter 18 WAR Packaging ...
Page 178: ......
Page 184: ...176 Chapter 20 Defining the Client Deployment Descriptor ...
Page 186: ...178 Chapter 21 Client Packaging ...
Page 188: ......
Page 192: ...184 Chapter 23 EAR Packaging ...
Page 194: ......
Page 200: ...192 Chapter 24 JOnAS Services ...
Page 204: ...196 Chapter 25 JOnAS and the Connector Architecture ...
Page 222: ...214 Chapter 27 Ant EJB Tasks Using EJB JAR ...
Page 234: ...226 Chapter 29 Web Services with JOnAS ...
Page 236: ......
Page 260: ...252 Chapter 34 How to use Axis in JOnAS ...
Page 270: ...262 Chapter 36 Web Service Interoperability between JOnAS and BEA WebLogic ...
Page 296: ......