The API for Context Variables

Set and get the predefined context variables. (It is not necessary (or even legal) to declare or remove the predefined context variables.)

Mediator provides the following Java services, which are defined in the class ISMediatorRuntimeFacade.java:

Use this Java service to retrieve a context variable’s value and assign it to a pipeline variable. All parameter names are case-sensitive.

Parameter	Pipeline Type	Data Type	Description	Examples
MessageContext	in	Object ref	This object is inserted into the pipeline by Mediator.	N/A
varName	in	String	Context variable name (predefined or custom).	PROTOCOL_HEADERS SOAP_HEADERS mx:CUSTOM_VAR
serValue	out	Object ref	Java.io.serializable value. (Usually a string).

All context variable values are typed as either string or int except for the predefined context variables PROTOCOL_HEADERS and SOAP_HEADERS, which are of the type IData. You can set or get values for PROTOCOL_HEADERS and SOAP_HEADERS in one of two ways:

Set the varName parameter in pub.mediator.ctxvar:setContextVariable to PROTOCOL_HEADERS or SOAP_HEADERS.

Set the varName parameter in pub.mediator.ctxvar:getContextVariable to PROTOCOL_HEADERS or SOAP_HEADERS.

If varName is set to PROTOCOL_HEADERS, you will get/set the entire IData structure containing all of the transport headers. The key is the transport header name (for example, Content-Type) and the value is a String. The IData object for PROTOCOL_HEADERS will contain a set of string values where each IData string key matches the header name in the transport headers map. The set of possible keys includes the HTTP v1.1 set of headers as well as any custom key-value pairs you might have defined.

If varName is set to SOAP_HEADERS, you will get/set the entire IData structure containing all of the SOAP headers in the SOAP envelope. The key is the array position starting with 0, and the value is an Axiom OMElement containing that SOAP header block.

Alternatively, you can set the varName parameter to address a specific element in the array. For example, setting it to PROTOCOL_HEADERS[Content-Type] would apply to the Content-Type transport header. Similarly, setting it to SOAP_HEADERS[0] would return a String representation of the first SOAP header block (as opposed to an Axiom OMElement).

Set the varName parameter in pub.mediator.ctxvar:setContextVariable to PROTOCOL_HEADERS[arrayElement], where [arrayElement] refers to a specific element. For example, PROTOCOL_HEADERS[Content-Type] or SOAP_HEADERS[0] (to indicate the first array element in the set).

Alternatively, use the method ISMediatorRuntimeFacade.setContextVariableValue(). You would use this method only if you are writing a Java service and you want to access it through the Java source code.

Set the varName parameter in pub.mediator.ctxvar:getContextVariable to PROTOCOL_HEADERS[arrayElement], where [arrayElement] refers to a specific element. For example, PROTOCOL_HEADERS[Content-Type] or SOAP_HEADERS[0] (to indicate the first array element in the set).

Alternatively, use the method ISMediatorRuntimeFacade.getContextVariableValue(). You would use this method only if you are writing a Java service and you want to access it through the Java source code.

You can set or get a nested value inside PROTOCOL_HEADERS and SOAP_HEADERS through an additional keyName. In this case, the object reference will not be an IData object.

For PROTOCOL_HEADERS, the keyName must match the transport header name in a case-sensitive manner (for example, PROTOCOL_HEADERS[Content-Type] or PROTOCOL_HEADERS[Authorization]). In this case, the Serializable value will be a string.

For SOAP_HEADERS, the keyName must match the 0-based array element. If a request has a SOAP security header element (that is, </wsse:Security>), then it would be addressed as SOAP_HEADERS[0]. In this case, the element will be in its string format.

Use this Java service to set a value on a context variable. The pipeline variable containing the context variable value should be an object reference that implements java.io.Serializable. All parameter names are case-sensitive.

Parameter	Pipeline Type	Data Type	Description	Examples
MessageContext	in	Object ref	This object is inserted into the pipeline by Mediator.	N/A
varName	in	String	Context variable name (predefined or custom).	PROTOCOL_HEADERS SOAP_HEADERS mx:CUSTOM_VAR
serValue	in	Object ref	Java.io.serializable value. (Usually a string).

Use this Java service to declare a custom context variable. All custom-defined context variables must be declared in a custom namespace that is identified by using the prefix mx (for example, mx:CUSTOM_VARIABLE). All parameter names are case-sensitive.

Note:
It is not legal to use this service to declare the predefined context variables; you can only declare custom variables.

Parameter	Pipeline Type	Data Type	Description
ctxVar	in	Object ref	The document type defining the context variable object. Use the ctxVar Document Type provided in the Java service pub.mediator.ctxvar:ctxVar and map it to this input variable. Define the name (for example, mx:CUSTOM_VARIABLE), the schema_type (string or int), and isReadOnly (true or false).
ctxVar	out	Object ref	The set Context variable document type.
varNameQ	out	Object ref	javax.xml.namespace.QName value. The QName of the variable.

After declaring the context variable, you can use the setContext variable to set a value on the context variable.

The predefined context variables provided by Mediator. If you attempt to declare an existing predefined context variable, an error will occur.

Any custom context variable that you define in a routing rule that you create in the context-based routing step.

Any custom context variables that you explicitly declare in source code using the API will have a declaration scope of SESSION.

Any custom context variable's state that is defined during the inbound request processing steps will still be available during the outbound response processing steps.

All context variable values are typed as either string or int (excluding the SOAP_HEADERS and PROTOCOL_HEADERS variables, which are of the type IData).

Valid names should be upper case (by convention) and must be a valid Java Identifier. In general, use alpha-numerics, $ or _ symbols to construct these context names. Names with punctuation, whitespace or other characters will be considered invalid and will fail deployment.

All custom context variables must be declared in a custom namespace that is identified by using an mx prefix (for example, mx:CUSTOM_VARIABLE).

To reference a custom context variable in a flat string, you need to prepend a $ symbol to the context variable name to indicate that variable’s value should be referenced. Think of this usage as being similar to the & address operation for C variables.

Notice that the values of the data type “int” are not enclosed in quotation marks, while the values of the data type “string” are. The quotation marks are only needed if a context variable expression (as opposed to a reference) is defined.

Use this Java service to remove a custom context variable from a request/response session. All parameter names are case-sensitive.

It is not legal to use this service to remove any predefined context variables; you can only remove custom variables.

Parameter	Pipeline Type	Data Type	Description	Examples
MessageContext	in	Object ref	This object is inserted into the pipeline by Mediator.	N/A
varName	in	String	Custom context variable name.	mx:CUSTOM_VAR

This flow service declares a pipeline variable named customName, which is set to the value mx:COMP_TEST.

This flow service will retrieve the context variable for customName and create an element for its context variable value in the response message return to the consumer.

We define the customName variable value to be mx:COMP_TEST so we can use this variable to lookup the custom variable name that was seeded in the previous example.

The call to pub.mediator.ctxvar:getContextVariable retrieves the value of the custom context variable from the context variable map.

This is just a sample Java service that takes the context variable and creates a top-level element in the response message using the same name and value.

This flow service declares a pipeline variable named customName, which is set to the value mx:COMP_TEST.

This flow service will retrieve the context variable for customName and create an element for its context variable value in the response message return to the consumer.

We define the customName variable value to be mx:COMP_TEST so we can use this variable to lookup the custom variable name that was seeded in the previous example.

The call to pub.mediator.ctxvar:getContextVariable retrieves the value of the custom context variable from the context variable map.

This is just a sample Java service that takes the context variable and creates a top-level element in the response message using the same name and value.