Application Administrators Handbook : Installing, Updating and Troubleshooting Software.

Format:

Book

Author/Creator:

Bourne, Kelly C.

Language:

English

Subjects (All):

Software maintenance--Handbooks, manuals, etc.

Software maintenance -- Handbooks, manuals, etc.

Software engineering--Management--Handbooks, manuals, etc.

Software engineering -- Management -- Handbooks, manuals, etc.

Physical Description:

1 online resource (623 pages)

Edition:

1st ed.

Place of Publication:

San Diego : Elsevier Science & Technology, 2013.

Contents:

Front Cover

Application Administrators Handbook: Installing, Updating and Troubleshooting Software

Copyright

Contents

Dedication

Acknowledgments

Chapter 1: What Does an Application Administrator Do?

1.1. Overview of the Position

1.1.1. Application administrator backgrounds

1.1.2. Potential skillset

1.1.3. Duties and responsibilities

1.1.4. Types of applications that need an administrator

1.2. Qualities of an Application Administrator

1.2.1. Service mentality

1.2.2. Persistence pays off

1.2.3. Continuous improvements

1.2.4. Document, document, document

1.2.5. Best practices

1.2.6. Process maturity

1.3. Where Do Application Administrators Come from?

1.4. What Jobs Can an Application Administrator Move up to?

1.4.1. IT architect

1.4.2. Software development

1.4.3. Work for the vendor

1.4.4. Consulting

1.5. Examples of Commercial Off The Shelf (COTS) Software

1.6. Dealing with People, Lots of People

1.7. Questions to Ask If Responsibility for an Application Is Dropped on You

1.8. Administering Multiple Applications

1.9. Training Your Replacement or Backup

Summary

Chapter 2: Design

2.1. Specifications

2.2. Interaction with Other Software Packages

2.3. Capacity Planning

2.4. Legacy Systems

2.5. Types of Hosting Models

2.5.1. Hosted internally

2.5.2. Hosted by the vendor

2.5.2.1. Application service provider (ASP)

2.5.2.2. Software as a service (SaaS)

2.5.3. Advantages and disadvantages of vendor-hosted environments

2.5.3.1. Support and updates

2.5.3.2. Stability

2.5.3.3. Security

2.5.3.4. Locked in

2.5.4. Comparing costs

2.6. Web Applications vs. Client-Server Applications

2.6.1. Client-server applications

2.6.2. Web-based applications

2.7. The Total Cost of Ownership (TCO) of Your Application.

Chapter 3: Architecture

3.1. Application Architecture

3.2. Through Thick and Thin

3.3. Tiers

3.3.1. Middleware

3.4. Computers, CPUs, and Cores

3.5. Virtual Servers

3.6. Fault Tolerant

3.7. Running Multiple Applications on a Server

3.8. Virtualized Desktops

3.9. High Availability/High Performance

3.9.1. Clustering

3.9.2. Load balancing

3.9.3. Heartbeats and failover

3.9.4. Added complexity

3.10. Operating Systems

3.11. Windows vs. UNIX vs. Linux

3.11.1. Windows

3.11.2. UNIX

3.11.3. Linux

3.12. Storage

3.12.1. Storage area network (SAN)

3.12.2. Solid-state drive (SSD)

3.13. What Does Your Server Look Like?

3.14. Scaling Up

3.15. Databases

3.15.1. Connection pooling

3.16. Code Base

3.17. Middleware

Chapter 4: Features Common to Many Applications

4.1. Multiple Modules in an Application

4.2. Customizations and Configuration Changes

4.3. Reporting for Users

4.3.1. Reporting without a report writer

4.3.1.1. Contents of file roster.sql

4.3.1.2. Contents of file roster.cmd

4.3.2. Report output formats

4.3.3. Report distribution

4.3.4. Bursting reports

4.3.5. Authorizing users to create reports

4.4. Reporting for Application Administrators

4.5. E-mail

4.6. User Preferences

4.7. Data

4.7.1. Data types

4.7.2. Databases

4.8. Feed Me! Getting Large Quantities of Data into or out of Your Application

4.9. Application Administration Tools

4.10. Console Administrator Tools for Support Software

4.11. Log Files

4.11.1. Application log files

4.11.2. Configuring application log files

4.11.3. Log file time-stamp issues

4.11.4. Support software log files

4.12. Navigation

4.12.1. Menus

4.12.2. Function keys/shortcut keys

4.12.3. Breadcrumbs

4.13. Error Messages

4.14. Dashboards

4.15. Limitations.

4.16. Workflow

4.17. Time Zone Trouble

4.18. Cookies

Chapter 5: Specifics About Your Application

5.1. Browsers Supported by Your Application

5.1.1. Compatibility mode

5.2. Is Your Application Brittle?

5.2.1. Documenting brittle areas

5.2.2. Mitigating brittleness

5.3. Does the Application ``Play Well´´ with Others?

5.4. Integrates well with Other Applications

5.5. License Keys

5.5.1. Updating license keys

5.6. Troubleshooting Assistance

5.7. Using the Application in Unexpected Ways

5.8. Source Code

5.8.1. Proprietary software

5.8.2. Source code escrow

5.8.3. Open source software

5.9. Phoning Home

5.9.1. Blocking phone calls home

5.10. Tracking Down Changes

5.10.1. Audit trail

5.10.2. Log files

5.10.3. Database tables

5.10.4. Login reports

5.11. Using Disk Space

5.11.1. Monitoring disk space

5.11.1.1. Manually

5.11.1.2. Write a script to do it

5.11.1.3. Use an operating system feature to do it

5.11.1.4. Download a freeware tool to do it

5.11.1.5. Incorporate it into the overall monitoring framework

5.11.2. Running out of disk space

5.11.2.1. Adding more disk space

5.11.2.2. Freeing up disk space

5.11.2.3. Relocating files

5.11.2.4. Modify the application to utilize another drive

5.11.2.5. Create a junction point

Chapter 6: Taking Responsibility for an Application

6.1. Overview of the Application

6.2. Availability

6.3. Performance

6.4. User Base

6.5. Backups

6.6. Production Support

6.7. Hardware

6.8. Software

6.9. Database

6.10. Security

6.11. Training

6.12. Disaster Recovery

6.13. The Vendor

6.14. Interactions with Other Applications

6.15. Outputs: Reports

6.16. Outputs: Logs

6.17. Changing the Application

6.18. Monitoring

Chapter 7: Change Control Management.

7.1. What Is Change Control Management?

7.1.1. Why to have change control management?

7.1.2. Change control steps

7.1.3. Approvals

7.1.4. Change control software

7.1.5. Workflow

7.2. Software Configuration Management (SCM) or Change Control Management?

7.3. Change Control Board

7.3.1. Change control board membership

7.3.2. Meetings

7.3.3. Proposing changes

7.4. Environments

7.4.1. The look of each environment

7.4.2. When differences are OK

7.4.3. Who can access each server?

7.4.4. Accessing environments from outside the organizations network

7.5. When to Move Changes into Production

7.6. Moving a Change into Production

7.7. Sarbanes-Oxley or SOX

7.8. Subverting the Change Control Process

7.9. Exceptions

7.10. Testing

7.10.1. Acceptance testing

7.10.2. Regression testing

7.10.3. Who should write the test script(s)?

7.10.4. Where is testing performed?

7.10.5. Who should do the testing?

7.10.6. Testing documentation

7.11. Application Version Numbers

Chapter 8: Installing Software

8.1. Be the Man, or Woman, with a (Project) Plan

8.2. How Many Installs have to Be Done?

8.2.1. Installations on user workstations

8.2.2. Application architectures can include multiple types of servers

8.2.3. Clustered or load-balanced environments

8.3. Preparing for the Installation

8.3.1. Read the installation guide

8.3.2. Worksheets in the installation guide

8.3.3. Write a project plan for the installation

8.3.4. Confirm the servers exist and are set up correctly

8.3.5. Verify that you can remotely access all the servers

8.3.6. Confirm that the operating system has been loaded

8.3.6.1. Service packs

8.3.7. Ensure that any required supporting software has been loaded

8.3.8. Database

8.3.9. Ports.

8.3.9.1. Tools to identify ports that are being used

8.3.9.2. Document all the ports being used

8.3.10. Environment variables

8.3.10.1. Two kinds of environment variables

8.3.10.2. Every operating system is different

8.3.10.3. Creating a new environment variable

8.3.10.4. Edit an existing environment variable

8.3.10.5. Environment variables and command lines

8.3.10.6. Warnings about timing and duration of environment variables

8.3.11. Run the installation program

8.3.11.1. Typical installation questions

8.3.11.2. Practice makes perfect

8.3.11.3. Get assistance from the vendor

8.3.11.4. It always takes longer than you expect

8.3.11.5. Document, document, document

8.3.11.6. After the install check for updates

8.4. User Acceptance Testing-UAT

8.5. Test Data

Chapter 9: Support Software

9.1. Support Software on Application Servers

9.1.1. Frameworks

9.1.1.1. .NET framework

9.1.1.2. Java frameworks

9.1.2. Clustering and load balancing

9.1.2.1. Clustering

9.1.2.2. Load balancing software

9.1.3. Web server

9.1.4. Software that supports applications

9.1.5. Databases

9.1.5.1. Database client software

9.1.5.1.1. Oracle client software

9.1.5.1.2. IBM DB2 client software

9.1.5.2. Database access tools

9.1.5.2.1. SQL*Plus

9.1.5.2.2. SQL Developer

9.1.5.2.3. Microsoft Server Management Studio

9.1.5.2.4. MySQL Query Browser

9.1.5.2.5. Toad and SQL station

9.1.6. Security

9.1.6.1. Firewalls

9.1.6.2. Antivirus (AV) software

9.1.6.3. Intrusion detection systems (IDS)

9.1.6.4. Log monitoring utilities

9.1.6.5. Security certificates

9.1.6.6. Vulnerability scanner

9.1.6.7. Update software

9.1.7. Reporting

9.1.8. Monitoring

9.1.9. Backup software

9.1.10. Utilities

9.1.11. Scheduling

9.1.12. Extract, transform, and load.

9.2. Support Software on User Workstations.

Notes:

Description based on publisher supplied metadata and other sources.

Other Format:

Print version: Bourne, Kelly C. Application Administrators Handbook

ISBN:

9780124017122

OCLC:

868231708