IBM InfoSphere Master Data Management Collaboration Server, Version 10.0.0

Data components

The data components consist of the XML envelope, XML data for specific functions, attribute types, and persisted user data content.

XML envelope and the data exchange XML structure

The data exchange format is XML, and the data model is based on a single envelope or container that defines the information that is required to process a transaction. The envelope defines the following things:

Header: Defines basic identification of the user who has initiated the session, and also the message identifier to uniquely identify the current interaction. The corresponding user name is also used to map the current portal user to an existing user.

Body: Contains the information that is extracted. This includes the information in the form of item information, and search results for an item. It also contains the command that needs to be invoked on the product. An additional piece of information is the collaboration area information.

Response type: Includes the state of the transaction and whether it was successful.

This envelope is used for constructing the request and response XML, for data exchange between the framework and IBM® InfoSphere® Master Data Management Collaboration Server.

XML data for specific functions

The script documentation provides information about the request and response XML structures for the supported Web services.

Attribute types

The mediator layer uses a set of parsers and generators to parse XML content from InfoSphere MDM Collaboration Server and to generate XML content for InfoSphere MDM Collaboration Server to use. These converters convert data in an XML format to a pre-defined Java™ object, and back. The conversion to a Java object requires the support of a defined set of data types, and data objects. The product defines a set of attributes for its item definition. These attributes are of various types that range from string to number to group attributes. These attribute types and their behavior on the user interface framework side are captured in a set of attribute and attribute type classes. The attributes provide a base that validation, formatting, and rendering functionality can be attached to.

The supported attributes are:

Binary Attribute
Image Attribute
ThumbnailImageAttribute
GroupAttribute
IntegerAttribute
LookupAttribute
TimeZoneAttribute
NumberAttribute
NumberEnumAttribute
PeriodAttribute
RelationshipAttribute
StringAttribute
CurrencyAttribute
DateAttribute
PasswordAttribute
SequenceAttribute
StringEnumAttribute
FlagAttribute
UnSupportedAttribute
URLAttribute
ImageURLAttribute
ThumbnailImageURLAttribute

Data beans for holding InfoSphere MDM Collaboration Server data hold this data in the instances of attribute types.

User data content that is persisted

The application maintains data content for some portlets across user sessions, for example transaction data and search history content are persisted in the system. The transaction IDs are persisted to track the state of transactions. This is maintained in an ASCII file, stored under the Portal_Enablement_WAR\WEB-INF\transDB folder. The file is specific for each user.

Similarly, the search history for item searches that use the advanced search portlet is stored for each user. The search history is stored in a Java Bean, and serialized onto a file when the user's session is completed.

Terms of Use | Feedback

Timestamp