Managing Arcsde Application Servers
Total Page:16
File Type:pdf, Size:1020Kb
ArcGIS® 9 Managing ArcSDE ® Application Servers Copyright © 1999–2005 ESRI All rights reserved. Printed in the United States of America. The information contained in this document is the exclusive property of ESRI. This work is protected under United States copyright law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system, except as expressly permitted in writing by ESRI. All requests should be sent to Attention: Contracts Manager, ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. The information contained in this document is subject to change without notice. U.S. GOVERNMENT RESTRICTED/LIMITED RIGHTS Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. In no event shall the U.S. Government acquire greater than RESTRICTED/LIMITED RIGHTS. At a minimum, use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR §52.227-14 Alternates I, II, and III (JUN 1987); FAR §52.227-19 (JUN 1987) and/or FAR §12.211/12.212 (Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (NOV 1995) (Technical Data) and/or DFARS §227.7202 (Computer Software), as applicable. Contractor/Manufacturer is ESRI, 380 New York Street, Redlands, CA 92373-8100, USA. ESRI, SDE, ArcView, MapObjects, the ESRI globe logo, ArcInfo, ArcSDE, ArcCatalog, ArcEditor, ArcMap, ArcGIS, ArcIMS, ArcStorm, Arc Objects, StreetMap, ArcInfo Librarian, GIS by ESRI, and www.esri.com are trademarks, registered trademarks, or service marks of ESRI in the United States, the European Community, or certain other jurisdictions. The names of other companies and products herein are trademarks or registered trademarks of their respective trademark owners. Contents 1 Introducing the ArcSDE application server 1 The ArcSDE application server 2 Properties of an ArcSDE application server 4 Tips on learning about the ArcSDE application server 5 2 Creating ArcSDE application servers 7 The ArcSDE home directory 8 The DBMS database 9 The ArcSDE DBMS administration account 10 The ArcSDE service on UNIX and Windows 11 Windows installs 12 Accessing an ArcSDE application server through a firewall 14 3 Configuring ArcSDE application servers 15 The services.sde file 16 Operating system services files 18 The service name on Windows 19 ArcSDE DBMS environment variables 20 ArcSDE system environment variables 21 The dbinit.sde file format 23 Displaying ArcSDE system environment variables 24 Adjusting ArcSDE application server initialization parameters 25 Displaying the ArcSDE initialization parameters 38 4 Managing ArcSDE application servers 39 Before starting an ArcSDE application server 40 Starting a local ArcSDE application server on Windows 41 Starting a remote ArcSDE application server on Windows 42 Starting a local ArcSDE application server on UNIX 43 The sdemon command output 44 Starting a remote ArcSDE application server on UNIX 45 Pausing, resuming, and shutting down an ArcSDE application server 46 III Shutting down an ArcSDE application server during the editing of a multiversioned table 49 Removing ArcSDE sessions (Windows and UNIX) 50 5 Monitoring ArcSDE application servers 53 Displaying ArcSDE application server status and lock table information 54 How ArcGIS uses ArcSDE locking 56 Displaying ArcSDE application server statistics 57 Displaying ArcSDE user session information 58 6 Troubleshooting the ArcSDE application server 59 What happens when you start an ArcSDE application server 60 What happens when an ArcSDE client connects to an application server 62 What happens when an ArcSDE client direct connects to the DBMS 64 Common ArcSDE startup problems on UNIX servers 65 Common ArcSDE startup problems on Windows servers 67 Setting the Windows SharedSection 69 The Windows Event Viewer 70 Examining the ArcSDE error logfiles 71 ArcSDE intercept 72 ArcSDE tracing 73 A ArcSDE data dictionary 75 B ArcSDE table definitions 97 C ArcSDE application server command references 113 D ArcSDE initialization parameters 125 IV MANAGING ARCSDE APPLICATION S ERVERS Glossary 133 Index 143 CONTENTS V Introducing the ArcSDE application server 1 IN THIS CHAPTER This chapter introduces the key components of the ESRI® ArcSDE® application server and provides an overview of the underlying configuration. Subsequent • The ArcSDE application server chapters discuss the creation, configuration, and management of the ArcSDE application server. The appendices contain descriptions of the ArcSDE home • Properties of an ArcSDE applica- tion server directory, the data dictionary, table definitions, listings of the ArcSDE commands, and the ArcSDE initialization parameters. • Tips on learning about the ArcSDE application server 1 The ArcSDE application server An ArcSDE application server conveys spatial data between geographic information system (GIS) applications and a database. The database may be any one of the supported database management systems (DBMSs) such as Oracle®, SQL Server™, Informix®, or DB2®. The database could also be a registered collection of ArcGIS® coverages or shapefiles. The applications that can connect to and access spatial data from an ArcSDE application server include ArcGIS Desktop, ArcIMS®, ArcView® 3, ArcInfo™ Workstation, MapObjects®, and ArcSDE CAD Client, as well as custom-built applications created by either you or an ESRI business partner. Two-tiered versus three-tiered architecture ArcSDE provides two alternative methods of connecting to the database instance—direct connection to the database instance in a two-tiered architecture or connecting through the ArcSDE application server in a three-tiered architecture. If it is your intention to adopt the two-tiered approach, then you should consult the Appendix titled ‘Making a Direct Connection’ in the ArcSDE Configuration and Tuning Guide for <DBMS> PDF file, located in the documentation folder on the ArcSDE CD. This guide is primarily concerned with the administration of the ArcSDE application server. However, information concerning such things as the management of server configuration parameters (Chapter 3 and Appendix D) and troubleshooting (Chapter 6) also apply to direct connections. 2 MANAGING ARCSDE APPLICATION S ERVERS The sdemon command allows the administrator to manage and monitor the ArcSDE service. Managed by sdemon C1 Connection request C3 Connection request Client 1 Client 3 Individual client (for example, ArcView GIS) (for example, ArcIMS) connections to the ArcSDE C2 Connection request C4 Connection request application ArcSDE Server Process—"giomgr" server. Listens for connection requests Verifies connection (username/password) Client 2 Client 4 (for example, ArcInfo) Spawns one dedicated "gsrvr" process per (for example, CAD Client) successful connection ArcSDE service—the giomgr process— manages client connections. C1 gsrvr C4 gsrvr Dedicated gsrvr processes— communicate with the DBMS on behalf of the client. DBMS INTRODUCING THE ARCSDE APPLICATION SERVER 3 Properties of an ArcSDE application server The ArcSDE application server, a client/server configuration, The Transmission Control Protocol/Internet Protocol has a number of defining properties; these are introduced in the service name and port number following sections. The ArcSDE application server, through the giomgr process, The home directory listens for application connection requests on a dedicated TCP/IP service name and port number. The gsrvr process, in Each ArcSDE application server has its own home directory, turn, communicates with the application on the same TCP/IP which is defined by the system variable, SDEHOME. The home service and port number. All communication between the directory contains the ArcSDE binary executable files, dynamic applications and the ArcSDE application server take place using shared libraries, configuration files, and internationalization the TCP/IP service name and port number. code pages. The configuration parameters The ArcSDE application server monitor—the giomgr process The ArcSDE application server can be configured to optimize the data flow between the connected applications and the database. Each ArcSDE application server has one giomgr process. This The configuration parameters are stored in the process listens for user application connection requests, spawns SDE.SERVER_CONFIG metadata table, making them accessible to gsrvr processes, and cleans up disconnected user processes. multiple application servers and direct connections. The The giomgr will not start if a valid server license has not been parameters are managed by editing the configuration files and installed. Contact ESRI customer support if you have not loading the values into the SDE.SERVER_CONFIG table. The already obtained a valid license. default configuration file, giomgr.defs, is located in the etc folder of SDEHOME. The gsrvr process The giomgr process spawns a gsrvr process for each application connected to the ArcSDE application server. The gsrvr process is dedicated to a single-user application connection. It communicates with the database on behalf of the connected application. The gsrvr process responds to the application’s query and edit requests to the database. 4 MANAGING ARCSDE APPLICATION S ERVERS Tips on learning about the ArcSDE application server About this book This book is designed to help you create and maintain an ArcSDE application