**The Portal for ArcGIS extension software is included with
ArcGIS for Server Advanced (Enterprise or Workgroup) and is licensed and priced
based on the number of named users.
Specifically with Portal for ArcGIS deployed locally, what does the statement, "is licensed and priced based on the number of named users" mean?
Portal for ArcGIS has a similar licensing model to ArcGIS Online, which is based on named users.
Hope this helps,
Do we have to buy ArcGIS Online "named user" seats to begin to use Portal? Are the "named user" seats one in the same from Online to Portal?
ANY further information on this would be much appreciated. I can't find any solid documentation that says anything other than "Portal" uses "named users". Nothing about what named users are, where you get them - in relation to Portal....
Hi Derek, (good to see you on the forums)
We really need some clarity on this subject - we too are evaluating products like Collector and Sharepoint for ArcGIS - and the pathway of integrating with existing enterprise logins is something we want to consider.
This is our scenario:
- We are building an emergency management portal (using Sharepoint) where people are authenticated via their enterprise login details (across multiple agencies)
- The portal that is being replaced, has realtime maps embedded that are a custom app - and can't be migrated due to technical issues.
- We would like to use the esri sharepoint webpart and/or the JS based templates - however, it sounds like users need to be named users?
We could have up to 30,000 people using this portal during peak bushfires - hence you see our problem.
The current model of ArcGIS Server means to scale to capacity needed, whereas Portal and ArcGIS Online seem to be limited to a set of named users. These are very different models, and it will be a struggle to understand how you can get ArcGIS Server and ArcGIS Portal to work together with such different models. Maybe I have this perception wrong.
Our alternative is to build our own JS map webpart - which is not a preferred option (we like to configure apps rather than having to build them - I know, an anti coding model :-).
Cheers - Anthony
Hi Adam, Anthony,
This answer from Esri's Q&A might shed a bit of light on how the license model of Portal for ArcGIS will work with ArcGIS for Server at 10.3:
UC Q&A | 2014 Esri User Conference
While Portal for ArcGIS is licensed by and ArcGIS for Server is licensed by cores (as Derek mentioned), at 10.3 server licensees will receive a number of Portal named users as part of their ArcGIS for Server license.
With regards to serving 30,000 people, remember that not all of these users will need "named user" accounts. Named users will be given to those in your organization who you want to be able to create and share content (web maps, apps, etc.); however, authors can still publish applications via Portal that enable anonymous access.
Hope this helps.
--
Drew.
Hi Anthony,
Good to hear from you! I hope all is well on your end and it sounds like you're working on an exciting project.
As Drew indicated, at the Esri UC 2014, some key announcements were made regarding ArcGIS for Server licensing:
- At 10.3, ArcGIS for Server Standard will include Portal for ArcGIS;
- At 10.3, ArcGIS for Server users will get additional named users depending on their edition (Workgroup vs Enterprise) and level (Standard vs. Advanced). See the link in Drew's post for details.
These are extra named users in addition to the named users that you get with the ArcGIS for Desktop entitlement (e.g., you get a named user for every license of ArcGIS for Desktop).
As a general rule of thumb, Portal for ArcGIS items (e.g., web map, apps, web services, etc) that are shared with "everyone" can be accessed without a named user account. In your case, it sounds like you will be using enterprise logins for authentication, which means that any member of your Windows Active Directory or LDAP should be able to access and use these public Portal items.
In the case of using the JavaScript application templates and the forthcoming Web AppBuilder (in Portal for ArcGIS 10.3), as long as the finished web apps are shared with "everyone", your end users will not need a named user account to access and work with them.
With regards to Collector for ArcGIS, yes - a named user is required to login to work with Portal for ArcGIS. As for the Esri Maps for SharePoint web part: someone who is authoring the web part in SharePoint will need to be a named user, but a named user is not needed to access the finished SharePoint page (that the web part resides on).
If you have additional questions, please send me an email to discuss further.
Hope this helps,
Derek and Anthony,
Thank you for your time, and sticking with this discussion. The answers are clearer now.
--Adam
Thanks Derek. Any chance there could be a matrix that spells out what you can and can't (based on the type of user) with the apps (Sharepoint, Collector, Operations Dashboard, etc), and if needed, one for Portal and one for ArcGIS Online?
Cheers - Anthony
These are extra named users in addition to the named users that you get with the ArcGIS for Desktop entitlement (e.g., you get a named user for every license of ArcGIS for Desktop).
Derek,
It was said again and again at the UC but it isn't exactly true. If your organization has an ELA you get zero Name Users for your Desktop licenses. Zero. You only get the number of Named Users you negotiate for in the ELA which you also pay for in the ELA. Between concurrent licenses and standalones my agency has around 100 desktop licenses but we could only afford 50 named users in the ELA.