A System Administrator's Guide to Preliminary .ppt
《A System Administrator's Guide to Preliminary .ppt》由会员分享,可在线阅读,更多相关《A System Administrator's Guide to Preliminary .ppt(32页珍藏版)》请在麦多课文档分享上搜索。
1、A System Administrators Guide to Preliminary Troubleshooting Techniques,Presented By: Darryl Wright and Volker Kleinschmidt,April 12, 2005,And now a word from our lawyers,Any statements in this presentation about future expectations, plans and prospects for Blackboard and other statements containing
2、 the words “believes,“ “anticipates,“ “plans,“ “expects,“ “will,“ and similar expressions, constitute forward-looking statements within the meaning of The Private Securities Litigation Reform Act of 1995. Actual results may differ materially from those indicated by such forward-looking statements as
3、 a result of various important factors, including the factors discussed in the “Risk Factors“ section of our most recent 10-K filed with the SEC. In addition, the forward-looking statements included in this press release represent the Companys views as of April 11, 2005. The Company anticipates that
4、 subsequent events and developments will cause the Companys views to change. However, while the Company may elect to update these forward-looking statements at some point in the future, the Company specifically disclaims any obligation to do so. These forward-looking statements should not be relied
5、upon as representing the Companys views as of any date subsequent to April 11, 2005. Blackboard, in its sole discretion, may delay or cancel the release of any product or functionality described in this presentation.,Objectives,Provide Blackboard System Administrators with an overview of their roles
6、, responsibilities, and their impact on the success of the Blackboard Academic Suite at their institutions Highlight best practices for keeping your Blackboard Academic Suite running smoothly and problem free Improve and standardize the troubleshooting process on campus. Methods for better troublesh
7、ooting. Describe ticket submission and escalation process within Blackboard Open Discussion: The evolution of your Blackboard Networked Learning Environment,System Administrator Roles I,Back-end administratorInstallations; webserver admin; database configuration and maintenance; application monitori
8、ng; snapshot and data integration; and even OS maintenance tasks Front-end GUI administratorCourse shell creation; user enrollment; export/import/copy; control over feature availability and design; set policies and business rules for account creation, content preservation etc.; portal administration
9、 System Extension DeveloperCreation of Building Blocks, Application Bridges and Portal Modules using Java and Blackboards APIs,System Administrator Roles II,CMS Help Desk ManagerTroubleshooting issues reported via email, phone, or a ticket system, or self-discovered; escalation of issues to Blackboa
10、rd Technical Support; training and supervision of general help desk staff Trainer creating online documentation and tip sheets Instructional DesignerIn some cases the system administrator may also train instructors and staff on pedagogically sound uses of technology, and participate in the creation
11、of course materials and the tracking and evaluation of student performance,Show of hands,Which roles do you fill at your institution? Back-end administrator Front-end administrator System Extension Developer CMS Helpdesk manager Trainer / Documentation Author Instructional Designer,User community ma
12、iling lists,Back-end administrator Front-end administrator System Extension Developer CMS Helpdesk manager Trainer / Documentation Author Instructional Designer,BBADMIN-L BLKBRD-L BB-OPEN_SRC BB-FS BB-ID,Evolution of System Administration Roles & Practices,MISSION CRITICAL,EXPLORATORY,SUPPORTED,STRA
13、TEGIC,TRANSFORMATIVE: THE NETWORKED LEARNING ENVIRONMENT,Phase I,Phase 2,Phase 3,Phase 4,Phase 5,INSTITUTIONAL GROWTH,Multiple People,Single Server Single Admin,Integrated Production Environment,Monitoring, Backup & Maintenance Practices,Ticketing System,Student /Faculty Training Programs,System Upd
14、ate Deployment Plans,Custom Instructional Tools,Long Range Planning,Help Desk Management,High Performance / High Availability,Strategic Owner,Business Continuity,Identified system manager,Help Desk,Change management practices,Best Practices,Be Prepared Avoiding is better than solving Have a well-est
15、ablished troubleshooting process on campus Train your users to be aware of pitfalls Document local policies and differences Top 10 tips for System Administrators,Best practices - Top 10 tips for System Administrators,Maintain current Operations Workbook Document all server and application changes Ma
16、intain a Test server environment Set up and test a Disaster Recovery Plan Plan ahead for increased usage Train users well to avoid problems Keep it clean - purge old records Manage and monitor your application logs Graph system metrics (MRTG, cricket) Participate in user community,Top 10 Best practi
17、ces for Course Management beginning of semester operational readiness,Fully document your system environment. This documentation should include the systems, applications, as well as the owners. Fill in the Operations Workbook. Practice change management. Make sure all changes to your configuration a
18、re logged, and that a rollback procedure is in place. If something goes wrong the first question should be “what changed?“ Maintain staging and test servers. Ensure that any change to your environment goes through an acceptance testing process. Use the test server to prototype and model changes, and
19、 the staging server for acceptance testing. Create daily full backups and regularly practice a restore to a test server. Understand how many courses and users will be / have been added between semesters. Analyze whether your hardware is powerful enough to handle the increase. Train your users. Sched
20、ule enough workshops early on to highlight new features, and provide actual use cases for better user adoption. Have documentation ready early. Purge records. Use the tools available to archive out courses a pre-determined period after the course is over. Maintain the archive for long term storage a
21、nd record keeping; and then purge the course from your system. Keeping unused courses and accounts on your system can slow performance. Know your logs. Enterprise applications have a number of error and system logs. Monitor them for unusual events and size. Make sure tasks such as log rotation and s
22、tats purging are scheduled appropriately. Verify regularly that they are working correctly. Actively monitor your environment using tools like Big Brother and graph crucial performance data with MRTG, cricket, or similar tools. Participate in the user community. Share experiences, gather resources a
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
2000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ASYSTEMADMINISTRATOR SGUIDETOPRELIMINARYPPT
