montanac
10th January 2003, 16:05
Hi all,
I am enclosing the best ever written installation tools:
Claudio Montanari
Senior Technical Manager KNOW-HOW Italy
Tel: +39 0522 232357
Fax: +39 0522 277364
Mobile: +39 348 7307217
E mail: claudio.montanari@know-how.it
Web: http://www.know-how.it
|******************************************************************************
|* Title : tcmcsinstall - Install Based on Customization Part
|* Author : Claudio Montanari
|* Co-Author : Lorenzo Monteforte
|* Date : 2002-05-07
|******************************************************************************
|* Script Type : 4GL
|* Description : Install software across hosts and VRC
|* Category : SysAdmin
|* License :
|*
|* Copyright 2002 by KNOW-HOW - All Rights Reserved
|*
|* Permission to use, copy, modify, and distribute this software and its
|* documentation for any purpose and without fee is hereby granted,
|* provided that the above copyright notice appear in all copies and that
|* both that copyright notice and this permission notice appear in
|* supporting documentation.
|*
|* Claudio Montanari nor KNOW-HOW DISCLAIM ALL WARRANTIES WITH REGARD TO THIS
|* SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
|* AND FITNESS, IN NO EVENT SHALL Claudio Montanari nor KNOW-HOW BE LIABLE FOR
|* ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
|* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
|* WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
|* TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE
|* OR PERFORMANCE OF THIS SOFTWARE.
|******************************************************************************
|*
|* This session installs the components of a customization part from one
|* environment to another.
|*
|* An environment is an host with a particular BSE (the same host can have
|* more that one environment, i.e. more tha one BSE).
|*
|* At the moment the session transfer the software from one environment to
|* another.
|* With few modifications it is possible to transfer the software to a batch
|* of hosts simultaneously.
|*
|* Export and Import of the software can be forced on VRC which are not the one
|* of the customization part.
|*
|* Using PMC for the same scope was not possible far the following reasons:
|* - Too many restrictions
|* - Too cumbersome
|* - Too many rigidity
|* - Going from customization part to PMC solution needed a session
|* - With the PMC it is not possible to have different origin VRC in the
|* same solution
|*
|* This ambitious project uses the export logic based on customization part
|* of the famous ttiexdeliverp.
|*
|* The two most important features of the PMC (rollback and log) are present.
|* An optional backup dump is written in the directory $BSE/install/backup.
|* A log file with all the activities done is present "$BSE/log/log.install"
|*
|* The session is platform and configuration independent (or at least it should
|* be so...), hence it works also on NT using the BW services (ottdllbw).
|*
|* Since it is nearly impossible (any volunteer?) from Baan code to know
|* where the BW client files are, if you want to use the BW, and you want
|* to tranfer files on a remote host, you must have the files BWC associated
|* to the executable BW.EXE instead of the executable BECS.EXE.
|* In alternative, you can install on your PC the BW client for iBaanERP.
|* In this latter case it seems that the BECS handle it correctly...a bit
|* disgusting I know, but the ottdllbw functions are very limited!
|* Morover a quite recent BW version is needed (>= 0.48).
|*
|* To save bandwidth (specially useful when you are connected trough a modem
|* line) and you are using a UNIX server (do you really use NT???) with the r*
|* services enabled, the files can be transferred directly from the source host
|* to the destination host with the UNIX command rcp.
|*
|* Please note that, in order to minimize the fingerprint of the installation
|* on a new environment (it is a tool, remember, nothing else) messages and
|* labels are hardcoded in english (this help too)... I know, this is a bit
|* hugly but in this way you only need to install in your system one session,
|* one form and one script on any existing VRC.
|*
|* You must also create the following directories:
|*
|* ${BSE}/install Root Directory
|* ./common Various file
|* ./import Used for imported dump
|* ./export Used for exporting dump
|* ./backup Used for backup dump
|*
|* The common directory must contain two foundamental files:
|*
|* ShellExec.exe On Windows 95 box I need a small VBS
|* exe which runs application files based
|* on their association mechanism.
|*
|* master.bwc A master bwc file for the BW client
|*
|*
|******************************************************************************
I am enclosing the best ever written installation tools:
Claudio Montanari
Senior Technical Manager KNOW-HOW Italy
Tel: +39 0522 232357
Fax: +39 0522 277364
Mobile: +39 348 7307217
E mail: claudio.montanari@know-how.it
Web: http://www.know-how.it
|******************************************************************************
|* Title : tcmcsinstall - Install Based on Customization Part
|* Author : Claudio Montanari
|* Co-Author : Lorenzo Monteforte
|* Date : 2002-05-07
|******************************************************************************
|* Script Type : 4GL
|* Description : Install software across hosts and VRC
|* Category : SysAdmin
|* License :
|*
|* Copyright 2002 by KNOW-HOW - All Rights Reserved
|*
|* Permission to use, copy, modify, and distribute this software and its
|* documentation for any purpose and without fee is hereby granted,
|* provided that the above copyright notice appear in all copies and that
|* both that copyright notice and this permission notice appear in
|* supporting documentation.
|*
|* Claudio Montanari nor KNOW-HOW DISCLAIM ALL WARRANTIES WITH REGARD TO THIS
|* SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
|* AND FITNESS, IN NO EVENT SHALL Claudio Montanari nor KNOW-HOW BE LIABLE FOR
|* ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
|* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
|* WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
|* TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE
|* OR PERFORMANCE OF THIS SOFTWARE.
|******************************************************************************
|*
|* This session installs the components of a customization part from one
|* environment to another.
|*
|* An environment is an host with a particular BSE (the same host can have
|* more that one environment, i.e. more tha one BSE).
|*
|* At the moment the session transfer the software from one environment to
|* another.
|* With few modifications it is possible to transfer the software to a batch
|* of hosts simultaneously.
|*
|* Export and Import of the software can be forced on VRC which are not the one
|* of the customization part.
|*
|* Using PMC for the same scope was not possible far the following reasons:
|* - Too many restrictions
|* - Too cumbersome
|* - Too many rigidity
|* - Going from customization part to PMC solution needed a session
|* - With the PMC it is not possible to have different origin VRC in the
|* same solution
|*
|* This ambitious project uses the export logic based on customization part
|* of the famous ttiexdeliverp.
|*
|* The two most important features of the PMC (rollback and log) are present.
|* An optional backup dump is written in the directory $BSE/install/backup.
|* A log file with all the activities done is present "$BSE/log/log.install"
|*
|* The session is platform and configuration independent (or at least it should
|* be so...), hence it works also on NT using the BW services (ottdllbw).
|*
|* Since it is nearly impossible (any volunteer?) from Baan code to know
|* where the BW client files are, if you want to use the BW, and you want
|* to tranfer files on a remote host, you must have the files BWC associated
|* to the executable BW.EXE instead of the executable BECS.EXE.
|* In alternative, you can install on your PC the BW client for iBaanERP.
|* In this latter case it seems that the BECS handle it correctly...a bit
|* disgusting I know, but the ottdllbw functions are very limited!
|* Morover a quite recent BW version is needed (>= 0.48).
|*
|* To save bandwidth (specially useful when you are connected trough a modem
|* line) and you are using a UNIX server (do you really use NT???) with the r*
|* services enabled, the files can be transferred directly from the source host
|* to the destination host with the UNIX command rcp.
|*
|* Please note that, in order to minimize the fingerprint of the installation
|* on a new environment (it is a tool, remember, nothing else) messages and
|* labels are hardcoded in english (this help too)... I know, this is a bit
|* hugly but in this way you only need to install in your system one session,
|* one form and one script on any existing VRC.
|*
|* You must also create the following directories:
|*
|* ${BSE}/install Root Directory
|* ./common Various file
|* ./import Used for imported dump
|* ./export Used for exporting dump
|* ./backup Used for backup dump
|*
|* The common directory must contain two foundamental files:
|*
|* ShellExec.exe On Windows 95 box I need a small VBS
|* exe which runs application files based
|* on their association mechanism.
|*
|* master.bwc A master bwc file for the BW client
|*
|*
|******************************************************************************