Beruflich Dokumente
Kultur Dokumente
BREAKWAT 3
Table of Contents
Table of Contents 4
1 BREAKWAT 1
2 Installation 3
2.1 Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1.1 Install Breakwat . . . . . . . . . . . . . . . . . . . . . . . 4
2.1.2 Install License . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Release-Notes 7
3.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.1 New features VERSION 3.01 VERSUS 3.00.0024 . . . . . 7
3.1.2 New features RELEASE 3.02 RELEASE 3.01.0001 . . . . 8
3.1.3 New features RELEASE 3.3.0.21 RELEASE 3.02.0000 . . 8
3.2 Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2.1 Modifications RELEASE 3.00.0023 RELEASE 3.00.0022 . 9
3.2.2 Modifications RELEASE 3.00.0024 VERSUS 3.00.0023 . . 11
3.2.3 Modifications RELEASE 3.01.0000 VERSUS 3.00.0024 . . 12
3.2.4 Modifications RELEASE 3.01.0001 VERSUS 3.01.0000 . . 14
3.2.5 Modifications RELEASE 3.02.0000 VERSUS 3.01.0001 . . 15
3.2.6 Modifications RELEASE 3.3.0.21 VERSUS 3.02.0000 (=ver-
sion 3.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3 Unsolved problems . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4 BREAKWAT FAQ 23
4.1 Known problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2 Report errors/suggestions . . . . . . . . . . . . . . . . . . . . . . 24
4.3 Getting complete version number . . . . . . . . . . . . . . . . . . 24
5 FLeXLM 25
6 Installation DS FLEX 27
6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.1 Local, Client . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.1.2 Server and Client . . . . . . . . . . . . . . . . . . . . . . . 30
6.1.3 Server Only . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2 Installation windows . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.3 Local, Client Installation . . . . . . . . . . . . . . . . . . . . . . . 36
3
BREAKWAT 3 README v2.0 July 16, 2010
7 DS FLEX FAQ 47
7.1 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . 47
7.1.1 FlexLM License Manager -”Server/Client installation does
not work while installation on both sides looks fine”: . . . . 47
7.1.2 FlexLM License Manager -” When using a license based
on a MAC-Address, it is possible that the License Manager
does not recognise it”: . . . . . . . . . . . . . . . . . . . . 47
7.1.3 FlexLM License Manager -”No such feature exists”: . . . . 47
7.1.4 FlexLM License Manager -”Bad encryption handshake with
vendor deamon”: . . . . . . . . . . . . . . . . . . . . . . . 48
7.1.5 FlexLM License Manager-“System clock has been set back” 48
7.1.6 FlexLM License Manager -“Can not find license file ”error: 48
7.1.7 FlexLM License Manager -“Terminal server Remote Client
not Allowed”: . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.1.8 FlexLM License Manager - When I start the program, I
get a “Cannot read dongle”error: . . . . . . . . . . . . . . 49
7.1.9 FlexLM- Server license does not work: . . . . . . . . . . . 49
7.2 Report errors/suggestions . . . . . . . . . . . . . . . . . . . . . . 60
Deltares 4
Chapter 1
BREAKWAT
With BREAKWAT 3 a conceptual design can be made for statically stable struc-
tures, like rubble mound breakwaters with an armour layer of rock or concrete
units, as well as for dynamically stable structures, like berm breakwaters, reef
type structures and near-bed structures. It is also possible to make calculations
for vertical (caisson) structures. BREAKWAT 3 uses modern design formulae
to perform calculations to the hydraulic response:
• wave run-up,
• wave transmission
1
BREAKWAT 3 README v2.0 July 16, 2010
Demo animations
To get an impression of the general program layout and the structure of BREAK-
WAT 3, watch the following animations via QuickTime Movie or Aawin (Au-
todesk Animation Player):
• in CreateCase.flc a calculation is carried out to determine the stability of
the top-layer of rock armour of a rubble mound breakwater
• in CreateGraph.flc a graph is created with the generated output of the
stability calculation
• in CompareCasesInGraph.flc the output of two cases is compared in a graph
• in CompareCasesInSpreadsheet.flc the output of two cases is compared in
a spreadsheet
• in VerticalCaissonBreakwater.flc the possibility of copying data from other
software to a specific case in BREAKWAT 3 is shown in a computation
with a vertical (caisson) breakwater.
For more information see PDF brochure BREAKWAT 3 (To view this PDF
brochure the user must have a PDF reader installed on his/her system)
Deltares 2
Chapter 2
Installation
• http://www.adobe.com
After inserting the BREAKWAT 3 installation disk in the CD-ROM the program
Install Shield.EXE starts if the AutoRun functionality is enabled on the system.
The dialog shown in Figure(2.1) will pop up.
This dialog Figure(2.1), enables the user to perform the following actions:
• Install
To start one of these options move the cursor across an item, which will high-
light(color red) the selected text. Double clicking the highlighted text activates
the selected option.
3
BREAKWAT 3 README v2.0 July 16, 2010
• Install BREAKWAT 3 : Selecting this option, the user installs the program
BREAKWAT 3 on the PC. To run BREAKWAT 3 correctly the regional
settings must be set to English UK/US, i.e. numbers and fractions should
be separated by a dot (.).
For Delft-Chess software two types of hardware keys are available. The first
type is called a BLACK DONGLE 8.0, see Figure(2.3). This type must be at-
tached to the computer via the parallel port and is only delivered with the soft-
ware on request. The second type is called an USB-dongle, see Figure(2.4) which
must be connect to the computer via an USB port. This type of dongle is deliv-
ered with the software by default. In case the user wants to replace a BLACK
DONGLE 8 with the USB-dongle, please contact delftchess.support@deltares.nl.
Deltares 4
BREAKWAT 3 README v2.0 July 16, 2010
For more detailed information on the installation of a license file see document
Installing DS Flex, which is located on the CD.
BLACK DONGLE 8.
USB DONGLE 9
Deltares 5
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 6
Chapter 3
Release-Notes
• The user is able to use (if licensed) a new design tool to predict the mean
wave overtopping discharge at coastal structures. The output of this tool
includes the Neural Network prediction of the mean wave overtopping dis-
charge and several other parameters indicating the uncertainty of the pre-
diction. The tool was developed by WL | Delft Hydraulics co-sponsored
by the Commission of the European Communities within the framework of
the CLASH project (‘Crest Level Assessment of Coastal Structures by full
scale monitoring, neural network prediction and Hazard analysis on per-
missible wave overtopping’). Details of the methodology followed for the
development of the prediction tool are described in Pozueta et al. (2004)
and Van Gent et al. (2004).
• The user is able to use (if licensed) a new design formula to determine the
stability of the rock armour at the rear side of rubble mound breakwaters
developed by Van Gent & Pozueta (2004). Based on physical model tests
Van Gent & Pozueta (2004) proposed a formula to estimate the stone
diameter for a given damage level for a wide range of conditions.
• The user is able to use (if licensed) a new set of design formulae to de-
termine the stability of rock armour on the front slope of rubble mound
breakwaters developed by Van Gent et al. (2003). Based on new physical
model tests Van Gent et al. (2003) proposed to apply modifications to
the formulae by Van der Meer (1988) to include situations in which wave
7
BREAKWAT 3 README v2.0 July 16, 2010
• The user is able to use (if licensed) a new design formula to determine the
stability of rock armour on the front slope of rubble mound breakwaters
developed by Van Gent et al. (2003). Based on new physical model tests
Van Gent et al. (2003) proposed a new, relatively simple design formula.
There is an influence of the wave period, but this influence is considered
small compared to the amount of scatter in the data due to other reasons.
Therefore, the wave period is not used in this formula and there is no
separation between ‘plunging’ and ‘surging’ conditions. The influence of
the permeability of the structure is incorporated by using the ratio between
the diameter of the core and the diameter of the main armour material.
The formula is suitable for both shallow and deep water conditions at the
toe of the structure.
• Input values, inclusive input tables, are restored again when switching
between different structure types or response factors or fomulae.
• A general calculator (menu item New case|Simple calculator 1.0 ) has been
implemented for the calculation of the following depending parameters:
• The formula for X-blocs has been added to the response factor 2. Structural
response 2.2 Concrete armour of the structure type 1. Rubble mound
stucture 1.1 Conventional Breakwater,
• The formula for rear-side stability of rubble mound structures with crest
element (van Gent (with crest elements)) has been added to the response
Deltares 8
BREAKWAT 3 README v2.0 July 16, 2010
3.2 Modifications
• Modifications RELEASE 3.00.0023 VERSUS RELEASE 3.00.0022
• Modifications RELEASE 3.00.0024 VERSUS RELEASE 3.00.0023
• Modifications RELEASE 3.01.0000 VERSUS RELEASE 3.00.0024
• Modifications RELEASE 3.01.0001 VERSUS RELEASE 3.01.0000
• Modifications RELEASE 3.02.0000 VERSUS RELEASE 3.01.0001
• Modifications RELEASE 3.3.0.21 VERSUS RELEASE 3.02.0000(=version
3.20)
Deltares 9
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 10
BREAKWAT 3 README v2.0 July 16, 2010
again. The reason for this problem was the Zparameter was set to ”NONE”
which caused the program to select another routine to create the graph.
Changing ”NONE” to ”” within BREAKWAT 3.0 solved the problem.
• The box containing CASE icons and PROJECT icons is now not visible
if nothing has been created. After creation of a CASE or PROJECT the
box becomes visible.
• If pause button was pushed, while an edit field in Property Editor was
selected BREAKWAT 3.0 crashed. This is solved now.
• The user is able to put only one value in the input table and generate
output tables with only one input value. This make it possible to put a
single value in a graph.
• The ratio H2%/H1/3 in the ‘wave height distribution’ is not equal to the
ratio H(P)/H1/3, when P has a value of 2 %.
• If 2 cases are active at the same time with the same name, problems
could arise, now case names are check and the user is informed if two
cases/projects have the same names.
Deltares 11
BREAKWAT 3 README v2.0 July 16, 2010
• The wave height factor αHs was not correctly implemented in the Hudson-
formula. This is the case for conventional rubble mound breakwaters, as
well as for breakwaters with a top-layer of concrete armour units. This is
now corrected.
• When closing BREAKWAT 3.0, the user was not always informed correctly
about if a file needed to be saved or not. This problem is solved now.
Files are stored in an object array. Before quitting this array will be walk
through sequentially to see if a file needs to be saved or not.
• A few textual improvements have been made to the GUI as well as the
manual.
• New icon has been made for BREAKWAT 3.0
• The undo-button has been removed from the property editor.
• At startup time the Regional Settings of the system are checked. If the
regional settings are not correctly set for BREAKWAT 3.0 the program
BREAKWAT 3.0 shows a warning.
Deltares 12
BREAKWAT 3 README v2.0 July 16, 2010
• All icons have been removed from the property editor, except the input,
output and message icon.
– wave overtopping
– stability formulae rock armour
– stability formula Cubes
– stability formula Accropodes
– toe berm stability of vertical(caisson) breakwater
– wave transmission over berm breakwaters
• The manual has also been converted to a document in PDF format. The
links throughout the document have been preserved. Users can quite easily
make hard copies of this document themselves. The design formulae are
displayed more clearly in the document.
• The parameter sm−1,0 has been added as a new output parameter for the
formula (TAW ,2002) for runup on conventional RMB’s.
• The roughness reduction factor γf has been changed for the formula (TAW
,2002) for runup on conventional RMB’s. The factor has been made linearly
dependent of the surf similarity parameter ξ0 on the interval 1.8 < ξ0 < 10.
• The stability formula for Accropodes has been changed: the threshold for
failure has been set to Hs/∆Dn = 2.5 is used in the formula, instead of
3.7 and 4.1. The confidence bands have been disabled.
• The possibility to work with Projects and/or Cases with the same name
(by using the “Save as” button), which ultimately results in a crash of
BREAKWAT, has been disabled.
Deltares 13
BREAKWAT 3 README v2.0 July 16, 2010
• The possibility to use the same name for different projects by using the
“Rename” button has been disabled.
• The possibility to select a file with any arbitrarily extension as the editor
has been disabled. It is only possible to select files with the extension exe.
• The Rayleigh distribution option in the Graph start window can only be
selected if the active case has a formula with an “Exceedance probability”
parameter.
• The initial profile for the calculation of the profile development of berm
breakwaters has to be specified with positive x- and y-values. The default
values for the initial profile have been changed slightly.
• If a value outside the valid range has been entered for the parameter Dn50-
core/Dn50 in formula Rock Armour, Van Gent et al., the error message is
displayed correctly now.
• The file “breakwat.ini” has been updated. Due to this update changing
between Neural Network and Toe Berm Stability of RMD formula will not
result in an invalid range messages.
• The valid range for cot(αu), Neural Network, has been changed. Values
between -1 and 10 are allowed now.
• A dimension parameter has been added to the header of the input x values
for Profile Development.
• Loading Neural Network cases/projects from directories other than the in-
stallation directory is possible now. Before an error was generated because
the file “nn overtopping.ntd” could not be found.
• During the setup the error message “The procedure entry point for read dir i8
could not be located in the dynamic library Dfortt.dll” could pop up. This
problem is solved now, by installing the file Dforrt.dll in the “c:\windows\system32”
directory instead of the installation directory.
• After pressing the menu option “Save” or “Save All” the files will be saved
at the locations where they have been save before. In previous versions
this was not the case. After pressing these menu options the files were
Deltares 14
BREAKWAT 3 README v2.0 July 16, 2010
• Extra check has been added to see if text editor exists. The default text
editor can be changed by selecting the menu option: “Settings|[Editor]”.
• The creation of the file “breakwat.txt” if forced every time a case is printed
to a text editor.
• If a new row is added to the input table for the calculation scenarios in the
case “1. Rubble mound, 1.2 Berm breakwater, 2. Structural response, 2.1
Rock armour”, all the values will be kept as they have been entered.
• If more then 2 cases are compared by using the Compare button, the cases
are displayed as rows instead of columns. To change the view press button
“arrow pointing clockwise”, which is situated in the upper left corner.
• If the option “Save All (F1)” is used, all cases are saved to the directory
specified as working folder. By default this will be the directory called
<installation directory>\WorkingFolder
• For formula “Van Gent et al. (2003)” in the case “1. Rubble mound, 1.1
Conventional breakwater, 2. Structural response, 2.1 Rock armour” the
exponent -1 in the term (1 + (Dn50core /Dn ))−1 has been changed to -2/3
• The units displayed for cot(alpha d) and cot(alpha u) for the case “1. Rub-
ble mound, 1.1 Conventional breakwater, 1 Hydraulic response,1.3 Over-
topping” have been changed to (-).
• The definition sketch for case “Rubble mound 1.1, Conventional breakwater,
Hydraulic response 1.1.1. Wave height distribution” has been improved.
• For the case “1. Rubble mound structure, 1.1 Conventional breakwater,
2 Structural response, 2.1 Rock armour, Probability of damage the input
parameter” the parameter Tm−1,0 is set inactive as it is not used for this
formula.
Deltares 15
BREAKWAT 3 README v2.0 July 16, 2010
• For the case “1. Rubble mound, 1.2 Berm breakwater, 2. Structural re-
sponse, 2.1 Rock armour”, the maximum number of row for input calcula-
tion scenarios is limited to 8.
• For the case “1. Rubble mound, 1.2 Berm breakwater, 2. Structural re-
sponse, 2.1 Rock armour”, all values in output tables are reset to zero.
Unfortunately if the user presses the button “All Profile Chart” all profiles
are plotted despite the error.
• For case Neural Network, the validity range for the parameter cot(αu) has
been changed for negative values.
• For formula Rock Armour, Van Gent et al.. a wrong value was displayed for
the parameter Dn50-core/Dn50 after entering a value outside the validity
range.
• The menu option “Save”, saves all files to the user specified working folder.
This folder can be set by selecting menu option “Settings|[Environment]
”.
• The menu option “Save As..” has been improved. It is now possible to use
this menu option to save a case without being obliged to change the name.
• For case “1. Rubble mound, 1.5 Near-bed structures, 2. Structural response,
2.1 Rock armour” the value hc is correctly read from file if value is outside
range.
• For case “1. Rubble mound, 1.2 Conventional breakwater, 1.Hydraulic re-
sponse,1.3 Neural network”, the Quantiles for the mean overtopping rate
are displayed in a graph if more than 1 input scenario is defined.
• For case “1. Rubble mound, 1.4 Reef type structure, 1 Structural response,
1.4 2.1 Rock armour” if the output parameter Hs is selected and the input
parameter Dn50 is set to 0.1 BREAKWAT does not crash anymore
Deltares 16
BREAKWAT 3 README v2.0 July 16, 2010
• The version number of dynamic library “ Proba2.dll” has been set to 1.0.0.3
due to changes in directory structure, not relevant for the user.
• Improved license handling with respect to server licenses to avoid the error
message “Bad Encryption Handshake”.
• The key combination CRTL-Z for the formula editor (property editor) has
been disabled as it serves no purpose and it causes BREAKWAT to crash
sometimes.
• For case “1. Rubble mound, 1.4 Reef type structure, 2 Structural re-
sponse,2.1 Rock armour, Reef type breakwat” the text “Warning: depth
limitation. . . .” has been adjusted.
Deltares 17
BREAKWAT 3 README v2.0 July 16, 2010
• For case “1. Rubble mound, 1.1 Conventional breakwater, Hydraulic re-
sponse 1.3 Overtopping, TAW”, the automatic restriction for formula γb ∗
γf ∗ γβ ∗ γvw > 4.0 and γb ∗ γf ∗ γβ > 4.0 has been removed. Instead, a
warning is posted if this occurs.
• For case “1. Rubble mound, 1.1 Conventional breakwater, Hydraulic re-
sponse 1.2 Runup, Runup on bermed slopes- TAW formula”, the automatic
restriction for formula γb ∗γf ∗γβ > 4.0 has been removed. Instead, a warn-
ing is posted if this occurs.
• The program DS Flex has been removed from the setup and incorporated
in the program Install Shield.exe. This enables the user to install BREAK-
WAT silently.
• The program DS Flex has been updated, current version is 5.6.3.0.
• After saving a case by using the menu option File|Save the directory name
is stored for this case.
• Deactivated the functions attached to the keyboard key “Pause” as it serves
no usable purpose. This function displayed all the BREAKWAT parame-
ters of the active property window.
• The background picture within the main window is resized after a resize
event.
• After resizing the property window the error text box is resized also.
• The formula for wave transmission of De Jong-d’Angremond has been
merged with the formula of wave transmission of Briganti et al, 2004.
B B
Either one is selected based on the criteria H < 10 or H >= 10.
• For case “1. Rubble mound, 1.1 Conventional breakwater, Hydraulic re-
sponse 1.3 Overtopping, Neural Network” , uncertainty levels are plotted
adding new values to the input table of an input parameter when using
add cell button instead of enter key.
• For case “1. Rubble mound, 1.2 Berm Breakwater, Hydraulic response 1.4
Rock armour, Van der Meer (Profile development)”, when defining profiles,
negative y values are allowed.
• For case “1. Rubble mound, 1.1 Conventional breakwater, Hydraulic re-
sponse 1.3 Overtopping, Neural Network” , BREAKWAT should be able
to find the dynamic library (DLL) ’nn overtopping.dll’.
• For case “Vertical (caissons) structure 2.1, Hydraulic response 2.1.1.3 Over-
topping, Van der Meer (overtopping)” , the manual has been updated due
to a typing error. The term H 2 should be H 3 in the overtopping formula.
• For case “1 Rubble mound, 1.1 Conventional breakwater, 2 Structural re-
sponse 2.4 Rear side stability, Van Gent & Pozueta ” , the parameter γf
has been added to the term (z1% − (γfRc
∗Hs)
).
Deltares 18
BREAKWAT 3 README v2.0 July 16, 2010
• The correct units are displayed in the first row of the summary tables.
• For the case “1. Rubble mound, 1.2 Berm breakwater, 2. Structural re-
sponse, 2.1 Rock armour” the total number, inclusize actual values, of
storm conditions is restored when switching between structure types, re-
sponse types or formulae.
• For case “Vertical (caisson) 2. Structural response 2.3 Toe berm stability”,
the formula Tanimoto has been changed to Tanimoto/Takahashi.
• For “Vertical (caisson) 2. Structural response 2.3 Toe berm stability Tan-
imoto” the calculation of Hs based on Dn50 is performed correctly now.
This has been corrected for the new formula Tanimato/Takahashi.
• When iterative processes do not converge, no ouput is printed for the pro-
vided input,
Deltares 19
BREAKWAT 3 README v2.0 July 16, 2010
• Write permission:
Deltares 20
BREAKWAT 3 README v2.0 July 16, 2010
• No solution has been found yet, to store the data which has been added to
a graph by the user.
• If a user creates a case and selects an input parameters, changes it’s value
and selects table, the entered value will be shown in the table, however, if
table is deselected for that particular parameter the entered value is reset
to the default value.
• When inserting a new row to the input table by using the insert button
at the left top of the window containing the table, the value shown after
insertion, varies sometimes from zero, nothing to default value of that
particular parameter.
Deltares 21
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 22
Chapter 4
BREAKWAT FAQ
Message -”Error in parsing vendor information from license file, closing application”:
This error indicates that the VENDOR information in the license file is not
correct. To solve this, please send an email to delftchess.support@deltares.nl,
including the license file.
23
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 24
Chapter 5
FLeXLM
The license files issued by Deltares are connected to a hardware key, also
called a dongle. Two types of dongles can be issued. The first type is called the
BLACK DONGLE 8 (see Figure(5.1)) which communicates via the parallel-port
and is issued on request only. The second type is called the USB-DONGLE 9
(see Figure(5.2)) which communicates via the USB-port and is issued with each
software delivery. Clients who currently use a BLACK-DONGLE 8 can exchange
this dongle for an USB-DONGLE 9 at a certain fee or free of charge, depending
on the maintenance contract. For exchanging dongles, please sent your request
to delftchess.support@deltares.nl.
25
BREAKWAT 3 README v2.0 July 16, 2010
REMARKS:
Deltares 26
Chapter 6
Installation DS FLEX
6.1 Introduction
Installing DS FLEX for the first time, consents the user to select a configu-
ration type, see Figure(6.1). Once this configuration type has been set, it
can be changed by simply rerunning the setup of DS FLEX. To add new li-
censes, select the menu item Start|P rograms|Delf t Hydraulics |DHS License
Manager([Configuration T ype])| Add License File. Within the brackets [], the
installed configuration is displayed.
To verify which license type has been issued, check the contents of the license
file. In general a license file contains one or more features. Each feature contains
(not in this order) a version number, expiration date, client information, type of
security (dongle, ethernet or demo) and in case of a server license the number
of licenses which can be issued. Further, a server license contains an additional
keyword called SERVER at the top of the license file. For more detailed infor-
mation on features see the manual LicensingEndUserGuide.pdf, which is located
in the installation directory of the program DS FLEX.
Apart from the installation of software and the license file the setup program
sets several environment variables, which enables programs to access the license
from an arbitrary location on a disk or network. As each FLeXLM version is
connected to a separate environment variable, the setup sets four different en-
vironment variables due to backwards compatibility. The following environment
variables are set:
27
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 28
BREAKWAT 3 README v2.0 July 16, 2010
One of the first windows the user comes across after starting the program
DS FLEX is shown in Figure(6.1). However, if the program DS FLEX is al-
ready installed on a system, the first window, after the introduction window, the
user comes across is not the window shown in Figure(6.1) but the window shown
in Figure(6.2).
• Server Only
Each of the items is described in the next sub-sections.
Deltares 29
BREAKWAT 3 README v2.0 July 16, 2010
The next section gives a description on the different windows which the user
could come across during the installation process depending on the type of con-
figuration selected!
Deltares 30
BREAKWAT 3 README v2.0 July 16, 2010
The window shown in Figure(6.2) notifies the user which license configu-
ration has been installed and that it will be removed before the new selected
configuration is installed.
Deltares 31
BREAKWAT 3 README v2.0 July 16, 2010
The next window the user comes across is shown in Figure(6.3). This window
allows the user to choose between installing just USB dongle drivers, or driver
for both USB(see figure (5.2)) and BLACKDONGLE (see figure (5.1)). The
installation of parallel port dongle drivers is only needed for users with a parallel
port dongle. The installation of ’USB dongle drivers only’ is recommended for
all users not using parallel dongles.
This window will only show up when the license software DS FLEX is in-
stalled one of the following operating systems:
• Windows 2000
Other operating systems will skip this choice and will install USB dongle
drivers only. Users with parallel port dongles using an operating system not
listed above should contact their software support or helpdesk. The general
e-mail address delftchess.info@deltares.nl can also be used for this purpose.
Deltares 32
BREAKWAT 3 README v2.0 July 16, 2010
The next window the user comes across is shown in Figure(6.4). This window
gives the user the possibility to select the destination folder to where the program
DS FLEX is to be installed. By default the installation directory has been set
to “C:\Program Files\DS Flex”.
To alter the location, press the button ’Browse...’ and select a different
directory.
Deltares 33
BREAKWAT 3 README v2.0 July 16, 2010
The next window the user comes across is shown in Figure(6.5). This window
allows the user to install the license file or to postpone this selection.
Deltares 34
BREAKWAT 3 README v2.0 July 16, 2010
The next window the user comes across, depending on whether or not the actual
license file needs to be installed, is shown in Figure(6.6). This window allows
the user to select the license file.
Deltares 35
BREAKWAT 3 README v2.0 July 16, 2010
The next window the user can come across, depending on whether the config-
uration type Server Only or Server and Client has been selected at the beginning
of the installation process, is shown in Figure(6.7). This window allows the user
to start a License Service on a computer. Selecting the option Yes will start
the service after the license software has finished automatically. To start such a
service manually, see section(6.4.2).
Deltares 36
BREAKWAT 3 README v2.0 July 16, 2010
• SERVER NAME: This predefined name must be set to the name of the
server. Remember, use either lower or upper case for all license files.
This sub-section contains the contents of an example license file, which is gen-
erated by FLexLM version 9. Use the tool ”Add License File” to install this
license file on the server.
This sub-section contains the contents of an example license file, which is gen-
erated by FLexLM version 10. Use the tool ”Add License File” to install this
license file on the server.
Deltares 37
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 38
BREAKWAT 3 README v2.0 July 16, 2010
• Services/License File
• System settings
• Utilities
• Start/Stop/Reread
• Server Status
• Config Services
• Borrowing
Not all functions are used for starting a service, so only the functions which
are of interest are discussed here.
Deltares 39
BREAKWAT 3 README v2.0 July 16, 2010
According to this Figure(6.9) the following fields are to be set, for specifying
a service:
• Service Name : Enter the name of the service here. It is also possible to
select another service
• Path to the lmgrd.exe file : Select the program lmgrd.exe (deamon) on your
computer.
• Path to the license file : Select a license file or specify a path which contains
the license files.
• Path to the debug log file : Specify the name of the log file, including the
location where it needs to be stored.
• Start Server at Power Up : Switch which makes sure that the daemon is
automatically started at power up.
After all values have been entered and the service has been saved (press
button Save Service and go to tab “Start/Stop/Reread” to start the service.
Deltares 40
BREAKWAT 3 README v2.0 July 16, 2010
• Button Reread License File: Rereads a new license file (see Paragraph(6.4.2)
of the highlighted service
After pressing the button Start Server, please check whether or not the service
has been started successfully by selecting the next tab called Server Status.
Selecting this tab opens the window according to Figure(6.11).
Deltares 41
BREAKWAT 3 README v2.0 July 16, 2010
When to update a service: Before the current license daemon can be up-
dated, all services which use this daemon needs to be stopped. To do this perform
the following actions:
• Select the service form the list “Service Name” which needs to be stopped,
Deltares 42
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 43
BREAKWAT 3 README v2.0 July 16, 2010
• Press the button “Stop Server”. This will stop the service which has been
selected on tab “Config Service”.
• Repeat this for each service which uses the daemon lmgrd.exe.
After all services attached to the daemon “lmgrd.exe” have been stopped, ac-
tivate the new version of the daemon “lmgrd.exe” by performing the following
actions:
• Install or copy the new version of the program “lmgrd.exe” and related
programs in the current DS FLEX directory or a new directory,
• After installation go to the installation directory and start the new version
of program “lmtools.exe” if it did not start automatically already after the
installation of the program DS FLEX,
• For each service displayed in the list (see Figure(6.12) perform the following
actions:
• After all services have been started, perform a status enquiry (tab Server
Status by pressing button “Perform Status Enquiry”, to check if all services
are running correctly.
Deltares 44
BREAKWAT 3 README v2.0 July 16, 2010
Update a license file: In case the current server license file needs to be
replaced by a new one the user can simply use the option Reread License File
on tab Start/Stop/Reread to activate it. To activate the new license file perform
the following actions:
• Overwrite the current license file by the new license or merged license file,
• After all services have been started, perform a status enquiry (tab Server
Status by pressing button “Perform Status Enquiry”, to check if all services
are running correctly.
1
Combining two server license files is also possible before updating the service. To merge two
server license file, copy all information in the new license file except the string which contains
the keyword SERVER. Furthermore if different versions of the VENDOR string (VENDOR
lmwldelft D:\app\flexlm\lmwldelft.exe ) are being used within one license file, put the string
containing the oldest version of the VENDOR daemon on top followed by a newer version (see
below)
SERVER EAGLE 00AAABDS TCP:8500
VENDOR lmwldelft D:\app\flexlm\lmwldelft.exe (version7)
VENDOR dwldelft D:\app\flexlm\dwldelft.exe (version 9)
VENDOR dhsdelft D:\app\flexlm\dhsdelft.exe (version 10)
After the VENDOR strings are correctly sorted, check if the location of each VENDOR daemon
is still specified correctly. If not enter the correct locations manually.
Deltares 45
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 46
Chapter 7
DS FLEX FAQ
47
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 48
BREAKWAT 3 README v2.0 July 16, 2010
• Select the System Settings tab. In the FLEXID box, the dongle number of
the dongle should be visible. The reading of lmtools is not always accurate,
i.e. sometimes lmtools does not report the dongle although the program
starts without problems and does not report an error. So always check
if the dongle works with both the program and lmtools. When lmtools
does report the dongle then the program should be able to use the dongle.
When the dongle is attached and the error still occurres or lmtools does not
detect the dongle,the dongle drivers needed for this dongle are not installed
properly.
Deltares 49
BREAKWAT 3 README v2.0 July 16, 2010
in all license files so that the case (upper or lower) that is used in all the license
files is the same. Take care to use the server name that is defined in a license
files from Delft Hydraulics that have been added to the server computer using
the ‘add license tool’ or alternatively use the server name that is defined in the
registry key
“System\CurrentControlSet\Control\ComputerName\ComputerName”. The ‘add
license tool’ uses the same registry key to determine the server name on during
installation of the license file.
Server node is down or not responding, although server log file looks fine. I
have configured my license Server and the server log does not contain any errors.
When I start my application on the Client PC, I get the error: Server node is
down or not responding
The client application needs to connect to the license daemon and vendor dae-
mon processes that are running on the Server. You need to check if there is a
fire wall configured on the Server that blocks the connection to these processes.
In the FLEXnet (FLEXlm) server log file the port numbers that are used by the
license daemon lmgrd and the vendor daemons lmwldelft, dwldelft and dhsdelft
are reported.
14:53:18 (lmgrd) ———————————————–
14:53:18 (lmgrd) Please Note:
14:53:18 (lmgrd)
14:53:18 (lmgrd) This log is intended for debug purposes only.
14:53:18 (lmgrd) In order to capture accurate license
14:53:18 (lmgrd) usage data into an organized repository,
14:53:18 (lmgrd) please enable report logging. Use Macrovision’s
14:53:18 (lmgrd) software license administration solution,
14:53:18 (lmgrd) FLEXnet Manager, to readily gain visibility
14:53:18 (lmgrd) into license usage data and to create
14:53:18 (lmgrd) insightful reports on critical information like
14:53:18 (lmgrd) license availability and usage. FLEXnet Manager
14:53:18 (lmgrd) can be fully automated to run these reports on
14:53:18 (lmgrd) schedule and can be used to track license
14:53:18 (lmgrd) servers and usage across a heterogeneous
14:53:18 (lmgrd) network of servers including Windows NT, Linux
14:53:18 (lmgrd) and UNIX. Contact Macrovision at
14:53:18 (lmgrd) www.macrovision.com for more details on how to
14:53:18 (lmgrd) obtain an evaluation copy of FLEXnet Manager
14:53:18 (lmgrd) for your enterprise.
14:53:18 (lmgrd)
14:53:18 (lmgrd) ———————————————–
14:53:18 (lmgrd)
14:53:18 (lmgrd)
14:53:18 (lmgrd) Done rereading
14:53:18 (lmgrd) FLEXnet Licensing (v10.1.3) started on WL06008 (IBM PC)
Deltares 50
BREAKWAT 3 README v2.0 July 16, 2010
(2/17/2006)
14:53:18 (lmgrd) Copyright (c) 1988-2004 by Macrovision Corporation. All rights
reserved.
14:53:18 (lmgrd) US Patents 5,390,297 and 5,671,412.
14:53:18 (lmgrd) World Wide Web: http://www.macrovision.com
14:53:18 (lmgrd) License file(s): C:\Program Files\DS Flex\delft3d.8-5E700060C1CF.lic
C:\Program Files\DS Flex\delft3d.of.8-5E700060C1CF.lic
14:53:18 (lmgrd) lmgrd tcp-port 8500
14:53:18 (lmgrd) Starting vendor daemons ...
14:53:18 (lmgrd) Started dhsdelft (pid 1660)
14:53:18 (lmgrd) Started dwldelft (pid 4012)
14:53:18 (dwldelft) Server started on WL06008 for: PHAROSUI
14:53:18 (dhsdelft) Server started on WL06008 for: MCI PHAROS GUI
14:53:18 (dhsdelft) DHS Delft3D FLOW
14:53:18 (lmgrd) dwldelft using TCP-port 1245
14:53:19 (lmgrd) dhsdelft using TCP-port 1249
In this example you need to make sure that the port numbers used by the
license Server lmgrd (8500) and the vendor daemon dwldelft and dhsdelft (in the
session that is shown in the log file: 1245 and 1249) are available and can be
reached by the Client computer.
To specify the port numbers that are used by the license Server and the vendor
daemon, you can modify the license file:
Check if the Server is running properly, which means: You need to check if the
license Server supports all the licensing features that you expect it to support.
You can do this by inspecting the Flex WL.log file in the DS Flex directory
on the Server.
In this file you will find the license files that are read by the license Server process
(lmgrd.exe) and a list of features that are supported.
If not all license files are listed in the log file
Check if the service configuration of the license Server is correct
Deltares 51
BREAKWAT 3 README v2.0 July 16, 2010
3. Check if the Path to the license file contains only the DS Flex directory
and no specific license file, see Figure(7.1)
Deltares 52
BREAKWAT 3 README v2.0 July 16, 2010
If you have edited the path to the license file, you should save the service and
stop and start the license Server. Stopping and starting the license Server can
be done with the Start/Stop/Reread tab, see Figure(7.2).
Deltares 53
BREAKWAT 3 README v2.0 July 16, 2010
Now you can check the log file again and see if all license files and features
are logged in the log file.
Have all the license files in the DS Flex directory been added with the Add Li-
cense File tool that can be found under
Start|Programs|Delft Hydraulics|DHS License Manager|Add License File?
This can be diagnosed by inspecting the first two lines in the license files. When
they look like:
SERVER SERVER NAME FLEXID=9-23EE9563 TCP:8500
VENDOR dhsdelft DHSDELFT DAEMON
It has not been processed by the Add License File tool; when the first two
lines look like:
SERVER WL06008 FLEXID=9-23EE9562 TCP:8500
VENDOR dhsdelft ”C:\Program Files\DS Flex\dhsdelft.exe”
Then the license file has been processed by the Add License File tool. It has
replaced the string “SERVER NAME ”with the actual server name, in this
example “WL06008 ”and it has replaced the string “DHSDELFT DAEMON
”with the actual path to the vendor daemon, in this example “C:\Program
Files\DS Flex\dhsdelft.exe”.
If files are found that have not been processed with the Add License File tool,
remove them from the DS Flex directory and add them with the Add License
File tool. Now stop and start the license Server, see Figure(7.2), and inspect the
log file of the license Server. All the files should be logged in the log file.
If not all features that you expect can be found in the log file
Make sure that all the license files that you have received from Delft Hydraulics
have been added with the Add License File tool. Restart the Server if necessary.
Deltares 54
BREAKWAT 3 README v2.0 July 16, 2010
• Step I: Check if the dongle is inserted in the USB port of the computer. If
the dongle is not inserted in the USB port, insert the dongle and check if
lmtools reports the dongle now.
• Step II: Perform an installation with the latest DS Flex installer. This in-
staller can be found at the Delft Hydraulics Support Site: “Delft Hydraulics Software/FL
the installation the dongle should be removed from the computer.
Deltares 55
BREAKWAT 3 README v2.0 July 16, 2010
1. The environment
The environment variables that are used are:
Running a license server with license files for PHAROS version 8.01 or lower
generates errors
When you use the latest distribution of license files on a license Server it is pos-
sible that the oldest vendor daemon , lmwldelft, will generate errors.
14:45:28 (lmgrd) ———————————————–
14:45:28 (lmgrd) Please Note:
14:45:28 (lmgrd)
14:45:28 (lmgrd) This log is intended for debug purposes only.
14:45:28 (lmgrd) In order to capture accurate license
14:45:28 (lmgrd) usage data into an organized repository,
14:45:28 (lmgrd) please enable report logging. Use Macrovision’s
14:45:28 (lmgrd) software license administration solution,
14:45:28 (lmgrd) FLEXnet Manager, to readily gain visibility
14:45:28 (lmgrd) into license usage data and to create
14:45:28 (lmgrd) insightful reports on critical information like
14:45:28 (lmgrd) license availability and usage. FLEXnet Manager
14:45:28 (lmgrd) can be fully automated to run these reports on
14:45:28 (lmgrd) schedule and can be used to track license
14:45:28 (lmgrd) servers and usage across a heterogeneous
Deltares 56
BREAKWAT 3 README v2.0 July 16, 2010
5E700060C1CF.perm.lic
14:45:28 (lmgrd) lmgrd tcp-port 8500
14:45:28 (lmgrd) Starting vendor daemons ...
14:45:28 (lmgrd) Started dhsdelft (pid 3832)
14:45:28 (lmgrd) Started dwldelft (pid 2708)
14:45:28 (lmgrd) Started lmwldelft (pid 1592)
14:45:29 (lmwldelft) Cannot open license file C: \flexlm \license.dat
As long as you run PHAROS version 8.02 or higher this will cause no problems
running PHAROS. We advise you to migrate to a higher version of PHAROS.
When this is not possible, you need to contact the Ed Ehrlich.
When you run a license Server with multiple license daemons, as is the case with
many PHAROS set-ups, it is possible that you get restarting license daemons.
This results in no licenses being served by the license Server. This problem can
also occur when you run license files from several suppliers on one license Server.
To illustrate the contents of alog file is printed below.
Log file
15:04:36 (lmgrd) ———————————————–
15:04:36 (lmgrd) Please Note:
15:04:36 (lmgrd)
15:04:36 (lmgrd) This log is intended for debug purposes only.
15:04:36 (lmgrd) In order to capture accurate license
15:04:36 (lmgrd) usage data into an organized repository,
15:04:36 (lmgrd) please enable report logging. Use Macrovision’s
Deltares 57
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 58
BREAKWAT 3 README v2.0 July 16, 2010
Deltares 59
BREAKWAT 3 README v2.0 July 16, 2010
#
FEATURE Delft3D dwldelft 3.39 01-jan-2007 22 34793B375BAB
VENDOR STRING=”USERNAME = ’ Mr Levelt ’; FIRMNAME = ’WL —
Delft Hydraulics’ ;” DUP GROUP=UHD
#
# Grid and bathymetry modules
#
:146
FEATURE RGFGRID dwldelft 4.29 01-jan-2007 2 54452261BA84
DUP GROUP=UHD
FEATURE D3D GIS RGFGRID dwldelft 4.29 01-jan-2007 1 419423F9D5EC
DUP GROUP=UHD
• Case 1: Only License files from Delft Hydraulics are used on this server
When the Add License File tool is consequently used when adding the
license files to the Server computer, this problem will not occur. To solve
the problem, take the license files that were originally provided by Delft
Hydraulics and add them, using the Add License File tool.
• Case 2: License files from multiple vendors are used on this Server Modify
the server names in all license files so that the case (upper or lower) that
is used in all the license files is the same. Take care to use the server name
that is defined in license files from Delft Hydraulics that have been added
to the Server computer using the Add License File tool or alternatively use
the server name that is defined in the registry key “System
CurrentControlSet
Control
ComputerName
ComputerName”. The Add License File tool uses the same registry key to
determine the server name on during installation of the license file.
Deltares 60