web server - Borland Technical Publications

More documents

Recommendations

Info

Application development overview EJB 1.1 example ejb-jar.xml deployment descriptor This example uses bean-managed persistence. ShmeAdapter Interface Jar Interface EJB for SHME Class /shme/test/shmeAdapter/schema/ Customer customer_bean shme/customer_bean com.shme.test.shmeAdapter.schema.CustomerHome com.shme.test.shmeAdapter.schema.CustomerRemote com.shme.test.shmeAdapter.schema.CustomerBean Stateless Bean SHME Repository URL for Connector configuration repositoryUrl java.lang.String s_repository://S_APP01 Location of Resource Adapter configuration within the SHME Repository configurationUrl java.lang.String /shme/client Reference to SHME Resource Adapter shme/shmeAdapter com.shme.shmeAdapter.ConnectionFactory Container ejb-inprise.xml deployment descriptor This corresponds to the ejb-jar.xml above. shme/customer_bean Chapter 27: Using VisiConnect 277
Other Considerations Other Considerations shme/customer_bean 0 shme/shmeAdapter eis/shmeAdapter False Working with Poorly Implemented Resource Adapters Some commercially available Resource Adapters may be poorly implemented. As there does not yet exist any mechanism to test a Resource Adapter for compliance to the Connectors specs (as the J2EE Compatibility Test Suite (CTS) tests a Connectors implementation for spec compliance), it is currently not a simple task to recognize, but among the symptoms, you will find: 1 The Resource Adapter will exhibit strange errors during deployment 2 The Resource Adapter will exhibit strange errors during method invocation on the connection factory. As VisiConnect strictly implements J2EE 1.3 and Connectors 1.0 requirements, it is often the only Connector Container which will detect poorly implemented Resource Adapters and not ignore the problem. Examples of Poorly Implemented Resource Adapters Generally, poorly implemented Resource Adapters are not compliant with the Connectors 1.0 specification. Examples of such Resource Adapters include: ■ ■ ■ The Resource Adapter with a connection factory implementing only java.io.Serializable, and not both java.io.Serializable and javax.resource.Referenceable as per the Connectors specification (Section 10.5 “JNDI Configuration and Lookup”). The local JNDI context handlers of application servers such as Borland Enterprise Server can only register objects if they implement both interfaces. If a Resource Adapter implements a connection factory as Serializable, and doesn't implement Referenceable, you will see exceptions thrown when the application server attempts to deploy the connection factory to JNDI. The Resource Adapter with a connection factory which poorly implements javax.resource.Referenceable (which inherits getReference() from javax.naming.Referenceable). The J2SE 1.3.x and 1.4.x specs specify that for javax.naming.Referenceable, getReference() either: a Returns a valid, non-null reference of the Referenceable object, or b Throws an exception (javax.naming.NamingException). If the Resource Adapter implements Referenceable such that getReference() can (and will) return null, you will see exceptions thrown when a client attempts to invoke a connection factory method such as getConnection(). The Resource Adapter with a connection factory correctly implementing Referenceable, but which does not provide an implementation of javax.naming.spi.ObjectFactory (which is required by the Connectors specification (Section 10.5 “JNDI Configuration and Lookup”)). Although such a Resource 278 BES Developer’s Guide
Page 1 and 2:
Developer’s Guide Enterprise Serv
Page 3 and 4:
Contents Chapter 1 Introduction to
Page 5 and 6:
Entity beans . . . . . . . . . . .
Page 7 and 8:
Chapter 23 Using JMS 209 Configurin
Page 9 and 10:
Entity Bean Properties (applicable
Page 11 and 12:
Figures 0.1 Borland Enterprise Serv
Page 13 and 14:
BES Products and Editions overview
Page 15 and 16:
Documentation conventions Important
Page 17 and 18:
Contacting Borland support World Wi
Page 19 and 20:
BES services overview Figure 0.1 Bo
Page 21 and 22:
The Partition and its services ■
Page 23 and 24:
Borland Enterprise Server and J2EE
Page 25 and 26:
14 BES Developer’s Guide
Page 27 and 28:
Creating Partitions Creating Partit
Page 29 and 30:
Running Partitions Table 3.1 Option
Page 31 and 32:
Configuring Partitions You can also
Page 33 and 34:
JMX support in Partitions ■ ■ A
Page 35 and 36:
JMX support in Partitions Figure 3.
Page 37 and 38:
Thread pools Partition properties r
Page 39 and 40:
Page 41 and 42:
Apache web server implementation Fo
Page 43 and 44:
Borland web container implementatio
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Smart Agent implementation Smart Ag
Page 51 and 52:
Page 53 and 54:
Apache web server to Borland web co
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Large data transfer Downloading lar
Page 61 and 62:
Large data transfer Uploading large
Page 63 and 64:
IIS web server to Borland web conta
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Session management with JSS If an i
Page 71 and 72:
Managing and configuring the JSS Co
Page 73 and 74:
The Borland IIOP connector BES supp
Page 75 and 76:
Setting up your web container with
Page 77 and 78:
Page 79 and 80:
Web-enabling your CORBA server Impo
Page 81 and 82:
Configuring your Apache web server
Page 83 and 84:
Configuring your Apache web server
Page 85 and 86:
Web Services and Partitions ■ ■
Page 87 and 88:
Web Service providers Java:RPC prov
Page 89 and 90:
How Borland Web Services work
Page 91 and 92:
Packaging Web Service Application A
Page 93 and 94:
Tools Overview Java2WSDL tool Note
Page 95 and 96:
Page 97 and 98:
Client view of an enterprise bean L
Page 99 and 100:
Client view of an enterprise bean E
Page 101 and 102:
Managing transactions Managing tran
Page 103 and 104:
Support for JNDI Support for JNDI T
Page 105 and 106:
EJB to CORBA mapping A CORBA progra
Page 107 and 108:
Page 109 and 110:
Application Client architecture Pac
Page 111 and 112:
Document Type Definitions (DTDs) my
Page 113 and 114:
Support of references and links The
Page 115 and 116:
Use of Manifest files Use of Manife
Page 117 and 118:
Page 119 and 120:
Sessions in secondary storage If yo
Page 121 and 122:
Page 123 and 124:
Container-managed persistence and R
Page 125 and 126:
Implementing an entity bean Generat
Page 127 and 128:
Container-Managed Persistence in Bo
Page 129 and 130:
Page 131 and 132:
Setting Properties Setting Properti
Page 133 and 134:
Setting Properties into a BLOB. The
Page 135 and 136:
Setting Properties Automatic table
Page 137 and 138:
Page 139 and 140:
Container-managed persistence and R
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:
Setting Properties J2EE 1.3 Entity
Page 157 and 158:
Setting Properties Figure 16.2 Edit
Page 159 and 160:
Setting Properties Table 16.1 ejb.m
Page 161 and 162:
Setting Properties Table 16.3 Table
Page 163 and 164:
Setting Properties Security Propert
Page 165 and 166:
Aggregate Functions in EJB-QL Selec
Page 167 and 168:
Support for ORDER BY Support for OR
Page 169 and 170:
Overriding SQL generated from EJB-Q
Page 171 and 172:
Container-managed data access suppo
Page 173 and 174:
Page 175 and 176:
Generating primary keys from a cust
Page 177 and 178:
Implementing primary key generation
Page 179 and 180:
Transaction manager services Consis
Page 181 and 182:
Transaction manager services When t
Page 183 and 184:
Transaction manager services Follow
Page 185 and 186:
Declarative transaction management
Page 187 and 188:
Declarative transaction management
Page 189 and 190:
JDBC API Modifications JDBC API Mod
Page 191 and 192:
Handling of EJB exceptions Applicat
Page 193 and 194:
Page 195 and 196:
Client View of an MDB Client View o
Page 197 and 198:
Clustering of MDBs This is yet anot
Page 199 and 200:
Error Recovery Redelivered messages
Page 201 and 202:
Page 203 and 204:
JNDI Definitions Module Important s
Page 205 and 206:
Disabling and Enabling a Deployed D
Page 207 and 208:
Configuring JDBC Datasources In the
Page 209 and 210:
Configuring JDBC Datasources To add
Page 211 and 212:
Defining the Connection Pool Proper
Page 213 and 214:
Defining the Connection Pool Proper
Page 215 and 216:
Descriptions of Borland Enterprise
Page 217 and 218:
Advanced Topics for Defining JDBC D
Page 219 and 220:
Connecting to JDBC Resources from J
Page 221 and 222:
Configuring JMS Connection Factorie
Page 223 and 224:
Defining Connection Pool Properties
Page 225 and 226:
Obtaining JMS Connection Factories
Page 227 and 228:
JMS and Transactions and its accomp
Page 229 and 230:
JMS and Transactions For instance:
Page 231 and 232:
Page 233 and 234:
Configuring JMS administered object
Page 235 and 236:
Tibco Creating Clustered JMS Servic
Page 237 and 238: Sonic serverUrl String localhost:72
Page 239 and 240: Sonic Creating Clustered JMS Servic
Page 241 and 242: OpenJMS Even though OpenJMS can be
Page 243 and 244: OpenJMS Important If you use OpenJM
Page 245 and 246: OpenJMS openjms.clean_messages_on_s
Page 247 and 248: OpenJMS Table 24.1 Property Name De
Page 249 and 250: Other JMS providers The following a
Page 251 and 252: 240 BES Developer’s Guide
Page 253 and 254: Creating the Interceptor Class For
Page 255 and 256: Creating the JAR file Creating the
Page 257 and 258: Components Components The Connector
Page 259 and 260: System Contracts Connection Managem
Page 261 and 262: System Contracts Security Managemen
Page 263 and 264: Common Client Interface (CCI) Conne
Page 265 and 266: Packaging and Deployment Figure 26.
Page 267 and 268: Resource Adapters Resource Adapters
Page 269 and 270: Connection management Connection ma
Page 271 and 272: Security management with the Securi
Page 273 and 274: Security management with the Securi
Page 275 and 276: Resource Adapter overview Note Reso
Page 277 and 278: Deployment Descriptors for the Reso
Page 279 and 280: Developing the Resource Adapter Con
Page 281 and 282: Deploying the Resource Adapter Pack
Page 283 and 284: Application development overview 8
Page 285 and 286: Application development overview //
Page 287: Application development overview
Page 291 and 292: Other Considerations To illustrate,
Page 293 and 294: Other Considerations } } { cf = new
Page 295 and 296: General syntax and usage General sy
Page 297 and 298: Syntax and usage for iastool Table
Page 299 and 300: Syntax and usage for java2iiop Exam
Page 301 and 302: Syntax and usage for appclient Tabl
Page 303 and 304: Building and running the BES exampl
Page 305 and 306: Using the iastool command-line tool
Page 333 and 334: Executing iastool command-line tool
Page 335 and 336: 324 BES Developer’s Guide
Page 337 and 338: element ■ ■ ■ element The
Page 339 and 340:
element The Partition statistics ag
Page 341 and 342:
element element The services eleme
Page 343 and 344:
element element The archive elemen
Page 345 and 346:
EJB Container-level Properties Tabl
Page 347 and 348:
EJB Container-level Properties Tabl
Page 349 and 350:
EJB Customization Properties: Deplo
Page 351 and 352:
Complete Index of EJB Properties Co
Page 353 and 354:
Complete Index of EJB Properties Ta
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Java Session Service (JSS) Properti
Page 361 and 362:
Java Session Service (JSS) Properti
Page 363 and 364:
Partition Transaction Service (Tran
Page 365 and 366:
Borland-specific web DTD 33, 36 bra
Page 367 and 368:
ejb.mdb.maxMessagesPerServerSession
Page 369 and 370:
J J2EE VisiClient 97 VisiClient env
Page 371 and 372:
optimistic concurrency 130 SelectFo
Page 373 and 374:
Sonic clustered service 228 SonicMQ
Page 375:
X XML DTD 99 VisiClient 98 grammar
show all

web server - Borland Technical Publications

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

Delete template?

Save as template?