This document provides information about the contents of this Tamino component and the installation.
Here you will find general information about the API and how to use it.
The Tamino HTTP Client API for JScript is installed with the Tamino XML Server installation.
|
Tamino Component Profile for the HTTP Client API for JScript |
|
|---|---|
|
Supported Platforms |
All Windows platforms that support Microsoft Internet Explorer. |
|
Location of Installed Component |
<TaminoInstallDir>\SDK\JScriptAPI (henceforth called <JScriptAPIDir>) |
|
Component Files |
API JScript file: <JScriptAPIDir>\TaminoLib.js |
|
Examples: <JScriptAPIDir>\examples\SampleChangeCountry.htm |
|
|
Sample Schema |
<TaminoInstallDir>\SDK\JScriptAPI\Documentation\examples\phone\TelephoneSchema.tsd |
|
Sample Data |
<TaminoInstallDir>\SDK\JScriptAPI\Documentation\examples\phone\Telephone.xml |
To work with the HTTP Client API for JScript
You need a running Tamino database server to deploy an API. If you
want to access an existing Tamino database, you must know its URI (such as
http://localhost/tamino/mydb). In the client HTML page, make sure
that it refers correctly to the file TaminoLib.js.
The controls attempt to auto-detect the latest MSXML parser - first
MSXML4 and then MSXML3. This behavior can be overridden. Use the method
UseServerHTTP for the ActiveX controls. Use the SYSTEM
environment variable SAG_NODELEVELUPDATE_MSXML
(MSXML3/MSXML4) for NodeLevelUpdate. It
is recommended to use MSXML3 with NodeLevelUpdate
