Go to documentation repository
Page History
External event protocol is created with the help of the idb.exe utility.
Note | ||
---|---|---|
| ||
If Time &and Attendance module is in use (the module is a part of ACFA - Intellect subsystem) use the RemoteProtocolConnector utility to extract event protocol into a separate database – see Intellect Web Report System. User Guide (the most relevant recent version of this document is available in AxxonSoft documentation repository). External event protocol is created with the help of the |
Info | ||
---|---|---|
| ||
To operate the Report System, which is a part of base Intellect, the method of extracting the event protocol into a separate database is used. The method is described in this section, i.e. using the idb.exe utility. Configuration of the connection to such protocol DB is required in the Report System, which is a part of base Intellect (see Connecting to the Events Log (PROTOCOL table)). |
It is necessary to create the protocol database The protocol database is to be created beforehand with the help of of the MS SQL Server program. For thisDo the following:
- Open Microsoft SQL Server Management Studio Express;.
- Select the Databases;.
- Right-click and select the New Database…;
- Specify the protocol database name in the Database name line in the New Database dialog box;.
- To create a new protocol database, click the OK ;button.
- Shut down Microsoft SQL Server Management Studio Express by clicking the the Close button in the upper right corner of the dialog box.
As a result, the protocol database is created.
To enable the external event protocol, do the following:
- Run the idb.exe utility (see Running and shutting - down the utility section).
- Select the Protocol administration database in from the Select source database: dropdown drop-down list.
- To enable the Protocol database, set the Use checkbox (1).
- As a result, the Build Configure button becomes active (2). To connect to the Protocol database, click the Build Configure button.
- As a result, the Data link properties dialog box appears. Go to the Provider tab.
- Select the Microsoft OLE DB Provider for SQL Server item in from the OLE DB Provider(s) list (1).
- Click the Next button (2).
- There is an auto switch You will be automatically redirected to the Connection tab.
- Do the following in the Connection tab:
- Select a server name in from the Select or enter a server name dropdown drop-down list (1).
- Specify the user name in the User name field and specify the password in the Password field (2).
- Set the Allow saving password checkbox (3).
- Go to the All tab.
- In the Persist Security Info field, set the True value. This is necessary to correctly save the user password.
Info title Note Each time you change the server connection parameters, you must set the Persist Security Info field value to True.
Select the protocol database in the Select the database on the server dropdown list drop-down list (4).
Click the Test connection button (5).
If If the connection to MS SQL server succededServer is successfully established, then the Test connection succeeded message appears.
Click the OK button in the message box; the . The box closes automatically.
- Select a server name in from the Select or enter a server name dropdown drop-down list (1).
- Select the dbi file. Click the button next to the Select dbi-file information field.
- As a result, the Open dialog box appears.
- Select Select the database structure file – C:\Program Files\Intellect\intellect.dbi.dbi file
- To update Click the Update database button to update the database in accordance with the intellect.dbi file specified in the Select dbi-file field, click the Update database button.
- As a result, database updating will start. Information about this process is displayed in the Protocol table.
- Database is updated, when there is the Database updating Updating is finishedcompleted! message in the Protocol table.
- To save INTELLECT™ Intellect connection parameters to the Protocol database, click the OK button. As a result, the dialog box closes automatically.
External event protocol is created and enabledconnected.