Configuring Message Senders
This section provides guidelines for configuring the components needed to support outbound messages to the GIS system.
Note:
For WACS (OCI Cloud) environment, Http/https in the Message Sender URL should be replaced with the substitution variable @EXT_PUB@. And the ArcGIS Server services should be served over port 443 since only port 443 will be accepted in OCI environment.Define a message sender for each of the outbound message types associated with the GIS Integration web service category using following guidelines.
Message Sender for Work Location
| Field / Context | Value |
|---|---|
| Invocation Type | Real-time |
| Message Class | SOAP: RHTTPSNDR (Send post messages via HTTP real-time)REST: RTJSONSNDR (Sender for real-time HTTP/JSON messages) |
| MSG Encoding | UTF-8 message encoding |
| HTTP Method | POST |
| Active | Yes |
| HTTP URL 1 | The URL of the corresponding service to be provided by GIS
team.
WAM REST Ex: https://xxxxxxxxxxxxx:6443/arcgis/rest/services/WAM/WorkLocations/FeatureServer/0/${pathParms} WACS REST Ex: @EXT_PUB@xxxxxxxxxxxxx:443/arcgis/rest/services/WAM/WorkLocations/FeatureServer/0/${pathParms} WAM SOAP Ex: https://xxxxxxxxxxxxx:6443/arcgis/services/WAM/WorkLocations/MapServer/FeatureServer WACS SOAP Ex: @EXT_PUB@xxxxxxxxxxxxx:443/arcgis/services/WAM/WorkLocations/MapServer/FeatureServer |
| HTTP Header | REST: Content-Type:application/x-www-form-urlencoded |
| HTTP Header | REST: Accept:application/json |
| HTTP Form Data | REST: adds=@XMLMSG@ |
Message Sender for Asset Outbound Sync
| Field/Context | Value |
|---|---|
| Invocation Type | Real-time |
| Message Class | SOAP: RHTTPSNDR (Send post messages via HTTP real-time) REST: RTJSONSNDR (Sender for real-time HTTP/JSON messages) |
| MSG Encoding | UTF-8 message encoding |
| HTTP Method | POST |
| Active | Yes |
| HTTP URL 1 |
The URL of the corresponding service to be provided by GIS team. WAM REST Ex: https://xxxxxxxxxxxxx:6443/arcgis/rest/services/WAM/DistributionNetwork/FeatureServer/${pathParms} WACS REST Ex: @EXT_PUB@xxxxxxxxxxxxx:443/arcgis/rest/services/WAM/DistributionNetwork/FeatureServer/${pathParms} WAM SOAP Ex: https://xxxxxxxxxxxxx:6443/arcgis/services/WAM/DistributionNetwork/MapServer/FeatureServer WACS SOAP Ex: @EXT_PUB@xxxxxxxxxxxxx:443/arcgis/services/WAM/DistributionNetwork/MapServer/FeatureServer |
| HTTP Header | REST: Content-Type:application/x-www-form-urlencoded |
| HTTP Header | REST: Accept:application/json |
| HTTP Form Data | REST: Edits=@XMLMSG@ |
Message Sender for Asset Inbound Sync
Note:
This communication supports REST protocol only.| Field / Context | Value |
|---|---|
| Invocation Type | Real-time |
| Message Class | RTJSONSNDR (Sender for real-time HTTP/JSON messages) |
| MSG Encoding | UTF-8 message encoding |
| HTTP Method | POST |
| Active | Yes |
| HTTP URL 1 |
The URL of the corresponding service to be provided by GIS team. WAM REST Ex: https://xxxxxxxxxxxxx:6443/arcgis/rest/services/WAM/ExtractDeltaChanges/GPServer/${pathParms} WACS REST Ex: @EXT_PUB@xxxxxxxxxxxxx:443/arcgis/rest/services/WAM/ExtractDeltaChanges/GPServer/${pathParms} |
| HTTP Header | REST: Content-Type:application/x-www-form-urlencoded |
| HTTP Header | REST: Accept:application/json |
Message Sender for Token Generation
Note:
This configuration is required only if the underlying map service published in ArcGIS Server are secured.This communication supports REST protocol only.| Field / Context | Value |
|---|---|
| Invocation Type | Real-time |
| Message Class | RTJSONSNDR (Sender for real-time HTTP/JSON messages) |
| MSG Encoding | UTF-8 message encoding |
| HTTP Method | POST |
| Active | Yes |
| HTTP URL 1 |
The URL of the corresponding service to be provided by GIS team. WAM REST Ex: https://xxxxxxxxxxxxx:6443/arcgis/rest/services/WAM/GenerateToken/GPServer/${pathParms} WACS REST Ex: @EXT_PUB@xxxxxxxxxxxxx:443/arcgis/rest/services/WAM/GenerateToken/GPServer/${pathParms} |
| HTTP Header | REST: Content-Type:application/x-www-form-urlencoded |
| HTTP Header | REST: Accept:application/json |
Parent topic: Configuring Legacy GIS Integration