Eniserver Quickstart E

User Documentation:
ENI Server
ENI Server Quickstart - Overview and First Steps
Document Version 3.0

tech_doc_e.doc / V1.1
 3S - Smart Software Solutions GmbH Page 1 of 14

eniserver_quickstart_E.doc
CONTENT
1 ENI – SHORT OVERVIEW 3
2 QUICKSTART 4
2.1 Prearrangements 4
2.2 Some remarks before installation 4
2.3 Installation 4
2.4 Configuration 5
2.5 Start 7
2.6 Preparing a CoDeSys Project for Source Control 7
3 TIPS FOR THE CONFIGURATION WITH VISUAL SOURCESAFE 6.0 8
4 TIPS FOR THE CONFIGURATION WITH THE SUBVERSION DATA BASE 10
CHANGE HISTORY 14
This document provides a short overview on the ENI functionality as well as a description of
how to do the first steps concerning installing and configuring the ENI Server in order to get a
CoDeSys project under source control in an ENI data base. The ENI Server will be installed
with CoDeSys which also provides the programs ENI Admin and ENI Control, which are needed
for managing the Server, and the program ENI Explorer.
Continuative documents:
- ENI Client Development Kit – Programmers Guide
- ENI Client Development Kit – XML-Format for ENI Objects
- Online Help for ENI Server, ENI Admin, ENI Control, ENI Explorer
- CoDeSys Manual resp. Online Help for V2.3

1 ENI – Short overview
The ENI is the ENgineering Interface of the CoDeSys programming system. It consists of a
server and a client part.
The ENI Server runs as a separate service. Typical clients are one or several CoDeSys
programming systems and other tools, which want to access the same sources in a shared
data base system (DB). Concerning the work with CoDeSys this makes possible to put
CoDeSys projects under version control, it allows multiuser operation and also access to the
project objects by external applications.
Supported Data Base Systems:

The server concept allows to put a common data base on a remote computer. By default the
ENI Server supports a local file system as well as the data base systems 'Visual SourceSafe
6.0', 'Visual SourceSafe 2005', and ‘Subversion’ as from V1.2.1.
It is however possible to customize the ENI Server to other data base systems. For a detailed
description see the ENI Driver Development Kit — Programmer's Guide.
Communication with the ENI Server:

TCP/IP is used as client-server protocol. For detailed information see the following documents:
- ENI Client Development Kit – Programmers Guide
- ENI Driver Development Kit XML — Format for ENI Objects
ENI in CoDeSys:
It is an option to use the ENI with the CoDeSys programming system. Further information on
this project option see in the User Manual for CoDeSys V2.3 and higher.
Installation and Start:

The installation of the ENI Server is done by the setup of CoDeSys. See chapter 2 in this
concern. After successful installation and later at each restart of the system the availability of
the ENI Server will be indicated by a Icon in the system tray and the ENI Server service will
be started automatically. As long as the server is running the Icon will be shining.
Administration:
The administration of the ENI Server is done with the aid of the programs ENI Control and ENI
Admin: ENI Control is used to define the basic server settings, which won't be changeable as
long as the server is running, e.g. data base connection, communication settings etc. Besides
that the ENI Server can be started and stopped explicitly with this tool. ENI Admin is used to
configure users, administrator password, groups and access rights as well doing the license
management. These operations are also possible while the server is running.
The ENI programs can be started from the Start menu of the computer as well as via the menu
which is attached to the ENI Icon. This icon will appear in the system tray of your computer as
soon as the ENI Server Suite has been installed. Click on the icon with the right mouse-button
to open the menu. There you also can start the Event Log tool, which as well is available in ENI
Control.

2 QuickStart
2.1 Prearrangements
1. Install the data base which should be served by the ENI service corresponding to the
provided installation instructions. Ideally install the data base on the same computer as the
ENI Server.
2. Start the data base system if applicable.
3. Data base system 'Local File System': Create a new empty folder, e.g. "D:\project1\..."
Regard for Visual Source Safe: The VSS Client must be installed on the same PC as the ENI
Server. (see chapter 3).
2.2 Some remarks before installation
• Operating mode and Licenses:
- 'Local' Mode: The server can only be accessed by localhost and only the driver for a
local file system will be available. This version does not need a license. Reasonably use
this mode, if the ENI Server exclusively is used to enable "tool cooperation".
- 'Server' Mode: A license is required. The server can be accessed by any computer in the
network. Depending on the license type a different selection of database drivers will be
provided. In addition to tool cooperation this mode will allow spread development
activities. A license can get requested with the aid of the 3S License Manager, which will
be automatically provided with the ENI Server.
• The ENI Client - ENI Server communication requires TCP/IP.
• Administrator rights on the computer are required.
• During installation you will be asked for a ENI Administrator password. At a primary
installation this question can be confirmed with OK without having inserted a password.
• The installation of the CoDeSys optionally includes the installation of the ENI Server as well
as that of the programs ENI Admin and ENI Control, which are needed for administration
and controlling the ENI. (Additionally the ENI Explorer program will be installed; for this
currently an online help eniexplorer.hlp is available in the ENI installation directory, which
must be called explicitly).
2.3 Installation
Insert the installation CD for CoDeSys and during setup choose (also) component ENI Server.
Per default the driver for a local file system will be installed which requires no license; also the
programs ENI Control, ENI Admin und ENI Explorer. After a restart of the computer the ENI
Server will be started automatically and the ENI icon in the system will shine.

2.4 Configuration
1. After a successful installation start program ENI Control for configuring the data base
connection. ENI Control is available in the programs menu under 'CoDeSys ENI Server'
resp. via the menu which opens when you perform a mouse-click on the ENI icon in the
system tray.
First the dialog 'Enter Administrator Password' will appear. If you are doing a primary
installation, close this dialog without any input by pressing the button OK. If ENI Control had
been installed previously, then you have to insert the valid administrator password. (The
administrator password is to be defined in the program ENI Admin.)
Hereupon the dialog 'Database' will be opened, where you can define the driver for the
desired data base system and do the corresponding configuration settings:
Select Database In the selection list next to 'Select Database Driver' you will find all
Driver available drivers. If the desired driver is not part of the list, then press
the button next to the list and search for the appropriate driver file on
your computer. The list of available drivers depends on the ENI license
which is installed on the computer. If a license-free version of the ENI
Server is used, just the driver for a local file system will be usable.
Currently the following drivers are available depending on the license:
- "File System Driver" (ENIDrvFileSystem.edd, local file system)
- "SourceSafe 6.0 and 2005" (ENIDrvSourceSafe 6.edd)*
- "Subversion" (ENIDrvSVN.edd)
* This driver supports SourceSafe 6.0 as well as 2005.
See in the following tables the configuration options for the particular database systems:
File System Driver:
Root Folder Local folder for the deposit of the project object files, e.g. D:\project1
ENI User Name User name used in the ENI Server for internal tasks.
Visual SourceSafe 6.0 and 2005:
Location of Define the path of the ini-File of the SourceSafe. Per default it will be
'srcsafe.ini' found in the installation directory of the SourceSafe. You can make use
of a browse dialog which opens as soon as you perform a double-click
on the entry field.
Even if the VSS data base is located on a remote computer, define here the
path of the srcsafe.ini file of the locally installed VSS (client). In this case
however this ini-file must contain an appropriate reference entry pointing on the
srcsafe.ini of the data base computer. See chapter 3!
Root project Insert here the path of the project which you have created in the data
base during the preparations (item 3 of 2.1), e.g. "$/project1".
Below this directory there can be created one or several subdirectories – by the
appropriate definition in the CoDeSys project options (see below 10.) – where
the desired objects will be hold. These subdirectories also could be created
previously, directly in the data base. In this case they will be already available
for selection when you configure the ENI in CoDeSys.
Temporary folder Folder, where the data base stores temporary files.
ENI user A special user account used by the ENI Server for internal tasks. This
account must exist also in the user management of the data base.
ENI password The password for the above set user account.
Structured Select ‘Yes’ or ‘No’. In case of ‘Yes’ the objects will be managed in the
saving of folders data base in a folder structure which corresponds to that used in the
Object Organizer in CoDeSys.
Attention:
1. This setting cannot be reversed and should not be changed after the first
use of the database, because no correct access on the previous database will
be possible!
2. For the use with CoDeSys V3.x this setting should be deactivated (‘No’)!
Note: The specification of the path of ss.exe, which is needed for SourceSafe 6.0, will be
configured automatically, because in any case this file must be managed in the \win32-
subfolder of that directory which contains the srcsafe.ini file. If ss.exe is not found there, the
path of srcsafe.ini will not be accepted.
Subversion: (currently only possible with SVN and File Protocol!)
Repository Path Define here the path of the Subversion data base which should be
connected via ENI.
Temporary folder Folder where the data base stores temporary files.
ENI user A special user account used by the ENI Server for internal tasks. This
account must exist also in the user management of the data base.
ENI password The password for the above set user account.
Structured saving Options ‚Yes’ or ‚No’. If ‚Yes’, then the objects will be organized in the
of folders data base in the same structure as in the CoDeSys Object Organizer.
Attention:
This setting cannot be reversed and should not be modified anymore after the
data base has been used the first time, because in this case correct access on
old data bases not anymore would not be possible!
Close the dialog with OK.
2. Now you can start ENI Admin in order to o set up a user configuration: This is not obligatory.
To get a working connection to the data base, it is sufficient to be registered as a valid user in
the data base. However an additional (switched in) user definition in the ENI Server might be
reasonable, e.g. if detailed access rights should be defined.
ENI Admin also can be started via the programs menu under 'CoDeSys ENI Server' or via the
menu which will open perform a click with the right mouse-button on the ENI icon in the
system tray. In case of a primary installation the program can be opened without entering a
password (The definition of the password for ENI Admin and ENI Control is to be done in the
tab 'Admin Password', see in this concern the ENI Admin online help.
Please regard the following for the user definition in ENI:

• For each user account you define and want to use in ENI Admin, also a corresponding
account must be set up in the data base (identical name and password). E.g. in Visual
SourceSafe you will use the user management Visual SourceSafe Admin for this
purposes.
• Each user account must be assigned to a group. In order to do this select the desired
group, press button 'Edit' and add the desired user accounts.
3. Now the ENI Server should automatically be started and ready for use. In this case ENI
Control will show "Running" as 'Current Status' and the ENI icon in the system tray will shine.

2.5 Start
After successful installation and after each restart of the computer the ENI Server Service will
be started automatically. The ENI icon in the system tray will start shining.
ENI Control resp. ENI Admin must be started explicitly, but cannot run both at a time. After
installation of the you will find these programs in the ENI Server Suite Start menu, but are also
available in the menu which will open if you a click on the ENI icon with the right mouse-button.
2.6 Preparing a CoDeSys Project for Source Control

See in the following a simple example of connecting a CoDeSys Project via the ENI Server to a
data base system.
1. Start the CoDeSys programming system and open any program.
2. - Select menu items 'Project' 'Options' 'Project source control'.
– Activate option 'Use source control (ENI)'.
– Press button 'configure ENI...'.
– Configure the ENI connection in category 'Project objects' as follows:
TCP/IP-Address Address of the computer on which the ENI Server is installed;

e.g. "localhost"
Port Number of the port on which the ENI Server "listens". Default: 80.
Projektname Name resp. path of the project as it should be created in the data
base below the root path (which is defined in ENI Control in category
'Database'). E.g. if you enter "project1\projektobjekte", and if you
have defined "$/" as Root in ENI Control, then you will get a new
project folder "$/project1/projektobjekte" in Visual SourceSafe.
Do not change the other settings in the dialog.

3. Click on 'Next' and do the same settings as described for the 'Project objects' also in the
categories 'Shared objects' and 'Compile files'.
4. Close the option dialogs with OK. You will be asked to log in to the ENI Server: Insert name
and password of a valid user account.
5. Now the project is connected to the data base but the POUs of the project are still just
"local". To put them to the data base, choose menu items 'Project' 'Data Base Link'
'Multiple Define' and in the 'Object properties' dialog, which will be opened, choose data
base option 'Project'. Now a selection dialog 'ENI-Selection' will offer you the available
project POUs. Select all objects you want to put to the data base and confirm with OK.
6. Now the chosen objects are connected with the data base. The connection parameters are
those which are defined in the dialog 'Project' 'Options' Project source control' 'Project
Objects'. Hence for these POUs all typical data base functions will be available in the
context menu.

3 Tips for the Configuration with Visual SourceSafe 6.0
Recommendation: ENI Server and VSS 6.0 with VSS-database are on the same network PC, in
order to avoid limitations and problems which might occur due to the internal interfaces Microsoft VSS.
If however the VSS-database must be installed on a remote PC, regard the following:
1. On the local PC indeed VSS must be installed, but in order to avoid errors of VSS there
should be no VSS data bases at all, even if they are not ENI relevant! Thus the local
SourceSafe directory only contains subdirectories (e.g. win32) needed for program execution
and program files, but no directories "data", "temp" or "users": For example:
On the other PC VSS is installed together with the ENI relevant VSS-database, thus the
SourceSafe-directory on this PC looks like this:

2. The local srcsafe.ini-file is that one, which is to be specified in the ENI Server configuration
(ENI Control). It only contains a reference (entry "include") to the srcsafe.ini-file which is on
the remote PC (where the database is) and which in turn references the database folders..
Example for local srcsafe.ini:
; Client srcsafe.ini
;
; Your Microsoft Visual SourceSafe Client installation uses this file to
; access a remote SourceSafe database on a network server. This file
; contains only one uncommented line: a #include statement containing the
; path to your network server's initialization file, SRCSAFE.INI. If this
; file does not contain such a line, add a #include statement containing
; the path to your network server's initialization file. For example:
; #include \\SRCSERVER\\SRCSHARE\SS4\SRCSAFE.INI
;
#include \\Server2\VSS_database\SRCSAFE.INI
Example f0r srcsafe.ini on database system: It is recommended to use absolute, not relative paths for the
references to the folders:
; srcsafe.ini
;
; Three of these variables -- Data_Path, Users_Path, and Users_Txt – must
; be in srcsafe.ini. Any other variable here can be overridden in ss.ini.
; Similarly, any ss.ini variable can be placed in srcsafe.ini to set a
; system "default," which individual users can still override in ss.ini.
;
; The two important paths used by SourceSafe.
Data_Path = \\Server2\VSS_database\data
Temp_Path = \\Server2\VSS_database\temp
;
; This tells admin where to put personal directories for new users.
Users_Path = \\Server2\VSS_database\users
;
; From this, find users.txt; from that, in turn, find ss.ini for a user.
Users_Txt = \\Server2\VSS_database\users.txt
;
; The following line contains common file groupings.
File_Types = VB(*.asp;*.bas;*.cls;*.ct?;*.dca;*.dep;*.dob;*.dox;*.ds?;*.fr?;
*.log;*.oca;*.pag;*.pgx;*.res;*.swt;*.vb?),VC(*.bmp;*.c;*.cpp;*.cur;*.cxx;
*.def;*.ds?;*.h;*.hpj;*.hpp;*.hxx;*.ico;*.inl;*.mak;*.rc;*.rc2;*.rgs),
VID(*.asa;*.asp;*.css;*.dbp;*.dtq;*.htm*;*.pkp;*.sln;*.sql;*.txt;*.vip;
*.wdm),VJ(*.java;*.vjp;*.pkp;*.sln;*.txt),VFP(*.cdx;*.db?;*.dc?;*.fpt;*.fr?;
*.idx;*.lb?;*.mn?;*.mpr;*.pj?;*.prg;*.qpr;*.sc?;*.vc?)
Img_File = HTMLFILE.GIF
Img_Folder = FOLDER.GIF
If you do not want to start the ENI Server via the Local System Account, perhaps because in this case
the access rights would not be as desired, you can configure a connection via another user account in
dialog 'Advanced Control' in ENI Control ('Service'). If the ENI Server is installed on a remote PC, on
the local and the remote PC an identical user account must be configured, the access data of which
have to be entered in the 'Advanced Control' dialog. This account then can be used to start the ENI
Server on the remote system.

4 Tips for the Configuration with the Subversion data base
General
The ENI Subversion driver can access the Subversion Repository (data base) in different ways. These
possibilities and the necessary configuration will be described in the following. The version information
matches May 2007.
Used software and its versions:
- CoDeSys ENI Server and Subversion driver from 3S-Software (http://www.3s-software.com):
o CoDeSys ENI Server V1.1.7.0
o Matching Subversion driver (ENIDrvSVN.edd)
- Subversion version management and TortoiseSVN Subversion Client from tigris.org
(http://subversion.tigris.org):
o for svn + http protocol:
Subversion 1.4.3 (svn-1.4.3-setup.exe)
TortoiseSVN 1.4.3 (TortoiseSVN-1.4.3.8645-win32-svn-1.4.3.msi)
o for file protocol:
Subversion 1.3.2 (svn-1.3.2-setup.exe)
TortoiseSVN 1.3.5 (TortoiseSVN-1.3.5.6804-svn-1.3.2.msi)
- Webserver from Apache Software Foundation (http://www.apache.org):
o Apache Webserver 2.0.59 (apache_2.0.59-win32-x86-no_ssl.msi)
Attention: For Subversion versions >1.3.2 the library libdb43.dll must be located in the ENI directory
(with ENI.exe) or in the Windows system32 directory in order to get the driver available in the data
base driver configuration. If this is not the case, the following error message will appear:
Other Subversion relevant information:

- the data base format BDB does not work on a network folder, but only locally (FSFS as an
alternative)
- it might be necessary to convert existing data bases into a new format before accessing
Big parts within this „Tips“ chapter base on the very useful Subversion and TortoiseSVN
documentation. So in case of getting lost, have a look there.
Setting up a data base

A Subversion repository either can be created with the help of the tool svnadmin.exe or directly via the
TortoiseSVN Client. For a detailed description please see the corresponding documentation.

Data base driver configuration in ENI Control

The necessary entries for Repository Path, ENI user and ENI password are described in the
following paragraphs referring to the particular protocols. The other parameters are described in
Chap. 2.4.
Using the svn protocol

In this case the Subversion server svnserve.exe is used. The call looks like follows::
svnserve.exe -d -r "Pfad\zur\Datenbank"
for example:
svnserve.exe -d -r "D:\SVN\ENI"
Before start some additional settings concering data base access must be done in the data base
itself.:
1. Create user account in file conf\svnserve.conf, for example:
### This file controls the configuration of the svnserve daemon, if you
### use it to allow access to this repository. (If you only allow
### access through http: and/or file: URLs, then this file is
### irrelevant.)
### Visit http://subversion.tigris.org/ for more information.
[general]
### These options control access to the repository for unauthenticated
### and authenticated users. Valid values are "write", "read",
### and "none". The sample settings below are the defaults.
anon-access = read
auth-access = write
### The password-db option controls the location of the password
### database file. Unless you specify a path starting with a /,
### the file's location is relative to the conf directory.
### Uncomment the line below to use the default password file.
password-db = passwd
### The authz-db option controls the location of the authorization
### rules for path-based access control. Unless you specify a path
### starting with a /, the file's location is relative to the conf
### directory. If you don't specify an authz-db, no path-based access
### control is done.
### Uncomment the line below to use the default authorization file.
# authz-db = authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, they should
### have the same password database, and vice versa. The default realm
### is repository's uuid.
# realm = My First Repository
2. Define access in file conf\passwd, for example:

### This file is an example password file for svnserve.
### Its format is similar to that of svnserve.conf. As shown in the
### example below it contains one section labelled [users].
### The name and password for each user follow, one account per line.
[users]
# harry = harryssecret
# sally = sallyssecret
eni = eni
frank = frank
Parameters for data base configuration in ENI Control:

Repository Path:
svn://<Hostname resp. IP-address>
for example:
svn://localhost
ENI user and ENI password must correspond with a user account defined in file
conf\svnserve.conf. At best create a separate user account for the server and use it here.
Using the file protocol

The access is done directly by using Subversion libraries. Due to the fact that the ENI Subversion
driver uses definite library versions, currently only Subversion up to Version 1.3.2 is supported.
Parameter for the data base configuration in ENI Control:
Repository Path:
file://</Pfad/zur/Datenbank>
for example:
file:///D:/SVN/ENI
Make sure to use slashes (/) instead of backslashes (\) !
ENI user and ENI password can be defined as desired, because there is no user management in the
data base. However at best define separate user access data for the server (e.g. eni / eni).

Using the http protocol

In this case the access is done via the Apache Webserver. Needed Subversion modules up to now
are only available for version 2.0. So currently version 2.2 cannot be used! Also versions older than
2.0 are not supported.
Before starting the Webserver the following steps must be executed:
1. Copy the Subversion modules (mod_dav_svn.so und mod_authz_svn.so) and the library for
accessing (libdb4x.dll) to the modules directory (…\modules) of the Webserver.
2. Create password file and set up user(s) via htpasswd.exe (in …\bin):
htpasswd -c <passwordfile> <username>
Further users can be defined by:
htpasswd <passwordfile> <username>
3. Edit Webserver configuration file (…\conf\httpd.conf):
- Remove the # character from the following lines:
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_module modules/mod_dav.so
- Insert the following lines at the end of section LoadModule:
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so
- Insert the following lines at the end of the file, enter the path of the data base behind
SVNParentPath, and the path of the password file behind AuthUserFile:
<Location /svn>
DAV svn
SVNListParentPath on
SVNParentPath D:\SVN
AuthType Basic
AuthName "Subversion repositories"
AuthUserFile bin/passwd
#AuthzSVNAccessFile svnaccessfile
Require valid-user
</Location>
Further possibilities concerning the Apache Webserver (e.g. detailed permission assignment)
are not addressed here in the document.
Parameters for data base configuration in ENI Control:

Repository Path:
http://<Hostname resp. IP-address>/<Location (see httpd.conf)>/<Database name>
for example:
http://localhost/svn/ENI
ENI user and ENI password ENI user and ENI password must correspond with a user account
defined in the password file. At best create a separate user account for the server and use it here.

Change History
Version Description Editor Date

1.0 Issued, Release MN, KeK 13.12.2002
1.1 Database user accounts automatically available for login MN, KeK 11.03.2003
via ENI (with CoDeSys 2.3.2.0)
1.2 additionally PVCS-driver; additional settings for MKS in MN, KeK 25.03.2004
ENI Control; Driver for SS5 not supported by default; ENI
Control not opened any longer automatically already during
installation -> Configuration must be done after installation
(with CoDeSys 2.3.3.0)
1.3 additional chapter 3 'Tips on VSS configuration' MN, KeK 27.10.2004
1.4 Structured saving of folders for PVCS and SS 6.0 drivers+ MN, KeK 18.04.2005
various changes in 2.4, 1. (with CoDeSys 2.3.4.2)
1.5 New: ClearCase driver (with CoDeSys V2.3.5.0), Chap.1, MN, MP 26.07.2005
2.4
1.6 New: Subversion Treiber, Chap. 1, 2.4 MN, TP 24.07.2006
1.6 Formal Review, Release MN 11.09.2006
2.0 Driver for SS 6.0 + 2005 (#7116), Description reduced to MN 24.04.2007
standard drivers (Chap. 1, Chap. 2.4)
2.0 Review OK MP 26.4.2007
2.0 new: Chap.4, Tips for SVN FHa 10.05.2007
2.0 Formal Review, Release MN 10.05.2007
2.1 Correction: Chap.4, Using the svn protocol (samples mixed MN 12.11.2007
up)
3.0 Release MN 07.12.2007


Eniserver Quickstart E

Uploaded by

Document Information

Original Description:

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

Eniserver Quickstart E

Uploaded by

Copyright:

Available Formats

User Documentation:

Document Version 3.0

 3S - Smart Software Solutions GmbH Page 1 of 14

1 ENI – SHORT OVERVIEW 3

3 TIPS FOR THE CONFIGURATION WITH VISUAL SOURCESAFE 6.0 8

4 TIPS FOR THE CONFIGURATION WITH THE SUBVERSION DATA BASE 10

 3S - Smart Software Solutions GmbH Page 2 of 14

1 ENI – Short overview

Supported Data Base Systems:

Communication with the ENI Server:

Installation and Start:

 3S - Smart Software Solutions GmbH Page 3 of 14

2.2 Some remarks before installation

• Operating mode and Licenses:

• The ENI Client - ENI Server communication requires TCP/IP.

• Administrator rights on the computer are required.

 3S - Smart Software Solutions GmbH Page 4 of 14

File System Driver:

Visual SourceSafe 6.0 and 2005:

Subversion: (currently only possible with SVN and File Protocol!)

Close the dialog with OK.

Please regard the following for the user definition in ENI:

 3S - Smart Software Solutions GmbH Page 6 of 14

2.6 Preparing a CoDeSys Project for Source Control

TCP/IP-Address Address of the computer on which the ENI Server is installed;

Do not change the other settings in the dialog.

 3S - Smart Software Solutions GmbH Page 7 of 14

3 Tips for the Configuration with Visual SourceSafe 6.0

 3S - Smart Software Solutions GmbH Page 8 of 14

Example for local srcsafe.ini:

 3S - Smart Software Solutions GmbH Page 9 of 14

4 Tips for the Configuration with the Subversion data base

Other Subversion relevant information:

Setting up a data base

 3S - Smart Software Solutions GmbH Page 10 of 14

Data base driver configuration in ENI Control

Using the svn protocol

### Visit http://subversion.tigris.org/ for more information.

2. Define access in file conf\passwd, for example:

Parameters for data base configuration in ENI Control:

Using the file protocol

 3S - Smart Software Solutions GmbH Page 12 of 14

Using the http protocol

Parameters for data base configuration in ENI Control:

 3S - Smart Software Solutions GmbH Page 13 of 14

Version Description Editor Date

 3S - Smart Software Solutions GmbH Page 14 of 14

You might also like