Service/Policy Context Variables
The following table lists the context variables related to services and policies.
gateway90
The following table lists the context variables related to services and policies.
Variable | Description |
|---|---|
${assertion.latency.ms} | Returns the assertion latency in milliseconds. |
${assertion.latency.ns} | Returns the assertion latency in nanoseconds. |
${assertion.number} | Returns the number of the current assertion. This is a multivalued variable. |
${assertion.numberstr} | Returns the number of the current assertion as a string (for example, "1.2.1.4". This is useful for locating an assertion when viewing a service policy. For more information, see Assertion Numbering. |
${policy.guid} | Returns the GUID of the current policy. When not used in a policy fragment, this context variable behaves the same as ${service.policy.guid} . |
${policy.name} | Returns the name of the current policy. |
${policy.version} | Returns the active revision of the current policy. When not used in a policy fragment, this context variable behaves the same as ${service.policy.version} . |
${service.defaultRoutingURL} | This variable allows routing assertions to be updated when a service endpoint changes following a change in UDDI.
The value of this variable is used in the routing assertion when publishing a new SOAP service. This context variable is read only. |
${service.name} | Returns the name of the protected service (the service published on the API Gateway ). |
${service.oid} | Returns the entity ID of the service policy. This entity ID is also displayed on the [ General ] tab of the Published Service Properties dialog. For more information, see Service Properties. |
${service.policy.guid} | Returns the GUID of the service policy. This GUID is also displayed on the [ General ] tab of the Published Service Properties dialog. For more information, see Service Properties. |
${service.policy.version} | Returns the active revision of the service policy. |
${service.resolutionUri} | Returns the current resolved service's resolution URI (for example, "/custom/foo/ /bar/ " ) if any. This is useful for logging and analytics purposes as this information may not be easily obtained from the actual $ {request.url} |
${service.url} | This context variable is deprecated and replaced by ${httpRouting.url} . You should adjust your service policies to use the new variable instead. |