Getting Started with WebSphere Application Server

More documents

Recommendations

Info

202 Getting Started with WebSphere Application Server Community Edition 11.5.6.1 DB2 Administration Notification Log The DB2 administration notification log provides diagnostic information about errors at the point of failure. On Linux and UNIX platforms, the administration notification log is a text file called .nfy (e.g. “db2inst.nfy”). On Windows, all administration notification messages are written to the Windows Event Log. 11.5.6.2 db2diag.log The db2diag.log provides more detailed information than the DB2 Administration notification log. It is normally used only by IBM DB2 technical support or experienced DBAs. Information in the db2diag.log includes: • The DB2 code location reporting an error. • Application identifiers that allow you to match up entries pertaining to an application on the db2diag.logs of servers and clients. • A diagnostic message (beginning with "DIA") explaining the reason for the error. • Any available supporting data, such as SQLCA data structures and pointers to the location of any extra dump or trap files. On Windows (other than Vista), the db2diag.log is located by default under the directory: C:\Documents and Settings\All Users\Application Data\IBM\DB2\DB2COPY1\ On Windows Vista, the db2diag.log is located by default under the directory: C:\ProgramData\IBM\DB2\DB2COPY1\ On Linux/UNIX, the db2diag.log is located by default under the directory: /home//sqllib/db2dump 11.5.7 System.out and System.err If you start the Community Edition server with the script startup.bat (on Windows) or startup.sh (On Linux and UNIX), System.out and System.err messages will be generated. In Windows, a new console will be opened to show all the messages. In Linux, AIX, or Solaris, all the output will be recorded in a log file under /var/log, the file is named server.out. 11.6 Summary This chapter discussed some common problems users may encounter when working with a Community Edition server, and how to troubleshoot them. The chapter focused on install/uninstall, start/shutdown, and deployment problems. It also discussed how to analyze log files for problem diagnosis. More details about troubleshooting can be found in
Chapter 11 – Troubleshooting 203 the Troubleshooting and FAQ sections of the online Community Edition User’s Guide at http://publib.boulder.ibm.com/wasce/V2.1.1 You can also post questions in the Community Edition forum at: http://www.ibm.com/developerworks/forums/forum.jspa?forumID=541&start=0 11.7 Review questions 1. How do you uninstall all the files in the Community Edition installation directory? 2. How do you specify the JVM path when you start/stop a Community Edition server? 3. How do you set a port offset for Community Edition? 4. How do you specify an RMI host? 5. Where are the log files of Community Edition? 6. Which option can you use to specify the JVM location when you install a Community Edition server? A. LAX B. VM C. LAX_VM D. JAVA E. JVM 7. Which of the following is not a log file generated by Community Edition installation? A. wasce_install_information.txt B. wasce_install_2010-01-01_01-01-01.log C. wasce_uninstall_information.txt D. wasce_uninstall_2010-01-02_01-01-01.log E. wasce.log 8. Which of the following are solutions to resolve port number conflicts? A. Change the value of portOffset in substitutions.properties B. Shutdown other applications which were using the port number C. Restart Community Edition server D. Re-install Community Edition E. Uninstall Community Edition
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:
Page 152 and 153: 152 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

Create successful ePaper yourself

Delete template?

Save as template?