[jboss-svn-commits] JBL Code SVN: r36514 - labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Mon Jan 10 19:14:47 EST 2011
Author: dlesage
Date: 2011-01-10 19:14:47 -0500 (Mon, 10 Jan 2011)
New Revision: 36514
Modified:
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Author_Group.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuration.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuring_WebService_Integration.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Contract_Publishing.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Monitoring_and_Management.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Revision_History.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/ServiceBindingManager.xml
labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/jBPM_Console.xml
Log:
SOA-2155 Merges from product doc QE process.
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Author_Group.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Author_Group.xml 2011-01-10 23:59:00 UTC (rev 36513)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Author_Group.xml 2011-01-11 00:14:47 UTC (rev 36514)
@@ -5,7 +5,7 @@
]>
<authorgroup>
- <author>
+ <author>
<firstname>JBoss ESB Development Team</firstname>
<surname>with Community Contributions</surname>
</author>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuration.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuration.xml 2011-01-10 23:59:00 UTC (rev 36513)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuration.xml 2011-01-11 00:14:47 UTC (rev 36514)
@@ -3,8 +3,7 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "Administration_Guide.ent">
%BOOK_ENTITIES;
]>
-
-<chapter id="configuration">
+<chapter>
<title>
Configuration
</title>
@@ -15,7 +14,7 @@
Service Bus</application> for use in financial institutions, banks,
telecommunications companies and other large
corporations. This chapter explains how to configure the software after
- the reader has followed the initial installation steps in the
+ the reader has followed the initial installation steps found in the
<emphasis>Getting Started Guide</emphasis>.
</para>
@@ -83,7 +82,7 @@
</listitem>
<listitem>
<para><firstterm>content-based routing</firstterm> (through
- <application>JBoss Rules</application>)</para>
+ JBoss Rules, XPath, Regex and Smooks)</para>
</listitem>
<listitem>
<para>integration with the <application>JBoss Business Process
@@ -94,6 +93,7 @@
</section>
+
<section id="standalone_server">
<title>
Stand-Alone Server
@@ -120,11 +120,7 @@
JBoss currently supports the use of a number of
<firstterm>Java Message Service</firstterm> applications in
conjunction with the <application>JBoss Enterprise SOA
- Platform</application>. These applications are
- <application>JBoss Messaging</application>, <application>Tibco
- 5.0</application> and <application>IBM MQ 6.0.2</application>.
- The following sections instruct the reader how to configure
- each of these.
+ Platform</application>. These can be found at <ulink url="http://www.jboss.com/products/platforms/soa/supportedconfigurations/" />. Each is discussed, in turn, below.
</para>
<warning>
@@ -213,7 +209,7 @@
</para>
</important>
-
+</section>
<section>
<title>
Max Sessions Per Connection
@@ -314,7 +310,7 @@
be found in the <filename>lib/ext</filename> directory.
</para>
</note>
-
+ </section>
<section id="JBossMessagingClusteringConfiguration">
<title>
JBoss Messaging Clustering Configuration
@@ -337,8 +333,8 @@
</note>
</section>
-</section>
+
<section id="active_mq">
<title>
@@ -387,57 +383,104 @@
</important>
<para>
- From a JBoss ESB perspective, configuring Websphere MQ providers is simple enough. You have 2 options:
+ There are two ways in which to do configure a Websphere MQ provider:
+ </para>
+
<orderedlist>
<listitem><para>As a JCA Provider using the Websphere MQ JCA Adapter through the <jms-jca-provider> configuration.</para></listitem>
+
<listitem><para>As a Standard JMS Provider through the <jms-provider> configuration.</para></listitem>
</orderedlist>
- </para>
+
+</section>
+
<section id="websphere_mq_series_providers">
<title>
Websphere MQ JMS Provider Configurations
</title>
+
<para>
The following is an example of a <jms-jca-provider> configuration:
</para>
- <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jca-provider-rar-config-01.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
+
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jca-provider-rar-config-01.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ </programlisting>
+
<para>
- The above configuration is an example of how to configure a gateway provider through the <jms-jca-provider> configuration. The main
- things to note of specific relevance to Websphere MQ are:
+ The above configuration is an example of how to configure a
+ gateway provider through the <jms-jca-provider>
+ configuration. The main things to note of specific relevance to
+ Websphere MQ are:
+ </para>
+
+
<orderedlist>
- <listitem><para>The adapter name "wmq.jmsra.rar". This rar file must be present in the server's deploy folder.</para></listitem>
- <listitem><para>The initial context factory "com.ibm.mq.jms.context.WMQInitialContextFactory".</para></listitem>
- <listitem><para>The "queueManager" configuration in the <activation-config>. You need to configure a Queue Manager
- in your Websphere MQ installation. All your Queues (all destinations) are configured under your Queue Manager.</para></listitem>
- <listitem><para>The "channel" configuration in the <activation-config>. A Queue Manager can be configured with
- a number of different types of "channels". Clients connect through "Server Connection" channels. A default server connection channel
- is added as part of the Websphere MQ installation ("SYSTEM.DEF.SVRCONN"), but it is a good idea to specify your own dedicated channels, especially if
- you are using extended (XA) transations. More on this later.
- </para></listitem>
- <listitem><para>The "transportType" configuration in the <activation-config>. Websphere MQ supports transport types "Client" and "Binding".</para></listitem>
+ <listitem><para>The adapter name "wmq.jmsra.rar". This rar
+ file must be present in the server's deploy
+ folder.</para></listitem> <listitem><para>The initial
+ context factory
+ "com.ibm.mq.jms.context.WMQInitialContextFactory".</para></listitem>
+ <listitem><para>The "queueManager" configuration in the
+ <activation-config>. You need to configure a Queue
+ Manager in your Websphere MQ installation. All your Queues
+ (all destinations) are configured under your Queue
+ Manager.</para></listitem> <listitem><para>The "channel"
+ configuration in the <activation-config>. A Queue
+ Manager can be configured with a number of different types
+ of "channels". Clients connect through "Server Connection"
+ channels. A default server connection channel is added as
+ part of the Websphere MQ installation
+ ("SYSTEM.DEF.SVRCONN"), but it is a good idea to specify
+ your own dedicated channels, especially if you are using
+ extended (XA) transations. More on this later.
+ </para></listitem> <listitem><para>The "transportType"
+ configuration in the <activation-config>. Websphere
+ MQ supports transport types "Client" and
+ "Binding".</para></listitem>
</orderedlist>
- </para>
+
<para>
- We said that the above <jms-jca-provider> configuration is an example of how to configure a gateway provider. That's not strictly true; it's just
- a provider configuration. It is the <jms-listener> configuration that determines the gateway/message-aware characteristics of a listener. What is true
- to say about the above configuration however is that, as far as Websphere MQ is concerned, it is only of use as a provider to a gateway listener i.e. would not
- work as a Message-Aware listener for Websphere MQ . This is because it does not specify an appropriate JNDI Provider URL (that can be used by the ServiceInvoker)
- for routing ESB messages to the destinations (buses) defined on the provider. Note the <activation-config> configures the JCA adapter for getting messages
- from the destinations. It does not specify any information used for delivering messages to the destinations. An example of a configuration that could be used as
- a provider for a Message-Aware listener would be:
+ Although it was stated that the above <jms-jca-provider>
+ configuration is an example of how to configure a gateway
+ provider, that is not strictly true; it is just a provider
+ configuration. It is the <jms-listener> configuration
+ that determines the gateway/message-aware characteristics of a
+ listener. However, it is true to say that, as far as Websphere
+ MQ is concerned, it is only of use as a provider to a gateway
+ listener. In other words, it would not work as a Message-Aware
+ listener for Websphere MQ . This is because it does not specify
+ an appropriate JNDI Provider URL (that can be used by the
+ ServiceInvoker) for routing ESB messages to the destinations
+ (buses) defined on the provider. Note the
+ <activation-config> configures the JCA adapter for
+ getting messages from the destinations. It does not specify any
+ information used for delivering messages to the destinations.
+ An example of a configuration that could be used as a provider
+ for a Message-Aware listener would be:
</para>
+
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jca-provider-rar-config-02.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
<para>
- Creating a standard JMS provider configuration is more or less the same:
+ Creating a standard JMS provider configuration is a similar process:
</para>
+
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jms-provider-config-01.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+
<para>
- What you should note with the standard provider is that there's no adapter and <activation-config> configurations. Listeners getting messages from the destinations defined in
- a standard provider do not use a JCA Adapter Inflow to receive the messages. Instead, they need to use JNDI to lookup the destination and get the messages. This
- effectively means that for Websphere MQ, the jndi-URL must always be specified (remember that for JCA it is only required for destinations that service a Message-Aware
- listener).
+ Note that, with the standard provider, there is no adapter nor
+ any <activation-config> configurations. Listeners
+ receiving messages from the destinations defined in a standard
+ provider do not use a JCA Adapter Inflow to obtain the messages.
+ Instead, they need to use JNDI to find the destination and
+ obtain the messages. This means that, for Websphere MQ, the
+ jndi-URL must always be specified (remember that for JCA it is
+ only required for destinations that service a Message-Aware
+ listener).
</para>
- </section>
+</section>
+
<section id="websphere_mq_series_jmsrouter">
<title>
JMSRouter Configuration for Websphere MQ
@@ -446,7 +489,9 @@
The following is an example of a JMSRouter configuration for routing messages to Websphere MQ from inside an ESB action pipeline:
</para>
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/wmq-jmsrouter-config.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- </section>section>
+ </section>
+
+
<section id="websphere_mq_series_xa_transactions">
<title>
@@ -512,7 +557,7 @@
</title>
<para>
- This is done programmatically by calling the "enableTrace" static method on the com.ibm.mq.MQEnvironment class.
+ Do this by calling the "enableTrace" static method on the com.ibm.mq.MQEnvironment class.
</para>
</section>
@@ -536,20 +581,20 @@
</listitem>
<listitem>
<para>
- If using <systemitem>XA connections</systemitem>, be sure to configure
+ If using <systemitem>XA connections</systemitem>, configure
a dedicated Queue Manager Channel for each component that gets or sets
- messages into a Websphere MQ destination. See earlier section titled
- "Websphere MQ and XA Transactions".
+ messages into a Websphere MQ destination.
</para>
</listitem>
<listitem>
<para>
- Make sure the GET and PUT properties on all your Websphere MQ destinations
- is not set to Inhibit. This can be set by default when the destination is created
- and results in the ESB not being able to put/get messages.
+ Make sure the GET and PUT properties on each of the Websphere MQ destinations
+ are not set to Inhibit. This can be happen when the destination is created
+ and results in the ESB being unable to obtain put/get messages.
</para>
</listitem>
- <listitem>
+ </orderedlist>
+
<para>
Check that the following items are present on the class-path:
</para>
@@ -590,8 +635,9 @@
</para>
</listitem>
</itemizedlist>
-
- If using the Websphere MQ v7.0 Client jar files you will also need to add the following jar files to your classpath:
+<para>
+ If using the Websphere MQ v7.0 Client JAR files, add the following to the classpath:
+ </para>
<itemizedlist>
<listitem>
<para>
@@ -609,6 +655,7 @@
</para>
</listitem>
</itemizedlist>
+
<note>
<para>
The client jars differ between MQ 5.3 and MQ 6.0. However the
@@ -620,11 +667,11 @@
<warning>
<para>
- The following exception may be encountered when running
+ The following exception may occur if running
<application>Websphere MQ 6.0</application>:
</para>
-<screen>Message: Unable to get a MQ series Queue Manager or Queue Connection. Reason: failed to create connection --javax.jms. JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager</screen>
+<screen>Message: Unable to get a MQ series Queue Manager or Queue Connection. Reason: failed to create connection javax.jms. JMSSecurityException: MQJMS2013: invalid security authentication supplied for MQQueueManager</screen>
<para>
This is a permissions issue. To fix this problem, add the user
@@ -633,12 +680,10 @@
group</systemitem>.
</para>
</warning>
- </listitem>
-</orderedlist>
-
- </section>
-
-</section>
+
+</section>
+
+
<section>
<title>
@@ -742,7 +787,7 @@
<orderedlist>
<listitem>
<para>
- For Red Hat MRG you should set the parameters to:
+ To use Red Hat MRG, set the parameters to:
</para>
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/redhat_mrg.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
@@ -750,7 +795,8 @@
<listitem>
<para>
- In your classpath in your classpath you should have the Apache Qpid qpid-common and qpid-client JARs.
+ Make sure that these
+ JARs are in the class-path:
</para>
<itemizedlist>
@@ -862,11 +908,7 @@
</listitem>
</itemizedlist>
- <note>
- <para>
- We tested with version 0.6.
- </para>
- </note>
+
</listitem>
</orderedlist>
@@ -990,8 +1032,8 @@
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/configuration/jndi_prefixes_property.xmlt" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
-</section>
+
</section>
<section id="ftp_configuration">
@@ -1123,21 +1165,26 @@
</para>
<screen>[ schema]$ ant
-Buildfile: build.xml
+ [groovy] JBoss SOA Platform Database Configuration Script
+ [groovy] ------------------------------------------------
+ [groovy]
+ [groovy] This script is used to configure the SOA platform and all its
+ [groovy] constituent components against a new RDBMS. Deployment scripts
+ [groovy] are currently available for the following databases:
+ [groovy] DB2 9.7, MS SQL 2008, MySQL 5.0, MySQL 5.1, Oracle 10g,
+ [groovy] Oracle 11g, Oracle 11RAC, PostgreSQL 8.2.4, PostgreSQL 8.3.7, PostgreSQL 8.4.x,
+ [groovy] Sybase ASE 15
+ [groovy]
+ [groovy] ** Warnings **
+ [groovy] This script may not work correctly if you have made manual
+ [groovy] changes to the database configuration.
+ [groovy] This script is only intended to do initial configuration.
+ [groovy] It is not intended to be used multiple times.
+ [groovy]
+ [groovy] Which server configuration are you changing?
+ [groovy] all, production, standard, web, minimal,
+ [groovy] default [default]:</screen>
-[echo] JBoss SOA Platform
-[echo] ------------------
-[echo] Database Configuration Script
-[echo]
-[echo] This script is used to configure the SOA platform and all it's
-[echo] constituent components against a new RDBMS. Deployment scripts
-[echo] are currently available for the following databases: MySQL,
-[echo] Oracle9i, PostgresSQL, Oracle10g
-[echo] ------------------
-[echo] NOTICE: THIS SCRIPT MAY NOT WORK CORRECTLY IF YOU HAVE MADE MANUAL
-[echo] CHANGES TO THE DATABASE CONFIGURATION.
-[echo] </screen>
-
</listitem>
<listitem>
<para>
@@ -1146,9 +1193,7 @@
<itemizedlist>
<listitem>
<para>
- the type of database being used. (Only MySQL,
- PostgreSQL, Oracle 9i and Oracle 10g are supported at
- this point in time.)
+ the type of database being used. These can be found at <ulink url="http://www.jboss.com/products/platforms/soa/supportedconfigurations/" />.
</para>
</listitem>
<listitem>
@@ -1184,18 +1229,11 @@
<filename><replaceable>${SOA_ROOT}</replaceable>/tools/schema/build.properties</filename>
file before running the script.
</para>
-
- <important>
- <para>
- Always re-deploy the ESB Management Console
- after configuring the data-source.
- </para>
-
- </important>
+
</listitem>
</orderedlist>
-
+</section>
@@ -1280,9 +1318,7 @@
</listitem>
<listitem>
<para>
- Edit the <filename>persistence.xml</filename>, located in either
- <filename>jbossesb-registry.sar/META-INF/</filename> or
- <filename>jbossesb-registry.sar/juddi_config/META-INF/</filename>.
+ Edit the <filename>jbossesb-registry.sar/META-INF/persistence.xml</filename> file. The
<property>hibernate.dialect</property> property must be set to the type
of database that is going to be used as the data source. (It may, for
example, be
@@ -1323,7 +1359,7 @@
</orderedlist>
</section>
- </section>
+
<section id="Using_a_JSR-170_Message_Store">
<title>
@@ -1340,8 +1376,8 @@
</para>
<para>
- A Java Content Repository implementation is included. It is called
- <application>Apache Jackrabbit</application>. To enable it, follow these steps:
+ Two Java Content Repository implementations are included,
+ <application>Apache Jackrabbit</application> and ModeShape. To enable JackRabbit, follow these steps:
</para>
<orderedlist>
@@ -1424,6 +1460,11 @@
</para>
</listitem>
</orderedlist>
+
+ <para>
+ ModeShape is a new repository that will become the default in the future. To learn how to install and configure it, refer to the <emphasis>Getting Started Guide</emphasis>.
+ </para>
+
</section>
@@ -1635,7 +1676,7 @@
The <application>JBoss Service-Orientated Architecture
Platform</application> includes the <firstterm>Open Web
SSO</firstterm> project (<application>OpenSSO</application>) service
- software. This is used in order to simplify the implementation of a
+ software. Use it to simplify the implementation of a
transparent <firstterm>Single Sign-On</firstterm> service.
</para>
@@ -1645,7 +1686,9 @@
visit this website: <ulink url="http://opensso.dev.java.net" />.
</para>
</note>
+</section>
+
<section id = "OpenSSO_in_Tomcat">
<title>
@@ -1662,7 +1705,7 @@
</para>
<para>
- Details of the deployment issue can be found at <ulink
+ To learn more about the deployment issue, go to <ulink
url="https://jira.jboss.org/jira/browse/SOA-731" />.
</para>
</important>
@@ -1936,8 +1979,5 @@
the SOA Platform to meet your company's needs. The rest of the book explains
day-to-day administration.
</para>
-</section>
-
-
- </section>
+ </section>
</chapter>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuring_WebService_Integration.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuring_WebService_Integration.xml 2011-01-10 23:59:00 UTC (rev 36513)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Configuring_WebService_Integration.xml 2011-01-11 00:14:47 UTC (rev 36514)
@@ -20,7 +20,7 @@
channel supported by the SOA Platform. Read this chapter to
learn how to configure this integration functionality.
</para>
-
+ <!-- REMOVE
<important>
<para>
Ensure that <application>JBossWS 2.0.1.SP2</application> (native)
@@ -35,7 +35,7 @@
more information.
</para>
</important>
-
+ -->
<section>
<!-- This section sourced from http://www.jboss.org/jbossesb/docs/4.7/javadoc/esb/org/jboss/soa/esb/actions/soap/proxy/SOAPProxy.html -->
<title>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Contract_Publishing.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Contract_Publishing.xml 2011-01-10 23:59:00 UTC (rev 36513)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Contract_Publishing.xml 2011-01-11 00:14:47 UTC (rev 36514)
@@ -11,7 +11,7 @@
<para>
Read this chapter to learn how, why and when to use the
- <application>Contract Application</application>.
+ <application>JBoss ESB Service List</application>.
</para>
<para>
@@ -24,32 +24,31 @@
<important>
<para>
- Red Hat is offering the <application>Contract
- Application</application> as a <emphasis>Technical
+ Red Hat is offering the <application>JBoss ESB Service List</application> as a <emphasis>Technical
Preview</emphasis> only at this point in time. It will
be replaced by different technology in a later release.
</para>
</important>
<para>
- The <application>Contract Application</application> provides
+ The <application>JBoss ESB Service List</application> provides
access to this requisite information. To use the application,
launch a web browser and go to this address: <ulink
url="http://127.0.0.1:8080/contract/" />.
</para>
- <figure><title>The Contract Application</title>
+ <figure><title>JBoss ESB Service List</title>
<mediaobject>
<imageobject>
<imagedata fileref="images/contract_publishing/contract_publishing_application.png" />
</imageobject>
- <textobject><phrase>The Contract Application</phrase></textobject>
+ <textobject><phrase>JBoss ESB Service List</phrase></textobject>
</mediaobject>
</figure>
<para>
- The <application>Contract Application</application> groups
+ The <application>JBoss ESB Service List</application> groups
end-points according to the services with which they are
associated. This is known as <firstterm>servicing</firstterm>.
</para>
@@ -81,7 +80,7 @@
<systemitem>action</systemitem> in the
<systemitem>pipeline</systemitem> that can publish contract
information. (If none of the actions can do so, then the
- <application>Contract Application</application> displays the
+ <application>JBoss ESB Service List</application> displays the
words, <screen>Unavailable on Contract</screen>.)
</para>
</listitem>
@@ -125,8 +124,7 @@
<para>
Having read this chapter, the reader
- now knows why and how to use the <application>Contract
- Application</application>.
+ now knows why and how to use the <application>JBoss ESB Service List</application>.
</para>
</section>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Monitoring_and_Management.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Monitoring_and_Management.xml 2011-01-10 23:59:00 UTC (rev 36513)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Monitoring_and_Management.xml 2011-01-11 00:14:47 UTC (rev 36514)
@@ -135,7 +135,8 @@
with both the stand-alone Enterprise Service Bus server and
JBossAS.
</para>
-</note>
+</note>
+ <!-- REMOVED OUTDATED SCREENSHOT
<para>
Here is a a screen-shot of the Console displaying M-Bean
information from each of the Enterprise Service Bus
@@ -154,7 +155,7 @@
</mediaobject>
</figure>
-
+ -->
<section id="services">
<title>
@@ -188,9 +189,9 @@
</para>
</listitem>
</itemizedlist>
-
+ <!-- REMOVED OUTDATED SCREENSHOT
<para>
- Here is a screenshot displaying this functionality:
+ Here is a screenshot that depicts this functionality:
</para>
@@ -202,7 +203,7 @@
<textobject><phrase>A screen-shot displaying services</phrase></textobject>
</mediaobject>
</figure>
-
+ -->
</section>
@@ -221,7 +222,7 @@
failed messages and records the number of processed bytes
and the time/date stamp for each message.
</para>
-
+<!-- REMOVED OUTDATED SCREENSHOT
<figure><title>Monitoring and Management Console Message Counter</title>
<mediaobject>
<imageobject>
@@ -231,7 +232,7 @@
Message Counter</phrase></textobject>
</mediaobject>
</figure>
-
+ -->
</section>
@@ -273,14 +274,14 @@
</para>
</section>
-
+<!-- POSSIBLY REMOVE
<section>
<title>
Alerts
-</title>
+</title> -->
<!-- This following section is derived from Len's blog at http://jbossesb.blogspot.com/2009/11/messagealerts-in-jbossesb-47.html -->
-
+<!--
<para>
Use the <firstterm>Message Alerts</firstterm> feature
(<classname>org.jboss.soa.esb.listeners.message.MessageAlerts</classname>)
@@ -415,7 +416,7 @@
thresholds.
</para>
-</section>
+</section> -->
</section>
<xi:include href="JON_for_SOA.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Revision_History.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Revision_History.xml 2011-01-10 23:59:00 UTC (rev 36513)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/Revision_History.xml 2011-01-11 00:14:47 UTC (rev 36514)
@@ -9,27 +9,82 @@
<simpara>
<revhistory>
- <revision>
- <revnumber>1</revnumber>
- <date>Fri Jul 16 2010</date>
+
+<revision>
+ <revnumber>1.3</revnumber>
+ <date>Thu Dec 23 2010</date>
<author>
<firstname>David</firstname>
<surname>Le Sage</surname>
<email>dlesage at redhat.com</email>
- </author>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Removed Clustered ESB Service. Section 1.3</member>
+ <member>Removed legacy performance tuning information. Chapter 10</member>
+ <member>Added Maximum Sessions per Connection. Section 1.3.1</member>
+ <member>Removed XA connections information. Section 1.3.3</member>
+ <member>Added Oracle configuration information. Section 1.3.4</member>
+ <member>Updated information and screenshots. Chapter 6.</member>
+ <member>Updated for SOA 5.1</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
+
+<revision>
+ <revnumber>1.2</revnumber>
+ <date>Fri Jun 11 2010</date>
<author>
- <firstname>Darrin</firstname>
- <surname>Mison</surname>
- <email>dmison at redhat.com</email>
+ <firstname>David</firstname>
+ <surname>Le Sage</surname>
+ <email>dlesage at redhat.com</email>
</author>
+ <revdescription>
+ <simplelist>
+ <member>SOA 2039 - Instructions for switching databases updated. Section 1.4.9</member>
+ <member>New content - Instructions for using remote JMS providers. Section 9.2.1</member>
+ <member>Updated for SOA 5.0.2</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
+
+<revision>
+ <revnumber>1.1</revnumber>
+ <date>Tue Apr 20 2010</date>
+ <author>
+ <firstname>David</firstname>
+ <surname>Le Sage</surname>
+ <email>dlesage at redhat.com</email>
+ </author>
<revdescription>
<simplelist>
- <member>Initial conversion from OpenOffice ODT files.</member>
+ <member>Updated for SOA 5.0.1</member>
</simplelist>
</revdescription>
</revision>
+
+<revision>
+ <revnumber>1.0</revnumber>
+ <date>Fri Dec 4 2009</date>
+ <author>
+ <firstname>David</firstname>
+ <surname>Le Sage</surname>
+ <email>dlesage at redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Created for Version 5.0</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
+
+
+
</revhistory>
</simpara>
</appendix>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/ServiceBindingManager.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/ServiceBindingManager.xml 2011-01-10 23:59:00 UTC (rev 36513)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/ServiceBindingManager.xml 2011-01-11 00:14:47 UTC (rev 36514)
@@ -16,7 +16,7 @@
central point at which to set the port configurations for every
instance.
</para>
-
+<!-- REMOVE
<note>
<para>
To learn how to use it, study information found in the
@@ -24,8 +24,8 @@
file.
</para>
</note>
+-->
-
<note>
<para>
The <application>JBoss Application Server</application>
Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/jBPM_Console.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/jBPM_Console.xml 2011-01-10 23:59:00 UTC (rev 36513)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Administration_Guide/en-US/jBPM_Console.xml 2011-01-11 00:14:47 UTC (rev 36514)
@@ -88,14 +88,15 @@
</listitem>
</orderedlist>
-<para>
- The configuration files within the appropriate directory should be
- used to replace the active configurations within the jbpm.esb
- directory, remembering to remove the .config suffix from each. It
- should also be noted that only one of the quartz message queue
- service definitions should be used, either jbm-queue-service.xml or
- jbmq-queue-service.xml, depending on which JMS implementation is
- currently in use.
+
+ <para>
+ Replace the active configurations found in the
+ <filename>jbpm.esb</filename> directory with the configuration files
+ found in the appropriate folders. (Remember to remove the
+ <filename>.config</filename> suffix from each.) Note that only one
+ of the Quartz message queue service definitions should be used,
+ either jbm-queue-service.xml or jbmq-queue-service.xml, depending on
+ which JMS implementation is currently in use.
</para>
More information about the jboss-svn-commits
mailing list