Console Perspective

The Console perspective displays a real-time view of all integration processes handled by a Taleo product.

The console perspective uses a single editor, the message list viewer, that lists all the messages in a Taleo product matching a particular criteria. This perspective distinguishes between the message and the document contained in the message.This perspective offers multiple views that analyze each message from different angles.

Message List Viewer

The Message List Viewer is an editor that primarily shows a list of messages from the target Taleo Connect Server. Technically, it is an editor, since the profile of the target Taleo Connect Server can be edited and saved here.

The information available in the message list is:

  • Identifier: A universally unique external identifier for the message.

  • Type: Determines if the message is a request or a response.

  • State: The current position of the message in the Taleo Connect Server processing workflow.

  • Creation Date: Indicates the date and time the message was received or created by the Taleo Connect Server.

The three actions available in the Message List viewer are:

  • Refresh the current list of messages.

  • Filter the list of messages according to a set of criteria.

  • Edit the profile of the target Taleo Connect Server.

Filters

The Filters define which messages will be part of the displayed list. The available filters are:

  • Key: Filters the messages based on whether the key matches the exact value provided. Since the message key is a unique value within a Taleo Connect Server instance, specifying a value here guarantees that a single message will be displayed.

  • Identifier: Filters the messages based on the whether the identifier contains the value provided. For example, using the value 'Candidate' would match 'CandiateImport-2006-03-12' and 'Extract-Candidates-2005-12-12'.

  • Conversation: Filters the messages based on whether the conversation contains the value provided. This is the same behavior as the Identifier filter.

  • Target: Filters the messages based on whether they are requests or responses. The Request option is an alias for the Application target. The Response option includes the Middleware, External, and Queue targets.

  • State: Filters the messages based on their state in the Taleo Connect Server workflow. The Incomplete option matches all states except In Progress.

  • Date: Filters the messages based on their creation date in the Taleo Connect Server. Selecting a specific date shows all messages from 00:00:00 to 23:59:59, local time of the computer running the Taleo Connect Console. Selecting a range of dates shows all message from 00:00:00 of the 'from' date to 23:59:59 of the 'to' date, local time of the computer running the Taleo Connect Console.

Profile

A Profile defines the connectivity information required to access the Taleo Connect Server embedded in a target Taleo product. The general information of a profile is:

  • Description: Information with no functional significance. May be used by customers to distinguish or identify profiles.

  • Version: The version of the target Taleo Connect Server. This value determines the communication protocol and the available features.

The connectivity information of a profile is:

  • Protocol: The type of HTTP communication used: plain HTTP or secure HTTPS.

  • Host: The host alias or the IP address of the target Taleo product.

  • Port: The port number of the target Taleo product.

  • Dispatcher: The location of the target Taleo product web service dispatcher entry point. For the Taleo Professional product this is /servlets/ServiceDispatcher?ServiceName=. For other Taleo products, the value is /product name/ServiceDispatcher?ServiceName=.

  • Username: The username required to authenticate web service requests to the Taleo Connect Server.

  • Password: The password required to authenticate web service requests to the Taleo Connect Server.

Message Details

The Message Details View shows the top level information of the integration message

  • Key: An internal identifier used by the Taleo Connect Server embedded in a target Taleo product. The message key's only external use is to uniquely associate request and response message instances. The key values are only unique within a particular Taleo product.

  • Identifier: A universally unique external identifier for the message. It is used by external systems to link messages within larger business processes.

  • Conversation: An identifier that loosely links several messages together in a business process. This is not a transaction identifier in the usual sense of the word (including two-phase commit and integrity concerns). A conversation is only used for monitoring purposes. In particular, a response generated by a Taleo Connect Server will always have the same conversation identifier as the request message (if none was provided, then the conversation identifier of the response will be the message identifier of the request).

  • Target: Determines the processing target in the Taleo Connect Server.

    Application indicates that this message contains a request and is to be processed by the Taleo product.

    Middleware or External indicates that this message contains a response and is to be pushed to another application.

    Queue also indicates that the message contains a response, but that the message should remain within the Taleo product and will be polled by an external party.

  • State: Either a Request or a Response. An integration message is a generic transmission from a source to a target application. The concept of request and response is only linked to the business document contained within the message.

  • Service: The unique identifier of the processing strategy of the Taleo Connect Server. This value only apply to messages with an Application target, i.e. request messages.

The full raw message content is available using the show full message action.

Message Actions

Under certain specific circumstances, it is possible to interact with messages from the console.

  • Suspend halts the processing of a message. This action is only applicable to request messages that are in the In Progress state. A signal will be sent to the Taleo product and the message will be marked as Suspending; the actual suspension is dependent on the type of processing and may not be immediate.

  • Resume resumes the processing of a message. This action is only applicable to messages that are in the Suspended or Interrupted states. The result of this action is to mark the message as Ready so the Taleo Connect Server will process it through the normal message queue. In the case of a request message, the processing will start after the last complete record. In the particular case of an export request, as there is only one record, the entire export is restarted. For response messages, the resume action resends the response to the middleware system when required.

Message Errors

When a technical process error occurs, the details of the problem are available in the second section of the view. It is important to note that only internal processing errors are visible in this view and specifically only when messages are either in the Interrupted or In Error states. Any business errors that occur during the processing of a particular record are stored in the response document and do not affect the overall processing of the message.

  • Source: Either the Server or the Client. An integration message is a generic transmission from a source to a target application. The concept of request and response is only linked to the business document contained within the message.

  • Code: An external unique identifier for the type of problem that occurred.

  • Reason: A contextualized message giving more information about the problem that occurred.

  • Detail: Further technical information about the problem. Specifically, if the problem was caused by an unmanaged Java language exception, this detail would be the stack trace of the exception.

Document Detail

The Document Detail View shows the top level information of the integration document.

  • Action: Defines how the target application is to process the records. The three possible values are Export, Import, or Business Service. In the two first actions, the records are handled by the generic integration services provided by the Taleo Connect Client. The last action signifies that the records are delegated to product specific business services for individual processing.

  • Progress: Shows how many records have currently been processed. In most cases, this value is identical for both the request and response message. For exports, the request document has a single record and the progress is only significant for the response document where the total indicates the number of entities that will be exported.

Each record processed during the integration is assigned a status: success or error. The total section first shows the overall number of records in the document then the amount of successful records and the amount of records in error.

Document Content

The document content view can display the content of the document or save it to file.