This chapter, 'Building a Combined WebSphere and Domino System' is excerpted from the new book, IBM WebSphere and Lotus: Implementing Collaborative Solutions, authored by John Lamb, Michael Laskey and Gopal Indurkhya. Copyright International Business Machines Corporation 2005. ISBN 0-13-144330-5. To learn more, www.phptr. com/title/0131443305.

This chapter, 'Build and Deploy Procedures' is excerpted from the new book, IBM WebSphere: Deployment and Advanced Configuration, authored by Roland Barcia, Bill Hines, Tom Alcott and Keys Botzum. © International Business Machines Corporation 2005.

The following sections describe the different categories of network security. Identity is the identification of network users, hosts, applications, services, and resources. Examples of technologies that enable identification include Remote Authentication Dial-In User Service (RADIUS), Kerberos, one-time passwords, digital certificates, smart cards, and directory services.

Having established an understanding of our unit of exchange - the message - we are now ready to delve into the mechanics of messaging using the JMS API. In this chapter we begin with a discussion on implementation choices, examining our options regarding the software components with which we might implement a JMS client.

The topic of transactions is one that most Java programmers would rather ignore than try to understand. And, in fact, in most cases you can ignore them - the default settings of WebSphere Application Server (WAS) and WebSphere Studio Application Developer work well enough in most situations that many programmers can build large and complex applications without having to know the details of how transactions work.