Difference between revisions of "Freeside:1.7:Documentation:Accounting:CrystalReports"

From Freeside
Jump to: navigation, search
(Configure the Freeside backend)
 
(3 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
<code>createuser -P reports</code>
 
<code>createuser -P reports</code>
  
* Grant the new PostgreSQL user read-only access to the freeside tables
+
* Grant the new PostgreSQL user read-only access to the freeside tables.  A dozen or so <code>"relation "xxx" does not exist</code> errors are to be expected, as long as the bulk of the commands execute.
 
<code>freeside/bin/pg-readonly ''freeside_username'' reports</code>
 
<code>freeside/bin/pg-readonly ''freeside_username'' reports</code>
  
* Allow the new PostgreSQL user access from the IP which will be running Crystal Reports.  Edit <code>pg_hba.conf</code> and add an access line, for example, for 192.0.2.56:
+
* Allow the new PostgreSQL user access from the IP which will be running Crystal Reports.  Edit <code>pg_hba.conf</code> and add an access line somewhere before <code>#reject all other connection attempts</code>.  For example, for 192.0.2.56:
 
<pre>
 
<pre>
 
# TYPE  DATABASE  USER    IP-ADDRESS  IP-MASK          METHOD
 
# TYPE  DATABASE  USER    IP-ADDRESS  IP-MASK          METHOD

Latest revision as of 14:16, 3 January 2007

Configuring Crystal Reports to access Freeside

Configure the Freeside backend

  • Add a PostgreSQL user and set a password

createuser -P reports

  • Grant the new PostgreSQL user read-only access to the freeside tables. A dozen or so "relation "xxx" does not exist errors are to be expected, as long as the bulk of the commands execute.

freeside/bin/pg-readonly freeside_username reports

  • Allow the new PostgreSQL user access from the IP which will be running Crystal Reports. Edit pg_hba.conf and add an access line somewhere before #reject all other connection attempts. For example, for 192.0.2.56:
# TYPE  DATABASE  USER     IP-ADDRESS  IP-MASK          METHOD
host    freeside  reports  192.0.2.56  255.255.255.255  md5
  • Restart PostgreSQL

Configure the Crysal Reports client

  • Use the PostgreSQL ANSI driver
  • Use the username (i.e. reports) and password you configured on the backend.