[jboss-cvs] JBossAS SVN: r101433 - projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Feb 24 20:55:04 EST 2010
Author: laubai
Date: 2010-02-24 20:55:03 -0500 (Wed, 24 Feb 2010)
New Revision: 101433
Modified:
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Administration_And_Configuration_Guide.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Pooling.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Transactions.xml
projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml
Log:
Adding Juca's corrections for JBPAPP-3361.
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Administration_And_Configuration_Guide.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Administration_And_Configuration_Guide.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Administration_And_Configuration_Guide.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -10,7 +10,7 @@
<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<part id="JBoss_AS_Infrastructure" label="I">
- <title>JBoss Enterprise Application Platform Infrastructure</title>
+ <title>JBoss Enterprise Web Platform Infrastructure</title>
<xi:include href="Architecture.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
@@ -19,7 +19,7 @@
<part id="Application_Configuration" label="II">
- <title>JBoss Enterprise Application Platform 5 Configuration</title>
+ <title>JBoss Enterprise Web Platform 5 Configuration</title>
<xi:include href="Deploy.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<!--<xi:include href="General_Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />-->
<xi:include href="Microcontainer.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Alternative_DBs.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -332,12 +332,45 @@
<para> <classname>org.jboss.resource.adapter.jdbc.vendor.InformixExceptionSorter</classname>
</para>
</listitem>
+ <listitem>
+ <para>
+<classname>org.jboss.resource.adapter.jdbc.vendor.DB2ExceptionSorter</classname>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+<classname>org.jboss.resource.adapter.jdbc.vendor.PostgreSQLExceptionSorter</classname>
+ </para>
+ </listitem>
</itemizedlist>
</listitem></varlistentry>
<varlistentry><term><literal>valid-connection-checker-class-name</literal></term><listitem>
<para>
- This specifies a class that implements the <classname>org.jboss.resource.adapter.jdbc.ValidConnectionChecker</classname> interface to provide a <literal>SQLException isValidConnection(Connection e)</literal> method that is called with a connection that is to be returned from the pool to test its validity. This overrides the <literal>check-valid-connection-sql</literal> when present. The only provided implementation is <classname>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</classname>.
+ This specifies a class that implements the <classname>org.jboss.resource.adapter.jdbc.ValidConnectionChecker</classname> interface to provide a <literal>SQLException isValidConnection(Connection e)</literal> method that is called with a connection that is to be returned from the pool to test its validity. This overrides the <literal>check-valid-connection-sql</literal> when present. The implementations provided with JBoss Enterprise Web Platform are:
</para>
+ <itemizedlist>
+ <listitem><para>
+ org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker
+ </para></listitem>
+ <listitem><para>
+ org.jboss.resource.adapter.jdbc.vendor.DB2ValidConnectionChecker
+ </para></listitem>
+ <listitem><para>
+ org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker
+ </para></listitem>
+ <listitem><para>
+ org.jboss.resource.adapter.jdbc.vendor.MySQLReplicationValidConnectionChecker
+ </para></listitem>
+ <listitem><para>
+ org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker
+ </para></listitem>
+ <listitem><para>
+ org.jboss.resource.adapter.jdbc.vendor.PostgreSQLValidConnectionChecker
+ </para></listitem>
+ <listitem><para>
+ org.jboss.resource.adapter.jdbc.vendor.SybaseValidConnectionChecker
+ </para></listitem>
+ </itemizedlist>
</listitem></varlistentry>
<varlistentry><term><literal>track-statements</literal></term><listitem>
<para>
@@ -553,7 +586,7 @@
<term><literal><![CDATA[<jndi-name>]]></literal></term>
<listitem>
<para>
- The JNDI name where it is bound. This is prefixed with <literal>java:\</literal> by default.
+ The JNDI name where it is bound. This is prefixed with <literal>java:/</literal> by default.
</para>
</listitem>
</varlistentry>
@@ -561,7 +594,7 @@
<term><literal><![CDATA[<use-java-context>]]></literal></term>
<listitem>
<para>
- Set this to <literal>false</literal> to drop the <literal>java:\</literal> context from the JNDI name.
+ Set this to <literal>false</literal> to drop the <literal>java:/</literal> context from the JNDI name.
</para>
</listitem>
</varlistentry>
@@ -867,26 +900,8 @@
<listitem><para><filename>$JBOSS_HOME/server/$PROFILE/conf/login-config.xml</filename>: This file is used in Java EE container managed security services.</para></listitem>
<listitem><para><filename>$JBOSS_HOME/server/$PROFILE/conf/standardjbosscmp-jdbc.xml</filename>: This file configures the CMP beans in the EJB container.</para></listitem>
-
-<!-- <listitem><para><literal><JBoss_Home>/server/all/deploy/ejb-deployer.xml</literal>: This file configures the JBoss EJB deployer.</para></listitem>
--->
-
+
<listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/ejb2-timer-service.xml</filename>: This file configures the EJB timer services.</para></listitem>
-
- <!-- <listitem><para><literal>${jboss.dist}/server/${server}/deploy/snmp-adaptor.sar/attributes.xml</literal>: This file is used by the SNMP service.</para></listitem>
- -->
-
- <listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/juddi-service.sar/META-INF/jboss-service.xml</filename>: This file configures the UUDI service.</para></listitem>
-
- <listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/juddi-service.sar/juddi.war/WEB-INF/jboss-web.xml</filename>: This file configures the UUDI service.</para></listitem>
-
- <listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties</filename>: This file configures the UUDI service.</para></listitem>
-
- <listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml</filename>: This file configures the UUDI service.</para></listitem>
-
-<!-- <listitem><para><filename>$JBOSS_HOME/server/$PROFILE/deploy/messaging/messaging-jboss-beans.xml</filename> and <filename>$JBOSS_HOME/server/$PROFILE/deploy/messaging/persistence-service.xml</filename>: Those files configure the JMS persistence service as we discussed earlier.</para></listitem>-->
-
- <!-- ${jboss.dist}/server/${server}/deploy/schedule-manager-service.xml -->
</itemizedlist>
</section>
@@ -916,25 +931,6 @@
</mbean>
]]></programlisting>
- <para>Similarly, you need to change the <filename>$JBOSS_HOME/server/$PROFILE/deploy/uuid-key-generator.sar/META-INF/jboss-service.xml</filename> file to change the table name from <literal>HILOSEQUENCES</literal> to something like <literal>schemaname2.tablename</literal> as well.</para>
-
-<programlisting><![CDATA[
-<!-- HiLoKeyGeneratorFactory -->
-<mbean code="org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory"
-name="jboss:service=KeyGeneratorFactory,type=HiLo">
-
-<depends>jboss:service=TransactionManager</depends>
-
-<!-- Attributes common to HiLo factory instances -->
-
-<!-- DataSource JNDI name -->
-<depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
-
-<!-- table name -->
-<attribute name="TableName">HILOSEQUENCES</attribute>
-]]></programlisting>
-
-
</section>
<section><title>DataSource configuration</title>
@@ -1073,7 +1069,7 @@
<term><varname><![CDATA[<use-java-context>]]></varname></term>
<listitem>
<para>
- A boolean indicating if the <varname>jndi-name</varname> should be prefixed with <literal>java:\</literal>, which causes the DataSource to only be accessible from within the JBoss server VM. The default is <literal>true</literal>.
+ A boolean indicating if the <varname>jndi-name</varname> should be prefixed with <literal>java:/</literal>, which causes the DataSource to only be accessible from within the JBoss server VM. The default is <literal>true</literal>.
</para>
</listitem>
</varlistentry>
@@ -1259,7 +1255,7 @@
</para>
</listitem>
</varlistentry>
- <varlistentry>
+ <!--<varlistentry>
<term><varname><![CDATA[<url-delimiter>]]></varname></term>
<listitem>
<para>
@@ -1282,7 +1278,7 @@
Database failover is part of the main DataSource configuration.
</para>
</listitem>
- </varlistentry>
+ </varlistentry>-->
<varlistentry>
<term><varname><![CDATA[<stale-connection-checker-class-name>]]></varname></term>
<listitem>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Architecture.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -8,7 +8,7 @@
<indexterm><primary>JBoss Enterprise Web Platform</primary><secondary>architecture</secondary></indexterm>
The following diagram illustrates an overview of the JBoss Enterprise Web Platform and its components.
<inlinemediaobject>
- <imageobject>
+ <imageobject><!--image must be replaced by RT#59811: https://engineering.redhat.com/rt3/Ticket/Display.html?id=59811-->
<imagedata fileref="images/jboss-as-components.png"/>
</imageobject>
</inlinemediaobject>
@@ -18,7 +18,7 @@
The directory structure of JBoss Enterprise Web Platform is outlined here:
</para>
<screen>
-<![CDATA[-jboss-as-web - the path to your JBoss Enterprise Application Server.
+<![CDATA[-jboss-as-web - the path to your JBoss Enterprise Web Platform application server.
|-- bin - contains start scripts and run.jar
|-- client - client jars
|-- common/lib - static jars shared across server configuration
@@ -53,7 +53,7 @@
The <classname>org.jboss.Main</classname> entry point in JBoss Enterprise Web Platform 5 loads an <classname>org.jboss.system.server.Server</classname> implementation. This is a JBoss Microcontainer.
</para>
<indexterm><primary>JBoss Enterprise Web Platform</primary><secondary>Server interface implementation</secondary></indexterm>
- <para>The default JBoss Enterprise Web Platform 5 <classname>org.jboss.system.server.Server</classname> implementation is <classname>org.jboss.bootstrap.microcontainer.ServerImpl</classname>. This implementation is an extension of the kernel basic bootstrap that boots the MC from the bootstrap beans declared in <filename><![CDATA[<jboss.server.config.url>/bootstrap.xml]]></filename> descriptors using a <classname>BasicXMLDeployer</classname>. In addition, the <classname>ServerImpl</classname> registers install callbacks for any beans that implement the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface. The <filename>bootstrap/profile*.xml</filename> configurations include a <classname>ProfileServiceBootstrap</classname> bean that implements the <classname>Bootstrap</classname> interface.
+ <para>The default JBoss Enterprise Web Platform 5 <classname>org.jboss.system.server.Server</classname> implementation is <classname>org.jboss.bootstrap.microcontainer.ServerImpl</classname>. This implementation is an extension of the kernel basic bootstrap that boots the MC from the bootstrap beans declared in <filename><![CDATA[<jboss.server.config.url>/bootstrap.xml]]></filename> descriptors using a <classname>BasicXMLDeployer</classname>. In addition, the <classname>ServerImpl</classname> registers install callbacks for any beans that implement the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface. The <filename>bootstrap/profile.xml</filename> configurations include a <classname>ProfileServiceBootstrap</classname> bean that implements the <classname>Bootstrap</classname> interface.
</para>
<indexterm><primary>ProfileService</primary><secondary>bootstrap</secondary></indexterm>
<para>The <classname>org.jboss.system.server.profileservice.ProfileServiceBootstrap</classname> is an implementation of the <classname>org.jboss.bootstrap.spi.Bootstrap</classname> interface that loads the deployments associated with the current profile. The <literal>$PROFILE</literal> is the name of the server configuration profile being loaded and corresponds to the <code>server -c</code> command line argument. The default <literal>$PROFILE</literal> is <literal>default</literal>.</para>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Concepts.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -20,7 +20,7 @@
who is in the cluster and reliably exchanging messages between the cluster
members. JGroups channels with the same configuration and name have the
ability to dynamically discover each other and form a group. This is why
- simply executing <code>run -c all</code> on two Enterprise Web Platform instances on the same network is
+ simply executing <code>run -c production</code> on two Enterprise Web Platform instances on the same network is
enough for them to form a cluster — each Enterprise Web Platform
starts one or more <classname>Channel</classname>s with the same default
configuration, so that they dynamically discover each other and
@@ -31,7 +31,7 @@
<para>
On the same Enterprise Web Platform instance, different services
can create their own <classname>Channel</classname>. In a standard startup
- of the Enterprise Web Platform 5 <literal>all</literal> configuration,
+ of the Enterprise Web Platform 5 <literal>production</literal> configuration,
two different services create a total of four different channels —
JBoss Messaging creates two, and a core general purpose clustering service
known as <classname>HAPartition</classname> creates two more. If you deploy clustered web applications
@@ -42,7 +42,7 @@
purpose caching and cluster wide state replication, and two channels used by JBoss Messaging.
</para>
<para>
- So, if you go to two Enterprise Web Platform 5 instances and execute <code>run -c all</code>,
+ So, if you go to two Enterprise Web Platform 5 instances and execute <code>run -c production</code>,
the channels will discover each other and you'll have a conceptual
<literal>cluster</literal>. It is easy to think of this as a two node
cluster, but it's important to understand that you really have multiple channels,
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Clustering_Guide_Introduction.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -18,7 +18,7 @@
<para>
The JBoss Enterprise Web Platform comes with clustering support out of
- the box, as part of the <literal>all</literal> configuration. The
+ the box, as part of the <literal>production</literal> configuration. The
<literal>all</literal> configuration includes support for the following:
<itemizedlist>
@@ -54,11 +54,6 @@
<para>A distributed cache for JPA/Hibernate entities.</para>
</listitem>
- <listitem>
- <para>A framework for keeping local EJB2 entity caches consistent
- across a cluster by invalidating cache entries across the cluster
- when a bean is changed on any node.</para>
- </listitem>
<!--<listitem>
<para>Distributed JMS queues and topics via JBoss Messaging.</para>
@@ -120,14 +115,14 @@
<para>If you want to run multiple
JBoss Enterprise Web Platform instances on a single server, you can either install the
full JBoss distribution onto multiple locations on your filesystem,
- or you can simply make copies of the <literal>all</literal>
+ or you can simply make copies of the <literal>production</literal>
configuration. For example, assuming the root of the JBoss distribution
was unzipped to <filename>/var/jboss</filename>, you would:</para>
<programlisting>
$ cd /var/jboss/server
-$ cp -r all node1
-$ cp -r all node2</programlisting>
+$ cp -r production node1
+$ cp -r production node2</programlisting>
</listitem>
<listitem>
@@ -216,7 +211,7 @@
<title>Launching a JBoss Enterprise Web Platform Cluster</title>
<para>The simplest way to start a JBoss server cluster is to start
several JBoss instances on the same local network, using the
- <code>-c all</code> command line option for each instance. Those
+ <code>-c production</code> command line option for each instance. Those
server instances will detect each other and automatically form a cluster.
</para>
@@ -255,7 +250,7 @@
<para>On node1, to launch JBoss:</para>
<programlisting>
$ cd /var/jboss/bin
-$ ./run.sh -c all -g DocsPartition -u 239.255.100.100 \
+$ ./run.sh -c production -g DocsPartition -u 239.255.100.100 \
-b 192.168.0.101 -Djboss.messaging.ServerPeerID=1</programlisting>
<para>On node2, it's the same except for a different <literal>-b</literal>
@@ -263,11 +258,11 @@
<programlisting>
$ cd /var/jboss/bin
-$ ./run.sh -c all -g DocsPartition -u 239.255.100.100 \
+$ ./run.sh -c production -g DocsPartition -u 239.255.100.100 \
-b 192.168.0.102</programlisting>
<!-- -Djboss.messaging.ServerPeerID=2 -->
- <para>The <literal>-c</literal> switch says to use the <literal>all</literal>
+ <para>The <literal>-c</literal> switch says to use the <literal>production</literal>
config, which includes clustering support. The <literal>-g</literal> switch
sets the cluster name. The <literal>-u</literal> switch sets the multicast
address that will be used for intra-cluster communication. The
@@ -294,7 +289,7 @@
JBoss instances use the same addresses and ServerPeerIDs as in
Scenario 1. The difference from Scenario 1 is that we need to be sure
each Enterprise Web Platform instance has its own work area. So, instead of using
- the <literal>all</literal> config, we are going to use the
+ the <literal>production</literal> config, we are going to use the
<literal>node1</literal> and <literal>node2</literal> configs we
copied from <literal>all</literal> in <!--
<xref linkend="clustering-prep-dualconfig"/>-->the previous section.</para>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Deploy.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -64,7 +64,7 @@
<indexterm><primary>Server Configuration</primary><see>Server Profile</see></indexterm>
<indexterm><primary>Server Profile</primary><secondary>definition</secondary></indexterm>
- <para>The JBoss Enterprise Web Platform ships with six server profiles. You can choose which configuration to start by passing the <code>-c</code> parameter to the server startup script. For instance, the <code>run.sh -c all</code> command would start the server in the <literal>all</literal> profile. Each profile is contained in a directory named <filename>JBOSS_HOME/server/[profile name]/</filename>. You can look into each server profile's directory to see the services, applications, and libraries included in the profile.</para>
+ <para>The JBoss Enterprise Web Platform ships with two server profiles. You can choose which configuration to start by passing the <code>-c</code> parameter to the server startup script. For instance, the <code>run.sh -c production</code> command would start the server in the <literal>production</literal> profile. Each profile is contained in a directory named <filename>JBOSS_HOME/server/$PROFILE/</filename>, where <literal>$PROFILE</literal> represents the profile name. You can look into each server profile's directory to see the services, applications, and libraries included in the profile.</para>
<note><para>The exact contents of the <filename>server/$PROFILE</filename> directory depends on the profile service implementation and is subject to change as the management layer and embedded server evolve.</para></note>
<itemizedlist>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Pooling.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Pooling.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Pooling.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -99,7 +99,7 @@
<section><title>Sticky Transactions</title>
- <para>Transaction stickiness is enabled by default in JBOss Enterprise Web Platform. The <literal><track-connection-by-tx/></literal> flag, which forced a pool connection to be reused throughout a transaction, is deprecated. This is the only supported behavior for local transactions. XA users can explicitly enable interleaving with the <literal><interleaving/></literal> element.</para>
+ <para>Transaction stickiness is enabled by default in JBoss Enterprise Web Platform. The <literal><track-connection-by-tx/></literal> flag, which forced a pool connection to be reused throughout a transaction, is deprecated. This is the only supported behavior for local transactions. XA users can explicitly enable interleaving with the <literal><interleaving/></literal> element.</para>
<!--<section><title>Sticky Transactions</title>
<para>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Transactions.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Transactions.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Transactions.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -11,7 +11,7 @@
components, such as the EJB container, as well as direct use by application
code. It is suitable for coordinating ACID transactions that involve one or
more XA Resource managers, such as databases or message queues.</para>
- <para>Two additional, optional, JBoss Transaction Service modules are also shipped with
+ <!--<para>Two additional, optional, JBoss Transaction Service modules are also shipped with
JBoss Enterprise Web Platform and may be deployed to provide additional functionality if
required. These are:</para>
<itemizedlist>
@@ -50,7 +50,7 @@
transactions created in other JBoss server instances or
non-JBoss containers.</para>
</listitem>
- </itemizedlist>
+ </itemizedlist>-->
</section>
<section>
<title>Configuration Essentials</title>
@@ -408,60 +408,6 @@
<para>You can find more information in the JBoss Transactions documentation, or in the
JBoss Transactions wiki at <ulink url="http://www.jboss.org/community/wiki/JBossTransactions">http://www.jboss.org/community/wiki/JBossTransactions</ulink>.</para>
</section>
- <section>
- <title>Installing JBossTS JTS</title>
- <para>Users who require transaction propagation between business logic in different
- servers will benefit from installing the JTS component. Although the JTS
- does have its own API, it is most commonly accessed via the standard JTA
- classes. In such cases, it's a drop in replacement for the default
- local-only JTA implementation. The necessary implementation classes are
- already in place, it is required only to modify the relevant configuration file to
- move between the JTA and JTS modules. The <filename>docs/examples/transactions/</filename>
- contains a version of the <filename>jbossts-properties.xml</filename>
- file suitable for running the JTS mode. It also contains a <filename>README.txt</filename> file
- detailing the changes necessary to various other files, including the
- <filename>transactions-jboss-beans.xml</filename>. An ant script which will perform these steps
- on your behalf is also included. However, we strongly recommend to consult
- the README file for additional information before running the script, as
- well as backing up any server configuration files which may be changed. Note
- that it is necessary to install the JTS into a server configuration that
- also contains the CORBA ORB service, as the JTS relies on this. We recommend
- the <literal>production</literal> configuration as a starting point for this. The selection of
- distributed JTA (JTS) or local-only JTA (the default) is done at the server
- level. The additional complexity of the JTS
- carries a slight performance overhead, so it is recommended to install the
- JTS only for servers which host applications requiring transaction context
- distribution. Servers running JTA will log:</para>
- <screen>INFO [TransactionManagerService] JBossTS Transaction Service (JTA version - ...)</screen>
- <para>at startup, whereas those running the JTS will log:</para>
- <screen>INFO [TransactionManagerService] JBossTS Transaction Service (JTS version - ...)</screen>
- </section>
- <section>
- <title>Installing JBossTS XTS</title>
- <para>The Web Services transaction component, XTS, may be installed to provide WS-AT
- and WS-BA support for web services hosted in the server. The application is
- packaged as a <filename>.sar</filename> file found in
- <filename>docs/examples/transactions/</filename> and should be
- installed by unpacking this archive into the a new <filename>jbossxts.sar</filename> directory
- which you should create in the <filename>server/$PROFILE/deploy/</filename> directory of a suitable
- server. Consult the <filename>README.txt</filename> in
- <filename>docs/examples/transactions/</filename> for any
- additional deployment information. The server must also be running either
- JBossTS JTA or JTS and JBossWS Native.</para>
- <note>
- <para>XTS is does not work with other JBossWS backends such as CXF.</para>
- </note>
- <para>The default XTS configuration is suitable for most usage and will automatically pick up
- network interface and port binding information from the application server
- configuration. Manual configuration changes are necessary only for
- deployments where applications require use of a transaction coordinator on a
- separate host, for which the XTS documentation should be consulted. The
- directory tree created by unpacking the <filename>jbossxts.sar</filename> file will contain a
- <filename>jbossxts-api.jar</filename>. Developers may link against this <filename>.jar</filename>
- at build time, but should not package it with their applications in order to avoid classloading
- problems. The remaining <filename>.jar</filename> files contain internal implementation classes
- and should not be used directly by application code.</para>
- </section>
<!--<section>
<title>Transaction Management Console</title>
<warning>
Modified: projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml 2010-02-25 01:30:55 UTC (rev 101432)
+++ projects/docs/enterprise/EWP_5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml 2010-02-25 01:55:03 UTC (rev 101433)
@@ -330,7 +330,7 @@
<section>
<title>EJB3 Stateless Session Bean (SLSB)</title>
- <para>The JAX-WS programming model support the same set of annotations on EJB3 stateless session beans as on <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Plain_old_Java_Object_POJO"># Plain old Java Object (POJO)</ulink> endpoints. EJB-2.1 endpoints are supported using the JAX-RPC progamming model.</para>
+ <para>The JAX-WS programming model support the same set of annotations on EJB3 stateless session beans as on <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Plain_old_Java_Object_POJO"># Plain old Java Object (POJO)</ulink> endpoints. <!--EJB-2.1 endpoints are supported using the JAX-RPC progamming model.--></para>
<programlisting role="JAVA">
@Stateless
@Remote(EJB3RemoteInterface.class)
@@ -1749,296 +1749,7 @@
<para>Where users will put the provider JAR is mostly up to them, although with JDK5 the best (and in some cases only) place to have it is in <filename>$JAVA_HOME/jre/lib/ext</filename>. Under Windows there will normally be a JRE and a JDK install of Java. If an installation does not work despite apparently correct installation, it is likely that the provider installation has not been used.</para>
</section>
</section>
- <section>
- <title>XML Registries</title>
- <para>J2EE 5.0 mandates support for Java API for XML Registries (JAXR). Inclusion of a XML Registry with the J2EE 5.0 certified Application Server is optional. JBoss EAP5 ships a UDDI v2.0 compliant registry, the Apache jUDDI registry. We also provide support for JAXR Capability Level 0 (UDDI Registries) via integration of Apache Scout.</para>
- <para>This chapter describes how to configure the jUDDI registry in JBoss and some sample code outlines for using JAXR API to publish and query the jUDDI registry.</para>
- <section>
- <title>Apache jUDDI Configuration</title>
- <para>Configuration of the jUDDI registry happens via an MBean Service that is deployed in the juddi-service.sar archive in the "all" configuration. The configuration of this service can be done in the <filename>jboss-service.xml</filename> of the META-INF directory in the <filename>juddi-service.sar</filename></para>
- <para>Let us look at the individual configuration items that can be changed.</para>
- <variablelist>
- <varlistentry>
- <term>Datasource Configuration</term>
- <listitem>
- <programlisting role="XML"><!-- Datasource to Database -->
-<attribute name="DataSourceUrl">java:/DefaultDS</attribute></programlisting>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Database Tables</term>
- <listitem>
- <para>Defines whether tables should be created on start, dropped on stop, dropped on start, etc.</para>
- <programlisting role="XML"><!-- Should all tables be created on Start-->
-<attribute name="CreateOnStart">false</attribute>
-<!-- Should all tables be dropped on Stop-->
-<attribute name="DropOnStop">true</attribute>
-<!-- Should all tables be dropped on Start-->
-<attribute name="DropOnStart">false</attribute></programlisting>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>JAXR Connection Factory to be bound in JNDI</term>
- <listitem>
- <para>Defines whether the connection factory should be bound, and the binding name.</para>
- <programlisting role="XML"><!-- Should I bind a Context to which JaxrConnectionFactory bound-->
-<attribute name="ShouldBindJaxr">true</attribute>
-
-<!-- Context to which JaxrConnectionFactory to bind to. If you have remote clients, please bind it to the global namespace(default behavior).
-To just cater to clients running on the same VM as JBoss, change to java:/JAXR -->
-<attribute name="BindJaxr">JAXR</attribute></programlisting>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Other common configuration</term>
- <listitem>
- <para>Add authorized users to access the jUDDI registry. (Add a SQL insert statement in a single line)</para>
-<programlisting> <![CDATA[
-Look at the script META-INF/ddl/juddi_data.ddl for more details. Example for a user 'jboss'
-
-INSERT INTO PUBLISHER (PUBLISHER_ID,PUBLISHER_NAME,
-EMAIL_ADDRESS,IS_ENABLED,IS_ADMIN)
-VALUES ('jboss','JBoss User','jboss at xxx','true','true');
-]]> </programlisting>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
- <section>
- <title>JBoss JAXR Configuration</title>
- <para>In this section, we will discuss the configuration needed to run the JAXR API. The JAXR configuration relies on System properties passed to the JVM. The System properties that are needed are:</para>
-<programlisting> <![CDATA[
-javax.xml.registry.ConnectionFactoryClass=org.apache.ws.scout.registry.
-ConnectionFactoryImpl
-jaxr.query.url=http://localhost:8080/juddi/inquiry
-jaxr.publish.url=http://localhost:8080/juddi/publish
-scout.proxy.transportClass=org.jboss.jaxr.scout.transport.SaajTransport
-]]> </programlisting>
- <para>Please remember to change the hostname from <literal>localhost</literal> to the hostname of the UDDI service/JBoss Server.</para>
- <para>You can pass the System Properties to the JVM in the following ways:</para>
- <itemizedlist>
- <listitem>
- <para> When the client code is running inside JBoss (maybe a servlet or an EJB). Then you will need to pass the System properties in the <filename>run.sh</filename> or <filename>run.bat</filename> scripts to the java process via the <code>-D</code> option.</para>
- </listitem>
- <listitem>
- <para> When the client code is running in an external JVM. Then you can pass the properties either as <code>-D</code> options to the java process or explicitly set them in the client code(not recommended).</para>
- </listitem>
- </itemizedlist>
-<programlisting> <![CDATA[
-System.setProperty(propertyname, propertyvalue);
-]]> </programlisting>
- </section>
- <section>
- <title>JAXR Sample Code</title>
- <para>There are two categories of API: JAXR Publish API and JAXR Inquiry API. The important JAXR interfaces that any JAXR client code will use are the following.</para>
- <variablelist>
- <varlistentry>
- <term><classname>javax.xml.registry.RegistryService</classname></term>
- <listitem>
- <para>The principal interface implemented by a JAXR provider. A registry client can get this interface from a Connection to a registry. It provides the methods that are used by the client to discover various capability specific interfaces implemented by the JAXR provider.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><classname>javax.xml.registry.BusinessLifeCycleManager</classname></term>
- <listitem>
- <para>This interface is exposed by the Registry Service, and implements the life cycle management functionality of the Registry as part of a business level API. There is no authentication information provided, because the Connection interface keeps that state and context on behalf of the client.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><classname>javax.xml.registry.BusinessQueryManager</classname></term>
- <listitem>
- <para>This interface is exposed by the Registry Service, and implements the business style query interface. It is also referred to as the focused query interface.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>Let us now look at some of the common programming tasks performed while using the JAXR API:</para>
- <formalpara>
- <title>Getting a JAXR Connection to the registry</title>
- <para><programlisting role="JAVA">String queryurl = System.getProperty("jaxr.query.url", "http://localhost:8080/juddi/inquiry");
-String puburl = System.getProperty("jaxr.publish.url", "http://localhost:8080/juddi/publish");
-..
-Properties props = new Properties();
-props.setProperty("javax.xml.registry.queryManagerURL", queryurl);
-props.setProperty("javax.xml.registry.lifeCycleManagerURL", puburl);
-
-String transportClass = System.getProperty("scout.proxy.transportClass", "org.jboss.jaxr.scout.transport.SaajTransport");
-System.setProperty("scout.proxy.transportClass", transportClass);
-
-// Create the connection, passing it the configuration properties
-factory = ConnectionFactory.newInstance();
-factory.setProperties(props);
-connection = factory.createConnection();
-</programlisting></para>
- </formalpara>
- <formalpara><title>Authentication with the registry</title>
-<para><programlisting role="JAVA">
-/**
- * Does authentication with the uddi registry
- */
-protected void login() throws JAXRException
-{
- PasswordAuthentication passwdAuth = new PasswordAuthentication(userid, passwd.toCharArray());
- Set creds = new HashSet();
- creds.add(passwdAuth);
-
- connection.setCredentials(creds);
-}
-</programlisting></para>
- </formalpara>
- <formalpara>
- <title>Save a Business</title>
-<para><programlisting role="JAVA">/**
- * Creates a Jaxr Organization with 1 or more services
- */
-protected Organization createOrganization(String orgname) throws JAXRException
-{
- Organization org = blm.createOrganization(getIString(orgname));
- org.setDescription(getIString("JBoss Inc"));
- Service service = blm.createService(getIString("JBOSS JAXR Service"));
- service.setDescription(getIString("Services of XML Registry"));
- //Create serviceBinding
- ServiceBinding serviceBinding = blm.createServiceBinding();
- serviceBinding.setDescription(blm.createInternationalString("Test Service Binding"));
-
- //Turn validation of URI off
- serviceBinding.setValidateURI(false);
- serviceBinding.setAccessURI("http://testjboss.org");
- ...
- // Add the serviceBinding to the service
- service.addServiceBinding(serviceBinding);
-
- User user = blm.createUser();
- org.setPrimaryContact(user);
- PersonName personName = blm.createPersonName("Anil S");
- TelephoneNumber telephoneNumber = blm.createTelephoneNumber();
- telephoneNumber.setNumber("111-111-7777");
- telephoneNumber.setType(null);
- PostalAddress address = blm.createPostalAddress("111", "My Drive", "BuckHead", "GA", "USA", "1111-111", "");
- Collection postalAddresses = new ArrayList();
- postalAddresses.add(address);
- Collection emailAddresses = new ArrayList();
- EmailAddress emailAddress = blm.createEmailAddress("anil at apache.org");
- emailAddresses.add(emailAddress);
-
- Collection numbers = new ArrayList();
- numbers.add(telephoneNumber);
- user.setPersonName(personName);
- user.setPostalAddresses(postalAddresses);
- user.setEmailAddresses(emailAddresses);
- user.setTelephoneNumbers(numbers);
-
- ClassificationScheme cScheme = getClassificationScheme("ntis-gov:naics", "");
- Key cKey = blm.createKey("uuid:C0B9FE13-324F-413D-5A5B-2004DB8E5CC2");
- cScheme.setKey(cKey);
- Classification classification = blm.createClassification(cScheme, "Computer Systems Design and Related Services", "5415");
- org.addClassification(classification);
- ClassificationScheme cScheme1 = getClassificationScheme("D-U-N-S", "");
- Key cKey1 = blm.createKey("uuid:3367C81E-FF1F-4D5A-B202-3EB13AD02423");
- cScheme1.setKey(cKey1);
- ExternalIdentifier ei = blm.createExternalIdentifier(cScheme1, "D-U-N-S number", "08-146-6849");
- org.addExternalIdentifier(ei);
- org.addService(service);
-
- return org;
-}</programlisting></para>
- </formalpara>
- <formalpara>
- <title>Query a Business</title>
-<para><programlisting role="JAVA">/**
- * Locale aware Search a business in the registry
- */
-public void searchBusiness(String bizname) throws JAXRException
-{
- try
- {
- // Get registry service and business query manager
- this.getJAXREssentials();
-
- // Define find qualifiers and name patterns
- Collection findQualifiers = new ArrayList();
- findQualifiers.add(FindQualifier.SORT_BY_NAME_ASC);
- Collection namePatterns = new ArrayList();
- String pattern = "%" + bizname + "%";
- LocalizedString ls = blm.createLocalizedString(Locale.getDefault(), pattern);
- namePatterns.add(ls);
-
- // Find based upon qualifier type and values
- BulkResponse response = bqm.findOrganizations(findQualifiers, namePatterns, null, null, null, null);
-
- // check how many organisation we have matched
- Collection orgs = response.getCollection();
- if (orgs == null)
- {
- log.debug(" -- Matched 0 orgs");
- }
- else
- {
- log.debug(" -- Matched " + orgs.size() + " organizations -- ");
-
- // then step through them
- for (Iterator orgIter = orgs.iterator(); orgIter.hasNext();)
- {
- Organization org = (Organization)orgIter.next();
- log.debug("Org name: " + getName(org));
- log.debug("Org description: " + getDescription(org));
- log.debug("Org key id: " + getKey(org));
- checkUser(org);
- checkServices(org);
- }
- }
- }
- finally
- {
- connection.close();
- }
-}
-</programlisting></para>
- </formalpara>
- <para>For more examples of code using the JAXR API, refer to the resources in the Resources Section.</para>
- </section>
- <section>
- <title>Troubleshooting</title>
- <qandaset>
- <qandaentry>
- <question><para>I cannot connect to the registry from JAXR.</para></question>
- <answer><para>Check the inquiry and publish url passed to the JAXR <classname>ConnectionFactory</classname>.</para></answer>
- </qandaentry>
- <qandaentry>
- <question><para>I cannot connect to the jUDDI registry.</para></question>
- <answer><para>Check the jUDDI configuration and see if there are any errors in the server log. Remember that the jUDDI registry is available only in the <literal>production</literal> configuration.</para></answer>
- </qandaentry>
- <qandaentry>
- <question><para>I cannot authenticate to the jUDDI registry.</para></question>
- <answer><para>Check that you have added an authorized user to the jUDDI datavase, as described earlier in this chapter.</para></answer>
- </qandaentry>
- <qandaentry>
- <question><para>I would like to view the SOAP messages in transit between the client and the UDDI Registry.</para></question>
- <answer><para>Use the <application>tcpmon</application> tool <ulink url="http://tcpmon.dev.java.net/">http://tcpmon.dev.java.net/</ulink> to view the messages in transit.</para></answer>
- </qandaentry>
- </qandaset>
- </section>
- <section>
- <title>Resources</title>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url="http://java.sun.com/webservices/jaxr/learning/tutorial/index.html">JAXR Tutorial and Code Camps</ulink>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://java.sun.com/j2ee/1.4/docs/tutorial/doc/">J2EE 1.4 Tutorial</ulink>
- </para>
- </listitem>
- <listitem>
- <para>
- <ulink url="http://www.amazon.com/exec/obidos/ASIN/0321146182">J2EE Web Services by Richard Monson-Haefel</ulink>
- </para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
- </section>
+
<section>
<title>JBossWS Extensions</title>
<para>This section describes proprietary JBoss extensions to JAX-WS.</para>
More information about the jboss-cvs-commits
mailing list