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
1. Build and test the XML pipeline. When testing, be sure to use the processors you will be using in your production environment. You specify the processors on the Deployment tab of the Scenario Properties dialog box.
2. Generate and compile Java code for the XML pipeline ( myPipeline.java, for example).
3. Copy the file representing your XML pipeline's transformation and operation components ( .xquery, .xslt, and .xsd, for example) to the target production server.

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
1. If you have not done so already, install the Stylus Studio 2007 XML Deployment Adapters module.
2. Modify the classpath to include the location of the Jar files associated with the Stylus Studio 2007 XML Deployment Adapters module.
3. Open the .java file ( myPipeline.java, for example) and edit the StylusFileFactory.unlockAPI() - this method's argument requires the installation ID of the Stylus Studio 2007 XML Deployment Adapters module.
4. Compile the .java file.

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.

Converting Custom EDI Message Types to XML

Vital and valuable legacy data locked in proprietary EDI files? See how to use DataDirect XML Converters™ custom EDI message type tools to convert nonconformant EDI to XML.

XML to PDF

Convert XML to PDF using Stylus Studio's XML publishing tools - the easiest way to design beautiful document layouts for use in XSL:FO based multi-channel publishing and single source publishing applications.

Text File to XML

Stylus Studio provides several easy-to-use document wizards that allow you to quickly convert text files to XML. Create XML from text and EDI, create XML Schema from EDIFACT, and more!

XML Notepad

XML Notepad simplifies building of XML applications, allowing authors to rapidly build and edit their XML files. With XML Notepad, you can create XML document prototypes quickly, easily, using an intuitive graphical interface.

Stylus Most Wanted

 
Free Stylus Studio XML Training:
W3C Member