The entirely new communication capability that WebView opens for a remote CIMPLICITY user affects how some CimView features perform.
When you configure CimView screens that remote users will access through WebView, keep the following basics in mind.
Because the third party Web browser is the primary interface, some of its features, such as the toolbar, will override features that a Viewer displays.
The consequences of the user's actions occur on the Web server, not at the Web browser location. For example, if a file is deleted through WebView, it is deleted on the Web server computer, not on the client computer.
Data is transmitted over low bandwidths (telephone lines) or through a network that is possibly being used by numerous other applications.
As a result, the configuration decisions you make will increase the effectiveness of the CimView screens being viewed from a remote location.
More specifically, following are some guidelines for CimView features in relation to WebView.
Guidelines for CimView Features in Relation to WebView
A browser user can perform an ExecuteCommand or scripted action that interacts with the server. A command that, for example deletes a file, can be very useful. However, because the result is on the server, some commands are not useful to the remote user. For example, if you configure an action that opens Microsoft Notepad, Notepad will open on the server. The browser user will not see it.
The Print action is not supported.
An Alarm Viewer that opens a specified CimView screen, when it is pushed, opens the screen on the server, not through the browser.
An Open Screen action behaves like an Overlay Action through a browser. It will replace the displayed screen with the selected screen. It does not open another browser window.
Note: When you create an Overlay Screen or Open Screen action, enter the name of the screen to overlay in the Screen name field. If no file name is specified and a remote user attempts to trigger the action, WebView will display an error message.
Browser's built in Window features
The browser's built in window features, such as the toolbar and menu, display instead of the CimView window features.
Browser window resizing
When a user increases or decreases the size of the browser window how CimView resizes depends on the browser. Under Internet Explorer, CimView resizes to the browser size. If a user decreases the size of Netscape, CimView stays at its original size and is clipped by the Netscape window.
Right mouse button behavior
Right mouse button actions are not recognized through a browser. This means that popup menus do not display and, consequently, a user cannot access other features through those menus.
ActiveX controls that WebView supports include Trend, Alarm Viewer OCX, SPC, CimGraph and Recipes. However, dialog boxes and menus for these features are not supported.
Note: You can script some of the features that use dialog boxes and menu items through CimView.
Third party ActiveX controls are not supported, although some may work. However, separate windows, display dialog boxes and menu displays will not work.
Basic scripting dialog boxes will not work.
A remote user can interact with OLE objects whose primary function is display (e.g. Word or WordArt).
Other OLE objects, such as sound, will open on the server. Someone who is near the server may hear them. The remote user will not.
Because WebView deals with Viewer capability, it is most efficient to put it on a server that points to both the primary and secondary computer in a redundant pair. However, if you decide to make the primary computer also the WebView server, you will have to manually reconnect the slave if the master goes down.
Other features to consider
The onscreen keypad, which is called through a command line parameter, /keypad, does not display through WebView.
The read-only Properties dialog boxes will not display when a remote user double clicks an object.
About CIMPLICITY Web access and Terminal Services.