AVEVA NET

Reporting - Installation Guide

AVEVA Solutions Ltd

Disclaimer
Information of a technical nature, and particulars of the product and its use, is given by AVEVA
Solutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim
any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.

Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person or
entity for any actions, claims, loss or damage arising from the use or possession of any information,
particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every
part of it (including source code, object code, any data contained in it, the manual and any other
documentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in
this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval
system, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where such
permission is granted, it expressly requires that this Disclaimer and Copyright notice is prominently
displayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any material
or electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also not
reverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of the
product described in this publication may be incorporated into any third-party software, product,
machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted by
law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal
prosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance with
the terms and conditions of the respective licence agreements, and in accordance with the relevant
User Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.

First published September 2008

© AVEVA Solutions Ltd, and its subsidiaries 2008

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

Trademarks
AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised
use of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or its
subsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product, its name or
logo belongs to its respective owner.
 AVEVA NET Reporting - Installation Guide

AVEVA NET Reporting - Installation Guide

Contents Page

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1
How this Guide is Organised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
AVEVA NET Reporting Common Installation Steps . . . . . . . . . . . . . . . . . . . . . . 1:2
Deploying to a Native Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:2
Deployment of AVEVA NET Reporting to the Native Report Server . . . . . . . . . . . . . . . . . . 1:3
Connecting the AVEVA NET Report Model to the AVEVA NET Data Source . . . . . . . . . . . 1:5
Deploy the Design Document Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:7
Parts List Reports and Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:8
Modify the Sample Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:8
Deploy the Parts List Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:8

Deploying to a Deep Integrated SSRS SharePoint Site . . . . . . . . . . 2:1

Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3
Creating a SharePoint Report Center Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4
Enable the Report Builder Model and Report Data Source Data Connection Types
2:4
Create the AVEVANETDataSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5
Upload the AVEVANETReportModel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6
Connecting the AVEVANETReportModel to the AVEVANETDataSource . . . . . . . . . . . . . . 2:7
Preparing to Upload the Sample Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:10
Uploading the RDL Parts Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:11
Connecting Reports to the AVEVANETReportModel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:11
Uploading the Design Document Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:11

© 2008 AVEVA Solutions Ltd i 4.3.SP1

 AVEVA NET Reporting - Installation Guide

Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:1
Potential Report and Model Deployment Issues and their Solutions . . . . . . . . A:1
Data Connection has been Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:1
Setting up Reporting Services for Deep Integration with SharePoint. . . . . . . . . . . . . . . . . . A:1
Deploying Report Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:1
Unable to show Sub Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:2
GRANT PERMISSIONS on SQL Functions and Views . . . . . . . . . . . . . . . . . . . . A:3
Preparing the Sample Templates for Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:4
OneClickInstallDeploy Installation and Deployment Procedure . . . . . . . . . . . . A:5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:5
One Click Create DataSource and Deploy Report Model . . . . . . . . . . . . . . . . . . . . . . . . . . A:5
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:6
Create DataSource and Deploy Report Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:7
Check Data Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:8
Deploy Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A:9

© 2008 AVEVA Solutions Ltd ii 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Introduction

1 Introduction

AVEVA NET Reporting is a facility which utilizes Microsoft SQL Server Reporting Services
(SSRS) to produce custom reports of data held within AVEVA NET, and includes
deployment methods for all AVEVA NET Standard Reports, AVEVA NET Standard Parts
Report Templates, AVEVA NET Data Source Connection and the AVEVA NET Report
Model.
AVEVA NET Reporting deploys with four example reports.
• Design Document Summary Report
• Parts List Report
• Summarised Bill of Materials Report
• Multi-level Indented Bill of Materials Report
Once deployed, with a small amount of customization for local settings these reports are
ready to use out of the box, but can be used as templates or further customized to change to
the content and presentation of the report. Creating and using reports is described in the
AVEVA NET Reporting Creation and User Guide.
AVEVA NET Reporting can be deployed in two different ways.
• To a Native Report Server
• To a Deep Integrated SSRS SharePoint Site
When choosing which variant of AVEVA NET Reporting you will install, you need to consider
if you want to use SharePoint Deep integration with SSRS or not. AVEVA recommends
Deep Integration for SharePoint as the standard for AVEVA NET Reporting, however you
may choose in the short term to reuse your existing Native Reporting Services installation.
In that case we also recommend keeping the Native Report Server separate from the
SharePoint Site Server, in order to make it easier to switch to Deep Integration at some
point in the future.
This document describes the installation and setup procedures for both choices of
deployment.

© 2008 AVEVA Solutions Ltd 1:1 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Introduction

1.1 How this Guide is Organised

This guide is divided into chapters and appendices, as follows:

Introduction A introduction to AVEVA NET 4.3 Reporting.

Deploying to a Native Report Server Describes deploying AVEVA NET 4.3 Reporting to a
Native Report Server.

Deploying to a Deep Integrated SSRS Describes deploying AVEVA NET 4.3 Reporting to
SharePoint Site Deep Integrated SSRS SharePoint Site.

Appendices:

Potential Report and Model Details common problems that can be encountered
Deployment Issues and their during installation.
Solutions

GRANT PERMISSIONS on SQL Explains what permissions must be set before

Functions and Views AVEVA NET 4.3 Reporting can run correctly.

Preparing the Sample Templates Describes how to prepare the sample templates
for Use supplied with AVEVA NET 4.3 Reporting.

OneClickInstallDeploy Installation Describes the OnceClickInstallDeploy process.

and Deployment Procedure

1.2 AVEVA NET Reporting Common Installation Steps

This document assumes that the AVEVA NET Reporting installer is run on the machine
hosting the SQL Server Reporting Services (be it Native or Deep Integrated SSRS
SharePoint). However, AVEVA NET Reporting may be installed on any machine in the
network with access to the AVEVA NET SQL Server Database and the SQL Server
Reporting Services.
From the AVEVA NET install page, select AVEVA NET Reporting. The default installation
path is C:\Program Files\AVEVA\NET\Reporting, but this may be changed to your preferred
location which may be on a shared network drive. This path will now be referred to as
<INSTALLATIONDIR>.

1.3 Deploying to a Native Report Server

1.3.1 Prerequisites
The following software must be installed
• Microsoft SQL Server 2005 SP2 with Microsoft SQL Server Reporting Services (SSRS)
• Internet Information Services (IIS)
If not already installed, SSRS can be installed as part of the Microsoft SQL Server
installation.

© 2008 AVEVA Solutions Ltd 1:2 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Introduction

1.3.2 Deployment of AVEVA NET Reporting to the Native Report Server

After extraction you will find the following subfolders within the folder:
<INSTALLATIONDIR>\SSRS\Deployment:
DataSource
Model
Reports
These folders contain the scripts used to deploy the AVEVA NET DataSource connection,
the AVEVA NET Data Model and AVEVA NET Reports.

• Simple Script File Edits

It is necessary to update the report data files to reflect your AVEVA NET database server
and database name.
1. Open the following file in a text editor such as Notepad:
<INSTALLATIONDIR>\SSRS\Deployment\DataSource\Data
Sources\AVEVANetV1.rds.rss
2. Modify the definition.ConnectString to replace the tag <DATASERVER> with the name
of the SQL Server hosting your AVEVA NET SQL Database.
Note: <DATASERVER> refers to the SQL Server which may not always necessarily be the
same as the Report Server

3. Replace the tag <DATABASENAME> with the name of the SQL Database which
relates to the AVEVA NET Community you wish to report against.

• Create Folders within the Report Server

Folders must be created within the Report Server which will be used for deployment of the
AVEVA NET DataSource connection, the AVEVA NET Data Model and the AVEVA NET
Sample Reports.
1. To do this first connect to the Report Manager, usually found at http://
<REPORTSERVER>/reports, where <REPORTSERVER> is the name of your server
running SSRS, e.g. SERVER002
2. Create the following folders:
• Data Sources
• Models
• DesignDocumentSummary
• AVEVA NET Parts List Reports

• Deploy DataSource Connection

The connection to the DataSource can now be deployed. Ensure that the following steps
are carried out a user with write permissions to the Report Server.
1. Run a DOS Command Prompt and change directory to
<INSTALLATIONDIR>\SSRS\Deployment\DataSource
2. Execute
RSDataSource.cmd <REPORTSERVER>
Replacing tag <REPORTSERVER> with the report server host name
3. Open the Report Manager. This is usually located at
http://<REPORTSERVER>/reports

© 2008 AVEVA Solutions Ltd 1:3 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Introduction

4. Check that the AVEVANetDataSource Datasource is created correctly into the

Data Sources folder, and check the log files within the <INSTALLATIONDIR>\SSRS\
Deployment\DataSource directory for any errors or warnings.

• Deploy AVEVA NET Data Model

The AVEVA NET Data Model contains the logical data model for objects which reside in the
AVEVA NET DataSource. This can be used rather than direct SQL when creating new
reports.
1. From the Command Prompt change directory to
<INSTALLATIONDIR>\SSRS\Deployment\Model
2. Execute
RSModel.cmd <REPORTSERVER>
Replacing tag <REPORTSERVER> with your report server name
3. Open the Report Manager.
4. Check that the AVEVANetReportModel Model is created correctly into the Models
folder, and check the log files within the <INSTALLATIONDIR>\SSRS\Deployment\
Model directory for any errors or warnings.
Note: In fact you should expect the following error message within the log file

Running script ".\Models\AVEVANetReportModel.smdl.rss"

The Relation property of the Role 'Document' refers to the
Target end of the Relation 'view_vitem_grp-baseline_objects',
which is not bound to a set of uniquely constrained columns
for the Table 'dbo_baseline_objects'. Roles with Cardinality
of One or OptionalOne require relations bound to uniquely
constrained columns of the table.
Unhandled exception:
Object reference not set to an instance of an object.
Although in fact there are 16 errors which you will only see in the event of making changes
to the Report Model say for Security Filters or similar, see screen shot below.

© 2008 AVEVA Solutions Ltd 1:4 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Introduction

1.3.3 Connecting the AVEVA NET Report Model to the AVEVA NET Data
Source
You must next set the Data Source connection for the AVEVA NET Report Model to the
AVEVANetDataSource DataSource;
1. In the Report Manager open the Models folder.
2. Open AVEVANETReportModel.

© 2008 AVEVA Solutions Ltd 1:5 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Introduction

3. Click Data Sources and then the Browse button.

4. Choose the AVEVANETDataSource DataSource within the Data Sources folder and
click OK.

© 2008 AVEVA Solutions Ltd 1:6 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Introduction

5. Then click Apply.

1.3.4 Deploy the Design Document Summary Report

1. Run a DOS Command Prompt and change directory to
<INSTALLATIONDIR>\SSRS\Deployment\Reports.
2. Execute
RSDemoReport.cmd <REPORTSERVER>
Replacing tag <REPORTSERVER> with your report server name.
3. Open the Report Manager.
4. Check that the DesignDocumentSummary Report is created correctly into the
DesignDocumentSummary folder, and check the log files within the
<INSTALLATIONDIR>\SSRS\Deployment\Reports directory for any errors or warnings.
You should only see a single report in the folder. Clicking the Show Details button will also
show the sub reports used by this report.

Before attempting to Execute this Report

• Check User Permissions against the DataSource
The default deployment assumes Windows Integrated Security connections to the
database, and you may be able to use this under most circumstances, however this does
rely on your security/permissions/access control settings and your company policy on
database connections and access control.
If you switch to using Credentials stored securely in the report server, before running the
report, you will need to amend, or check and re-enter, the database server and database
name and Username and password within the AVEVANetDataSource located in the Data
Sources folder of the Report Manager.
You will also have to consider who are to be the users of the reports and you will need to
add them into the SQL Database as data readers. They also require execute permissions
on SQL functions used by the reports. To explicitly grant permissions to execute and select
from the functions See GRANT PERMISSIONS on SQL Functions and Views (contact your
SQL Database Administrator or equivalent for assistance with this).
Once you have granted permissions, you can then try running the
DesignDocumentSummary report:
1. Open the DesignDocumentSummary folder in the Report Manager.
2. Click DesignDocumentSummary.

© 2008 AVEVA Solutions Ltd 1:7 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Introduction

1.3.5 Parts List Reports and Templates

The Parts List Reports are included as both stand alone Report Files, which are deployed in
a similar way to the Design Document Report Summary report, but also as Templates to
allow easy modification or customization as required.

1.3.6 Modify the Sample Templates

The sample reports have been provided as Report Templates (.RDL files) in the folder
<INSTALLATIONDIR>\SSRS\RDL Templates. These can be used with the existing reports
without risking the integrity of the original samples.
The supplied RDL Templates all link to an image file intended to display your Company
Logo, this must be updated to reflect your server location before use. Please refer to
Preparing the Sample Templates for Use for more detailed instructions.

1.3.7 Deploy the Parts List Reports

1. Copy the modified RDL Template files to
<INSTALLATIONDIR>/SSRS/Deployment/reports/AVEVA NET Parts List Reports.
2. Run a DOS Command Prompt and change directory to
<INSTALLATIONDIR>\SSRS\Deployment\Reports.
3. Execute
RSPartsListReports.cmd <REPORTSERVER>
Replacing tag <REPORTSERVER> with your report server name.
4. Open the Report Manager.
5. Check that the following Report are created correctly into the AVEVA NET Parts List
Reports folder:
• AVEVAIndentedBOM
• AVEVASingleLevelPartsList
• AVEVASummarisedBOM.
6. Check the log files within the <INSTALLATIONDIR>\SSRS\Deployment\Reports
directory for any errors or warnings.
You will also have to consider who are to be the users of the reports and you will need to
add them into the SQL Database as data readers. They also require execute permissions
on SQL functions used by the reports. To explicitly grant permissions to execute and select
from the functions. See GRANT PERMISSIONS on SQL Functions and Views (contact your
SQL Database Administrator or equivalent for assistance with this).
Once suitable permissions have been granted run the reports:
1. Open the AVEVA NET Parts List Reports folder in the Report Manager.
2. Click on each report to run it.

© 2008 AVEVA Solutions Ltd 1:8 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

2 Deploying to a Deep Integrated SSRS

SharePoint Site

Reporting Services configured for SharePoint 3.0 Integration are required. Please refer to
the Microsoft documentation for detailed instructions:
Configuring Reporting Services for SharePoint 3.0 Integration
http://technet.microsoft.com/en-us/library/bb283321.aspx
A variety of deployment scenarios are supported: either deploying to a single server or a
distributed deployment across multiple computers.
The diagrams below illustrate two possibilities:
1. Single Server used for SharePoint and SQL Server Reporting Services

Note: Exact locations of AVEVA NET components are dependent on deployment.

The Navigation Portal may also instead be deployed to a different server than the
Report Server, or other AVEVA NET components may be deployed to the Report
Server

The following software must be installed on the Report Server:

• Microsoft SQL Server 2005 SP2 with Microsoft SQL Server Reporting Services (SSRS)
Note: Service Pack 2 adds essential capabilities for SharePoint integration

© 2008 AVEVA Solutions Ltd 2:1 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

• Security Update for SQL Server 2005 Service Pack 2 (KB954606) (build 9.00.3073.00)
OR Security Update for SQL Server 2005 Service Pack 2 (KB954607) (build 9.00.
3282.00)
• Microsoft .NET Framework 3.0 with ASP.NET 2.0 enabled
• Microsoft Office SharePoint Server (MOSS) 2007
• Report Center templates enabled in MOSS
• Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint
Technologies
For detailed setup instructions see: How to: Configure SharePoint Integration on a Stand-
alone Server http://msdn.microsoft.com/en-us/library/bb677368.aspx
2. Multiple Servers: Reporting Services installed on AVEVA NET Datasource Server,
separated from the SharePoint Server

The following software must be installed on the SharePoint Server

• Microsoft .NET Framework 3.0 with ASP.NET 2.0 enabled
• Microsoft Office SharePoint Server (MOSS) 2007 SP1
• Report Center templates enabled in MOSS
• Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint
Technologies
The following software must be installed on the AVEVA NET Datasource Server
• Microsoft SQL Server 2005 SP2 with Microsoft SQL Server Reporting Services (SSRS)

© 2008 AVEVA Solutions Ltd 2:2 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

Note: Note: Service Pack 2 adds essential capabilities for SharePoint integration

• Security Update for SQL Server 2005 Service Pack 2 (KB954606) (build 9.00.3073.00)
OR Security Update for SQL Server 2005 Service Pack 2 (KB954607) (build 9.00.
3282.00)
• Microsoft .NET Framework 3.0
• Microsoft Office SharePoint Server (MOSS) 2007 SP1 or Windows SharePoint
Services 3.0
Note: The SharePoint configuration and content databases can also be separated from the
SharePoint server, and other multiple machine configurations are possible. For
additional information and detailed setup instructions see: How to: Configure
SharePoint Integration on Multiple Servers http://msdn.microsoft.com/en-us/library/
bb677365.aspx

2.0.1 Resources
Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint
Technologies can be downloaded from here
http://www.microsoft.com/downloads/details.aspx?familyid=1E53F882-0C16-4847-B331-
132274AE8C84&displaylang=en
Installation instructions for the Microsoft SQL Server 2005 Reporting Services Add-in for
Microsoft SharePoint Technologies are given here:
http://technet.microsoft.com/en-us/library/bb839479.aspx
MOSS Service Pack 1 can be downloaded from here
http://www.microsoft.com/downloads/details.aspx?FamilyId=AD59175C-AD6A-4027-8C2F-
DB25322F791B&displaylang=en
Security Update for SQL Server 2005 Service Pack 2 (KB954606) (build 9.00.3073.00)
http://go.microsoft.com/fwlink/?LinkID=132078&clcid=0x409
Security Update for SQL Server 2005 Service Pack 2 (KB954607) (build 9.00. 3282.00)
http://go.microsoft.com/fwlink/?LinkID=132079&clcid=0x409

2.0.2 Further Reading

The following links give additional background information about the integration between
Reporting Services and SharePoint.
For an introduction to the SharePoint Report Center see:
http://office.microsoft.com/en-us/SharePointserver/
HA101741991033.aspx?pid=CH101785431033
For more background / overview of SSRS SharePoint Deep Integration technology /
architecture, see:
http://bloggingabout.net/blogs/mglaser/archive/2006/10/11/SQL-Server-2005-Service-Pack-
2-_2800_Integration-between-Reporting-Services-and-SharePoint-2007_2900_.aspx
How To Topics: Report Server in SharePoint Integrated Mode:
http://technet.microsoft.com/en-us/library/bb283321.aspx

© 2008 AVEVA Solutions Ltd 2:3 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

Configuration required for Reporting Services - How to: Create a Report Server Database
for SharePoint Integrated Mode
http://technet.microsoft.com/en-us/library/bb283151.aspx
Configuration required in the SharePoint Central Administration - How to: Configure the
Report Server Integration Feature in SharePoint Central Administration
http://msdn.microsoft.com/en-us/library/bb326213.aspx

2.0.3 Creating a SharePoint Report Center Site

In brief, to create a Report Center Site you must choose:
• Enable Enterprise features
from within SharePoint Central Administration -> Operations -> Upgrade and Migration. If
you have more than one site you may also need to choose
• Enable features on existing sites
You may alternatively enable the Reporting Services Feature in your chosen site collections
from their Site Settings -> Site Collection Features
• Report Server Integration Feature

2.1 Overview
In summary though specific to AVEVA NET Reporting, the manual deployment to a
SharePoint Report Center Site requires the following main steps:
1. Create the AVEVANETDataSource
2. Upload the AVEVANETReportModel
3. Connect the AVEVANETReportModel to the AVEVANETDataSource
4. Upload the Parts Report Masters
5. Upload the Design Doc Summary Report
6. Connect the Bill of Materials Reports to the AVEVANETDataSource
7. Connect all other Reports to the AVEVANETReportModel
The sections below will attempt to indicate exactly how to do this in the event of unfamiliarity
with Deep Integrated SSRS and SharePoint.

2.2 Enable the Report Builder Model and Report Data

Source Data Connection Types
1. Ensure Microsoft SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint
Technologies has been installed and configured for Deep Integration between your
SQL Server and SharePoint site.
2. Open http://<sharepoint_reportserver>/reports.
3. Open Data Connections.
4. From the menu select Settings > Data Connection Library Settings.
5. Choose Add from existing site content types.
6. Add Report Builder Model and Report Data Source.
7. Click OK.

© 2008 AVEVA Solutions Ltd 2:4 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

2.3 Create the AVEVANETDataSource

1. Open http://<sharepoint_reportserver>/reports.
2. Open Data Connections.
3. From the menu select New > Report Data Source.

4. Enter the details for connection to your AVEVA NET DataSource in the form presented
and click OK. An example is shown below:

© 2008 AVEVA Solutions Ltd 2:5 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

This is an example of the settings for setting up the standard datasource (note you will need
to use the exact name AVEVA NET DataSource as above), in this example ukched3138b is
the data server and the database is zodiactst. The format of the connection string is:
• Data Source=<SQL Server name>;Initial Catalog=<SQL Database name>
The stored credentials are those of an individual with sysadmin permissions on the
SQL Database, and you also need the correct password. Notice the two extra
checkboxes checked.
• Use as Windows credentials
• Set execution context to this account
In some circumstances you may simply be able to use Windows authentication
(integrated), however depending on your server configuration, and where you have
located your data server with respect to your SharePoint server will mean you will need
to use Stored Credentials as illustrated above.
Also select:
• Enable this data source.

2.3.1 Upload the AVEVANETReportModel

1. Open http://<sharepoint_reportserver>/reports.
2. Open Data Connections.
3. From the menu select Upload > Upload Document.

4. Select Browse and open <INSTALLDIR>\SSRS\Deployment\model\Models.

5. Select AVEVANETReportModel and click Open.

© 2008 AVEVA Solutions Ltd 2:6 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

6. Click OK to upload the Report Model.

2.3.2 Connecting the AVEVANETReportModel to the AVEVANETDataSource

You will now need to connect the AVEVANETReportModel to the AVEVANETDataSource.

Note: The steps to connect three of the Bill of Materials Parts Reports to the
AVEVANETDataSource are identical to this.

1. Hover over the Report Model (or indeed the Bill of Materials Reports) and select the
drop down menu Manage Data Sources.

© 2008 AVEVA Solutions Ltd 2:7 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

2. Select the AVEVANetV1 DataSource.

3. To select the Data Source Link, navigate to the AVEVANetDataSource by clicking on

the button.

© 2008 AVEVA Solutions Ltd 2:8 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

4. You may need to select Up to navigate up a folder. Then select the Data Connections
folder.

5. Select the AVEVANETDataSource which was previously created and click OK.

© 2008 AVEVA Solutions Ltd 2:9 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

6. Click Close to complete the connection.

2.3.3 Preparing to Upload the Sample Reports

For detailed instructions on Uploading Reports to SharePoint Integrated mode please refer
to http://technet.microsoft.com/en-us/library/bb326283.aspx.
The sample reports have been provided as Report Templates (.RDL files) in the
<INSTALLATIONDIR>\SSRS\RDL Templates. These can be used to modify and 'play' with
the existing reports, without risking the integrity of the original samples.
The supplied RDL Templates all refer to an image file intended to display your Company
Logo which must be updated to reflect your server location before use. Please refer to
Appendix 3 Preparing the Sample Templates for Use for more detailed instructions.

© 2008 AVEVA Solutions Ltd 2:10 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

The standard Deployment for AVEVA NET Reporting creates two sub folders under the
Reports (Report Centre) folder of the Deep Integrated Site, one for Parts that is called Parts
Reports and one for Design Documents that is called Design Doc Reports.

2.3.4 Uploading the RDL Parts Reports

Upload the modified templates for Parts into the Parts Reports folder.
The following reports consist of complex queries implemented directly in SQL so bypass the
AVEVANETReportModel and connect directly to the AVEVANETDataSource.
• Indented Bill of Materials Report
• Summarized Bill of Materials Report
• Item ID version of the Bill of Materials Report
Please refer to Connecting the AVEVANETReportModel to the AVEVANETDataSource for
connecting these reports to the AVEVA NET DataSource.
The remaining Parts List Reports are implemented using the AVEVA NET Report Model, so
must be connected to the AVEVANETReportModel, described in the next section.

2.3.5 Connecting Reports to the AVEVANETReportModel

This is a virtually identical process to connecting to the AVEVANETDataSource as
described in Connecting the AVEVANETReportModel to the AVEVANETDataSource, except
selecting the AVEVANETReportModel instead of the AVEVANETDataSource in this case.

2.3.6 Uploading the Design Document Summary Report

The Design Document Summary Report contains one main Report named
DesignDocumentSummary and several sub reports.
Upload the all the Design Document Summary Reports and Sub Reports into the Design
Doc Reports folder.
Each of these sub reports along with the main report need to be connected to the
AVEVANETReportModel in the same way as other Reports are connected. Please refer to
Connecting the AVEVANETReportModel to the AVEVANETDataSource for instructions.
You will need to ensure that you do not miss out any of them otherwise they will show on the
Report as SubReport Not found.

© 2008 AVEVA Solutions Ltd 2:11 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Deploying to a Deep Integrated SSRS SharePoint Site

© 2008 AVEVA Solutions Ltd 2:12 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

A Appendices

A.1 Potential Report and Model Deployment Issues and

their Solutions

A.1.1 Data Connection has been Deleted

• If when attempting to run a report which uses a Report Model, you get an error referring
to data connection information has been deleted.
The report server cannot process the report. The data source connection information
has been deleted. (rsInvalidDataSourceReference)
Check the connection between the Report Model AVEVANETReportModel and it's
Data Source AVEVANETDataSource, as outlined in #Reconnecting Report Model to
Data Source above and reconnect as normal.

A.1.2 Setting up Reporting Services for Deep Integration with SharePoint

• If when Setting up Reporting Services onto a server which has SharePoint on, it fails to
properly complete the set up, and does not really give much clues as to why.
Solution is to use port 81 for the <ReportServer> reference i.e. SERVER002:81 as
SharePoint seems to 'steal' the default port.

A.1.3 Deploying Report Model

• If when you come to deploy a model onto a Report Server (RSModel.cmd) it fails with a
useless unhandled exception error, and you have no clues as to what needs to be done
to solve it.
Solution is to insert this extra line into web.config. ie:
<httpRuntime maxRequestLength="8192" />
into WEB.CONFIG within C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\
CONFIG or equivalent
Example here showing inserted line at end of file or towards the end as extract:
<transformers>
<add name="RowToFieldTransformer"
type="System.Web.UI.WebControls.WebParts.RowToFieldTransformer" />
<add name="RowToParametersTransformer"
type="System.Web.UI.WebControls.WebParts.RowToParametersTransformer" />
</transformers>
</webParts>
<httpRuntime maxRequestLength="8192" />
</system.web>
</configuration>
You will then need to restart the server.

© 2008 AVEVA Solutions Ltd A:1 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

A.1.4 Unable to show Sub Report

• If you see the error message unable to show sub report when running the report
against some of the sub reports.
Solution is to ensure you install a minimum of SP2 of SQL 2005.

© 2008 AVEVA Solutions Ltd A:2 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

A.2 GRANT PERMISSIONS on SQL Functions and Views

This can be done via T-SQL Scripts. The SQL below can be used, substituting the relevant
Windows UserName/Groups into <WINDOWSUSERNAME>. You will need Systems
Administrator permissions against the Database. If you are going to be setting permissions
specifically for yourself you will need to run the SQL Query as another Windows User
(remember to place square brackets around your windows [username]). Alternatively
replace the <WINDOWSUSERNAME> with the word public to give all users access to the
report functions.
GRANT EXECUTE ON [dbo].[AVEVAECRNumbers] TO <WINDOWSUSERNAME>
GRANT EXECUTE ON [dbo].[AVEVAApprovedBy] TO <WINDOWSUSERNAME>
GRANT EXECUTE ON [dbo].[AVEVAApprovalDate] TO <WINDOWSUSERNAME>
GRANT EXECUTE ON [dbo].[ebf_has_permission_gb] TO <WINDOWSUSERNAME>
GRANT EXECUTE ON [dbo].[AVEVA_get_person_id] TO <WINDOWSUSERNAME>
GRANT SELECT ON [dbo].[AVEVABOMExplosion] TO <WINDOWSUSERNAME>
GRANT SELECT ON [dbo].[AVEVABOMExplosion_ItemID] TO <WINDOWSUSERNAME>
GRANT SELECT ON [dbo].view_proj_doc_responsibilities TO <WINDOWSUSERNAME>
GRANT EXECUTE ON [dbo].[AVEVATagReferences] TO <WINDOWSUSERNAME>

© 2008 AVEVA Solutions Ltd A:3 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

A.3 Preparing the Sample Templates for Use

The sample reports have been provided as Report Templates (.RDL files) in the
<INSTALLATIONDIR>\SSRS\RDL Templates. These can be used to modify and play with
the existing reports, without risking the integrity of the original samples.
Note that the supplied RDL Templates all refer to an image file intended to display your
Company Logo. The location for the image is specified within the RDL Templates and is
defaulted to http://@REPORTSERVER@. This should be updated to your report server
name. Copy the templates to a new location to edit them.

Note: To modify these files using Business Intelligence Studio 2005 copy them to
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\
ProjectItems\ReportProject\ or the equivalent location for your installation.

You should also create the following folder structure to suit within your Report Server folder
structure that is:
<DefaultWebFolder>Corporate/Logo, and store the topleftheader.gif file, and any other
corporate related logos that will appear on reports into that folder.

© 2008 AVEVA Solutions Ltd A:4 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

A.4 OneClickInstallDeploy Installation and Deployment

Procedure

A.4.1 Overview
AVEVA NET 4.3 Reporting provides a prototype tool called OneClickInstallDeploy which
can be used as an alternative to the manual steps involved in installation and deployment of
both the Native and SharePoint Deep Integration deployments.
The use of this tool is currently unsupported but instructions are provided here if you choose
to try it.

A.4.2 One Click Create DataSource and Deploy Report Model

After Extraction you will find an executable file within the <INSTALLATIONDIR>SSRS folder
called OneClickInstallDeploy.
Double Click on OneClickInstallDeploy to open the OneClickInstallDeploy Executable and
begin the Reporting Install Deployment

On running the application you should see this screen.

© 2008 AVEVA Solutions Ltd A:5 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

Note that the settings shown on entry are specific to the Windows User Name that you
logged onto Windows with (albeit the default settings largely prompt you for entry), and
another user will have their own settings.
It is recommended that you allocate a single Windows User Name (say Administrator) to
running this program, and setting up your AVEVA NET Reporting facilities.
OneClickInstallDeploy will save your configuration settings (or not if you answer no when
asked), and this will allow you to re-run the program without having to remember what your
previous settings.

A.4.3 Getting Started

To get started you first need to Unlock the Configuration Settings by clicking the Unlock/
Lock Config button.

© 2008 AVEVA Solutions Ltd A:6 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

Notice on unlocking the Config Settings that you are now prevented from actioning the two
One Click buttons, until you Lock the Settings again after completing the necessary Inputs.
The example settings on entry assume a Deep Integrated SharePoint example (hence the
Native checkbox is not clicked), and here we will continue with that assumption. A Native
installation should be relatively intuitive once you have performed a Deep Integrated
installation.

A.4.4 Create DataSource and Deploy Report Model

Enter the Name of your Deep Integrated SharePoint Site or site/sub site, into the 'Report/
SharePoint Server' Input field

Note: DO NOT prefix the name with http:// or anything similar, as at the moment this will not
produce anything, and also will not produce any error messages either (a later
release should address one or both of these issues).

Note: You must have already set up your own Default Integrated SharePoint Site and
implemented Report Centre into this Site. Please refer to the online links provided
above to assist with this.

Enter the Name of your Data Server which is the Name of the AVEVA NET SQL Server that
hosts the SQL Database which is connected to your AVEVA NET Community.
Enter the Name of the Database which is the Name of the SQL Database connected to your
AVEVA NET Community.
Enter the Username of a valid Windows User, in the same format as shown within the
Stored Credential Username (SharePoint Deep) Input field
Enter the valid password associated with that Username. (Note for security purposes you
will have to enter this password each time you access the OneClickInstallDeploy program,
as this is not stored in the Configuration Settings).
Enter a valid Windows Group User Name that any Reporting User will exist in. If you have
more than one Windows Group likely to be using AVEVA NET Reporting, you will have to

© 2008 AVEVA Solutions Ltd A:7 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

perform this step as many times as you have Reporting User Groups (or enter individual
Users if you do not wish to enable Reporting across Groups). This is required because
OneClickInstallDeploy will assign permissions to this (these) Group(s)/Users to enable the
execution of specific Reporting functions, and also enable the db_datareader role against
them.
However, this does rely on you having the necessary SQL permissions to execute the
associated internal standard SQL procedure called sp_addrolemember. If you do not have
this permission you may need to contact your IT Administrator / Support person to either to
give you that permission or run the OneClickInstallDeploy under his account.
Check that the default Report Model Path corresponds to the Drive/Directory Path where
you installed AVEVA NET Reporting, and if any or all of it is incorrect, then amend it to suit
your chosen path and remember to save the Config Settings on exit.
After checking all your inputs are valid and correct you can now Lock the Config Settings
and then click the Create DataSource and Deploy Report Model button.

This will create the AVEVANETDataSource, upload the AVEVANETReportModel into the
Data Connections Folder/Library, and automatically connect it to the aforementioned
DataSource.

A.4.5 Check Data Connections

Locate and open the Data Connections Library on your specified SharePoint Site, and
check that the AVEVANETDataSource and AVEVANETReportModel objects are present.
In the event of them not existing, check all your entries and spellings, and retry the Create
DataSource and Deploy Report Model button before contacting Support.

Note: If you do not have a Data Connections Library then you will first need to check your
MOSS and Report Centre Installation as this Library forms part of that Installation.

Note: Under some circumstances some time after clicking the One Click Create
DataSource button, you may receive a dialog which recommends you should double

© 2008 AVEVA Solutions Ltd A:8 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

check that the Report Model has in fact been correctly created within your Data
Connections folder. This is an intermittent error that has been noticed on some
occasions, and if after checking and waiting a bit you still do not see the Model and
DataSource simply retry the One Click Create.

If you just see the Model without DataSource, you will need to delete the Model and retry the
One Click Create.
Do not continue to deploy reports until you have both the Data Source and Model within
your Data Connections folder.
Make sure you check and double check your Report/Sharepoint Server Name entry to
confirm that it is spelt correctly and does NOT have a trailing /.

A.4.6 Deploy Reports

• Design Document Summary Report Path

Once again continuing to use the OneClickInstallDeploy tool Unlock the Configuration
Settings, by clicking the Unlock/Lock Config button.

Check that the first part of the default settings for Master Design Doc RDL Path (before
Design Document Summary) correspond to the Drive and Directory Path where you
installed AVEVA NET Reporting, and if any or all of it is incorrect, then simply amend it to
suit your chosen path and remember to save the Config Settings on exit.

• Standard Parts Reports Path

Check that the first part of the default settings for Master Parts Templates RDL Path
(before RDL Templates) corresponds exactly with the Drive and Directory Path where you
installed AVEVA NET Reporting, and if any or all of it is incorrect, then amend it to suit your
chosen path and remember to save the Config Settings on exit.

© 2008 AVEVA Solutions Ltd A:9 4.3.SP1

 AVEVA NET Reporting - Installation Guide
Appendices

• Business Intelligence Studio RDL TemplatesPath

The default setting for this Input field assumes Business Intelligence Studio 2005 (or Visual
Studio 2005 with the Business Intelligence Add On templates). If you are using a different
version of Business Intelligence Studio, you will need to determine the equivalent Report
Item template folder. This folder is used to place copies of the Master Standard Parts
Reports held within the 'Master Parts Templates RDL Path' folder into the available Report
Items when creating New Reports in Business Intelligence Studio.
In other words the Parts List Reports are included as both stand alone Report Files, which
will be deployed in a similar way to the Design Document Report Summary report, but also
as separate ReportTemplates to allow easy modification or customisation as required.
OneClickInstallDeploy handles both the copying of the Standard Reports Templates into the
necessary internal Business Intelligence Studio Report templates folder, and also caters for
the cross referenced image logo files which you will need to upload onto your SharePoint
Site into the Corporate/Logo folder. The image must be named topleftheader.gif.

• Extending Standard Report Templates

You can extend these available templates to include any that you design yourself, by simply
placing them into the Master Parts Templates RDL Path.

Note: You will need to cater for any images that you wish to include within these templates
in a similar way to the AVEVA Standard Templates.

Click OneClick Deploy Master RDLs to deploy the reports.

Check that these three Parts List Reports are created in your Parts Reports folder on your
Deep Integrated SharePoint Site (http://@SharePointSite@/ReportsLibrary)
• AVEVAIndentedBOM
• AVEVASingleLevelPartsList
• AVEVASummarisedBOM
Note: Execute and Selection Permission setting is incorporated within the One Click
Deploy mechanism.

However, you will still need to ensure that all AVEVA NET Users and Groups that are
registered within AVEVA NET are given at least data reader permissions within the relevant
AVEVA NET Datasource. This is to ensure Reporting adheres properly to the AVEVA NET
Security principles, and OneClickInstallDeploy will also assist in this.
OneClickInstallDeploy can create the necessary valid Windows User / Group Names into
the specified SQL Server (as long as you have sufficient permission to create Users in the
AVEVA NET Datasource).
To test the reports, open the AVEVA NET Parts Reports folder (http://@SharePointSite/
ReportsLibrary/Parts Reports) and click them.

© 2008 AVEVA Solutions Ltd A:10 4.3.SP1

 AVEVA NET Reporting - Installation Guide

Index

© 2008 AVEVA Solutions Ltd Index page 1 4.3.SP1

 AVEVA NET Reporting - Installation Guide

© 2008 AVEVA Solutions Ltd Index page 2 4.3.SP1