JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
ToolTalk User's Guide
search filter icon
search icon

Document Information

Preface

1.  Introducing the ToolTalk Service

2.  An Overview of the ToolTalk Service

3.  Message Patterns

4.  Setting Up and Maintaining the ToolTalk Processes

Location of the ToolTalk Service Files

Version

Requirements

Environment Variables

ToolTalk Environment Variables

Other 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

Redirecting the ToolTalk Database Server

Redirecting the Host Machine

Redirecting the File System Partition

5.  Maintaining Application Information

6.  Maintaining Files and Objects Referenced in ToolTalk Messages

7.  Participating in ToolTalk Sessions

8.  Sending Messages

9.  Dynamic Message Patterns

10.  Static Message Patterns

11.  Receiving Messages

12.  Objects

13.  Managing Information Storage

14.  Handling Errors

A.  Migrating from the Classing Engine to the ToolTalk Types Database

B.  A Simple Demonstration of How the ToolTalk Service Works

C.  The ToolTalk Standard Message Sets

D.  Frequently Asked Questions

Glossary

Index

Redirecting the ToolTalk Database Server

You can redirect both database host machines and the file system partitions.

Redirecting the Host Machine

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:

  1. Create a hostname_map file.

    For example:


    # Map first host machine
    oldhostname1  newhostname1
    
    # Map second host machine
    oldhostname2  newhostname2

    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.

  2. Store the file in the same location at which the ToolTalk Types databases are stored.

    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).

Redirecting the File System Partition

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:

  1. Create a partition_map file.

    For example:


    # Map first partition
    /cdrom  /usr
    
    # Map second partition
    /sr0/export/home  /export/home

    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.

  2. Store the map file in the same location at which the system ToolTalk Types databases are stored.

    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).