$JONAS_ROOT/lib
.
Configuration of JOnAS is made via a little number of configuration files:
jonas.properties
file is used to configure the JOnAS
server and the different services that it may launch,jndi.properties
file is used to configure access to JNDI,config_env
files:
$JONAS_ROOT/bin/unix/config_env
on
Unix%JONAS_ROOT%\bin\nt\config_env.bat
on WindowsCLASSPATH
used by JOnAS.
JOnAS servers are configured via files
named jonas.properties
. It contains a list of key/value pairs
presented in the java properties file format.
Such files can be found at three different places:
$JONAS_ROOT/config/jonas.properties
$HOME/jonas.properties
./jonas.properties
A JOnAS server will read the three possible files in this order (1, 2, 3),
each one may overwrite properties defined in a previous file. Finally, it is
possible to define properties on the command line: (java -D...
).
jonas check
command to review the JOnAS configuration state.
The properties files related to Datasource configuration follows the same rule than the previous one.
The jndi.properties
file is automatically looked up by JNDI in the classpaths.
When you need to have the visibility of specific .jar
files,
the best practice consists in updating the config_env
file.
For example, to see the JDBC driver classes you need you may update in this file
one of the variables IDB_CLASSES
, ORACLE_CLASSES
, POSTGRE_CLASSES
,
INTERBASE_CLASSES
.
Another way to put an additional .jar
in the classpaths
of your JOnAS server is to insert at the end of config_env
file such a line:
CLASSPATH=<The_Path_To_Your_Jar>$SPS$CLASSPATHAt least, a third way to do this is to set the environment variable named
CLASSPATH
.
jonas.name
and jonas.orb.port
, the former indicates the name
of the JOnAS server, the latter the port number on which the remote objects receive calls.
jonas.name
is jonas.
When you need to have several JOnAS servers running simultaneously
it is valuable to set a different name for each JOnAS server and so it will be possible to administrate
these servers via the JOnAS administration tools.
jonas.orb.port
is 0 this means that an anonymous port is chosen.
Setting this property to a specific port number may be used when JOnAS server is behind a firewall.
Access to JNDI is bound to a jndi.properties
file that must
be accessible from the classpath.
Such a file is supplied with the JOnAS distribution in the
$JONAS_ROOT/config
directory and by default the CLASSPATH
is up to date
to access to this file by the way of the config_env file.
The jndi.properties
file contents for RMI and DAVID is:
java.naming.factory.initial com.sun.jndi.rmi.registry.RegistryContextFactory java.naming.provider.url rmi://localhost:1099 java.naming.factory.url.pkgs org.objectweb.jonas.naming
The jndi.properties
file contents for JEREMIE is:
java.naming.factory.initial org.objectweb.jeremie.libs.services.registry.jndi.JRMIInitialContextFactory java.naming.provider.url jrmi://localhost:12340 java.naming.factory.url.pkgs org.objectweb.jonas.naming
Customization of JNDI consists to edit the
$JONAS_ROOT/config/jndi.properties
file and mainly to choose between RMI and JEREMIE.
You may change localhost
to the hostname where registry will be run.
You may want to change the standard port number too. In this case, don't forget to run
registry with this port number as argument: registry <Your_Portnumber>
,
when the registry is not launched inside the EJB server.
Remember of the default configuration of the JOnAS distribution is for RMI.
The following steps are required to change from RMI to JEREMIE:
jndi.properties
file as indicated previously.OBJECTWEB_ORB=JEREMIE
in the $JONAS_ROOT/bin/unix/config_env
file
on Unix (or in the %JONAS_ROOT%\bin\nt\config_env.bat
file on Windows). If you have already deployed EJB with RMI you must redeploy (i.e. run the GenIC tool) them for JEREMIE use.
JEREMIE has a special configuration file
jonathan.xml
under
$JONAS_ROOT/config
, that, in general you can easily ignore.
This file must be seen via the classpath and it is the case by default thanks to
the JOnAS bootstrap
class.
Look at Configuring Jonathan/Jeremie how to
disable security feature with JEREMIE.
From now on, you can build/use JOnAS on the top of DAVID which is the CORBA personality of the JONATHAN ORB.This version uses two naming services for object binding:
The general operation principle of JOnAS over rmi-iiop is the same operation principle than JOnAS over rmi-jrmp, there are only some restrictions listed at the end of this section. Remember of the default configuration of the JOnAS distribution is for RMI.
The following steps are required to change from RMI to DAVID:
jndi.properties
file as for RMI.OBJECTWEB_ORB=DAVID
in the $JONAS_ROOT/bin/unix/config_env
file
on Unix (or in the %JONAS_ROOT%\bin\nt\config_env.bat
file on Windows).COSNAMING_PORT=14727
(this is an example, set your Cosnaming port)
COSNAMING_HOST=jonas.objectweb.org
(this is an example, set your Cosnaming host) in
the $JONAS_ROOT/bin/unix/config_env
file on Unix (or in
the %JONAS_ROOT%\bin\nt\config_env.bat
file on Windows). If you have already deployed EJB with RMI or JEREMIE you must re-deploy (i.e run the GenIC tool) them for DAVID use.
DAVID has a special configuration file
jonathan.xml
under
$JONAS_ROOT/config
, that, in general, you can easily ignore.
This file must be seen via the CLASSPATH
and it is the case by default
thanks to the JOnAS bootstrap
class.
Look at Configuring Jonathan/David how to
disable security feature with DAVID.
CosNaming and Registry with DAVID special features
jonas.services.registry.mode
to value remote
in the JONAS_ROOT/config/jonas.properties
file.
The default value for jonas.services.registry.mode
is automatic
so, if you start the remote registry
before the JOnAS server with the default configuration, it will work fineregistry 14727 1099
.
The last two numbers (CosNaming port and Registry port) are optional, if they are not
specified,
the registry starts with default configuration: with the CosNaming port set to 14727 and
the registry port set to 1099. Be sure that, if you run
the registry command with the 2 port numbers,
this two numbers correspond to your server configuration (COSNAMING_PORT
and
provider.url port in the jndi.properties file
)Rmi Iiop Client with DAVID
The following steps are required to launch a rmi iiop client with David:
OBJECTWEB_ORB
set to DAVID)registry <cosnaming port> <registry port>
EJBServer <cosnaming host> <cosnaming port>
java \
-Dorg.omg.CORBA.ORBClass=org.objectweb.david.libs.binding.orbs.iiop.IIOPORB \
-Dorg.omg.CORBA.ORBSingletonClass=org.objectweb.david.libs.binding.orbs.ORBSingletonClass \
-Djavax.rmi.CORBA.StubClass=org.objectweb.david.libs.stub_factories.rmi.StubDelegate \
-Djavax.rmi.CORBA.PortableRemoteObjectClass=org.objectweb.david.libs.binding.rmi.ORBPortableRemoteObjectDelegate \
-Djavax.rmi.CORBA.UtilClass=org.objectweb.david.libs.helpers.RMIUtilDelegate \
-Ddavid.CosNaming.default_method=0 \
-Ddavid.rmi.ValueHandlerClass=com.sun.corba.se.internal.io.ValueHandlerImpl \
-Ddavid.CosNaming.default_host=$COSNAMING_HOST \
-Ddavid.CosNaming.default_port=$COSNAMING_PORT \
your.client.ClassName
JOnAS with DAVID Restrictions:
Since Jonas 2.5, the logging system is based on Monolog, the new standard API for Objectweb projects. Configuring trace messages inside Jonas can be done by two ways :
A standard file is given in $JONAS_ROOT/config/trace.properties
The policy to retrieve this file is to use the CLASSPATH. You can either change the file in its standard location, or to copy
your own version somewhere else.
You can refer to the monolog documentation to know in more details how you can configure logging.
Basically, we must know that monolog is build above a standard log API (currently, log4j). You can define loggers, each one
being backed on a handler.
An handler represents an output. An handler is identified by its name.
It has a type and few others properties. In trace.properties file
two handlers have been defined :
Each handler can define the header it will use, the type of logging (console, file, rolling file), and the file name.
Note that if you specify as output filename the tag "automatic", JOnAS will replace this tag by a file pointing
to $JONAS_BASE/logs/<jonas_name_server>-<timestamp>.log
The logf handler which is bundled with JOnAS use this "automatic" tag.
Loggers are identified by names which are structured as a tree. The root of the tree is named root.
Each logger is a topical logger, i.e. is associated with a topic. Topic names are usually based on the package name. Each logger can define the handler it will use, and the trace level among these 4 values :
If a logger has nothing defined, it will use the properties defined for its parent.
Jonas code is written using directly monolog API, it can use the tty handler.
Example of setting DEBUG level for the logger used in jonas_ejb module:
logger.org.objectweb.jonas_ejb.level DEBUG
Example for setting the output of JOnAS traces both on console and file /tmp/jonas/log
:
handler.logf.output /tmp/jonas.log logger.org.objectweb.jonas.handler.0 tty logger.org.objectweb.jonas.handler.1 logf
Example for setting the output of JOnAS traces on a file in $JONAS_BASE/logs/
directory:
handler.logf.output automatic logger.org.objectweb.jonas.handler.0 logf
Jadmin
administration console, which is a Servlet based application using the JMX technology. Note that Jadmin can only manage available services (currently it is not possible to launch a service via Jadmin).
jonas.services
property in the jonas.properties
file must contain a list of the required service names. Currently, these services will be started in the order they appear in the list. Therefore, the following constraints should be considered:
Consider de following example :
jonas.services registry,jmx,security,jtm,dbm,resource,jms,mail,web,ejbThe registry could be omitted from the list as this service is automatically launched if it is not already activated by another previously started server.
Note also, that it is possible to launch the Transaction manager service alone.
Most of configuration information for services are located in the jonas.properties
file following a precise naming convention : a service XX will be configured via a set
of properties:
jonas.service.XX.foo
something
jonas.service.XX.bar
else
jndi.properties
see Configuring JNDI Environment.
There are several Registry launching modes depending on the value of the
JOnAS property, jonas.service.registry.mode
.
The possible values of the jonas.service.registry.mode
property are:
collocated
: the Registry is launched in the same JVM as JOnAS Server,remote
: the Registry has to be launched before in a separate JVM,automatic
: the Registry is launched in the same JVM as JOnAS Server,
if it's not already started, (this is the default value).The port number on which the Registry is launched, is defined in the
jndi.properties
file.
An EJB container can be created from an ejb-jar
file using one of the following possibilities:
ejb-jar
file name is listed in the jonas.service.ejb.descriptors
property in jonas.properties
file. If the file name does not contain an absolute path name,
than it may be located in the directory where the JOnAS server is launched or in the $JONAS_ROOT/ejbjars/
directory. The container is created when the JOnAS server starts.
Example:
jonas.service.ejb.descriptors Bank.jarHere the Container service will create a container from the
ejb-jar
file named Bank.jar
.
If there is no Bank.jar
file in the directory where JOnAS was launched,
this file will be searched in $JONAS_ROOT/ejbjars/
directory.
ejb-jar
files in an autoload directory. The name of this directory is specified using the jonas.service.ejb.autoloaddir
property in jonas.properties
file.
ejb-jar
files using the Jadmin
tool.
JOnAS also allows for loading unpacked EJB components. The name of the xml
file containing the EJB's deployment descriptor must be listed in the jonas.service.ejb.descriptors
property. Note that the JOnAS server must have access to the component's classes which may be achieved using the XTRA_CLASSPATH
environment variable.
Jadmin
tool.
If the environment variables $JETTY_HOME
or $CATALINA_HOME
are not set, the web container service can't be loaded at the JOnAS startup. So a warning is displayed.
A WEB container is created from a war
file. If the file name does not contain
an absolute path name, than it may be located in the directory where the JOnAS Server
is launched or in the $JONAS_ROOT/webapps/
directory.
In order for JOnAS to create WEB containers, the corresponding file names may be provided using the jonas.service.web.descriptors
property
in jonas.properties
file. In this case, the WEB containers are created when the
JOnAS server starts.
WEB containers may be also dynamically created from war
files using the Jadmin
tool.
Example:
jonas.service.web.descriptors Bank.warHere the WEB Container service will create a container from the
war
file named Bank.war
.
If there is no Bank.war
in the directory where JOnAS was launched,
this file will be searched in $JONAS_ROOT/webapps/
directory.ejb-jar
and war
files packed in an ear
file).
This service is based upon the WEB container service and the EJB container service. The WEB container service is
used to provide the WEB containers for the wars
composing the J2EE application, and the
EJB container service is used to provide the EJB containers for the ejb-jars
composing the J2EE application.
This service may be configured by setting the jonas.service.ear.descriptors
property
in jonas.properties
file. This property provides a list of ears
that must be deployed when
JOnAS is launched.
The Jadmin
tool can be used to dynamically deploy the J2EE application components from an ear
file.
When using relative paths for ear
file names, the files may be located in the directory where the JOnAS Server
is launched or in the $JONAS_ROOT/apps/
directory.
Example:
jonas.service.ear.descriptors Bank.earHere the EAR service will deploy the
ear
file named Bank.ear
.
If there is no Bank.ear
in the directory where JOnAS was launched,
this file will be searched in $JONAS_ROOT/apps/
directory.jonas.name TM jonas.services jtm jonas.service.jtm.remote falseand
jonas.name EJB jonas.services jmx,security,jtm,dbm,ejb jonas.service.jtm.remote true jonas.service.ejb.descriptors foo.jarAnother possible configuration is the value of the transaction time-out, in seconds, via the
jonas.service.jtm.timeout
property.
jonas.service.jtm.timeout 60
In order to be able to access one or several relational databases (e.g. Oracle, InstantDB, PostgreSQL, ...), JOnAS will create and use DataSource objects. You have to configure such a DataSource object according to the database you intend to use for the persistence of a bean. More details about DataSource objects and their configuration is provided in the "Configuring JDBC DataSources" chapter of the Bean Programmer's Guide.
The subsections below briefly explains how to configure a DataSource object for your database, in order to be able to run the Entity Bean example delivered with the platform.
A template Oracle1.properties file is
supplied in the installation directory. This file is used to define a
DataSource object, named Oracle1
.
You must update this template with values proper to your installation.
The fields are the following:
datasource.name | JNDI name of the DataSource: The name used in the example is jdbc_1 .
|
datasource.url | The JDBC database URL: for the Oracle JDBC "Thin" driver it is jdbc:oracle:thin:@hostname:sql*net_port_number:ORACLE_SID If you are using an Oracle OCI JDBC driver, the URL is jdbc:oracle:oci7: or jdbc:oracle:oci8:
|
datasource.classname | Name of the class implementing the Oracle JDBC driver:oracle.jdbc.driver.OracleDriver
|
datasource.username | Database user name |
datasource.password | Database user password |
In order that the EJB platform creates the corresponding DataSource object,
you must have its name (Oracle1, not the JNDI name) in your
jonas.properties
file, on the jonas.service.dbm.datasources line:
jonas.service.dbm.datasources Oracle1
You may have several DataSource objects defined for an EJB server, in this case, you will have several dataSourceName.properties files, and the list of DataSource names on the jonas.service.dbm.datasources line of the jonas.properties file:
jonas.service.dbm.datasources Oracle1, Oracle2, InstantDB1
Your Oracle server must be running, and a JDBC driver installed (Oracle
JDBC drivers may be downloaded at their Web site).
You can then create the table used by the example with the SQL script
provided in examples/src/eb/Account.sql
.
For example:
sqlplus user/passwd SQL> @Account.sql SQL> quit
The JDBC driver classes must be accessible from the classpath. For that, you must
update the config_env file;
($JONAS_ROOT/bin/unix/config_env
on Unix,
or %JONAS_ROOT%\bin\nt\config_env.bat
on Windows).
A template InstantDB1.properties file is supplied in the installation directory. This file is used to define a Datasource object, named InstantDB1. You must update this template with values proper to your installation. The fields are the following:
datasource.name | JNDI name of the DataSource:
The name used in the example is jdbc_1 .
|
datasource.url | The JDBC database URL: for InstantDB it is
jdbc:idb=db1.prp
|
datasource.classname | Name of the class implementing the JDBC driver:
org.enhydra.instantdb.jdbc.idbDriver
|
In order that the EJB platform creates the corresponding DataSource object,
you must have its name (InstantDB1, not the JNDI name) in your
jonas.properties
file, on the jonas.service.dbm.datasources line
jonas.service.dbm.datasources InstantDB1
InstantDB should have been properly installed and configured. You should use a version higher than 3.14. (examples have been tested with 3.25).
The JDBC driver classes must be accessible from the classpath. For that, you must
update the config_env file;
($JONAS_ROOT/bin/unix/config_env
on Unix,
or %JONAS_ROOT%\bin\nt\config_env.bat
on Windows).
You have to create the Account database using the utility provided with InstantDB:
cd examples/src/eb . $JONAS_ROOT/bin/unix/config_env java org.enhydra.instantdb.ScriptTool Account.idb
The same kind of process can be used for other databases. We supply with JOnAS a template of datasource for PostgreSQL and for InterBase. Of course many other databases are currently used by the JOnAS users, e.g. Informix, Sybase, SQL Server, ... however not all JDBC drivers have been tested against JOnAS.
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 security. The Security service exploits security roles and method permissions found in the EJB deployment descriptor.
Note that:
jonas.properties
file for configuring security service.
It is up to Jonathan/Jeremie to propagate the security context
(built after authentication process). However if this security feature is not needed,
you can disable this feature by modifying the
jonathan.xml
file and
put this line in comments:
<ELEM name="200"><ALIAS name="/jeremie/SSHandler/instance"/></ELEM>
Disabling the security feature increases performance.
It is up to Jonathan/David to propagate the security context
(built after authentication process). However if this security feature is not needed,
you can disable this feature by modifying the
jonathan.xml
file and
put this line in comments:
<ELEM name="200"><ALIAS name="/david/SSHandler/instance"/></ELEM>
Disabling the security feature increases performance.
With RMI in order to use security in JOnAS, special Stubs and Skeletons must
be generated.
This is done by using GenIC tool with the
-secpropag
option.
With Tomcat4.1.x (both on RMI or on Jeremie), in the
$CATALINA_HOME/conf/server.xml
file, or $CATALINA_BASE/conf/server.xml
replace the following line:
<Realm className="org.apache.catalina.realm.MemoryRealm"/>
by :
<Realm className="org.objectweb.security.tomcat.interceptor.SecurityCtxInterceptor41"/>
web-jetty.xml
file under WEB-INF
directory in the .war
file in which it specified that the security interceptor org.objectweb.security.jetty.realm.JonasRealm
for JOnAS must be used instead of the default one.jettyRealm.properties
file that is used by jetty for authentication. You will find under JONAS_ROOT/config
an example of such a file currently initialized for using jadmin
, earsample
example and alarm
demo.JOnAS relies on the
jonas-users.properties
file for the access control to
the methods of EJB components. This is a simple properties file where
each property has the following
syntax: <principal> = <list of roles>
where
<principal>
is a string identifying the user. It can
be an email address
(joe.bar@foo.com
) or a login (barj
) or
whatever identifying the user.
<list of roles>
is a list of roles separated by
commas (e.g.: administrator, user
). These roles will
be used in the deployment descriptor of the EJB component.It has to be noted that to use Tomcat to identify and authenticate
the users, the principals defined in the jonas-users.properties
must be the same that those in the
$CATALINA_BASE/conf/tomcat-users.xml
file for Tomcat 4.1.x.
However, the roles defined in these two files may be
the same but it is not mandatory:
tomcat-users.xml
file
are used in Tomcat.jonas-users.properties
file are used in JOnAS.For Jetty the corresponding configuration file is jettyRealm.properties
file in which users passwords and roles are defined for each web application. This file is by default under JONAS_ROOT/config
.
jonas.properties
file for jms service:
jonas.service.jms.collocated
for setting the JMS server launching mode.
If set to true it is launched in the same JVM as JOnAS Server (this is the default value)
if set to false it is launched in a separate JVM in this case the jonas.service.jms.url
must be set with the connexion url to the JMS server.
jonas.service.ejb.mdbthreadpoolsize
is used for setting the default thread pool
used Message Driven Beans (10 is the default value).
jonas.service.jms.queues
and jonas.service.jms.topics
are used for setting lists
of administered objects queues or topics at launching time.
jonas.service.jms.mom
is used to indicate what class must be used to perform
administrative operations. This class is the wrapper to the actual JMS provider
implementation. The default one is org.objectweb.jonas_jms.JmsAdminForJoram
that must be used for Joram.
You may get a com.swiftmq.appserver.jonas.JmsAdminForSwiftMQ class from the
SwiftMQ site if you intend to use the SwiftMQ product.
The role of the Connector Architecture Resources service is to deploy the Resource Adapters in the JOnAS server i.e configure it in the operational environment and register in JNDI name space a connection factory instance that can be looked up by the EJB components.
The way to configure the Connector Architecture Resources service is one of the following methods:
rar
file name is listed in the jonas.service.resource.resources
property in jonas.properties
file. If the file name does not contain an absolute path name,
then it may be located in the directory where the JOnAS server is launched or in the $JONAS_ROOT/rars/
directory.
Example:
jonas.service.resource.resources MyEISIf there is no
MyEIS.rar
file in the directory where JOnAS was launched,
this file will be searched for in the $JONAS_ROOT/rars/
directory.
This property is a comma-separated list of resource adapter file names ('.rar' suffix is optional).
rar
files in an autoload directory. The name of this directory is specified using the jonas.service.resource.autoloaddir
property in jonas.properties
file.
This directory is relative to the $JONAS_ROOT/rars/
directory.
In each resource adapter a jonas specific resource adapter configuration xml file must be included. This file reflects the values of all configuration properties declared in the deployment descriptor for the resource adapter. See Using a Connector Architecture Resource Adapter with JOnAS for additional information.
Jadmin
.This is not a mandatory service
but if it is needed, it must be launched first. Its configuration consists in choosing one of the two supported JMX implementations, SUN RI or MX4J. The choice is done based on the value of the jonas.service.jmx.class
property in the JOnAS configuration
file. The two possible values are:
org.objectweb.jonas.jmx.sunri.JmxServiceImpl
, for choosing the SUN RIorg.objectweb.jonas.jmx.mx4j.Mx4jJmxServiceImpl
, for choosing MX4JIn order to be able to send or receive mails we need a mail factory. JOnAS provides two types of mail factories : javax.mail.Session
and javax.mail.internet.MimePartDataSource
.
MimePartDataSource
factories allow you to send mails with a subject and recipients already set.
Mail factory objects must be configured accordingly to their type. The subsections below briefly explain how to configure Session
and MimePartDataSource
mail factory objects,
in order to be able to run the SessionMailer
SessionBean and the MimePartDSMailer
SessionBean delivered with the platform.
The template MailSession1.properties file
supplied in the installation directory defines a mail factory of Session
type. The JNDI name of the mail factory object is mailSession_1
.
You must update this template with values proper to your installation.
See the section "Configuring a mail factory" for the list of available properties.
The template MailMimePartDS1.properties file
supplied in the installation directory defines a mail factory of MimePartDSMailer
type. The JNDI name of the mail factory object is mailMimePartDS_1
.
You must update this template with values proper to your installation.
You'll find in the section "Configuring a mail factory" the list of available properties.
Let's see before, how to configure JOnAS in order to create the mail factory objects you need.
In order for JOnAS to create mail factory objects,
you must name them. In the mailsb example, we defined 2 factories called
MailSession1 and MailMimePartDS1.
For each factory we provided a configuration file named with the name of the
factory and having the .properties
extension (MailSession1.properties
for
the MailSession1 factory).
Also, the jonas.properties
file must define the jonas.service.mail.factories
property. In the case of our example, we have:
jonas.service.mail.factories MailSession1,MailMimePartDS1
The fields are the following:
Required properties | mail.factory.name | JNDI name of the mail factory. |
mail.factory.type | The type of the factory. This property can be javax.mail.Session or
javax.mail.internet.MimePartDataSource .
|
Optional properties | |
Authentication properties | |
mail.authentication.username | Set the username for the authentication |
mail.authentication.password | Set the password for the authentication |
javax.mail.Session.properties(see JavaMail documentation for more information) | |
mail.authentication.username | Set the username for the authentication |
mail.authentication.password | Set the password for the authentication |
mail.debug | The initial debug mode. Default is false. |
mail.from |
The return email address of the current user, used by the
InternetAddress method getLocalAddress .
|
mail.mime.address.strict |
The MimeMessage class uses the InternetAddress method
parseHeader to parse headers in messages. This property
controls the strict flag passed to the parseHeader
method. The default is true.
|
mail.host |
The default host name of the mail server for both Stores and Transports.
Used if the mail.protocol.host property isn't set.
|
mail.store.protocol |
Specifies the default message access protocol. The
Session method getStore() returns a Store
object that implements this protocol. By default the first Store
provider in the configuration files is returned.
|
mail.transport.protocol |
Specifies the default message access protocol. The
Session method getTransport() returns a Transport
object that implements this protocol. By default the first Transport
provider in the configuration files is returned.
|
mail.user |
The default user name to use when connecting to the mail server.
Used if the mail.protocol.user property isn't set.
|
mail.<protocol>.class | Specifies the fully qualified class name of the provider for the specified protocol. Used in cases where more than one provider for a given protocol exists; this property can be used to specify which provider to use by default. The provider must still be listed in a configuration file. |
mail.<protocol>.host |
The host name of the mail server for the specified protocol.
Overrides the mail.host property.
|
mail.<protocol>.port | The port number of the mail server for the specified protocol. If not specified the protocol's default port number is used. |
mail.<protocol>.user |
The user name to use when connecting to mail servers
using the specified protocol.
Overrides the mail.user property.
|
MimePartDataSource properties (Only used if mail.factory.type is javax.mail.internet.MimePartDataSource) | |
mail.to | Set the list of primary recipients ("to") of the message |
mail.cc | Set the list of Carbon Copy recipients ("cc") of the message |
mail.bcc | Set the list of Blind Carbon Copy recipients ("bcc") of the message |
mail.subject | Set the subject of the message |