This section 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 for ActiveX is installed with the Tamino XML Server installation.
Tamino Component Profile for the HTTP Client API for ActiveX |
|
---|---|
Supported Platforms |
All Windows platforms supported by Tamino XML Server. |
Location of Installed Component |
<TaminoInstallDir>\SDK\ActiveXAPI (henceforth called <ActiveXAPIDir>). |
Component Files |
ActiveX controls: In <ActiveXAPIDir> you find the following files:
TaminoX.ocx |
Examples: In <ActiveXAPIDir> you find examples in these subdirectories:
sampleVBXML (in VisualBasic) |
To Work with the HTTP Client API for ActiveX
You need a running Tamino database server to deploy an API. If you
want to access an existing Tamino database, you need to know its URI (such as
http://localhost/tamino/mydb
).
The ActiveX controls TaminoX.ocx and TaminoNonXml.ocx need to be registered after installation.
To register TaminoX.ocx
regsvr32 TaminoX.ocx
To register TaminoNonXml.ocx
regsvr32 TaminoNonXml.ocx
After registration, the HTTP Client API for ActiveX can be found in the list of all available ActiveX controls.
The name of the API for XML data is "Software AG - Tamino DOM Interface". The name of the API for non-XML data is "Software AG - Tamino Non XML Interface".
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