ZimWeb requires a TEMPLATE parameter. It is not optional (see Parameter Template can be Specified for this Procedure). Ability to Handle POST and GET Requests ZimWeb can accept parameters via either a POST request or a GET request (with the parameters in the URL, which means you can bookmark a ZimWeb request or add a…
Leia mais
Installation Here are some additional details about installing ZimWeb. The ZimWeb package ZimWeb is packaged as a WAR (Web Application Archive) file containing the following files: Package Contents example/index.htm Home page for the ZimWeb Example Application. WEB-INF/example/template/*.htm Page templates for the ZimWeb Example Application. WEB-INF/example/xslt/*.xsl XSLT style sheets for the ZimWeb Example Application. WEB-INF/web.xml/ Configuration…
Leia mais
fbarbosafbarbosa182003-01-27T14:37:00Z2003-01-27T14:45:00Z12721552ZIM Technologies12319059.3821 Creating Secure ZimWeb Applications Some key guidelines for creating secure ZimWeb applications include:- Secure access to the ZimWeb Administration servlet so that unpriviledged users cannot access it. The installation instructions for Tomcat (See Installation) show how to reserve it for a given user name and password. Ensure that the client DEBUG facility is…
Leia mais
Execution Error Conditions The execution environment of a Zim client-server application involves products from more than one vendor. This can introduce the potential for additional error situations. For example, if the parameters to the connect command are not specified correctly for the particular installation of the SQL server being used, then the connect command fails…
Leia mais
The benefit of $serverfunction is the ability to code server functions that Zim does not support. Often there are similar functions in Zim and the server, but the mapping is not exact. As a result, the function is not present in the .sql file, forcing Zim to retrieve the entire table and evaluate the where…
Leia mais
Zim Client-Server uses the SQLCPI variable to find the SAM module and the utilities used to import and export objects. Under Windows, the SQLCPI variable is set in the Windows registry and is set to the directory where the SAM software is installed. When running Zim on Windows, ensure that the registry variable SQLCPI is…
Leia mais
In addition to installing Zim and modifying your UNIX operating environment to accommodate the Zim software, you must also set the environment variable “SQLCPI” to represent the directory for SAM files. To define SQLCPI, enter the following command if you are running the Bourne or Korn shells: SQLCPI=/usr/zim; export SQLCPI where zim is the directory…
Leia mais
The Import/Export functions of the Zim Development Center application provides support for the import/export and translation of database object definitions between the Zim and SQL server environments. In particular, Zim EntitySet and data relationship definitions can be exported to the SQL server to create corresponding tables and indexes. Additionally, SQL table definitions can be extracted…
Leia mais
This option is used to import table definitions from the SQL server and to translate them into equivalent Zim definitions. To import SQL definitions into Zim, select the Tools/Import/Objects/From SQL option from the development center main menu. The SQL Definition Import window appears. On this window, choose the ODBC Server as the server from which…
Leia mais
The export facility is used to translate Zim definitions for entity sets and/or data relationships and create them on the designated SQL server. The definitions of the resulting tables (with associated indexes) correspond to each exported Zim EntitySet or data relationship definition. The Zim definitions to be exported are selected from the EntitySets and Relationships…
Leia mais
Portuguese 
English