Service interceptors follow a developer-administrator workflow, with each role carrying distinct responsibilities throughout the interceptor lifecycle. Developers create interceptors using Java, the only supported language, and package them using the tools provided by the ArcGIS Enterprise SDK. Administrators then register these interceptors with ArcGIS Server to activate them.
Developer
The developer is responsible for creating service interceptors using the ArcGIS Enterprise SDK. The process involves the following steps:
- Installing the ArcGIS Enterprise SDK and its prerequisites on the development machine.
- Installing the Maven archetype deployed by the ArcGIS Enterprise SDK to bootstrap development.
- Writing the interceptor logic in Java. To get started with writing a service interceptor and packaging its code into an
.interceptorfile (custom deployment package) for deployment, see Quick Tour of Service Interceptors.
Administrator
The administrator is responsible for deploying and managing service interceptors within an ArcGIS Enterprise or a standalone ArcGIS Server environment. The administrator decides which services the interceptor runs on. The process involves the following steps:
- Deploying the
.interceptorfile with ArcGIS Server. - Managing interceptor properties, such as the URL pattern and description.
- Enabling or disabling interceptors as needed.
- Defining the execution order when chaining multiple interceptors.
Once deployed, service interceptors activate immediately and start intercepting requests from target services, enabling organizations to extend and customize the behavior of their services in innovative and impactful ways.