ch04.html

详细介绍了jboss3.0的配置等

</td><td align="center">Y</td></tr><tr><td>1PC using Local-Transactions</td><td>One Phase Commit is sufficient for transactions within a single EIS.   If a resource adapter for an EIS supports only local transactions, the jboss transaction manager can manage transactions in the EIS through the use of the local-transaction ConnectionManager.</td><td align="center">Y</td></tr><tr><td colspan="3"><span class="emphasis"><i>Compatibility Features with other Subsystems</i></span></td></tr><tr><td>JCA Wrappers for JDBC Drivers.</td><td>JBoss provides connection to RDBMSs that have not yet implemented JCA-JDBC drivers through JCA wrappers for JDBC drivers.  Currently there are wrappers for JDBC Type-1 Drivers and JDBC Type-2 extension XADataSource based drivers.  This architecture makes it simple to work around the peculiarities of a driver for a particular database by writing a specific JCA wrapper for that driver, without modifying core JBoss code.</td><td align="center">Y</td></tr><tr><td>Messaging (JMS)</td><td>TBD based on JCA 2.0 (JSR 112).
For details on JCA 2.0, see:
http://www.jcp.org/jsr/detail/112.jsp
</td><td align="center">To do</td></tr><tr><td>Resource Adapter for JMS.</td><td>JCA resource adapter for a JMS system, allowing JMS activity to participate in declarative container managed transactions.  We believe this is the first such product available anywhere.</td><td align="center">Y</td></tr><tr><td>MetaData</td><td>TBD based on JCA 2.0 (JSR 112).
For details on JCA 2.0, see:
http://www.jcp.org/jsr/detail/112.jsp</td><td align="center">To do</td></tr><tr><td>WebServices, SOAP, XML</td><td>In a project named Jboss.net, development is proceeding rapidly on a SOAP/ webservices implementation based on Apache Axis.</td><td align="center">Y</td></tr><tr><td colspan="3"><span class="emphasis"><i>Security</i></span></td></tr><tr><td>Security</td><td>JBossCX uses JBossSX for standards based security.
JBossSX provides a Pluggable Security Framework based on JAAS.</td><td align="center">Y</td></tr><tr><td>JaasSecurityManager</td><td>JBossSX uses the JaasSecurityManager by default.  The LoginModules implement the Authentication and RoleMapping behavior for the security Domain.  

For server-side login:  Included are ProxyLoginModule, LdapLoginModule, DatabaseServerLoginModule, and SRPLoginModule.

For client-side login:  Included are ClientLoginModule, SRPLoginModule
</td><td align="center">Y</td></tr><tr><td>Credentials.</td><td>Security information that can be used to authenticate a Principal.</td><td align="center">Y</td></tr><tr><td>Principal.</td><td>An entity that can be authenticated by an authentication mechanism.
"Caller Principal" is the Application Security Domain.
"Resource Principal" is the EIS Security Domain.
When a Caller Principal requests an EIS connection, the Resource Principal has 4 choices for propagating the credentials:  Configured Identity; Principal Mapping; Caller Impersonation; Credential Mapping.</td><td align="center">Y</td></tr><tr><td>Resource Principal using Configured Identity.</td><td>This Resource Principal has its own configured identity and security attributes independent of the Caller Principal.  This configured identity can be specified either during deployment or dynamically by the application when creating the connection.</td><td align="center">Y</td></tr><tr><td>Resource Principal using Principal Mapping.</td><td>The Resource Principal is determined by a mapping in the J2EE server between the Caller Principal and the Resource Principal. The RP does not inherit any attributes from the CP.</td><td align="center">Y</td></tr><tr><td>Resource Principal using Caller Impersonation.</td><td>The Resource Principal acts on behalf of a Caller Principal - i.e. The Callers credentials are delegated to the EIS.  This requires an end-to-end security domain (e.g. Kerberos V5.).</td><td align="center">Y</td></tr><tr><td>Container Managed Sign-On.</td><td>The Application provides no security information when requesting a Connection.  The J2EE Server is configured to manage EIS sign-on.  The J2EE Server provides the required security information for the Resource Principal through its configured security policies and mechanisms.  The J2EE Server itself requests the authentication of the Resource Principal to the EIS, or it passes authentication responsibility to the Resource Adapter.JBoss currently provides an implementation of a simple policy and additional methods can easily be implemented.</td><td align="center">Y</td></tr><tr><td>Component Managed Sign-On.</td><td>The Application provides explicit security information when requesting a Connection.  The J2EE Server does not see the security information, and so must rely on the Application and Resource Adapter to manage the EIS sign-on.</td><td align="center">Y</td></tr><tr><td>Authentication based on UserName/Password.</td><td>JBossSX can be used to provide UserName/Password authentication.</td><td align="center">Y</td></tr><tr><td>Authentication based on Digital Certificates.</td><td>JBossSX can be used to provide client-to-server and server-to-server authentication using Digital Certificates.</td><td align="center">Y</td></tr><tr><td>Re-Authentication of Physical Connection.</td><td>If a resource adapter supports reauthentication, the jboss ConnectionManagers can be configured to use it to change the Principal for a connection with each Connection request. A Resource Adapter has to Re-Authenticate when the J2EE Server attempts to allocate a connection with a security context different from the context previously associated with the physical connection.  This assumes that the underlying EIS supports re-authentication of existing physical connections.</td><td align="center">Y</td></tr><tr><td colspan="3"><span class="emphasis"><i>Logging</i></span></td></tr><tr><td>Logging</td><td>Comprehensive logging capabilities using Log4J.
JBossCX is fully instrumented for logging with Log4J so you can detect and resolve errors faster.  Each component can be configured for different levels of logging.</td><td align="center">Y</td></tr><tr><td>Persist logs to various data stores.</td><td>Log4J can persist to File or any popular RDBMS.</td><td align="center">Y</td></tr><tr><td colspan="3"><span class="emphasis"><i>Deployment</i></span></td></tr><tr><td>Dynamic Resource Adapter Deployment.</td><td>JBoss offers on-the-fly resource adapter deployment and undeployment.   You can deploy and undeploy a resource adapter archive by adding it or removing it from a watched directory, by executing deploy/undeploy actions from the JMX console, or by programmatic interaction (inter or intra-vm) with the JMX server.  Using the jboss dynamic dependency mechanisms, undeploying a resource adapter currently being used by one or more ConnectionFactories will suspend the ConnectionFactories until the resource adapter is redeployed: when it is, the dependent ConnectionFactories will be automatically restarted.</td><td align="center">Y</td></tr><tr><td>Dynamic ConnectionFactory Deployment.</td><td>In keeping with the JBoss philosophy of dynamic deployment and configuration, ConnectionFactories may be, at any time, loaded and unloaded with the associated ManagedConnectionFactory, security and ConnectionManager configurations.  The configuration of these components may be changed at any time, while the server is running.</td><td align="center">Y</td></tr><tr><td>RAR deployment as part of an EAR</td><td>JBoss supports deployment of resource adapters contained in an EAR.</td><td align="center">Available Real Soon Now!</td></tr><tr><td>RAR deployment using accessible classloaders.</td><td>By using the jboss dynamically extensible classloader for deployment and redeployment of resource adapters while the server is running, JBoss allows applications to access the actual classes implementing the CCI interfaces, thus avoiding the reflection-based approaches necessary with certain other application servers.</td><td align="center">Y</td></tr><tr><td>Appropriate binding of ConnectionFactories in JNDI</td><td>In JBoss, ConnectionFactories are bound in JNDI using the referencable interface, so the exact instance bound is returned on lookup.  This is in contrast to certain commercial implementations that mistakenly use the serialization mechanism to bind ConnectionFactories, resulting in the creation of duplicate components on every lookup.</td><td align="center">Y</td></tr><tr><td colspan="3"><span class="emphasis"><i>Management and Administration</i></span></td></tr><tr><td>Management, Administration, Configuration Fully instrumented for management using JMX MBeans.</td><td>Consistent with the JMX based management structure of JBoss, all JBoss JCA related components are implemented as MBeans, allowing consistent and fine-grained control. Behavior can be set at Startup and can be dynamically/programmatically modified while the application is in production.</td><td align="center">Y</td></tr><tr><td>Remote Administration.</td><td>Administrators can create, delete, modify and set properties for all administered objects.</td><td align="center">Y</td></tr><tr><td>Remote Monitoring.</td><td>JBoss features the reference implementation of the JSR-77 management framework, providing comprehensive statistics and management capabilities. The JBossCX components fully participate in this framework.</td><td align="center">Under active development</td></tr><tr><td colspan="3"><span class="emphasis"><i>Documentation</i></span></td></tr><tr><td>Documentation</td><td>Comprehensive written documentation with examples.
The JBoss manual contains extensive discussion of all configuration parameters for JCA components.  Examples are provided for popular RDBMSs and EISs.</td><td align="center">Y</td></tr><tr><td>Comprehensive FAQ.</td><td>&nbsp;</td><td align="center">To do</td></tr></tbody></table></div></div></div><table border="0" cellpadding="0" cellspacing="0" height="65"><tr height="65"><td rowspan="2"><img src="gbar.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/gbar.gif" width="432" height="79"></td><td rowspan="2" background="gbar.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/gbar.gif" width="100%" align="right" valign="top"><a href="index.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/index.html"><img src="doc.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/doc.gif" border="0"></a><a href="index.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/index.html"><img src="toc.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/toc.gif" border="0"></a><a href="ch03s13.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch03s13.html"><img src="prev.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/prev.gif" border="0"></a><a href="ch04s02.html" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/ch04s02.html"><img src="next.gif" tppabs="http://www.huihoo.org/jboss/online_manual/3.0/next.gif" border="0"></a></td></tr><tr></tr></table></body></html>