Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Access Manager module loads module gets the components objects required for its proper operation directly from the SQL Server database of the Intellect Server.  This This causes some problems issues for the module operation in distributed architecturessystems, based on a variety of combinations between the Intellect Server, the Remote Admin WorkstationAdministrator's workstation, and theRemote Client (see Configuration of distributed architecture).

In particular, attempting when you try to run the Access Manager module remotely from a computer with a Client installation leads to inability of the Remote Client, the Access Manager to will not display the objects, which are loaded from the database of the Intellect Server DB, e.g. the lists of users and departments. In order to circumvent eliminate this issue, when configuring the distributed architecture administrator is recommended to system, the administrator should do the following:

  1. On the computer with a Client installationthe installed Remote Client:
    1. Install the OLE DB Driver for SQL SERVER driver by selecting the msoledbsql file that is located in the redist folder in the installation directory according to the language and bitness of the Remote Client, or fully install the SQL Server database server. Thus, the SQL Server on a the computer with a the installed Remote Client installation will be able to connect to the SQL Server on the computer with an Intellect the Intellect Server installation.
    2. Ensure the SQL Server authentication through the base sa account.
    3. Ensure uninterrupted connection of the SQL Server on the computer with a the installed Remote Client installation to the SQL Server on the computer with the the installed Intellect Server installation.

  2. On the computer with an Intellect Server installation and the installed Intellect Server and the Access Manager module:
    1. Configure the SQL Server to allow remote connections.
    2. Ensure the SQL Server authentication through the base base sa account.
    3. Configure the Intellect Server connection to its database using the idb.exe utility. For this, you must perform do the following actions:
      1. Run the utility from the Intellect Server installation directory.
      2. In the utility interface, click the Configure button (1). The database connection window will open.
      3. In the Select or enter a server name field (2), type enter the name or the IP address of the SQL server used to for database management (2).

        Note
        titleNote

        Please note Note that you must specify the explicit name or the IP address of the machine on which the database is installed. A the The format (local)\ SQLEXPRESS would be incorrect.


      4. In the Enter the information to log on to the server settings section (3), check select the Use a specific user name and password radio button. In the User name field enter sa. In the Password field, enter the password for the sa user. (3)

        Note
        titleNote

        Note that accounts user names other than sa are not allowed.


      5. Set the Allow saving password checkbox (4).

        Note
        titleNote

        This step is also mandatory.


      6. Set Select the Select the database on the server selector radio button and choose select intellect from  from the drop-down list (5).
      7. Click the OK button to save the connection settings parameters (6). The parameters will be displayed in the Connection string field in  field (7) in the idb.exe (7)utility interface.
      8. Click OK in the OK button (8) in the idb.exe  to utility interface to save the changes.

Setting up Configuring the proper correct operation of the Access Manager module in a distributed architecture system is complete.