Howard's book isn't enough. Study ibm redbooks: SG24-6198-01 (IBM WebSphere Performance, Scalability, and
High Availability) at least some chapters and SG24-6195-00 (IBM WebSphere Application Server V5.0 System Management and Configuration)
J2EE application client components may also perform transaction, but they must access the transaction directly through JNDI as follows:
UserTransaction transaction = (UserTransaction)jndiContext.lookup("jta/usertransaction");
application clients are not required to have direct access to the transaction facilities of the J2EE platform. A J2EE product is not required to provide a JTA UserTransaction object for use by application clients
Which of the following statements are false with respect to an SSL connnection? SSL can be used between an "Applet container" and:
A. the embedded HTTP Server
B an EJB COntainer
C a Web Container
D a Web Server
E client Container
I'm in doubt about this question:
9. When setting up the JMS server, in a test environment which is already running message-driven beans (MDB), which of the following properties MUST be configured to correctly communicate messages to a new MDB?
A. Queue JNDI name
B. Initial state to: Started
C. Queue name
D. Connection factory JNDI name
E. Listener port name
Select 2 answers.
Answer A is obviously wrong, E seems to be wrong too, because you set up the listener port in the DD, not in the test environment.
But, you should specify both names and jndi names for both queue and connection factory. So, A, C and D are all correct
Could you show me my mistake?
The Deployer should avoid associating more than one message-driven beanwith the same JMS Queue. If there are multiple JMS consumers for a queue, JMS doesn't define how messages are distributed between the queue receivers