Certain programming layers require converted XML objects to work with the IBM® Content Manager connector.
The layers include:
- Web services
- IBM Content Manager HTTP interface that accepts your XML messages (defined by cmbmessages.xsd) in a SOAP envelope to perform run time operations such as import, export, search, create, update, retrieve, delete, and document routing. The web services automatically wrap and extract the XML messages in the SOAP message, and send them to the XML messaging JavaBean.
- JavaBeans (XML)
- Reusable Java™ classes based on the IBM Content Manager connector XML APIs and the JavaBeans. The XML JavaBeans perform run time operations such as import, export, search, create, update, retrieve, delete, and document routing. In particular, the CMBXMLMessage bean parses all XML messages based on the cmbmessages.xsd schema.
- Schema mapping utility (XML)
- XML conversion tool that can convert a user-defined schema into the storage schema that IBM Content Manager supports.
- IBM Content Manager connector (XML)
- XML application programming interfaces that can import and export data model metadata objects, administrative metadata objects, and data instance objects.
The following figure illustrates how these XML layers relate to the IBM Content Manager connector.
Figure 1. XML services programming
layers
The following flowchart depicts a real-world scenario for communicating with IBM Content Manager through its XML interface:
Figure 2. XML services communication
flowchart
- The XYZ insurance company defines schemas to hold its data, by using application development tools like WebSphere® Application Developer (WSAD) to create them. The company also chooses to store its data in IBM Content Manager as items.
- In an effort to migrate all data to IBM Content Manager, the XYZ insurance company uses the IBM Content Manager XML schema mapping tool to convert its schema to ones that IBM Content Manager can parse, for example, the storage schema.
- The XYZ insurance company, through the XML schema mapping tool, creates the data model definition corresponding to the storage schema; then stores the schema mapping into IBM Content Manager. The XML schema mapping tool internally invokes the ingest() API of the XML services to create the data model definition.
- The XYZ insurance company writes a custom application that uses web services transactions to create, retrieve, update, delete, and route data in IBM Content Manager. The web services layer retrieves the schema mapping and transforms the data; then invokes the XML beans to perform the operation that manages data in the IBM Content Manager.
