The eG Installation Guide - eG Innovations

Recommendations

Info

Installing and Configuring on Windows Environments 3. When Figure 3.201 appears, select the Schermata iniziale e account di sistema check box (i.e., the Welcome screen and system accounts check box in English) therein and click the OK button to copy the current user's settings to the system accounts. Figure 3.201: Copying the current user's settings to the system accounts The following services are started when the eG agent is installed. The services are: • eGurkhaAgent (core agent process) • eGAgentMon (agent recovery process) If the status corresponding to the eGurkhaAgent service shows “Started”, then it implies that the agent has been started successfully. Please check the \agent\logs\error_log file to find out the reasons due to which the agent failed to start. In Windows environments, executing the eG agent in the debugon mode automatically triggers error logging. The steps involved in this process are detailed below: 1. Stop the eG agent. 2. Run the debugon.bat file in the \lib directory by double-clicking on it. 3. Finally, restart the eG agent. 307
Installing and Configuring on Windows Environments 4. Upon restarting, the following files will be automatically created in the \agent\logs directory: The agentout.log file, which records details of the tests run and measures reported by the agent to the manager The agenterr.log and error_log files to which the runtime errors encountered by the eG agent are logged The agentupgrade.log file which provides the agent upgrade status. 5. The errors (if any) will be logged in the error_log file that will be automatically created in the \agent\logs directory. You can ‘switch off’ error logging if so required, by running the debugoff.bat file in the \lib directory. 3.19 Performance Impact of the eG Agent The resource utiliation of an eG agent is dependent on various factors including: the number of components that are being monitored by the eG agent; the specific component types to be monitored; the frequency of monitoring; whether the agent is monitoring applications in an agent-based or an agentless manner; For an internal agent monitoring a single application on the server at a 5 minute frequency, the agent typically consumes 0.1-0.3% of CPU. Network traffic generated by the agent is about 0.05 – 0.2 kbps. The size of the agent on disk is about 100 MB. When the agent is started, its memory footprint will be about 10-15 MB additional to that of the Java Virtual Machine. In total, the eG agent process consumes 30 – 50 MB of memory. For an agent that monitors multiple applications on a server, or for an agent that monitors components in an agentless/external manner, the CPU, memory, and network bandwidth usage will be higher. 3.20 Increasing the Memory of the eG Agent The eG agent runs as a Java process. The maximum heap memory that can be allocated to a 32-bit eG agent process is limited to 1.5 GB. The maximum heap memory allocation to a 64-bit eG agent process on the other hand, is limited to 3 GB. If an eG agent has been configured to monitor many components, then, you may have to allocate more heap memory to the eG agent. In such a case, follow the steps below for a Windows agent: 1. Login to the eG agent host. 2. Edit the debugon.bat or debugoff.bat file in the \lib directory. 3. Look for the entry -Xmx in the file. You will find the following entry: -Xmx128M 4. From the Xmx specification, you can infer that by default, a maximum of 128 MB of memory has been allocated to the eG agent. If you want to increase the heap memory allocation to say, 256 MB, then your specification should be changed as indicated below: -Xmx256M 308
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 and 18:
Introduction 1.1.3 Database Figure
Page 19 and 20:
Introduction hosting the eG manager
Page 21 and 22:
Installing and Configuring on Unix
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
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:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
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: Installing and Configuring on Windo
Page 319: Installing and Configuring on Windo
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

Create successful ePaper yourself

Delete template?

Save as template?