![Close [x]](http://dw1.s81c.com/i/c.gif){kind=small}
The Product element
A <Research> element can consist of more than one
product, each referring to an individual research document. Listing 1
shows an example of this required element.
The <Product> element is a sequence: Each
instance of the <Product> element should have
the sequence attribute set to a unique value within
the document. A sequence number starting at 1 is typically used. The
productID is a unique identifier for the research
document being delivered as part of the RIXML string. The
productID is typically constructed by appending the
sequence number to researchID at the root level.
The <StatusInfo> element within the
<Product> element represents the status of the
research. Set statusDateTime to the time at which
this research bundle was prepared for transmission. (This attribute should have
the same value as createDateTime.) The
currentStatusIndicator indicates whether the status
represents the current status of the document: it should be set to
Yes.
The statusType attribute is set to
Released in this particular example. It is possible
for organizations to use multiple <StatusInfo>
instances in the RIXML string. Each instance of the element can represent a
particular phase in the life cycle of research, such as Pending,
Revised, Recalled,
Deleted, Published,
Rebroadcast, and Released.
If you use multiple instances of <StatusInfo> (perhaps to provide a history of
revisions and releases, or a schedule of future releases), you might
indicate which instance represents the current status of the research by
setting currentStatusIndicator="Yes"; in the
other instances of <StatusInfo>, you
set currentStatusIndicator="No".
However, the typical use of RIXML is to separate each transmission into a separate
payload so the processing can be simple at the receiving and transmitting ends.
In other words, when a document is sent with a <StatusInfo>
value of Published, and then revised, the new RIXML
string will only contain a <StatusInfo> of
Revised, and the content has the newly revised document.
It is recommended that the receiver and transmitter manage the different versions
of their documents within their own DMS.
Each <Product> element contains the following four
elements:
<Source>: This element represents the originator of the research, including the organization name, the analyst producing the information, and details of the analyst, such as phone numbers and e-mail addresses.<Content>: This element contains the actual output of research, including the type of output (for example, Word document, spreadsheet) and the document itself.<Context>: This element contains information related to the area of research, including the product focus described above and information about the company on which the research was conducted.<Legal>: This element consists of legal disclaimers regarding the research and the transmission.
For the sake of simplicity, you should have only one instance of these elements within each product.
Table of contents
Next steps from IBM
WebSphere Application Server can leverage its built in Web Services support to expose services to remote consumers in an industry-standard way.
- Try: The no-charge WebSphere Application Server Community Edition is a pre-integrated, lightweight Java 5 application server built on Apache Tomcat and includes built in Web Services support.
- Article: Learn how to use of the JAX-WS programming model to create dispatch and dynamic proxy clients and how to create an asynchronous Web service client.
- Tutorial: This tutorial takes you through the steps to deploy Data Web Services to the WebSphere Application Server Community Edition.
- Demo: This demo shows how to extract and install the IBM Java Platform, Java EE 5 SDK with WebSphere Application Server.
- Buy: WebSphere Application Server - Express
