With the push towards ArcGIS Enterprise, the successful integration of Portal for ArcGIS has become increasingly important to a smooth deployment of your Web GIS. Portal, though just one component of ArcGIS Enterprise, a few IT-centric system requirements and require a bit of pre-planning. This Spotlight Talk looks at 3 areas in the pre-planning process that can help smooth out the implementation of Portal for ArcGIS.
Access: One of the first decisions to make before deploying Portal, is to decide whether or not you need external access. When making this decision you want to consider your data's sensitivity, the need for public access, whether you need a mobile solution, and the type of security you will implement. Deciding on the access of your Portal will help dictate some other decisions you will need to make when implementing Portal.
Security: There are a variety of ways that you can authenticate your Portal, and it’s important to think about who your users will be, how they will be using the Portal, and most importantly where they will be accessing it from.
SSL/TLS: This is how secure websites leverage HTTPS to encrypt all web traffic. Having a valid TLS will safeguard your sensitive data from being compromised and it happens to be a requirement for running Portal for ArcGIS!
These components are the heavy hitters that you will want to take into consideration when you start to prepare to implement Portal. We recommend starting with a kick it off meeting with your IT department to look at your organizations access needs, security requirements, and SSL/TLS availability. In our experience these are things that can derail a smooth implementation, and even cause some hiccups down the road if not properly considered during the planning stages.