Intelligence 2012 (v 1.5.100)
Wonderware Intelligence 2012 Readme
Last revision: 3/19/2012About This Readme
This document contains important information about Wonderware® Intelligence software 2012 (version 1.5.100). Review this document for known issues in this version and changes, if any, to the Intelligence software documentation included on this CD.
Use the following links to navigate to the various sections of this Readme:
About this ReleaseSystem Requirements
Product Compatibility
Licensing
Known Issues
Known Issues – Documentation
Software Documentation
About this Release
This release includes a new version of the Analytics Client and Dashboard Server, which are both based on Tableau Software, version 7.0.1.
The Wonderware Intelligence software now enforces licensing for the Analytics Client through license keys provided by Wonderware, on your license certificate. When you first start the Analytics Client, a software activation window prompts you to enter the license key.
System Requirements
This section describes the hardware, software, and operating system requirements to install the Wonderware Intelligence software.
Hardware Requirements
The following are the hardware requirements to install the Wonderware Intelligence software:
- 32 or 64 bit processors
- Fast (100 Mbit or faster) and reliable network connection to external software systems
The following table lists the hardware requirements for the Wonderware Intelligence Server, Wonderware Intelligence Client, and Intelligence Analytics Client:
| Intelligence Component Requirements | Processor | Memory (RAM) | Available Disk Space | System | Network Connection |
| Intelligence Server Minimum | 3 GHz or greater | 4 GB or greater | 50 GB to 500 GB, depending on quantity of data being aggregated | Server class system | - |
| Intelligence Run-time Server Recommended | 3 GHz or greater (Quad processor) | 16 GB or greater | 100 GB, depending on quantity of data being aggregated | Server class system | - |
| Intelligence Database Recommended | 3 GHz or greater (Quad processor) | 8 GB or greater | 500 GB, depending on quantity of data being aggregated | Server class system | - |
| Intelligence Data Adapter Service Recommended | 3 GHz or greater | 2 GB or greater | 100 MB | - | 10/100 Mbps or greater connection to the Intelligence Server and data source systems |
| Intelligence Client Recommended | 2.6 GHz or greater | 1 GB or greater | 100 MB | - | 10/100 Mbps or greater connection to the Intelligence Server |
| Intelligence Analytics Client Minimum | 2.6 GHz or greater | 2 GB or greater | 100 MB | - | - |
Operating System Requirements
The following table lists the supported operating systems for Wonderware Intelligence Server and Client. The requirements a remote data adapter are the same as for a Wonderware Intelligence Server.
| Operating System | Edition | Service Pack | Bit Version | Wonderware Intelligence Server or Remote Data Adapter | Wonderware Intelligence Client |
| Windows XP | Professional | SP3 | 32-bit (x86) only | Single node installation only* | Supported |
| Windows Server 2003 | Standard, Enterprise | SP2 | 32-bit (x86) only | Supported | Supported |
| Windows Server 2003 R2 | Standard, Enterprise | SP2 | 32-bit (x86) only | Supported | Supported |
| Windows Vista | Business, Enterprise, Ultimate | SP2 | 32-bit (x86) and 64-bit (x64) | Single node installation only* | Supported |
| Windows Server 2008 | Standard, Enterprise | SP2 | 32-bit (x86) and 64-bit (x64) | Supported | Supported |
| Windows Server 2008 R2 | Standard, Enterprise | (none) | 64-bit (x64) only | Supported | Supported |
| Windows Server 2008 R2 | Standard, Enterprise | SP1 | 64-bit (x64) only | Supported | Supported |
| Windows 7 | Professional, Enterprise, Ultimate | (none) | 32-bit (x86) and 64-bit (x64) | Single node installation only* | Supported |
| Windows 7 | Professional, Enterprise, Ultimate | SP1 | 32-bit (x86) and 64-bit (x64) | Single node installation only* | Supported |
*A single node installation is meant for demonstration purposes only.
Support for Non-English Versions of Operating Systems
The English version of the Wonderware Intelligence software runs on the following non-English operating systems:
- French
- German
- Japanese
- Simplified Chinese
Software Requirements
The following are the Wonderware and other third-party software requirements to install or use the Wonderware Intelligence software:
- Microsoft SQL Server. For more information, see Microsoft SQL Server Requirements.
- Microsoft .NET Framework 3.5 SP1 and 4.0
If you are using the Windows Server 2008 R2 operating system, the .NET Framework is part of the operating system and must be enabled before you install the Intelligence software. If you do not enable it before installing the Intelligence software, an error occurs when the Intelligence prerequisites are checked. For more information on enabling the .NET Framework, see the Microsoft Knowledge Base article KB 2027770. - ArchestrA Integrated Development Environment (IDE) version 3.1 SP2 P01, 3.1 SP3, or 3.5 (2012)
The following are third-party software that are required for the various data adapters of the Wonderware Intelligence software:
- Microsoft.ACE.OLEDB.12.0 is required on the data adapter service node if you plan to use the text file data adapter
- OSIsoft PI client connectivity component version 3.3.0.1a is required on the data adapter service node if you plan to use the OSIsoft PI OLE DB data adapter
- OSIsoft PI SDK 1.3.8.391 is required on the data adapter service node if if you plan to use a OSIsoft PI Native data adapter
- Oracle 10g and 11g, if used as a data source
- Microsoft SQL Server 2005 SP3 or later if used as a data source. Note that Microsoft SQL Server 2005 is not supported for the Intelligence Server.
Microsoft SQL Server Requirements
The following versions of Microsoft SQL Server are supported:
- Microsoft SQL Server 2008 SP1 or SP2 Standard 32-bit (x86) only
- Microsoft SQL Server 2008 SP1 or SP2 Enterprise 32-Bit (x86) only
- Microsoft SQL Server 2008 R2 Standard 32-Bit (x86) or 64-Bit (x64)
- Microsoft SQL Server 2008 R2 Enterprise 32-Bit (x86) or 64-Bit (x64)
Additional notes:
- The SQL Server language must be the same as the operating system language. For example, you can only run the French version of SQL Server on the French version of the operating system. You can, however, have a UK English operating system and a US English SQL Server, and vice versa.
- The SQL Server collation settings must be compatible with the operating system version. Having different language versions of the operating system and the SQL Server collation is not supported. Note that the default SQL Server database collation setting is sensitive to the regional settings (such as the date/time format). SQL Server should be installed after the regional settings have been set.
- A named instance of SQL Server is supported.
- A case-sensitive SQL Server is not supported.
- SQL Server Express is not supported.
- Microsoft SQL Server fail-over clustering is supported.
- The following Microsoft SQL Server 2008 SP1 components have to be installed on the Wonderware Intelligence Server node, if the data store is on a node other than the Wonderware Intelligence Server:
- Client Tools Connectivity
- Management Tools – Basic
Product Compatibility
Wonderware Intelligence software 2012 is compatible and can co-exist with the following products:
- Wonderware® Application Server 3.1 SP1, 3.1 SP2, 3.1 SP3, 3.1 SP3 P01, 3.5 (ArchestrA System Platform 2012)
- Wonderware® InTouch® 10.1 SP1, 10.1 SP2, 10.1 SP3, 10.1 SP3 P01, 10.5 (ArchestrA System Platform 2012)
- Wonderware® Historian 9.0 P2, 10.0 SP1 (ArchestrA System Platform 2012)
- Wonderware® Historian Client 10.0 SP1, 10.0 SP2 (ArchestrA System Platform 2012)
- Wonderware® Information Server 4.0, 4.0 SP1, 4.5 (ArchestrA System Platform 2012)
- Wonderware® Operations & Execution (MES) 3.5/4.0 and later
- Wonderware® InBatch™ 9.0 SP1 and later
- Skelta™ BPM.Net 2009 (Version 3.5.9102.15)
- InFusion™ CE 3.0
Depending on the version, some products may require SQL 2005 installed as the default instance, in which case, the Intelligence Data Store must be configured against a SQL Server 2008 SP1 named instance, if they are installed on the same computer.
Licensing
Wonderware Component Licensing
The Wonderware components are licensed through a paper license certificate.
Tableau Component Licensing
The Dashboard Server (Tableau Server) is licensed using a key provided on the paper license.
The Analytics Client (Tableau Desktop) version shipped with Wonderware Intelligence is allowed to access data only from the Wonderware Intelligence
data store. The Intelligence data store, however, can contextualize and aggregate data from several data sources, whether they are Wonderware sources or non-Wonderware sources (as per the compatible Intelligence data adapters.) The Analytics Client cannot directly access databases other than the Intelligence data store; all other databases must be included in the Intelligence model (as defined in the ArchestrA IDE) and deployed to the Intelligence data store.
The Wonderware Intelligence software enforces licensing for the Analytics Client through license keys provided by Wonderware, on your license certificate. When you first start the Analytics Client, a software activation window prompts you to enter the license key.
Known Issues
| L00095280: | When you start the Intelligence Analytics application from a Remote Desktop environment, you may see the following message "License not found". Restart the Intelligence Analytics application to resolve this problem. |
| L00095542: | If you deploy the whole Galaxy model and then undeploy the deployed Dimensions individually, the undeploy operation is successful but a warning message is logged in the ArchestrA Logger: "Cannot undeploy
dimension {Dimension name} because it is not in the run-time model."
If you deploy the Dimension object individually, and then do the undeployment of the Dimension object, no warning message is logged in the ArchestrA Logger. |
| L00095544: | If you deploy the whole Galaxy model that includes Dimension and DataSource objects, and then deploy the Measure object individually after creating an instance of the Measure object, a warning message
is logged in the ArchestrA Logger: "Measure {Measure name} refers to a data source that does not exist anymore."
If you deploy the Dimension/DataSource object individually, and then do the deployment of Measure object, no warning message is logged in the ArchestrA Logger. |
| L00095753: | If you switch between screens/tabs in the Configurator Utility, data that was entered in the previous screen is lost. |
| L00096461: | If you delete the dimension fields that were used in the dimension filter, and then validate the Dimension object, the Dimension object still validates correctly. |
| L00096493: | If you modify, save, and close a DataSource object editor after having opened both that DataSource and a Dimension object using that DataSource object at the same time, the following warning message
may appear on saving and closing the Dimension Object Editor: "Source data item with name '{column name}' does not exist in data source '{Data Source name}'. Save Anyway?"
The Dimension and Measure object using a modified data source while in edit mode should be closed and re-opened to complete the configuration. |
| L00096498: | If you are using the Simplified Chinese version of the operating system, and you select several items from the Source Data item editor into the Fields tab of the Dimension editor, you cannot view all the columns for the selection due to unavailability of the horizontal scroll bar. |
| L00096807: | In the Intelligence Client application, if you drag the column between the Projects and Dashboards list view in the Dashboard Browser to the right as much as you can, then the Dashboards list disappears. It cannot be dragged back. You must close and re-open the Intelligence Client to view the Dashboards list. |
| L00096894: | If you configure the Intelligence Client ClickOnce through the Web Publish mode on a computer with SharePoint Central Administration, and then start the Intelligence Client ClickOnce application, an
error message appears: "Cannot download the application. The application is missing required files. Contact application vendor for assistance."
To resolve this issue, you must exclude the ClickOnce path from SharePoint (if installed on the same computer). |
| L00097257: | The table names that include special characters are not listed in the Source Data Item Picker. |
| L00097886: | When you try to retrieve the schema for a CSV file that has a name that is sixty characters long, an error message appears: "Schema retrieval failed. Data item schema is null or empty: [Truncated Long File Name]". |
| L00098143: | If you change the order of columns in the Custom Query, the columns in the preview data do not change their order. |
| L00098152: | If you change the Time Zone of the computer on which the Intelligence Server is installed, you must restart the Wonderware Intelligence Service before the Intelligence Server takes the Time Zone change into account. |
| L00098514: | You create a DataSource that consists of three Dimensions {a}, {b}, and {c}, where the Dimension {a} and {c} are linked to Dimension {b}, and a Measure has a relationship to Dimension {a}.
When you deploy this model, the Dimension does not takes into consideration the inter-dependencies due to linking for deploying the Dimension. The Dimensions are deployed based on the alphabetical order. As a result of this, at run time, a warning message appears about Dimension {a} not having the link's destination dimension and the execution of that Dimension is skipped when it runs for the first time. The Measure that depends on Dimension {a} although will have null values for the Dimension Relationship column. When the Dimension {a} successfully runs the next time, it will have the expected record along with the link values, but the existing Measure records will continue to have null values in the Dimension relationship column unless that period is part of the Measure Update Period. To resolve this situation, you can deploy dimensions individually, starting with the independent dimensions, and then successively through all levels of linked dimensions. Then deploy the measure objects. |
| L00098633: | The default functionality of Wonderware Historian retrieval that uses the {End DateTime} period time zone for a query spanning a daylight time (DST)/non daylight time, returns different results depending on whether
the DST is on.
For example, if you create a dimension based on DateTime [Key], value and then backfill with data crossing the DST time (fall) change, the TimeStamps of the dataset before the time change will be off by 1 hour when you query with no specific wwTimeZone parameter. |
| L00098863: | You derive and create an instance of DataSource object after importing the Intelligence Object in the ArchestrA IDE using the French or German operating system, and then configure it with a datasource
that contains data of datetime type and data value that exceeds 12 o'clock, such as 15:00.
Now, you derive an instance of Dimension or Measure, checking the Select Source button, and then select the data item that you have configured. The data value for this datetime type is not shown correctly in the Preview Date window. However, if you click the data item, it is shown correctly. |
| L00098983: | If you include one or more spaces in the Intelligence database name, the Intelligence Service throws an exception and the staging database is not created properly. | ||
| L00099059: | If you have a GR node remote to the IDE, and you validate or propagate more than two objects at a time, you may experience slow performance and/or the validation may fail. To workaround this issue, validate/propagate one object at a time, or run the following file on the GR node: \Program Files\Wonderware\Intelligence\AppObjects\SingleThreadObjectValidation.reg | ||
| L00099117: | If you use the right-click menu to check out a DataSource object used by a measure, and then use the right-click menu to validate the Measure object that depends on the DataSource object, when you try to check in or undo the check out for the DataSource object, an error messages is shown. To fix the issue, you need to reopen the IDE. | ||
| L00100104: | The activation of Tableau Server fails if the ArchestrA License Server is running. Temporarily stop the ArchestrA License Server, activate the Tableau Server license, and then restart the ArchestrA License Server. | ||
| L00101880: | A configuration error in the Intelligence model results in an arithmetic overflow error in SQL Server for some of the data records at the source. The error returned in the ArchestrA Logger is as follows: "Error - Measure Transform ProductionMeasure Query execution failed with Query: ...". However, there are no details on what caused the measure transform error. This error is often the result of a data type mismatch between the source and the configured object data type in Intelligence. For example, if a calculation is configured in Intelligence with a Byte data type, and the source data type is Double, you will get an arithmetic overflow error. Double-check the data type(s) for your Intelligence objects to make sure that they are consistent with the source.
You can also discover more of the root cause of the error message by copying and pasting the query included in the error message into a query window in SQL Server Management Studio. When you execute the query, SQL Server will return more information about the actual cause of the error. |
||
| L00102637: | If the data source for an aggregate calculation is unavailable (for example, the network is down, the host computer is not responding, and so on), all advanced calculations that depend on that aggregate calculation will fail. This will generate an error in the ArchestrA Logger, and the executing time slice from the execution plan of the Measure object will be skipped. This could result in a loss of data if that slice is never recalculated. | ||
| L00102671: | Using the Configurator, if you attempt to configure the Intelligence Server with a user-defined data or log file path that does not already exist on the server, the configuration fails with an error message. To work around this issue, manually create the folder first using Window Explorer. | ||
| L00102948: | If you import a model using .csv, and the model includes dimensions that have filters, the objects will be in an error state after you validate them.
To work around this issue, open the Dimension object, go to the Filter tab, slightly modify the filter expression (for example, add a space at the end), and then validate the expression. After you save and check in the object, the object will no longer be in an error state. |
||
| L00102970: | Database locks can occur in Wonderware MES due to queries by Wonderware Intelligence against the MES database. This causes performance issues in Wonderware MES and timeouts for Wonderware Intelligence data loads.
To work around this issue, open the following file: C:\Program Files\Wonderware\Intelligence\Bin\IntelligenceDataAdapterService.exe.config Then, change <add key="IsolationLevel" value="ReadCommitted"/> to <add key="IsolationLevel" value="ReadUnCommitted"/>. |
||
| L00102993: | When you import a large model (.aaPKG file),
the import fails and not all of the objects are imported. An example model that would cause this is as follows:
To work around this issue, first split up the export into three package files: one for the data sources, one for the dimensions, and one for the measures. Then import them in the following order: data sources, dimensions, and measures. |
||
| L00108588: | Measure records will get a valid context reference only when both the dimension key field's data type and measure source field's data type in the measure relation are the same. If they are not of the same data type, then 0 (meaning no matching record found) is assigned as the context reference for the measure record. This issue mainly occurs when you are using any numeric data type as a key dimension field. | ||
| L00108915: | When you are implementing a custom query in an OSI-PI data source,
you may view the error message: “Undefined data type:‘xs:<type> ’" when previewing the data.
You may also see this error if you try to use this custom query in a Dimension or Measure.
If you see such an error message, the value column must be cast to the proper type within the custom query. Some examples:
|
||
| L00109411: | A data source custom query must not include an ORDER BY clause in the syntax. Although the validation and data preview succeed, data will not be processed at run time. | ||
| L00110814: | If you attempt to view a custom query in an instance of a DataSource object in the ArchestrA IDE version 3.1 SP3 or later, the IDE stops responding. To work around this issue, view the custom query in the object template, not the instance. | ||
| L00111217: | When an object is imported, the "Galaxy Name" and "Galaxy Repository Name" are read from the object’s information contained in the package file. If these names do not match the Galaxy into which the object is being imported, the object is in an error state. You must open the Measure object editor and, on the Calculation tab, validate each calculation that has a filter to take the object out of the error state. | ||
| L00111434: | The data backfill time for a measure cannot be saved if you modify the number of days by a value smaller than 10. | ||
| L00111882: | When selecting the data source items, if you select a public group from the Historian that contains no tags, an error occurs. This is likely because the group is empty or the TagName filter for the Historian data source filters out all the tags in the group. | ||
| L00112788: | If you deploy multiple selected Dimension objects, and at least one of them is already deployed, then the entire deploy operation will be cancelled when the system encounters the first object that is already in the deployed state. Also, if you undeploy multiple selected Dimension objects, and at least one of them is already undeployed, then the entire undeploy operation will be cancelled when the system encounters the first object that is already in the undeployed state. To work around this issue, you must deploy or undeploy starting at the lowest level of the object hierarchy and work backward to the root level. | ||
| L00113644: |
When you are configuring a DataSource object, if you switch the data adapter type and then save the DataSource object, the following error occurs: "Data source does not contain any source data items. Try updating the schema. Save Anyway?"
To work around this issue, after you switch the data type for the object, click the Connection tab, ensure that the user credentials are still valid for the newly-selected data adapter type, and then click the Get Schema button. If you had created any custom queries, validate them again or delete them if they no longer apply. |
||
| L00114494: | If you undeploy an object too quickly after you deploy it, you may get a run-time error. Wait for the initial execution to finish (you will see the data in the corresponding measure table) and then try undeploying again. | ||
| L00115013: | If you select the Override SQL Server default file group check box in the object configuration, and the file group name is empty, the measure object fails to deploy. Either click to clear the check box or configure a valid file group name. | ||
| L00115066: | When you change only the priority of a source data item using the Select Source Data Items dialog box for a dimension, the object is not marked as updated. Even after you redeploy the object, the old configuration is retained. Make sure that you have performed some other configuration (for example, edit the description) so that the asterisk appears next to the object name and you are prompted to save the object. | ||
| L00115393: |
On systems with Internet Protocol Version 6 (IPv6) enabled, the Intelligence Client window may not show any sample or published reports, and the following error appears in the status bar: ERROR [28000] FATAL: no pg_hba.conf entry for host "fe80:8c4c:956a:46f4:3e40%10", user "tableau", database "workgroup", SSL off.
This error may indicate an issue with Microsoft Internet Protocol version 6 (IPv6). Disable IPv6 on the computer running the Intelligence Client Access Service by doing the following:
Additional information is available in the following Microsoft KB article: http://support.microsoft.com/kb/929852 |
||
| L00115732: |
A custom query for an OSIsoft PI native data adapter source can be selected in the Source Data Item dialog box using the filter field. The custom query should not be available for an OSIsoft PI Server native data adapter source.
To work around this issue, when you switch the data adapter type from OSIsoft PI Server OLEDB to the OSIsoft PI Server Native in the DataSource object editor, make sure that you delete all custom queries. Custom queries are not supported for the OSIsoft PI Server Native data adapter type. Then on the Connection tab, click the Get Schema button. |
||
| L00115753: | If you lock the Data Adapter Type list in a DataSource object derived template, changes to the available adapter list performed at the derived template level are not propagated to the instance object. Because the DataAdapterTypes attribute contains an incorrect list, this causes errors if you set/retrieve the DataAdapterType attribute for the instance object. To work around this issue, do not lock the Data Adapter Type list. |
Installation and Upgrade Issues
| L00093348: | If you access the Intelligence Client application from a node where .NET Framework 3.5 SP1 is not installed, a warning dialog box appears. |
| L00097226: | If you do not uninstall the Wonderware Intelligence software, the Intelligence Analytics Client is not uninstalled, but all the other components of Wonderware Intelligence Install are uninstalled. | ||
| L00103727: | If the Wonderware Intelligence software is distributed across multiple nodes, you must upgrade all of the Intelligence components on all of the nodes to the latest version or the system will not work properly. | ||
| L00103925: | When you install one feature from a network share and then modify (add or remove) other features from the local drive, the following error appears: "SILauncher has encountered a problem and needs to close." Disregard this message, as the operations will complete successfully. | ||
| L00112796: |
After you upgrade to Wonderware Intelligence 1.5 or later (from 1.x), you must reconfigure any existing OSI PI Server data sources as follows:
|
||
| L00113291: | Starting with Wonderware Intelligence 1.5, you can configure a measure calculation so that it applies to all tags in a Wonderware Historian's public group(s). In the case where the Intelligence model is being upgraded from a previous version, to take advantage of this new feature, you must retrieve the schema again by selecting the GetSchema button in the Data Source object's editor. | ||
| L00113423: |
After you install Wonderware Intelligence 1.5 or later, import the objects, and import the Information Model with an .aaPKG extension (in this specific case, the .aaPKG file was created from a Wonderware Intelligence version prior to 1.5), the wrong function type appears in the Function list for an average calculation for a Historian data source that does not use a custom query. The "Average (Row Based)" is configured instead of "Average (Time Weighted)". To correct the function type:
|
||
| L00113425: |
After you install Wonderware Intelligence 1.5 or later, import the objects, and then use the Galaxy Load function to import the Information Model from a .csv file (in this specific case, the .csv file was created from a Wonderware Intelligence version prior to 1.5), no function types appear in the Function list for an average calculation.
This is because the single "Average" function has been replaced with two different types of average functions, which are based on the type of aggregation(s) supported by the data source: "Average (Row Based)" and "Average (Time Weighted)". You will need to reconfigure the Measure object to use one of these two functions as follows:
|
||
| L00114358: | The Analytics Client Data Source Generator application is not automatically added to the notification area of the task bar after installation until the computer is restarted. | ||
| L00119655: | If you are upgrading to ArchestrA System Platform 2012, we recommend that you first undeploy the Intelligence objects in the Galaxy before performing the ArchestrA System Platform upgrade. When you undeploy the Intelligence objects, a dialog box appears with the following prompt: "Remove existing data for selected objects if found in the data store?" Click No to keep your data. After the upgrade to ArchestrA System Platform 2012 is complete, when you deploy the Intelligence objects, a dialog box appears with the following prompt: "Overwrite existing data for selected objects if found in the data store?" Click No to keep your data. IT IS VERY IMPORTANT TO CLICK "NO" IN BOTH OF THESE DIALOG BOXES SO THAT YOUR INTELLIGENCE DATA IS NOT DELETED. |
Known Issues – Documentation
The following table describes corrections to the Wonderware Intelligence user documentation.
| Item | Location | Existing Documentation | Correction |
| 1 | IntelligenceInstall.chm and IntelligenceInstall.pdf page 25, “Configuring the Wonderware Intelligence Server” topic/section | -- | Add the following paragraph to the introduction:
The user account that you specify for the Intelligence Service must be a valid domain account and must be the same account you use for the Data Adapter Service. |
| 2 | IntelligenceInstall.chm and IntelligenceInstall.pdf page 30, “Configuring the Wonderware Data Adapter Service" topic/section | -- | Add the following paragraph to the introduction:
The user account that you specify for the Data Adapter Service must be a valid domain account and must be the same account you use for the Intelligence Service. |
| 3 | IntelligenceConfig.chm and IntelligenceConfig.pdf page 32, “Configuring the OSIsoft PI Server OLE DB Connection” topic/section | The dialog box does not show the Tag Name Filter box. The box is not described. | The dialog box should show the Tag Name Filter box.
The following new step should be added after the existing step 10: 11. In the Tag Name Filter box, type the filter criteria to retrieve tags for a specific OSIsoft PI Server data source system. You need to type the filter similar to an SQL "LIKE" clause. For example, to retrieve tags that contain "ABC" in their names, you need to type "'%ABC%". |
Software Documentation
The Wonderware Intelligence software documentation set includes the following:- Wonderware Intelligence Software Installation Guide - Provides information about installing and configuring the Wonderware Intelligence software features.
- Wonderware Intelligence Administration Guide - Provides information about configuring and mapping of various data sources; managing Intelligence objects such as dimension, measures, datasource, and their deployment; and security.
- Wonderware Intelligence Client Guide - Provides information about customizing and managing the published dashboards using the Wonderware Intelligence Client.
- Object Help - Provides information about run-time behavior, configuration, and run-time attributes of the Dimension, Measure, and the DataSource objects.
- ReadMe (This document) - Provides information about software and hardware requirements, known issues, licensing, and documentation.
http://www.adobe.com/products/reader.html
After installing Adobe Reader, double-click on a PDF file to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu.
The Wonderware Intelligence software installation instructions are located in the root folder of the Wonderware Intelligence software installation CD as an online Help file. You can view these instructions by clicking Help as you start the Wonderware Intelligence software installation procedure.
(c) 2009-2012 Invensys Systems, Inc. All Rights Reserved.
