• Chapter 1: Getting Started with Stylus Studio®
• Chapter 2: Editing and Querying XML
• Chapter 3: Converting Non-XML Files to XML
• Chapter 4: Working with XSLT
• Chapter 5: Creating XSLT Using the XSLT Mapper
• Chapter 6: Debugging Stylesheets
• Chapter 7: Defining XML Schemas
• Chapter 8: Defining Document Type Definitions
• Chapter 9: Writing XPath Expressions
• Chapter 10: Working with XQuery in Stylus Studio
• Chapter 11: Composing Web Service Calls
• Chapter 12: Accessing Relational Data as XML
• Chapter 13: Building XML Pipelines
  • What is an XML Pipeline?
  • The XML Pipeline Editor
  • Steps for Building an XML Pipeline
  • Planning an XML Pipeline
    • Design Approaches
    • XML Pipeline Components
    • Identifying Resources
    • Deployment Considerations
  • Use Case: Building order.pipeline
  • Working with Nodes
  • Working with the XML Pipeline Diagram
  • Debugging an XML Pipeline
  • Generating Code for an XML Pipeline
  • XML Pipeline Node Properties Reference
• Chapter 14: Publishing XML Data
• Chapter 15: Integrating with Third-Party File Systems
• Chapter 16: Extending Stylus Studio
• Chapter 17: The Stylus Studio Java API
• Chapter 18: Stylus Studio GUI Reference

Home > Online Product Documentation > Table of Contents > Deployment Considerations

Deployment Considerations

When you are finished building and testing your XML pipeline, you will want to generate the code that executes the XML pipeline so that you can incorporate it in an application that uses the XML processing it defines.

In order to do this, you need to understand the environment in which the XML pipeline's application will be run and model that environment in Stylus Studio. For example, your XML pipeline might be required to use a given XML Schema validation engine, or a specific XQuery or FO processor, so you should plan for these requirements when designing your XML pipeline.

You choose the processors you want the components in your XML pipeline to use by specifying the Execution Framework settings on the Deployment page of the Scenario Properties dialog box.

See Specifying an Execution Framework for more information.