Smart object for EagleView pictometry

In short, the answer to our question is Yes, but it might not be out of the box and could require custom development of a Service broker to communicate with EagleView.

To understand the path you would need to take, you would need to understand what APIs this product has available and if any of those APIs were compatible with any of the out of the box K2 integration options (such as the Endpoint Brokers) or if you would have to write your own Service Broker (Static or Dynamic ie Described vs. Discovered.)

I suspect given that this is GIS software, you will have to take the latter approach and write you own. The Market (link above) is full of examples of Service Brokers for communicating with a host of backend systems that you could use as a guide.

Before you get started writing your own broker, I recommend installing the Visual Studio templates for K2 located in the market at this link: http://community.k2.com/t5/K2-blackpearl/Visual-Studio-Project-Templates-for-K2-blackpearl-Extensions/ba-p/1081

The templates are a great accelerator for getting started writing a host of extensions to the K2 platform including Service Brokers.

There is a good starting entry in the developer guide that you can reference to begin getting a better understanding of writing your own custom broker. Here is a link to the article: http://help.k2.com/onlinehelp/k2blackpearl/DevRef/4.6.11/default.htm#Custom_Service_Brokers.htm%3FTocPath%3DExtending%2520the%2520K2%2520Platform%7CSmartObjects%7CCustom%2520Service%2520Brokers%7C_____0

Finally, any gaps you need to have filled in you can always post to the community site. There are many developers on the site, including myself, that have experience writing custom brokers who can help clue you in to some of the nuances for writing your own broker.

A few final pieces of advice, if and when you decide to write your own broker.

• Prototype out the code for communicating with the API in a console app outside of K2. This will help you work out the details of talking to the API and ensure that functionality is working before adding the additional complexity of implementing that code inside a service broker.
• Also, during the broker development cycle, the SmartObject Service Tester tool is a valuable assest to have to be able to test your broker. 
• You can attach the Visual Studio debugger to the K2 Service which will allow you to step through your broker code as it is executing hitting break points and stepping through.

Hope this helps.

S.