JBoss Enterprise Application Platform Common Criteria Certification ...

More documents

Recommendations

Info

16 Part II. JBoss Enterprise Application Platform 5 Configuration Part II. JBoss Enterprise Application Platform 5 Configuration
JBoss Enterprise Application Platform Common Criteria Certification 5 Administration And Configuration Guide 17 Chapter 3. Logging Logging is the most important tool to troubleshoot errors and monitor the status of the components of the Platform. log4 j provides a familiar, flexible framework, familiar to Java developers. Section 3.1, “Logging Defaults” contains information about customizing the default logging behavior for the Platform. See Section 3.2, “Component-Specific Logging” for additional customization. Appendix B, Logging Information and Recipes provides some logging recipes, which you can customize to your needs. 3.1. Logging Defaults The log4 j configuration is loaded from the JBOSS_HOME/server/PROFILE/conf/jboss-log4j.xml deployment descriptor. log4 j uses appenders to control its logging behavior. An appender is a directive for where to log information, and how to do it. The jboss-log4j.xml file contains many sample appenders, including FILE, CONSOLE, and SMTP. Table 3.1. Common log4 j Configuration Directives Configuration Option Description appender The main appender. Gives the name and the implementing class. errorHandler Delegates an external class to handle exceptions passed to the logger, especially if the appender cannot write the log for some reason. param Options specific to the type of appender. In this instance, the is the name of the file that stores the logs for the FILE appender. layout Controls the logging format. Tweak this to work with your log-parsing software of choice. Example 3.1. Sample Appender For more information on configuring log4 j, see http://logging.apache.org/log4j/1.2/. 3.2. Component-Specific Logging Some Platform components have extra logging options available, or extra mechanisms for customizing logging. 3.2.1. SQL Logging with Hibernate Hibernate has two ways to enable logging of SQL statements. These statements are most useful during the testing and debugging phases of application development.
Page 1 and 2: JBoss Enterprise Application Platfo
Page 3 and 4: Abstract JBoss Enterprise Applicati
Page 11 and 12: Chapter 1. Introduction JBoss Enter
Page 15: JBoss Enterprise Application Platfo
Page 19 and 20: Chapter 4. Deployment Deploying app
Page 21 and 22: web JBoss Enterprise Application Pl
Page 23 and 24: Chapter 6. The JNDI Naming Service
Page 33 and 34: Example 6.2. A JNDI client that use
Page 53 and 54: @XmlAccessorType(XmlAccessType.FIEL
Page 57 and 58: 7.15. WebServiceContext The WebServ
Page 59 and 60: ** * The getPort method returns a p
Page 61 and 62: Message Payload In this mode, clien
Page 67 and 68:
JBoss Enterprise Application Platfo
Page 69 and 70:
Page 71 and 72:
@WebServiceClient(name = "EchoServi
Page 73 and 74:
@WebService(name = "StatefulEndpoin
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:
** * Creates a Jaxr Organization wi
Page 91 and 92:
Page 93 and 94:
** * Annotation for specifying the
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
that have not completed after a spe
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Oracle 10g: org.hibernate.dialect.O
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:
That's it; that's all it takes to g
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Application Platform ships with a d
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:
ean. By default true, since replica
Page 165 and 166:
a different physical host. If not a
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:
deployment (war, ear, jar, whatever
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:
The available attributes in the FD
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:
import org.jboss.ha.cachemanager.Ca
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Example A.10. Sybase Datasource [ 1
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Example A.25. PostgreSQL XA Datasou
Page 255 and 256:
Example B.2. Filtering App1 Log Out
show all

JBoss Enterprise Application Platform Common Criteria Certification ...

Create successful ePaper yourself

Delete template?

Save as template?