Use the subexpression builder to build complex rule conditions from subexpressions by using AND, OR, NOT and parenthetical grouping. The rule builder validates the rule when you apply the changes, and alerts you to mismatched parentheses, and unsupported logic operators.
To view this administrative console page, click Servers > On demand routers > odr_name> HTTP On demand router properties > Routing policy HTTP rules > Add > Subexpression builder.
To modify rules with the rule builder, you must have administrator administrative privileges.
Depending on the protocol you select, different operands are displayed. The following table includes the operand names as displayed in the console, the actual operand as it will appear in the expression, the valid protocols for each operand, and the description for each operand.
Request variable | Valid protocols | Description | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
application |
IIOP | The name of the Enterprise Application where the EJB is contained. | ||||||||||||||||||
clienthost | HTTP SOAP IIOP SIP |
The fully-qualified client host name. This is the value of the internet protocol (IP) command host name. This operand does not support numeric operators such as >, >=, <, <=. | ||||||||||||||||||
clientport |
IIOP | The client port name. | ||||||||||||||||||
clientipv4 | HTTP SOAP SIP |
The IP address of the client computer using the Internet Protocol version 4 (IPv4) dotted quad address type n.n.n.n. | ||||||||||||||||||
clientipv6 | HTTP SOAP SIP |
The Internet Protocol version 6 (IPv6) 128-bit address type of x:x:x:x:x:x:x:x following Request for Comments 1924 (RFC 1924) of the client computer. | ||||||||||||||||||
Contact header | SIP |
The Contact header field. |
||||||||||||||||||
Contact URI | SIP |
The URI of the Contact header field. |
||||||||||||||||||
cookie$<name> | HTTP SOAP |
A cookie name. For example, the expression cookie$My_Cookie_Name='My_Cookie_Value' tests
a request to see if it contains a cookie named My_Cookie_Name with
a value of My_Cookie_Value. To test for the
presence or absence of a particular cookie, use one of the following
expressions: cookie$MyCookieName IS NOT NULL cookie$MyCookieName IS NULL |
||||||||||||||||||
ejbmodule |
IIOP | The module name of an EJB. | ||||||||||||||||||
ejbname |
IIOP | The name of an EJB. | ||||||||||||||||||
ejbmethod |
IIOP | The name of a method within the EJB. | ||||||||||||||||||
From header | SIP |
The From header field. |
||||||||||||||||||
From header display name | SIP |
The display name in the From header field. |
||||||||||||||||||
From URI | SIP |
The URI of the From header field. |
||||||||||||||||||
From URI host | SIP |
The host in the From header field. |
||||||||||||||||||
From URI port | SIP |
The port in the URI of the From header field. |
||||||||||||||||||
From URI user | SIP |
The user in the From header field. |
||||||||||||||||||
header $<name> | HTTP SOAP SIP |
A header name and value. For example, the expression header$Host='localhost' tests
a request to see if it contains an HTTP host header with a value of localhost.
To test for presence or absence of the host header, use one of the
following expressions: header$Host IS NOT NULL header$Host IS NULL |
||||||||||||||||||
HTTPMethod | HTTP SOAP |
The HTTP method for the request. Possible values are POST, GET, PUT, and DELETE. | ||||||||||||||||||
MIMEType | HTTP SOAP |
The MIME type of the request. | ||||||||||||||||||
operation | SOAP | The name of a Web service operation. | ||||||||||||||||||
percentage$<val> | HTTP SOAP IIOP SIP |
The percentage operand evaluates to true, a fixed percentage of the time. For example, percentage$50 evaluates to true on average 50% of the time. | ||||||||||||||||||
port | HTTP SOAP IIOP SIP |
The listening port on which the request was received. | ||||||||||||||||||
protocol | HTTP SOAP |
The communications protocol that transmits the request. Currently supported protocols are HTTP, HTTPS, SOAP, and SOAPS. | ||||||||||||||||||
queryparm$<name> | HTTP SOAP |
A header name and value. For example, the expression queryparm$timezone='EST' tests
a request to see if the request contains an HTTP query parameter named timezone with
a value of EST. To test for presence or absence
of a query parameter, use one of the following forms: queryparm$timezone IS NOT NULL queryparm$timezone IS NULL |
||||||||||||||||||
rampup$<startTime>$<completionTime> | HTTP SOAP IIOP SIP |
The rampup operand evaluates to true a
variable percentage of the time. It always evaluates to false before <startTime> and
to true after <completionTime>.
As time progresses from <startTime> to <completionTime>,
it evaluates to true, a linearly increasing percentage. The format of <startTime> and <completionTime> is day/month/year::hour:min:sec. where day is the day of the month, month is one of the twelve months: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec, year is the 4 digit year, hour is the 2 digit hour of the 24 hour clock, and min and sec are 2 digit values for minute and second, respectively.For example, rampup$01/Jan/2007::08:00:00$01/Jan/2007::17:00:00 begins to occasionally evaluate to true at 8 AM on Jan 1, 2007 and always evaluates to true by ramp up completion time at 5 PM of the same day. |
||||||||||||||||||
Request transport | SIP |
The transport of the request. |
||||||||||||||||||
Request URI | SIP |
The request URI. |
||||||||||||||||||
Request URI host | SIP |
The host in the request URI. |
||||||||||||||||||
Request URI port | SIP |
The port in the request URI. |
||||||||||||||||||
Request URI user | SIP |
The user in the request URI. |
||||||||||||||||||
Scheme of From header | SIP |
The scheme of the From header field. |
||||||||||||||||||
Scheme of To header | SIP |
The scheme of the To header field. |
||||||||||||||||||
Scheme of URI | SIP |
The scheme of the URI. |
||||||||||||||||||
serverhost | HTTP SOAP IIOP SIP |
The fully-qualified host name of the server. This operand does not support numeric operators such as >, >=, <, <=. | ||||||||||||||||||
serveripv4 | HTTP SOAP SIP |
The IP address of the server computer using the IPv4 dotted quad address type n.n.n.n. | ||||||||||||||||||
serveripv6 | HTTP SOAP SIP |
The IPv6 128-bit address type of x:x:x:x:x:x:x:x following RFC 1924 of the server computer. | ||||||||||||||||||
service | SOAP |
The name of a web service. | ||||||||||||||||||
SIP method | SIP |
The method for the request. Possible values are INVITE, TRYING, RINGING, ACK, OK, and BYE. If the message is not a request, this operand returns null. |
||||||||||||||||||
Response code | SIP |
The response code of the response. If the message is not a response, this operand returns -1. |
||||||||||||||||||
time | HTTP SOAP IIOP |
This operand is used to define the date and time of day that a given request must be honored. Two optional fields are StartTime and EndTime. If a request is received outside of that defined window, the request will not be processed. The Start Time and End Time fields each have the following format: dayOfWeek/dayOfMonth/month/year::hour:minute:second. For example, Thursday, the 11th of April, year 2007 at 1:03:45 PM is specified as: Thu/11/Apr/2007::13:03:45 Any field can use a wild card with the value *. For example, the 1st of each month is specified as */1. The dayofWeek values are Sun, Mon, Tue, Wed, Thu, Fri, Sat, and the dayOfMonth values range from 1-31. The month value is a non-numeric value representing the twelve months: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec. The year value is comprised of the year's four digits. For example, 2007. The hour value is the hour of day in the 24-hour clock. For example, 8am is represented as ::8. The minute and second are integers ranging from 0-59. The forward slash (/) is used to separate date parameters, the double colon (::) is used to separate the date and time values, and the colon (:) is used to separate the time of day parameters. Note that it is the boolean result of the entire rule in which the time operand is used that determines the routing action taken. |
||||||||||||||||||
To client host | SIP |
The client host in the To header field. |
||||||||||||||||||
To header | SIP |
The To header field. |
||||||||||||||||||
To header display name | SIP |
The display name in the To header field. |
||||||||||||||||||
To URI | SIP |
The URI of the To header field. |
||||||||||||||||||
To URI host | SIP |
The port in the URI of the To header field. |
||||||||||||||||||
To URI user | SIP |
The user in the To header field. |
||||||||||||||||||
virtual host | HTTP SOAP |
Virtual portals are created within WebSphere® Portal Server, and WebSphere Extended Deployment supports this operand for better integration with WebSphere Portal Server. The virtual port is the request URL minus the context root for the WebSphere Portal application's web module. If a given request matches the virtual portal defined, then the routing action defined for that rule is taken. | ||||||||||||||||||
xpathexpr | SOAP |
The XPath string expression has a required field
used to contain the XPath expression and an optional field for defining
local namespace(s). If all the name spaces contained in the XPath
expression are standard, then the second field can be optional. If
there are multiple local namespaces, then separate each with a comma
(,). An example of an xpathexpr with one local namespace definition
follows:xpathexpr$/soap:Envelope/soap:Body/m:getTimeZone/n:clientId$m\\=http://test.classify.ws.ibm.com,n\\=http://test2.classify.ws.ibm.com = \\'1000\\' or operation IS NOT NULL In the previous expression , the XPath expression is /soap:Envelope/soap:Body/n:getTimeZone/n:clientId. It contains the local namespace of n. So, the second field of the xpathexpr is defined as n \\=http://test.classify.ws.ibm.com. The dollar sign ($) is used to denote the start of a field definition. The double backslashes are the escape sequence in this example. The first equals sign (=) is escaped because it is part of the local namespace definition, whereas the second equals sign (=) is the operator in the classification expression and must not be escaped. Following is an example of an xpathexpr with two local namespaces: xpathexpr$/soap:Envelope/soap:Body/m:getTimeZone/n:clientId$m\\=http://test.classify.ws.ibm.com,n\\=http://test2.classify.ws.ibm.com = \\'1000\\' or operation IS NOT NULL A list of standard namespaces for xpathexpr follows:
|
Depending on the operator that you choose, type in a value for the subexpression that you are choosing to create.
Generate the subexpression as a result of the operand, operator, and values that you have specified.
Click to append to the box on the rules panel.
WebSphere Virtual Enterprise information center (online)