Comment faire pour
Detaching a WebReports Database
You detach a WebReports database to make the database available for subsequent attachment (when installing or upgrading WebReports to another operating system or computer).
Use this workflow to upgrade an Enterprise Server system. An Enterprise Server system can include an Enterprise Server, one or more SmartX servers and WorkStations, and supporting administrator software, such as Device Administrator.
The workflow applies to upgrading a system from version 1.8, 1.9, 2.0 or 3.0 to version 3.1.
If your system contains any MNB BACnet devices make sure to upgrade them.
Pour plus d'informations, voir Upgrade to Native MNB BACnet Devices .
Repair LonWorks Systems Running Version 1.8
The following flowchart shows the tasks for repairing LonWorks configurations in all EcoStruxure BMS servers running version 1.8.1. The EcoStruxure BMS servers need to be repaired before the upgrade from version 1.8.1 to version 3.1. Related information can be found in the sections after the flowchart.
If you upgrade a system with LonWorks devices from version 1.8.1 to version 3.1, install WorkStation hotfix v1.8.1.34000 , or higher.
If you upgrade a system with LonWorks devices from version 1.8.1 to version 3.1, install Enterprise Server hotfix v1.8.1.34000 , or higher.
If you upgrade a system with LonWorks devices from version 1.8.1 to version 3.1, install SmartX server hotfix v1.8.1.34000 , or higher.
Install the hotfix on all SmartX servers hosting LonWorks devices that are based on the LonWorks imported device templates (.XIF) or resource kits (.DRF). If you are uncertain, install the hotfix on all SmartX servers hosting LonWorks devices.
In WorkStation, select the Enterprise Server and repair the LonWorks configurations in the Enterprise Server and all online SmartX servers running version v1.8.1.34000 , or higher.
Ensure you have installed the hotfix v1.8.1.34000, or a later consolidation point where the hotfix is included, for WorkStation and the EcoStruxure BMS servers before you repair the LonWorks configurations. WorkStation and the EcoStruxure BMS servers must be running hotfix v1.8.1.34000, or a later consolidation point where the hotfix is included.
You cannot upgrade to version 3.1 until the LonWorks configurations in all EcoStruxure BMS servers running version v1.8.1.34000, or a later, are repaired.
Restart the repaired EcoStruxure BMS servers by running the warm start command from WorkStation.
The list of repaired EcoStruxure BMS servers is obtained in the previous step, when you repair the LonWorks configurations.
Pour plus d'informations, voir Warm Starting a SmartX Server .
Pour plus d'informations, voir Warm Starting an Enterprise Server .
Delete obsolete LonWorks objects from your EcoStruxure BMS servers to increase available space.
Ensure that all EcoStruxure BMS servers in the configuration are updated to version v1.8.1.34000, or later.
Pour plus d'informations, voir Delete Obsolete LonWorks Objects .
Pour plus d'informations, voir Deleting Obsolete LonWorks Objects .
Prepare for Upgrade
Prior to upgrading a system, complete the tasks listed in the following flowchart. Related information can be found in the sections after the flowchart.
If you are upgrading WebReports, stop the Reporting Agent Windows service. Pour plus d'informations, voir Stopping the Reporting Agent Windows Service .
Perform a new All data backup of the Enterprise Server and the SmartX servers when backing up the system.
Pour plus d'informations, voir Backing Up EcoStruxure BMS Servers Manually .
For systems that include a Reports Server, back up the WebReports database.
Pour plus d'informations, voir Backing Up the WebReports Database .
Use the Services tool to stop the License Server Windows service. Pour plus d'informations, voir Stopping the License Server .
Upgrade the EcoStruxure Building Operation Software
The following flowchart shows the tasks for upgrading the EcoStruxure Building Operation software, except SmartX servers. Related information can be found in the sections after the flowchart.
Upgrade the License Server and License Administrator. Pour plus d'informations, voir Upgrading the License Administrator and the License Server .
Upgrade the Device Administrator. Pour plus d'informations, voir Upgrading the Device Administrator Installation .
Install the Enterprise Server and select Upgrade current version to . Pour plus d'informations, voir Upgrading the Enterprise Server .
If a newer version of Enterprise Server already is installed, ensure that the Enterprise Server Windows service of this version is stopped.
If Device Administrator is running on the same PC as the Enterprise Server, you can simulate the Enterprise Server upgrade to see if you can fix configuration issues in the Enterprise Server before you upgrade it. Pour plus d'informations, voir Previewing the Enterprise Server or Enterprise Central Database Upgrade .
The Enterprise Server Windows service automatically restarts after the Enterprise Server upgrade is complete. If the Enterprise Server Windows service does not start, restart the computer.
If you want to use a language pack in WebStation, install the language pack and change the language setting in WebStation.
Pour plus d'informations, voir Adding a Language in WebStation .
Pour plus d'informations, voir Modification de la configuration régionale utilisateur .
Upgrade WorkStation and select the editor tools and language packs you want to upgrade. Pour plus d'informations, voir Upgrading WorkStation and Client Tools Installation .
Keep one WorkStation at version 1.8.1.34000 , 1.9, 2.0 or 3.0 in case you need to make configuration changes to EcoStruxure BMS servers running 1.8, or 1.9, 2.0 or 3.0 if you need to perform LonWorks configuration preparations or repair locally on a SmartX server before version 3.1 upgrade.
Upgrade SmartX servers
The following flowchart shows the tasks for upgrading SmartX servers. Related information can be found in the sections after the flowchart.
When you upgrade from 2.0 to a higher version, you must install certificates to establish a trusted chain between the computer running Device Administrator and the Smart X servers. A trusted chain increases the security of your system and must be used if you use HTTPS.
If you upgrade from 3.0 to a higher versionhigher version and have already established the trusted chain with certificates, no further action is needed.
Pour plus d'informations, voir Device Administrator Certificate Workflow .
Pour plus d'informations, voir Device Administrator Licenses .
Use the upgraded Device Administrator to upgrade the databases of the SmartX servers using the IP network or USB port. Pour plus d'informations, voir Uploading and Upgrading a SmartX Server .
Open the Device Administrator upgrade log to get detailed information about the SmartX server upgrade process. Pour plus d'informations, voir Opening the Upgrade Log .
You can postpone the upgrade of some SmartX servers running version 1.8, 1.9, 2.0 or 3.0, while you upgrade the Enterprise Server, WorkStation, and other SmartX servers to version 3.1.
Open the two conversion logs to see warning and error messages that occurred when the databases were upgraded.
Use Device Administrator to open the conversion log. Pour plus d'informations, voir Opening the Conversion Log .
In Windows, open the high priority conversion log. Pour plus d'informations, voir Opening the High Priority Conversion Log .
Determine if you can use the converted database for download or if you need to fix configuration issues in the SmartX server and perform a new upgrade of the SmartX server database.
Pour plus d'informations, voir Conversion Logs .
Pour plus d'informations, voir Log Entry Interpretation .
When you are comfortable with the content of the high priority conversion log, use Device Administrator to download the upgraded database to the SmartX server.
Pour plus d'informations, voir Downloading an Upgraded Database to a SmartX Server .
Reset and Confirm Server Functions
The following flowchart shows the tasks for confirming the functions of the EcoStruxure BMS servers. Related information can be found in the sections after the flowchart.
Use the Software Administrator (or the Services tool) to verify that the Enterprise Server Windows service is running. Pour plus d'informations, voir Starting the Enterprise Server or Enterprise Central Windows Service .
In WorkStation, verify that the control and monitoring operations of the Enterprise Server are functioning normally per the guidelines specified for your site.
In the Security Certificate Risk dialog box, click Trust certificate to temporarily trust the certificate and log on to the EcoStruxure BMS server.
In Binding Diagnostics, check for invalid or unresolved bindings. Pour plus d'informations, voir Checking the Status of Bindings .
Replace any invalid or unresolved bindings with new bindings, using the Bindings view. Pour plus d'informations, voir Bindings Management .
The system may require 10 to 30 minutes to complete the process of resolving invalid or unresolved bindings. Wait for this process to finish before editing the bindings.
In WorkStation, generate, add, and activate certificates for the EcoStruxure BMS servers.
Pour plus d'informations, voir Generating a Certificate .
Pour plus d'informations, voir Adding a Certificate .
Pour plus d'informations, voir Activating a Certificate .
On the computer running the current version of WebReports, stop the Reporting Agent service by way of the Control Panel.
Ensure that any other applications that might be accessing the database are closed.
Open SQL Server Management Studio (type SQL in the Start menu Search box).
Expand the Databases folder.
Right-click the WebReports database, click Tasks , and then click Detach .
Select Drop Connections and then click OK .
Copy the database files StruxureWareReportsDB.mdf and StruxureWareReportsDB.ldf in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation WebReports\Database Files to a convenient location, for later attachment.
DéclarationSave the database files to an external device such as a USB memory device.
You now attach the database at the computer where you want to install WebReports. Pour plus d'informations, voir Attaching a WebReports Database .
Enterprise Server System Upgrade Workflow
Attaching a WebReports Database