EVision 7.0 Installation Guide For UNIX

TIE
Installation Guide
Installation of eVision for

UNIX Server and
WindowsClient
Release 7.0
Trademarks
eVision is a trademark and spEDI*map is a registered trademark of

TIE Kinetix. Microsoft, Windows and MS-SQL Server are either registered
trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries. Oracle is a registered trademark of Oracle
Corporation. Pentium is a registered trademark of Intel Corporation. A+ is
a trademark and Cleo is a registered trademark of Interface Systems, Inc.
UNIX is a registered trademark of The Open Group.
U.S. Government Restricted Rights
Use, duplication, or disclosure by the U.S. Government is subject to

restrictions set forth in subparagraphs (a) through (d) of the Commercial
Computer-Restricted Rights clause at FAR 52.227-19 when applicable, or in
subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013, or to TIE Kinetix's standard
commercial license, as applicable, and in similar clauses in the NASA FAR
Supplement.
Trademark and Copyright Owner
TIE Kinetix
1360 Energy Park Drive, Suite 110
St. Paul, MN 55108 USA
651.999.8600
24 New England Executive Park
Boston, MA 01803 USA
TIE Kinetix Confidential and Proprietary
THIS WORK CONTAINS VALUABLE CONFIDENTIAL AND PROPRIETARY

INFORMATION. DISCLOSURE, USE, OR REPRODUCTION WITHOUT THE
WRITTEN AUTHORIZATION OF TIE KINETIX IS PROHIBITED. THIS
UNPUBLISHED WORK BY TIE KINETIX IS PROTECTED BY THE LAWS OF THE
UNITED STATES AND OTHER COUNTRIES AND BY INTERNATIONAL TREATY
PROVISIONS. IF PUBLICATION SHOULD OCCUR, THE FOLLOWING NOTICE
SHALL APPLY:
Copyright 1996 - 2014
TIE Kinetix
All Rights Reserved
Document Title
Installation of eVision for UNIX Server and Windows Client

Release 7.0
May, 2014
Contents
Chapter 1
Chapter 2
2014 TIE Kinetix
Introduction
1-1
Scope of This Document
1-1
Terminology
1-1
System Requirements
System configuration rules
Hardware and software requirements
eVision Net/Server requirements
eVision Enterprise requirements
Connectivity requirements
1-3
1-3
1-6
1-7
1-8
1-9
Licensing
1-9
The Next Step
1-9
First-Time Installation
2-1
Licensing
Temporary license
Permanent license
Choosing a license
2-1
2-1
2-1
2-2
Parts of the Installation Process
2-2
Installing the Database
2-2
Before You Begin

Completing the pre-installation checklist
2-2
2-2
Installing eVision Server

Extracting eVision Server installation software
Running the installation script
Install EDI Standards and Options
2-3
2-4
2-4
2-10
Installing eVision Client

Running setup.exe
Welcome
License agreement
Customer Information
Destination folder
Select features
Installation progress indicator
2-11
2-11
2-11
2-12
2-12
2-13
2-13
2-16
Contents
Chapter 3
Chapter 4
ii
Installation completion and exit

Restart
Start menu
2-16
2-17
2-17
Configuring the eVision Workbench

Configure Options
eVision Workbench
2-17
2-18
2-19
Conclusion
2-20
Upgrading an Existing Installation
3-1
Licensing
Temporary license
Permanent license
Choosing a license
3-2
3-3
3-3
3-3
Before You Begin

Preparing for an eVision product upgrade
3-4
3-4
Upgrading eVision Server

3-4
3-5
3-5
3-12
Upgrading eVision Client

Running setup.exe
Welcome
License agreement
Destination folder
Select features
Restart
3-12
3-12
3-13
3-13
3-14
3-15
3-15
3-18
3-18
3-19
Testing eVision
3-19
Conclusion
3-20
Maintenance Issues
4-1
Modifying, Repairing or Removing eVision Client
4-1
Setting Up a Test Environment

Activating eVision
4-3
4-4
Backing Up and Restoring eVision
4-4
Disaster Recovery
4-5
2014 TIE Kinetix
Contents
Appendix A
Appendix B
2014 TIE Kinetix
DB Installation Considerations
A-1
Overview
Estimating disk space for the database server
Network protocols for the database server
Database security
Create a database instance
Test connectivity with the database server
A-1
A-1
A-1
A-1
A-1
A-2
Creating a TNS Name and DSN
A-3
Requesting a License
B-1
My-TIE
Submitting a license request
Checking the status of a license request
Downloading the license file
B-2
B-2
B-4
B-6
TIE Kinetix Technical Support
B-8
iii
Contents
iv
2014 TIE Kinetix
Chapter 1 Introduction
This manual describes how to install eVision for UNIX. The
UNIX version of eVision employs a UNIX system to host the
eVision Server and one or more Windows systems for the
eVision Client(s). A database server is also required, which may
run on the eVision Server, one of the eVision Clients or on its
own UNIX- or Windows-based system.
Electronic versions of all user documentation are present in a
root level folder named Documentation. This folder is present
on the install CD for eVision Client for UNIX and is copied into
the clients destination folder during the installation process
(referred to throughout this document as the setup program).
Scope of This Document

This chapter provides an overview of eVision, including
terminology, a list of eVision components, system requirements
and examples of some common eVision system configurations.
Chapter 2, First-Time Installation provides step-by-step
instructions for customers installing an eVision system for the
first time.
Customers using a previous version of eVision will find upgrade
instructions in Chapter 3, Upgrading an Existing Installation.
Chapter 4, Maintenance Issues provides information on other
(less common) procedures such as modifying, repairing or
removing eVision, setting up a test environment, backing up
and restoring eVision, and disaster recovery.
Database installation considerations are discussed in
Appendix A, DB Installation Considerations.
Instructions for requesting an eVision license are presented in
Appendix B, Requesting a License.
Terminology
database server. The computer on which the database
management software and the eVision database are installed,
2014 TIE Kinetix
1-1
Introduction
and which fulfills requests from client machines. Not to be

confused with the eVision Server, which may or may not be
installed on the same physical machine.
eVision Client. An eVision component that manages
workflows. It consists of two user interface modules, eVision

Workbench and eVision Workflow Monitor. An eVision system
can support multiple clients, each installed on a different
computer. eVision Client can only be run under Windows.
Note that the term eVision Client is often used interchangeably
to refer to the eVision Client software or to the computer on
which the eVision Client software resides.
eVision Net/Server. An eVision configuration designed to
support eVision over a network, using one or more eVision

Clients.
eVision Enterprise. An eVision configuration designed to
support multiple eVision Clients. eVision Enterprise has all the

functionality of eVision Net/Server, along with additional
capabilities and components not available with eVision
Net/Server.
eVision Server. The eVision component that manages
communications between the client(s) and the database. There

can be only one eVision Server in any eVision system. The
server software may reside on its own UNIX-based computer or
on a UNIX-based computer with the database.
Note that the term eVision Server is often used interchangeably
to refer to the eVision Server software or to the computer on
which the eVision Server software resides.
eVision Workbench. The user interface component of the
eVision Client software, from which you create and manage

workflows. eVision Workbench can only be run under Windows.
eVision Workflow Monitor. The eVision Client GUI module that

provides feedback on the status of workflow processes.
Messenger Client. An eVision Enterprise-only component that
bundles wflaunch with scripts that utilize eVision Enterpriselevel mailboxing features.
spEDI*map. The mapping component of the eVision Client
software. spEDI*map can only be run under Windows.
workflow. A defined sequence of computer commands that,
when executed, performs meaningful work.
1-2
2014 TIE Kinetix
Introduction
wflaunch. An eVision component, available only on eVision
Net/Server and eVision Enterprise systems, that allows

launching of eVision workflows from a script running on a
remote machine. Also called Workflow Launch Client.
System Requirements
eVision software is designed for a client-server environment
under the UNIX (eVision Server) and Windows (eVision
Client)operating systems. The network must use TCP/IP
protocol.
Numerous applications, from TIE as well as other software
providers, make use of Java code. Each machine on which you
plan to install eVision wflaunch or eVision Messenger Client
must also have either a Java 2 Platform Standard Edition 5.0 or
higher runtime environment (J2SE JRE) or development kit
(J2SE JDK) installed.
A complete copy of eVision for UNIX consists of three elements.
They may reside on as few as two machines. The eVision
elements are:
eVision Server
database server
at least one eVision Client
eVision for UNIX supports the Oracle database, version 10g or

higher. Regardless of the Oracle Server version, the Oracle 10g
client and shared libraries must be installed on the eVision
server machine.
The eVision Server, the eVision Client, and the relational
database have different configuration requirements when they
are installed on different computers. The requirements are
described in this section.
System configuration rules

These rules govern eVision system configuration. Remember
that the eVision Server and the database server are different
components.
You may distribute the eVision Server software, relational
database management system with database files and one or
more copies of eVision Client software over multiple computers.
The following rules apply:
2014 TIE Kinetix
1-3
Introduction
An eVision configuration may have only one copy of

eVision Server software installed on one computer.
An eVision Server can support one or more clients.
An eVision configuration may have only one copy of

eVision Client software installed per computer.
An eVision Server and its clients must all use the same
instance of the relational database.
The database server may hold two or more eVision

database instances, but each instance must be linked to
a different eVision Server.
Different eVision Servers cannot switch or share

databases.
The eVision Client has a direct interface with the eVision

Server and the database server.
The following three illustrations show possible configurations

for an eVision production system, each with two clients.
Throughout this document, references to eVision should be understood to apply
to both eVision Net/Server and eVision Enterprise, unless otherwise noted.
The figure on the left is the most common configuration while

the one on the right is the least common. Dashed lines denote
links made via CS Connector and solid lines represent database
connectivity (ODBC) links.
Fig 1. Sample eVision production system configurations
1-4
2014 TIE Kinetix
Introduction
The following illustration shows another possible configuration

for an eVision production system, again with two clients, but
with each software component residing on its own machine.
Fig 2. Another sample eVision production system configuration
Finally, here is a possible configuration using two eVision

Servers, one devoted to the production system and the other
to a test system. The database server runs two instances of the
database, one for each system.
Fig 3. Sample dual eVision Server system
2014 TIE Kinetix
1-5
Introduction
Hardware and software requirements

The hardware requirements listed here may vary according to
usage and volume of data, and are guidelines only. When the
eVision Server and the database server reside on the same
machine, all requirements are increased.
Estimating Disk Space for the eVision Server. eVision needs
space for the database server and space to store the raw
electronic data interchange (EDI) data transmitted and
received on the eVision Server.
Estimate the amount of EDI data that you will exchange daily
and multiply that by the number of days you will keep the EDI
data online. Because larger amounts of EDI data require
additional storage space for temporary application file data,
multiply the result by 1.5. Add 100 megabytes for programs
and overhead.
EXAMPLE: If you send and receive a total of one megabyte
(MB) daily and plan to keep the data online for 30 days,
calculate as follows:
30 MB
x 1.5
45 MB
+ 100 MB
145 MB
monthly turnover
for all data
for programs and overhead
total
In this example, you should set your minimum space to 145

MB.
Our example assumes that data is kept for 30 days before it is
archived, although a large organization must archive more
often than this. Archiving more frequently requires less
database space. Archiving batches, but keeping audit
information online, requires more database space.
If you are installing the database on a separate server, a good
method to approximate your database server storage
requirement is to set the figure at about 70% of the eVision
Server storage requirement. Of course, if you use the database
for other applications in addition to eVision, your storage
1-6
2014 TIE Kinetix
Introduction
requirements will be significantly larger, to accommodate those

other applications.
Its advisable to overestimate the space you think you will need, especially if
you will be unable later to increase your disk capacity dynamically without
disrupting the existing applications.
eVision Net/Server requirements

eVision Server. This table lists requirements for eVision
Net/Server when the database server resides on another

computer.
Item
Requirement
Operating System
HP-UX 11.23 64-bit (PA-RISC or Itanium), Solaris 10 64-bit (SPARC

or Opteron), Red Hat Enterprise Linux 3.0/4.0 32-bit
Processor
Recommended: 500MHz or higher
RAM
Minimum: 256 MB
Recommended: 1+ GB
Mass storage
Minimum: 500 MB SCSI (ultra-wide)

Recommended: 1+ GB
Client/server
connection
TCP/IP
Database Server. An Oracle 10g (or higher) database is
required. Since storage requirements vary from database to

database, we encourage you to refer to your database vendor
for storage requirement specifications. As a general guideline,
consider approximately 70% of the space requirement on the
eVision Server as a suggested storage requirement value for
the database server.
eVision Client. The eVision Client may run on any of the listed
Windows operating systems that meet the requirements listed

in this table.
2014 TIE Kinetix
Item
Requirement
Operating System
Windows 2008 Server, Windows 2012 Server, Windows

7 or Windows 8
SVGA monitor, 800 x 600 pixels.
Processor
Minimum: Pentium 233 MHz

Recommended: Pentium 500+ MHz
1-7
Introduction
Item
Requirement
RAM
Minimum: 64 MB
Recommended: 128+ MB
Mass storage
200 MB free disk space
Client/server connection
TCP/IP (included with the Windows operating systems)
eVision Enterprise requirements

eVision Server. This table lists the requirements for the eVision
Enterprise server when the database server is on another

computer.
Item
Requirement
Operating System
HP-UX 11.23 64-bit (PA-RISC or Itanium), Solaris 10 64bit (SPARC or Opteron), Red Hat Enterprise Linux 3.0/4.0
32-bit
Processor
Recommended: Multiprocessor Server 500MHz or higher
RAM
Minimum: 256 MB
Recommended: 1+ GB
Mass storage
Minimum: 10-35+ GB for higher volumes

Recommended: Multiple SCSI Channels
TCP/IP
Database Server. An Oracle 10g (or higher) database is
required. Since storage requirements vary from database to

database, we encourage you to refer to your database vendor
for storage requirement specifications. As a general guideline,
consider approximately 70% of the space requirement on the
eVision Server as a suggested storage requirement value for
the database server.
eVision Client. The eVision Client may run on any of the listed
Windows operating systems that meet the requirements listed

in this table.
1-8
Item
Requirement
Operating System
Windows 2008 Server, Windows 2012 Server, Windows

7 or Windows 8
SVGA monitor, 800 x 600 pixels.
Processor
Minimum: Pentium 233 MHz

Recommended: Pentium 500+ MHz
2014 TIE Kinetix
Introduction
Item
Requirement
RAM
Minimum: 64 MB
Recommended: 128+ MB
Mass storage
200 MB free disk space
TCP/IP (included with the Windows operating systems)
Connectivity requirements
Depending on the specific relational database you use,
database connectivity software may also need to be installed.
Connectivity software will establish and maintain the actual
communication with the database. The eVision server currently
requires the Oracle 10g client shared library files. Generic
software such as ODBC drivers will serve as the bridge between
eVision Client or eVision Server and the database connectivity
software. The ODBC driver configuration that communicates
with Oracle is identified as a data source name (DSN). The
eVision components use the DSNs to communicate directly with
the database.
Licensing
Installation CDs include a 60-day temporary runtime license.
The 60-day period begins when the CD is created, not when the
software is installed. If the period expires, you may request
another temporary license from TIE Kinetix. Your permanent,
machine-specific license must be acquired separately and may
be done before or after the installation is performed.
When eVision is installed, the setup program searches for the
license file. The file must reside in any browsable folder, that
is, it must be in a folder visible to the setup program. The setup
program copies the license into a default folder where eVision
will always look for it.
The Next Step

If you are installing eVision for the first time, go directly to
Chapter 2, First-Time Installation. If you are upgrading an
existing eVision system, go to Chapter 3, Upgrading an
Existing Installation.
2014 TIE Kinetix
1-9
Introduction
1-10
2014 TIE Kinetix
Chapter 2 First-Time Installation

This chapter assumes that you have not yet installed your
relational database or the eVision software.
Always install the eVision Server before installing eVision Clients. The eVision
services are part of the eVision Server installation, and these services must be
running to properly install and configure the eVision Clients.
Licensing
To use your eVision software, you must have a license. Every
eVision installation CD comes with a temporary license which
permits you to use the software until you acquire and install a
permanent license.
Temporary license
The supplied temporary license is good for sixty (60) days from
the time the CD was created, not from the time the software is
installed. So, for example, if you install your software 53 days
after the CD was created, you will only be able to run eVision
for seven days. In such a case, you may request another
temporary license if you have not yet acquired your permanent
license.
Permanent license
Your permanent license is one created by TIE Kinetix, based on
information provided by you about the machine which is to
function as your eVision Server. The license file you will receive
contains information specific to that machine, and that machine
alone will be recognized as the eVision Server. For this reason,
you should request your permanent license only when your
choice of machines for the eVision Server is no longer subject
to change.
See Appendix B for details on requesting a permanent license.
2014 TIE Kinetix
2-1
Choosing a license
During installation, you will be prompted for the license to use.
You may select the supplied temporary license, or path to the
location of your permanent license.
Parts of the Installation Process

The installation process consists of three parts: installing the
database, installing eVision Server and installing eVision
Client(s).
Database installation. Since your database is not supplied by
TIE Kinetix, its installation is a process distinct from eVision

installation. The TIE Kinetix-supplied CD-ROM only contains
installation software for eVision.
eVision Server installation. The compressed file containing all
the necessary installation files and scripts (ship.cpio on the

installation CD-ROM) must be copied to the UNIX server and its
files extracted. Then, the installation script instEDI must be run.
eVision Client installation. The eVision setup program
(setup.exe on the installation CD-ROM) allows you to choose to

install and configure client components on each eVision Client
machine.
Installing the Database

Your database administrator should install the database, with
database owner access, on the database server. For details,
refer to Appendix A, DB Installation Considerations.
When the database is installed and running, continue with the
following section, Before You Begin.
Before You Begin

Completing the pre-installation checklist
Before you install eVision, complete one of the following
checklists. Later in the installation process, youll need the
information you supply here to configure eVision Server and
eVision Client to communicate through ODBC. See your system
administrator if you need help. After completing the
2-2
2014 TIE Kinetix
appropriate checklist, continue with Installing eVision Server

on page 2-3.
Table 2-1
Selecting the checklist to use
Database
Do you have
connectivity?
Checklist to use
Oracle
No
Table 2-2
Oracle
Yes
Table 2-3
Table 2-2
Complete if you dont have connectivity with Oracle database
Response
Question
What is the service name?
What network protocol will be used?
What is the host name?
What port number is to be used?
What is the net service name (or TNS)?
Table 2-3
Complete if you have connectivity with Oracle database
Response
Question
What is the net service name?
What is your database login ID and password?
What is the name of the eVision Server?
What port ID will you use on the eVision Server?
What is the UNIX username and password?
What port ID will you use on the eVision Server for CS
Connector?
Installing eVision Server

To perform this installation you will copy the compressed file to
the UNIX server and extract its contents, then run the
installation script.
2014 TIE Kinetix
2-3

When installing eVision Server software from a CD-ROM, remember that a
CD-ROM from TIE Kinetix is not a mountable device.
Connect to the UNIX server using Telnet or a similar utility.
Create a directory on the server system where the eVision

software will be installed. We suggest naming it eVision.
Extract the installation files from the shipped files on the

media into the directory you just created. To do this, run the
CPIO command with the following switches:
cpio icvBdum < dev/device_filename
where device_filename specifies a load device, for example

rmt0, where the TIE installation media is located. If youre
installing on a Linux server, run this CPIO command:
cpio ivBdum < dev/device_filename
When the files are extracted, read the ver_rel.txt file for
version-specific preinstallation instructions. These include
the required settings for environment variables specific to
each UNIX platform.
When youve completed the instructions in ver_rel.txt,

continue with the next section.

In the following section, the text that is bolded represents the
prompts displayed by the instEDI script and the regular text
identifies your instructions.
1
Run instEDI from the eVision directory (or EDIhome). You

receive this prompt:
eVision installation script

eVision needs a startup script installed in a directory in your
path. Enter the directory to install to, or hit <Enter> to
default to current directory (current directory).
2-4
2014 TIE Kinetix
Type name of the directory to install to or press the Enter key

to use the current directory. You receive this prompt:
Ok to install startup scripts to (current directory)?

Enter N to re-enter directory or X to exit
(Press <Enter> to continue installation)
Press Enter to proceed. The following text is displayed:
Checking for running services

No services running. Installation proceeding...
Uncompressing the new programs
Uncompressing bin/AuditAgent.Z
Uncompressing bin/CSConnect.Z
Uncompressing
[the list of files being uncompressed continues to

completion]
Updating base evision files
.
..
Base evision files installed successfully
Setting environment variables for clear screen and pager commands
You receive the prompt:
Creating startup script: <current directory>/evenv

Detected <OS name> Operating System
Extracting sharelibs from shlib.tar
shlib.txt
.
Would you like to configure the server now?
Type Y.
This script creates an evision.ini file to configure the eVision Server and
database.
Validating evision.license file for valid key...
The license file is valid.
Information for License File evision.license:
[information specific to your license appears here]

5
Would you like to replace it with a a different license file?
2014 TIE Kinetix
2-5
Type Y to replace the existing license with a new one (enter

the complete path to the license file when prompted) or N to
keep the existing license.
6
You receive the following prompt:
Would you like to add e-mail notification settings?
Type Y and respond appropriately to each of the following

prompts, or N and skip to the next step.
Enter the default email address to send mail from : <email address of
sender>
Enter the name of the SMTP server you will be using :<mail server name>
Some UNIX systems require you to use an escape character \ to precede the @
symbol in email addresses: john.doe\@mycompany.com
Enter the SMTP Port Number (e.g., 25) :

<mail server port>
Enter the Port ID for CS Connect [<CS Connector port (default is 2010)>]:
Enter the new Port ID or press Enter to accept the default.

8
Enter the login name for Database :
Enter your login name.

9
Enter the Password for the database login :
Enter your login password.

10 You receive the following prompt:
Enter the Access Library Name [ORACLE] :
Enter the Access Library Name or press Enter to accept the

default.
2-6
2014 TIE Kinetix

Enter the Database Alias Name (if local leave blank). Here you must
supply the name of your database server, as it is known to your
database client. Typically, the server name is established when your
database is installed. See your system administrator if you are in doubt
:
Enter the Database Alias Name.

Enter the Database Name (if local leave blank). If you RDBMS system
supports the notion of multiple databases driven by a single server,
supply the name of the database you wish to use. If not, just hit enter. :
Enter the Database Name or press Enter.

13 You receive the message:
eVision configured successfully
In the event the configuration fails, the process asks you to

reconfigure the server. Otherwise, you will see the following
information displayed:
Checking settings with chkdb utility.
User: <database username>
Password:
**********
Access Info: <database access library>
Server: <database server name>
Database connection valid.
14 If you chose to add email settings in Step , youll see the
following prompt. If you answered N in Step , skip to Step .
Would you like to test email notifications?
Type Y to test email notifications (described below). To skip

the test, type N and continue with to Step .
2014 TIE Kinetix
2-7
eVision Mail Notification Settings

---------------------------------Mail to:
<e-mail address sent from>
Mail from: <e-mail address sent from>
Inbox server:Outbox server:

<mail server name>
SMTP port:
<mail server port>
POP3 port:
0
Tracing enabled:
No
Tracefile name:
Notification enabled: Yes
Local Host: <host name>
Checking SMTP Server status:
Address: <mail server name and (IP address)
Port: <mail server port>
Attempting to connect to SMTP server and send a test mail...
Connected...
Sent hello from <host name>...
Connected...
Set To: and From: fields...
Sent message...
Shut down connection...
Success. Check mailbox.
Was the test message delivered successfully?
Type Y.
2-8
2014 TIE Kinetix
15 Next youre prompted to allow the SPLOAD process to load
your database tables.
Loading eVision databases with spload using install

Storing results of database load into file spload.log
Checking database connection
Password:
**********
16 You will see instructions displayed that are similar to the
following:
----------------------------------------------------------------SPLOAD is about to examine your database, and prepare it for eVision.

If you are installing eVision to an existing eVision database,
no data will be erased or re-initialized.
Please read the screen carefully, as it will tell you what actions
will be taken.
----------------------------------------------------------------Do you wish to continue?
[Y/N]
Type Y.
17 Next, you see this prompt:
Checking to see if eVision tables are already installed.
No eVision tables found. Proceeding with database initialization.
[a series of database messages appears]

installing Perl
nnnn blocks
Installation complete!
Password:
**********
2014 TIE Kinetix
2-9
18 Next, the script installs the necessary Comm packages.

Server ready to accept COMM install.
Installing Comm packages
[a series of comm installation messages appears]

Comm Packages installed.
19 You will be prompted, Y/N, for each selected Version
Standard you want to install. Be sure to select only those

Versions you actually need.
Installation complete.
Enter evenv to run eVision via command line or scripts
To run the evenv script from any directory,
you must add <current directory> to your path.
Otherwise, you must change directory to <current directory>
before executing this script.
20 Type evenv.
21 Now at the EVENV prompt, start the eVision Audit Agent, CS
Connector, and Workflow Maestro services by typing evStart.
To verify that these services are running, type

showservices.
To stop the eVision services, type evStop.
For information on other switches, type the service
name followed by -h.
22 Exit the EVENV script by typing exit.

23 Disconnect from the eVision UNIX server.

If you were shipped EDI Version Standards or other options for
the eVision Server in a separate file, load the software now by
entering the cpio command in the format appropriate to the
media. This step is unnecessary if the server Version Standards
were included in your eVision Server software.
If you have EDI version tables to install from other media,
install them by typing instTABLES. Under normal install
conditions instEDI runs this script. The instTABLES script can
also be used to install tables you originally chose not to install.
2-10
2014 TIE Kinetix
If you have communiction scripts to install, install them by

typing instCOMM. Under normal install conditions instEDI
runs this script. The instCOMM script can also be usd to install
communications scripts you originally chose not to install.
Based on need or purchase of additional functionality, you may
need to perform some or all of the following steps to install
these function(s) on the eVision Server.
If you have purchased the Status Feedback Loop option for
your SAP system, install the option by typing instAIMSFL. You
must restart your eVision services after this step.
Installing eVision Client

To perform this installation you must be logged onto each
machine with Administrator rights. Remember, the eVision
Server must be installed before you install the eVision Client(s).
Running setup.exe
Insert the eVision installation CD-ROM in the drive. The setup
program autoruns. If it does not, navigate in Windows Explorer
to the root of the CD-ROM drive and double-click setup.exe.
Welcome
When the setup program starts, it briefly displays some
information-only dialog boxes and then the InstallShield
Wizard prepares itself to run. After this initialization process is
complete, the Welcome screen displays.
Click Next.
2014 TIE Kinetix
2-11
License agreement
The License Agreement screen appears.
In order to install eVision Client, you must agree to the terms

of this license. Select the I accept the terms of the license
agreement radio button and click Next.
The license agreement to which this step refers is not to be
confused with the license file provided by TIE Kinetix. You must
agree to the terms of this license agreement in order to install
the software; the license file must be installed in order to run
the software.
The Customer Information screen appears.
2-12
2014 TIE Kinetix
By default, the name and company to which the computer is

registered appears in the User Name and Company Name fields.
Click Next to accept the defaults, or make any necessary
changes and then click Next.
Destination folder
On this screen you specify the base directory in which you want
eVision Client installed. The default is C:\TIE\eVision .
To accept this folder, click Next.
To choose a different folder, click the Change button.

The Choose Folder dialog box appears. Navigate to the
folder in the Directories: tree structure or type in the
complete path in the Path: field. If the folder you specify
does not exist, the setup program will create it for you.
Select features
In this part of the installation, you are presented with a list of
possible components to install.
The components are grouped into the following categories:
Server Components, Server Standards, Comm Scripts, Client
Components, spEDI_map Standards, Web Components and
UNIX Installations. Of these, only three apply to eVision Client:
Client Components, spEDI_map Standards and UNIX
Installations.
2014 TIE Kinetix
2-13
Client Components. At the minimum, you will install
Workbench Client. Unless you have custom mapping

capabilities of your own, you must also install spEDI_map.
Workflow Launch Client (wflaunch) is available to eVision

Net/Server users. Messenger Client bundles wflaunch with
mailboxing features and is available to eVision Enterprise users
only.
Heres a summary of the Client Components appropriate for the
two eVision configurations:
eVision
configuration
Workbench
Client
spEDImap
Net/Server
Enterprise
Messenger
Client
Workflow
Launch Client
spEDI_map Standards. This set of standards is for the use of
the eVision Client. You should install the same standards at
2-14
2014 TIE Kinetix
each client that you installed (or will install) on the eVision
Server.
Installation of client standards is much less time-consuming

than server standards; we recommend you select them during
the initial installation.
UNIX Installations. If you use a UNIX machine to control an
eVision Server remotely, you may install these UNIX versions

(scripts) of eVision components.
The files that are installed are self-extracting files. After they
are copied to the eVision Client you must move them to the
UNIX machine that will remotely control the eVision Server.
When the files are run from there, they will install themselves
in the proper locations.
2014 TIE Kinetix
2-15

The setup program is ready to begin copying files to the
computer.
Click the Install button to begin the file copy process.

An installation progress indicator appears as files are copied
from the CD-ROM to the computers hard drive.

At the completion of the setup program, a screen similar to the
following appears.
By default, the option to view the RELEASE NOTES file is

checked. When you click the Finish button, the RELEASE NOTES
2-16
2014 TIE Kinetix
file appears. This file summarizes the current version of eVision

in the following categories: Enhancements and Changes/Fixes.
If you dont wish to view the RELEASE NOTES file, clear the
checkbox before clicking Finish.
You can view the RELEASE NOTESfile anytime by
clicking the Windows Start button, then selecting
Programs->TIE Kinetix->eVision Release Notes or
navigating to the folder in which you installed eVision and

opening release_notes.html.
Restart
A dialog box similar to the following appears. We strongly
recommend you select the default option to restart now.
Start menu
When the setup program is complete, your Start menu will have
a new TIE Kinetix folder with shortcuts to the following: eVision
Release Notes, eVision Workbench, eVision Workbench Help,
eVision Workflow Monitor, spEDI*map, spEDI*map Help and
Uninstall eVision.
Configuring the eVision Workbench

Follow the instructions in this section for each computer on
which eVision Client is installed.
2014 TIE Kinetix
2-17
Start eVision Workbench. Youll see a message box similar to

the one shown below.
Click OK.
Dont be concerned about failed tests at this point. Validity test failures are to be
expected, particularly on remote eVision Clients, because the clients have not
yet been fully configured.
Configure Options
Database Setup. Open the Options dialog box (select Tools->Options)
and select the Database Setup tab.
Make sure that all fields on this tab match the choices you made
during the installation of the eVision Server. Make any
necessary changes.
2-18
2014 TIE Kinetix
Now select the CS Connector tab.

CS Connector.
Change eVision Server Name to the correct name.
If you chose a port ID other than the default 2010 during

installation of the eVision Server, change Port ID here to
match it.
Click OK to close the Options dialog box.

Exit the eVision Workbench.
eVision Workbench
Start eVision Workbench again. Now you should see a message
box similar to the one shown below.
2014 TIE Kinetix
2-19
Conclusion
This completes the installation process. If you experience
problems with the installation and cannot resolve the issue with
these instructions, call TIE Kinetix Technical Support at 1-877787-7644 or send an email to support@tiekinetix.com.
2-20
2014 TIE Kinetix
Chapter 3 Upgrading an Existing

Installation
This chapter assumes that you are running a previous version
of eVision and are already aware of all installation and database
connectivity issues involved with installing and running the
product.
Upgrading your eVision software modifies eVision executables
in the eVision directory structure and database table schemas.
The upgrade process preserves existing data, maps, and other
data such as trading partner setups. If there are schema
changes, the upgrade process will export data from the
affected database tables, modify the schema, and reimport the
saved data.
We strongly recommend that you have a test eVision Server license, and that you install
the upgrade on your test server with a current copy of your production data. After you
have tested the upgrade and are sure it works, install it on your production system.
In order to upgrade to eVision 5.x, you must be running eVision 4.2, build 521
or higher. If you are running an earlier version, you must first upgrade to
version 4.2, build 521 or higher and then upgrade to 5.x.
The upgrade installation is almost identical to the first-time
installation, with the following exceptions:
2014 TIE Kinetix
When you upgrade a remote eVision Client, by default the

upgrade will be installed in the same folder as the old
software. It should not be installed anywhere else.
3-1
The setup program backs up your BIN directory into a

directory called BIN_<date>, where <date> is the
current date. After the upgrade is tested and in
production, have your system administrator remove the
backup BIN.
Always note current directory permissions if they have been altered from the
default as installed values. Directory permissions may be reset to default values
by the upgrade process.
The setup program upgrades the database tables and

rebuilds selected tables in the new layout. Youll be
prompted to confirm that you want to execute this step.
Always note if database tables have special permissions set for users other than
database user creating the tables. These special permissions may be lost if the
table is updated by dropping and reloading the table. Also any new tables added
during upgrade process may require your special permissions to be set.
The setup program also upgrades the base workflows

that shipped with your system to the new format,
including all workflows that were installed with your
initial eVision system. The users workflows remain
intact.
Its not necessary to reinstall any existing standards, but

you may wish to install new standards that were
unavailable in previous versions.
Always install the eVision Server before installing eVision Clients. The eVision
services are part of the eVision Server installation, and these services must be
running to properly install and configure the eVision Clients.
Licensing
To use eVision software, you must have a license. If you are
upgrading existing eVision software, you already have one.
You may be able to continue using your current license, or you
may have to request a new one, depending upon the nature of
the upgrade.
3-2
2014 TIE Kinetix
If you are upgrading to a new version of eVision (for

example, from 4.x.x to 5.x.x, or from 5.0.x to 5.1.x), you
must replace your current permanent license with a new
one.
If you are simply upgrading to a newer build of your

current version (for example, 5.0.315 to 5.0.318), you
can continue using your current license.
If you must replace your permanent license, you may use the
temporary license included on the eVision installation CD. The
temporary license permits you to use the software until you
acquire and install your new permanent license.
Temporary license
The supplied temporary license is good for sixty (60) days from
the time the CD was created, not from the time the software is
installed. So, for example, if you install your software 53 days
after the CD was created, you will only be able to run eVision
for seven days. In such a case, you may request another
temporary license if you have not yet acquired your permanent
license.
Permanent license
Your permanent license is one created by TIE Kinetix, based on
information provided by you about the machine which is to
function as your eVision Server. The license file you will receive
contains information specific to that machine, and that machine
alone will be recognized as the eVision Server. For this reason,
you should request your permanent license only when your
choice of machines for the eVision Server is no longer subject
to change.
See Appendix B for details on requesting a permanent license.
Choosing a license
During installation, you will be prompted for the license to use.
You may select the supplied temporary license, or path to the
location of your permanent license.
2014 TIE Kinetix
3-3
Before You Begin

Preparing for an eVision product upgrade
1
Read through the release_notes.html file contained in the

root directory on the eVision CD-ROM. This document lists
changes to the eVision system since the last release.
In Workbench, disable all scheduled activity.
Exit Workbench and all other processes that connect to the

eVision Server.
Back up your system, making a complete copy of the eVision

directory and the database instance. Make sure the copies
are identical to the originals and that no data was processed
following the backup.
If you plan to install upgraded communication scripts, you

should copy your mailbox setup information. The best way
to do this depends upon the kind of scripts youre using:
if youre using Perl communication scripts, copy your

comm\defaults directory.
otherwise, copy your comm\commpkg\name\van
directory, where name is your communications
package (like Aplus or 3780Plus) and van is your VAN
subdirectory.
If you have modified any of the scripts supplied with eVision

without renaming them, make sure you copy these scripts
to another directory because the setup program will
overwrite them in the eVision script directory. We
recommend renaming the customized versions of these
scripts and using the renamed scripts in production.
Similarly, if you have modified any of the standard Workflow

Actions or Workflow Objects supplied with eVision, rename
them. During the upgrade process, eVisions pre-configured
Workflows are reset to their original parameters.
Note that all optional components you use, such as

wflaunch, Messenger Client or the SAP status feedback loop,
must be upgraded at the same time as the eVision Server.
Upgrading eVision Server

To perform this installation you will copy the compressed file to
the UNIX server and extract its contents, then run the
installation script.
3-4
2014 TIE Kinetix

When upgrading eVision Server software from a CD-ROM, remember that a
CD-ROM from TIE Kinetix is not a mountable device.
Connect to the UNIX server using Telnet or a similar utility.
Create a directory on the server system as a backup

directory for your existing eVision software. Move all the
contents of the current eVision directory into the backup
directory.
Extract the installation files from the shipped files on the

media into the installation directory. To do this, run the CPIO
command with the following switches:
cpio icvBdum < dev/device_filename
where device_filename specifies a load device, for example

rmt0, where the TIE installation media is located. If youre
installing on a Linux server, run this CPIO command:
cpio ivBdum < dev/device_filename
When the files are extracted, read the ver_rel.txt file for
version-specific preinstallation instructions. These include
the required settings for environment variables specific to
each UNIX platform.
When youve completed the instructions in ver_rel.txt,

continue with the next section.

In the following section, the text that is bolded represents the
prompts displayed by the instEDI script and the regular text
identifies your instructions.
1
Stop the eVision services.
Run instEDI from the eVision directory (or EDIhome). You

receive this prompt:
eVision installation script

eVision needs a startup script installed in a directory in your
path. Enter the directory to install to, or hit <Enter> to
default to current directory (current directory).
2014 TIE Kinetix
3-5
Type name of the directory to install to or press the Enter key

to use the current directory. You receive this prompt:
Ok to install startup scripts to (current directory)?

Enter N to re-enter directory or X to exit
(Press <Enter> to continue installation)
Press Enter to proceed. The following text is displayed:
Checking for running services

No services running. Installation proceeding...
Storing old programs in bin.old and uncompressing the new
programs
Uncompressing the new programs
Uncompressing bin/AuditAgent.Z
Uncompressing bin/CSConnect.Z
Uncompressing
[the list of files being uncompressed continues to

completion]
Updating base evision files
.
..
Base evision files installed successfully
Setting environment variables for clear screen and pager commands
Creating startup script: <current directory>/evenv

Extracting sharelibs from shlib.tar
shlib.txt
.
Would you like to configure the server now?
Type Y.
This script creates an evision.ini file to configure the eVision Server and
database.
Validating evision.license file for valid key...
The license file is valid.
Information for License File evision.license:
[information specific to your license appears here]
3-6
2014 TIE Kinetix
Would you like to replace it with a a different license file?
Type Y to replace the existing license with a new one (enter

the complete path to the license file when prompted) or N to
keep the existing license.
7
Would you like to add e-mail notification settings?
Type Y and respond appropriately to each of the following

prompts, or N and skip to the next step.
Enter the default email address to send mail from : <email address of
sender>
Enter the name of the SMTP server you will be using :<mail server name>
Enter the SMTP Port Number (e.g., 25) :

<mail server port>
Enter the Port ID for CS Connect [<CS Connector port (default is 2010)>]:
Enter the new Port ID or press Enter to accept the default.

9
Enter the login name for Database :
Enter your login name.

Enter the Password for the database login :
Enter your login password.

Enter the Access Library Name [ORACLE] :
Enter the Access Library Name or press Enter to accept the

default.
2014 TIE Kinetix
3-7

Enter the Database Alias Name (if local leave blank). Here you must
supply the name of your database server, as it is known to your
database client. Typically, the server name is established when your
database is installed. See your system administrator if you are in doubt
:
Enter the Database Alias Name.

Enter the Database Name (if local leave blank). If you RDBMS system
supports the notion of multiple databases driven by a single server,
supply the name of the database you wish to use. If not, just hit enter. :
Enter the Database Name or press Enter.

14 You receive the message:
eVision configured successfully
In the event the configuration fails, the process asks you to

reconfigure the server. Otherwise, you will see the following
information displayed:
Checking settings with chkdb utility.
Password:
**********
15 If you chose to add email settings in Step , youll see the
following prompt. If you answered N in Step , skip to Step .
Would you like to test email notifications?
Type Y to test email notifications (described below). To skip

the test, type N and continue with to Step .
3-8
2014 TIE Kinetix
eVision Mail Notification Settings

---------------------------------Mail to:
<e-mail address sent from>
Mail from: <e-mail address sent from>
Inbox server:Outbox server:

<mail server name>
SMTP port:
<mail server port>
POP3 port:
0
Tracing enabled:
No
Tracefile name:
Notification enabled: Yes
Local Host: <host name>
Connected...
Connected...
Set To: and From: fields...
Sent message...
Shut down connection...
Success. Check mailbox.
Was the test message delivered successfully?
Type Y.
2014 TIE Kinetix
3-9
16 Next youre prompted to allow the SPLOAD process to load
your database tables.
Loading eVision databases with spload using install

Storing results of database load into file spload.log
Checking database connection
Password:
**********
17 You will see instructions displayed that are similar to the
following:
----------------------------------------------------------------SPLOAD is about to examine your database, and prepare it for eVision.

If you are installing eVision to an existing eVision database,
no data will be erased or re-initialized.
Please read the screen carefully, as it will tell you what actions
will be taken.
----------------------------------------------------------------Do you wish to continue?
[Y/N]
Type Y.
18 Next, you see this prompt:
Checking to see if eVision tables are already installed.
Existing eVision tables were found.
Would you like to upgrade the existing tables?
(Answering Y will not erase any of your existing eVision data.)
[Y/N]
Type Y.
19 You see this prompt:
Updating eVisionPlease wait
3-10
2014 TIE Kinetix
[a series of database messages appears]

installing Perl
nnnn blocks
Installation complete!
Password:
**********
20 Next, the script installs the necessary Comm packages.

Server ready to accept COMM install.
Installing Comm packages
[a series of comm installation messages appears]

Comm Packages installed.
21 You will be prompted, Y/N, for each selected Version
Standard you want to install. Be sure to select only those

Versions you actually need.
Installation complete.
Enter evenv to run eVision via command line or scripts
To run the evenv script from any directory,
you must add <current directory> to your path.
Otherwise, you must change directory to <current directory>
before executing this script.
22 Type evenv.
23 Now at the EVENV prompt, start the eVision Audit Agent, CS
Connector, and Workflow Maestro services by typing evStart.
To verify that these services are running, type

showservices.
To stop the eVision services, type evStop.
For information on other switches, type the service
name followed by -h.
24 Exit the EVENV script by typing exit.

25 Disconnect from the eVision UNIX server.
2014 TIE Kinetix
3-11

If you were shipped EDI Version Standards or other options for
the eVision Server in a separate file, load the software now by
entering the cpio command in the format appropriate to the
media. This step is unnecessary if the server Version Standards
were included in your eVision Server software.
If you have EDI version tables to install from other media,
install them by typing instTABLES. Under normal install
conditions instEDI runs this script. The instTABLES script can
also be used to install tables you originally chose not to install.
If you have communiction scripts to install, install them by
typing instCOMM. Under normal install conditions instEDI
runs this script. The instCOMM script can also be usd to install
communications scripts you originally chose not to install.
Based on need or purchase of additional functionality, you may
need to perform some or all of the following steps to install
these function(s) on the eVision Server.
If you have purchased the Status Feedback Loop option for
your SAP system, install the option by typing instAIMSFL. You
must restart your eVision services after this step.
Upgrading eVision Client

To perform this installation you must be logged onto each
machine with Administrator rights. Remember, the eVision
Server must be installed before you install the eVision Client(s).
Running setup.exe
Insert the eVision installation CD-ROM in the drive. The setup
program autoruns. If it does not, navigate in Windows Explorer
to the root of the CD-ROM drive and double-click setup.exe.
3-12
2014 TIE Kinetix
Welcome
When the setup program starts, it briefly displays some
information-only dialog boxes and then the InstallShield
Wizard prepares itself to run. After this initialization process is
complete, the Welcome screen displays.
Click Next.
License agreement
The License Agreement screen appears.
2014 TIE Kinetix
3-13
In order to install eVision Client, you must agree to the terms

of this license. Select the I accept the terms of the license
agreement radio button and click Next.
The license agreement to which this step refers is not to be
confused with the license file provided by TIE Kinetix. You must
agree to the terms of this license agreement in order to install
the software; the license file must be installed in order to run
the software.
The Customer Information screen appears.
By default, the name and company to which the computer is

registered appears in the User Name and Company Name fields.
Click Next to accept the defaults, or make any necessary
changes and then click Next.
3-14
2014 TIE Kinetix
Destination folder
On this screen you specify the base directory in which you want
eVision Client installed. The default isthe folder in which the
existing eVision Client is installed.
We strongly recommend installing the upgrade in the same

folder as the previous version. Click Next.
Select features
In this part of the installation, you are presented with a list of
possible components to install. The components that are
already installed on your system are checked by default, unless
you install your upgrade in a different folder from the previous
software (not recommended). Leave these components
checked; if you uncheck them, they will be removed from
your system!
The components are grouped into the following categories:
Server Components, Server Standards, Comm Scripts, Client
Components, spEDI_map Standards, Web Components and
UNIX Installations. Of these, only three apply to eVision Client:
Client Components, spEDI_map Standards and UNIX
Installations.
2014 TIE Kinetix
3-15
Client Components. At the minimum, you will install
Workbench Client. Unless you have custom mapping

capabilities of your own, you must also install spEDI_map.
Workflow Launch Client (wflaunch) is available to eVision

Net/Server users. Messenger Client bundles wflaunch with
mailboxing features and is available to eVision Enterprise users
only.
Heres a summary of the Client Components appropriate for the
two eVision configurations:
eVision
configuration
Workbench
Client
spEDImap
Net/Server
Enterprise
Messenger
Client
Workflow
Launch Client
spEDI_map Standards. This set of standards is for the use of
the eVision Client. You should install the same standards at
3-16
2014 TIE Kinetix
each client that you installed (or will install) on the eVision
Server.
It is not necessary to install existing standards again. If you do

not need to add any new standards to your system, you may
skip to the next section.
Installation of client standards is much less time-consuming
than server standards; we recommend you select them during
the initial installation.
UNIX Installations. If you use a UNIX machine to control an
eVision Server remotely, you may install these UNIX versions

(scripts) of eVision components.
The files that are installed are self-extracting files. After they
are copied to the eVision Client you must move them to the
UNIX machine that will remotely control the eVision Server.
2014 TIE Kinetix
3-17
When the files are run from there, they will install themselves
in the proper locations.

The setup program is ready to begin copying files to the
computer.
Click the Install button to begin the file copy process.

An installation progress indicator appears as files are copied
from the CD-ROM to the computers hard drive.

At the completion of the setup program, a screen similar to the
following appears.
3-18
2014 TIE Kinetix
By default, the option to view the RELEASE NOTES file is

checked. When you click the Finish button, the RELEASE NOTES
file appears. This file summarizes the current version of eVision
in the following categories: Enhancements and Changes/Fixes.
If you dont wish to view the RELEASE NOTES file, clear the
checkbox before clicking Finish.
You can view the RELEASE NOTESfile anytime by
clicking the Windows Start button, then selecting
Programs->TIE Kinetix->eVision Release Notes or
navigating to the folder in which you installed eVision and

opening release_notes.html.
Restart
A dialog box similar to the following appears. We strongly
recommend you select the default option to restart now.
Testing eVision
Test your system to make sure it is functioning properly. For
example, reprocess some sample data before re-enabling the
automation that you have established.
If your tests are unsuccessful and you want to return to a
previous version, please communicate with TIE KinetixKinetix
Technical Support or your authorized TIE reseller before
reverting to an older version.
To revert to an older version
2014 TIE Kinetix
Move the upgraded eVision directory to a new location on

your hard drive.
Restore your original directory and database instance from

your backup.
3-19
Reinstall your original system from the previous eVision

CD-ROM using the above procedure.
The new eVision installation created new registry settings, so

you must reestablish all user preferences, such as:
Toolbar preferences
ODBC connections
CS Connector locations
VAN communications setups
Conclusion
This completes the upgrade process. If you experience
problems with the upgrade and cannot resolve the issue with
these instructions, call TIE Kinetix Technical Support at 1-877787-7644 or send an email to support@tiekinetix.com.
3-20
2014 TIE Kinetix
Chapter 4 Maintenance Issues

Modifying, Repairing or Removing eVision Client
After eVision is installed, you may want to add client features
you didnt select during the original installation, such as
spEDI*map standards. Or, you may wish to reinstall eVision
Client if you encountered difficulties the first time. You might
even want to remove eVision Client entirely.
You can take any of these actions by running the setup program
setup.exe again (the program autoruns when you put the
installation CD-ROM in the drive; otherwise youll find it in the
CD-ROMs eVision installation directory).
Modify. Use this option if you want to install additional

features. For example, you may have chosen not to install
spEDI*map standards during the initial installation, but now
want to add them. Or perhaps youve just purchased new
optional components and wish to install them. Click Next and
follow the on-screen prompts.
2014 TIE Kinetix
4-1
Maintenance Issues
You may also selectively remove components using this option.

TIE Kinetix does not recommend selectively removing
components. The potential exists for inadvertently deleting a
shared file, which could cause the remaining components to
cease working reliably.
A cleaner and more reliable way to remove components is to
remove eVision entirely and then reinstall, selecting only those
components you need.
If you choose to selectively remove components, select Modify
and, at the Select Features screen, clear the checkboxes of the
components you want removed.
Repair. Use this option to reinstall eVision with all the same
components you selected during the original installation. Your

license file, database tables and application preferences remain
intact during a Repair.
Remove. Use this option to remove eVision. Remove uninstalls

the eVision application software, but your license file, database
tables and application preferences remain intact.
Customers upgrading to version 5.0 should note that selecting

the Remove option will NOT automatically revert your system to
the previous version of eVision in a fully operational state. To
revert to a previous version, you must Remove the new version,
restore the directory structure and database instance that you
previously backed up and then install the previous version of
eVision from the installation CD.
4-2
2014 TIE Kinetix
Maintenance Issues
Setting Up a Test Environment

A test environment simplifies testing your system and reduces
the risks of data loss. Purchasing a test license is an investment
in system stability.
Your test systems eVision Server must reside on a different
computer from that of your production system. Because you
are using it for test and development purposes, the test system
neednt be as robust as your production system. Ensure you
have128 MB of RAM and reserve at least 2 GB of available hard
drive space.
If you choose to have your test database instance on the same
database server as your production system, we suggest you set
it up with a different user name and password. This will reduce
the chance of confusion when setting up the ODBC and
configuring eVision Workbench.
To set up your test environment
2014 TIE Kinetix
Back up your production system, including the database and

the eVision directory. This is a precaution in case you
encounter problems while you are creating the test system.
Create a new test database instance. For example, you

might use evision_test as the name for your test database.
Your database administrator may be able to assist with this.
Copy the eVision directory from the production system to

the test system.
Set up a DSN for testing and point it to the evision_test with

the new login information.
Install eVision on the test system in the same directory to

which you just copied the production system. Be sure to use
the new DSN so that eVision points to the test database
created in Step 2. Verify that eVision is running successfully
before you continue.
Copy the eVision database to the test database. Your

database administrator may be able to assist with this.
If appropriate, install the eVision upgrade as outlined in

Chapter 3, Upgrading an Existing Installation.
4-3
Maintenance Issues
Activating eVision
You can activate eVision and the selected eVision components
using the following procedure.
To activate eVision and its components
1
After installing the selected components, you are prompted

to restart your computer, either now or at a later time, to
activate eVision and all its components.
Select the desired restart option and click Finish.

eVision and its components will not be available until after
you have restarted your computer.
Backing Up and Restoring eVision

You should always back up your eVision software before you
upgrade or modify your system. Backing up your eVision
software prevents data loss or corruption in the event of a
system failure.
A proper backup must include your database files from the eVision database
server and the directory structure from the eVision Server. Be sure to backup all
these eVision resources at the same time. If you do not, the backed-up
components will be out of sync and will not work properly when you restore
them.
To back up your eVision system
1
Back up your eVision directory structure to a server or

alternate drive.
Make a copy of the eVision database instance and save it to

a server or alternate drive. Your database administrator
may be able to assist you with this.
To restore your eVision system
4-4
Copy the eVision directory structure from the backup server

or drive to the drive where the restored eVision will reside.
Restore your database instance.
Install eVision Server and eVision Client on the restored

drive. Make sure to point eVision to the backup database.
Verify that eVision is running successfully before you
continue.
2014 TIE Kinetix
Maintenance Issues
If appropriate, install the eVision upgrade using the

procedure Chapter 3, Upgrading an Existing Installation.
Disaster Recovery
It is important to all recovery scenarios that you have a current
and valid backup of both your eVision Server files and your
database. The two must be in sync. If they are not in sync, any
attempted restoration of the backups will result in errors from
the database and/or errors from the eVision Server. You are
responsible for maintaining and preserving a timely backup of
your complete eVision system.
To recover from a disaster or to transfer eVision Server and
database to a different machine
2014 TIE Kinetix
If appropriate, stop the eVision services on the existing

machine to prevent any scheduled processing from
occurring during the transfer.
Create a database instance on the new machine.
Copy the eVision tables from the existing database to the

new machine, or restore them from the database backup.
Ensure database connectivity from the eVision Server and

eVision Client machines to the database server.
Copy the entire eVision directory to the new machine, or

restore the eVision Server backup to the new location. Make
sure all sub-directories are included in the copy/restore
process.
Install eVision. When you are prompted to install database

tables, say No. This will preserve your existing eVision data
in the database.
Install any other optional components that are currently on

your system (AIM, MPL, etc.).
Install your communications modules.
Test the new system.
4-5
Maintenance Issues
4-6
2014 TIE Kinetix
Appendix A DB Installation
Considerations
Your database administrator should install the database, with
database owner access, on the database server.
This appendix contains information youll find helpful in getting eVision set up
to work with your database, but it is not intended as a database installation
guide. Refer to the database vendors documentation for instructions on
installing and configuring your database.
Overview
Estimating disk space for the database server
While an approximation of about 70% of the eVision Server
storage requirements is a starting point, you should check with
your database administrator for more information on the
storage requirements of your relational database.
Network protocols for the database server

Consider what best meets your needs for data security when
you select a network protocol.
Database security
You should select the security type that your database
administrator recommends.
Create a database instance

Create a database instance in the previously installed
database. Name it evision_prod.
Check with your database administrator regarding the level of
security needed to install eVision and to run eVision on a
regular basis. To use eVision effectively, all users need Insert,
Select, and Delete permissions for the tables in the eVision
database. The tables are created while installing the eVision
2014 TIE Kinetix
A-1
server and tables, and the user who creates the database
during the installation must have database owner access to the
database. This level of security is to be determined at the
database level, not the application level.
In order to prevent the transaction log from growing to an unmanageably large
size, be sure to do the following when you configure your database:
select an appropriate recovery model,
select an appropriate backup routine and
select an appropriate backup schedule.
Test connectivity with the database server

Most relational databases come with utilities that allow a client
to test database connectivity.
The following procedure verifies that the database connectivity
is correctly set up and that the tables created for the eVision
database can be accessed and manipulated. These conditions
must be met for a successful eVision server installation.
Because the eVision Client machines must access information
from the eVision database tables, you must test connectivity
from each eVision Client machine. If you only have one client,
and it is installed on the same machine as the server, you need
only perform the procedure once.
To test connectivity with the database server
1
Launch the query tool on the client PC and connect to the

database instance you intend to use for the eVision
installation.
Although eVision users normally need only the default permissions to the
eVision database, you must have database owner or system administrator
permission to the database to install the eVision Server and to run the
WFMaestro service.
2
In a Query window enter the following SQL command:

Create table test (col1 numeric, col2 char(10))
A-2
Execute the command. It should return a message that the

command completed successfully.
2014 TIE Kinetix
If the success message does not appear, your database

administrator must correct the situation. You may also
arrange for assistance from TIE Consulting.
4
Open a new query. Enter and execute this command:

Select * from test
You should receive the following message:

col1
col2
(0 row(s) affected)
In a new query window, enter and execute this command:

drop table test
The query tool should return the message that the command
completed successfully. Your table is now clear of data.
6
Close all windows and quit the query tool.
You have verified that the relational database is accessible to

the machine(s) on which you will install the eVision software.
Creating a TNS Name and DSN

You must have a TNS (or Net Service Name) for eVision to use,
and it must be created before the setup program begins
copying files to the Oracle database. The eVision Server and
each eVision Client must be configured to use the TNS.
You must also have a DSN for each eVision Client after the TNS
has been created.
Sample procedures are outlined below, using Oracle Net
Configuration Assistant to create the TNS and ODBC Data
Source Administrator to create the DSN. Note that these are
sample procedures onlyother tools may be used.
2014 TIE Kinetix
A-3
To create a TNS (eVision Server and eVision Clients):

1
Open the Oracle Net Configuration Assistant. Youll find it by

clicking the Windows Start button, then selecting Programs> Oracle-->Configuration and Migration Tools--> Net
Configuration Assistant.
Select Local Net Service Name configuration and click Next.

2
The dialog box changes to this:
Select Add and click Next.
A-4
2014 TIE Kinetix
Enter the name for the service in the Service Name field.
Click Next.
4
Select TCP as the protocol to use.
2014 TIE Kinetix
A-5
Enter the Host name for your database computer and the
port number to use. The standard Oracle port (default) is
1521. Click Next.
6
At this point, you can test connectivity to your database

(recommended). Select Yes, perform a test and click Next.
A-6
2014 TIE Kinetix
If your connectivity test passes, the dialog box changes to

this:
Click Next.
8
Enter the Net Service Name you want to use. (The Net Service
Name defaults to the Service Name you assigned in Step 3.)
2014 TIE Kinetix
A-7
Unless you want to configure another Net Service Name,

select No and click Next.
10 The dialog box changes to this:
The process is complete. Click Next.
A-8
2014 TIE Kinetix
11 The dialog box changes to this:
Click Finish.
To create a DSN:
1
Open the ODBC Data Source Administrator on the eVision

Client. This dialog box appears during a first-time
installation of eVision, but it can also be opened through the
Windows Control Panel. By default, the User DSN tab is
displayed.
Select the System DNS tab and then click the Add button to
create a new Data Source Name.
2014 TIE Kinetix
A-9
The Create New Data Source dialog box appears.
Scroll down to and select the Oracle driver, then click Finish.
3
The Oracle ODBC Driver Configuration dialog box appears.
First, enter the Data Source Name for the DSN, a Description
for it and the TNS Service Name.
The text that appears in the dialog box fields on this and the following pages are
examples only. You should enter names and other information that are
appropriate to your own system.
4
Complete the information on the five tabs of the dialog box.
Click the OK button to complete the DSN creation, or the Test

Connection button to test connectivity.
Your Oracle DSN has been created.

Repeat the process for every eVision Client.
A-10
2014 TIE Kinetix
Appendix B Requesting a License

There are two ways to request an eVision license: login at the
TIE Global Customer Portal and submit your request
(recommended) or call TIE Kinetix Technical Support. These
methods apply whether you are requesting a permanent
license or an extended temporary license.
If you are requesting a permanent license, you must include your eVision Server
host name with your request. Heres how to find the machine name: connect to
the UNIX server using Telnet or a similar utility. Type evenv and press the
Enter key. Then at the EVENV prompt, type CheckLicense -request. The
system will return a message saying the file licenseRequest.txt has been created.
This file contains the information required to an updated license file.
2014 TIE Kinetix
B-1
My-TIE
Submitting a license request
Go to https://my-tie.net and login. The Customer Portal screen
appears. Click the Support link.
The Support page appears. Click the second Support link.
B-2
2014 TIE Kinetix
The Support Incident page appears.
This page displays the following fields:
2014 TIE Kinetix
Relation - this field is automatically completed by the

system.
Related Account - Ignore this field.
Contact Person (1) - When this field is blank, a red

exclamation point appears. Click on the icon to the left of
the exclamation point and then choose your name from
the drop-down list that appears. If your name does not
appear, go to the My Account Data link (2) from the top
menu and edit the contact person information and add
yourself.
Description (1) - Give a brief description of your request.

Specify whether you are requesting a permanent license
or a temporary one.
Classification (1) - Select License from the drop-down

list.
Product - Ignore this field.
Serial Number - Ignore this field.
Document - Ignore this field.
Related Request - Ignore this field.
Question - If you have any additional information to

include with your request, click the T-Timestamp (3)
button (this automatically enters the system date and
time in the Question field) and type in any additional
B-3
information (4). If youre requesting a permanent

license, be sure to include the licenseRequest.txt file
information you noted earlier (page B-1).
When youve completed the necessary fields, submit your
request by clicking the S-Submit button (5) near the top of the
screen.
You may return to My-TIE at any time to check the status of
your request, as described in the next section.
Checking the status of a license request

When you return to My-TIE and login, click the Requests link.
The Search:Requests screen appears. Click the S-Search

button.
B-4
2014 TIE Kinetix
The Search:Requests results screen appears. The status of

your request is displayed in the Status column on the far right
of the table.
For more detailed information, click the Support Incident link in
the appropriate row (the description you entered for your
request will help you identify it if you have other requests
pending).
The Support Incident page relevant to your license request

appears (below).
Note the Realize box in the center of the screen. The green
border around this box indicates that your request is being
processed.
Later, when your license file is ready for download, the Status
column on the Search:Requests results screen will show a
2014 TIE Kinetix
B-5
status of Processed and the Support Incident page will look

similar to this:
The red border around the Process box indicates that the
support ticket is closed.
Downloading the license file

Click the Documents link.
B-6
2014 TIE Kinetix
The Search:Documents screen appears. Click the S-Search

button.
The Search:Documents results screen appears (below).

Documents having a Security Level of 1 are available to anyone
using the Customer Portal, while those having a Security Level
of 3 are customer-specific and visible only to the intended
recipient.
2014 TIE Kinetix
B-7
Click on the licence in the Subject column. The license download

screen appears:
Click the 9-Download button. The following download

confirmation prompt appears:
Click Save and select a destination folder for the license file.
After the download is complete, move the license file to the
eVision home directory on the eVision Server.
Finally, restart the eVision services (including Tomcat, if you are
using eVision Web Client).
TIE Kinetix Technical Support

If your company does not have a My-TIE customer account, call
TIE Kinetix Technical Support to request your license at 1-651999-8601 or toll-free at 1-877-787-7644.
B-8
2014 TIE Kinetix

EVision 7.0 Installation Guide For UNIX

Uploaded by

Copyright:

Available Formats

EVision 7.0 Installation Guide For UNIX

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EVision 7.0 Installation Guide For UNIX

Uploaded by

Copyright:

Available Formats

TIE

Installation of eVision for

eVision is a trademark and spEDI*map is a registered trademark of

Use, duplication, or disclosure by the U.S. Government is subject to

THIS WORK CONTAINS VALUABLE CONFIDENTIAL AND PROPRIETARY

Installation of eVision for UNIX Server and Windows Client

2014 TIE Kinetix

Scope of This Document

The Next Step

Parts of the Installation Process

Installing the Database

Before You Begin

Installing eVision Server

Installing eVision Client

Installation of eVision for UNIX Server and Windows Client

Installation completion and exit

Configuring the eVision Workbench

Upgrading an Existing Installation

Before You Begin

Upgrading eVision Server

Upgrading eVision Client

Modifying, Repairing or Removing eVision Client

Setting Up a Test Environment

Backing Up and Restoring eVision

Installation of eVision for UNIX Server and Windows Client

2014 TIE Kinetix

2014 TIE Kinetix

Creating a TNS Name and DSN

TIE Kinetix Technical Support

Installation of eVision for UNIX Server and Windows Client

Installation of eVision for UNIX Server and Windows Client

2014 TIE Kinetix

Scope of This Document

2014 TIE Kinetix

Installation of eVision for UNIX Server and Windows Client

and which fulfills requests from client machines. Not to be

workflows. It consists of two user interface modules, eVision

eVision Net/Server. An eVision configuration designed to

support eVision over a network, using one or more eVision

support multiple eVision Clients. eVision Enterprise has all the

eVision Server. The eVision component that manages

communications between the client(s) and the database. There

eVision Workbench. The user interface component of the

eVision Client software, from which you create and manage

eVision Workflow Monitor. The eVision Client GUI module that

spEDI*map. The mapping component of the eVision Client

software. spEDI*map can only be run under Windows.

workflow. A defined sequence of computer commands that,

when executed, performs meaningful work.

Installation of eVision for UNIX Server and Windows Client

2014 TIE Kinetix

wflaunch. An eVision component, available only on eVision

Net/Server and eVision Enterprise systems, that allows

at least one eVision Client

eVision for UNIX supports the Oracle database, version 10g or

System configuration rules

2014 TIE Kinetix

Installation of eVision for UNIX Server and Windows Client

An eVision configuration may have only one copy of