BEA Logo BEA WebLogic Collaborate Release 1.0

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

   WebLogic Collaborate Doc Home   |   Getting Started   |   Previous Topic   |   Next Topic   |   Contents   |   Index

XML Tools Packaged with the WebLogic Collaborate Software

 

WebLogic Collaborate includes the following third-party XML tools designed to assist you with XML:

 


Extensibility XML Authority

Extensibility XML Authority enables the development and deployment of e-business grammars for your company and trading partners. XML Authority provides a comprehensive design environment that accelerates the creation, conversion, and management of XML schemas. The XML Authority graphical environment provides you with a powerful tool to help create e-business infrastructures.

You typically use XML Authority to create the XML schemas (or DTDs) for documents that are sent or received. You place the schemas created with XML Authority into the c-hub repository. The URL has the following syntax:

file://path/file

For example:

file://D:/WLCollaborate/examples/rosettanet/PIP3A2/supplier.xml

 


Extensibility XML Instance

Extensibility XML Instance is a schema-driven data editing product that helps you create, edit, and manage data-oriented XML documents, messages, and configuration files. XML Instance includes the following features:

The WebLogic Collaborate installation procedure provides customized views of the Enabler.xml file based on the DTDs provided by BEA. (As part of the installation procedure, the EnablerConfig.dtd.xip file is copied into the XI/presentations directory.) These views make it easy to enter the attributes for most elements on a single line.

You typically use XML Instance to edit the Enabler.xml file's URL files for the c-enabler.

When you edit the enabler.xml file in the XML instance tool, be sure to use the provided enabler.dtd file so that XML Instance can verify that the changes you make conform to the DTD. For example, if you change or create a new enabler.xml file:

  1. Start the XML Instance tool.

  2. Choose Set Schema on the tool bar.

  3. Load in the DTD.

You can use XML Instance to edit any elements in any of the XML files you create. XML Instance also makes it easy to edit the data in the example RosettaNet PIP3A2 documents.

 


Apache XML Parser

One main use of the Apache XML parser for developers of WebLogic Collaborate applications is to create, modify, read, navigate, and validate XML documents via the standard level 1 DOM API.

For example, an application can create a DOM tree and pass it to the Conversation.publish() method of the c-enabler API (see the Enabler API Javadoc more details). When a c-enabler receives a message from the c-hub, the WebLogic Collaborate messaging service calls the registered conversation handler by passing the business document of the message as a DOM object. The application uses the DOM API, provided by the Apache parser, to extract information from the DOM tree.

 


Apache Xpath and XSLT

You use XPath as the format of publish-side filters in WebLogic Collaborate. You can use XSLT to transform one XML document to another.

For example, a company is using WebLogic Collaborate to collaborate with its trading partners through standard RosattaNet PIPs and the corresponding XML documents. Internally the company uses one XML document format to interface to its inventory control application. XSLT can be used by the company to transform the RosettaNet messages to the format required by the inventory control application. The company's developers can write XSLT stylesheets that define the transformation, and the XSLT engine is invoked at run time by passing in the RosettaNet document and the stylesheet. The engine produces the transformed document that can be presented directly to the inventory control application.