Server Installation

On each server in your system (with the exception of permanent standby servers), you need to:

1. Install the ClearSCADA software, including:
   • The relevant SAP Crystal Reports runtime engine for .NET Framework 4 component(s) (see Prerequisite Components in the ClearSCADA Installation Guide).

     The SAP Crystal Reports runtime components are NOT installed by default. If you intend to install them you must purchase a Crystal Reports runtime license for each server on which these components are to be operational (clients do not need a license to use the runtime components). For servers on which the runtime components are operational, the Crystal Reports runtime license is included with the ClearSCADA Crystal Reports driver license. Please contact your Schneider sales representative for more information.

     If you intend using Crystal Reports on your system, you also need to install the Crystal Reports prerequisites and driver on any Permanent Standby servers, in order for the ClearSCADA database to synchronize. However, as the Permanent Standby ClearSCADA servers do not require the Crystal Reports driver to be operational, they do not require a Crystal Reports runtime license. (On the Modules tab on the Server Status Tool of such servers, the Crystal Reports driver will show a red 'No License' state due to the lack of runtime license. This is expected on Permanent Standby servers. On all other servers on systems that use Crystal Reports, the Crystal Reports driver and runtime components must be licensed.)

     NOTE: You must install .NET 3.5 Full Runtime (see Prerequisite Components in the ClearSCADA Guide to Installation). With Windows Server 2016, Windows Server 2012, Windows Server 2012 R2, Windows 8.1 and 10, you must do this before you run Setup. Use Programs and Features in the Windows Control Panel to turn the feature on (see the Windows Help). With Windows 7 or Windows Server 2008 R2, you can either use this method or you can select .NET 3.5 Full Runtime from the available prerequisite options when you run Setup (see Installation of Prerequisites).

   • The Server Crystal Reports component
   • The Data Access component (which includes ODBC).
2. Set up the required ViewX client connections to the server. For information, see:
   • Crystal Reports Installation on ViewX Clients on Which You Want to Edit Reports
   • Crystal Reports Installation on Clients on Which You Only Want to Display or Print or Export Reports
   • ViewX Client - System Connections in the ClearSCADA Guide to Client Administration.
3. Add an ODBC Data Source Name (DSN) for the ClearSCADA driver, to allow Crystal Reports to access the ClearSCADA database. Crystal Reports uses the DSN to access the relevant database whenever you generate, print, or export a report using the Generate Report, Print Report, or Export Report pick actions.

   You add the DSN using the ODBC Data Source Administrator Tool. You can access the tool from the Administrative Tools section of the Windows Control Panel (see Configure an ODBC Client - System Connection using a DSN in the ClearSCADA Guide to Client Administration).

   The DSN has to be an ODBC System DSN.

   On a computer running a 64-bit version of Windows®, the DSN has to be a 64-bit ODBC System DSN. (ClearSCADA’s Crystal Reports driver is a native application and so requires a 64-bit DSN on 64-bit machines, and a 32-bit DSN on 32-bit machines.)

   We advise that the same System DSN name is used throughout your system. That is, that the System DSN has the same name on both the client(s) on which the reports are to be created, and on the server(s) that will be used to generate those reports. This applies even if you are only going to access the Local Database with Crystal Reports. (The Local Database is the ClearSCADA database that contains the report.)

   NOTE: If the ClearSCADA Server Configuration Tool is running locally on the server, you can also access the ODBC Data Source Administrator Tool from the Crystal Reports section of the ClearSCADA Server Configuration Tool (see Configuring Crystal Reports Server Settings).

   For more information on setting up an ODBC DSN, see Configure an ODBC Client - System Connection using a DSN in the ClearSCADA Guide to Client Administration.

4. Use the Crystal Reports section of the ClearSCADA Server Configuration Tool to enter the name of ODBC System DSN that you added in step 3. This provides the association between the ClearSCADA database and the ODBC DSN that the Crystal Reports driver uses to access the local database (see Configuring Crystal Reports Server Settings, and see Accessing the ClearSCADA Database).
5. If your system comprises Multiple Databases, repeats step 2 to 4 as required, in order to add a client connection and ODBC Data Source Name (DSN) for each ClearSCADA database that Crystal Reports is to access from the server.

   If Crystal Reports is to access the data from one or more Remote Database(s)(see Specify the Data Source) the DSNs used in such reports have to match on the client(s) and server(s) on your system. (That is, for each ClearSCADA database, the DSN has to have the same name and be connected to the same data source on the client(s) on which the reports are to be created, and on the server(s) that will be used to generate those reports.)

6. Repeat the above steps for the other servers on your system (except permanent standby servers).

Furthers Information

For diagrams that illustrate the location of the ClearSCADA components that you need to install, see ClearSCADA Software Components.