1. Introducing the ToolTalk Service
2. An Overview of the ToolTalk Service
4. Setting Up and Maintaining the ToolTalk Processes
Location of the ToolTalk Service Files
ToolTalk Environment Variables
Environment Variables Required to Start Programs on Remote Hosts
Using Context Slots to Create Environment Variables
Installing the ToolTalk Database Server
Confirming that the rpc.ttdbserverd is installed on a system.
Confirming that the rpc.ttdbserverd is running on a system.
From the Solaris Distribution CD-Rom
Running the New ToolTalk Database Server
5. Maintaining Application Information
6. Maintaining Files and Objects Referenced in ToolTalk Messages
7. Participating in ToolTalk Sessions
13. Managing Information Storage
A. Migrating from the Classing Engine to the ToolTalk Types Database
B. A Simple Demonstration of How the ToolTalk Service Works
You can redirect both database host machines and the file system partitions.
Redirecting a database host machine allows a ToolTalk client to physically access ToolTalk data from a machine that is not running a ToolTalk database server.
Redirecting a file system partition allows a ToolTalk database to logically read and write ToolTalk data from and to a read-only file system partition (for example, a CD-Rom) by physically accessing a different file system partition. Redirecting a file system partition also is done if a system administrator wants all ToolTalk databases to reside on a single local partition instead of one per local partition, which is the default.
When you redirect a database host machine, a ToolTalk client can physically access ToolTalk data from a machine that is not running a ToolTalk database server. To redirect the host machine, you need to map the hostnames of the machines the ToolTalk client is to access. On the machine running the ToolTalk client that is making the database query:
For example:
|
where oldhostname is the name of the machine the ToolTalk client needs to access and newhostname is the name of a machine that is running the ToolTalk database server.
The map files have the same order of precedence as the ToolTalk Types databases (see tt_type_comp(1).
Note - A file defined in the TT_HOSTNAME_MAP environment variable has a higher precedence than the map in the user database.
The map file is read into a ToolTalk client when the client makes a tt_open call. For detailed information on host redirection see hostname_map(4).
When you redirect a file system partition, a ToolTalk database can logically read and write ToolTalk data from and to a read-only file system partition by physically accessing a different file system partition. To redirect a file partition, you need to map the partitions to where the ToolTalk database will write. On the machine running the ToolTalk database server:
For example:
|
maps the read-only partition /cdrom to /usr, a read-write partition; and maps the read-only partition /sr0/export/home to /export/home, a read-write partition.
Note - A file partition defined in the TT_PARTITION_MAP environment variable has a higher precedence than the file partition defined in this map file.
The map file is read when the ToolTalk database server is started, or when the database server receives a USR2 signal. For detailed information on partition redirection see partition_map(4).