Knowledge Base
cancel
Showing results for 
Search instead for 
Did you mean: 

How to configure SevenReports on a Remote Client or for Third Party Access

Issue

Can a Remote Client run I/NET Reports (SevenReports) from the I/NET Seven Server's SQL database?

Environment

I/NET Seven

SevenReports

Cause

In a Remote Client configuration the local SQL database is not used, and is typically blank.  To enable the local SevenReports engine to connect to the I/NET Server the ODBC data source must be configured to successfully connect to this server workstation. 

Resolution

To download more detail instructions please Click Here

Remote Client:

The following procedures describe how to configure the local I/NET Seven ODBC data source to communicate with the SQL server on another I/NET Seven workstation.


  1. Open the ODBC Data Source Administrator editor. (Control Panel / Administrative Tools)
  2. In the ODBC Data Source Administrator editor, click the System DNS tab, highlight the Seven ODBC data source and click Configure....
  3. In the DSN Configuration editor, use the Server field to specify the name of the I/NET Seven workstation and SQL Server instance that will be used as the server for this workstation.
  4. Click Next and enter the third-party Login ID and Password appropriate for the selected server. If the server is using the default settings for these parameters, the Login ID will be INetThirdParty and the Password will be passinetdb3p_SE.
  5. Click Next two more times and then click Finish.
  6. In the resulting window, review the summary of settings. If necessary, you can use the Back button to return to previous screens and make changes to the configuration.
  7. Click the Test Data Source... button to test the connection.
  8. Click OK to close the Test Results window.
  9. Click OK to close the DSN Configuration editor.
  10. Click OK to close the ODBC Data Source Administrator editor.

Third-Party Applications

Use the following procedures to create a new ODBC data source on a PC that is not running I/NET Seven. The purpose of this task is to allow local third-party applications to communicate with I/NET Seven running on another PC.

  1. Open the ODBC Data Source Administrator editor. (Control Panel / Administrative Tools)
  2. In the ODBC Data Source Administrator editor, click the System DNS tab and click Add....
  3. In the resulting window, scroll through the list and highlight the driver appropriate for the version of SQL Server installed on your PC: 
    - For MSDE/SQL Server 2000, select SQL Server.
    - For SQL Server 2005, select SQL Native Client.
    - For SQL Server 2008, select SQL Native Client 10.
  4. Click the Finish button.
  5. In the DSN Configuration editor, make the following settings: 
    - Define the data source Name as “Seven ODBC”. 
    - Define the Description as “ODBC Connection for I/NET Seven”. 
    - Use the Server field to specify the name of the I/NET Seven workstation that will be used as the SQL server for applications on this PC.
  6. Click Next and make the following settings: 
    - Select the With SQL Server authentication using a login ID and password entered by the user option.
    - Near the bottom of the editor, enter the third-party Login ID and Password appropriate for the selected server. If the server is using the default settings for these parameters, the Login ID will be INetThirdParty and the Password will be PassInetDb3p_SE.
  7. Click Next two more times and then click Finish.
  8. In the resulting window, review the summary of settings. If necessary, you can use the Back button to return to previous screens and make changes to the configuration.
  9. Click the Test Data Source... button to test the connection.
  10. Click OK to close the Test Results window.
  11. Click OK to close the DSN Configuration editor.
  12. Verify that the new ODBC data source has been added to the list of System Data Sources.
  13. Click OK to close the ODBC Data Source Administrator editor.

More detailed information is also available on Extranet in TCON301 Chapter 2 - ODBC Driver Interface section.

Tags (1)
Labels (1)
Version history
Revision #:
2 of 2
Last update:
‎2018-09-10 12:56 PM
Updated by:
 
Contributors