培训手册Wonderware Application Server

Lab 1 –Creating the GalaxyIntroductionIn this lab, you will create the Galaxy and connect to it using the ArchestrA IDE. This Galaxy will be used during the class to develop the sample application.ObjectivesUpon completion of this lab, you will be able to:Create a GalaxyConnect to a Galaxy using the ArchestrA IDECreate the GalaxyIn the following steps, you will create a Galaxy and connect to it.1.Open the ArchestrA IDE(Start | All Programs | Wonderware | ArchestrA IDE).The Connect To Galaxy dialog box appears with the local node name displayed in the GR node name drop-down list.In this image, TRAININGPC-ENG2is the local computer name.2.Click the New Galaxy button to create a new Galaxy.The New Galaxy dialog box appears.3.In the Galaxy name field, enter TrainingGalaxy.4.In the Galaxy type field, confirm Base_Application_Server.cab is selected.5.Click Create.The Create Galaxy dialog box appears and shows the Galaxy creation progress. This will take a few moments. Check to make sure that no error messages are displayed.6.When the Create Galaxy progress displays 100% completed, click Close.The newly created TrainingGalaxy now appears in the Galaxy name drop-down list.7.Click Connect.The Connect To Galaxy dialog box closes and, after a few seconds, the ArchestrA IDE opens.You will use the ArchestrA IDE to develop the Galaxy throughout the remainder of this class.-This page intentionally left blank -。

w o n d e r w a r e培训Wonderware培训Wonderware公司推出旗舰级 InTouch软件，这是第一个基于微软Windows&reg操作系统的人机界面（HMI）。

Wonderware只能在windows环境下运行，支持32位及64位操作系统，但wonderware公司建议使用32位操作系统因为64位操作系统部是很稳定，系统容易崩溃带来不必要的损失。

Wonderware软件架构：Intouch等可视部分客户端 Active factory分析部分Information Server CAL等第3方认可软件即符合（微软技术标准，工业标准） App Server发布数据三个服务器 Historian历史数据Information Server实时数据DAServer/I/OserverPLC等第三方软件Daserver/ioserver :收到采集命令，采集数据，发广播包，工作完成后，各机从DAseerver堆栈中提取数据。

概念：1.Archestry 只是一个名字2.Application server：应用程序服务器。

类似于I/Osever 客户端（阀门，泵，开关等运行配置，控制配置，run_time部分）3.Galaxy：数据库4.Galaxy Repostistory:配置的指令存储在此可以用这台机器进行开发。

5.GR是装Galaxy数据库的机器一个（工程）网络只能有一个Galaxy。

安装前准备：APPLICATION SERVER 的同时还可以安装I/OserverGR SQLSERVER可单独也可与APPLICATION 一起装。

Historation > 安装SQL server2005数据库需要建立防火墙，需专门一台机器。

Information server >安装SQL server2005数据库需要建立防火墙，需专门一台机器。

步骤1：1.每台机器装BOOTSTAP（需要主动对GR访问取数据的必须安装不是主动对GR 访问被动的接收数据的不用安装）。

Lab 7 –Configuring Change Control and PropagationIntroductionIn this lab, using the derivation hierarchy, you will control the changes made to derived objects by locking attributes. Additionally, you will use this feature to propagate the changes from templates to existing derived objects. This helps to establish standards in the Galaxy.ObjectivesUpon completion of this lab, you will be able to:Control changes to derived objects by locking attributesPropagate changes from templates to derived objectsLock the Attributes in $TankIn the following steps, you will lock attributes, which prevent changes to those attributes on derived objects. You will then observe that the changes have been propagated down the derivation hierarchy.1.Click on the Derivation tab to display the Derivation view.The derivation from the $UserDefined template to the Mixer_001instance is displayed.2.Double-click the $Tank template to display the configuration editor and ensure LT.PV is selected.3.In the Description field, enter Tank Level value.4.In the Engineering units field, change the value from Gallons to Liters.5.For both the Description and Engineering units attributes,click the lock icon.6.Expand the Enable I/O scaling area by clicking on the down arrow button.7.Next to the Scaling group, click the lock icon.This locks all of the attributes in this group.8.Click the lock icons to unlock the following attributes:EU value: MaximumEU range value: MaximumThis enables you to use this template for a variety of derived tanks where the maximum attributes differ depending on the tank type. These attributes can then be customized when derived objects are created.9.In the Field attributes list, click TT.PV.10.In the Description field,enter Tank Temperature value and lock the attribute.11.In the Engineering units field, change the value to Celsius and lock the attribute.12.In the Enable I/O scaling area, lock all of the attributes except for the maximum attributes, as donebefore, for the LT.PV field attribute.13.Save and close the configuration editor.14.In the Check In dialog box,Comment field,enter Locking attributes and click OK.The Check In dialog box appears.Notice the messages display that the $Mixer derived template and the Mixer_001instance were updated, because they are derived from the $Tank template.15.Click Close.In the Derivation view, notice the icon next to the Mixer_001instance showing that it requires redeployment for the changes to take effect. You will redeploy this instance later.Verify the Propagation to an InstanceNext, you will verify that the changes you made in the previous steps have propagated to the instance.16.Double-click on the Mixer_001instance to open the configuration editor.17.In the Inherited field attributes list, click on LT.PV and expand the Enable I/O scaling area.The previously locked attributes are now grayed out and cannot be changed, but the unlocked attributes can still be changed.18.Click on TT.PV to view that the same configuration applies to the locked and unlocked attributes.19.Click on the Close button to close the configuration editor.Lock the Attributes in $MixerNext, you will lock some of the attributes within the mixer template.20.Double-click the $Mixer template to open the configuration editor.21.In the Field attributes list, ensure TP1.Cmd is selected.22.In the Description field, enter Command to start/stop Transfer Pump1and lock the attribute.23.In the following field attributes, type the following descriptions and lock the attributes:All of the field attributes are now configured.24.In the Inherited field attributes area, click on LT.PV and expand the Enable I/O scaling group.25.Lock the Scaling Maximum values.26.Click on TT.PV and change the following attributes:EU value: Maximum450.0and lockedEU range value: Maximum455.0and locked27.Save and close the configuration editor.28.In the Comment field, enter Locking attributes and click OK.The Check In dialog box appears.Notice that the changes have propagated down the hierarchy structure to the Mixer_001instance.29.Click Close.Verify PropagationNext, you will verify that the changes have propagated to the instance.30.Open the Mixer_001configuration editor.31.In the Inherited field attributes list, click on each of the TP1.Cmd,TP1.PV,TP2.Cmd, and TP2.PVattributes to confirm that the descriptions are locked and cannot be edited.32.Click on the LT.PV and TT.PV attributes and expand the Enable I/O scaling group to confirm that thescaling maximum attributes have been locked.33.Close the configuration editor.Redeploy the Mixer InstanceNow, you will redeploy the instance to runtime.34.Right-click Mixer_001and select Deploy.35.Keep the default options and click OK.36.When the progress shows 100% completed, click Close.-This page intentionally left blank -。

Lab 16 –Configuring HistoryIntroductionIn this lab, you will configure the Galaxy for historization to the local Historian Server. Specifically, you will configure the $gAppEngine object to store historical data.Additionally, you will configure the object attributes to be historized.ObjectivesUpon completion of this lab, you will be able to:Configure a $gAppEngine object to store historical data to a Historian ServerConfigure objects to enable history including a History extensionConfigure Objects for HistoryIn the following steps, you will configure multiple objects in the Galaxy to begin historizing data.1.In the Deployment view, double-click AOSPlatform1to open the configuration editor.2.On the General tab, in the History store forward directory field, enter C:\S&F.3.Save and close the configuration editor.4.In the Check In dialog box, Comment field, enter Store and Forward configuration and click OK.5.Double-click AppEngine1to open the configuration editor.6.On the General tab, check the Enable storage to historian check box.7.In the Historian field, enter [your instructor will confirm the computer name]. In this image,TrainingPC-ENG2will be used.8.Save and close the configuration editor.9.In the Check In dialog box,Comment field, enter Historian configuration and click OK.10.In the Template Toolbox,Working toolset, double-click $Mixer to open the configuration editor.11.In the Inherited field attributes list, select LT.PV and check the Enable history check box.12.In the Trend high field, enter 100.0and lock the history group.13.Save and close the configuration editor.14.In the Check In dialog box,Comment field, enter LT historization and click OK.15.When the Check In progress shows Object 1 of 1 completed, click Close.16.In the Template Toolbox,Working toolset, double-click Inlet1to open the configuration editor.17.Check the Historize PV check box and lock the PV group.18.Save and close the configuration editor.19.In the Check In dialog box,Comment field, enter PV historization and click OK.20.When the Check In progress shows Object 1 of 1 completed, click Close.21.In the Template Toolbox,Working toolset, double-click Agitator to open the configuration editor.22.On the Extensions tab, Extendable Attributes list, select Speed.23.Configure the Speed attribute as follows:History extension checked and lockedEngineering units:RPMTrend high:50Description:Agitator Speed24.Save and close the configuration editor.25.In the Check In dialog box,Comment field, enter Speed historization and click OK.26.When the Check In progress shows Object 1 of 1 completed, click Close.The Deployment view now displays several objects that need to be redeployed.27.Deploy AOSPlatform1and keep the default options.28.When the Deploy progress displays 100% completed, click Close.View the Historical Data with Historian ClientNow, you will use Wonderware Historian Client Trend to view a trend of the historical data.29.Start Wonderware Historian Client Trend (Start | All Programs | Wonderware | Historian Client |Trend).The Server List Configuration dialog box appears.30.In the Server field, enter [check with your instructor]. In this image, TrainingPC-ENG2will be used.31.Check the Use Integrated security check box and click Add.After a few moments, the computer name appears in the Server list.32.Click Close.The Wonderware Historian Client Trend window opens and in the Tag Picker pane, all of the tags configured for historization are displayed.33.Double-click the Agitator_001.Speed tag to add it to the trend chart.The Agitator_001.Speed historical data now displays in the trend chart.You can also drag and drop tags to the trend chart to add them.34.Drag and drop Inlet1_001.PV and M1XX.LT.PV onto the trend chart.Your trend chart will now display all three tags at the same time.35.On the toolbar, click the Enable or disable live or replay mode button.The trend chart now updates automatically.36.Close the Trend application.The Wonderware Historian Client dialog box appears.37.Click No .。

Lab 11 –Adding Auto Reconnect to DDESuiteLinkClientIntroductionIn this lab, you will configure the $gDDESuiteLinkClient to automatically reconnect to the data source when the connection is lost. You will do so by extending the objects with UDAs with scripts.Using a UDA/script combination, you will also add additional diagnostic information that will indicate the number of disconnects the object has experienced since it last went on scan.ObjectivesUpon completion of this lab, you will be able to:Create scripts in an objectCreate scripts with multiple execution typesAdd reconnect functionality to the $gDDESuiteLinkClient objectAdd the Auto Reconnect FunctionalityIn the following steps, you will create a script that will automatically reconnect to the data source when the connection is lost.1.In the Template Toolbox,Global toolset, double-click $gDDESuiteLinkClient to open theconfiguration editor.2.On the Scripts tab, click the Add Script button. the new script Reconnect and press Enter.4.Configure the Reconnect script as follows:Aliases:lockedDeclarations:lockedScripts: Execution type:Execute(default) and lockedBasics lockedExpression: Me.Connectionstatus<>2Trigger Period:00:00:05.0000000Script body Me.Reconnect=true;This script will attempt to reconnect every 5 seconds when not connected to the data source.Now, you will validate the script syntax by using the Validate feature. If the script has a syntax error, it will appear in the yellow bar just above the script body area.5.To the right of the Execution type drop-down list, click the Validate button.6.In the UDAs tab, click the Add button.7.Rename the new UDA t and press Enter.8.Configure the t UDA as follows:Data type:IntegerCategory:Calculated9.In the Scripts tab, click the Add button. the new script Disconnect.Monitor and press Enter.11.Configure the Disconnect.Monitor script as follows:Aliases:lockedDeclarations:lockedScripts: Execution type:Execute(default) and lockedBasics lockedExpression: Me.Connectionstatus<>2Trigger type:OnTrueScript body t=t+1;This script will increase a counter by one every time the condition is true.12.Click the Validate button.You will now add code within the same script under a different execution type that will run when the object goes on scan.13.While still in the Disconnect.Monitor script, change the Execution type to OnScan.14.In the script body, type t=0;.This script will reset the counter to zero every time the object goes on scan.15.Save and close the configuration editor.16.In the Comment field of the Check In dialog box, type Reconnect script and click OK.17.When the Check In progress displays Object 1 or 1 completed, click Close.18.Redeploy PLCSim, leaving the default options.19.When the Deploy progress displays 100% completed, click Close.View the Scripts in RuntimeNext, you will use Object Viewer to view the runtime data of the scripts.20.In the Deployment view, right-click PLCSim and select View in Object Viewer.21.Click on the PLCSim tab.Add the following attributes to the watch window:tDisconnect.Monitor.ExecutionCntReconnect.ExecutionCnt22.Save the watch window.Note:Your instructor will now disconnect your connection to the Device Integration server, and then reconnect the connection so that you can observe the behavior.Your Watch List now displays that there was a disconnect, but the connection has been restored.。

Lab 20 –Configuring RedundancyIntroductionIn this lab, you will configure a second network connection in Windows for use as the Redundancy Message Channel. Then, you will configure the Galaxy platforms and engines for redundancy. Finally, you will create the hosting relationship, deploy the changes, and force a failover to confirm the functionality.ObjectivesUpon completion of this lab, you will be able to:Configure a secondary network connection in Windows as the Redundancy Message Channel Configure WinPlatform and AppEngine objects for redundancyCreate a deployment model for redundant enginesForce a failover on a redundant systemConfigure Windows for RedundancyIn the following steps, you will configure a second network connection in Windows as the Redundancy Message Channel (RMC). This will need to be done on both computers, where the first is the computer where GRPlatform is deployed and the second is the computer where AOSPlatform1is deployed.1.Connect to the machine where the GRPlatform is installed [for the remote computer, this will be themachine where the AOSPlatform1in installed].2.Open Network Connections(Start | Control Panel | Network and Sharing Center).3.Click Change adapter settings.The Network Connections window appears.4.Right-click Local Area Connection and select Rename.5.Rename the connection ArchestrA.6.Right-click Local Area Connection 2and select Rename.7.Rename the connection RMC.8.Press Alt+N to unhide the Menu bar.9.On the Advanced menu, select Advanced Settings.The Advanced Settings dialog box appears.10.In the Connections area, select ArchestrA and click the Up Arrow button.The ArchestrA connection is now listed first.11.Click OK.12.In the Network Connections window, right-click RMC and select Properties.The RMC Properties dialog box appears.13.In the This connection uses the following items area, select Internet Protocol Version 4(TCP/IPv4).14.Click the Properties button.The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box appears.15.Click the Use the following IP address option.16.In the IP address field, enter 192.168.1.1. [For the remote computer, this will be 192.168.1.2]17.Click in the Subnet mask field to automatically assign the subnet mask.18.In the bottom-right of the window, click the Advanced button.The Advanced TCP/IP Settings dialog box appears.19.On the DNS tab, uncheck the Register this connection’s addresses in DNS check box.20.Click OK.21.In the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box, click OK.22.In the RMC Properties dialog box, click Close.23.Repeat Steps 1to 22on the remote computer where AOSPlatform1is deployed. The IP address thatwill be used on the remote computer will be 192.168.1.2.Configure the Platforms for RedundancyYou will now return to the ArchestrA IDE and configure the platforms for redundancy.24.In the Deployment view, open the GRPlatform configuration editor.25.In the Redundancy area, Redundancy message channel IP address field, enter 192.168.1.1.26.Save and close the configuration editor.27.In the Check In dialog box,Comment field, enter Redundancy configuration and click OK.28.Open the AOSPlatform1configuration editor.29.In the Redundancy group, Redundancy message channel IP address field, enter 192.168.1.2.30.Save and close the configuration editor.31.In the Check In dialog box,Comment field, enter Redundancy configuration and click OK.The Deployment view now displays that both platforms have pending changes.You will redeploy the platforms later in this lab.Configure AppEngine1 for RedundancyYou will now configure AppEngine1for redundancy. Since AppEngine1is currently deployed, you must first undeploy it.32.Right-click AppEngine1and select Undeploy.33.In the Undeploy dialog box, keep the default options and click OK.34.When the Undeploy progress is complete, click Close.35.Open the AppEngine1 configuration editor.36.On the Redundancy tab, check the Enable Redundancy check box.The Redundancy configuration settings auto populate with the default values.37.Keep the defaults and click Save and close.38.In the Check In dialog box,Comment field, enter Redundancy configuration and click OK.The Deployment view now displays the AppEngine1icon with the primary redundant engine icon.39.Expand the Unassigned Host folder to reveal the new backup application engine instance.This was automatically created when redundancy was enabled in AppEngine1.You will now have GRPlatform host the new AppEngine1 (Backup) object.40.Drag and drop AppEngine1 (Backup)onto GRPlatform.Now, you will redeploy the platforms.41.Select both the AOSPlatform1and the GRPlatform.42.Right-click either platform and select Deploy.43.Keep the default options and click OK.44.When the Deploy progress is complete, click Close.45.Return to Object Viewer.Because the platforms redeployed, you will get the following error in Object Viewer.46.Click OK.Object Viewer closes.You will now deploy the application engines using the Include Redundant Partner option.47.In the Deployment view, right-click AppEngine1and select Deploy.48.In the Deploy dialog box, check the Include Redundant Partner check box.49.Click OK.50.When the Deploy progress is complete, click Close.The Deployment view now displays that all objects have been deployed.View the Redundancy Functionality and Data in RuntimeYou will now use Object Viewer and observe selected AppEngine1attributes in the runtime environment. You will then force a failover and observe the changes.51.In the Deployment view, right-click AppEngine1and select View in Object Viewer.52.On the File menu, select Load Watch List.53.Navigate to C:\Training and select MyWatchWindow.54.Click Open.55.Add the following attributes to the watch window:HostRedundancy.IdentityRedundancy.StatusRedundancy.PartnerPlatformRedundancy.PartnerStatusRedundancy.FailoverOccurredRedundancy.ForceFailoverCmdThe watch window displays that AOSPlatform1is currently hosting AppEngine1and the redundancy status is active. Additionally, the GRPlatform is the partner platform and is currently in a Standby mode.56.Save the watch window.You will now force a failover to trigger redundancy and observe the changes.57.In the watch window, double-click AppEngine1.Redundancy.ForceFailoverCmd.The Modify Boolean Value dialog box appears.58.Click the True option and click OK.After a few seconds, the watch window displays GRPlatform as the host platform andAOSPlatform1as the partner platform.You will now refresh Object Viewer to view the changes.59.In the console tree pane, collapse and expand AOSPlatform1and GRPlatform.The pane now displays that AOSPlatform1is no longer hosting any objects and GRPlatform is now hosting all of the objects.60.Click the Mixer1tab.The watch window displays that all attributes are still running and producing good quality data.Lab 20–Configuring Application Redundancy 9-33Application Server 201261.On the Mixer2watch window, observe the same behavior.You will now force another failover to return to the primary redundancy configuration.62.In the Redundancy watch window, double-click AppEngine1.Redundancy.ForceFailoverCmd .63.In the Modify Boolean Value dialog box, click the True option and click OK .After a few seconds, the watch window displays AOSPlatform1as the host platform andGRPlatform as the partner platform.You can also observe what happens when the connection to the remote computer loses connectivity.64.Disable the RMC network connection.After a few seconds, the watch window now displays that the Standby Status isActive –Standbynot Available.9-34Module 9–RedundancyInvensys Learning Services 65.Reenable the RMC connection.After a few seconds, the watch window displays the Standby Statusis back to Active .。

Lab 9 –Creating the MixerIntroductionIn this lab, you will use the valve and motor templates that you created in previous lab to create dedicated templates for each mixer component. You will use these templates and the mixer template to create an object containment, which integrates all of the parts that make up the mixer.You will then update the existing instance by adding instances and configure their attribute references so that their values can be viewed in Object Viewer.Finally, you will create a new instance of the mixer container, which will also create all of the instances of the container and the contained objects.ObjectivesUpon completion of this lab, you will be able to:Create contained templates and a containment relationshipUpdate an existing mixer instanceDeploy contained instancesCreate a new containment instanceCreate the Mixer Containment RelationshipIn the following steps, you will create templates for the parts of the mixer container.1.In the Template Toolbox,Working toolset, right-click $Valve and select New | Derived Template.2.Rename the template $Inlet1.3.Right-click $Valve and select New | Derived Template.4.Rename the template $Inlet2.5.Right-click $Valve and select New | Derived Template.6.Rename the template $Outlet.7.Right-click $Motor and select New | Derived Template.8.Rename the template $Agitator.You will now assign the newly created templates to the mixer template to create a container at the template level.9.Drag and drop the following templates onto the $Mixer template:$Inlet1$Inlet2$Outlet$AgitatorContained templates lose the $at the beginning of their names. If you were to take one or more out of the containment relationship, the $would reappear.Now, you will create instances for all the contained objects that will be added to the existing Mixer_001.10.Display the Model view.11.In the Template Toolbox,Working toolset, right-click Agitator and select New | Instance. Keep thedefault name.12.Create the following instances and keep the default names:The Model view now displays the new instances in the Unassigned Area folder.Configure the Existing Mixer InstanceYou will now create the containment at the instance level.13.In the Model view, assign all four instances in the Unassigned Area folder to the Mixer_001instance.The four contained object instances display configuration warnings, which you will resolve later in this lab.The contained name displays next to an object name in brackets. You will now change the contained name for the new four instances to match the template names.14.In the Model view, right-click Agitator_001and select Rename Contained Name.The Rename Contained Name dialog box appears.15.Rename the contained name Agitator and click OK.The Model view now displays the new contained name for the Agitator_001object.16.Rename the contained names for the following:Inlet1_001change to Inlet1Inlet2_001change to Inlet2Outlet_001change to OutletConfigure I/O for Valves and AgitatorNext, you will configure the attribute references for the newly created contained instances.17.In the Model view, open the Agitator_001configuration editor.18.On the Inputs tab, click the ellipsis button next to the Input Source Reference field.The Galaxy Browser -TrainingGalaxy window appears.19.In the Instances pane, click PLCSim.20.Select the Tagname.M1XX_AG_AuxContact attribute, where XX is your student number. In thisimage, 00will be used.21.Click OK.The Input Source Reference field is now populated with the correct attribute reference.22.In the Outputs tab, click the ellipsis button next to the Output Destination Reference field.23.Select the Tagname.M1XX_AG_CmdStart attribute and click OK.The Output Destination Reference field is now populated with the correct attribute reference.24.Save and close the configuration editor.25.In the Check In dialog box,Comment field,enter I/O references configuration and click OK.26.Open the Inlet1_001configuration editor.27.In the Inputs tab, configure the Input Source Reference as follows:Input 2: CLS Tagname.M1XX_IV1_CLSInput 1: OLS Tagname.M1XX_IV1_OLSThe Input Source Reference fields now display the correct attribute references.28.In the Outputs tab, configure the Output Destination Reference as follows:Output 1: CmdOpen Tagname.M1XX_IV1_CmdOpenThe Output Destination Reference field now displays the correct attribute reference.29.Save and close the configuration editor.30.In the Check In dialog box,Comment field,enter I/O references configuration and click OK.31.Open the Inlet2_001configuration editor.32.In the Inputs tab, configure the Input Source Reference as follows:Input 2: CLS Tagname.M1XX_IV2_CLSInput 1: OLS Tagname.M1XX_IV2_OLSThe Input Source Reference fields now display the correct attribute references.33.In the Outputs tab, configure the Output Destination Reference as follows:Output 1: CmdOpen Tagname.M1XX_IV2_CmdOpenThe Output Destination Reference field now displays the correct attribute reference.34.Save and close the configuration editor.35.In the Check In dialog box,Comment field,enter I/O references configuration and click OK.36.Open the Outlet_001configuration editor.37.In the Inputs tab, configure the Input Source Reference as follows:Input 2: CLS Tagname.M1XX_OV_CLSInput 1: OLS Tagname.M1XX_OV_OLSThe Input Source Reference fields now display the correct attribute references.38.In the Outputs tab, configure the Output Destination Reference as follows:Output 1: CmdOpen Tagname.M1XX_OV_CmdOpenThe Output Destination Reference field now displays the correct attribute reference.39.Save and close the configuration editor.40.In the Check In dialog box,Comment field,enter I/O references configuration and click OK.The Model view no longer displays any exclamation points.Deploy the InstancesEven though Mixer_001is already deployed, the newly contained instances still need to be deployed.41.In the Deployment view, select all four new instances.42.Right-click on any of the highlighted instances and select Deploy.43.Keep the default options and click OK.44.When the Deploy progress displays 100% completed, click Close.View the Mixer Data in RuntimeYou will now return to Object Viewer to observe the attribute values in runtime.45.Right-click on Mixer_001and select View in Object Viewer.Object Viewer appears and is refreshed.Although the container relationship was created and the container deployed, Object Viewer does not display this relationship in the object list.46.In the details pane, add the following attributes to the watch window:The data being displayed is updating in the watch window.47.Save the watch window.Create a New Instance of $MixerNext, you will create a new instance of the mixer template.48.In the ArchestrA IDE,Template Toolbox,Working toolset, right-click $Mixer and select New |Instance.49.In the Model view, under the Unassigned Area folder, expand the Mixer_002instance.Mixer_002has the contained instances of the mixer created with the correct contained names, as well as the mixer instance.The configuration warnings and deployment for these objects will be addressed in a later lab.。

Lab 2 –Creating Global Derived TemplatesIntroductionIn this lab, you will create derived templates from base templates using the ArchestrA IDE. These derived templates will be used throughout the remainder of the class to develop the sample application. You will then organize the templates into template toolsets. You will then hide the template toolsets that contain the base templates to ensure that instances are not created from base templates.ObjectivesUpon completion of this lab, you will be able to:Create a new template toolset to organize templatesCreate a derived templateHide a template toolsetCreate the Template ToolsetsIn the following steps, you will create template toolsets to help organize the templates that you will create.1.In the Template Toolbox, right-click TrainingGalaxy and select New Template Toolset.2.Rename the new toolset Training.Note: The Rename feature can be found by right-clicking the folder or object.You will now create template toolsets in the Training template toolset.3.Right-click the Training toolset and select New Template Toolset.4.Rename the new toolset Global.5.Repeat Steps 3&4and rename the new toolset Working.Create the Derived TemplatesFor the remainder of this lab, you will create derived templates and organize them in the template toolsets that were just created.6.Expand the Device Integration toolset by clicking on the plus icon to the left of the templatetoolset.7.Right-click $DDESuiteLinkClient and select New | Derived Template.8.Rename the new derived template $gDDESuiteLinkClient.9.Repeat Steps 7&8three times to create three more new derived templates from the following basetemplates:The Template Toolbox now displays all four new derived templates in the Device Integration template toolset.10.Drag and drop the four new derived templates into the Global toolset.11.Expand the System template toolset.12.Create four new derived templates from the following base templates:The Template Toolbox now displays the four new derived templates in the System template toolset.Note: You will not create a derived template from $InTouchViewApp, because it is a special object that does not accept second level derivation.13.Drag and drop the four new derived templates and the $InTouchViewApp object to the Globaltoolset.To ensure that instances are not created from base templates, you will hide the Device Integration and System template toolsets. Going forward, you will only use the Application and Training template toolsets.14.Right-click on the Device Integration template toolset and select Hide.15.Repeat Step 14to hide the System template toolset.Your Template Toolbox now displays the organization as seen below.-This page intentionally left blank -。

Wonderware培训Wonderware公司推出旗舰级InTouch软件，这是第一个基于微软Windows&reg操作系统的人机界面（HMI）。

Wonderware只能在windows环境下运行，支持32位及64位操作系统，但wonderware 公司建议使用32位操作系统因为64位操作系统部是很稳定，系统容易崩溃带来不必要的损失。

Wonderware软件架构：Intouch等可视部分客户端 Active factory分析部分Information Server CAL等第3方认可软件即符合（微软技术标准，工业标准）App Server发布数据三个服务器 Historian历史数据Information Server实时数据DAServer/I/OserverPLC等第三方软件Daserver/ioserver :收到采集命令，采集数据，发广播包，工作完成后，各机从DAseerver 堆栈中提取数据。

概念：1.Archestry 只是一个名字2.Application server：应用程序服务器。

类似于I/Osever 客户端（阀门，泵，开关等运行配置，控制配置，run_time部分）3.Galaxy：数据库4.Galaxy Repostistory:配置的指令存储在此可以用这台机器进行开发。

5.GR是装Galaxy数据库的机器一个（工程）网络只能有一个Galaxy。

安装前准备：APPLICATION SERVER 的同时还可以安装I/OserverGR SQLSERVER可单独也可与APPLICATION 一起装。

Historation > 安装SQL server2005数据库需要建立防火墙，需专门一台机器。

Information server >安装SQL server2005数据库需要建立防火墙，需专门一台机器。

步骤1：1.每台机器装BOOTSTAP（需要主动对GR访问取数据的必须安装不是主动对GR访问被动的接收数据的不用安装）。

培训手册Wonderware ApplicationServer 3.1目录一、简介 (5)1.1 Wonderware系统平台 (5)Lab 1 创建Galaxy (6)1.2 ArchestrA IDE (9)1.3 系统对象 (17)1.4 建模及规划 (18)Galaxy项目开发流程 (18)Lab 2 搅拌器建模分辨 (19)二、平台应用结构 (22)2.1 模板 (22)Lab 3创建一个模板 (22)2.2 开发模板 (27)Lab 4创建部署模板 (27)2.3 运行环境 (35)Lab 5如何使用对象查看器 (35)2.4 连接现场数据 (41)Lab 6 连接现场数据 (41)三、平台应用对象 (49)3.1 模板与实例 (49)3.2 用户定义对象 (51)Lab 7 创建热交换器模板 (51)3.3 改变控制及衍生 (61)Lab 8 如何改变控制及衍生 (61)3.4 模拟型设备对象 (64)Lab 9 创建仪表模板 (64)3.5 离散型设备对象 (66)Lab 10 创建阀、泵、电机模板 (66)3.6 模板容器 (74)Lab 11创建Mixer (74)四、扩展对象 (91)4.1 UDAs (91)4.2 扩展属性 (91)Lab 12配置电机速度属性 (91)4.3 脚本简介 (96)Lab 13用脚本添加自动连接至DDE Suitelink Client (96)Lab 14用脚本配置自动注释 (99)五、报警和历史 (105)5.1 报警 (105)Lab 15报警配置 (105)5.2 历史 (117)Lab 16历史配置 (117)六、安全 (122)6.1 安全回顾 (122)Lab 17安全配置 (122)七、Galaxy 维护 (142)7.1 导出导入对象 (142)7.2 通过.csv文件配置实例 (143)7.3 系统管理控制（SMC） (144)7.4 网络账户功能 (145)八、数据采集产品 (145)8.1 IO Server (146)8.2 DA Server (147)8.3 DI Object (147)九、多节点开发 (148)9.1 应用系统冗余 (148)Lab 18 配置应用冗余 (148)9.2 数据采集冗余 (150)Lab 19 配置DI对象冗余 (150)9.3 多节点应用 (153)Lab 20 转换到网络开发环境 (153)一、简介1.1 Wonderware 系统平台系统架构节点 描述 安装组件Galaxy Repository GR 节点，一个Galaxy 就有一个GR 节点。

安装WEB服务器准备工作：1 将计算机节点名修改为WEB （此名称可根据实际需要命名），此名称一经确定建议在通常情况下不要修改2 添加一个名称为EMS的本地用户并设置密码：baosight(可根据实际需要而定)，此帐户在以后安装过程中需要用到。

3 以管理员身份登陆此计算机（建议将管理员密码设为：baosight）4 Microsoft Windows Server 2003 系统光盘一张5 Microsoft SQL Server Standard 2008 光盘一张及Microsoft SQL Server Standard 2008 SP1 补丁包光盘两张6 Wonderware Application Server 3.2 SP2 光盘一张7 Wonderware Information Server 光盘一张第一步安装IIS服务和1 将Microsoft Windows Server 2003 系统光盘放入光驱自动运行2 单击【安装可选的Windows组件】3 选中【应用程序服务器】，单击【详细信息】4 按照上图所示勾选，然后单击【确定】5 单击【下一步】6 单击【完成】第二步安装SQL Server 2008 及SQL Server 2008 SP11 将Microsoft SQL Server Standard 2008 光盘放入光驱自动运行2 单击【确定】3 单击【安装】4 单击【退出】5 单击【下一步】6单击【下一步】7 单击【继续】8 单击【完成】9 单击【确定】重新启动我的电脑feature to an existing installation】11 单击【OK】12 单击【Next】13单击【Next】14 单击【Install】15等待安装完毕16单击【Next】17选择【Select All】,然后单击【Next】18单击【Next】19单击【Next】20 单击【Use the same account for all SQL Server services】21选择【NT AAUTHORITY\NETWORK SERVICE】单击【OK】22单击【Next】23选择【Mixed Mode】填写password:baosight 选择【Add Current User】单击【Next】24 选择【Add Current User】单击【Next】25单击【Next】26 单击【Next】27单击【Next】28单击【Install】29单击【Next】30 单击【Close】完成SQL Server 2008 的安装第三步安装SP11 将SP1光盘放入光驱2 双击【SQL Server 2008 sp1-….x86】3单击【下一步】4单击【下一步】5选择【全选】单击【下一步】6单击【下一步】7单击【更新】8单击【下一步】9单击【关闭】完成SP1补丁包的安装第四步安装SharePoint1 下载SharePoint 3.0，并根据下图运行以下指令运行—CMD完成安装 V2.02单击【继续】3选择【高级】4选择【web前端】单击【立即安装】5等待安装6单击【关闭】7单击【下一步】8单击【是】9选择【否】单击【下一步】10填写数据库服务器：（此名称为WEB服务器节点计算机名）填写用户名：（此为创建的本地账户名）填写密码：（此为创建的本地账户密码）单击【下一步】11单击【下一步】12单击【下一步】13等待完成安装14单击【完成】15填写用户名及密码单击【确定】16单击【添加】17单击【关闭】，完成安装SharePoint 3.0,接着安装SharePoint Services 3.0 Service Pack 2 SP2补丁包18单击【继续】19单击【下一步】20单击【是】21单击【下一步】22单击【确定】23等待完成安装24单击【完成】25填写用户名及密码单击【确定】26单击【创建SharePoint网站】27单击【新建Web应用程序】28选择【使用现有IIS网站】中默认网站29选择【NTLM】30填写用户名及密码31单击【确定】32单击【确定】33单击【创建网站集】34填写标题：默认网站选择：空白网站35填写用户名单击【确定】36 单击【确定】完成配置网页第五步安装Application Server (BootStrap)1 将Application Server 光盘放入光驱自动运行2单击【安装必备组件】3单击【下一步】4单击【Next】5单击【Next】6 按照上图配置选择，然后单击【Next】7填写用户名及密码，然后单击【Next】8单击【Next】9单击【Next】10单击【Finish】11单击【是】重新启动我的电脑，完成Bootstrap的安装第六步安装InformationServer1 将InformationServer光盘放入光驱，自动运行2单击【Next】3单击【Next】4单击【Install】5单击【Configure】6单击【Information Server】7 选择【Authentication Mode】为：SQL 填写密码：baosight 及用户密码；单击【LicenseManager】单击8单击图示位置9找到License位置选择：ArchestrA.Lic单击【打开】单击10单击图示位置11选择ArchestrAServer.lic单击【打开】12单击【Copy to Clipboard】。

Lab 6 –Modeling the MixerIntroductionIn this lab, you will configure the analog and discrete field attributes in the $UserDefined object to model a mixer device. You will also use the Galaxy Browser to find and build attribute references using the PLCSim object created in the previous lab to provide the connection to the live values within the mixer. ObjectivesUpon completion of this lab, you will be able to:Configure analog and discrete field attributes in a $UserDefined objectBuild attribute references using the Galaxy BrowserCreate the Tank TemplateIn the following steps, you will create the tank template.1.In the Template Toolbox,expand the Application toolset.2.Right-click the $UserDefined template and select New|Derived Template.3.Rename the derived template $Tank.4.Move the $Tank template to the Working toolset.5.Double-click $Tank to open its configuration editor.6.On the Field Attributes tab,click the Add Analog button to add a new analog field attribute.7.In the Name field, rename the field attribute LT.PV and press Enter.8.Click on the Add Analog button again and rename the new field attribute TT.PV and press Enter.Your Field attributes list displays both attributes.9.Click the LT.PV field attribute and configure the attributes as follows:Access mode:InputData type:FloatEngineering units:GallonsEnable I/O scaling checkedRaw value: Maximum4095.0EU range value: Minimum-5.0EU range value: Maximum105.010.Click the TT.PV field attribute and configure the attributes as follows:Access mode:InputData type:FloatEngineering units:Deg FEnable I/O scaling checkedRaw value: Maximum4095.0EU value: Maximum250.0EU range value: Minimum-5.0EU range value: Maximum255.011.Click Save and close.12.In the Check In dialog box,Comment field, enter LT and TT configuration.13.Click OK.14.When the Check In progress displays Object 1 of 1 completed, click Close.Create the Mixer TemplateNext, you will create the mixer template.15.Right-click the $Tank template and select New | Derived Template.16.Rename the new template $Mixer.17.Double-click the $Mixer template to open its configuration editor.Notice the inherited attributes from the parent object,$Tank.18.Click the Add Discrete button.19.Configure the field attribute as follows:Name:TP1.CmdAccess mode:OutputCategory:User writeable (default) Enable state labels checkedLabel for ‘False’ state:StopLabel for ‘True’ state:Start20.Click the Add Discrete button again and configure the attributes as follows:Name:TP1.PVAccess mode:InputEnable state labels checkedLabel for ‘False’ state:StoppedLabel for ‘True’ state:Running21.Click the Add Discrete button again and configure the attributes as follows:Name:TP2.CmdAccess mode:OutputCategory User writeable (default)Enable state labels checkedLabel for ‘False’ state:StopLabel for ‘True’ state:Start22.Click the Add Discrete button again and configure the attributes as follows:Name:TP2.PVAccess mode:InputEnable state labels checkedLabel for ‘False’ state:StoppedLabel for ‘True’ state:RunningAll four new field attributes are displayed in the Field Attributes list.23.Click Save and close.24.In the Check In dialog box,Comment field, enter Pump attribute configuration and click OK.25.When the Check In progress displays Object 1 of 1 completed, click Close.Create the Mixer InstanceNext, you will create an instance of the mixer template.26.In the Template Toolbox,Working toolset, right-click the $Mixer template and select New |Instance.27.Keep the default name Mixer_001.28.In the Model view, assign the Mixer_001instance to the Line1area.Notice the exclamation point to the left of the Mixer_001instance. This is because the object has configuration warnings.Now, you will check the warning messages.29.Right-click the Mixer_001instance and select Properties.The Mixer_001Properties window appears.30.Click the Errors/Warnings tab to view the configuration issues that need attention.Notice that the window is displaying the items that need the proper I/O addressing, because ---.---is a place holder for an attribute reference. The warning messages indicate that the listed attributes do not have valid attribute references.31.Click Close.Now, you will configure the attribute references for the field attributes.32.In the Model view, double-click on the Mixer_001instance to open its configuration editor.33.In the Inherited field attributes list, select TP1.Cmd.34.To the right of the Output destination field, click the ellipsis button.The Galaxy Browser -TrainingGalaxy window appears.35.In the Instances pane, click PLCSim to view the attributes of the device integration object.36.Select Tagname.M1XX_TP1_CmdStart where XX is your student number and click OK.In thisimage,the student number is00.The Output destination now displays the correct value.37.Repeat steps32through35to configure the Output source for attribute TP2.Cmd using theTagname.M1XX_TP2_CmdStart attribute.38.Configure the rest of the attributes with the following Input sources:All of the inherited field attributes are now configured.39.Click Save and close, and then in the Check In dialog box,Comment field, enter I/O referencesconfiguration and click OK.Notice that the exclamation point is no longer displayed.40.In the Deployment view, right-click the Mixer_001instance and select Deploy.41.Keep the default options and click OK.42.When the Deploy progress displays 100% completed, click Close.View the Mixer in Object ViewerNext, you will observe the attribute values for the object created in the previous steps.43.Right-click on the Mixer_001instance and select View in Object Viewer.44.If you closed Object Viewer, on the File menu, select Load Watch List to open the watch list file yousaved earlier.45.Add a new watch window and rename the tab Mixer.46.Add the following attributes to the newly created Mixer watch window:LT.PVTT.PVTP1.CmdTP1.PV.MsgTP2.CmdTP2.PV.Msg47.Save the watch window.。