Getting Started with WebSphere Application Server

More documents

Recommendations

Info

200 Getting Started with WebSphere Application Server Community Edition Both the install and un-install log files are located at directory where is the user primary directory in the operating system. In Windows, is in C:\Document and Settings\ directory; while in Linux and UNIX it is in /home/ directory. Table 11.2 below provides the file names for the install and uninstall log files and their description. Log file name wasce_install_information.txt wasce_install_YYYY-MM-DD_HH- MM-SS.log wasce_uninstall_information.t xt wasce_uninstall_YYYY-MM- DD_HH-MM-SS.log Description Records every variable being revoked during installation. Records system variable settings and JVM information during installation, where YYYY- MM-DD_HH-MM-SS is a timestamp. Records every variable being revoked during uninstallation. Records system variable settings and JVM information during uninstallation, where YYYY-MM-DD_HH-MM-SS is a timestamp. Table 11.2 - File name for install and uninstall logs 11.5.2 Server log Messages from the server, applications and deployment are logged to the /var/log/server.log file. The file location, name, and the log levels can be changed by editing the /var/log/server-log4j.properties file. For example, if you would like to change the root log level to DEBUG, you can change the log4j.appender.FILE.Threshold property in the server-log4j.properties to this value as shown in Listing 11.2. log4j.rootLogger=DEBUG, CONSOLE, FILE log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender log4j.appender.CONSOLE.Threshold=${org.apache.geronimo.log.ConsoleLogLe vel} log4j.appender.CONSOLE.Target=System.out log4j.appender.CONSOLE.lausert=org.apache.log4j.PatternLausert log4j.appender.CONSOLE.lausert.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m%n log4j.appender.FILE=org.apache.log4j.RollingFileAppender log4j.appender.FILE.Threshold=DEBUG log4j.appender.FILE.lausert=org.apache.log4j.PatternLausert log4j.appender.FILE.lausert.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m%n Listing 11.2 - Sample of server-log4j.properties file
Chapter 11 – Troubleshooting 201 The server-log4j.properties file can also be edited from the admin console by selecting the Server Logs portlet. With the admin console, you can also filter the server.log entries. In Linux, AIX, or Solaris users can use the tail -f server.log command to display current entries to the server.log file while the server is running. 11.5.3 Client log Messages from Java EE client applications are written to the file /var/log/client.log. Similar to server.log, you can change the file location, name and the log levels by editing the /var/log/clientlog4j.properties. 11.5.4 Deployer log Messages are generated when an application is deployed to a server. These messages are logged to the /var/log/deployer.log file. You can change the file location, name and the log levels in /var/log/deployerlog4j.properties. 11.5.5 Web log HTTP requests to the Web container are logged. The HTTP request information includes the type of request (GET or POST), the time of access, and other related data. You can see the access log files in the /var/catalina/logs folder. The file name has the format: _access_log..txt For example, 0.0.0.0_access_log.2010-06-29.txt, records all the access information on 2010.06.29 from every client. From the admin console you can review and edit the Web server log file and edit its properties by selecting Server Logs -> Web Access Log Viewer. With the admin console, you can use a filter to narrow down log entries. 11.5.6 DB2 database log DB2 database log files include information about the DB2 database server, such as database startup and shutdown information. There are two main logs: • DB2 Administration Notification log • db2diag.log
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7 and 8:
Trademarks IBM, the IBM logo, and i
Page 9 and 10:
3.8 Exercises .....................
Page 11 and 12:
9.3.2 Changing port numbers .......
Page 13 and 14:
13 Preface Keeping your skills curr
Page 15:
The DB2 on Campus book series 15
Page 18 and 19:
18 Getting Started with WebSphere A
Page 21 and 22:
1 Chapter 1 - Introduction to WebSp
Page 23 and 24:
Introduction to WebSphere Applicati
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 47 and 48:
3 Chapter 3 - Development with Comm
Page 49 and 50:
Chapter 3 - Development with Commun
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:
4 Chapter 4 - Working with database
Page 67 and 68:
Chapter 4 - Working with databases
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:
5 Chapter 5 - Enterprise Java Beans
Page 91 and 92:
1. Define local and remote interfac
Page 93 and 94:
Chapter 5 - Enterprise Java Beans 9
Page 95 and 96:
Page 97 and 98:
Note: Chapter 5 - Enterprise Java B
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
6 Chapter 6 - Messaging Messaging i
Page 111 and 112:
Chapter 6 - Messaging 111 3. Messag
Page 113 and 114:
Chapter 6 - Messaging 113 2. Get JM
Page 115 and 116:
Chapter 6 - Messaging 115 Figure 6.
Page 117 and 118:
Chapter 6 - Messaging 117 Figure 6.
Page 119 and 120:
Chapter 6 - Messaging 119 For examp
Page 121 and 122:
textMessage.getText()); } catch (JM
Page 123 and 124:
Chapter 6 - Messaging 123 3. Copy t
Page 125:
Chapter 6 - Messaging 125 D. Messag
Page 128 and 129:
128 Getting Started with WebSphere
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151: 150 Getting Started with WebSphere
Page 161: PART III - ADMINISTERING COMMUNITY
Page 181 and 182: 10 Chapter 10 - Tuning a Community
Page 183 and 184: Chapter 10 - Tuning a Community Edi
Page 191 and 192: 10.4.2 Operating system tuning Chap
Page 193: Chapter 10 - Tuning a Community Edi
Page 211 and 212: A Appendix A - Solutions to review
Page 213 and 214: Appendix A - Solutions to review qu
Page 219 and 220: B Appendix B - Up and running with
Page 221 and 222: Appendix B - Up and running with DB
Page 223 and 224: 4. The following is performed by de
Page 235: C Appendix C - Using the sample cod
Page 240: 240 Getting Started with WebSphere
show all

Getting Started with WebSphere Application Server

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

Delete template?

Save as template?