83 lines
5.2 KiB
HTML
83 lines
5.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
<!DOCTYPE html
|
||
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html lang="en-us" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow" />
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<meta name="DC.Type" content="reference" />
|
||
|
<meta name="DC.Title" content="Requirements for using XPCML" />
|
||
|
<meta name="abstract" content="The Extensible Program Call Markup Language (XPCML) has the same workstation Java virtual machine requirements as the rest of the IBM Toolbox for Java." />
|
||
|
<meta name="description" content="The Extensible Program Call Markup Language (XPCML) has the same workstation Java virtual machine requirements as the rest of the IBM Toolbox for Java." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzahhxpcmlmain.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rzahhxpcmlrequire" />
|
||
|
<meta name="DC.Language" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
<title>Requirements for using XPCML</title>
|
||
|
</head>
|
||
|
<body id="rzahhxpcmlrequire"><a name="rzahhxpcmlrequire"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Requirements for using XPCML</h1>
|
||
|
<div><p>The Extensible Program Call Markup Language (XPCML) has the same
|
||
|
workstation Java™ virtual machine requirements as the rest of the IBM<sup>®</sup> Toolbox
|
||
|
for Java. </p>
|
||
|
<div class="section"><p> For more information, see the following page:</p>
|
||
|
<blockquote><a href="rzahnm0403.htm#rzahnm0403">Workstation requirements for running IBM Toolbox for Java applications</a></blockquote>
|
||
|
<p>In addition, using XPCML includes requirements
|
||
|
for the XML schema file, XML parser, and Extensible Stylesheet Language Transformation
|
||
|
(XSLT) processor:</p>
|
||
|
</div>
|
||
|
<div class="section"><h4 class="sectiontitle">XML schema file</h4><p>Your XPCML documents must know the
|
||
|
location of the file that contains the schema. The default schema for IBM Toolbox
|
||
|
for Java is
|
||
|
xpcml.xsd, which resides within the jt400.jar file.</p>
|
||
|
<p>To use the default
|
||
|
schema, extract xpcml.xsd from jt400.jar, then place the file in a suitable
|
||
|
location. The following procedure shows one way that you can extract the .xsd
|
||
|
file on a workstation.</p>
|
||
|
<div class="p"><strong>Extract the xpcml.xsd schema file</strong><ul><li>Start a command line session in the directory that contains jt400.jar</li>
|
||
|
<li>Use the following command to extract the .xsd file:<pre>jar xvf jt400.jar com/ibm/as400/data/xpcml.xsd</pre>
|
||
|
</li>
|
||
|
</ul>
|
||
|
</div>
|
||
|
<div class="note"><span class="notetitle">Note:</span> If you do not run the previous command from the directory that
|
||
|
contains jt400.jar, you can specify a fully qualified path to jt400.jar.</div>
|
||
|
<p> You
|
||
|
can place the default schema file (or any schema file) in any directory.
|
||
|
The only requirement is that you specify the location of the schema file by
|
||
|
using the xsi:noNamespaceSchemaLocation attribute in the <xpcml> tag. </p>
|
||
|
<p>You
|
||
|
can specify the location of the schema as a file path or as a URL.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> Although
|
||
|
the following examples use xpcml.xsd as the schema file, you can specify any
|
||
|
schema that extends xpcml.xsd.</div>
|
||
|
<ul><li>To specify the same directory as the XPCML file, use xsi:noNamespaceSchemaLocation='xpcml.xsd'</li>
|
||
|
<li>To specify a fully qualified path: xsi:noNamespaceSchemaLocation='c:\myDir\xpcml.xsd'</li>
|
||
|
<li>To specify a URL: xsi:noNamespaceSchemaLocation='http://myServer/xpcml.xsd'</li>
|
||
|
</ul>
|
||
|
<p>To see an HTML version of the xpcml.xsd file, see the following page:</p>
|
||
|
<blockquote><a href="rzahhxpcmlschemaxsd.htm">Schema xpcml.xsd file</a></blockquote>
|
||
|
</div>
|
||
|
<div class="section"><h4 class="sectiontitle">XML parser and XSLT processor</h4><p>At run-time, you must
|
||
|
include an XML parser and an XSLT processor in your CLASSPATH environment
|
||
|
variable. For more information, see the following page:</p>
|
||
|
<blockquote><a href="rzahhxmlparserxslprocessor.htm">XML parser and XSLT processor</a></blockquote>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahhxpcmlmain.htm" title="Extensible Program Call Markup Language (XPCML) enhances the functionality and usability of the Program Call Markup Language (PCML) by offering support for XML schemas. XPCML does not support serialization, so unlike PCML, you cannot serialize an XPCML document.">Extensible Program Call Markup Language</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|