Namespace definition, Implementing enterprise metadata discovery classes – IBM WebSphere Adapters User Manual
Page 142
v
Name
– For example, VENDORID
v
Type
– For example, string
v
Cardinality
– 1 or N
v
Required
– Boolean
v
ObjectTypeName
– For cases where an attribute maps to an object for example,
porecord:PORECORD.
v
Max Length
v
– the MetadataObject representing attribute-level application-specific
information.
ImportedNamespace:
ImportedNamespace describes the names that must be imported into the business
object definition.
This class represents the import statement in the XML schema definition. There are
two properties that discovery service must provide:
v
NameSpace – The name that must be imported
v
Location – The location of the file that must be imported
Metadata:
The metadata component describes information about a business object definition
and its attributes.
The business object and attribute level metadata should be modeled using this
component. The discovery service must provide the following information for this
object:
v
Source
– Added in the application-specific information statement. For example,
WBI.
v
NameSpace
– Added to application-specific information clause.
v
Name-value pairs for application-specific information properties (HashMap). –
For example, pasi:Getter value getObjectName.
Namespace definition
The namespace http://www.ibm.com/xmlns/prod/websphere/j2ca is reserved for
XML artifacts produced by or employed by WebSphere Adapters.
Adapters should use http://www.ibm.com/xmlns/prod/websphere/j2ca/
for any adapter-specific artifacts generated during the metadata
import process; for example, http://www.ibm.com/xmlns/prod/websphere/j2ca/
peoplesoft
.
For Business Objects the name of the business object should be appended to the
base name space; for example,http://www.ibm.com/xmlns/prod/websphere/j2ca/
peoplesoft/purchaseorder
.
For ASI schema the target namespace used must be http://www.ibm.com/xmlns/
prod/websphere/j2ca/peoplesoft/metadata
.
Implementing enterprise metadata discovery classes
The following subsections describe the steps and constructs required for
implementing an enterprise metadata discovery instance.
136
WebSphere Adapters: WebSphere Adapter Toolkit User Guide