Select to view content in your preferred language

Migrating your Enterprise publishing workflow in Site Scan for ArcGIS

739
2
07-29-2025 10:24 AM
dozer
by Esri Contributor
Esri Contributor
2 2 739

Overview

The connector tool allows you to publish your processed outputs from Site Scan to ArcGIS Online or ArcGIS Enterprise. On September 30th, 2025 the existing connector in Site Scan will be updated to the 2.1 version, currently in beta. The updated connector includes an improved user interface and faster publishing times. The new version also supports publishing additional data types into ArcGIS Online, including tiled and dynamic imagery layers and Oriented Imagery Layers. 

If you currently use the connector to publish data from Site Scan to ArcGIS Enterprise, or create packages in Site Scan for publishing to Enterprise using the ArcGIS Pro geoprocessing tool, you must complete the migration steps listed below before September 30th, 2025 to avoid disruptions. Once you complete the migration, enable the beta version of the connector and no further changes will be needed by or on September 30th.

At a minimum, this involves reconfiguring the existing Application item in your ArcGIS Enterprise portal. If you use the create packages option in the connector for secure publishing to your Enterprise behind a firewall, this migration also involves downloading and configuring an updated version of the geoprocessing tool. Please read further for detailed migration steps.

Note: If your organization already uses the beta connector, or if your organization only publishes to ArcGIS Online (and not to ArcGIS Enterprise), no further action is needed.

 

In your ArcGIS Enterprise portal

Have an admin perform these steps once for your organization:

  1. Open a web browser and sign into your ArcGIS Enterprise portal. 
  2. In the Content list, open the application item that was created for the Site Scan connector. If you do not see the application, check with your ArcGIS Enterprise administrator, or you can create a new application by following the steps here. If you create a new application, make sure to reconfigure the App ID (Client ID) in Site Scan (Organization Settings > ArcGIS Enterprise).
  3. Open the application item details and click Settings. 
  4. Add https://aid-1.img.arcgis.com/apps/ssfa to the URL in the Application URL field. 
  5. Under Redirect URLs, add the following URLs: 
    https://aid-1.img.arcgis.com/apps/ssfa 
    http://aid-1.img.arcgis.com/apps/ssfa 

    Save the new URLs to the portal app item. Note that prior versions of ArcGIS Enterprise will have a different appearance.Save the new URLs to the portal app item. Note that prior versions of ArcGIS Enterprise will have a different appearance.

    Note
    : In ArcGIS Enterprise version 11.1.x and earlier, the Redirect URLs can be configured by updating the App Registration section.

  6. Click Save.
  7. Copy the Client ID for the next step, if needed.

If your ArcGIS Enterprise publishing workflow involves publishing directly from Site Scan to Enterprise (rather than creating packages then publishing from Pro), you are now finished with the migration. We recommend verifying your updated configuration:

  1. Enable the beta connector (click your organization icon > User Settings > Features).
  2. Browse to a mission and click Share to ArcGIS.
  3. Sign into ArcGIS Enterprise.
  4. Publish the layers that you wish.
  5. After publishing is completed, verify the layer appears in your portal.

If your publishing workflow involves creating packages, complete the steps below to update the GP tool.

Publish packages in ArcGIS Pro: Download and configure the new GP tool

Any user who intends to publish Site Scan packages from ArcGIS Pro should complete these steps.

  1. Download the new geoprocessing tool here. 
  2. Unzip the file. 
  3. Browse to SSFA_PublishingPackagestoArcGISEnterprise > Parameter > Credentials. 
  4. As a best practice, create a copy of the server1.json file. 
  5. Open the original server1.json file. 
  6. Under “portal”, add the values below.
  7.  Save server1.json and close the file. 
"portal": { 
        "url": "<ENTER_PORTAL_URL>", 
        "admin": { 
            "username": "", 
            "password": "", 
            "appid":"<ENTER_CLIENT_ID>", 
            "cert_file": "", 
            "key_file": "" 
        }, 

Note: You may optionally include your username and password; if you do, it will override the credentials for the current user signed into ArcGIS Pro during publishing. 

Enable the beta connector and verify your new configuration 

It is highly recommended to test your updated configuration ahead of time using the connector v2.1 beta version so that there are no surprises when the switch is rolled out on September 30th.

  1. Log into Site Scan. 
  2. Enable the ArcGIS Connector v2.1 by clicking on your organization icon in the bottom left corner > User Settings > Features. 
  3. Confirm the Enterprise Portal information is saved to the Site Scan organization (requires Site Scan administrator role). Browse to Organization Settings > ArcGIS Enterprise, and see that the Portal URL and Client ID (App ID) are saved and match the values in the server1.json file. If your portal uses IWA, ensure that the IWA option is checked. 
  4. Browse to a mission that has data you want to publish for your secured Enterprise. 
  5. Click Share to ArcGIS and choose ArcGIS Enterprise.
  6. When prompted, sign into ArcGIS Enterprise. 
  7. Add an item name and specify additional options that you wish.
  8. Choose the layers you want to create a package for.
  9. Click Create Package at the bottom. This step may take between 10 minutes to an hour. You can view the status of the jobs by clicking the Check Status tab.
  10. Open ArcGIS Pro. 
  11. Sign into your ArcGIS Enterprise and select it as your active portal. 
  12. In the Catalog, under Toolboxes, remove any existing SSFA_Connector toolboxes from the project. 
  13. Add the new SSFA_Connector toolbox by right clicking on Toolboxes and choosing Add Toolbox. 
    Add a toolbox to your project in ArcGIS Pro.Add a toolbox to your project in ArcGIS Pro.
  14. Browse to the location of the new GP tool > Tools > SSFA_Connector.pyt. Click OK.
  15. Open the Publish SiteScan Package tool. 
    Expand the toolbox and open the publishing tool.Expand the toolbox and open the publishing tool.
  16. Select the item you want to publish. Items will only appear after they have been successfully packaged in Site Scan. 
     
    Note: If items still are not appearing in the dropdown after they are successfully packaged in Site Scan, verify the server1.json file is correctly configured by double checking the Portal URL and Client ID match between the file, Site Scan, and the Application item in the Portal. Close and reopen ArcGIS Pro and load the tool again. 
     
  17. Click Run. 
  18. Once the tool completes successfully, verify that the data is now in your ArcGIS Enterprise Portal content list.

Automating your workflow

You may also automate the publishing workflow using the batch file (browse to Batchfiles > automate.bat) included in the new GP tool download folder by using Windows Task Scheduler. By running the automation file, you do not need to manually run the GP tool in ArcGIS Pro to publish packages.

For more information on configuring the automation workflow, or more information about the Enterprise configuration in general, see the updated documentation. 

If you have trouble during the migration, please contact technical support.

2 Comments
AustinOffice
Occasional Contributor

What are the rest of the instructions for updating the GP tool? I think there's some missing steps about what to do with the json file after it's been saved. 

dozer
by Esri Contributor
Esri Contributor

Hi @AustinOffice , once you configure and save the new json file as specified in  the section, 'Publish packages in ArcGIS Pro: Download and configure the new GP tool,' the new version of the GP tool should be ready to use in ArcGIS Pro. Just make sure to remove the old SSFA tool from your toolbox in Pro, if it's there already, then add the new tool that you just downloaded/configured (see steps 12-16 under the section 'Enable the beta connector and verify your new configuration').

Contributors