• 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
  • Use Case: Building order.pipeline
  • Working with Nodes
  • Working with the XML Pipeline Diagram
  • Debugging an XML Pipeline
  • Generating Code for an XML Pipeline
    • Processor Settings and Code Generation
    • Code Generation Settings
    • How to Generate Java Code for an XML Pipeline
    • Compiling Generated Code
    • Deploying Generated Code
      • Overview
      • About the unlockAPI() Method
  • 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 > Deploying Generated Code

Deploying Generated Code

If your XML Pipeline uses Stylus Studio's adapter file system technology - to convert CSV or EDI to XML, or to render relational data as XML, for example - you need to use the Stylus Studio 2007 XML Deployment Adapters package if you wish to deploy your code in any environment on a machine (such as a test or application server) that does not have a Stylus Studio license. The Stylus Studio 2007 XML Deployment Adapters package is purchased and installed separately from the Stylus Studio 2007 XML Enterprise Suite.

Similarly, if you use DataDirect XQuery in your XML pipeline, you must acquire additional licences if you wish to deploy the XML pipeline application.

Write Stylus Studio at stylusstudio@stylusstudio.com, or call 781.280.4488 for more information.

Overview

The process for deploying generated XML pipeline code that uses Stylus Studio's adapter file system technology includes the following steps:

In Stylus Studio

Source files ( .edi and .txt files , for example) need to be copied if they will not be accessible on the deployment platform.

On the Production Server

You can now run the application code independently, or incorporate it in another application on the same server.

About the unlockAPI() Method

The unlockAPI() method is part of the Stylus Studio Custom File System API. This method takes as its argument a Stylus Studio installation ID, one from either Stylus Studio 2007 XML Enterprise Suite, or from the Stylus Studio 2007 XML Deployment Adapter.

The Enterprise Suite installation ID is adequate for testing purposes on your local workstation, but if you want to deploy an XML pipeline that uses Stylus Studio adapters on one or more test or application servers, you need to use the Deployment Adapter installation ID for the unlockAPI() method's argument.