![Red Hat Application Server Manual Download Page 32](http://html.mh-extra.com/html/red-hat/application-server/application-server_manual_1427406032.webp)
24
Chapter 3. JOnAS Configuration
You can configure JOnAS to use several protocols simultaneously. To do this, just specify a comma-
separated list of protocols in the
carol.protocols
property of the
carol.properties
file. For
example:
# jonas rmi activation (choose from jrmp, iiop, and cmi)
carol.protocols=jrmp,iiop
3.3.2. Security and Transaction Context Propagation
JOnAS implements EJB security and transactions by using the communication layer to propagate
the security and transaction contexts across method calls. By default, the communication proto-
col is configured for context propagation. However, this configuration can be changed by disabling
the context propagation for security and/or transaction; this is done primarily to increase perfor-
mance. The context propagation can be configured in the
jonas.properties
file by setting the
jonas.security.propagation
and
jonas.transaction.propagation
properties to
true
or
false
:
# Enable the Security context propagation
jonas.security.propagation
true
# Enable the Transaction context propagation
jonas.transaction.propagation
true
3.3.3. Multi-protocol Deployment (GenIC)
The JOnAS deployment tool (GenIC) must be told which protocol stubs (for remote invocation) are to
be generated. Choosing several protocols will eliminate the need to redeploy the EJBs when switching
from one protocol to another. The default is that GenIC generates stubs for
rmi/jrmp
. To change this
configuration, call GenIC as described in Section 6.5
GenIC
. Use the
-protocols
option to specify
a comma-separated list of protocols (chosen from
jrmp
,
iiop
, and
cmi
). For example:
GenIC -protocols jrmp,iiop
This list of protocols can also be specified for Ant EJB tasks (refer to Chapter 27
Ant EJB Tasks:
Using EJB-JAR
):
jonas destdir="${dist.ejbjars.dir}"
jonasroot="${jonas.root}"
protocols="jrmp,iiop"
keepgenerated="true"
verbose="${verbose}"
mappernames="${mapper.names}"
additionalargs="${genicargs}"
/jonas
3.4. Configuring Logging System (monolog)
The logging system is based on Monolog, the standard API for ObjectWeb projects (refer to
http://www.objectweb.org/monolog/doc/index.html). Configuring trace messages inside Jonas can be
done in two ways:
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: ......