Maximizing Your ArcGIS Silverlight Viewer In your Enterprise
In this presentation we describe how to utilize the ArcGIS Silverlight Viewer technology for utility needs.
Maximizing ArcGIS Silverlight Viewer In your Enterprise
1.
2. Eugene Water & Electric Board
Founded 1911
Oregon's largest customer-owned utility
Provides electricity, water and steam to more than 86,000 homes,
business, schools and other customers in Eugene, Oregon.
3. Electric
Distribution Engineering
Systems Engineering
Dispatch (Outage
Management)
Operations
Fiber Management
Right-of-Way
Surveyors
Water
Engineering
Operations
Energy Management
Power Resources
Generation
Carmen-Smith Project
Environmental
Source Protection
Water Quality
Etc.
4. Over 300+ Users
Majority Viewers
Power Users/Editors
Designers
Field Crews
Management
Etc.
6. Provide a way to smoothly integrate non-GIS systems
with web based GIS System using a Single framework for
delivering applications to users
Allow non-desktop users access to maps/data
Use of Telvent ArcFM Silverlight Viewer
Allow interaction with existing apps
Create additional value
Use of multiple systems together instead of separate ones
Streamline end-user functions
Easily jump from one app to another
7. “The ArcFM Viewer application must have the ability to
receive requests from other web-based applications
and display a specific query request in the viewer.”
8. Push data to a Silverlight App
Silverlight Applications are “sand-boxed”
Inherent tightened security measures
Unknown “other web-based applications”
9. Esri
ArcGIS Server for Microsoft .Net Framework 10
with Service Pack 3
ArcGIS API for Silverlight 2.2
Telvent
ArcFM Server 10.0.3
ArcFM Silverlight SDK 2.2
Visual Studio 2010
Silverlight 4 and related toolkits
10. “The ArcFM Viewer application must have the ability to receive requests …”
Silverlight LocalMessageSender and
LocalMessageReceiver
The channel is started by the LocalMessageReceiver
and one or more LocalMessageSenders can
communicate with it. The receiver can also respond
to the original message which promotes a two-way
conversation, if needed. The message that is sent
can be simple text or complex structures that can
be serialized, such as XML or JSON data.
11.
12. “The ArcFM Viewer application must have the ability to receive requests …”
Sample proof-of-concept application
13.
14.
15.
16. Start ArcFM Silverlight viewer if not running
Parameters on the URL
Send parameters to Silverlight app startup
Parse parameters in Silverlight app
Tap into existing Telvent searching
17.
18.
19.
20.
21.
22.
23. Questions / More Information
Raul Duato
EWEB
raul.duato@eweb.org
Jeff Mertz
SSP Innovations, LLC
Visit us at EXPO Booth 301 !
jeff.mertz@sspinnovations.com
http://www.sspinnovations.com/communicating-with-arcfm-silverlight-application.aspx
Editor's Notes
One of the challenges in working with a Silverlight application is dealing with external events other than the typical asynchronous communication used to retrieve data. We usually think of a Silverlight application as a "pull only" client and face the dilemma of trying to "push" data to it to get it do something without direct user intervention.
One of the challenges in working with a Silverlight application is dealing with external events other than the typical asynchronous communication used to retrieve data. We usually think of a Silverlight application as a "pull only" client and face the dilemma of trying to "push" data to it to get it do something without direct user intervention.
One of the challenges in working with a Silverlight application is dealing with external events other than the typical asynchronous communication used to retrieve data. We usually think of a Silverlight application as a "pull only" client and face the dilemma of trying to "push" data to it to get it do something without direct user intervention.
There are a couple of strategies that could be used to accomplish this (e.g. a polling thread), but to provide a more "real-time" experience to the user, we chose to use local messaging via the LocalMessageSender and LocalMessageReceiver classes first introduced in Silverlight 3. Local messaging allows the ability for multiple Silverlight applications (plug-ins) running on a single computer to set up and use a communication channel.
There are a couple of strategies that could be used to accomplish this (e.g. a polling thread), but to provide a more "real-time" experience to the user, we chose to use local messaging via the LocalMessageSender and LocalMessageReceiver classes first introduced in Silverlight 3. Local messaging allows the ability for multiple Silverlight applications (plug-ins) running on a single computer to set up and use a communication channel.
There are a couple of strategies that could be used to accomplish this (e.g. a polling thread), but to provide a more "real-time" experience to the user, we chose to use local messaging via the LocalMessageSender and LocalMessageReceiver classes first introduced in Silverlight 3. Local messaging allows the ability for multiple Silverlight applications (plug-ins) running on a single computer to set up and use a communication channel.
There are a couple of strategies that could be used to accomplish this (e.g. a polling thread), but to provide a more "real-time" experience to the user, we chose to use local messaging via the LocalMessageSender and LocalMessageReceiver classes first introduced in Silverlight 3. Local messaging allows the ability for multiple Silverlight applications (plug-ins) running on a single computer to set up and use a communication channel.
There are a couple of strategies that could be used to accomplish this (e.g. a polling thread), but to provide a more "real-time" experience to the user, we chose to use local messaging via the LocalMessageSender and LocalMessageReceiver classes first introduced in Silverlight 3. Local messaging allows the ability for multiple Silverlight applications (plug-ins) running on a single computer to set up and use a communication channel.