Before the software can be validated, two codes must have been obtained from Baan when the order was accepted. The validation procedure cannot take place without these codes:
· The customer code
The code under which the customer is known at Baan.
· The license code
The code under which the customer’s system configuration is known at Baan.
1 Maintain Requested System Configuration(ttiex3100m000)
The procedure begins by entering the commercial functions per package, standard or customized, which will be used after the validation. This is done in the Maintain Requested System Configuration (ttiex3100m000) session. In addition to the names of the commercial functions, the period for which they will be validated must be entered.
2 Maintain Requested System Configuration (Tools) (ttiex3101m000)
Because BAAN IV Tools is different from the other packages, the commercial functions of this package are entered independently in the Maintain Requested System Configuration (Tools) (ttiex3101m000) session. The commercial functions of BAAN IV Tools include user interfaces and database drivers. For each commercial function, the period for which it is validated is entered. For user interfaces, the maximum number of users allowed to use the packages concurrently is also specified.
3 Print Requested System Configuration (ttiex3400m000)
Next, a report of the requested system configuration is printed and sent to Baan. For this purpose, the Print Requested System Configuration (ttiex3400m000) session is used. In this session, customer code, license code, and organization name of the customer are entered. The report will contain the options that were entered in the previous sessions as well as a security code generated on the basis of the data entered in this session. After having been printed, the report is sent to Baan.
4 Maintain Security Code/Validation Key (ttiex3102m000)
On the basis of the security code and the requested system configuration, Baan will generate two more codes: a validation key for BAAN IV Tools and a validation key for standard software. Software distributors who have developed their own modules or customizations, could issue a validation key for these modules or customizations.
The security code and the validation keys are entered in the Maintain Security Code/Validation Key (ttiex3102m000) session. Customer code, license code, and organization name are also entered at this point. It is imperative that the codes are entered correctly, since any error will cause the software to become inoperable.
5 Validate Tools Set (ttiex3220m000)
Next, the actual validation process is started by means of the Validate Tools Set (ttiex3220m000) session. This session will create a /.brand directory containing the .brand6.1 file. Normal UNIX users are not authorized to do this, and it is therefore essential to be logged in as root in UNIX.
The .brand6.1 file may never be amended, copied, removed, or moved, because the software will immediately become inoperable. Also, it is not allowed to overwrite this file when the system is restored by means of a back-up, as this will also make the software inoperable immediately.
6 Configure Application (ttiex3225m000)
Before the software can be used, the environments have to be patched in the Configure Application (ttiex3225m000) session. Patching the objects must be the only BAAN IV process running which means that no user, including the root, can be logged into BAAN IV.
Once the validation procedure is completed, it is possible to set the parameters, etc. to initialize the BAAN IV application.
Baan-ERP-Validation-Procedure
14 Tuesday Aug 2012
Posted Baan ERP
in