topic Re: Creating basic and standard deployments in Java Maps SDK Questions

Creating basic and standard deployments

MichaelKnight — Thu, 05 Jun 2014 17:36:21 GMT

Hi Guys,

We would like to create two kinds of deployment for our customers. One basic deployment that comes as default with our software and another standard one that can be purchased as an upgrade.

Currently our mapping component is a single jar but it uses both basic and standard ESRI classes.

Is it possible to use this jar for both deployment scenarios along with one deployment of the runtime? Or would we need to create two seperate jar's and runtime deployments to get this to work?

Thanks,
Mike

Re: Creating basic and standard deployments

CarlosColón-Maldonado — Sat, 07 Jun 2014 00:12:16 GMT

Is it possible to use this jar for both deployment scenarios along with one deployment of the runtime? Or would we need to create two separate jar's and runtime deployments to get this to work?

Hi, Mike,

It seems to me that enabling/disabling application features based on license types initialized at start-up would allow you to use one jar. This can be determined by the license level from ArcGISRuntime. However, if you plan on using the LocalServer for execution of "standard" features, you're going to have to figure out when to call it and what would you do instead of using it, e.g., loading map service layers vs. local tile layers that do not require server execution to the map. If you do this right, you may also get away with one deployment package as well (with all features included). You'll know immediately when a standard feature is being used that requires a standard license when you've initialized ArcGISRuntime with a basic one. Those would be the ones I'd disable and inform users of the requirement.

Hope this helps,

Carlos

Re: Creating basic and standard deployments

MichaelKnight — Mon, 09 Jun 2014 06:10:16 GMT

Hi Carlos,

Thanks for the response I will use the single jar approach. What is the easiest way of working our exactly what parts of the SDK lie within each license level for example dynamic workspaces?

I guess one way would be to just apply the basic license and see if I get any exceptions being thrown when using the software.

Thanks,
Mike

Re: Creating basic and standard deployments

MichaelKnight — Mon, 09 Jun 2014 07:05:08 GMT

It seems that I cannot open a .mpk with a basic license is this correct?

Re: Creating basic and standard deployments

MarkBaird — Mon, 09 Jun 2014 08:38:25 GMT

Hi Mike,

An mpk file needs to use Local Server which is functionality which requires a Standard level license.

https://developers.arcgis.com/java/guide/license-your-app.htm

If you attempt to use this functionality with only a Basic license you will get an error in your application.

Mark

Re: Creating basic and standard deployments

CarlosColón-Maldonado — Mon, 09 Jun 2014 11:37:40 GMT

It seems that I cannot open a .mpk with a basic license is this correct?

If you're fund of the look-and-feel of your map package, you could create a tiled layer to replicate it, without all of the functions that can be done with map package contents. You should be able run your app in "basic" mode, then remove these tiled layers and load dynamic layers using your map packages once the license is upgraded on restart or "on-the-fly" (with some work).

What we've decided to do was licensed our app with a developer license when no license file is provided, but only because it suited our situation. As of 10.1.1, ArcGISRuntime warns users of the license being used on the deployed app for testing and evaluation only. I like what they've done at 10.2.3 in watermarking the map when using them.

Regards.

Re: Creating basic and standard deployments

MichaelKnight — Mon, 16 Jun 2014 06:09:31 GMT

We could create a .tpk file from our .mpk and then we could use it within the basic license. However we need a much higher resolution of map than a .tpk offers. We are often required to provide maps of CAD files for internal building schematics.

As a result a .mpk file was best suited to us because it has no limit on the zoom.

Re: Creating basic and standard deployments

MarkBaird — Mon, 16 Jun 2014 06:37:41 GMT

Tile packages (tpks) only work at fixes levels of detail, so you are limited to the scales you can zoom to. This works fine when you know the zoom scales you are working at.

Another alternative is to use the new geodatabase format. You can export this from ArcMap or from a ArcGIS Server Feature Service. If you are only using the data for read only (not editing it), you are free to use these with a Basic level license.

If you need any more information on this let us know.

Mark

Re: Creating basic and standard deployments

MichaelKnight — Wed, 18 Jun 2014 08:20:03 GMT

That's interesting does this new format allow us to zoom in on data in a similar way to using a .mpk based map?

If so then I would certianly be interested in getting further information what SDK level does it require?

Thanks,
Mike

Re: Creating basic and standard deployments

MiguelMartinez1 — Fri, 15 Aug 2014 18:14:48 GMT

Hi Mark,

I have the same problem, I want to load information(just for read, not for edition), I'm trying to use standard license, but if it easier using that kind of functionality please tell me how to do it, now I'm using a TPK(fro base map) and MPK for my info, I can identify on click or mouse over, is it possible to do it using "the new geodatabase format"?

Thanks

Re: Creating basic and standard deployments

CarlosColón-Maldonado — Fri, 15 Aug 2014 22:12:55 GMT

Hi Mike,

I'm a bit intrigued by this "new geodatabase format" that allows you to render its containing data using a basic license so long as it's read-only. Up to this point, I've had to use a standard deployment license just to render rasters off mosaic datasets from a geodatabase unto the map, with no editing capability, because of merely using the LocalServer class. Has this changed? I am interested in getting more information on this.

Thanks,

Carlos

Re: Creating basic and standard deployments

EricBader — Sat, 16 Aug 2014 14:50:42 GMT

Yes, this local geodatabase can be used as a datasource for your feature layers that get added to your map, and they behave just like connected feature layers: zoom in on the map, search and query, etc.

If all you need to do is visualize and query these feature layers, this is a BASIC-level licensing scenario.

If you want to edit these feature layers from the local geodatabase, while disconnected from Internet access, this is a STANDARD-level licensing scenario.

Hope this helps.

Re: Creating basic and standard deployments

JeremieJoalland1 — Mon, 18 Aug 2014 12:32:37 GMT

Could it be possible to have some code sample for this ?

How to add this kind of Local Feature Layer to the map ?

would be great. thanks.

Re: Creating basic and standard deployments

MiguelMartinez1 — Mon, 18 Aug 2014 15:28:33 GMT

Hi Eric,

It's just that I want to do, local data, identify, zoom in and zoom out, some code sample would be great!

Thanks!

Re: Creating basic and standard deployments

EricBader — Mon, 18 Aug 2014 18:20:57 GMT

Once you have a geodatabase file on the file system, you can add feature layers to the map from it...

Geodatabase geodatabase = new Geodatabase(path);

GeodatabaseFeatureTable featureTable = geodatabase.getGeodatabaseFeatureTableByLayerId(0);

// create a feature layer from the feature table

featureLayer = new FeatureLayer(featureTable);

map.getLayers().add(featureLayer);

Once the layer is in the Map, it behaves like any other full-fledged FeatureLayer.

Does this help?