COPYRIGHTS & TRADEMARKS: For complete copyright and trademark information, go to www.zebra.com/
copyright.
WARRANTY: For complete warranty information, go to www.zebra.com/warranty.
END USER LICENSE AGREEMENT: For complete EULA information, go to www.zebra.com/eula.
Terms of Use
•Proprietary Statement
This manual contains proprietary information of Zebra Technologies Corporation and its subsidiaries
(“Zebra Technologies”). It is intended solely for the information and use of parties operating and
maintaining the equipment described herein. Such proprietary information may not be used, reproduced,
or disclosed to any other parties for any other purpose without the express, written permission of Zebra
Technologies.
•Product Improvements
Continuous improvement of products is a policy of Zebra Technologies. All specifications and designs are
subject to change without notice.
•Liability Disclaimer
Zebra Technologies takes steps to ensure that its published Engineering specifications and manuals are
correct; however, errors do occur. Zebra Technologies reserves the right to correct any such errors and
disclaims liability resulting therefrom.
•Limitation of Liability
In no event shall Zebra Technologies or anyone else involved in the creation, production, or delivery of the
accompanying product (including hardware and software) be liable for any damages whatsoever
(including, without limitation, consequential damages including loss of business profits, business
interruption, or loss of business information) arising out of the use of, the results of use of, or inability to
use such product, even if Zebra Technologies has been advised of the possibility of such damages. Some
jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above
limitation or exclusion may not apply to you.
Revision History
Changes to the original guide are listed below:
ChangeDateDescription
Rev A07/16Initial Release
-0307/17Updates to:
Instructions for handling HTTPS protocol.
Downloading and deploying DB Server specific java connector components.
Update versions and requirements.
Version 1.3.2 ............................................................................................................................. 45
Version 1.2.7 ............................................................................................................................. 45
Version 1.2.6 ............................................................................................................................. 45
6
About This Guide
Introduction
This installation guide describes how to install TekSpeech Pro Device and Operator Manager (DOM).
Topics covered in this guide are as follows:
•Introduction
•File Storage Setup
•Database Server Setup
•Application Server Setup
•Web Server Setup
•Network Load Balancing Setup
•DOM Upgrade
•Data Backup and Restore
•Rollback to Previous Version
•Setup Verification
•Version Information
Notational Conventions
The followingconventions are used in this document:
•Bold text is used to highlight the following:
•Dialog box, window and screen names
•Drop-down list and list box names
•Check box and radio button names
•Icons on a screen
•Key names on a keypad
•Button names on a screen.
7
•Bullets (•) indicate:
•Action items
•Lists of alternatives
•Lists of required steps that are not necessarily sequential.
•Sequential lists (e.g., those that describe step-by-step procedures) appear as numbered lists.
Icon Conventions
The documentation set is designed to give the reader more visual clues. The following graphic icons are used
throughout the documentation set. These icons and their associated meanings are described below.
WARNING! The word WARNING with the associated safety icon implies information that, if disregarded,
could result in death or serious injury, or serious product damage.
CAUTION The word CAUTION with the associated safety icon implies information that, if disregarded, may result
in minor or moderate injury, or serious product damage.
About This Guide
IMPORTANTtext text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text
NOTE NOTE contains information more important than the surrounding text, such as exceptions or
preconditions. They also refer the reader elsewhere for additional information, remind the reader how to
complete an action (when it is not part of the current procedure, for instance), or tell the reader where
something is located on the screen. There is no warning level associated with a note.
Related Documents and Software
For the latest version of this guide and all related documentation, go to: zebra.com/support.
Service Information
If you have a problem with your equipment, contact Zebra Global Customer Support for your region. Contact
information is available at: zebra.com/support
When contacting support, please have the following information available:
•Serial number of the unit
.
•Model number or product name
•Software type and version number.
Zebra responds to calls by email, telephone or fax within the time limits set forth in support agreements.
If your problem cannot be solved by Zebra Customer Support, you may need to return your equipment for servicing
and will be given specific directions. Zebra is not responsible for any damages incurred during shipment if the
approved shipping container is not used. Shipping the units improperly can possibly void the warranty.
8
About This Guide
If you purchased your Zebra business product from a Zebra business partner, contact that business partner for
support.
Provide Documentation Feedback
If you have comments, questions, or suggestions about this guide, send an email to EVM-Techdocs@zebra.com.
9
Introduction
Overview
TekSpeech Pro Device and Operator Manager (DOM) consists of four main components:
•Web server
•Application server
•Database server
•Data server.
This guide is presented in order of installation steps. All of the servers can be installed on one machine (see Single
Instance Application Server with Local DB and Data on page 13), be installed as clusters (see Multiple Application
Server Instance on page 15), or installed on multiple machines (see Multiple Application Server and Web Server
Instance on page 16). This guide also presents one example of load balancing in the clustered setup.
For an understanding of the solution stack, see Software Solution Stack on page 11.
TekSpeech Pro DOM System Architecture
Figure 1 TekSpeech Pro DOM in Relation to Other Components in the Complete System
10
Introduction
Hardware Components
Table 1 Hardware Components
ComponentDescription/Purpose
Database
Server
Application
Server
Web ServerProvide the web frontend to the Application Server. Includes browser access for administrators
Data StorageProvide unstructured data access to the application. Includes PDK files, firmware files, operator
Provide structured data access to the application.
Provide the execution of the TekSpeech Pro DOM application.
and web service access for device clients.
profiles, configurations, and extra resources. This can be provided locally on the same machine
as the Application server or provided remotely (For example, using NAS technology).
Software Solution Stack
Table 2 Required Software components
Stack
Component
Operating
System
Windows Server 2008 R2, 64-bit or
Windows Server 2012, 64-bit or
Windows Server 2012 R2, 64-bit or
Windows Server 2016, 64-bit
Version
Database
Server
Java RuntimeJava SE Runtime Environment 8uXX, 64-bit (version 1.8.0_131-b11 verified)
Consider the information in the following table when planning a TekSpeech Pro DOM system installation. The
information provided should help determine the correct architecture based on an organization's goals for size,
performance and reliability.
.
Table 4 System Architecture Scenarios
ScenarioFeatures
Single Instance Application Server
•Single local application server instance
•Single local web server instance
•Single local (or remote) database server
•Single local (or remote) data storage (NAS)
•Intended for small systems with less than 250
operators.
•The web server, application server, database
server, and storage could be provided on the
same machine.
•The database and/or data storage could be
provided on separate machines for improved
performance and reliability.
Multiple Instance Application Servers
•Multiple application server instances.
•Single or multiple, local or remote web server
instances.
•Remote database server
•Remote data storage (NAS)
•Provides for best performance.
•Provides for best redundancy and availability.
•Load balancing and application server affinity is
provided by the web server.
•Further redundancy can be provided with a
frontend load balancing technology.
12
Administrator Access
Table 5 Administrator Access
Introduction
Browser
Parameter
Target Screen
Resolution
Name and
Version
1280 x 1024 pixels
Google Chrome 34
Safari 7
Firefox 27
Internet Explorer 10
Minimum Requirement
System Architecture Scenarios
Single Instance Application Server with Local DB and Data
In this scenario, all of the software stack components are installed on one machine. This scenario should only be
used for small systems.
Figure 2 Single Instance Application Server with Local DB and Data
13
Introduction
Single Instance Application Server with Remote DB and NAS
In this scenario, the web server and application server are installed on one machine. The database server and
NAS are installed on separate machines. This scenario can be used in small to medium sized systems where
performance is important but redundancy is not important.
Figure 3 Single Instance Application Server with Remote DB and NAS
14
Loading...
+ 32 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.