Solstice X.400 Client Toolkit 9.0 Administrator's Guide · A Sun Microsystems, Inc. Business Part No.: 802-5046-10 Revision A ... machine_name% You have mail. AaBbCc123 What you …

Solstice™ X.400 Client Toolkit 9.0Administrator’s Guide

A Sun Microsystems, Inc. Business

Part No.: 802-5046-10Revision A, February 1996

2550 Garcia AvenueMountain View, CA 94043U.S.A.

PleaseRecycle

1996 Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain View, California 94043-1100 U.S.A.

All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use,copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any meanswithout prior written authorization of Sun and its licensors, if any.

Portions of this product may be derived from the UNIX® system, licensed from UNIX System Laboratories, Inc., a wholly ownedsubsidiary of Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. Third-partysoftware, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth insubparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19.The product described in this manual may be protected by one or more U.S. patents, foreign patents, or pending applications.

TRADEMARKSSun, Sun Microsystems, the Sun logo, Solaris, SunLink, Solstice, SunSoft, and the SunSoft logo are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark in the UnitedStates and other countries, exclusively licensed through X/Open Company, Ltd. OPEN LOOK is a registered trademark ofNovell, Inc. PostScript and Display PostScript are trademarks of Adobe Systems, Inc. Motif is a registered trademark of OpenSoftware Foundation, Inc.

All SPARC trademarks are trademarks or registered trademarks of SPARC International, Inc. in the United States and othercountries. SPARCcenter, SPARCcluster, SPARCompiler, SPARCdesign, SPARC811, SPARCengine, SPARCprinter, SPARCserver,SPARCstation, SPARCstorage, SPARCworks, microSPARC, microSPARC-II, and UltraSPARC are licensed exclusively to SunMicrosystems, Inc. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

The OPEN LOOK® and Sun™ Graphical User Interfaces were developed by Sun Microsystems, Inc. for its users and licensees.Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical userinterfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, whichlicense also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written licenseagreements.

X Window System is a trademark of X Consortium, Inc.

THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES AREPERIODICALLY ADDED TO THE INFORMATION HEREIN. THESE CHANGES WILL BE INCORPORATED IN NEWEDITIONS OF THE PUBLICATION. SUN MICROSYSTEMS, INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES INTHE PRODUCT(S) AND/OR THE PROGRAMS(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.

iii

Contents

1. Introducing the Solstice X.400 Client Toolkit . . . . . . . . . . . . . 1

Overview of an X.400 Message Handling System . . . . . . . . . . . 2

Remote Access With Solstice X.400 Client Toolkit Applications 4

Overview of the Solstice X.400 Client Toolkit . . . . . . . . . . . . . . 6

X/Open Message Access (XMA) Interface . . . . . . . . . . . . . . 7

X/Open Message Store (XMS) Interface . . . . . . . . . . . . . . . . 7

X/Open OSI-Abstract-Data Manipulation (XOM) Interface 8

Client Toolkit Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

SNMP Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

RFC1006 Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

The osixapia Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

An Example Solstice X.400 Client Toolkit Application . . . . . . . 10

Summary of Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2. Using the Solstice Client Toolkit Configuration Tool. . . . . . . 13

Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

iv Solstice X.400 Client Toolkit Administrator’s Guide—February 1996

Setting Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . 14

▼ Starting xapiatool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Introducing the Solstice Client Toolkit Configuration Tool (xapiatool) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

▼ Saving a Backup Configuration . . . . . . . . . . . . . . . . . . . . 17

▼ Restoring From a Backup Configuration . . . . . . . . . . . . 17

▼ Printing Client Toolkit Database and Daemon Information18

▼ Using the Command-Line Print Tool (xapiaprt) . 19

Configuring Messaging Servers in the Client Toolkit Database 19

▼ Adding a Messaging Server to the Client Toolkit Database19

▼ Adding Other Messaging Servers to the Client ToolkitDatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

▼ Changing the Parameters of a Messaging Server in the ClientToolkit Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

▼ Deleting a Messaging Server from the Client ToolkitDatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring UAs in the Client Toolkit Database . . . . . . . . . . . . 23

▼ Adding a UA to the Client Toolkit Database . . . . . . . . . 23

▼ Adding Other UAs to the Client Toolkit Database 26

▼ Changing the Parameters of a UA in the Client ToolkitDatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

▼ Deleting a UA from the Client Toolkit Database . . . . . . 26

Displaying the osixapia Daemon Address . . . . . . . . . . . . . . . 27

Tuning the osixapia Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . 27

▼ Tuning the Remote Operation Service Element (ROSE) 27

Contents v

▼ Tuning the Session Layer . . . . . . . . . . . . . . . . . . . . . . . . . 28

3. Troubleshooting and Diagnostics . . . . . . . . . . . . . . . . . . . . . . . 31

Troubleshooting with xapiatrace . . . . . . . . . . . . . . . . . . . . . . 31

Finding osixapia Daemon and OSI Stack Messages . . . . . . . 33

Errors Returned by xapiatool . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Errors Indicating Rejected RFC1006 Connections . . . . . . . . . . . 35

vi Solstice X.400 Client Toolkit Administrator’s Guide—February 1996

vii

Figures

Figure 1-1 The X.400 Message Handling System Model . . . . . . . . . . . . . . 2

Figure 1-2 X.400 MHS Without Solstice X.400 Client Toolkit Applications 4

Figure 1-3 X.400 MHS With Solstice X.400 Client Toolkit Applications . 5

Figure 1-4 Components of Solstice X.400 Client Toolkit. . . . . . . . . . . . . . . 6

Figure 1-5 Components Used in P3 Access to a Message Transfer Agent 7

Figure 1-6 Components Used in P7 Access to a Message Store. . . . . . . . . 7

Figure 1-7 osixapia Daemon and Transport Providers . . . . . . . . . . . . . 9

Figure 1-8 Example Solstice X.400 Client Toolkit Application . . . . . . . . . 11

Figure 2-1 xapiatool Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Figure 2-2 Print Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Figure 2-3 Add an MTA or MS (Messaging Server) Options. . . . . . . . . . . 20

Figure 2-4 Add a User Agent (Messaging Client) Options . . . . . . . . . . . . 24

viii Solstice X.400 Client Toolkit Administrator’s Guide—February 1996

viii

Preface

The Solstice X.400 Client Toolkit Administrator’s Guide describes how to configureand maintain the SolsticeTM X.400 Client Toolkit. The Solstice X.400 ClientToolkit is a messaging toolkit, which you can use to write X.400 applicationsand to enable applications to communicate remotely with the Solstice X.400Messaging Server.

This book provides:

• An introduction to X.400 and the Solstice X.400 Client Toolkit, and how theircomponents combine to give you a messaging toolkit.

• Instructions on how to use the Solstice X.400 Client Toolkit configurationtool (xapiatool ) to configure your system. xapiatool provides a menusystem with which you can add information about your messagingapplications.

• Troubleshooting information to help you locate and diagnose problems.

Who Should Use This BookRead this book if you are configuring the Solstice X.400 Client Toolkit. Youneed to know your system and how network devices installed on yourmachine are connected. You also need a good understanding of X.400, OSI, andother networking principles and terminology.

ix Solstice X.400 Client Toolkit Administrator’s Guide—February 1996

How This Book Is OrganizedChapter 1, “Introducing the Solstice X.400 Client Toolkit”, provides anoverview of X.400 and the Solstice X.400 Client Toolkit. It introduces theSolstice X.400 Client Toolkit architecture and the structure of the software.

Chapter 2, “Using the Solstice Client Toolkit Configuration Tool”, describesthe Solstice X.400 Client Toolkit configuration tool and its components, andhow to use it.

Chapter 3, “Troubleshooting and Diagnostics”, introduces a command-linetool you can use to monitor communication, and discusses some problems thatyou might encounter while configuring or using the Solstice X.400 ClientToolkit. It suggests ways to fix and avoid these problems.

Related DocumentationThe Solstice X.400 Client Toolkit documentation set includes the followingdocuments:

• Installing and Licensing Solstice X.400 Products describes the procedure forinstalling and licensing the Solstice X.400 Client Toolkit.

• Solstice X.400 Programming Reference Manual describes the X/OpenTM

message access (XMA) and message store (XMS) application programminginterfaces.

• Solstice XOM Programming Reference Manual describes the OSI objectmanagement application programming interface (API). Use this API inconjunction with the application-specific APIs described in the Solstice X.400Programming Reference Manual to develop your remote-access messagingapplications.

• Solstice X.400 Messaging Server Administrator’s Guide describes SNMP agentsand the RFC1006 driver. See “SNMP Agent” on page 8” and “RFC1006Driver” on page 8 for an introduction to these components.

If you decide to use the SunLink OSI Communications Platform (Stack) insteadof the RFC1006 driver, you will also need the following documents:

• Installing and Licensing SunLink OSI (Part No. 804-4666)

• SunLink OSI Communication Platform Administrator’s Guide(Part No. 801-4975)

x

What Typographic Changes MeanThe following table describes the typographic changes used in this book.

Shell Prompts in Command ExamplesThe following table shows the default system prompt and superuser promptfor the C shell, Bourne shell, and Korn shell.

Table P-1 Typographic Conventions

Typeface orSymbol Meaning Example

AaBbCc123 The names of commands,files, and directories;on-screen computer output

Edit your .login file.Use ls -a to list all files.machine_name% You have mail.

AaBbCc123 What you type, contrastedwith on-screen computeroutput

machine_name% suPassword:

AaBbCc123 Command-line placeholder:replace with a real name orvalue

To delete a file, type rm filename.

AaBbCc123 Book titles, new words orterms, or words to beemphasized

Read Chapter 6 in User’s Guide.These are called class options.You must be root to do this.

Table P-2 Shell Prompts

Shell Prompt

C shell prompt machine_name%

C shell superuser prompt machine_name#

Bourne shell and Korn shellprompt

$

Bourne shell and Korn shellsuperuser prompt

#

xi Solstice X.400 Client Toolkit Administrator’s Guide—February 1996

Restrictions on Messaging System Component NamesThe following characters must not be used for any of the names describingmessage transfer agents (MTAs), message stores, or user agents:

MTA and message store names can be up to and including 32 characters long;user agent names can be up to and including 16 characters long.

Invalid Characters Description

@ “at” symbol

/ Forward slash

\ Backslash

# Hash or pound sign

Space

-> Tab

1

Introducing the Solstice X.400Client Toolkit 1

This chapter provides:

• An overview of a typical X.400 Message Handling System (MHS) and anintroduction to the terminology used to describe the components of theMHS.

• A discussion of the advantages of adding applications written with theSolstice X.400 Client Toolkit to your messaging environment.

• An overview of the components in the Solstice X.400 Client Toolkit software.

• A case study that discusses the use of a Solstice X.400 Client Toolkitapplication to transfer files.

• A summary of the steps you must follow to configure your messagingsystem for Solstice X.400 Client Toolkit applications.

Overview of an X.400 Message Handling System page 2

Remote Access With Solstice X.400 Client Toolkit Applications page 4

Overview of the Solstice X.400 Client Toolkit page 6

An Example Solstice X.400 Client Toolkit Application page 10

Summary of Steps page 12

2 Solstice X.400 Client Toolkit Administrator’s Guide—February 1996

1

Overview of an X.400 Message Handling SystemThe Solstice X.400 Client Toolkit works within an X.400 Message HandlingSystem (MHS) environment. Figure 1-1 shows the components of a typicalX.400 MHS. This system is used to transfer electronic messages from one enduser to another.

Figure 1-1 The X.400 Message Handling System Model

The basic parts of the X.400 Message Handling System are:

• User Agents (UA)A user agent is a messaging client. It handles the submission and delivery ofelectronic messages. A UA provides the direct interface between end users(application processes) and message transfer agents. Every UA has an X.400address, which is known as an originator/recipient address or O/R address.The O/R address specifies the information needed to deliver a message toan end user.

Message Transfer

MessageTransfer Agent

System (MTS)

User Agent 1

User Agent 3

MessageTransfer Agent

MessageStore

User Agent 2

Introducing the Solstice X.400 Client Toolkit 3

1

• Messaging ServersA messaging server consists of the following components:

• Message Transfer Agent (MTA)Message transfer agents are the X.400 routers. They handle the routing ofelectronic messages. A collection of MTAs is called a message transfersystem (MTS).

Your local MTA is the MTA running on your local machine. It handlesthe routing of electronic messages between user agents (applicationprograms) and remote MTAs. It is the focal point through which allmessages pass through your local messaging system.

Remote MTAs are the message transfer agents with which your localMTA can communicate directly. They handle the routing and relaying ofelectronic messages throughout the X.400 domain.

• Message Store (MS)A Message store acts as an intermediary between MTS users and anMTA. It stores X.400 messages, and let users manipulate and sendmessages in a variety of ways. Without a message store, UAs mustconnect to an MTA and explicitly request to receive messages.

A message store accepts delivery of messages on behalf of a UA andstores the messages for subsequent viewing, retrieval, and forwarding.The MS provides a UA with additional functionality compared to directsubmission to the MTS. For example, an MS can send alerts to a UAwhen it receives a certain message.

For a full description of messaging server components, see the Solstice X.400Messaging Server Administrator’s Guide.


1

Remote Access With Solstice X.400 Client Toolkit ApplicationsFigure 1-2 shows an example MHS configuration. The user agents were notdeveloped with the Solstice X.400 Client Toolkit.

Figure 1-2 X.400 MHS Without Solstice X.400 Client Toolkit Applications

To communicate with remote MTAs, each system in this example must run thefollowing software applications:

• One or more User Agents• A Messaging Server (message transfer agent and/or message store)• The OSI communications platform (stack)

Now consider the example MHS configuration in Figure 1-3 on page 5. SystemD and system E are running UAs developed with the Solstice X.400 ClientToolkit. These UAs have remote access to a local messaging server via anEthernet LAN. Only one machine needs to be running an MTA and OSI stack.

X.25

OSI Stack

System A

Remote MTAsX.400

UA UA

OSI Stack

UA

OSI Stack

UA UA

System B System C

UA

Ethernet LAN


1

Figure 1-3 X.400 MHS With Solstice X.400 Client Toolkit Applications

The configuration shown in Figure 1-3 has several advantages over theconfiguration shown in Figure 1-2 on page 4. With applications developed withthe Solstice X.400 Client Toolkit, the messaging system uses fewer messagingservers (MTAs) and OSI stacks. With fewer messaging components, theconfiguration is more cost effective to implement. You also have the flexibilityof locating your user agent applications on systems without an MTA. In otherwords, an application developed using the Solstice X.400 Client Toolkit willrun without modification on both a machine running a messaging server and amachine without a messaging server. An application developed using theSolstice X.400 Messaging Server will run only on the same machine as themessaging server.

X.25

Solstice X.400

OSI Stack

Server

Remote MTAs

Ethernet LAN

System D System E

X.400

Client ToolkitUser Agents


1

Overview of the Solstice X.400 Client ToolkitThe Solstice X.400 Client Toolkit is a messaging toolkit, which you can use towrite X.400 MHS applications. You can develop applications that have remoteaccess to an MTA, using the industry standard X/Open Message Access (XMA)interface, and remote access to a MS, using the industry standard X/OpenMessage Store (XMS) interface.

Figure 1-4 shows the components of the Solstice X.400 Client Toolkit.

• Remote-access applications are linked to the MA or MS library. They use theXMA interface or the XMS interface to call library functions.

• The osixapia daemon manages access to the network.

• The client toolkit database contains information about the configuration ofyour applications and each MTA and MS that they communicate with.

The Solstice X.400 Client Toolkit also includes the X/Open object management(XOM) interface, a graphical tool that you use to update the client toolkitdatabase, a SNMP agent, and an RFC1006 driver.

Figure 1-4 Components of Solstice X.400 Client Toolkit

Remote access to MTA or MS

Solstice X.400

MA Applications

XMA Interface

database

Client Toolkit

osixapiadaemon

MS Applications

XMS Interface

MS LibraryMA Library


1

X/Open Message Access (XMA) Interface

The X/Open Message Access (XMA) interface is a programming interface tothe MA library. With the XMA interface, you can write UA applications thattransfer information to and from MTAs using the P3 protocol. Figure 1-5 showsthis interaction.

If you are running more than one MA application or process on a system, theMA library is shared between the applications. For a full description of theXMA interface, see the Solstice X.400 Programming Reference Manual.

Figure 1-5 Components Used in P3 Access to a Message Transfer Agent

X/Open Message Store (XMS) Interface

The X/Open Message Store (XMS) interface is a programming interface to theMS library. With the XMS interface, you can write UA applications that transferinformation to and from message stores using the P7 protocol. Figure 1-6shows this interaction.

If you are running more than one MS application or process on a system, theMS library is shared between the applications. For a full description of theXMS interface, see the Solstice X.400 Programming Reference Manual.

Figure 1-6 Components Used in P7 Access to a Message Store

P3 protocol

Network Access

MAMessage

Transfer Agentapplication

P7 protocol

Network Access

MS MessageStoreapplication


1

X/Open OSI-Abstract-Data Manipulation (XOM) Interface

The X/Open OSI-Abstract-Data Manipulation (XOM) interface provides aneasy way to encode and decode objects using abstract syntax notation one(ASN.1). Use the XOM interface in conjunction with the XMA and XMSinterface when you develop X.400 applications.

For a full description of the XOM interface, see the Solstice XOM ProgrammingReference Manual.

Client Toolkit Database

The client toolkit database contains configuration information for your remoteaccess applications (UAs), and information about each MTA and MS that yourapplications communicate with. The MA and MS libraries use the client toolkitdatabase to get information on and determine the association between the localUAs and their MTAs or message stores located on another system.

There is a client toolkit database on each system where you install the SolsticeX.400 Client Toolkit. To configure the Solstice X.400 Client Toolkit, you addUA, MTA, and message store entries to the client toolkit database. To do this,use the Solstice X.400 Client Toolkit configuration tool (xapiatool ). SeeChapter 2, “Using the Solstice Client Toolkit Configuration Tool”.

SNMP Agent

The simple network management protocol (SNMP) agent lets you usemanagement applications such as the Solstice Messaging Manager to monitorand analyze the Solstice X.400 Client Toolkit from a single location. The agentis described in the Solstice Messaging Management Administrator’s Guide.

RFC1006 Driver

The RFC1006 driver gives you the option of running the Solstice X.400 ClientToolkit without the SunLink OSI Communications Platform (stack). For moreinformation see Installing and Licensing Solstice X.400 Products, the Solstice X.400Messaging Server Administrator’s Guide, and the manpages for rk6d(1M) ,rk6stat(1M) , and rk6trace(1M) .


1

The osixapia Daemon

The osixapia daemon is a process that transfers data between a Solstice X.400Client Toolkit application and its MTA or MS located on another system. Thedaemon uses UNIX IPC (inter-process communication) to communicate withX.400 applications. Figure 1-7 illustrates the components of the daemon, andshows its association with transport providers.

Figure 1-7 osixapia Daemon and Transport Providers

The Remote Operation Service Element (ROSE), uses the presentation layer totransfer data to and from remote systems. ROSE transfers information inoperation protocol data units (OPDUs).

The session layer manages and synchronizes communication between thesystems. If there is a problem with either system, the session layer uses itssynchronization points to determine where it should resume the dataexchange.

You can tune ROSE and the session layer using the Solstice X.400 Client Toolkitconfiguration tool (xapiatool ). See Chapter 2, “Using the Solstice ClientToolkit Configuration Tool”.

ROSE

osixapia Daemon

Presentation

OSI Transport

LAN WANTCP/IP

RFC1006

Session

Transport Level Interface (TLI)


1

An Example Solstice X.400 Client Toolkit ApplicationThis example shows how a telecommunications company uses a Solstice X.400Client Toolkit application to collect customer billing information.

A telecommunications company collects and processes customer informationfor billing purposes. The company has many data-collection sites across thecountry. Each site produces customer billing information in the form of largefiles. These files are sent as X.400 messages across a network to the company’sdata-processing headquarters. The company uses an X.400 messaging systemto transfer the files because of its reliability and security features.

Figure 1-8 on page 11 shows the components of one data collection site. Datacollection devices monitor customer usage to produce the billing files. An MAapplication, written with the Solstice X.400 Client Toolkit, reads the files. Itcontains multiple processes that share the MA library:

• Sender processes read the billing files from the data collection devices andtransfer them over an Ethernet LAN to the MTA. Each file is sent as an X.400message with a request for a delivery report.

• A Receiver process reads the delivery reports sent back by a remote MTA. Ifthere was a problem delivering a message, the receiver process requests asender process to resend the message.

When a process is ready to send or receive data, it binds to the MTA across anEthernet LAN as a user agent. All the processes use the same O/R address, sothe server needs only one UA defined on the MTA. This multiple binding ofprocesses to an MTA enables the receiver process to read delivery reports.

The MTA routes the messages to a remote MTA at the company’s data-processing headquarters. The remote MTA delivers the messages to a dataprocessing application, and sends back delivery reports to the data-collectionsite.


1

Figure 1-8 Example Solstice X.400 Client Toolkit Application

X.25

Remote MTA, located

Ethernet LAN

OSI Stack

Server

MA Application

osixapiadaemon

Sender process

Sender process

Receiver process

XMA Interface

BillingFile

BillingFile

Data CollectionDevices

at the data-processing

Data Collection System

X.400

UNIX IPC

MA Library

Other datacollection sites

headquarters

Other datacollection systems


1

Summary of StepsBefore you can write Solstice X.400 Client Toolkit remote-access applications,you must configure your messaging system. On a machine where you will runa Solstice X.400 Client Toolkit application, follow these steps:

1. If necessary, install the SunLink OSI Communications Platform (Stack).See Installing and Licensing SunLink OSI.

2. Install the Solstice X.400 Client Toolkit.See Installing and Licensing Solstice X.400 Products.

3. Set the environment variables.See “Setting Environment Variables” on page 14.

4. Write the Solstice X.400 Client Toolkit application.See the Solstice X.400 Programming Reference Manual.

5. Add the UA to the MHS configuration on the remote machine running theMTA or MS.For information on how to add UAs to a Solstice X.400 environment, see theSolstice X.400 Messaging Server Administrator’s Guide.

6. Add the MTA or MS to the client toolkit database.See “Adding a Messaging Server to the Client Toolkit Database” on page 19.

7. Add the UA to the client toolkit database.See “Adding a UA to the Client Toolkit Database” on page 23.

13

Using the Solstice Client ToolkitConfiguration Tool 2

This chapter describes how to configure your local environment so that youcan develop and use remote access applications. The Solstice X.400 ClientToolkit configuration tool (xapiatool ) has a Motif® graphical user interface.With xapiatool , you can easily add information about UAs, MTAs, andMessage Stores to the client toolkit database.

Before You StartMake sure that the software is installed correctly, as described in Installing andLicensing Solstice X.400 Products. If you are using an OSI transport provider,also make sure that you have installed and configured the SunLink OSIcommunications platform (stack).

Before You Start page 13

Introducing the Solstice Client Toolkit Configuration Tool (xapiatool) page 16

Configuring Messaging Servers in the Client Toolkit Database page 19

Configuring UAs in the Client Toolkit Database page 23

Displaying the osixapia Daemon Address page 27

Tuning the osixapia Daemon page 27


2

Setting Environment Variables

Before you use xapiatool , set your UIDPATH to /opt/SUNWconn/mhs/lib/gui ,and add the following paths to the environment variables in your shellinitialization file:

PATH /opt/SUNWconn/sbin

MANPATH /opt/SUNWconn/man

If you installed the software in other directories instead of the defaultdirectories, modify your environment variables to include those directories.

▼ Starting xapiatool

To start xapiatool :

1. Log in as root or become superuser .

2. Make sure that the transport provider is running:

a. If your messaging applications use an OSI transport provider, makesure that the SunLink OSI stack is running.

If the stack is not running, start it manually by typing:

b. If your messaging applications use the RFC1006 transport provider,make sure that the rk6d daemon is running.

If the daemon is not running, start it manually by typing:

hostname# ps -ef | grep osinetdroot <pid> <timestamp> /usr/sbin/osinetd

hostname# /etc/rc2.d/S90osinet start

hostname# ps -ef | grep rk6droot <pid> <timestamp> /usr/sbin/rk6d

hostname# /etc/rc2.d/S90rk6 start

Using the Solstice Client Toolkit Configuration Tool 15

2

3. Make sure that the osixapia daemon is running.If you rebooted your machine after you installed Solstice X.400 ClientToolkit the daemon should already be started. You can verify this by typing:

If the daemon is not running, start it manually by typing:

4. Start xapiatool .

If osinetd , osixapia , or xapiatool do not start correctly, an error messageis displayed. See “Troubleshooting and Diagnostics” on page 31 for possiblecauses and solutions.

Note – Only one xapiatool can run on a host at a time.

hostname# ps -ef | grep osixapiaroot <pid> <timestamp> osixapia osixapia osixapia

hostname# x400start osixapia

hostname# xapiatool &


2

Introducing the Solstice Client Toolkit Configuration Tool (xapiatool )The Solstice X.400 Client Toolkit configuration tool, xapiatool , is a graphicaluser interface to the client toolkit database. Use it to add or change informationabout UAs, MTAs, and Message Stores in the client toolkit database.

When you start xapiatool , a window similar to that shown in Figure 2-1 isdisplayed. If this is the first time you have started xapiatool on yourmachine, there will not be any items in the scrolling lists.

Figure 2-1 xapiatool Main Window

The xapiatool main window has the following pull-down menus:

• Servers — Use to add MTAs and Message Stores to the client toolkitdatabase, and edit or delete them in the client toolkit database. Each MTAand MS you add is displayed in the Messaging Servers scrolling list.


2

• Clients — Use to add UAs to the client toolkit database, and edit or deleteUAs in the client toolkit database. Each UA you add is displayed in theMessaging Clients scrolling list.

• Tune — Use to adjust the parameters of, for example, ROSE.

• Binding — Use to display the address of the local osixapia daemon.

• File — Use to back up, restore, and print the client toolkit database, and toexit from xapiatool .

The following sections describe how to use these menus.

▼ Saving a Backup Configuration

Use the Backup item on the File menu to make a backup of the client toolkitdatabase. To safeguard your data, make a backup when you complete a newconfiguration or make changes to an existing one. Making a backup also savesyou time configuring the client toolkit database on other systems. Once youhave made a backup on one system, copy the backup file to another systemand restore it there. You can then make any necessary changes to the clienttoolkit database for that system. By default, a backup file is saved in thedirectory /var/opt/SUNWconn/OSIROOT/mhs/conf . You can specify analternative location.

1. Choose Backup from the File menu.A file selection window is displayed.

2. Choose a directory and type a file name.

3. Click OK to back up your configuration to file.

▼ Restoring From a Backup Configuration

Use the Restore item to load a backup of the client toolkit database.

1. Choose Restore from the File menu.A file selection window is displayed.

2. Choose a directory and configuration file.Use the Filter input line to filter out names from the list of files.

3. Click OK to load the contents of the configuration file.


2

▼ Printing Client Toolkit Database and Daemon Information

Use the Print option to print the current contents of the client toolkit databaseand information about the configuration of the osixapia daemon. You canselect which items you want to print, and print to any local printer or to a file.

1. Choose Print from the File menu.The Print Configuration window is displayed, as shown in Figure 2-2.

Figure 2-2 Print Configuration Options

2. Deselect any items you do not want to print.By default, all items are printed.

3. Type the name of a printer or specify the name of a file to print to.

4. Click OK to print.


2

▼ Using the Command-Line Print Tool (xapiaprt )

You can also use the command-line print tool, xapiaprt , to print client toolkitdatabase and daemon information. You might use this when, for example, youare using a character-based terminal.

♦ To print your current configuration on the default printer, type thefollowing:

Type xapiaprt -h for information on how to print specific parameters.

Configuring Messaging Servers in the Client Toolkit DatabaseTo enable your applications (UAs) to communicate with a messaging server (anMTA or MS), you must add information about the server to the client toolkitdatabase on the same system as the UA.

▼ Adding a Messaging Server to the Client Toolkit Database

To add a messaging server to the client toolkit database, you first have to findout the OSI selectors and network address. Get this information from thesystem administrator who installed the messaging server. If it is a Solsticemessaging server, you can use x400tool to find out its OSI selectors(replacing the transport selector with P3 for an MTA or P7 for an MS) andnetwork address. For information on how to use x400tool , see the SolsticeX.400 Messaging Server Administrator’s Guide.

If the messaging server you are adding is both an MTA and message store, youmust add it twice to the client toolkit database; once as an MTA and once as amessage store.

1. Choose Add from the Messaging Servers menu.A window similar to that shown in Figure 2-3 on page 20 is displayed.Depending on the type of network you use, the Network Access parametersmay be different from those shown in Figure 2-3.

hostname$ xapiaprt -a | lp


2

Figure 2-3 Add an MTA or MS (Messaging Server) Options

2. Specify the information shown in Table 2-1 on page 21.

3. Click OK to add the messaging server to the client toolkit database.


2

Table 2-1 MTA and MS Parameters

Parameter Description

Server Name A name for the messaging server. This must be unique within the client toolkitdatabase.

Presentation The OSI presentation selector (PSEL) specifies the access point of an X.400application. It is used by the presentation service to identify an applicationlayer entity.Use the Presentation menu option button to choose a hexadecimal or characterformat for the access point.

Session The OSI session selector (SSEL) is used by the session layer to identify apresentation layer entity.Use the Session menu option button to choose a hexadecimal or characterformat for the access point.

Transport The OSI transport selector (TSEL) is used by the transport service to identify asession layer entity.If you are adding a Solstice MTA, type P3 as the transport selector. If you areadding a Solstice message store, type P7 as the transport selector.Use the Transport menu option button to choose a hexadecimal or characterformat for the access point.

Network Type The network type specifies how the messaging server is physically attached tothe network.Use the Network Type menu option button to choose the type of network usedfor the connection.

Address The address is used by a UA to reach the messaging server across the network.Depending on the type of network, type:

• An IP (Internet Protocol) address, if the network type is RFC 1006(TCP/IP).

• An X.25 address, if the network type is X.25 (WAN) 1980.

• A CONS NSAP, if the network type is X.25 (CONS) 1984.

• A net selector, if the network type is LAN-LLC1.

Use the Address menu option button to choose a hexadecimal or characterformat for the address.

Host Name If the network type is RFC 1006, and you use a domain name service, insteadof entering the network address on the Address input line you can enter thehost name that corresponds to the address.


2

▼ Adding Other Messaging Servers to the Client Toolkit Database

Once you have added a messaging server you can use its parameters as atemplate for adding other MTAs or Message Stores. This can save you time re-entering parameters that are the same for several messaging servers. They mayhave, for example, the same OSI selectors. To use this shortcut, follow thesesteps:

1. Select a messaging server from the messaging servers scrolling list in themain window.

2. Choose Copy from the Servers menu.The screen shown in Figure 2-3 on page 20 is displayed, which includes theparameter settings for the messaging server you selected.

3. Change the name and any other parameters that are different for themessaging server you are adding, then click OK.

▼ Changing the Parameters of a Messaging Server in the Client ToolkitDatabase

To change the parameters of a messaging server in the client toolkit database,do the following:

1. Double-click on a messaging server in the messaging servers scrolling listin the main window.The Edit a Message Server window is displayed, which is similar to thescreen shown in Figure 2-3 on page 20. The window shows the currentparameter settings for the messaging server you selected.

2. Change any parameters, then click OK.For a description of each parameter, see Table 2-1 on page 21.


2

▼ Deleting a Messaging Server from the Client Toolkit Database

To delete a messaging server from the client toolkit database, do the following:

1. Disconnect or delete from the client toolkit database any UAs bound tothe messaging server.Select a UA from the message clients scrolling list in the main window, thenuse the up and down arrow keys as a quick way to find out which UAs arebound to the messaging server. When a UA is selected, the messaging serverit is served by is highlighted in the message servers scrolling list.

For information on how to disconnect a UA, see “Changing the Parametersof a UA in the Client Toolkit Database” on page 26. For information on howto delete a UA, see “Deleting a UA from the Client Toolkit Database” onpage 26.

2. Select a messaging server from the messaging servers scrolling list.

3. Choose Delete from the Message Servers menu.

Configuring UAs in the Client Toolkit DatabaseTo enable communication between a messaging server and a UA, you mustadd the UA X.400 originator/recipient (O/R) address to the client toolkitdatabase. The local MA and MS libraries can then read the client toolkitdatabase to get information on the messaging server that a UA is bound to.

▼ Adding a UA to the Client Toolkit Database

To add a UA to the client toolkit database, you need its name (and password, ifone exists), global domain identifier, and the name of the MTA it will be boundto. Obtain this information from the system administrator who installed theUA.

Note – Before you add a UA, add the messaging server that it is to beconnected to. For information on how to do this, see “Adding a MessagingServer to the Client Toolkit Database” on page 19.


2

1. Choose Add from the Messaging Clients menu.The screen shown in Figure 2-4 is displayed.

Figure 2-4 Add a User Agent (Messaging Client) Options

2. Specify the information shown in Table 2-2 on page 25.Depending on the type of O/R address a UA has, some of the parametersdescribed in Table 2-2 are mandatory while others are conditional. SeeTable 2-3 on page 25 for a summary of mandatory (M) and conditional (C)UA parameters. For more information on the types of O/R address, see theSolstice X.400 Programming Reference Manual.

3. Click OK to add the UA to the client toolkit database.


2

Table 2-2 UA Parameters


Name The name assigned to the UA. This must be the same as its namedefined on the local MTA, and must be unique within the client toolkitdatabase.

Password The password defined for this UA, if there is one.

Country, ADMD, PRMD The global domain identifier of the UA. This is used by an MTA to findthe UA within the X.400 domain.

X.121 Address, Terminal ID,Numeric User ID

These specify the terminal O/R address. This identifies the UA bymeans of its network address.

Surname, Given Name,Initials, Generation

Personal name attributes of the UA.

Organization, Org. Unit 1 to 4 Organizational attributes of the UA.

Remote Server The name of the messaging server that the UA is bound to. Use theremote server button to select a messaging server from the scrolling list.

Table 2-3 Mandatory and Conditional UA Parameters

Parameter Mnemonic Numeric Terminal

Name, Password M1 M1 M1

Country & ADMD M M C

PRMD C C C

X.121 Address - - M

Terminal ID - - C

Numeric User ID - M -

Personal name attributes (Surname, Given Name, Initials,Generation)

C2 - -

Organization name C - -

Organization unit name attributes (Org. Units 1 - 4) C2 - -

Remote Server M M M1 The Password parameter is optional if the UA is bound to an MTA. In other words, the Password parameter is mandatory for a P7

MS UA.2 No members of this group need be present.


2

▼ Adding Other UAs to the Client Toolkit Database

Once you have added a UA, you can use its parameters as a template foradding other UAs. This can save you time re-entering parameters that are thesame for several UAs. UAs may have, for example, the same global domainidentifier. To use this shortcut, follow these steps:

1. Select a UA from the messaging clients scrolling list in the main window.

2. Choose Copy from the Messaging Clients menu.The Edit a Message Client window is displayed, which is similar to thescreen shown in Figure 2-4 on page 24. The window shows the currentparameter settings for the UA you selected.

3. Change the name and any other parameters that are different for the UAyou are adding, then click OK.For a description of each parameter, see Table 2-2 and Table 2-3 on page 25.

▼ Changing the Parameters of a UA in the Client Toolkit Database

To change a parameter of a UA in the client toolkit database, do the following:

1. Double-click on a UA in the messaging clients scrolling list in the mainwindow.The screen shown in Figure 2-4 on page 24 is displayed, with the currentparameter settings for the UA.

2. Change any parameters, then click OK.For a description of each parameter, see Table 2-2 on page 25.

▼ Deleting a UA from the Client Toolkit Database

To delete a UA from the client toolkit database, do the following:

1. Select a UA from the messaging clients scrolling list in the main window.

2. Choose Delete from the Message Client menu.


2

Displaying the osixapia Daemon AddressUse the Binding menu from the xapiatool main window to display theaddress of your local osixapia daemon. This might be useful when, forexample, you use x400tool on a system running a MTA to declare a UA inthe MHS. For a description of the parameters, see Table 2-1 on page 21.

Tuning the osixapia DaemonYou can tune two components of the osixapia daemon: the RemoteOperation Service Element (ROSE) and the session layer. If your MTA is aSolstice MTA, you do not need to tune ROSE or the session layer.

▼ Tuning the Remote Operation Service Element (ROSE)

The Remote Operation Service Element (ROSE) is a request-reply protocol usedby application entities. It defines procedures that can be processed remotely.ROSE has several configurable parameters. Each parameter has a default value,which is usually sufficient for ROSE to work efficiently. If your MTA is not aSolstice MTA, you may decide to fine-tune ROSE.

To tune ROSE, do the following:

1. Choose Remote Operations Service from the Tune menu.You can change the following parameters:

Parameter Default Description

Window Size 8 operations The initial number of operation protocol data units (OPDUs)that can be exchanged between application entities.

Receive Queue Size 16 operations The maximum number of OPDUs that ROSE can store ineach incoming queue.

Ready Timer 60 seconds The time ROSE waits for a reply after it sends a request to anapplication entity.

Default Block Size 8 Kbytes The maximum size of data that ROSE transmits in a block.This is only used if the block size is not defined elsewhere.

Memory Data Size 4 Kbytes The maximum amount of message data ROSE stores inmemory. If the amount of data is greater than this size,ROSE saves the data in a file. Specify a value of 0 to forceROSE to save in files all the data it receives.


2

2. Drag the sliders to change the value of a parameter.

3. Click either:• OK to save your configuration changes (the new values take effect

immediately),• Cancel to discard any changes, or• Default to return to the default settings.

▼ Tuning the Session Layer

You can tune session layer parameters to change how the session entity dealswith the data received from or sent to the transport layer. If your MTA is aSolstice MTA, you do not need to tune the session layer.

1. Choose Session Layer from the Tune menu.

You can change the following parameters:


Timeout Defines the time during which a session connection can wait for an accept,after which the connection aborts.Specify a value between 30 and 1200 seconds. The default value is 60s.

Initiator Reuse Timeout If the transport connection can be reused (according to the outcome of thePropose Reuse of TC protocol negotiation), when the timeout between thetermination of a session connection and the initiation of another sessionconnection expires, the associated transport connection is terminated. Thistimeout specifies how long to maintain the transport connection open afterthe associated session connection is closed, if the connection was initiatedlocally.Specify a value between 30 and 1200 seconds. The default value is 30s.

Acceptor ReuseTimeout

If the transport connection can be reused (according to the outcome of thePropose Reuse of TC protocol negotiation), when the timeout between thetermination of a session connection and the initiation of another sessionconnection expires, the associated transport connection is terminated. Thistimeout specifies how long to maintain the transport connection open afterthe associated session connection is closed, if the connection was initiatedremotely. Specify a value between 30 and 1200 seconds. The default value is30s.


2

2. Drag the sliders to change the value of a parameter.

3. Click either:• OK to save your configuration changes (the new values take effect

immediately),• Cancel to discard any changes, or• Default to return to the default settings.

Functional Units The functional unit options are for debugging purposes. The default is thatall functional units are supported by the local session entity. These can beoverridden by negotiated values. These options do not normally need to beupdated.

Protocol Options Click on the checkboxes to switch the following protocol options on or off:

Version 1 specifies length restrictions on PDUs.Version 2 specifies no length restriction for PDUs.Extended Concatenation allows the extended concatenation of PDUs andTPDUs.Select the version of the session entity that is supported. You must choose atleast version 1 or version 2.Accept Reuse of TC accepts the reuse of a transport connection whenproposed by the remote system.Propose Reuse of TC proposes to the peer session entity that the transportconnection should be used again after the specified timeout. If the peersession entity accepts, the transport connection can be reused. If you choosethis option, make sure that the Accept Reuse of TC is also set on.Include SSAP-ID in AC SPDU adds the session service access point identifierto the AC SPDU (Session layer Protocol Data Unit Accept PDU).Try to reuse TC specifies that new connection requests can attempt to reuse atransport connection to the peer session entity. If you choose this option,make sure that the Propose Reuse of TC is also set on. The peer sessionentity must also allow reuse of transport connections. Ensure that the AcceptReuse of TC and Propose Reuse of TC are both selected if you choose thisoption.Use TRS Expedited Data specifies that the Transport Expedited Data serviceshould be used if it is available.



2

31

Troubleshooting and Diagnostics 3

This chapter describes the Solstice X.400 Client Toolkit tracing facility(xapiatrace ), provides a list of xapiatool error messages, and explainssome of the ways to avoid problems in your network configuration.

Troubleshooting with xapiatrace

The Solstice X.400 Client Toolkit tracing facility (xapiatrace ) is used toreturn dynamic information recovered from an MTA or MS. It is similar tox400trace , the Solstice X.400 Messaging Server tracing facility.

To start xapiatrace :

The command-line options are:

Troubleshooting with xapiatrace page 31

Finding osixapia Daemon and OSI Stack Messages page 33

Errors Returned by xapiatool page 33

Errors Indicating Rejected RFC1006 Connections page 35

hostname# xapiatrace [-dfr] [-p<protocols>] [-i<osi_processes>] [<filters>]


3

-d : Used to recover a full trace of ROSE and Association Control ServiceElements (ACSEs).

-f : Used to recover a full buffer trace. Without this option, only the firsttwenty lines of a message body part is displayed.

-r : Used to suppress the names of PDU service elements from the trace. Thisoption is valid only when you specify a pdu filter.

Valid protocols are shown in Table 3-1. If you do not specify a -p option, thenall protocols are traced.

Valid OSI processes are shown in Table 3-2.

Valid filters are shown in Table 3-3.

Table 3-1 xapiatrace Protocols

Protocol Description

p3 Traces communication between an MTA and a UA or MS.

p7 Traces communication between a UA and a MS.

Table 3-2 xapiatrace OSI Processes

Process Description

osixapia Traces the ROSE component of the osixapia daemon.

Table 3-3 xapiatrace Filters

Filters Description

events Returns status and error messages recovered from the osixapiadaemon.

pdu Returns ASN.1 decoding of incoming and outgoing messages.

debug Used to recover a full trace of the remote operation service element(ROSE) and ACSE presentation. A -d command-line option has thesame effect as this filter.


3

Finding osixapia Daemon and OSI Stack MessagesError messages, events, and other messages returned by the osixapiadaemon and the OSI stack process osinetd are logged in the file/var/SUNWconn/osinet/osilogd.log

Errors Returned by xapiatool

This section provides a list of xapiatool error messages. Each message ispresented with a brief description of the possible cause and, if applicable, asuggested action.

Note – This section does not list every error message, since most are self-explanatory.

Access denied to resourcesxapiatool does not have the correct access permissions. Make sure thatyou run the tool as superuser, or that you are not running the tool already.

Cannot access daemon resourcesxapiatool was unable to communicate with the osixapia daemon. Tofind out why, see the logfile (/var/SUNWconn/osinet/osilogd.log ).Type the following to make sure that the daemon is running:

If it is not, use x400start osixapia to start the daemon before runningxapiatool . If the daemon is running, stop it by typing x400stoposixapia then restart it.

hostname$ ps -ef | grep osixapia


3

Cannot connect to API daemonxapiatool was unable to communicate with the osixapia daemon. Tofind out why, see the logfile (/var/SUNWconn/osinet/osilogd.log ).Type the following to make sure that the daemon is running:


Cannot send command to API daemonxapiatool was unable to communicate with the osixapia daemon. Tofind out why, see the logfile (/var/SUNWconn/osinet/osilogd.log ).Type the following to make sure that the daemon is running:


Error copying daemon init fileIndicates an internal error while copying the osixapia daemoninitialization file. When you tune ROSE, changes are first sent to ROSE, thensaved in the file osixapia.init . You may have renamed this file (in whichcase rename it back to osixapia.init ), or there may be a problem withyour file system.

Error creating daemon init fileIndicates an internal error while creating the osixapia daemoninitialization file (osixapia.init ). There may be a problem with your filesystem.

Load of backup failedxapiatool was unable to restore a backup configuration. You may havespecified a file that was not a backup file generated by xapiatool , or theremay be a problem with your file system.




3

Error reading daemon init fileIndicates an internal error while reading the initialization file for theosixapia daemon (osixapia.init ). There may be a problem with yourfile system.

Too many servers configuredThe client toolkit database cannot contain more than 250 MTAs and MessageStores.

Too many clients configuredThe client toolkit database cannot contain more than 250 UAs.

Errors Indicating Rejected RFC1006 ConnectionsIf you use RFC1006 (TCP/IP) transport as provided by SunLink OSI, you mayreceive error messages indicating that connections have been rejected. Thismay be because SunLink OSI has a default connection pool size of 4. To avoidrejected connections, use ositool to increase the number of connectionsallowed per TCP/IP subnetwork. See the SunLink OSI Communication PlatformAdministrator’s Guide.


3

37

Index

Aabstract syntax notation one (ASN.1), 8application processes, 2, 10application programming interface

(API), x, 7application programs, 3applications developed with SunLink

X.400 Client Toolkit, 4association control service element

(ACSE), 32

Bbacking up a configuration, 17

Ccharacters allowed, xiiclient toolkit database, 6, 8client, See user agent (UA)configuration tool - See xapiatool

Ddefault connection pool size, 35default installation, 14delivery report, 10domain name service, 21

Eenvironment variables, setting, 14error messages, 33Ethernet, 4, 10expedited data, 29

Gglobal domain identifier, 25

Hhost name, 21

Iinclude SSAP-ID in AC SPDU, 29invalid

characters, xiiIPC (inter process communication), 9

Llength of name, xiilog file, 33, 34

Mmessage access (MA) library, 6, 7, 8


message access interface (XMA), x, 6, 7message handling system (MHS), 2message store (MS), 3

changing attributes of in the clienttoolkit database, 22

deleting from the client toolkitdatabase, 23

message store (MS) library, 6, 7message store interface (XMS), x, 6, 7message transfer agent (MTA), 3



message transfer system (MTS), 3messaging server, 3

See Also message transfer agent(MTA) and message store(MS)

messaging system, 2multiple bind, 10

Nname length, xiinetwork address, 21network type, 21

OO/R address, 25operation protocol data unit (OPDU), 9,

27organizational attributes, 25OSI stack, x, 4, 8, 12, 35

starting, 14OSI transport, 9, 13, 14osilogd.log , 33osixapia daemon, 6, 8, 9

displaying address, 27starting, 15tuning, 27

osixapia.init , 34

PP3 protocol, 7P7 protocol, 7password, 25personal name attributes, 25presentation selector, 21printing the current configuration, 18, 19propose reuse of TC, 29

Rrelaying messages, 3remote access application, 4remote operation service element

(ROSE), 9parameters, 27, 28tuning, 27

restoring a configuration, 17RFC1006

driver, x, 8rejected connections, 35transport, 9

router, See message transfer agent (MTA)routing

messages, 3

Sserver, 2session layer, 9, 21

protocol options, 29tuning, 28

session selector, 21SNMP agent, x, 8

Ttransport level interface (TLI), 9transport provider, 9, 13transport reuse connection, 29transport selector, 19, 21TRS expedited data, 29

Index 39

Uuser agent (UA), 2

adding to the client toolkitdatabase, 23, 26



Vvalid characters, xii

XX.25, 4x400tool , 19, 27x400trace , 31xapiatool , 8

error messages, 33starting, 14

xapiatrace , 31XMA, See message access interface (XMA)XMS, See message store interface (XMS)XOM interface, x, 8


Documents

Solstice X.400 Client Toolkit 9.0 Administrator's Guide · A Sun Microsystems, Inc. Business Part No.: 802-5046-10 Revision A ... machine_name% You have mail. AaBbCc123 What you …