|Home > Documentation > Creating deployment plans > Creating deployment plans for applications > Configuring resources in the application scope|
In this section, we will discuss about the configurations that are already deployed and running in the server when the server is installed and started.
Apache Geronimo ships with embedded Derby database and ActiveMQ message broker. There are also connection pools that connect to Derby and activeMQ configured to run in the installed server. The following sections discuss about various such configurations already running in the installed server.
Apache Geronimo ships with embedded Derby database. The Derby libraries are present in the server repository at
<geronimo_home>/repository/org/apache/derby. By default, a Derby database by name
SystemDatabase is created and the files related to the database are stored at
<geronimo_home>/var/derby/SystemDatabase. Along with that, by default, server deploys a database connection pool over the
SystemDatabase with the configuration name
org.apache.geronimo.configs/system-database/2.1/car. The name of the database connection pool is
SystemDatasource. The configuration artifacts are stored at
<geronimo_home>/repository/org/apache/geronimo/configs/system-database. The deployment plan used for database connection pool is as follows.
The default namespace of the above XML document is
http://geronimo.apache.org/xml/ns/j2ee/connector-1.2. The XML elements that do not have a namespace prefix belong to the default namespace.
After starting the server, the running database connection pool
SystemDatasource can be observed on the admin console from
console Navigation => Services => Database pools. The resource adapter used to deploy the above database connection pool is
tranql-connector-derby-embed-xa-1.3.rar. The above plan is actually deployment plan of a outbound resource adapter. If the above plan is packaged along with the
rar file, the xml content will be placed in
META-INF/geronimo-ra.xml of the archive.
Closely observe various configurations in the deployment plan. Many derby libraries in the server repository are mentioned as dependencies. After configuring the outbound resource adapter, there are series of gbeans configured for the database connection pool.
By default, a JMS resource adapter that connects to embedded activemq message broker is deployed and running in the apache geronimo server. This is an outbound jms resource adapter that configures a connection factory and two message queues. The configuration name of the resource adapter is
org.apache.geronimo.configs/activemq-ra/2.1/car. The artifacts of the resource adapter are stored at
<geronimo_home>/repository/org/apache/geronimo/configs/activemq-ra. The deployment plan is as follows.
The default namespace of the deployment plan is
http://geronimo.apache.org/xml/ns/j2ee/connector-1.2. The xml elements that do not have a namespace prefix belong to default namespace.
The resource adapter used to deploy the above plan is
<geronimo_home>/repository/org/apache/geronimo/modules/geronimo-activemq-ra/2.1. After the server is started, the running resource adapter can be looked up on the admin console from
Console Navigation => Services => JMS Resource. We can also observe the connection factories and queues deployed by the resource adapter on the admin console.
A Java EE application may consist of several components that can be deployed into different containers such as WEB container, EJB container, WebServices container in a JEE5 server. This kind of deployment allows multi-tier applications that interact with one another to perform a given user task. Multi-tier JEE5 applications can be secured by properly selecting authenticating mechanisms and designing authorization levels or roles. If the application components use declarative security management, the authentication and authorization aspects are declared in corresponding JEE5 deployment descriptors. The declared security roles or levels are mapped to real security roles or levels in the geronimo deployment plans through security realms. In Apache Geronimo , the security realms abstract away authentication and authorization aspects of the application components. The authentication and authorization together enable access control for the various components of the application.
Depending on the selected authenticating system, a JAAS login module is selected and configured in a security realm. JAAS login modules connect to corresponding user/group repositories and perform authentication and retrieve authorization information. The Geronimo server provides login modules that connect to different types of user/group repositories. These are PropertiesFileLoginModule, LDAPLoginModule, SQLLoginModule and CertificatePropertiesFileLoginModule.
For example, Geronimo uses geronimo-admin security realm to authenticate users when they login to the geronimo administration Console. The deployment plan of the security realm is follows.
The default namespace of the above XML document is
http://geronimo.apache.org/xml/ns/deployment-1.2. The XML elements that do not have a namespace prefix belong to the default namespace.
The above security realm is deployed over two property files
var/security/groups.properties that contain user/group information using
org.apache.geronimo.security.realm.providers.PropertiesFileLoginModule. The Geronimo Administration Console is a web application that uses the above security realm for user authentication.
The security realm deployment plan is an XML file that uses http://geronimo.apache.org/xml/ns/deployment-1.2 schema for moduleId, dependency and security realm GBean configurations. The XML file uses http://geronimo.apache.org/xml/ns/loginconfig-2.0 schema for login module configuration. All the XML schema files
(.xsd) are located at
The following table provides the summary of user/group repositories and corresponding login modules in Apache Geronimo
Depending on the type of the login module, the options for configuration may change.
Once a security realm is deployed, it is available for any JEE5 application deployed in Geronimo to map declared roles to actual users/groups through a Geronimo specific deployment plan.