The eG Installation Guide - eG Innovations

Installing and Configuring on Unix
Note:
If MS SQL Server 2008 is being used as the eG backend, then ensure that the password
provided for the eG database user is a strong password. Strong passwords are defined by the
following parameters:
7. The configuration process next prompts the user to specify if the database user name specified
has already been created.
Does the 'egurkha' account already exist y/n? [n] :
If the user response is y here, then the following message will appear:
User 'egurkha' exists! Continuing ...
If the user response is n, then the configuration process prompts for the user’s consent to create
the database user account.
Do you want to create the 'egurkha' account now y/n? [y] :
Enter y to invoke the following:
New user creation requires database administrator privileges.
Enter the DBA user name (eg., sa or in the form domain/dbaccount) :
Enter the DBA password :
Note:
Has at least 6 characters
Does not contain "Administrator" or "Admin"
Contains characters from three of the following categories:
1. Uppercase letters (A, B, C, and so on)
2. Lowercase letters (a, b, c, and so on)
3. Numbers (0, 1, 2, and so on)
4. Non-alphanumeric characters (#, &, ~, and so on)
Does not contain the corresponding username
For instance, if the name of the special database user is egdb, then the password that you set
for this user should be a strong password such as, db123$%#@.
Note that without a ‘strong password’, the eG manager installation will fail.
Note:
Before attempting to set an existing database user name as the eG database user, make sure
that dbowner privileges are granted to such a user.
If the specified DBA user has an empty password, then type null as the DBA password and
proceed.
32