Field | Description |
Service Name | Fully qualified or partial name of services to find (such as OrderPartner.Services:processOrder) or processOrder). Note: The top, unlabeled text box on the Advanced search tab and the Service Name field are both for specifying the full or partial name of the services to find. Use only one of these two fields. |
Server ID | Integration Server on which the services to find ran or are running. Type the Integration Server's DNS name and port (such as integration.east.rubicon.com:5555) or partial DNS name or port (such as rubicon). |
Context ID | Full service context ID of services to find. |
Root Context ID | Full root context ID, to find all services that were invoked one after another starting with the specified root service. |
Parent Context ID | Full parent service context ID, to find all services invoked by the specified parent service. |
Status | Status of services to find. To select multiple statuses, hold down the CTRL key while selecting each status. For information about statuses, see
Service Statuses. |
User | Full or partial user name of the client that invoked services to find. |
Activity Message | Full or partial message entered in the Full Message field in the Activity Messages panel on the Service Detail page. The Full Message field is populated if a service logs user-defined messages by calling the pub.prt.log:logActivityMessages service. |
Filter By | Predefined date option to narrow the search. Choose Date Last Updated to search for services based on the most recent date and time service data was logged. Choose Start Date to search for services based on when services were started. |
Range area | Search for services based on the most recent date and time data was logged for the services. You can choose a predefined time period in the Range list, or you can use the calendar pickers to specify a Start Date and End Date and then select the numbers for the hours and minutes from the lists. Note: If you want to add the search results to a My webMethods workspace, using a predefined time period causes the search results on the workspace to be dynamic, showing data relative to the current date (for example, yesterday). Using exact start and end dates causes the search results to always contain data for the specific dates you use, regardless of the current date. |
Field | Description |
Log Field Name | Full name of a custom logged field to use for the search. The field name is case-insensitive. Wildcard characters are not supported. |
Operator | Select the operator to use: Equal, Contain, or NotContain, != , < , >, <= , >= |
Value | Specify the value to use for comparison. Click Add Row to specify additional fields. |