Use the TwineBallRequest node to find out how WebSphere® Adapters nodes work.
This topic contains the following sections:
The TwineBallRequest node is provided for educational purposes and allows you to see how the WebSphere Adapters nodes work. The TwineBallRequest node is a sample node with its own sample EIS. You cannot use the TwineBall nodes to connect to the external SAP, Siebel, and PeopleSoft EIS systems.
The TwineBallRequest node is contained in the WebSphere Adapters drawer of the message flow node palette, and is represented in the workbench by the following icon:
When you have put an instance of the TwineBallRequest node into a message flow, you can configure it. For more information, see Configuring a message flow node. To display its properties, either double-click the node, or right-click the node and click Properties. All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.
The TwineBallRequest node terminals are described in the following table.
Terminal | Description |
---|---|
In | The input terminal that accepts the request business object. |
Out | The output terminal to which the result business object is sent if it represents successful completion of the request, and if further processing is required within this message flow. |
Failure | The output terminal to which the business object is routed if a failure is detected during processing in the node. |
The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk on the panel if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the bar file to deploy it).
The TwineBallRequest node Description properties are described in the following table.
Property | M | C | Default | Description |
---|---|---|---|---|
Node name | No | No | The node type, e.g. TwineBallRequest | The name of the node. |
Short Description | No | No | A brief description of the node. | |
Long Description | No | No | Text that describes the purpose of the node in the message flow. |
Property | M | C | Default | Description |
---|---|---|---|---|
Adapter component | Yes | No | The name of the adapter component that contains configuration properties for the adapter. Either enter a name of an adapter file, or click Browse to select an adapter file from the list of files that are available in referenced message set projects. | |
Default method | Yes | Yes | The default method binding to use. |
Property | M | C | Default | Description |
---|---|---|---|---|
Message domain | No | No | DataObject | The domain that is used to parse the incoming message. By default, the message that is propagated from the TwineBallRequest node is in the DataObject domain. You cannot specify a different domain. |
Message set | Yes | No | The name or identifier of the message set in which the incoming message is defined. | |
Message type | No | No | The name of the incoming message. The node detects the message type automatically. You cannot set this property. | |
Message format | No | No | The name of the physical format of the incoming message. You cannot set this property. |
Property | M | C | Default | Description |
---|---|---|---|---|
Transaction mode | No | No | Automatic | This property specifies how updates are handled. If you select Yes, updates are performed in a single transaction (coordinated message flows). If you select No, updates are performed independently (uncoordinated message flows). |
Property | M | C | Default | Description |
---|---|---|---|---|
Method Location | Yes | No | $LocalEnvironment/Adapter/MethodName | The business method that is used to trigger the TwineBallRequest node to perform an
action on the external system. For example:
|
Data Location | Yes | No | $Body | The location in the incoming message tree from which data is retrieved to form the request that is sent from the TwineBallRequest node to the EIS. |
Property | M | C | Default | Description |
---|---|---|---|---|
Output data location | No | No | $OutputRoot | The message tree location to which the TwineBallRequest node sends output. |
Copy local environment | No | No | Selected | Select this check box to copy the local environment. |