DOCSLIB.ORG

OTRS 2.3 - Admin Manual OTRS 2.3 - Admin Manual Bora Bora Edition Copyright © 2003-2008 OTRS AG

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
OTRS 2.3 - Admin Manual OTRS 2.3 - Admin Manual Bora Bora Edition Copyright © 2003-2008 OTRS AG OTRS 2.3 - Admin Manual OTRS 2.3 - Admin Manual Bora Bora Edition Copyright © 2003-2008 OTRS AG René Bakker, Hauke Böttcher, Jens Bothe, Udo Bretz, Martin Edenhofer, Manuel Hecht, Christopher Kuhn, André Mindermann, Henning Oschwald, Thomas Raith, Stefan Rother, Burchard Steinbild This work is copyrighted by OTRS AG. You may copy it in whole or in part as long as the copies retain this copyright statement. UNIX is a registered trademark of X/Open Company Limited. Linux is a registered trademark of Linus Torvalds. MS-DOS, Windows, Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP and Windows 2003 are registered trademarks of Microsoft Corporation. Other trademarks and registered trademarks are: SUSE and YaST of SUSE AG, Red Hat and Fedora are registered trademarks of Red Hat, Inc. Mandrake is a registered trademark of MandrakeSoft, SA. Debian is a registered trademark of Software in the Public Interest, Inc. MySQL and the MySQL Logo are registered trademarks of MySQL AB. All trade names are used without the guarantee for their free use and are possibly registered trade marks. OTRS AG essentially follows the notations of the manufacturers. Other products mentioned in this manual may be trademarks of the respective manufacturer. Table of Contents Preface ........................................................................................................................................................x 1. Basics about trouble ticket systems......................................................................................................1 1.1. What is a trouble ticket system, when do you need it? ...............................................................1 1.2. What is a trouble ticket?..............................................................................................................2 2. OTRS - Open Ticket Request System ..................................................................................................3 2.1. Basics ..........................................................................................................................................3 2.2. Features .......................................................................................................................................3 2.2.1. New features of OTRS 2.3..............................................................................................5 2.2.2. New features of OTRS 2.2..............................................................................................6 2.2.3. New features of OTRS 2.1..............................................................................................7 2.3. Hard and software requirements .................................................................................................8 2.4. Community..................................................................................................................................9 2.5. Commercial Support for OTRS.................................................................................................10 3. Installation / Upgrade of the OTRS framework ...............................................................................11 3.1. The simple way - Installation of prebuilt packages...................................................................11 3.1.1. Installing the rpm on a SUSE distro.............................................................................11 3.1.2. Installing OTRS on a Debian system ...........................................................................16 3.1.3. Installing OTRS on Microsoft Windows systems ........................................................16 3.2. Installation from source (Linux, Unix) .....................................................................................17 3.2.1. Preparing the installation from source..........................................................................17 3.2.2. Installation of needed Perl modules .............................................................................18 3.2.3. Configuring the apache web server ..............................................................................21 3.2.4. Configuring the database ..............................................................................................22 3.2.5. Setting up the cron jobs for OTRS ...............................................................................26 3.3. Upgrading the OTRS Frameworks............................................................................................31 4. First steps in OTRS..............................................................................................................................32 4.1. Agent web interface ..................................................................................................................32 4.2. Customer web interface.............................................................................................................32 4.3. Public web interface..................................................................................................................33 4.4. First login ..................................................................................................................................34 4.5. An overview to the web interface..............................................................................................35 4.6. What is a queue? .......................................................................................................................38 4.7. User preferences........................................................................................................................39 5. The admin area of OTRS ....................................................................................................................41 5.1. Basics ........................................................................................................................................41 5.2. User, groups and roles...............................................................................................................41 5.2.1. User...............................................................................................................................42 5.2.2. Groups ..........................................................................................................................42 5.2.3. Roles.............................................................................................................................45 5.3. Customer users and customer groups........................................................................................48 5.3.1. Customer users .............................................................................................................48 5.3.2. Customer groups...........................................................................................................49 5.4. Queues.......................................................................................................................................50 5.5. Salutations, signatures, attachments and responses ..................................................................51 iii 5.5.1. Salutations ....................................................................................................................53 5.5.2. Signatures .....................................................................................................................54 5.5.3. Attachments..................................................................................................................55 5.6. Auto answers.............................................................................................................................56 5.7. Email addresses.........................................................................................................................58 5.8. Notifications ..............................................................................................................................59 5.9. SMIME......................................................................................................................................60 5.10. PGP .........................................................................................................................................61 5.11. States .......................................................................................................................................62 5.12. The graphical configuration frontend (SysConfig) .................................................................63 5.13. Using mail accounts ................................................................................................................64 5.14. Filtering incoming messages...................................................................................................65 5.15. Executing automated jobs with the GenericAgent..................................................................68 5.16. Admin email............................................................................................................................70 5.17. Session management ...............................................................................................................71 5.18. System Log .............................................................................................................................72 5.19. SQL queries via the SQL box .................................................................................................73
Load more

Recommended publications
  • Automated IT Service Fault Diagnosis Based on Event Correlation Techniques
    Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Dissertation an der Fakultat¨ fur¨ Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universitat¨ Munchen¨ vorgelegt von Andreas Hanemann Tag der Einreichung: 22. Mai 2007 1. Berichterstatter: Professor Dr. Heinz-Gerd Hegering, Ludwig-Maximilians-Universit¨at M¨unchen 2. Berichterstatterin: Professor Dr. Gabrijela Dreo Rodosek, Universit¨at der Bundeswehr M¨unchen Automated IT Service Fault Diagnosis Based on Event Correlation Techniques Dissertation an der Fakultat¨ fur¨ Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universitat¨ Munchen¨ vorgelegt von Andreas Hanemann Tag der Einreichung: 22. Mai 2007 Tag der m¨undlichen Pr¨ufung: 19. Juli 2007 1. Berichterstatter: Professor Dr. Heinz-Gerd Hegering, Ludwig-Maximilians-Universit¨at M¨unchen 2. Berichterstatterin: Professor Dr. Gabrijela Dreo Rodosek, Universit¨at der Bundeswehr M¨unchen Acknowledgments This thesis has been written as part of my work as a researcher at the Leib- niz Supercomputing Center (Leibniz-Rechenzentrum, LRZ) of the Bavarian Academy of Sciences and Humanities which was funded by the German Re- search Network (DFN-Verein) as well as in cooperation with the research group of Prof. Dr. Heinz-Gerd Hegering. Apart from the LRZ, this research group called MNM-Team (Munich Network Management Team) is located at the University of Munich (LMU), the Munich University of Technology (TUM) and the University of Federal Armed Forces in Munich. At first, I would like to thank my doctoral advisor Prof. Dr. Heinz-Gerd Hegering for his constant support and helpful advice during the whole prepa- ration time of this thesis. I would also like to express my special gratefulness to my second advisor, Prof.
    [Show full text]
  • Ticketing Systems with RT
    Ticketing Systems with RT Network Startup Resource Center www.nsrc.org These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (http://creativecommons.org/licenses/by-nc/4.0/) Typical Support Scenario • Lots of email traffic requesting help, request for services, etc • Archived as text without classification • Very difficult to find current status or problem history • Sometimes problems were forgotten or never resolved • Difficult for another person to follow up on a problem that someone else started dealing with Why Ticketing Systems? Ticketing Systems Why are they important? • Track all events, failures and issues • Focal point for help desk communication Use it to track all communications • Both internal and external Events originating from the outside: • customer complaints Events originating from the inside: • System outages (direct or indirect) • Planned maintenance, upgrades, etc. Ticketing Systems (Contd.) • Use a ticket system to follow cases, including communication between the support staff • Each case is considered a ticket • Each ticket has a ticket number • Each ticket goes through a similar life cycle: • New – Open – … – Resolved Help Request with Tickets Request Tracker / Trac RT • Heavily used worldwide • Can be customized to your location • Somewhat difficult to install and configure • Handles large-scale operations • A hybrid including wiki & project management features • Web-only ticket system works well but not robust as RT • Often used for ”trac”king group projects.
    [Show full text]
  • OTRS Asterisk PBX Integration Module PIM V2.0.0B Administrator's
    OTRS Asterisk PBX Integration Module PIM v2.0.0b Administrator's Guide 2019 © IP-LAB.RU Contents Introduction .................................................................................................................................................. 3 Preparing Asterisk PBX for integration with OTRS ........................................................................................ 4 Install the PIM package on the OTRS server ................................................................................................. 5 Configuring the PIMv2.0.0b module ............................................................................................................. 6 Definition of "Tracking number" ................................................................................................................... 8 Setting agent extensions ............................................................................................................................... 9 Assign agent extensions to the "Tracking Number" ................................................................................... 10 Customer User identification ...................................................................................................................... 11 CallerID modification ................................................................................................................................... 11 Starting the service ....................................................................................................................................
    [Show full text]
  • Onapp Admin Guide
    2.0 Admin Guide 2.0 Admin Guide Contents 0. About This Guide ............................................................................................... 5 1. OnApp Overview ................................................................................................ 6 1.1 Servers ................................................................................................................... 6 1.2 Networks ................................................................................................................ 7 1.3 Templates .............................................................................................................. 8 1.4 Virtual Machines .................................................................................................... 8 1.5 Scalability .............................................................................................................. 8 1.6 Availability and Reliability .................................................................................... 8 1.7 Security .................................................................................................................. 9 1.8 API and Integration ............................................................................................... 9 2. OnApp Hardware & Software Requirements ................................................. 10 2.1 Hypervisor Servers ............................................................................................. 10 2.2 Control Panel Server ..........................................................................................
    [Show full text]
  • Install Perl Modules
    How to install OTRS (Open Source Trouble Ticket System) on Ubuntu 16.04 Prerequisites Ubuntu 16.04. Min 2GB of Memory. Root privileges. Step 1 - Install Apache and PostgreSQL In this first step, we will install the Apache web server and PostgreSQL. We will use the latest versions from the Ubuntu repository. Login to your Ubuntu server with SSH: ssh [email protected] Update Ubuntu repository. sudo apt-get update Install Apache2 and a PostgreSQL with the apt: sudo apt-get install -y apache2 libapache2-mod-perl2 postgresql Then make sure that Apache and PostgreSQL are running by checking the server port. netstat -plntu You will see port 80 is used by apache, and port 5432 used by PostgreSQL database. Step 2 - Install Perl Modules OTRS is based on Perl, so we need to install some Perl modules that are required by OTRS. Install perl modules for OTRS with this apt command: sudo apt-get install -y libapache2-mod-perl2 libdbd-pg-perl libnet-dns-perl libnet-ldap-perl libio-socket-ssl-perl libpdf-api2-perl libsoap-lite-perl libgd-text-perl libgd-graph-perl libapache- dbi-perl libarchive-zip-perl libcrypt-eksblowfish-perl libcrypt-ssleay-perl libencode-hanextra- perl libjson-xs-perl libmail-imapclient-perl libtemplate-perl libtemplate-perl libtext-csv-xs-perl libxml-libxml-perl libxml-libxslt-perl libpdf-api2-simple-perl libyaml-libyaml-perl When the installation is finished, we need to activate the Perl module for apache, then restart the apache service. a2enmod perl systemctl restart apache2 Next, check the apache module is loaded with the command below: apachectl -M | sort And you will see perl_module under 'Loaded Modules' section.
    [Show full text]
  • OTRS 3.1 - Admin Manual OTRS 3.1 - Admin Manual Copyright © 2003-2012 OTRS AG
    OTRS 3.1 - Admin Manual OTRS 3.1 - Admin Manual Copyright © 2003-2012 OTRS AG René Bakker, Stefan Bedorf, Michiel Beijen, Shawn Beasley, Hauke Böttcher, Jens Bothe, Udo Bretz, Martin Edenhofer, Carlos Javier García, Martin Gruner, Manuel Hecht, Christopher Kuhn, André Mindermann, Marc Nilius, Elva María Novoa, Henning Oschwald, Martha Elia Pascual, Thomas Raith, Carlos Fernando Rodríguez, Stefan Rother, Burchard Steinbild, Daniel Zamorano. This work is copyrighted by OTRS AG. You may copy it in whole or in part as long as the copies retain this copyright statement. The source code of this document can be found at source.otrs.org [http://source.otrs.org/viewvc.cgi/doc-admin/]. UNIX is a registered trademark of X/Open Company Limited. Linux is a registered trademark of Linus Torvalds. MS-DOS, Windows, Windows 95, Windows 98, Windows NT, Windows 2000, Windows XP, Windows 2003, Windows Vista and Windows 7 are registered trademarks of Microsoft Corporation. Other trademarks and registered trademarks are: SUSE and YaST of SUSE Linux GmbH, Red Hat and Fedora are registered trademarks of Red Hat, Inc. Mandrake is a registered trademark of MandrakeSoft, SA. Debian is a registered trademark of Software in the Public Interest, Inc. MySQL and the MySQL Logo are registered trademarks of Oracle Corporation and/or its affiliates. All trade names are used without the guarantee for their free use and are possibly registered trade marks. OTRS AG essentially follows the notations of the manufacturers. Other products mentioned in this manual may be trademarks of the respective manufacturer. Table of Contents Preface .......................................................................................................................... xii 1. Trouble Ticket Systems - The Basics ...........................................................................
    [Show full text]
  • Openstackでnecが実現する 「OSSクラウド」の世界
    ＯｐｅｎＳｔａｃｋでＮＥＣが実現する 「ＯＳＳクラウド」の世界 ２０１３年３月１２日 日本電気株式会社 プラットフォームマーケティング戦略本部 ＯＳＳ推進室 技術主幹 高橋 千恵子 目次 ▐ ＯＳＳの動向 ▐ ＮＥＣのＯＳＳ/Ｌｉｎｕｘ事業 ▐ ＯＳＳプラットフォームへの取り組み 高可用Ｌｉｎｕｘプラットフォーム ＯＳＳミドルウェアの活用 ▐ ＯＳＳクラウド ＯｐｅｎＳｔａｃｋへの取り組み ＯＳＳクラウドソリューション ～沖縄クラウドサービス基盤～ ＯｐｅｎＦｌｏｗ+ＯｐｅｎＳｔａｃｋ ▐ 最後に ●本資料に掲載された社名、商品名は各社の商標または登録商標です。 Page 1 © NEC Corporation 2013 ＯＳＳの動向 Page 2 © NEC Corporation 2013 ＯＳＳコミュニティによるプロジェクト ▐ 全般 ・・・・・SaaS型アプリケーションが増加/著名OSSのベンダー配布、有償サポートや買収が進む OSS定点観測は、freecode.com にて実施。 ▐ ｲﾝﾌﾗ系・・・仮想化やクラウド基盤関係のOSSが注目される/システム、ネット管理OSSの伸びがある サイトでの人気度（300以上)で順位付け。 OSSプロジェクトは2012.4時点で32.4万件。 ▐ ﾃﾞﾌﾟﾛｲﾒﾝﾄ系・・PostgreSQL、mySQLが高人気 これらのDB管理、DBクラスタリングOSSも伸びている ビジネス用途を中心に表示。 ▐ ｱﾌﾟﾘ系・・・・SaaS型グループウェアOSS、ソフトウェア分類を越えた統合的な著名OSSの伸びがある コンシューマ・プライベート系は除く。 コンテンツアプリケーション •PHProject [GW] エンジニ ｺﾗﾎﾞﾚｰﾃｨﾌﾞ •EGroupware CRM ERM SCM • Dokuwiki [Wiki] • jGnash アリング • WebGUI [CMF] • phpBB [GW] •OBM [GW] • Enterprise CRM and ア • Tiki Tiki CMS Groupware • ProcessMaker • CorneliOS [CMS] • Ariadne Groupware System • Task Juggler [PM] • Blender オペレーション • TinyMCE [DCM] • XODA • Simple Groupware [GW] プ • OpenWebMail[webmail]• Teamwork [GW] • Dolibarr • Achievo [PM] • mxGraph 製造管理 • Drupal [CMS] • mnoGoSerch • LedgerSMB • white_dune • eZpublish [publish FW]• Managing • ZIm [blog] • Plans [GW] • The Apache Open リ • Tine2.0 [CRM&GW] • GnuCash • Jgraph • OTRS • XWiki [Wiki] • Midgard • Zimbra [GW] for Business • Elastix • GroupOffice [GW] • Twiki [KB] • TUTOS[ERP&PM] • graphviz • FUDForum • OpenSearch Project ｺﾝｼｭｰﾏ 系 • SquirrelMail [Webmail] • Time Trex • BRL-CAD • Asterisk • Plone CMS Server • Citadel [bbs] •
    [Show full text]
  • ITIL: Microsoft and Open Source
    ITIL: Microsoft and Open Source ITIL: Microsoft and Open Source White Paper Microsoft Corporation Published: October 26, 2007 1 White Paper – ITIL: Microsoft and Open Source Contents ITIL: Microsoft and Open Source ........................................................................................ 4 Introduction to ITIL ............................................................................................................. 4 Service Support ............................................................................................................... 5 Service Delivery ............................................................................................................... 5 History of ITIL ...................................................................................................................... 6 Benefits of ITIL .................................................................................................................... 6 IT Service Support: Incident Management ......................................................................... 6 Definition ........................................................................................................................ 6 Product Comparison ....................................................................................................... 7 Open Source ................................................................................................................ 8 Microsoft ....................................................................................................................
    [Show full text]
  • Und Open-Source-Einführung Im Auswärtigen Amt
    Dieser Artikel ist Teil des Open Source Jahrbuchs 2007 GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA Everyone is per- mitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation‘s software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to yourOpen Source Jahrbuch 2007 programs, too. BerndWhen we Lutterbeckspeak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that youMatthias know you Bärwolff can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the soft- ware, or if you modify it.
    [Show full text]
  • Documentation Manual Do OTRS Business Solution™ 6
    Documentation Manual do OTRS Business Solution™ 6 Build Date: 2017-09-27 Manual do OTRS Business Solution™ 6 Copyright © 2017 OTRS AG Este trabalho é registrado pela OTRS AG. Você pode copiá-lo em todo ou em parte desde que mantenha esta declaração de direitos autorais. Todos os nomes são utilizados sem a garantia de seu uso gratuito e são possivelmente marcas registradas. Todos os produtos mencionados nesse manual podem ser marcas registradas dos seus respectivos fabricantes. O código fonte deste documento encontra-se em t github, in the repository doc-otrsbusiness. As contribuições são bem-vindas. Você pode auxiliar traduzindo-a para o seu idioma em Transifex. Table of Contents 1. Introdução .................................................................................................................. 1 2. Atualizando para OTRS Business Solution™ ......................................................... 2 3. Características da OTRS Business Solution™ ........................................................ 3 1. O Chat ................................................................................................................ 3 1.1. Descrição ................................................................................................. 3 1.2. Configuração ............................................................................................ 3 1.3. Setup ........................................................................................................ 5 1.4. Uso geral .................................................................................................
    [Show full text]
  • Bacula Monitoring Mit Nagios Oder Icinga
    http://www.netways.de Bacula Monitoring mit Nagios oder Icinga Julian Hein – NETWAYS GmbH NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Agenda . Kurzvorstellung . Nagios Einführung . AddOns & Erweiterungen . Bacula Überwachung . Fragen & Antworten NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de NETWAYS GmbH Kurzvorstellung NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Allgemeine Daten . Julian Hein . Firmengründung 1995 . GmbH seit 2001 . Open Source seit 1997 . Nagios / Netsaint seit 1999 . 20 Mitarbeiter . Sitz in Nürnberg NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Leistungsbereiche Open Source Open Source Systems Management Data Center Solutions . Monitoring . High Availability Lösungen . Performance Management . Cluster Lösungen . Configuration Management . Loadbalancing . Service Management . Virtualisierung . Knowledge Management . Speicherlösungen . Asset Management . Firewalls . Identity Management . Datenbanken . Backup & Datensicherung . Voice over IP Managed Services Monitoring HW Veranstaltungen NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Konferenzen 4. Monitoring Conference (OSMC) . Mehr als 250 Teilnehmer . 5 Tracks mit Vorträgen & Workshops . 28. - 29. Oktober -> http://netways.de/osmc 2. Open Source Datacenter Conference (OSDC) . Mehr als 80 Teilnehmer . 3 Tracks mit Vorträgen & Workshops . 26. – 27. Mai -> http://netways.de/osdc NETWAYS GmbH . Deutschherrnstr. 15-19 . 90429 Nürnberg . +49 911 92885-0 . http://www.netways.de http://www.netways.de Eigene Nagios AddOns und unzählige Nagios Plugins NETWAYS GmbH . Deutschherrnstr. 15-19 .
    [Show full text]
  • Conference Reports From
    LISA ’07: 21st Large Installation System Administration Conference Dallas, TX November 11–16, 2007 conference KEYNOTE ADDRESS Autonomic Administration: HAL 9000 Meets Gene reports Roddenberry John Strassner, Motorola Fellow and Vice President, Autonomic Networking and Communications, Motorola Research Labs THANKS TO OUR SUMMARIZERS Summarized by Rik Farrow John Strassner gave a keynote that was, strangely, con - Saurabh Arora sidered to contain too much math for most of the audi - Mukarram Bin Tariq ence. John began by demonstrating his motivation for Leah Cardaci coming up with a system that can function when there are seven different groups controlling over 60 sets of Marc Chiarini services, all—theoretically, at least—striving to satisfy Rik Farrow the same business goals. Part of the problem with this Nathaniel Husted picture (see his slide 4 diagram on the LISA ’07 Web site), is that it is much too complicated for mere mor - Kevin James tals to understand how the different groups can work Ski Kacoroski together. The other issue is that the data within each Kimberly McGuire group is not compatible—that is, each group is a verti - cal stovepipe, with systems not designed or originally Will Nowak intended to be shared among groups. Shaya Potter Even the meanings of goals, such as Service Level Agree - Chris St. Pierre ment (SLA), are different among the various groups. At Josh Simon the management level, an SLA specifies the point where lowered performance means a loss of income, whereas at Gautam Singaraju the network administration level, the SLA specifies the Anu Singh percentage of bandwidth to be allotted to each customer.
    [Show full text]