User Manual Customer Interaction Express 3.3 Archiving

Transcription

1 User Manual Customer Interaction Express 3.3 Archiving Edition /22/2015 COMPAS ID

2 2015 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full legal page information, please see the complete document, Avaya Legal Page for Software Documentation, Document number To locate this document on the website, simply go to and search for the document number in the search box. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site: Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site: COMPAS This document is also available in the COMPAS database. The COMPAS ID for this document is

3 Contents About this manual Questions about this manual Who is part of the target group? What kind of information is provided here? What kind of information is not provided? How is the manual structured? Which edition are you reading? What has changed since the last edition? Where can you find additional information? Second-level UMR Archiving Archie archiving process Restriction What is multi-level archiving? Properties of second-level archiving Error messages second-level archiving Basics Which prerequisites must be met by the source and target database? Which settings do you have to take into account for sending faxes? How is the data stored in the target database? Which criteria have to be met by the data records to be archived or deleted? Configuration Where is the configuration stored? Which values can be found in the rod.ini file? Operation UMR administrator: Scheduler and archiving process Prerequisites for the display of archiving and delete jobs Creating and processing archiving jobs Activating/deactivating archiving/delete jobs Duplicating archiving/delete jobs Creating and processing delete jobs Tips and tricks Do you have to archive? What happens if the database is full? How often do we recommend archiving? One-time archiving Cyclic archiving Archiving do not working Glossary Index Edition /22/2015 3

4 4 User Manual CIE 3.3 Achiving

5 About this manual About this manual Questions about this manual Before you start reading you might have questions regarding this document. We will answer some questions to start with. Who is part of the target group? This manual is intended for experienced database administrators who want to set up and configure an archiving database (second-level archiving) for the UMR. A sound knowledge of database technology is a prerequisite: SQL databases, ODBC drivers. The database administrators must be capable of adapting existing DDL scripts to the particular needs of a company and of writing dedicated DDL scripts for databases that are not supported. It makes no difference whether you are using this document in printed or online form. What kind of information is provided here? This manual contains information about installing and configuring an archiving database as well as information about second-level archiving. What kind of information is not provided? This document does not provide information on the installation and configuration of a CIE system with UMR. How is the manual structured? This manual provides you with background knowledge on second-level archiving and explains how an archiving database is set up and configured. Once you have read a few pages you will notice that the chapters are structured similarly. Usually, an introduction to the topic is provided first. Prerequisites or necessary skills are often described next, followed by instructions. Illustrations or examples further clarify the topic. Edition /22/2015 5

6 Which edition are you reading? The following table lists information about this edition: Information Explanation Compiled on July 22th 2015 Based on: Customer Interaction Express 3.3 Editor Andreas Marquardt Available as: Acrobat Reader file (PDF) What has changed since the last edition? The following table shows the history of this document. Version Change 1.0 CIE 3.3 Where can you find additional information? This manual describes the necessary knowledge and requirements and provides instructions you need to be able to set up and configure an archiving database. For additional information on the CIE system please refer to: Customer Interaction Express System Administration manual Customer Interaction Express Configuration manual 6 User Manual CIE 3.3 Achiving

7 Second-level UMR Archiving Second-level UMR Archiving Archie archiving process Restriction The CIE-archiving is a technical solution so that the default database (c3k) remains powerful. No longer relevant documents can be stored in a second database. The CIE-archiving is not a long-term archiving tool. For the archive database, there is no level indication, and no automatic backup and no functions for memory overflow. What is multi-level archiving? The CIE UMR component works with documents stored in a runtime database. These documents can be archived in various levels once they have been completely processed. First-level archiving Second-level archiving First-level archiving Completed documents will be displayed in the folder Completed. You can identify in the UI internal documents (Right click - Archive). This marked documents are displayed in the folder Completed. The documents are stored in the database C3K. Second-level archiving The present UMR Archiving Manual only describes second-level archiving. At the second level of archiving the documents are stored in a second database. The archiving is done by the Archie archiving process. Archie is a Reporting on Demand (RoD) process of C3000. Why is a second database needed for archiving? A second database (archiving database) is needed for the following reasons: Since the runtime database (first-level archiving) grows too large and can no longer be handled efficiently it is necessary to store (archive) the data in a second database at certain intervals. A second database (second-level archiving) can make the data access by customer applications easier. Edition /22/2015 7

8 Which databases can be used for second-level archiving? In principle, any ODBC-capable database can be used. However, due to the different behavior of ODBC databases of different suppliers only the following databases have been supported so far: PostgreSQL MS SqlServer 2000 Oracle (as of 9i) For further information on the availability of other databases, please refer to your account manager at Avaya. Can you start second-level archiving from the UMR Administrator? Archiving can be started cyclically via the UMR Administrator. You will find a detailed description in Operation on page 14. Can you access externally stored archive data from the UMR system? If you use PostgreSQL for the archived data, then you can use the following functions in the UI in the folder Archive. View Archive Note long load times for large data set. Filter by Archive Print the document from the archive You can not edit a document in the archive. Properties of second-level archiving Second-level archiving provides you with the following features: Deleting the documents from the runtime database Writing the documents to an archiving database Parallel to that, deleting the documents from the runtime database Starting the delete/archiving jobs using the Scheduler. For further information please refer to chapter UMR administrator: Scheduler and archiving process on page User Manual CIE 3.3 Achiving

9 Second-level UMR Archiving Error messages second-level archiving If an archiving or delete job cannot be processed, this information is passed on to the scheduler with an error code. This is complemented by a technical error message (partially forwarded original message of the faulty component) in English which can be displayed in the UMR Administrator. The interfaces also show the status of the last job that was completed. Archiving or delete job failed If an archiving or delete job failed it will not be repeated. Instead, the application will wait for the next periodic job. Error messages Detailed error messages are written in TTrace. If required you can set up a warning behavior using TTrace. More detailed information about TTrace can be found in the Installation and Configuration TTrace manual. Edition /22/2015 9

10 Basics The archiving process transports data from the runtime database into an archiving database. The archiving database can be located on the same database server or on another one. Which prerequisites must be met by the source and target database? The following prerequisites must be met by the source and target database. The source database must be PostgreSQL. The target database must offer ODBC as an interface for writing data records. INSERT instructions are used and BLOBS or TEXT columns are inserted. The required tables are created in the PostgreSQL database during installation of UMR. For Microsoft SqlServer 2000 and Oracle 9i, DDL scripts are generated during installation. These DDL scripts can be found in the following directory after installation: <Installations directory for ROD>/ArchiveDDL As a database administrator you might have to adapt these DDL scripts to local conditions (see comments at the beginning of the DDL scripts) and then use them on the desired database. For information about installing PostgreSQL, refer to the Customer Interaction Express System Administration user manual. 10 User Manual CIE 3.3 Achiving

11 Second-level UMR Archiving Which settings do you have to take into account for sending faxes? Note the following settings for sending faxes. If you archive all the binary files of the fax graphics you will need a lot of memory and the system will be exposed to heavy load. If you do not archive the binary files of the fax graphics the faxes you sent will no longer be available later on. When configuring this parameter you have to decide which of these two aspects shall take precedence over the other. You configure the CopyCachedFaxPages entry in the rod.ini in the <Rod directory>/ini directory. If you Want to save the fax graphic created by a transmitted fax as a binary file in the archive database. Do not want to save the fax graphic created by a transmitted fax in the archive database. Then set CopyCachedFaxPages to ON OFF (default) For further information on the rod.ini file please refer to Kapitel Configuration on page 13. How is the data stored in the target database? The following source data is stored. C3K_DOCUMENT C3K_DOCPROP C3K_DOCUMENT_INDEX C3K_CONFIG_DOCINDEX C3K_REQUEST C3K_USER C3K_USER2 In the target database the data is stored in the following tables: C3K_DOCUMENT_ARCHIVE C3K_DOCPROP_ARCHIVE C3K_DOCUMENT_INDEX_ARCHIVE C3K_CONFIG_DOCINDEX_ARCHIVE C3K_REQUEST_ARCHIVE C3K_USER_ARCHIVE C3K_USER2_ARCHIVE Edition /22/

12 Which criteria have to be met by the data records to be archived or deleted? The following criteria must be met: All the documents that belong to one task are always archived or deleted together. This process revolves around the main document. The main document is the document that initiates the whole process. It is the document with the earliest time of creation. The main document must meet the following criteria: - The document is archived in the archived state. This guarantees that only Call Center messages are archived. - The document was created before a given time. 12 User Manual CIE 3.3 Achiving

13 Second-level UMR Archiving Configuration Where is the configuration stored? The configuration of delete and archiving jobs is saved in Reporting on Demand (RoD) ini files. Path for rod.ini for Microsoft Windows 2003 C:\Documents and Settings\All Users\Application Data\Avaya\Customer Interaction Express\Unified Media Archiving\ini Path for rod.ini for Microsoft Windows 2008 R2 C:\ProgramData\Avaya\Customer Interaction Express\Unified Media Archiving\ini To show the path, set the option Show hidden files, folders, and drives in the explorer. Which values can be found in the rod.ini file? The following table contains values that can be found in the rod.ini file in the [Archie] section. You can change these values if necessary. Change Possible values Description Default EnableUMR ON, OFF If ON, the document archiving/ deletion is activated. ArchiveDocuments ON, OFF If OFF, the documents will not be archived before they are deleted. DeleteArchivedDocumen ts ON, OFF If OFF, deletion of moved data is suppressed (to be used for testing purposes only). CopyCachedFaxPages ON, OFF If ON, the fax pages (binary files) stored in the database will be archived. ArchDestUsername DB user name User name in the target database. ArchDestPwd DB password (encrypted) Encrypted password in the target database. ArchDestOdbcDriver ODBC driver name Name of the ODBC driver that can be used for the target database. ArchDestOdbcConnect ODBC-Connectstring ODBC-Connectstring leaving out the user and password. ON ON ON OFF c3k_archive LamZA: - - Edition /22/

14 Operation UMR administrator: Scheduler and archiving process Database entries can can be deleted or archived. To do this, you can use archiving and delete jobs. The execution of archiving and delete jobs is scheduled. This is controlled by means of the Scheduler, that works in the background and is operated using the settings on the tabs described below. In order to carry out archiving functions click on the Archive/Delete page in WebAdmin. The following tabs will be displayed. Archiving UMR documents Delete UMR documents Recommendations Since the information on these two tabs is not updated automatically we recommend that you click on the Update button whenever changes are to be expected. For high message volume, we recommend that the archiving job be performed when operations are slow. Default The Scheduler receives a standard archiving job following the installation of the UMR in the CIE. This standard archiving job (once a week, on Sunday at 2.00 am) is meant to be an example and can be changed at any time. Prerequisites for the display of archiving and delete jobs You must have the privilege of UMR Administrator in order to display and process archiving jobs and delete jobs. 14 User Manual CIE 3.3 Achiving

15 Second-level UMR Archiving Creating and processing archiving jobs How do you create an archiving job? Proceed as follows to create a archiving job. 1. In the UMR Administrator, click the Archive/delete page. 2. Click on the Archive UMR documents tab. 3. Click on the the Add button. An area is displayed with default settings for mode, time. 4. Select a mode. Mode once repeat after Explanation The archiving is only completed once. The archiving job is completed at regular intervals (cyclic archiving). Enter a number in the field and select a unit from the list box (minutes, hours, days, weeks, months). 5. Enter a time for starting and ending. To do this, enter a date and time in the Start and End field. You can also enter the date by clicking on the... button and clicking on the required day in the calendar. The Start field contains the current date and time by default. 6. Enter a period of time in the All documents older than field and select a unit (minutes, hours, days, weeks, months, years) from the list box. The default value is 1 day. All documents older than the period of time before the start will be archived. You can see this in the All documents before the column. Example: Start , Period of time: 3 months. Everything before will be archived. 7. Activate the archiving job. For further information please refer to the Kapitel How do you activate an archiving/delete job? on page Decide whether you want to save or discard the changes. 9. Confirm the archiving job by clicking the green check mark. The archiving job is added to the list of archiving jobs. Discard the archiving job by clicking the red cross. Which statuses can an archiving job take on? An archiving job can take on one of the following four statuses. Status disabled ready executing OK Explanation The archiving job is not enabled and will not be completed. The archiving job is ready and will be completed at the set time. The archiving job is just being executed. The archiving process has been completed. The status of an archiving job is displayed in the Status column. Edition /22/

16 Which icons can be displayed in the Previous Execution column? The Previous Execution column can display the following icons. Icons in red mean error messages and are displayed with the corresponding date and time. Icon Color Explanation Green red red previous execution o.k. [Previous Execution OK] System error Error in previous execution [System Error in previous execution] Parameter error Error in previous execution [Parameter Error in previous execution] How do you create an archiving job? Proceed as follows to change an archiving job: 1. Select the archiving job from the list and click on the corresponding pencil. The editable area is displayed. 2. Enter the changes. 3. Click on the green check mark to save your changes or click on the red cross to discard the changes. How do you delete an archiving job? Proceed as follows to delete a archiving job. 1. Select the archiving job from the list and click on the corresponding Deleted icon. You are asked whether you want to delete the archiving job. 2. Click on OK to delete the archiving job or click on Cancel, the job will not be deleted. Note The archiving job will be deleted permanently, i.e. it cannot be restored. 16 User Manual CIE 3.3 Achiving

17 Second-level UMR Archiving Activating/deactivating archiving/delete jobs How do you activate an archiving/delete job? After creating or editing an archiving/delete job you must enable it for execution. Complete the following steps: 1. Click on the pencil next to the archiving/delete job. The activate check box is displayed. 2. Activate this check box. The archiving/delete job is now activated. How do you deactivate an archiving/delete job? If an active archiving/delete job shall no longer be executed you must deactivate it. Complete the following steps: 1. Click on the pencil next to the archiving/delete job. The activated activate check box is displayed. 2. Deactivate this check box. The archiving/delete job is now deactivated. Duplicating archiving/delete jobs How do you duplicate an archiving/delete job? You can duplicate an existing job and then adapt it to your needs so as to avoid having to do all the settings manually for each new job. Complete the following steps: 1. Click on the pencil next to the job you want to duplicate. The job switches to the processing mode. 2. Click on the Duplicate button. The job is duplicated and is displayed directly under the original job. 3. Edit the duplicated job as required. Edition /22/

18 Creating and processing delete jobs How do you create an archiving job? Complete the following steps: 1. In the UMR Administrator, click the Archive/delete page. 2. Click on the Delete UMR documents tab. 3. Click on the Add button. 4. An area is displayed with default settings for mode, time. 5. Select the mode. Mode once repeat after Explanation The deletion is only completed once. The deletion is completed at regular intervals (cyclic deletion). Enter a number in the field and select a unit from the list box (minutes, hours, days, weeks, months). 6. Enter a time for starting and ending. To do this, enter a date and time in the Start and End field. You can also enter the date by clicking on the... button and clicking on the required day in the calendar. The Start field contains the current date and time by default. 7. Enter a period of time in the All documents older than field and select a unit (minutes, hours, days, weeks, months) from the list box. The default value is 1 day. All documents older than the period of time before the start will be deleted. You can see this in the All documents before the column. Example: Start , Period of time: 3 months. Everything before will be deleted. 8. Activate the delete job by enabling the check box in the Status column. 9. Click on the green check mark to save your settings or click on the red cross to cancel the process. 18 User Manual CIE 3.3 Achiving

19 Second-level UMR Archiving Which statuses can a delete job take on? A delete job can take on one of the following four statuses. Status disabled ready executing OK Explanation The delete job is not enabled and will not be completed. The delete job is ready and will be completed at the set time. The delete job is just being executed. The delete process has been completed. How do you change a delete job? Complete the following steps: 1. Select the delete job from the list and click on the corresponding pencil. The editable area is displayed. 2. Enter the changes. 3. Click on the green check mark to save your changes or click on the red cross to discard the changes. How do you delete a delete job? Note: The delete job will be deleted permanently, i.e. it cannot be restored. Complete the following steps: 1. Select the delete job from the list and click on the corresponding Deleted icon. You are asked whether you want to delete the delete job. 2. Click on OK to delete the delete job or click on Cancel, the job will not be deleted. Edition /22/

20 Tips and tricks This topic explains how to make use of second-level database archiving in the CIE. Do you have to archive? We recommend to archive regularly the entries in the database c3k to ensure a fast database access. What happens if the database is full? The umarchive database is automatically enlarged by 10% when the free memory drops below 100 MB. How often do we recommend archiving? The intervals for archiving your runtime database depend for example on the following factors: Number of documents Size of the documents Size of database Since these factors can vary considerably from one company to another it is not possible to make a general recommendation. However, by rule of thumb you should start the archiving process when your runtime database is 75 % full. 20 User Manual CIE 3.3 Achiving

21 Second-level UMR Archiving One-time archiving The following is an example of a one-time archiving process. Let us assume that we want to start the archiving process on at 8:00 pm and that we would like to archive all Call Center messages that are older than 3 months. Signal this as follows: How do you create an archiving job? Complete the following steps: 1. In the UMR Administrator, click the Archive/delete page. 2. Click on the Archive UMR documents tab. 3. Click on the Add button. 4. An area is displayed with default settings for mode and time. 5. Select the once mode. 6. In the Start field, enter for the date and 20:00 for the time. 7. Enter the figure 3 in the All documents older than field and select the unit Months from the list box. Now all UMR documents before will be archived. In order for this to actually happen, you must activate the archiving job. For information on how to activate an archiving job please refer to Kapitel How do you activate an archiving job? on page 21 Afterwards, please return to this place. 8. Click on the green check mark to include the archiving job in your list. How do you activate an archiving job? After creating an archiving job you must enable it for execution. Complete the following steps: 1. Click on the pencil next to the archiving job just created. The activate check box is displayed. 2. Activate this check box. The archiving job you have created is thus activated. Edition /22/

22 Cyclic archiving We recommend that you always create a cyclic archiving job for archiving UMR documents. For this purpose a sample archiving job was created in the Scheduler already during setup. During setup you decided whether the sample archiving job was activated or deactivated. Let us assume that you have already activated the sample archiving job during setup. Let us assume that you want to start the cyclic archiving job on at 8:00 pm and that you would like to archive all Call Center messages automatically once a month for 12 months until the You would like for each archiving process only to include the UMR documents that are older than 3 months at the time of the archiving job. Signal this as follows: 1. In the UMR Administrator, click the Archive/delete page. 2. Click on the Archive UMR documents tab. Select the sample archiving job and click on the pencil. An area is displayed with default settings for mode and time. 3. Select the repeat after mode, enter the figure 1 in the field and select the unit Months from the list box. 4. In the Start field, enter for the date and 20:00 for the time. 5. In the End field, enter for the date and 20:00 for the time. 6. Enter period of time 3 in the All documents older than field and select the Months unit from the list box. Now all UMR documents that are older than three months will be archived. Since you have already agreed to the activation of the cyclic archiving job during setup the activate check box is already activated. 7. Click on the green check mark to include the archiving job in your list. 8. Your modified cyclic archiving job will be completed as desired from :00 until :00 on the first of each month at 8:00 pm. Archiving do not working If the archive does not work, the following instructions may be helpful. Check the file rod.ini. May not work the name resolution. Replace the server name with the corresponding IP address. Example ArchDestOdbcConnect = Server = , Port = 5000; Database = umarchive; Text Size = Check the services: Archie Rod, Rod CommadExecuter, Rod Reposerv, Rod Rodomat, Rod scheduler server Check for these services the messages in TTrace. 22 User Manual CIE 3.3 Achiving

23 Glossary Archiving database DB server DDL scripts DNS Domain Second-level archiving: Documents are transferred to a second database for storage. The archiving job is completed by the Archie archiving process. Archie is a Reporting on Demand (RoD) process. The archiving database is needed because over time the runtime database is growing too big and because data access by customer applications will be made easier with a second database. The DB server administers the CIE system configuration. DDL scripts are database scripts in which it is defined how the database is to be constructed. DNS (Domain Name System) is a standard name service for Internet and TCP/IP. Using the DNS service client computers can register and resolve DNS domain names in the network. These names are used for searching for and accessing resources which are available on other computers in your own or in other networks, for example on the Internet. A domain is a group of computers that are part of a network and use a shared directory database. A domain is organized in levels and is managed as a single unit using shared rules and procedures. Each domain has a unique name. On the Internet domains are defined by means of an IP address. All devices that share the use of part of the IP address are in the same domain. In an Internet address the domain is generally the word or the number that describes the type of owner of the address, e.g..com or.org HTTP IP LAN LNA server See also IP address HTTP stands for hypertext transport protocol. HTTP is a general, status-less, object-oriented protocol for data transfer within the framework of the World Wide Web (WWW). IP stands for Internet Protocol. It is used to address and fragment data and transmit this data to the recipient. It is a 32-bit address that is used to identify a node in an integrated IP network. A unique IP address consisting of a network identifier and a host identifier must be assigned to each node in an IP network. This address is normally transmitted in dotted decimal point format, in which case the decimal value of each group of eight digits is separated by a point, for example LAN stands for Local Area Network. A LAN is a group of computers, which are interconnected in a network. The LNA server records changes in the database and informs the relevant processes of these changes. Edition /22/

24 Glossary Mailboxes ODBC Mailboxes for topics/agents are provided by the CIE. The mailboxes are displayed in the UMR WebClient as mailbox folders (these are tabs). ODBC stands for Open DataBase Connectivity (Open Database Connectivity) and is a database driver, and therefore provides a programming interface (API) that enables a programmer to develop his application irrespective of the database server used (the database). The technology makes it possible to integrate data from any applications into a database system. This interface was originally developed for Microsoft Access, but in the mean time has also been adopted by other software manufacturers. ODBC has since been established as the standard in many fields. Modern programming environments (e.g. Borland Builder) use ODBC to enable uncomplicated access to a wide range of different database management systems (using ready-made data-sensitive control elements). Data access is never made directly to a table or a database, but always via the corresponding (ODBC) component! Using ODBC it is possible to access any local or remote data source. PDF Runtime database SMTP UMR WebClient UMR Classes that define methods for handling the data resources from different database systems are available for object-oriented programming languages (e.g. C++). The programmer no longer needs to worry about any database-specific details. PDF stands for Portable Document Format. First-level archiving: Documents can can be archived using the UMR WebClient. These documents can be accessed from the UMR WebClient. They behave similarly to as yet unarchived documents. This is achieved by giving the documents in the runtime database an archive flag. SMTP stands for Simple Mail Transfer Protocol and is a layer-four protocol (application layer) in the OSI layer model. It is used to send to an Internet Service Provider's (ISP) SMTP server and from there on over the Internet to the recipient's mailbox. In this way, other SMTP servers can be used as intermediate stations. The UMR WebClient is a web-based processing interface component of the UMR system. An agent can use the UMR WebClient to log into or out of the UMR system and to read and process documents ( /fax/sms). The supervisor can also view agent mailbox folders and delegate/delete documents. UMR stands for Unified Messaging Routing. 24 User Manual CIE 3.3 Achiving

25 Index Index Symbols [Archie] 13 Numerics 1 23 A activate Archiving job 17 Delete job 17 Add (button) 15, 21 Adding a word Button 18 All data before the (column) 21 All documents before the (Column) 15, 18, 21 All documents older than (Field) 15, 18, 21, 22 ArchDestOdbcConnect 13 ArchDestOdbcDriver 13 ArchDestPwd 13 ArchDestUsername 13 Archie Archiving process 7 Archie archiving process 7 Archive flag 24 ArchiveDocuments 13 Archiving cyclic 15, 22 first-level 7, 24 second-level 7, 23 Archiving database 10 Archiving job activate 17 Deactivate 17 Delete them 16 duplicating 17 PIN 16 Prerequisite 14 Start 15, 21, 22 Status 15 Stop 15, 22 Archiving jobs creating 15 edit 15 Scheduler 8 Archiving process 10, 14 Archiving UMR documents (Tab) 15, 21, 22 Archiving Deleting (page in WebAdmin) 15, 21, 22 Page 18 ASA 23 B Button Adding a word 15, 18, 21 Refreshing views 14 C C3K_CONFIG_DOCINDEX 11 C3K_DOCPROP 11 C3K_DOCUMENT 11 C3K_DOCUMENT_INDEX 11 C3K_REQUEST 11 Client computer 23 Column All data before the 21 All documents before the 15, 18, 21 Previous Execution 16 Configuration 13 CopyCachedFaxPages 13 ON 11 creating Delete job 18 Cyclic archiving 22 cyclic archiving 15 cyclic deletion 18 D Database entries 14 DB password encrypted 13 DB user name 13 Edition /22/

26 Index Deactivate Archiving job 17 Delete job 17 Delete cyclic 18 Delete job activate 17 creating 18 Deactivate 17 Delete them 19 duplicating 17 PIN 19 Prerequisite 14 Start 18 Stop 18 Delete jobs Scheduler 8 Delete them Archiving job 16 Delete job 19 Delete UMR documents (Tab) 18 DeleteArchivedDocuments 13 Deleting the documents from the runtime database 8 Directory database 23 disabled (status) 15, 19 DNS (Domain Name System) 23 DNS domain names 23 DNS service 23 duplicating Archiving job 17 Delete job 17 E Edition 6 EnableUMR 13 encrypted DB password 13 End (archiving job) Field 15, 22 End (delete job) Field 18 Error code 9 Scheduler 9 Error in previous execution Parameter error 16 System error 16 Error messages Second-level archiving 9 executing (status) 15, 19 F Field All documents older than 15, 18, 21, 22 End Archiving job 15 Start 15, 18, 21, 22 Stop 18, 22 G Glossary 23 H History 6 I Information 5, 6 Internet 23 IP address 23 K Knowledge 6 N Name User target database 13 O ODBC driver 13 ODBC driver name 13 ODBC-Connectstring 13 OK (status) 15, 19 once 15, 18 Open Database Connectivity 24 P Page Archiving Deleting 15, 18, 21, 22 Parameter error 16 PIN Archiving job 16 Delete job 19 Prerequisite Archiving job User Manual CIE 3.3 Achiving

27 Index Delete job 14 Prerequisites Source database 10 Target database 10 Previous Execution (column) 16 previous execution o.k. 16 Properties Second-level archiving 8 R ready (status) 15, 19 repeat after 15, 18 rod.ini 13 Runtime database 10 S scheduled 14 Scheduler 9, 14 Archiving jobs 8 Delete jobs 8 Second-level archiving Error messages 9 Properties 8 UMR WebClient 8 Second-level UMR Archiving 7 Simple Mail Transfer Protocol 24 Standard archiving job 14 Standard name service 23 Start (archiving job) Field 15, 21, 22 Start (delete job) Field 18 Status Archiving job 15 disabled 15, 19 executing 15, 19 OK 15, 19 ready 15, 19 Store data Target database 11 System error 16 T Tab Archiving UMR documents 15, 21, 22 Delete UMR documents 18 Target database 13 Store data 11 TCP/IP 23 U Unified Messaging Router 24 Update (button) 14 W Writing the documents to the archiving database 8 WWW 23 Edition /22/

28 Index 28 User Manual CIE 3.3 Achiving