IBM eServer and JD Edwards EnterpriseOne Technology Foundation : Ensuring a High Quality of Service.

Front cover -- Contents -- Figures -- Tables -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. What Technology Foundation is -- Part 1 Before installation -- Chapter 2. Methods and requirements -- 2.1 Methodology for producing a physical architecture -- 2.2 A logical architecture -- Chapter 3. Logical architecture selection -- 3.1 Key logical architecture issues for Technology Foundation -- 3.1.1 Fault tolerance -- 3.1.2 Degree of security -- 3.2 Supported, standard logical architectures -- 3.2.1 Standard Security, Highly Available -- 3.2.2 Standard Security, Continuously Available -- 3.2.3 Highly Secure, Highly Available -- 3.2.4 Test architecture -- 3.3 Allowed customizations to logical architectures -- 3.3.1 Connecting to third-party external directory servers (LDAPs) -- 3.3.2 Downgrading availability for non-mission critical elements -- 3.3.3 Increasing performance for remote locations -- 3.3.4 Very high internal security -- 3.3.5 Providing Internet access -- 3.3.6 Secure Sockets Layer accelerators -- 3.3.7 Third-party IP sprayers -- 3.3.8 Third-party database vendors -- 3.4 Selecting appropriate fault tolerance and security -- 3.4.1 Determining fault tolerance requirements -- 3.4.2 Determining security requirements -- Part 2 After installation -- Chapter 4. Configuring and tuning Technology Foundation for high transaction volumes -- 4.1 pSeries benchmark -- 4.1.1 Physical architecture -- 4.1.2 Detailed logical architecture -- 4.2 Recommended parameter values and reasoning -- 4.2.1 Tuning parameters that prevent dropped transactions at high volumes -- 4.2.2 Parameters that enhance response time -- 4.2.3 Tempting but insignificant parameters -- 4.3 xSeries -- 4.4 iSeries -- 4.5 Miscellaneous tuning tips -- 4.5.1 Database configuration changes.

4.5.2 Watching for contention on the next numbers table -- 4.5.3 Ensuring your test scripts do not lock tables -- 4.5.4 Paying attention to how your test tool classifies dropped transactions -- Chapter 5. Managing Technology Foundation -- 5.1 Installation and maintenance roles -- 5.2 Operations monitoring and management tools -- 5.2.1 WebSEAL -- 5.2.2 Network Dispatcher -- 5.2.3 HTTP -- 5.2.4 WebSphere Application Server -- 5.2.5 Portal -- 5.2.6 EnterpriseOne Web Server (JAS) -- 5.2.7 DB2 Universal Database -- 5.2.8 System monitoring -- 5.3 Maintenance -- 5.3.1 Quality assurance environments for new software releases -- 5.4 Commonly overlooked best practices for maintenance -- 5.5 Beyond Technology Foundation -- 5.5.1 Enhancing Technology Foundation with portlets -- 5.5.2 Portal's Credential Vault -- 5.5.3 Publicly accessible enterprises -- 5.5.4 Running additional applications on the hardened J2EE application server -- 5.5.5 Extending the architecture using Java Message Service -- 5.5.6 Using WebSphere Enterprise Edition features to do business process modeling -- Appendix A. Sample logical architecture selection document -- Table of contents -- Executive summary -- Business overview -- Business objectives -- Acme's current environment -- Current physical architecture -- Current user community -- Current security mechanisms -- Recommended logical architectures -- Initial rollout recommendation -- Medium-term recommendation -- Long-term recommendation -- Rationale for architecture proposal -- Required skills -- Next steps -- Sample proposal glossary -- Glossary -- Related publications -- IBM Redbooks -- References -- Online resources -- How to get IBM Redbooks -- Help from IBM -- Index -- Back cover.

Description based on publisher supplied metadata and other sources.

Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2024. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.