Showing 8 result(s) for category: ArcGIS Server

Start the New Year with ArcGIS 10.5 and Geocortex

Esri’s ArcGIS 10.5 is now available and we’re excited for what it has to offer Geocortex customers. This major release not only includes stability enhancements and improved functionality; it represents a big leap forward for Esri’s emerging Web GIS pattern, and makes it significantly easier for organizations to begin taking advantage of the modern pattern’s powerful capabilities.

 

 ArcGIS Enterprise: A Major Advancement in the Server Platform

ArcGIS Server is being renamed to ArcGIS Enterprise. Beginning at 10.5, ArcGIS Enterprise licensees will be able to take advantage of the ArcGIS Server, Portal for ArcGIS, ArcGIS Web Adaptor, and ArcGIS Data Store components under one license. The transition to ArcGIS Enterprise is straightforward and will continue to provide customers with deployment flexibility; you will now be able to deploy a complete web GIS in your own infrastructure.   

New ArcGIS Membership Levels

Another important advancement in 10.5 is the introduction of new membership levels. Level 1 membership is for users who only require viewing privileges for maps and apps that have been shared with them through the organization. Level 2 membership is for members who require the ability to view, edit, create and share content.

The new membership levels make web GIS more cost-effective and allow you to better tailor your deployments. You can learn more about the new membership levels here.

Geocortex & ArcGIS 10.5

Our product development and QA teams have been testing ArcGIS 10.5 pre-release software extensively over the past couple months, and we are very pleased to announce that the Geocortex product suite is completely compatible with 10.5.

"Portal for ArcGIS is central to our modern Geocortex product strategy."

Geocortex Essentials provides seamless integration with Portal for ArcGIS, and can leverage both web maps and map services (secured and anonymous) stored in Portal for ArcGIS or ArcGIS Online. One of the most powerful implications is that if a protected web map is used to build a Geocortex viewer application, the application will honor the security and prompt users to log-in with their ArcGIS identities.

Let us Help

We think that there has never been a better time to consider making the move to a modern web GIS. Geocortex will increasingly include tie-ins, dependencies, and value adds to Portal for ArcGIS and ArcGIS Online; the release of ArcGIS 10.5 makes it much easier for you to take advantage of the new pattern.

Many organizations may not be fully equipped to deploy modern Geocortex and Esri technology. Our ArcGIS Implementation Services team can help you navigate the transition, and fast-track effective deployments of Portal for ArcGIS and related technologies.

To learn more about how we can help you take advantage of web GIS in 2017, get in touch with us at arcgis-services@latitudegeo.com.

 


Geocortex Essentials 2.0 and ESRI’s Developer APIs

UPDATE: This message was originally posted for our customers on the Geocortex Support Center on October 6, 2008 and is posted here for folks who don't have access to the Geocortex Support Center. Also, here's the link to the Geocortex Essentials: The Road Ahead webinar.

I’m posting to provide some insight into current and upcoming Geocortex Essentials development, as it relates to ESRI’s new and emerging developer APIs.

It is clear to us that these APIs will have an integral role to play (alongside Web ADF) for many customers in the years to come and so we are actively engineering Geocortex Essentials 2.0 to encompass these developer technologies.

Agnostic support and integration for various ESRI developer technologies (as they come into existence) has always been part of the long-term vision for Geocortex Essentials and so our work has always been designed to be exposed in an agnostic way at some point in the future. With the intense demand for Web ADF features and the absence of other APIs, Geocortex Essentials development has been focused on the Web ADF realm for the 1.x product generation, while ensuring we we could make the core elements generic once warranted. And that’s what we’re doing right now.

We’re currently working on a Geocortex Essentials REST API to initially expose search, reporting, data linking and printing via a RESTful interface. This functionality can then be leveraged by either Javascript or Flex API applications—or any other application that connects RESTfully to our API. We decided to expose these particular core elements because they’re needed at the heart of many real-world ArcGIS Server implementations. Let us know if other features are a priority to your organization.

Before long, we’ll also get behind one or more lightweight viewer APIs by developing software to streamline and enhance the development and management of applications built on them. While we’re working with each and may provide sample Javascript and Flex API template applications on which to base development, we have yet to “pick a pony” regarding technological emphasis on the lightweight viewer/application development side. We don’t think all the information is available yet to ensure the correct decision, and we’re confident our customers won’t want us to risk going down the wrong path by making a premature choice.

We’re anticipating a Q1 2009 release of version 2.0. Finally, because Geocortex Essentials is about success with ArcGIS Server, everything we’re talking about here will be delivered to you as part of regular product updates.


Group Layers in Cached ArcGIS Server Map Services

Christian passed along a tip for when creating cached ArcGIS server map services that he picked up at this year’s ESRI International User Conference. When creating a cached map service, create an ArcMap “group layer” containing all the layers for each specific scale level.

By grouping layers by scale, you can quickly turn off and on the groups to define symbology and labels for each without concerning yourself with the other scale levels. You can also tell at a quick glance what information is available at each scale level.


Post-San Diego Commentary

I intended to blog once or twice during the ESRI International User Conference, but found my conference schedule and meetings all-consuming. This was our seventh time exhibiting at the conference, and I think it was the best one yet. ArcGIS Server 9.3 is what we hoped it would be, the new/emerging developer APIs are valuable, and I generally think ESRI is on the right track. I’m excited about the coming year.

Since it was first released, I’ve been very candid about my perspective on ArcGIS Server 9.2 (that it was the future but not quite ready for prime-time). This has caused consternation among some, but I always defended my position because our customers count on us for advice about technology and timing.

I’ve always contended that, regardless of new capabilities, the majority of ESRI customers will be reluctant to move from ArcIMS to ArcGIS Server until the shift doesn’t involve any significant steps backward from ArcIMS. There have been two main aspects to this; comparable performance and comparable functionality.

I think I can now see the tipping point. Aside from the general improvements in 9.3, during the plenary on Monday afternoon, ESRI announced that the new rendering engine for ArcGIS Server (which everyone was expecting as part of 9.4) would ship as part of ArcGIS Server 9.3 Service Pack 2 in January or February 2009. Even though you can actually do lots to improve performance (Mapservice/application tweaking and pre-rendering), this is big news for organizations that have been awaiting improved performance that doesn’t require much rearranging of the furniture.

As for the latter aspect (functional parity), the complementary use of Web ADF and the new developer API’s allow/will allow functionality, ease-of-development, and ease-of-use to be taken to the next level. We’ve been working hard over the last twenty months to be prepared with comparable and/or superior functionality (relative to ArcIMS-gen technology) in time for ESRI’s release of comparable performance. And we’re nearly there.

Bottom line… things are falling into place. Last year, we talked mostly with people who wanted to learn more about ArcGIS Server. This year, we talked mostly with people serious about getting going with ArcGIS Server. I predict 2009 will be remembered as being a significant year in the widespread transition from ArcIMS to ArcGIS Server.


ArcGIS API for Flex

The JavaScript/REST APIs have been generating lots of buzz, but I think the (really) new Flex API is awesome too and will garner lots of attention at ESRI’s International User Conference next week. Check out the samples:

http://resources.esri.com/arcgisserver/apis/flex/index.cfm?fa=samples

ESRI has clearly been hard at work on this, and it seems pretty slick. I can't say for sure yet, but I'd guess that a lot of the work that was put into ArcWeb Services was leveraged, and it appears to offer most of the functionality needed to build a basic site with Flash.

We’re doing plenty of work to incorporate emerging technologies like this into Geocortex Essentials in an agnostic way, but for 2.0 we’d planned to concentrate on leveraging the heck out of the JavaScript/REST APIs alongside Web ADF. But the more I play with this, the more I want to cover the Flex API right away too. It’ll be interesting to see how people react to this next week; this will help guide our decision.


Geocortex Essentials Betas available

Well, I'm happy to blog that two weeks after the release of ArcGIS Server 9.3, we're offering full Geocortex Essentials compatibility. I must concede that this work didn't take two weeks; it took a couple months (we were very busy during the Beta program during which we made some educated guesses that proved correct).

We're actually releasing two new versions of Geocortex Essentials: Geocortex Essentials 1.3.1 Beta, and Geocortex Essentials 1.4 Beta. 1.3.1 is a maintenance release in the ArcGIS Server 9.2 edition of Geocortex Essentials. It contains updated language resources and bug fixes for customers who've built apps on 9.2. 1.4 is the big release that supports ArcGIS Server 9.3.

It has been a pleasure to start using the new features in Web ADF 9.3. Most notably (for developers):

  • The new Web ADF JavaScript object model (not to be confused with the JavaScript API released in tandem with ArcGIS Server 9.3, which is also cool and we're doing lots of work with)
  • Support for MS AJAX partial postbacks which will streamline future development (thankfully, adding full support for partial postbacks wasn't as arduous as we thought it might be)

Maybe we've been staring at it too long, but it appears the long-awaited 9.3 performance improvements are quite noticeable (we'll be able to quantify these improvements once we start playing with the Geocortex Optimizer Alpha in a couple weeks). Cool.

Next, maximizing the performance of Essentials (which has never received that much attention because we didn't really worry that much about our stuff being a bottleneck with 9.2) will be a core focus during the next couple 3-week iterations.

But first, I think the team is going to enjoy Latitude's annual "4th of July" picnic this afternoon/evening up at Shawnigan Lake.



Geocortex Optimizer for ArcGIS Server

optimizerThough we announced it last month at our user conference, I want to post briefly about Geocortex Optimizer, our new product for ArcGIS Server we're timing for release around the ESRI International User Conference in San Diego this year.

Geocortex Optimizer is comprised of four distinct modules (think our ArcIMS-generation Geocortex Statistics and Geocortex Uptime products rolled into one, plus more) that will maximize the value and effectiveness of an investment in ESRI’s next-generation web-based GIS foundation. Initial versions will focus on maximizing ArcGIS Server performance and distributed system performance monitoring, with emphasis shifting to ease-of-management and the ROI calculation side of things.

This has been a challenging and exciting project that is really taking shape and that I think is going to appeal to single server organizations, large enterprises, and everyone in between. Now that the original design is coming to life and the team has some great momentum, we're getting really excited about this product.

Notwithstanding any unforeseen technical hurdles in the next couple iterations, we should be announcing a Beta program fairly soon. Let us know if you're interested in participating.