T24Inbound component helps to receive events emitted from any T24 transaction. 

The component using the interface provided in the Metadata configuration of the T24Inbound CPS (Configuration Property Sheet) fetches all the available flow names. The component receives messages the events for the selected flow names. A unique response port and request port (in case of non scheduled mode) will be created for each selected flow name.

Component configuration and Testing


Figure 1: Component Configuration properties

Metadata configuration

Error handling configuration

For setting up Error Handling Configurations, please refer the respective sections in the Common Configurations page.

T24 Connection Type

Interface to be used to connect T24 for fetching the list of all the available flow names:

  • Web Service

    Web Service interface

  • TAFC

    TAFC (Temenos Application Framework C-version) is a classic jBase with JDC interface.

Integration Flow service WSDL Configuration


Figure 2: Specifying the URL or WSDL file of the Integration Flow Service

Location of the Integration Flow Service WSDL. This can be provided as URL or attached as a file.

This can be used to get the list of flows available

T24 Authentication Configuration


Figure 3: T24 Authentication Configuration options

T24 User Name

The User Name with which the connection to T24 Web Service interface is made.

T24 Password

 Password for the user as specified by the property T24 User Name.

T24 Company Code

 Company Code to connect T24. This property is optional.

Icon

The properties Integration Flow Service WSDL URL, T24 Username, T24 Password, T24 Company code are visible only when T24 Connection Type property is set to 'Web Service'.

TAFC Configuration


Figure 4: TAFC Configuration options

TAFC Agent Host Name

Specify the host name of the TAFC Agent.

TAFC Agent Port

Specify the port number of the TAFC Agent.

T24 OFS Source ID

The Source ID of the T24 OFS (Open Financial Service). 

Icon

The properties TAFC Agent Hostname, TAFC Agent Port, T24 OFS Source ID are visible only when T24 Connection type property is set to 'TAFC'.

Selected Events


Figure 5: Event Selection

To select an event for polling, the following operations can be used:

OperationDescription
>To include one or more events from the list of events in the left panel.
<To exclude one or more events from the list of events in the right panel.
>>To include all the events in the left panel.
<<To exclude all the events in the right panel.
reloadTo update the left panel for new events.

Runtime Configuration

T24 Connection Type

Select the connection type from the following options available:

  • Web service
    Micro Service uses the T24 Web Service interface to get the events for the selected flows.
     
  • TAFC
    Micro Service connects to TAFC (Temenos Application Framework C-version) to get the events. To make this work, we have to install and run the TAFC.
     
  • TAFJ-EJB 
    Micro Service connects to TAFJ (Temenos Application Framework J-version) to get the events. To make this run, we have to deploy the TAFJ into JBOSS (version 7 or above).
    To use this EJB approach, we have to add the following jars which are part of the TAFJ deployment:
    • t24-IntegrationFrameworkService-Data.jar
    • t24-IntegrationFrameworkService-ejb.jar
    • tComponentFramework.jar

Integration Framework service WSDL Configuration


Figure 6: Specifying the URL or WSDL of the Integration Framework Service

Location of the Integration Framework Service WSDL. This can be provided as URL or attached as a file.

This can be used to poll for events of the selected flow names.

T24 Authentication Configuration for Web service


Figure 7: Component Authentication Configuration panel

T24 Username

The User Name with which the connection to T24 Web Service interface is made.

T24 Password

Password for the user as specified by the property T24 User Name.

T24 Company Code

Company Code to connect T24. This property is optional.

Icon

The properties Integration Framework Service WSDL URL, T24 Username, T24 Password, T24 Company code are visible only when T24 Connection Type property is set to 'Web Service'.

T24 Authentication Configuration for TAFC


Figure 8: Authentication Configuration

Username and password for T24 Sign On authentication scheme

TAFC Configuration


Figure 9: TAFC Connection Configuration

Configuration window to provide details of TAFC Agent interface.

Icon

The properties T24 Authentication Configuration and TAFC Connection Configuration are visible only when T24 Connection Type property is set to 'TAFC'.

TAFJ Connection Configuration

Configuration window to provide details of the JBoss application server to use TAFJ-EJB interface.


Figure 10: TAFJ Connection Configuration

Icon

The TAFJ Connection Configuration property is visible only when T24 Connection Type property is set to 'TAFJ-EJB'.

Maximum events count

The maximum number of events to be polled for a particular request from the server.

Send Empty Message for No events

If this property is enabled, then an empty message is sent out for each request when there are no events on the server; no message is sent if the property is disabled.

Scheduling Configuration

Select the Enable scheduling checkbox to configure scheduling.

For setting up Scheduling configuration, please refer the respective section in the Common Configurations page.

Expert Properties


Figure 11: Expert Properties


Pre Processing XSL Configuration

Pre Processing XSL configuration can be used to transform request message before processing it. Click the ellipses button against the property to configure the properties.

Refer to the Pre/Post Processing XSL Configuration section under the Common Configurations page for details regarding Pre Processing XSL configuration and Post Processing XSL configuration (below).

Post Processing XSL Configuration 

Post Processing XSL configuration can be used to transform the response message before sending it to the output port.

Process Message Based on Property

The property helps components to skip certain messages from processing.

Refer to the Process Message Based On a Property section under the Common Configurations page.

Connection Pool Configuration

Please refer the Connection Pool Params section in the Common Configurations page.

Others

Input Target Namespace

Target Namespace for the request and response XML messages.

For description, refer to the Target Namespace section in the Common Configurations page.

Input and Output

Input

T24Inbound component takes the input in XML format as shown below when scheduling is disabled:

Output

Output schema is fetched based on the flow name selected and set on the respective response port.

Functional Demonstration

Scenario

Configure the T24Inbound component as described in Configuration and Testing section to receive events of TTI-CashAccountType flowname and use Feeder and Display components to send sample input and check the response respectively.

             
Figure 12: Demonstrating scenario with sample input and output

Input Message

Output Message

Adaptavist ThemeBuilder EngineAtlassian Confluence