EventInvocation Activity
The EventInvocation activity works as invocation service. This activity must be run with the ReplytoSiebelEvent activity. It receives the data and performs the defined operations then displays the result in Output tab. If any error occurs during the operation it throws a fault and the same is communicated to the Siebel server. On the successful completion of this activity the next activity of ReplytoSiebelEvent responds to the Siebel server.
Once this activity receives the data, it displays this data in the Output tab. This is applicable for Query Non Siebel Business Component and Send Receive Integration Object.
This activity performs the Query operation on Siebel Server by using the received the data. This is applicable for the Siebel Business Component and Query Siebel Integration Component and shows the result in the Output tab.
General Tab
The following table lists the configurations in the General tab of the EventInvocationProcess activity:
Field | Visual diff | Module Property? | Description |
---|---|---|---|
Name | Yes | No | The name of the activity is displayed. |
Siebel Connection | Yes | Yes |
Specify the Siebel Connection type that must be used. For more details, see Creating a Siebel Connection Using the Siebel Connection Resource. Click the search icon and select the appropriate connection. |
Siebel Object Type | Yes | No | The following Siebel object types are available: |
Business Event Name | Yes | Yes | You can enter the business event name in this field. This field name must be unique and must match with the Event Name that is used while publishing the event from Siebel Server. If you use same names in two different activities then no error is thrown by the plugin. |
Siebel Object Reference | Yes | No |
This is not applicable for Non Siebel Business Component Type. To specify the object for reference, click the Search icon and select the appropriate object from the displayed dialog box. For more details, see Creating a Siebel Schema Using the Siebel Objects Editor. |
Publish as XML | Yes | No | This field is applicable only for the Send Receive Integration Object activity. This displays the output in XML data in String format in the Output tab in the XMLMessage element. |
Integration Object Name | Yes | Yes | This is the name of the integration object that is to be a part of the reply. |
Description Tab
In this tab, you can enter a short description for the EventInvocationProcess activity.
Advanced Tab
Field | Module Property? | Description |
---|---|---|
Sequence Key | No | This field contains an XPath expression that specifies which processes runs in order. Process instances with sequencing keys that evaluate to the same value are executed sequentially in the order the process instances were created. |
Custom Job ID | No | This field contains an XPath expression that specifies a custom jobID for the process instance. This ID is displayed in the TIBCOAdministrator View Service dialog and it is also available in the $_processContext process variable. |
Output Tab
Field | Description |
---|---|
EventName | The event name that is generated from the Siebel server. |
Operation | Name of operation received as data from the Siebel server. |
SiebelTimeStamp | The time stamp received from the Siebel server. |
UniqueData | This is a unique string used to identify the socket object used to send response to Siebel Server.
You must map this to the UniqueData input tab element of ReplyToSiebelEvent Activity. |
XMLMessage | XML data is published as a String. This field is applicable only when you select the Publish as XML check box in the General tab. |
Fault Tab
In the Fault tab, you can find the error message and error message code of the EventInvocation activity. For more details, see Error Codes.
Error Schema Element | Data Type | Description |
---|---|---|
SiebelPluginException | String | This exception is thrown due to the errors occurring while replying over the socket, errors related to Kafka, or during String to XML conversions. |
SiebelJDBException | String | Displays an exception related to the Siebel operation. The exception is generated either by the Siebel server or due to operation failure. |