Use the Invoke Tuxedo Service activity to invoke a Tuxedo service as an asynchronous request/response.
General
The various tabs in the
Invoke Oracle Tuxedo Service window are explained as follows.
In the
General tab, you can specify the reference to the Oracle Tuxedo Connection shared resource and XSD schemas related to the Oracle Tuxedo service invoked by the activity.
The following table lists the configurations in the
General tab of the Invoke Oracle Tuxedo Service activity:
Field
|
Module Property
|
Visual Difference
|
Description
|
Name
|
No
|
Yes
|
Specify the name to be displayed as the label for the activity in the process.
|
Oracle Tuxedo Connection
|
Yes
|
Yes
|
Click
to select an Oracle Tuxedo Connection shared resource. The Oracle Tuxedo Connection is strictly used for runtime since schema is downloaded using the Oracle Tuxedo Schema shared resource.
|
Request Timeout (ms)
|
Yes
|
Yes
|
Timeout property at activity level which would end request to Oracle Tuxedo server should the timeout value is met.
|
Service Name
|
Yes
|
Yes
|
Specify the service name to invoke Oracle Tuxedo service.
Note:
- You can use only Literal values as module property is not supported.
- For the projects developed in previous versions where the
Service Name property did not exist, the
Service Name can be maintained in this release manually or by using the Refactor process available in TIBCO Business Studio.
|
Input Schema
|
No
|
Yes
|
The XSD schema used for the request to the Oracle Tuxedo server. Click the
Load Input Schema button to pick up the schema.
|
Output Schema
|
No
|
Yes
|
The XSD schema used for the reply from the Oracle Tuxedo server. Click the
Load Output Schema button to pick up the schema.
|
Validate Schema
|
No
|
NA
|
Validates the input and output
XSD schema field name and field ID with
Jolt Repository field name and field ID for mentioned service name.
|
Note: The summary shown on the pop-up screen only shows discrepancies where a field exists in XSD but not in Jolt Repository and vice versa. The generated file contains more information concerning discrepancies in field IDs. To check for incorrect field IDs, execute the Refactor process available in TIBCO Business Studio.
After you click
Validate Schema, it generates a .txt file displaying the discrepancy of field ID of XSD schema and field ID of jrepository. A sample .txt file is shown below :
Total matches:0
Total mis-matches: 10
Following fields are mis-matched for XSD and Jrepository:
Field_Name: EMPID XSD Field_ID: 33558533 JRepository Field_ID: 33554433
Field_Name: SALARY XSD Field_ID: 100667401 JRepository Field_ID: 100663301
Field_Name: CITY XSD Field_ID: 167776269 JRepository Field_ID: 167772169
Field_Name: DEPTNAME XSD Field_ID: 167776264 JRepository Field_ID: 167772164
Field_Name: HRA XSD Field_ID: 4107 JRepository Field_ID: 7
Field_Name: EVENT_NAME XSD Field_ID: 167776270 JRepository Field_ID: 167772170
Field_Name: DEPTID XSD Field_ID: 33558534 JRepository Field_ID: 33554434
Field_Name: EMPNAME XSD Field_ID: 167776263 JRepository Field_ID: 167772163
Field_Name: BASIC XSD Field_ID: 134221834 JRepository Field_ID: 134217734
Field_Name: CFLAG XSD Field_ID: 67112972 JRepository Field_ID: 67108872
Total fields which are not present in Jrepository but present in XSD: 0
Total fields which are not present in XSD but present in Jrepository: 0
Note: If there is any mismatch of the field name between XSD Schema and Jolt Repository, the user can get it corrected by contacting the Oracle Tuxedo administrator team.
Fault
The
Fault tab contains the fault schemas used by the activity when generating a specific error. The fault name would be TuxedoPluginException.
The following table lists error schema elements in the
Fault tab of the Invoke Oracle Tuxedo Service activity:
Error Schema Element
|
Data Type
|
Description
|
msg
|
String
|
Displays the error message.
|
msgCode
|
String
|
Displays the error code.
|