Where does ArcGIS Server copy data to?

Where does ArcGIS Server copy data to?

The copied data is placed in a folder on one of the ArcGIS Server machines. The exception to this is if your ArcGIS Server site has a managed database and you publish a feature service or WFS-T service; in that case, the data is copied to the managed database.

How do I register a geodatabase with ArcGIS Server?

For file geodatabases, use the option described in the subsequent section titled Register a folder.

1. Sign in to ArcGIS Server Manager, and click Site > Data Stores.
2. Click the Register drop-down arrow and select Database.
3. Provide a unique name for the registered database.
4. Click Import.

How to add data to the ArcGIS Server?

If the publisher’s machine and the ArcGIS Server site will reference data in the same folder, specify the publisher’s folder path and set the ArcGIS Server site’s folder path to Same as publisher’s path when registering your data. This scenario is just like the previous one, except it uses folders, not databases.

Can a publisher reference the same database as an ArcGIS Server?

If the publisher’s machine and the ArcGIS Server site will reference the data in the same database, workgroup geodatabase, or enterprise geodatabase, import the publisher’s database connection and set the ArcGIS Server site’s database connection to Same as publisher’s connection when registering your data.

How to maintain a separate copy of geodatabase?

If you want to maintain a separate copy of the data in your enterprise geodatabase for web use. If the publisher’s machine and the server are working out of the same folder, specify the publisher’s folder path and set the server’s folder path to Same as publisher’s path when registering your data.

Why do I need to register my ArcGIS Server?

As a server administrator, you have the option to register your data folders and geodatabases with ArcGIS Server. Data registration gives the server a list of locations that the GIS server can access and also helps the GIS server understand how to adjust data paths when publishing across machines.