nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Service Publishing Basics 10.2.2

DaveTenney

All,

just a general best practice question for everyone, any and all input is welcome!

If a project has been built on Machine A that is within Environment 1 and published as a service. Can the mxd and associated data just be copied over to Machine A within Environment 2 and be published as a service? or would it be best practice to copy over associated data and rebuild the mxd before publishing?

thank you all for your input on the matter!

Dave

Find more posts tagged with

Accepted answers

dewright_ca

No, there should not be a issue with that; again the key is making sure you have the paths in a similar structure for the MXD to DATA relationship; and that you have registered the data-sources properly with the server.

I do this between 3 environments and have no issue promoting servers from DEV to TEST to PROD.

All comments

dewright_ca

If your services use the same data-path structure; and you have the data folder/s or database connection/s setup in both environments using the same names; then you should be able to take the service from 1 and publish it to 2.

DaveTenney

is there anything wrong with doing what I outlined with the idea that the data would be copied over and local incase Machine A in Environment 1 happens to implode we still have the data locally on Machine 1 in Environment B?

thanks David for the response

Dave

dewright_ca

I do this between 3 environments and have no issue promoting servers from DEV to TEST to PROD.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.