| - |
|
This document describes the additional setup steps required for UD6 and Polyserver on Windows.
It is not necessary to use polyserver/userver to use UD6/CMtool Driver. In some environments, getting the best performance from the UD6/CMtool Driver may involve the use of Polyserver/Userver. Ask your support or sales representative for more information if required.
If you require information about setting up UD6 and Polyserver on Unix, please refer to the UD6/CMtool Driver Installation Guide for Unix (available as a PDF).
Instructions for Uniface 8 userver are very similar to the Polyserver setup, but some details may vary.
NOTE: You cannot use the evaluation version of UD6/CMtool Driver with Polyserver.
Polyserver is a part of the Uniface suite that separates database access from the client.
Typically Polyserver is installed on the same server as the database resides and the database drivers are installed on the server rather than the client. The Uniface client has the Polyserver driver inbuilt.
UD6/CMtool Driver works with Polyserver exactly the same way. Instead of installing UD6 on the client, it is installed on the server. The Unfiace clients access the UD6 repository via Polyserver.
Polyserver setup can be complex and daunting. March Hare strongly suggest that you successfully set up UD6 on a client, and Polyserver with another database (such as SOLID) before attempting a UD6 Polyserver Installation.
Alter the default Polyserver INI file (eg: c:\psys72\bin\psys.ini) to reference the UD6 DLL. Eg:
[uniface_dlls]
demandload=zsecintc.dll,...,ud6.dll
Determine which is the correct ASN file, either the specified ASN or psys\psys.asn.
The ASN file which a particular polyserver uses is set in the psys.ini file. Eg:
[default]
Polyserver=c:\psys72\bin\psv.exe
Solid=c:\psys72\bin\psv.exe /asn=c:\users\psv\solid.asn
Make the same ASN file changes to this file as you would for a client using UD6.
The settings will vary depending on whether you are using UD6 Option Pack and / or National Language Support.
Here is an example:
[SETTINGS]
$MAXFILES=2048
[PATHS]
$DEF $DEF
$UUU $DEF
$IDF $UD6
$SYS $DEF
[ENTITIES]
;
; Don’t store temporary data in XML
USTMP.DICT $uuu:USTMP.*
UAPLLST.DICT $uuu:UAPLLST.*
UGCROSS.DICT $uuu:UGCROSS.*
USIMPKW.DICT $uuu:USIMPKW.*
USSPCKW.DICT $uuu:USSPCKW.*
;
; Improve performance by leaving these entities out
USIPARM.DICT $uuu:USIPARM.*
USILINK.DICT $uuu:USILINK.*
;
; Final catch-all for IDF dictionary
*.dict $idf:\ud6data\sources\other.dir\*.*
[DRIVER_SETTINGS]
USYS$UD6_PARAMS = config c:\psys72\bin\
The current working directory of the Polyserver can often be difficult to determine, so March Hare recommend usnig a literal path in the "catch all" (*.dict above) and also in the UD6/CMtool Driver joins configuration fiel.
Here is a partial example:
UFORM:ULABEL:ULABEL::\ud6data\sources\components.dir\*
UXGROUP:UFORM:ULABEL,UBASE::UFORM
.
.
The Client ASN file must specify the Polyserver address, port and name to connect to, and direct the Uniface source code to the appropriate Path:
[PATHS]
$UD6 TCP:10.0.0.2+12000|Administrator|xxxx|Polyserver
$IDF $UD6
[ENTITIES]
;
; Don’t store temporary data in XML
USTMP.DICT $uuu:USTMP.*
UAPLLST.DICT $uuu:UAPLLST.*
UGCROSS.DICT $uuu:UGCROSS.*
USIMPKW.DICT $uuu:USIMPKW.*
USSPCKW.DICT $uuu:USSPCKW.*
;
; Improve performance by leaving these entities out
USIPARM.DICT $uuu:USIPARM.*
USILINK.DICT $uuu:USILINK.*
;
; Final catch-all for IDF dictionary
*.dict $idf:\ud6data\sources\other.dir\*.*
Windows Polyserver can be ran in "debugging" mode from the server:
c:
cd \psys72\bin
ptcpwnt /dbg
Guide to Installing UD6/CMtool driver.
UD6 Troubleshooting Guide
How the driver works (includes a section on the file format)
How to use the driver with a configuration management solution
How to migrate from UVCS
How to use the driver to load CSV files with LONG fields
Using UD6 for EDI/XML Data Interchange
National Language Support in UD6/CMtool.
Where to get more information
How to get support
| $Revision: 1.6 $ $Date: 2011/02/28 02:56:32 $ | [go to top] |