ArcGIS for Server, find publisher of a service?

Unmasking the Publisher: Finding Out Who’s Behind That ArcGIS for Server Service

Ever wondered who actually published that service in your ArcGIS for Server setup? It’s a question that comes up more often than you’d think. Knowing the service’s origin is super important – it helps with everything from fixing problems to keeping your data top-notch and making sure your whole system runs smoothly. Trouble is, ArcGIS Server isn’t always upfront about this info. So, how do you play detective and uncover the publisher? Let’s dive in.

Direct Clues: Your First Stop, Server Manager

Okay, so there isn’t a big, obvious “Published By” field staring you in the face. But Server Manager does drop some hints if you know where to look.

First, check out the “Original Document Path.” Head to the service in Server Manager, give it a click, and then hit the “General” tab. See that “Original Document” section? That’s where you’ll find the “Machine Name” and “Path.” This tells you which machine the service came from and the location of the original file used to create it. It’s not a name tag, but it definitely narrows down the suspects, right?

Next, dig into the metadata. Think of metadata as the service’s “about me” section. If the person who published the service was on the ball, they filled this out. You might just find their name or contact info tucked away in there! You can usually get to the metadata through the item page in ArcGIS Enterprise portal, or in the Catalog view in ArcGIS Pro. For the more technically inclined, you can even tack /info/metadata onto the end of the service’s REST URL to grab an XML file with all the juicy details.

Playing Detective: Indirect Methods to the Rescue

Sometimes, the direct approach doesn’t pan out. Don’t sweat it! We’ve got some backup plans.

Consider the security settings. ArcGIS Server uses roles to control who can do what. By checking the security settings for the service, you can see which users or roles have publishing privileges. This helps you figure out who could have been the publisher. Just a heads-up: from version 10.4 onwards, only admins can publish geoprocessing services and deploy service extensions.

Then there are the log files. ArcGIS Server keeps a record of pretty much everything, including when services are published. Sifting through these logs can be a bit of a pain, but it might just reveal the user account that was used.

Don’t forget the REST API and service definition files. The ArcGIS REST API lets you get into the guts of ArcGIS Server programmatically. When a service gets published, it uses a service definition file (.sd). If you can get your hands on the scripts or processes used to publish the service, examining the service definition file might give you some clues.

And if your ArcGIS Server is buddies with an ArcGIS Enterprise portal (we call that “federated”), the portal’s security rules take over. Service ownership and sharing are all managed through the portal. So, check the item details in the portal to see who owns the service. The good news is you can reassign ownership to someone else if needed.

A Few Things to Keep in Mind

In federated setups, the admin who set up the federation usually becomes the initial owner of the services. But, like we said, you can shuffle things around later.

Seriously, make sure people fill out the metadata! It’s not just about finding the publisher; it helps everyone find and understand the services.

Set up some clear guidelines for documenting when services are published. Write down who published it, why it exists, and any special settings. Trust me, your future self will thank you.

Keep your security tight. Regularly check and enforce your security rules to control who can get into ArcGIS Server and its services. Things like using HTTPS, standardizing queries, and managing those tokens are key.

It’s worth noting that, as of a few years ago (2019 to be exact), there wasn’t a direct way to see service ownership in Server Manager. While ArcGIS Enterprise portal does a better job with content management, it’s still a good idea to have your own way of tracking things internally.

Troubleshooting Quick Tips

Services MIA in the REST Services Directory? Make sure the account trying to access them has the right permissions. Also, double-check that the service directories are there and that the service account has full control.

Service sharing properties acting weird? If things seem to change on their own in a federated setup, look for problems with the portal connection or user permissions.

By using a mix of these tips and tricks, you’ll be able to track down the publishers of services in ArcGIS for Server like a pro, keep things organized, and make sure everyone’s playing by the rules. Happy sleuthing!