Creating a Scenario

This section describes how to create a DB-to-XML scenario.

Naming Scenarios

Stylus Studio supplies a default name, like Scenario0, for example. for new DB-to-XML scenarios. You can accept the default name, but you should consider typing a name that makes it easy to distinguish one scenario from another. See How to Rename a Scenario.

How to Create a Scenario

To create a scenario:
1. Open the DB-to-XML data source editor if it is not already open.
2. Select Create Scenario from the scenario drop-down list at the top of the editor window.

Stylus Studio displays the Scenario Properties dialog box. The name field displays a default scenario name ( Scenario1, for example) in edit mode.

3. Change the default scenario name.
4. Specify the connection settings. See Specifying Connection Settings if you need help with this step.
5. Click OK to save the scenario with the new settings.

Stylus Studio connects to the server specified in the scenario.

Alternative

Use this procedure if the Scenario Properties dialog box is already open.

To create a scenario when the Scenario Properties dialog box is already open:
1. Click New on the Scenario Properties dialog box.

The name field displays a default scenario name ( Scenario0, for example) in edit mode.

2. Change the default scenario name.
3. Specify the connection settings. See Specifying Connection Settings if you need help with this step.
4. Click OK to save the scenario with the new settings.

Stylus Studio connects to the server specified in the scenario.

Using DTD in Java Applications

Learn how to validate XML documents using industry-standard DTD's from within your Java applications using Java DTD components including Apache Xerces and XSV.

Publishing & Printing

It is really hard to get things to look pretty, especially XML. That's why these publishing & printing companies use Stylus Studio to make a Mona Lisa out of data integration. Check out these top companies that are "stunning" with Stylus Studio!

Map between EDIFACT and X12

Anything can be mapped to anything: EDIFACT to X12 or vice-versa, either to XML, and any of those to flat files or other formats. Both the XSLT and XQuery mappers can help bridge complex formats with ease.

Using Relational Data in XML Applications

"Using Relational Data in XML Applications" By Dr. Michael Kay covers an overview of several common use cases and provides insight into the benefits and drawbacks of using the approaches available today including XQuery and SQL/XML.

Stylus Most Wanted

 
Free Stylus Studio XML Training:
W3C Member