Installing Pervasive DataExchange with No Previous Installation

Installing Pervasive DataExchange with No Previous Installation
Instructions for First-time Installation
This chapter contains procedures for installing Pervasive DataExchange. The chapter contains the following sections:
*
*
*
*
 
Before You Install DataExchange
This section contains information with which you need to be familiar to successfully install Pervasive DataExchange. Before installing Pervasive DataExchange, review the following information:
*
Preparing to Install Pervasive DataExchange. This chapter provides important information including system requirements and platform specific notes that are relevant to your operation.
*
Windows Platform Notes
Be aware of the following conditions.
*
*
Installing Over Windows Terminal Services
Microsoft Terminal Services is a multisession environment that provides remote computers access to Windows-based programs running on a server. (Citrix MetaFrame extends Windows Terminal Services with additional client and server functionality.)
Tip See the Pervasive Software web site for a list of supported environments.
To install DataExchange to a Terminal Server client, you must first modify a registry setting on the Terminal Server client. The default value for the registry setting prevents you from performing Pervasive PSQL administrative functions. You must have administrative authority to install DataExchange.
Use the following steps to modify the registry setting. You must have administrative authority on the Terminal Server client.
Caution Incorrectly editing your computer’s registry can damage the registry. The damage can cause undesirable results, such as your computer not being able to boot. If you do not feel comfortable editing the registry, obtain the services of a qualified technician. Pervasive Software accepts no responsibility for a damaged registry.
*
Note We suggest that you create a backup of your registry before editing the registry. Refer to the online help for your operating system. Look for index entries such as “registry, backing up,” or “emergency repair disk.”
1
Registry Editor opens.
2
HKEY_LOCAL_MACHINE\Software\Pervasive Software\Utilities Interface\Settings\Restricted Access On WTS client
3
Double-click REG_DWORD for the key.
The Edit DWORD Value dialog box opens.
4
5
The REG_DWORD value should read 0x00000000 (0).
6
Note Changing this registry setting to zero grants Pervasive PSQL administrative authority to everyone who has access to the Terminal Server client machine. To restrict Pervasive PSQL administrative authority, you may want to restore the default value of the registry setting after DataExchange is installed. To do this, change the REG_DWORD value back to 1 (see step 4 in To modify the security registry setting on a Terminal Server client).
You may also use regedt32 to change the permissions on the registry key so that only certain users are allowed to modify the key value.
Installing Pervasive DataExchange
You must install Pervasive DataExchange on a machine that contains a Pervasive PSQL Server or Workgroup engine.
Note The Pervasive PSQL database engine is stopped and restarted during the installation of Pervasive DataExchange. If your business requirements prohibit stopping the database engine during certain hours, install DataExchange during an acceptable period.
If the installation fails before the program copies any files to the target installation directory, refer to the installation log file (replinst.log) in the <drive>:\Windows directory.
DataExchange installs a service called the notification agent if the machine contains the Pervasive PSQL Server product. The notification agent is not available if you install DataExchange on a machine with the Pervasive PSQL Workgroup product. See dxagent in Pervasive DataExchange User’s Guide.
*
You will run the installation twice: once on the First Site and once on a Partner Site.
1
*
*
The Welcome window appears.
2
Click Next.
The Software License Agreement appears.
3
The installation asks for a DataExchange license key.
4
*
*
A First Site and a Partner Site use the same key, which is provided on the case of the DataExchange installation CD, the product registration card, and the printed license agreement.
At the end of the evaluation period, the replication engine returns an error when it tries to start. You may apply a license key at any time. See To upgrade an evaluation license.
5
Click Next.
The installation asks you to choose a site type.
Figure 3-1 Site Type
6
*
You will use a First Site to design and configure the replication network. Its components include the administrative utilities and the replication engine.
*
A Partner Site replicates data with the First Site. Its components include the DataExchange administrative utilities and replication engine. You may install a Partner Site before installing a First Site, but you must initialize and configure the replication network from the First Site.
Caution Do not install more than one First Site on a network, or replication conflicts may occur.
7
Click Next, then continue as follows:
*
To install a First Site, click Yes if you have not installed a First Site on your replication network and continue with the next step. Otherwise, click No.
*
8
Click Next.
A dialog appears on which you specify site information.
Figure 3-2 Site Information
Both names default to the host name of your machine.
*
The Site Name identifies your machine on the replication network. The name can be whatever you want. Accept the default or enter a more descriptive site name.
*
The Host Name identifies this machine to the DataExchange Engine. If your machine has a fixed IP address and you prefer to use it, enter it here. If the address is assigned by DHCP, accept the machine host name by default.
9
Click Next.
A summary of installation settings appears.
10
Review the settings and click Next if they are correct. You may click Back to change a setting.
The DataExchange installation process continues, displaying a series of status messages that inform you what action is taking place. Most of the message dialogs contain a progress bar to indicate the amount of time elapsed.
The following types of status messages appear:
*
*
*
*
*
*
At the end of the installation, setup informs you that it is complete and prompts you to view the readme file.
Pervasive Software strongly recommends that you view the readme file for important release notes concerning configuration and use of the product.
11
Click Finish.
12
*
*
If you cleared the View the readme file option, setup exits.
After You Install DataExchange
Pervasive DataExchange Data Synchronization Edition provides different methods to design and deploy a database for replication. The methods involve a variety of decisions, which are explained in Pervasive DataExchange User’s Guide. See Data Synchronization Deployment Models in that guide.
Pervasive PSQL Security
Pervasive PSQL provides security models for Btrieve applications. However, the activated databases created by DXdeploy do not contain security, even if the source database does. You may add security to a replication database if you choose. See Pervasive PSQL Security in Pervasive DataExchange User’s Guide. For more details, see also the chapter on Pervasive PSQL Security in the Pervasive PSQL Advanced Operations Guide.
Common Questions After Installing Pervasive DataExchange
This section contains information that you may have after running the installation program.
Do I Have to Configure Anything in Pervasive Control Center (PCC) for DataExchange?
No. DataExchange requires no special settings in PCC.
Does DataExchange Create Any Log Files?
Yes. See Log Files in Pervasive DataExchange User’s Guide.
How Do I Automate a Scheduled Replication?
See Schedule Tasks in Pervasive DataExchange User’s Guide.
How Do I Get Notified by E-mail for a Replication Failure?
See Pervasive DataExchange Agent in Pervasive DataExchange User’s Guide.
What happened to PVSW\BIN?
Pervasive DataExchange files are no longer installed to <drive>:\pvsw\bin. This change comes as Pervasive Software adopts the same program and security guidelines established by Microsoft for its current operating systems.
Where are the Pervasive DataExchange files installed?
To comply with the new guidelines established by Microsoft for the Vista operating system, new installations of Pervasive DataExchange are in the following default location:
<drive:>\ProgramData\Pervasive Software\PSQL\Replication
<drive:>\Program Files\Pervasive Software\PSQL\BIN
<drive:>\Program Files (x86)\Pervasive Software\PSQL\Replication
<drive:>\Program Files (x86)\Pervasive Software\PSQL\BIN
<drive:>\Documents and Settings\All Users\Application Data\Pervasive Software\PSQL\Replication
<drive:>\Program Files\Pervasive Software\PSQL\BIN
<drive:>\Program Files (x86)\Pervasive Software\PSQL\Replication
<drive:>\Program Files (x86)\Pervasive Software\PSQL\BIN
<drive:>\Program Data\Pervasive Software\PSQL\Replication
<drive:>\Program Files\Pervasive Software\PSQL\Replication
<drive:>\Documents and Settings\All Users\Application Data\Pervasive Software\PSQL\Replication
<drive:>\Program Files\Pervasive Software\PSQL\Replication
Note: The DataExchange Event Handler files are installed on all 64-bit platforms at <drive:>\Program Files\Pervasive Software\PSQL\BIN
1 Windows Vista and later refers to Windows Vista and any Windows operating system released after Windows Vista that is currently supported by Pervasive PSQL.
2 Windows pre-Vista refers to any Windows operating system currently supported by Pervasive PSQL that was released prior to Windows Vista.
Uninstalling Pervasive DataExchange
The uninstall program removes all DataExchange components from your system. Uninstall removes databases registered by Pervasive PSQL that are located under <Installation Directory >\Replication.
The uninstall program does not remove any databases that were created in locations other than under <Installation Directory >\Replication. It also does not remove the DSNs and database names associated with these databases.
If you have activated databases located under <Installation Directory >\Replication, perform the following actions before you uninstall DataExchange:
*
Deactivate each database with the dxdeact utility. See dxdeact in Pervasive DataExchange User’s Guide.
*
Remove the template with Template Remover wizard. See trwizard in Pervasive DataExchange User’s Guide.
*
If you do not deactivate the database before you remove the template, uninstall leaves the database files and the associated replication files. The replication files do not cause any problems but you may prefer to reclaim physical storage by deleting them.
Note The Pervasive PSQL database engine must be stopped and restarted during the uninstall of Pervasive DataExchange. If your business requirements prohibit stopping the database engine during certain hours, uninstall DataExchange during an acceptable period.
*
Note You are not required to uninstall DataExchange before upgrading it. If you want to upgrade DataExchange, see Upgrading Pervasive DataExchange. An uninstall removes all DataExchange design and activated database information from your system, as well as any databases created under the <Installation Directory >\Replication directory. Uninstalling requires that you redesign your replication databases.
1
Access the Add/Remove Programs from Control Panel on your Windows operating system.
2
Click Pervasive DataExchange in the list.
3
Click the button to remove a program. The button may be labelled Add/Remove or Remove. The program to uninstall Pervasive DataExchange begins.
4
Click OK in response to the message about completely removing DataExchange.
5
Click Yes (and OK to confirm) in response to any messages about removing shared components in the Pervasive directory structure.
6
Click OK when the uninstall program completes.
7