ER/Studio - Embarcadero Technologies Product Documentation

More documents

Recommendations

Info

ADMINISTRATOR’S REFERENCE > UNDERSTANDING AND MAINTAINING THE REPOSITORY Repository Architecture and Design The Repository relies on a native client connection and the TCP/IP protocol to send and receive information between ER/Studio, the Repository Server, and the Repository Database. There is a metadata diagram of the Repository schema in the SystemModels directory (Repository300MetaModel.dm1). It includes relationships between entities as documentation whereas the actual database, for performance reasons, does not include FK constraints. The file shows the propagation chain which could be helpful for writing queries to run against the Repository. For a complete list of software and installation requirements, and supported Repository Databases, see the Installation Guide. Repository Client ER/Studio provides the user interface for the Diagram data stored in the Repository. The ER/Studio Repository menu gives you access to all Repository functions and features. To access and use the Repository, you must have ER/Studio running. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 322
ADMINISTRATOR’S REFERENCE > MANAGING REPOSITORY FILES Repository Server The Repository Server links ER/Studio to the Repository Database. The Repository Server contains the SQL code necessary to query the database to retrieve data or to insert data into the database. The Repository Server runs this code when it receives a request to execute an operation that requires it to read data in the database and return the appropriate information and when it receives a request to execute an operation that requires it to write new data to the database. NOTE: Because the Repository Server is responsible for inserting data into the database, and retrieving data from the database, you can only have one Repository Server for each Repository Database. The Repository Server manages the state of the Repository data, which it stores in the Repository database. It records modeling change operations as requested by ER/Studio users. When the server receives a request, it does the following: 1 Checks to make sure the user has the necessary permissions to perform the operation. 2 If the operation requests data from the Repository database, the server retrieves the data from the database and sends it to the ER/Studio instance from which the request originated. 3 If the operation attempts to store data in the Repository database, the Repository Server writes the data out to the database. 4 Notifies all ER/Studio “clients” of the new state of the Repository and sends them the appropriate information to update the displays. Managing Repository Files The Repository Server installation includes several folders, described below. Depending on your configuration options, particularly if the -deleteoff option is set on your server, you may want to manually remove older files collecting in your Repo In/Out folders as described here. It is always safe to delete a .pri or .pro file. It is safe to delete any files with old dates since the files are generally processed immediately upon being written to the directory. This applies to .out and .err files. Files with a .in extension should not be deleted and should not be in the folders for more than the time it takes to process them, unless the Repo Services have been stopped. Folder Description Repository This folder contains the Repository subfolders, listed below. It also contains the executable files for the three Repository services, along with the Repository Server Licensing application, a copy of the license agreement, and a copy of a compiled help file that contains information about installing and licensing the Repository. Logs This folder is a subdirectory of the Repository folder. It is used to store log files that are used by each of the Repository services to store information about events or transactions. RepoIn Stores the request files received from an ER/Studio client until they are processed by the server. If you have older files collecting here: 1. Open the directory in the Windows Explorer. 2. Sort the files by Date Modified with the oldest files at the top. 3. Select all files starting from the top and stopping wherever you feel safe. A good idea is to select all files modified before the current day. 4. Delete those files. RepoOut Stores files being sent from the Repository server to the ER/Studio client until they are processed. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 323
Page 1 and 2:
ER/Studio® 8.0.3 User Guide
Page 3 and 4:
Contents Welcome to ER/Studio . . .
Page 5 and 6:
CONTENTS Enhancing Data Integrity U
Page 7 and 8:
CONTENTS Optimizing Repository Perf
Page 9 and 10:
Welcome to ER/Studio ER/Studio is a
Page 11 and 12:
WELCOME TO ER/STUDIO > DATABASE SUP
Page 13 and 14:
ER/STUDIO OVERVIEW > ER/STUDIO FAMI
Page 15 and 16:
ER/STUDIO OVERVIEW > APPLICATION IN
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
ER/STUDIO OVERVIEW > CONFIGURING AN
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
ER/STUDIO OVERVIEW > DATA MODELING
Page 37 and 38:
ER/STUDIO OVERVIEW > DEVELOPING A D
Page 39 and 40:
Using ER/Studio This section includ
Page 41 and 42:
USING ER/STUDIO > CREATING AND WORK
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
USING ER/STUDIO > BEST PRACTICES 8
Page 65 and 66:
USING ER/STUDIO > COMMON TASKS Comm
Page 67 and 68:
USING ER/STUDIO > COMMON TASKS Movi
Page 69 and 70:
USING ER/STUDIO > COMMON TASKS Copy
Page 71 and 72:
USING ER/STUDIO > COMMON TASKS Chan
Page 73 and 74:
USING ER/STUDIO > COMMON TASKS 3 To
Page 75 and 76:
USING ER/STUDIO > COMMON TASKS The
Page 77 and 78:
USING ER/STUDIO > COMMON TASKS 4 Co
Page 79 and 80:
USING ER/STUDIO > COMMON TASKS Sync
Page 81 and 82:
USING ER/STUDIO > COMMON TASKS In c
Page 83 and 84:
USING ER/STUDIO > COMMON TASKS Adva
Page 85 and 86:
USING ER/STUDIO > COMMON TASKS Asso
Page 87 and 88:
USING ER/STUDIO > COMMON TASKS Comp
Page 89 and 90:
USING ER/STUDIO > COMMON TASKS Dime
Page 91 and 92:
USING ER/STUDIO > COMMON TASKS •
Page 93 and 94:
USING ER/STUDIO > COMMON TASKS See
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
USING ER/STUDIO > COMMON TASKS 3 In
Page 103 and 104:
USING ER/STUDIO > COMMON TASKS Chan
Page 105 and 106:
Page 107 and 108:
USING ER/STUDIO > COMMON TASKS Shap
Page 109 and 110:
USING ER/STUDIO > COMMON TASKS Addi
Page 111 and 112:
USING ER/STUDIO > DEVELOPING THE LO
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
USING ER/STUDIO > DEVELOPING THE PH
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
USING ER/STUDIO > WORKING WITH THE
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
USING ER/STUDIO > DOCUMENTING DATA
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
USING ER/STUDIO > SAVING AND USING
Page 251 and 252:
USING ER/STUDIO > GENERATING RTF AN
Page 253 and 254:
USING ER/STUDIO > EXPORTING THE DAT
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272: USING ER/STUDIO > EXPORTING THE DAT
Page 273 and 274: USING ER/STUDIO > EXPORTING THE DAT
Page 275 and 276: USING ER/STUDIO > EXPORTING AN IMAG
Page 277 and 278: WORKING WITH THE REPOSITORY > WORKI
Page 297 and 298: WORKING WITH THE REPOSITORY > CANCE
Page 299 and 300: AUTOMATING ER/STUDIO > Related Topi
Page 301 and 302: AUTOMATING ER/STUDIO > Object Model
Page 303 and 304: AUTOMATING ER/STUDIO > Macros which
Page 305 and 306: AUTOMATING ER/STUDIO > Meta Data Ma
Page 307 and 308: AUTOMATING ER/STUDIO > • Definiti
Page 309 and 310: AUTOMATING ER/STUDIO > Access ER/St
Page 311 and 312: AUTOMATING ER/STUDIO > You can cust
Page 313 and 314: AUTOMATING ER/STUDIO > The table be
Page 315 and 316: AUTOMATING ER/STUDIO > Click the ?
Page 317 and 318: Administrator’s Reference This se
Page 319 and 320: ADMINISTRATOR’S REFERENCE > CONNE
Page 321: ADMINISTRATOR’S REFERENCE > UNDER
Page 325 and 326: ADMINISTRATOR’S REFERENCE > MANAG
Page 327 and 328: ADMINISTRATOR’S REFERENCE > MANAG
Page 329 and 330: ADMINISTRATOR’S REFERENCE > ESTAB
Page 337 and 338: Tutorials The tutorials are intende
Page 339 and 340: TUTORIALS > GETTING STARTED WITH ER
Page 341 and 342: TUTORIALS > LOGICAL AND PHYSICAL MO
Page 355 and 356: TUTORIALS > DOCUMENTING AN EXISTING
Page 363 and 364: TUTORIALS > DOCUMENTING DATA LINEAG
Page 373 and 374:
TUTORIALS > DIAGRAM NAVIGATION AND
Page 375 and 376:
TUTORIALS > DIAGRAM NAVIGATION AND
Page 377 and 378:
TUTORIALS > IMPORTING AND EXPORTING
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
TUTORIALS > DIMENSIONAL MODELING Si
Page 385 and 386:
TUTORIALS > DIMENSIONAL MODELING Wo
Page 387 and 388:
TUTORIALS > AUTOMATING TASKS Automa
Page 389 and 390:
TUTORIALS > AUTOMATING TASKS 7 Name
Page 391 and 392:
TUTORIALS > COLLABORATIVE MODELING
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Glossary A Active File Directory: T
Page 411 and 412:
GLOSSARY Denormalization: The inten
Page 413 and 414:
GLOSSARY M Macro: Code written in t
Page 415 and 416:
GLOSSARY S Scale: The scale of a nu
Page 417 and 418:
Index Symbols 284, 299, 308 @var su
Page 419 and 420:
INDEX Metadata Import Options 44 Me
Page 421:
INDEX Adding a Macro 315 Deleting a
show all

ER/Studio - Embarcadero Technologies Product Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?