C.1 Platform Requirements
| For reasons of mobility and convenience, I chose to develop the samples on Open Source software and publicly available software on a notebook PC to illustrate the concepts and technology in this book. I have also verified and tested it on Solaris OE version 8 on an Ultra-10 system. Conceptually, these examples should be executable on any Unix operating system with minor modification of the class paths. Obviously, there are small platform differences in Unix when specifying the file name and path notation; for example, the Windows platform uses a backslash "\" while Unix uses a forward slash "/". The details should be referred to in the individual software product. C.1.1 Hardware RequirementsThe minimal hardware platform is recommended to be a Pentium 3 processor with a 400MHz CPU, 128MB RAM and at least 400MB additional hard disk space. You will require another 200MB or more to install the optional components . The sample programs in this book are tested on a Pentium 3 notebook PC with 700MHz CPU, 256MB RAM, and a 30GB hard disk, as well as on an Ultra-10 with 128MB RAM and a 20GB hard disk running on Solaris OE version 8. C.1.2 Software RequirementsThe sample programs are tested on Windows 2000 and Solaris OE version 8, respectively. The software products listed in Tables C-1 and C-2 are used to support the sample programs and the Case Study in this book. The software used here will likely have newer versions by the time the book is published. Conceptually, the installation procedures should be similar, and the set-up files will have slightly different file names . Please note that you may need to check the compatibility in the release notes, revalidate the set-up, and retest all sample programs if you use a newer software release. If you are using the Unix platform, you also need to verify the file locations in the build.properties (such as the environment variable docs.path), build.xml, and in the source program files (such as the file location for the " sample_soap_keystore " in the file ProfileServlet.java ). Netegrity's jSAML Toolkit version 1.0, which comes with an existing Single Sign-on sample program, is used here to illustrate Single Sign-on integration using Security Assertion Markup Language (SAML). Liberty specification (for cross-domain Single Sign-on and federated identity management) is already available online at http://www.projectliberty.org . There have been recent updates to SAML since then. Netegrity's jSAML Toolkit does not have any new updates to support these new changes yet. Thus, the software toolkit is used, for instruction purposes, as it is, and there are likely some architectural or software changes required in order to be compliant with the latest SAML or Liberty specifications. Sun ONE Identity Server 6.0 ( http://wwws.sun.com/software/products/identity_srvr/home_identity.html ) now provides a similar SAML toolkit and supports the latest SAML and Liberty specifications. VeriSign's Trust Service Integration Kit is an up-to-date toolkit to support XML Key Management Specification and WS-Security. Core Software ComponentsTable C-1. Core System Components Used in This Book
Optional Software ComponentsTable C-2. Optional System Components Used in This Book
|
- Challenging the Unpredictable: Changeable Order Management Systems
- Context Management of ERP Processes in Virtual Communities
- Distributed Data Warehouse for Geo-spatial Services
- Healthcare Information: From Administrative to Practice Databases
- A Hybrid Clustering Technique to Improve Patient Data Quality