Professional Documents
Culture Documents
It doesn’t matter...
• what kind of computer sends the message or on which operating system
it is running
• where in the world the client is sending the message from
• what language the software that the client is running on is written in
• to the client what type of SOAP processor is running on the server
Key Components
• SOAP
• specifies XML grammar for sending and responding to messages
• HTTP
• standard that facilitates transfer of SOAP messages and WSDL
documents between computers
• Advantage: permitted through Firewall (unlike CORBA/DCOM)
• WSDL
• Specification that tells us how to describe a piece of software in
terms of the method calls it responds to. Described in abstract way,
independent of programming language
• Also contains concrete details of how to make the connection:
• Method Calls
• Parameters it accepts
• Responses it will send back
• Protocols it can process
• Data format specifications it can accept
• URLs for the service
Resource Adaptor
• A system-level software driver, which is used by a Java application to
connect to an EIS (T24 on TAFC).
Why JCA?
• Before JCA was defined, no specification provided a standard
architecture for integrating heterogeneous EIS systems.
• Enables an EIS vendor (Temenos) to provide a standard Resource
Adapter for its EIS (T24).
• Single resource adapter can plug in to any application server that
supports JCA. (JBOSS, WebSphere, WebLogic)
Benefits
• Independence from proprietary Temenos Connectivity Software
(TCServer)
• Simplification of Browser, ARC-IB and TWS deployment and
configuration
• Availability of standard message monitoring and integration tools
• Clients have existing configuration expertise.
Server 2
JEE Standard JMS Consumer
JMS Consumer - Leverages Application Server
(OFSMessage MDB) pooling, failover and load
balancing
Interface Protocols
SOAP /
HTTP SSL WMQ JMS File
XML
T24 RA
(t24-ra.rar)
Generated WSDL
Generated Classes
1
4 5
T24 Application Server
ServiceLandscape OFS
(EB.SERVICE/PW.ACTIVITY)
Web
T24 T24 Web Generated Web Deploy
Services
Server Service Services Annotated Services Annotated
Definitions Classes Classes Interfaces
Generator Packages (WSDL)
Web
T24 T24 Web Generated Web Deploy Services
Server Service Services Annotated Services Annotated
Definitions Classes Classes Interfaces
Generator Packages (WSDL)
JAXB (JDK)
JAX-WS METRO
Supporting Technologies Supporting Technologies
T24Updates:
• T24 Core
• EB_Foundation
• New WS product and component data items
• EB_Interface
• Include additional information on the beginning of the OFS response.
• Supports Arrangement Architecture (AA)
• EB_PresentationServices
• Determine the type of a T24 data field when generating XML schemas
• Shared with new T24 UI (UX product)
• EB_Reports
• Return enquiry output in a modified format where the enquiry in question
is invoked from a Web Service
• Supports Paged Enquiries.
• EB_TransactionControl
• Recognise/accept ‘WS’ as a valid T24 product
• WS Product
• WS_ConnectionSetup
• detects that an incoming message received by T24 originated from
either the TWS Eclipse tooling, or a deployed Web Service
• WS_Metadata
• generates XML schemas which describe applications, Versions &
Enquiries.
• Pre-R11:
• JF_Foundation (now replaced by EB_AgentFramework)
• entry point into T24 for TWS tooling (both platforms)
OFS.SOURCE
• Dedicated record for TWS
• Source Type: TELNET
• Attributes: TWS (multi-valued field)
• Deployment: Configure in t24-ds.xml tx-connection-factory
Java Platform
• Eclipse 3.5 (Galileo) or , from R10: Eclipse 3.6 (Helios)
• Eclipse installation must include Web Tools Platform (WTP)
(included in the ‘Eclipse IDE for Java EE Developers’)
• Eclipse ‘Installed JRE’ must be JDK 6
• Enterprise application server :
• JBoss 4.2.3GA, 5.1.0GA and 6.0.0.Final
• Glassfish Server 3.0.1 on Sun Sparc
• WebSphere 6.1 and 7
• WebLogic 10.3 and 11g
• EB.SERVICE
• ACCOUNT.MANAGEMENT
• QUERY.CUSTOMER
Eclipse IDE
• Plug-in deployment (\dropins)
com.temenos.tws.plugin_1.1.0.201012091043-R10.jar
• Run Eclipse.exe
• Select/create workspace & close Welcome screen
• JavaEE Perspective
• Create a new TWS Project
• File > New > Other > Temenos Web Services > TWS Project
• Name: signon1
• Tick ‘Enable project specific settings’
• Change Port to 20006
• Select business operations:
• Open Current Account LCY
• Query Business Partner > Enquiry > Find Customer
<context-param>
<param-name>log4jRefreshInterval</param-name>
<param-value>1000</param-value>
</context-param>
<listener>
<listener-
class>org.springframework.web.util.Log4jConfigListener</listener-class>
</listener>
<!-- end of configuration for log4j -->
• Logs:
• ..\workspace\.metadata\.log
• ..\jboss\server\default\log\server.log
Browser:
• Browse to:
http://127.0.0.1:9095/signon1/services
http://127.0.0.1:9095/signon1/services?wsdl
SOAPUI
• Create a test project based on a WSDL
• Create a T24 transaction via a SOAP Request
• View request & response in JBOSS console
• View INAU account using T24 Browser
• Run a T24 Enquiry via a SOAP Request
• View request & response in JBOSS console
• Supply in full with any support-request
• ..\ModelBank-201012PB\3rdParty\jboss\server\default\log\server.log
successIndicator
• a string value indicating the success / failure of the web service request.:
transactionId
• the T24 transaction id for the completed request
messages
• list of all success / error messages returned from T24 or TWS web
application
SUBROUTINE SIGNON.WORK.BALANCE(CUST.ID,WORK.BALANCE)
$INCLUDE T24.BP I_COMMON
$INCLUDE T24.BP I_EQUATE
$INCLUDE T24.BP I_F.ACCOUNT
WORK.BALANCE = 0
CALL F.READ('F.CUSTOMER.ACCOUNT',CUST.ID,R.CUSTOMER.ACCOUNT,'',YERR1)
LOOP
REMOVE ACCT.ID FROM R.CUSTOMER.ACCOUNT SETTING ACCT.POS
WHILE ACCT.ID : ACCT.POS
R.ACCT = ''
CALL F.READ('F.ACCOUNT',ACCT.ID,R.ACCT,'',YERR2)
WORK.BALANCE += R.ACCT<AC.WORKING.BALANCE>
REPEAT
RETURN
END
Design
• Define the Web Service field parameters & data type (Request/Response)
• Define the inputs/outputs for the T24 routine
• Decide the message format to be passed
• OFS format or custom design
T24
• Write the Business Operation (T24 subroutine)
• Expose it in PGM.FILE as a type ‘S’ubroutine
Eclipse
• Modify beans.xml: define the class to be used for the Web Service
• Create a custom source folder
• Create a custom package
• Write a Request class and a Response class with annotations
• Write the Web Services implementation class
• Generate and deploy (standard procedure)
Demonstration
• Create a TWS Notification project
• Define the event:
• Supply a name
• Select a Version and an Exit Point
• Select a Target service
• JMS Queue
• External Web Service (WSDL)
• Save the project – updates T24
• Export the Enterprise Java Bean (EJB)
• Authorise the VERSION and WS.EXIT.POINTS records
• Input a T24 contract (FUNDS.TRANSFER)
• Observe the delivery of the message
We have: