Bug 778478 (SOA-968)

Security: Added: Public

p. 7 end of 1.3 - DB config:

The last sentence (about the location of data source definition) is wrong.
The dir is "jbossesb.esb", but not "jbossesb.sar".

So, the right statement is: "The data-source definition can be found in the jbossesb.esb/message-store-ds.xml." 

p. 9: 1.4.1 Step... step 6.
The dir "jboss-messaging" is wrong... it should be "jboss-messaging.sar", so the right statement is:

"Replace deploy/jboss-messaging.sar/hsqldb-persistence-service.xml with..."

Another note.
It should be mentioned, that in case of clustered environment (e.g. all/production configuration of embedded version of soa-p) the replaced file is called "clustered-hsqldb-persistence-service.xml".

p. 9:  1.5. Using a JSR-170... jrc.jndi.path point:

The dir ("jbossesb.sar"), where repository.xml file is located is wrong. The right dir is "jbossesb.esb".

The right statement is: "... based on the repository.xml located in the root of jbossesb.esb. In this case..."

p. 12: 1.8.1 Installing ... OpenSSO in Tomcat, step 6.:

There is wrong path to the server.xml file ("$tomcat/server.xml"), It should be:

 "/opt/tomcat/conf/server.xml"

p. 19: Ch. 4 Default ReplyTo EPR:

"For JMS..." and "For JDBC..." points:
   '_reply' nad '_reply_table' are suffixes (not prefixes).

p. 23: Ch. 6 Monitoring and Management:

"service=<Service-name>..." point is wrong. It should be: "service-name=<Service name> - Displays ..."

p. 29: 7.1 Server mode:

Point 5. ("Bussiness Proccess Definitions"):
Article's headline is on page 29, but body is whole on page 30. I thing that it would be better for a reader to have the headline and the body on the same page...

None of the above issues have been fixed in the docs that hit 4.3 GA

More comments:

1.1
http://wiki.jboss.org/wiki/ConfiguringMultipleJBossInstancesOnOneMachine
----> This has moved to:  http://www.jboss.org/community/docs/DOC-9384

1.2. JMS Providers
The JBoss Enterprise SOA Platform currently supports JBoss Messaging, IBM Websphere MQ Series
(version 5.3 and 6.0) and Tibco EMS as Java Message Service (JMS) providers.   (We only tested with MQ 6 - where did the 5.3 reference come from?)

Each JMSListener and JMSGateway can be configured to use it's own JMS provider so you can use more than one provider in your deployment.   (its)

1.2.5. Tibco Enterprise Message Service (EMS)

TibcoEMS version 4.4.1 has tested with JBoss SOA   (version 5 has been tested too)

1.4. Switching Databases

Why don't we mention the schema tool in this section of the document?  /jboss-esb/tools/schema

<type-mapping>PostgreSQL 7.2</type-mapping>    (We only tested with Postgres 8)

1.7. Clustering and Fail-over support

Furthermore, in not all gateways have been modified to use the ServiceInvoker,    ("not all gateways")

1.8.1. Installing and configuring OpenSSO in Tomcat

(Duplicate text)

JAVA_OPTS="$JAVA_OPTS "-Xmx1G" "-
Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager"
JAVA_OPTS="$JAVA_OPTS "-Xmx1G" "-
Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager"
JAVA_OPTS="$JAVA_OPTS "-Xmx1G" "-
Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager"
-
JAVA_OPTS="$JAVA_OPTS "-Xmx1G" "-
Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager"
Example 1.1. Adding max size to JAVA_OPTS
JAVA_OPTS="$JAVA_OPTS "-Xmx1G" "-
Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager"
Example 1.2. Adding max size to JAVA_OPTS

(We should direct the reader to the opensso quickstart as it also describes the opensso installation process.)

Chapter 5

The Jboss application server documentation     ("JBoss")

Sections 6.1.2 and 6.1.4 are different descriptions of the same information.

6.3 JON for SOA

Existing archives can be deleted by checking them in the list of Child Resources and clicking
DELETE.  (We should also tell the reader that they have to "uninventory" the archive to remove it from the JON management console.)

see the groovy QuickStart at http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossESBQuickStart
----> This has moved to:  http://www.jboss.org/community/docs/DOC-10363

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossESBContentBasedRouting
----> This has moved to:  http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossESBContentBasedRouting

All these items have been updated with the exception of:

1.4. Switching Databases
Why don't we mention the schema tool in this section of the document? /jboss-esb/tools/schema
<type-mapping>PostgreSQL 7.2</type-mapping> (We only tested with Postgres 8) 

The schema tool is not not refered to in the source doc (ESB Admin Guide), that is why it's not here.  Should we create a JIRA for someone to create that content ?

what should the type-mapping be? <type-mapping>PostgreSQL 8</ type-mapping> or <type-mapping>PostgreSQL 8.0</ type-mapping> or something else?

I've added some content in for the schema tool.  Do we still want to include the step-by-step instructions as well.

I think so - the schema tool does this automatically for the user. Let me check with Julian - he owns the tool now - I want to make sure that it handles the clustered configs.

Link: Added: This issue related SOA-965

We can delete the manual steps - SOA-965 handles this.

content updated

Last change verified in 4.3 CP01 CR2 version of the doc.