The eG Installation Guide - eG Innovations

Recommendations

Info

Introduction alarm window immediately highlights the pending alarms in the target environment, prioritized based on the eG manager’s assessment of the severity of the associated problems. The previous sections have highlighted the key components of eG Enterprise. In the following chapters, we will describe the first two stages involved in deploying eG Enterprise, namely: 1. Installation of the eG manager and the agents. This stage mainly involves deployment of the software on the appropriate servers, creating user accounts, and setting up the directory structures. 2. Configuration of the eG manager and the agents. In this stage, the environment is set up for the proper operation of eG Enterprise and the manager and agent processes are started. 1.2 Factors Governing the Location of the Manager The first step in installing eG Enterprise is the installation of the eG manager. To understand the considerations that govern the exact location where the eG manager should be installed in a target environment, consider Figure 1.4, which depicts the various components of the eG manager. The discovery process is responsible for auto-discovery of the environment and for determining the configurations of the agents. To present a web-based user interface, the eG manager includes a Tomcat server for Unix environments. For Windows environment, the eG manager requires an Internet Information Server (IIS) to be co-located with it, on the same host. The various factors that should be taken into account while determining the exact location of the eG manager in the target environment are: a. Performance impact of the eG manager: For monitoring smaller environments, in which five agents or less are to be used, the eG manager can be co-located on any of the staging servers of the infrastructure. For larger environments, it is advisable that users dedicate a host for supporting the eG manager. b. Network bandwidth usage: As can be seen from Figure 1.4, several of the eG manager components communicate with the database server to store measurement results and to retrieve the results for display. Co-locating the database server with the eG manager minimizes the network bandwidth usage. Moreover, this configuration can also reduce response times seen by users accessing the eG manager. The location of the eG manager relative to the agents also governs the network bandwidth usage. For example, the eG manager may be located at an ISP site, external to the target environment. In this case, the results reported by the agents have to be communicated over an external network all the way back to the manager. To minimize network bandwidth usage, the eG manager should be located as close as possible to the agents deployed in the target environment. At the same time, since eG Enterprise’s default external agent is co-located with the manager, the eG manager should be located so that measurements made by the external agent are representative of the quality of service perceived by users of the IT infrastructure. For example, the eG manager can be located on a server that is directly connected to the access router of the IT infrastructure. Doing so ensures that the eG external agent uses the same data path that is used by users of the infrastructure. c. Firewall set-up: In Figure 1.4, while the web server/Tomcat communications are internal to the eG manager, accesses from users and agents to the eG manager involve remote communication to and from the eG manager’s web server port (7077 is the default port). If there are any firewalls used in the target environment, it is essential to ensure that the firewalls are configured to allow all communications to and from the web server component of the eG manager. In the event the eG database is hosted on a server other than the one 5
Introduction hosting the eG manager, the firewall rules should also allow the manager-database communications. Users eG Agents eG Manager Port Port 7001 7077 Apache / IIS Web Server Figure 1.4: The main components of the eG manager 1.2.1 Sizing the Hardware and Database Required by an eG Manager The hardware sizing for the eG manager and database (i.e., CPU speed, memory required, disk space required, etc.) depends on the number of servers to be monitored, the frequency of the monitoring and on the number of days of raw metrics that are to be stored in the database. eG Innovations engineers will provide a sizing calculator that will allow you to determine the hardware requirements for the eG manager and database depending on your specific requirements. 6 Port 7078 Discovery Manager Tomcat User Interface Components Port 7079 JServ Port 1521/1433 eG Database Server
Page 1 and 2: The eG Installation Guide eG Enterp
Page 3 and 4: Table of Contents INTRODUCTION.....
Page 5 and 6: 3.25 UNINSTALLING THE EG MANAGER...
Page 7 and 8: Figure 2.64: The WebLogic 7.0 conso
Page 9 and 10: Figure 3.69: The setup program requ
Page 11 and 12: Figure 3.211: The New Destination S
Page 13 and 14: Figure 3.355: Uninstall seeking con
Page 15 and 16: Introduction specification and cont
Page 17: Introduction 1.1.3 Database Figure
Page 21 and 22: Installing and Configuring on Unix
Page 69 and 70:
Installing and Configuring on Unix
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
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:
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:
Installing and Configuring on Windo
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:
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:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
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:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
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:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Configuring Double-byte Support for
Page 431 and 432:
Configuring Double-byte Support for
Page 433 and 434:
Backing up and Restoring eG Enterpr
Page 435 and 436:
Backing up and Restoring eG Enterpr
Page 437 and 438:
Configuring eG Enterprise to Work i
Page 439 and 440:
Configuring eG Enterprise to Work i
Page 441 and 442:
Configuring the eG Manager to Send
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Troubleshooting Figure 8.1: The err
Page 465 and 466:
Troubleshooting Figure 8.3: Checkin
Page 467 and 468:
Troubleshooting To start this serve
Page 469 and 470:
Troubleshooting 8.5 Installing the
Page 472:
Conclusions Conclusions eG Enterpri
show all

The eG Installation Guide - eG Innovations

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

Delete template?

Save as template?