home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
dommagr.zip
/
READ.ME
< prev
Wrap
Text File
|
1996-02-02
|
17KB
|
412 lines
Welcome to the ibex Domain Manager
----------------------------------
This document contains last minute information that is not contained in
the printed documentation. Please take the time to review all of this
information carefully. If there are discrepancies between the written
documentation and this document, the information in READ.ME is correct.
The build contained on this CD is defined in \IDM101\OS2\CDINST\IDMDSC.DSC.
We recommend that you read chapters 1 and 2 of the manual before installing.
To install ibex DomainManager, start \IDM101\OS2\CDINST\INSTALL.EXE.
Install asks you for the following paths:
IDM program directory : The path to which the iDM executables are copied to.
NOTES program dirextory: The path to your notes executables
NOTES data directory: The path to the Notes databases
The database IDM-UG.NSF, the Users Guide, contains the complete electronic
version of the printed manual.
ibex DomainManager packed files (.PAK) can be expanded using the standard
OS/2 UNPACK command.
Even though the CD cover booklet mentions that you can place more info on the
CD-R, we did change the format of the disk for compatibility reasons. It is
no longer possible to add data to the CD.
-------------------------------------------------------------------------
This README is split into the following sections:
0 - Installing over older versions of iDM
1 - Documentation Changes
2 - Program & Database Changes
3 - Bug fixes
4 - Known bugs
-------------------------------------------------------------------------
0 - Installing over older versions of iDM
-------------------------------------------------------------------------
iDM allows you to change messages such that they suit your needs. We have
not yet automated the procedure for copying new messages to the configuration
database. Therefore, some extra care is required when updating messages
from IDM-CD.NSF. We will implement an automated process in the future.
Until this has been done, please follow the instructions below.
Installation & Configuration
----------------------------
Run the installation and configuration program as outlined in the user's
guide.
If you did change messages in iDM-CD
------------------------------------
You have to save the changed messages to a temporary database, then
copy IDM-CD.NSF before starting the installation. Then follow the
procedure outlined below, and finally paste your adapted messages
back and delete the duplicates.
If you did NOT change messages in iDM-CD
----------------------------------------
You have to manually copy all messages from the new IDM-CD.NTF template to
your existing master IDM-CD.NSF database (the messages will be replicated
to other servers from there).
Open IDM-CD in view "Messages/Language, Module". Select all messages
(Ctrl-A), and delete them (Del).
Open the IDM-CD.NTF template in view "Messages/Language, Module". Select
all messages (Ctrl-A), and copy them to the clipboard (Ctrl-C).
Now, re-open the IDM-CD.NSF configuration database, and paste the messages
from the clipboard.
-------------------------------------------------------------------------
1 - Documentation Changes
-------------------------------------------------------------------------
Config
------
CONFIG.EXE will create the ServerKeyFileName entry in NOTES.INI, if it
detects that it is not present already.
ExecuteTasks
------------
Contrary to documentation, it accepts wildcard file names for post processing
(still no support for multiple files to detach in preprocessing).
-------------------------------------------------------------------------
2 - Program & Database Enhancements
-------------------------------------------------------------------------
IDM-DA
------
- IDM-DA now handles multiple Replicas of a database (with different paths)
on a single server.
- Due to a version change in the API we based DA on (InterFloX), and the
associated bug fixes, DACLEAN is no longer needed. It is no longer
distributed with the package.
- IDM-DA checks for the version of InterFloX that has been loaded in order
to avoid problems when other programs using the same API are used.
- IDM-DA checks for databases that might have been scanned multiple times
if you had setup directory links in strange ways.
- IDM-DA no longer uppercases all ACL entries it adds - ThIs_UsEr would
be entered as that, not as THIS_USER.
- The Repository has been standardized to use the Abbreviated format for
canonical names (macros to add and delete servers have still used the
full canonicalized name which resulted in unexpected view layouts).
IDM-DA 1.1x is a significant improvement from the 1.0x versions:
- it implements a time check which greatly enhances the speed of the
checking process (2 - 10x)
- it changed the handling of replica ID changes which makes these easier
for the administrator and safer in general
- it changed the handling of roles in order to avoid replication conflicts
that could occur with earlier releases
- it has been "hardened" against user errors like copying and pasting
database descriptions, double ACL entries for the same name, and has
generally better checks for legal inputs (name lengths, character
sets, etc.)
- more command line parameters have been implemented and documented
(see below)
There were also slight improvements done in IDM-DA.NTF/NSF: Where necessary, checks for legal input have been added.
Changing Replication IDs
------------------------
Generally, a change of replication ID is NOT a simple thing and should only
be done after ample consideration. If you need to do it, IDM-DA can assist
you.
Once you have entered the replication ID change order on the database form,
IDM-DA will execute the change in the next run after the order has been
set up.
After successful completion of the process, the repository is updated as
follows:
- if the database description contains a single server,
- its original description with the Replica ID change order is deleted
completely,
- a new description is created (which will be set to
managed no matter what your default managed state is).
- if the database description contains a list of servers,
- the current server is removed from the server list in the now obolete
description
- a new description is created (which will be set to
managed no matter what your default managed state is).
Whereas the single server scenario does not create any problems, the
multiserver scenario will create replication conflicts on the old description
of the database: each server updates the list of servers in each document,
so, this would leave you with (number of servers - 1) replication conflicts
per document that is part of the database description.
Once you have confirmed that all databases have been changed, you can delete
the obsolete database description and consolidate the new database
descriptions by adding all servers to one server list, and deleting the other
database descriptions.
We are aware of the fact that more elegant solutions are possible. We are
working on these - stay tuned.
Command Line Parameters
-----------------------
IDM-DA 1.10 and newer offer the following commmand line parameters:
switch (default) function
----------------------------------------------------------
/A | /A1 | /A0 (/A1) ACL processing on/off
/C<databasefilename> alternate configuration database
/D | /D1 | /D0 (/D0) design processing on/off
/S<databasefilename> single database mode
/T | /T1 | /T0 (/T1) time check
ACL Processing /A
--------------
By default turned on, this switch enables you to prevent IDM-DA from
checking ACL settings.
Usage: IDM-DA /A ENABLES ACL processing (default)
IDM-DA /A1 ENABLES ACL processing (default)
IDM-DA /A0 disables ACL processing
Alternate Configuration Database /C
--------------------------------
By default, IDM-DA uses the default configuration database specified
during the installation, defined by the IDMCD= entry in NOTES.INI.
This switch allows you to specify another configuration database for the
current run.
Usage: IDM-DA USES IDM-CD specified in NOTES.INI (default)
IDM-DA /CTRAINING\IDM-CD.NSF uses an alternative configuration database
Design Processing /D
-----------------
By default, design processing is turned off in IDA-DA. There are various
pitfalls when enabling design tracking. Most prominent among these is
the use of templates. Whenever an update is done using this process,
new design notes may be entered into the database. The administrator
would have to run IDM-DA once on one replica copy of the redesigned
database in unmanaged (monitoring) mode to get an updated structure
of the design, then re-set managed mode, and add all the other servers
that carry the same replica copy.
In addition, be prepared that if design processing is enabled, run time
of IDM-DA is roughly doubled.
Therefore, we chose to turn this option off by default.
Usage: IDM-DA /D0 DISABLES design processing (default)
IDM-DA /D enables design processing
IDM-DA /D1 enables design processing
Single Database Processing /S
--------------------------
If this switch is specified, IDM-DA will work on the single database
whose path and file name is specified after this switch - Useful for
implementing specific changes to one database immediately.
Usage: IDM-DA will work on all databases (default)
IDM-DA /SNAMES.NSF will work on NAMES.NSF only
Time Check /T
----------
Starting with IDM-DA 1.10, a time check is implemented. Instead of
scanning through all documents in repository and all databases on the
server, IDM-DA checks if the repository data and/or database non-data
have changed since IDM-DA's last run. This speeds processing by orders
of magnitude, but if changes have been replicated slowly, or IDM-DA had
trouble during a run, it will NOT check changes that it didn't process
in the previous run. As a safeguard, we implemented this switch, which
allows you to turn the time check off, and have IDM-DA do a complete
"real-estate" check again.
Usage: IDM-DA /T ENABLES time check (default)
IDM-DA /T1 ENABLES time check (default)
IDM-DA /T0 disables time check
IDM-ET
------
Contrary to documentation, IDM-ET's post processing can now handle wild-
card specifications. This allows you to grab several files without naming
each one, or to grab files whose name is only partially known at the time
you setup the task.
If you select "Generate document if above file(s) do not exist" to be Yes,
ET will generate a database document or a mail announcing that no files
have been found. If you select No, no document will be created in this case.
When specifying post processing delivery via database & replication, the
fields form name, field name, and database name are mandatory, the field
database server name is only needed if the destination database is not
local, but on another server.
When specifying post processing delivery via mail, the send to field is
required, subject is optional.
ET Example Jobs
---------------
In talking with customers, we found that iDM-ET is the part of iDM most
underestimated by far. In order to address this problem, we included example
IDM-ET jobs and fragments in the IDM-ET.NTF template. They will be copied
over to your initial IDM-ET.NSF database automatically. Since they are all
disabled, they will do no harm. Look at them and learn from them.
-------------------------------------------------------------------------
3 - Bug fixes
-------------------------------------------------------------------------
Build 28 fixes the following problems:
Licensing:
- Domain names containing characters > CHR(127) are now supported - and these
characters are no longer case sensitive.
- There is now an option for outfits with a large number of domains that allows
us to bypass the domain name check. Ask for this option if you do have a large
number of domains. The customer who requested the feature has > 150 domains...
CONFIG:
- removed calls to DACLEAN - no longer needed.
IDM-DA:
- kaizened internal operations - some double processing of databases has been
prevented from happening.
- There is no need for DACLEAN anymore. The program has been removed from the
suite.
IDM-ET:
- does no longer execute disabled jobs that share their name with an enabled
job (happened most notably with our own example, GET_SERVER_MONITOR_LOG...)
IDM-FM:
- enabled FM to process relative directory link pointers ("..").
Build 27 fixes the following problems:
Licensing:
- The number of licenses field is now trimmed before saving it.
This has caused ET to issue a ET4830 message (too many servers
using iDM).
Build 26 was an internal-only build.
Build 25 fixes the following problems:
All programs:
- occasional problems when initializing notes (most often in SM)
- parameter substitution in messages: substituted texts containing
the sequences '<>' and '<...' at the very end would crash the
logging procedure.
CONFIG:
- the progress indicator has been fixed to only show actions which
are performed. It used to show all actions.
IDM-DA:
- IDM-DA now handles multiple Replicas of a database (with different
paths) on a single server.
- Due to a version change in the API we based DA on (InterFloX), and
the associated bug fixes, DACLEAN is no longer needed. It is no
longer distributed with the package.
- IDM-DA checks for the version of InterFloX that has been loaded in
order to avoid problems when other programs using the same API are
used.
- IDM-DA checks for databases that might have been scanned multiple
times if you had setup directory links in strange ways.
- IDM-DA no longer uppercases all ACL entries it adds - ThIs_UsEr
would be entered as that, not as THIS_USER.
- The Repository has been standardized to use the Abbreviated format
for canonical names (macros to add and delete servers have still
used the full canonicalized name which resulted in unexpected view
layouts).
- sensitivity to operator error has greatly been reduced
- update of replica ID now works reliably
- no more ACL entries that cannot be managed with Notes client
- roles documents replication conflicts have been omitted
IDM-ET:
- a problem with license handling has been fixed
- ET now allows to move its log database anywhere
- Occasional double starts have been prevented
IDM-FM:
- multiple documents for a single directory are now flagged and
removed
- various problems when updating the repository after handling change
requests have been fixed.
-------------------------------------------------------------------------
4 - Known bugs
-------------------------------------------------------------------------
INTER-IBEX is aware of the following bugs in Build 27:
IDM-DA:
- not actually a bug, but a conceptual problem: If you "unmanage" a
database description in the repository that was used by a list of
servers, the first server to detect a change to this database will
delete this description and insert a new one in which only itself is
listed. Consequently, after the deletion has replicated, all other
servers that have been in the list will no longer find a description
for this database and will treat it as a new database.
IDM-FM:
- Updates documents of unchanged directories indicating a change if
directories contain "lots of text", i.e., a lot of files & directories,
or many long file- and directory names. The critical limit is about 14kB
of file- and directory names per directory - as soon as there are
multiple fileListing or directoryListing fields (you can check that in
Design, Document Info).
INSTALL:
- The installation program is not yet CID-enabled.
- Uninstalling does not clean up NOTES.INI and CONFIG.SYS.
-------------------------------------------------------------------------
Please direct all inquiries to:
Notes:
Nick Behrmann @ IBEX @ WorldCom
Nick Behrmann @ IBEX @ LotusInt
Skip Bockoven @ IBEX @ Worldcom
Skip Bockoven @ IBEX @ LotusInt
Internet:
Skip_Bockoven@interibex.com
Nick_Behrmann@interibex.com
Phone numbers:
Nick Behrmann +1-415-572-6160 or +1-800-IBEX-IDM
Skip Bockoven +41-1-802-8680