Tws PDF

Welcome to this learning unit on Installing TWS .NET.
You will learn how to install and setup

TWS for the .NET platform.
TWS3.Install TWS .NET-R12.01 1

At the end of the session, you will be able to
Install TWS .NET

Configure TWS .NET
Create, publish and test TWS .NET Project
Use strong data type in TWS .NET

Web services are standard ways to publish/access program functions on the
internet . You are allowed to choose any web service.
Web service is typically an Application Programming Interface (API) or WebAPI that

is accessed via Hypertext Transfer Protocol (HTTP) and executed on a remote
system, hosting the requested service.
Web Services Description Language (WSDL) is a XML document that describes

a web service, providing its location (URL), the method calls and the parameters
which it accepts, the associated data format specifications, the responses the
service will return, and the protocol(s) it can process.
W3C Definition: A web service is a software system designed to support

interoperable machine-to-machine interaction over a network. It has an interface
described in a machine-processable format (specifically WSDL). Other systems
interact with the web service in a manner prescribed by its description using SOAP
messages, typically conveyed using HTTP with XML serialization in conjunction with
other web-related standards.
Interaction between the client and the web service is independent of the operating
system, SOAP processor, client software platform/programming language and
geographical location. This is due to the interoperability provided by the SOAP
format and the fact that XML can be represented/transmitted easily as plain ASCII
characters.
TWS4.Install TWS EE-R12.01 3

Slide 3
n1 Please change the sentence

nnalini, 2/3/2012
n2 Please clarify W3C definition

nnalini, 2/3/2012
The steps to create a web service using TWS are as follow:
1 -> A user creates a project using TWS project template and communicates with T24
application server.
2 -> After connection is established, a list of Business Services and Operations is fetched.
3 -> The user selects the list of Business Operations from the Business Service to be
published as Web API.
4 -> TWS then creates a web service for the selected Business Services and Operations
and configures T24ConnectorService.
5-> The user then publishes the newly created WCF web service to the web server.
Certificate Server: It’s a virtual layer which validates the SSL certificate between Web Server
and Application Server.

Let us now look at the path of communication in TWS:
1 -> External interface communicates with web services published in the web server.
2 -> The wrapper code communicates with the T24 application server and executes the
intended function or operation.
3 -> The web server receives the OFS response which is parsed to the respective class
object. CallOFS is the web method provided by default on creation of any web service, to
send OFS message as native OFS. To get the OFS response as Native OFS, create
OFS.SOURCE record as:
• Syntax Type : OFS
• Source : TELNET
4 -> The output is then picked up by the external interface from the web server.
Certificate Server: It’s an optional layer which validates the SSL certificate between Web
Server and Application Server.

Temenos Web Services help you to provide SOA Web services for T24 .
TWS is a tool which exposes T24 Business Services and Business operations as WS-I
compliant Web APIs’ using NRemote connectivity.
• Temenos packages these T24 services according to BIAN service landscape.

• TWS allows you to add or amend service operations to create / modify services in T24 as
required.
• You may also create new service landscapes to expose services in a variety of hierarchies.
Note : TWS uses jRemote.dll for connectivity, it is been mentioned as nremote, and so it
refers .NET not java.

The prerequisites for TWS are :
1. Visual Studio 2010
2. Microsoft .NET 4.0 (Automatically gets installed when visual studio is installed)
3. WCF 4.0 (is part of the .NET frame work and get installed automatically along with it)
4. IIS 5.1 and above
5. Secure Sockets Layer (SSL) is an optional component registered at TAFC Agent level
(must be started with it) and at TWS Composer (deployed in the OS where it is run) / IIS
(has to be deployed inside IIS, not enough if it is just available at the OS)
Note:
1. Components 2 and 3 have been included to ensure their availability, once visual studio
is installed.
2. Check whether WPFToolkit.dll is available in your machine. The command to check the
same:
gacutil /l | findstr WPFToolkit
3. If WPFToolkit.dll is not there, then you can download and add it to Global Assembly
Cache. The command to do the same is:

gacutil /i <path where the dll is stored>\WPFToolkit.dll

Note:
How to install products and updates are not covered as part of this course. Participants are
expected to have a basic knowledge of Updates and TOCF EE concepts.

TWS composer installation kit can be downloaded from KB (provided by Temenos).
The path to the installation files must not contain any spaces.
Start the installation by executing ‘TWSSetup.vsix’ file. Since this adds an extension to VS
2010, you may not see TWS in ‘Add / Remove Programs’ as you had in the older version of
TWS.
Once the above step is completed, execute TWSConsole.exe. TWS Console setup will ask
you to supply two paths:
Please enter the Visual Studio 2010 IDE path: Enter the path where the devenv.exe is
present
Please enter the Microsoft SDK path: Enter the path where the xsd.exe is present
Note:
1. As a pre check make sure the user is signed in as an administrator.
2. Close all Visual Studio instances.

Web Services created by TWS Composer establish connection with T24 through
T24ServiceConnector hosted in IIS by endpoint configuration. This type of architecture
implements a scalable mechanism to add additional connectors to T24ServiceConnector
and leverages WCF connection handling properties such as e.g. service throttling.
T24Service connector provides the following,

1. Connection factory / connection pooling – establishes connection with the configured
TAFC Agents’.
2. Load balancing / high availability – provides load balancing within the configured TAFC
Agents’.
3. OFSML-OFS Parser – Converts incoming OFSML request message to respective OFS
request message format and sends to T24. Then the OFS response message is
converted to respective OFSML response message.
The default file in which you have to configure the URL, OFS Source, Host and Agent is
MyConnectors.xml. But you can also have a different configuration file, in such case the
web.config file of T24ServiceConnector has to be updated with the new configuration file.
In the URL tag, you have to specify the T24 Service Connector URL.
Ex: http://localhost:6066/ServiceConnectorT24
More about this configuration file is explained later in this session.

Slide 10
a2 To deploy T24Connector, you need administrator or equivalent permission

akavitha, 5/30/2011
The port specified in the URL tag is registered at the Windows O/S-level. Netsh command
can be used to register the URL.
Example:
netsh http add urlacl url= http://+:6066/ServiceConnectorT24 user=IIS_IUSRS
For Windows XP or earlier operating system use httpcfg instead of netsh

Note:
To register the port (Need to be done if and only T24ConnectorService is accessed by non
administrator user):
1. Go to Start > Accessories > Command Prompt > Right-Click (Run as Administrator).
2. Execute this at the command prompt:
netsh http add urlacl url=http://+:6066/T24ServiceConnector user=DOMAIN\username
6066 here is your port number, you can replace this with a port number of your choice (using
which your WCF service is hosted)
Example:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC> netsh http add urlacl
url=http://+:6066/ServiceConnectorT24 user=IIS_IUSRS
You should get a message saying “URL reservation successfully added”.
For Windows XP you can use httpcfg tool or a utility known as httpconfig.

Once you install TWS .NET Composer, you can create your own Web Services to expose
T24 API’s. These web services internally connects to a web service called as T24 Service
Connector. It generates WSDL’s at runtime, which can use any port. These runtime
WSDL’s in turn connect with TAFC agent, that is connected to T24. The runtime WSDL path
is configured in MyConnectors.XML.

T24 Service Definition – XML based representation of the T24 business service
(EB.SERVICE and PW.ACTIVITY). This xml contains the grouping information for
EB.SERVICE and PW.ACTIVITY. This file can be found under the folder <Project
folder>/external/landscapes.
Web Services Generator – Temenos Visual Studio plugins allow browsing T24 business
services, and generation of code behind the packages.
Web Services Package – Temenos plug in uses platform calls to manually deploy the code
behind packages (C# only) to the IIS runtime, which triggers the WSDL generation.
Packages handled by core T24 libraries/artifacts. Connection pooling is also handled by
them.
Example: TWSParser.dll, ObjectPoolManager.dll, TAFCNetRemoteConnector.dll. Found
under the folder
{TWS install
path}\TWS(.NET)InstallKit_11.0.0.1\TWS(.NET)InstallKit_11.0.0.1\SupportFiles\Gac_Librari
es.
Web Services Definition Language (WSDL) – Deployment target is standardized IIS
(.NET) Web Services Interface – WSDL
T24ServiceConnector - Web Services created by TWS Composer establish connection
with T24 through T24ServiceConnector hosted in IIS by endpoint configuration.
Note: Attributes are tags that are inserted into source code so that they can be processed
using tools. An Attribute, in C# .NET, is a special form of syntactic metadata that can be
added to C# .NET source code. Attributes provide a powerful method of associating
declarative information with C# code (types, methods, properties, and so forth). Once
attributes have been associated with program elements, reflection can be used to query their
existence and values.

1. T24 provides the service definitions to be deployed via a number of core
system calls using the same meta data as the UI.
2. Temenos Visual Studio plugin is coded to allow browsing of the T24
business services, and generation of the “code behind” packages.
3. Temenos plug-in uses platform calls to manually deploy the “code
behind” packages (C# only) to the IIS runtime, which triggers the WSDL
generation.
4. Deployment of target is standardised:IIS (.NET)

The diagram shows the technical model for TWS .NET.
1. T24 produces XML Schema to denote an underlying Business Operation.
2. A webservices generator (i.e.- TWS Composer), is used to create web services

endpoints for the Business Operation. This composer is available in the form of a plugin
for Visual Studio. The actual generation of the web service is done by the underlying
.NET WCF platform. The deployment artifact that is produced, in this case a .dll is
hosted inside IIS.
3. TWS connects to T24 through the standard architecture. nRemote uses the jRemote
API to ‘talk’ to the TAFC Agent.

Slide 15
gt1 A WCF client connects to a WCF service via an Endpoint. Each service exposes its contract via one or
more endpoints. An endpoint has an address, which is a URL specifying where the endpoint can be
accessed, and binding properties that specify how the data will be transferred.
Gerard Thomas, 2/1/2011

Business Services
•Business Services are specified in EB.SERVICE.
•A Business Service exposes a collection of Business Operations.
Business Operations
•Business Operations are specified in PW.ACTIVITY.
•A Business Operation can either be a contract (i.e.- a VERSION and function) or a
query(i.e.- an ENQUIRY).
The descriptions provided in PW.ACTIVITY and EB.SERVICE should be unique and not
contain special characters.
The selected Business Operations are exposed as web services via Web APIs which
connect to T24 via nRemote.

TWS uses the existing PW module to create Business Operations. This Business Operation
created using the application PW.ACTIVITY will be mapped to a Business Service created
using the application EB.SERVICE.
The EB.SERVICE record will show a multi-valued list of Activity Ids. One or more
EB.SERVICE records define all the activities which are exposed as Web Service operations.
Note: The description provided while creating records in PW.ACTIVITY & EB.SERVICE
should satisfy the below conditions,
• The description should not be repeated.
• The description should not have special characters.
• Record IDs for PW.ACTIVITY and EB.SERVICE need not necessarily be the same.
This is because from R12 onwards the description field in PW activity will be used for
naming the Web Service operation.
PW.Activity ID should start with WS., in order to bypass the PW.Activity ID validation.

We need an OFS.SOURCE record to communicate with T24 when we use TWS.
The record we use for connecting TWS should have Source Type set to “Telnet”, Syntax
Type to “OFS” and Attribute value to “TWS”. The attribute PREAUTHENTICATED is
discussed later.
Note:
1. If there is a requirement to receive the OFS responses from the “callOFS” methods as
native OFS responses, then the Attributes field should be left blank.
2. 2. Refer to the OFS courseware for more details on the OFS.SOURCE application.

TAFC Agent has to be started for establishing the connectivity between TWS and
TEMENOS T24. TAFC Agent may be started from the command line/shell via the following
command.
jbase_agent –p 20001 (If the port number is not specified, it will default to 20002).
Note: Before starting jbase agent, make sure the OFSSOURCE key is configured with the
ID of the OFS. Source record in web.config / devenv.exe.config is as follow:
<appsettings>
<add key=“OFSSOURCE value=“GCS”/>
</appsettings>
Note: For other options and instructions on how to start TAFC Agent as a service, please
refer the nRemote / TAFC Agent user guide.

Open Visual Studio 2010 and create a new project.
Click File >New > Project to create a new project.

1. Choose Integration Studio under Visual C# and select WebService composer Template.
2. Name the project and click OK.

Now, the project gets created and the message ‘Creating Project [PROJECT NAME]…
project creation successful’ will be displayed on the left bottom pane of Visual Studio 2010.
• Open Solution Explorer, view the project created.
• Double click on TWS.t24 file.

Right click on the T24Services, and select Connect.
Once the connection is established, Refresh and Disconnect option will be enabled and
Connect option will be disabled. The Refresh option is provided to reload the Landscapes
from T24.The disconnect option clears the landscape tree view and keeps the TWS
composer in a disconnected state.
Once the logon screen appears, type the IP address (e.g., Localhost if T24 is available in the
same machine where Visual Studio is running), the Port Number (20005) where jbase_agent
is listening and the OFS Source ID.
‘WSDL with Strong Data Types’ is an option available in the ‘Log On’ screen. Select the
option as of now. We will discuss about this option in detail later in this session.

• Once the connection is authenticated, the Business Services and Business Operations will
be displayed.
•Choose the Business operations, for which Web APIs (methods) have to be created.
• The Service Properties Pane will indicate the information of the respective Business
operation selected.
• Click on Create Web Service.
• During the process, the progress bar will hold the status of the process.
Note: Each function against each service will generate at least one web method. For every
'Input' web method created, an equivalent 'Validate' web method is also created. In addition
to this, the CallOFS web method is also created by default for any version/enquiry to send
OFS messages to T24.
When a saved project is reopened, only the check box next to the operation (PW.ACTIVITY)
for which web service has been generated is checked and not the parent node. This is to
inform the user as to what are the operations for which web services has been generated
under this project.
If the user wants to add more services as part of the same project, they have to select the
operations along with the parent node. If you want the existing service also to be part of the
changed product, mere selection of operation is not enough, its parent node should also be
selected. If not, the old information will be lost and a new web service with only the new
operations will be created.

Click on Show all files icon to check the service that has generated. The newly created
service will be named as [PROJECT NAME].svc E.g. DemoTWS.svc and any user defined
code to be added to the web service has to be done in this file. The code is written in C#. To
open this file, just double click on this file.
Note: While creating a project, the information for creating the metadata will be fetched from
the T24 system. Once the project is closed, the user is reconnected to the project and the
meta data will be loaded from the already saved XML file (found under the folder <project
path>\<project name>\External\LandScape). Only Refresh button will connect to T24 to
rebuild the meta data for some changes.

You could have seen a similar ‘Log on’ screen earlier in this session. This what makes the
difference in validating the data entered by the user. But how?
While connecting to T24 in your TWS project, you can select ‘WSDL with Strong Data
Types’. This ensures that the schema created for the VERSION and ENQUIRY holds typed
data not just string. This ensures simple data validation happens at Web Service itself.
By itself, this does not validate data. To validate the request based on the XSD, you have
add a key “ValidateRestrictions” and set its value to true in the web.config file.

The T24 data types are: String, Currency, Date, Recurrence, Frequency,
Password, Amount, BlockText and imUpload.
The .NET types that are getting mapped with the fields in XSD as:
String – for T24 types String, Currency, BlockText, imUpload,
Recurrence, Frequency, Password
Date - for T24 type Date
Decimal - for T24 type Amount

In TWS R11, all data were treated as string data. This means that T24 performs simple
check for valid data entry.
But in R12, TWS performs data type validations.

Restrictions ensure that only specific pattern of data is allowed. For ex., you know that the
CURRENCY field holds data of 3 character length. Earlier it was allowed to enter any 3
characters input for the CURRENCY field. But the new TWS .NET applies restrictions and
hence the web service will accept only 3 alphabets input.

You learnt that the T24ConnectorService enables the communication between the jBase
agent and the web service. While creating TWS project, we have to configure this
T24ConnectorService to the location where it is deployed, as follow:
•Expand ‘Service Reference’ and right click ‘T24Connector’.
•Select ‘Configure Service Reference’ option.

In the popup window, specify the WSDL path of the T24ConnectorService and click on OK.

Now, execute the TWS project either using PLAY button or F5 key. The above slide displays
file with .svc as extension.

Choose ‘Run without debugging’ option and click on OK. On successful execution, a
browser window will appear.
Note: Either of the options can be selected. It will just affect the UI behavior, but the
business functionality will not be affected.

To test the web service:
Step 1 -> Copy the WSDL url from the browser.

Step 2 -> Open WCF Test Client , and click Add Service.
Step 3 -> Paste the url as http://localhost:7955/DemoTWS.svc?wsdl (in this case)
and click on OK.

Now choose the method that you want to execute. You can see the tab where to specify the
request and get the response.
This screen shot shows the result of executing an Enquiry. There you need to specify the
T24 user name and password. In the response you can see the result and the status
message of TWS. You can scroll down to check the complete response.

This gives an example for funds transfer transaction. The response will contain the complete
funds transfer record and the status message of the TWS transaction.

In this slide you can see the data for CREDIT account number and if the currency given is
wrong then the transaction fails with T24 SuccessIndicatorValue as ‘ValidationError’. This
means that this transaction never reached T24, but the basic validation happened at the web
service level.

When you create a web service using Visual Studio, you can test it without deploying it
under the web server. But after testing the web service, it has to be deployed under the web
server.
To deploy the TWS service, click on the ‘Solution Explorer’ and select the below mentioned
files using ‘Ctrl’ key.
1. All the dll files under bin folder except the dll named as <Project Name>.dll.
2. All the XML Schemas. These XML Schemas are available under External\XSD.
3. TWS service. The name of this file would be <Project Name>.svc.
Now right click the selected files and choose ‘Include In Project’ option.

Now you can publish the TWS web service by selecting ‘Publish <Project Name>’ option
from Build menu.

Slide 40
A1
Publish will work with Adminstrator or equivalent rights

Kavitha, 1/23/2012
Here the TWS project is deployed under the local IIS.
•Specify Service URL and Site/Application.

•Click Publish.

Here you can view the deployed service in IIS and execute the web service from the IIS.

T24ServiceConnector has two files for configuration under conf folder, connectors.xml and myconnectors.xml. The connection
properties to T24 (TAFC Agent) are specified in the configuration file. You can have more than one serviceconnector defined in the
configuration file.
Id- Identifies the T24 service connector instance.

URL- WCF Service URL.
OFSSourceId- T24 OFS.SOURCE record used by this connection.
HostIP- Comma separate list of TAFC Agent instance. Syntax: <host>-<port>,<host>-<port>,….
LoadBalancing- When enabled, T24ServiceConnector will create a connection pool with evenly allocated connections among the
list of available servers. If disabled then only High availability is ensured.
High availability - T24ServiceConnector will attempt to access the first mentioned TAFC agent host details and will create
connection pool, based on the configuration settings while the first request is initiated. While the TAFC agent connected goes down
for an unavailable state,then the request is routed to the next available TAFC agent configured. Based on the Retry count
configured the retry attempts are done.
Note: High availability of the Web service deployed in IIS is to be achieved by the user having the mechanisms available in the
market.
Charset -Character set configured in T24 (e.g. UTF-8, ISO-8859-1, etc.).
MaxPool -The max. number of TAFC Agent connections to spawn.
MinPool- The min. number of TAFC Agent connections to spawn. This option will pre-fill the pool.
IdleTimeout- Timeout (in milliseconds) after which an idle TAFC Agent connection is released to the pool.
IncrementFactor -Increment factor used when spawning new TAFC Agent connections.
ActionTimeout- Timeout (in seconds) after which TAFC Agent will terminate a connection that has not processed a request in the
specifiednumber of seconds.
RetryInterval -Wait interval (in milliseconds) before re-connecting after a second connection failure.
RetryAttempts- No. of reconnection attempts.
SSL- Indicates whether to enable SSL encryption between T24ServiceConnector and TAFC Agent.
DN- Specifies the SSL certificate’s distinguished name. Only used when enabling SSL.
Compression- Indicates whether to enable data compression between T24ServiceConnector and TAFC Agent.
CompressionThreshold - Specifies the minimum size (in bytes) for data packets to be compressed.
AllowInput - Indicates whether to allow users to enter data on the console output when requested by T24 (e.g. due to T24 input
request, JBC debugger prompt, etc.).
EnvironmentVariables -Semicolon separated list of additional environment variables to be applied to a TAFC Agent connection
(e.g..MYVAR1=AA; MYVAR2;BB).
AgentUser- TAFC Agent user to use when TAFC Agent is started in user authentication mode.
AgentPassword- TAFC Agent password to use when TAFC Agent is started in user authentication mode.

T24ConnectorService has a web.config file in which you can configure
T24ConnectorService. Here some of the important aspects of the configuration file is
described.
The WCF service throttling feature enables us to limit the number of concurrent WCF
connections. We recommend setting the maxConcurrentCalls attribute to the same value as
the T24 Service Connector ’s MaxPool property.

The properties shown here enable users to configure additional WCF settings as e.g. the
maximum message size, etc. The file that holds the connection properties is mentioned in
the connectors_config_file key. Therefore if you want to specify your own file instead of
MyConnectors.xml file, then you have to specify the file name here along with the path.
Note: Please refer .NET Windows Communication Framework documentation for further
details.

There are two file for appsettings configuration in TWS project.
Let us see about the configuration files used for TWS:
devenv.exe.config – Used for the configuration purpose of TWS composer (C:\Program

Files\Microsoft Visual Studio 9.0\Common7\IDE\ devenv.exe.config).
In general :
1. WCF service configuration should be given in "devenv.exe.config" (and not in app.config
file in a solution).
2. Addins and Plugins configuration can be specified in devenv.exe.config

web.config is used for configuration of specific web application / web service for ASP .NET
based projects. This file is available under the TWS project created. If you are using IIS to
host your service, use the web.config file.
And the settings that has to be configured are:
ConnectorServiceID: Specifies the Service connector instance (unique) ID configured in

the configuration file (connectors.xml) of T24ServiceConnector.
ConnectorServiceURL: Specifies the respective url configured in the configuration file
(connectors.xml) of T24SeriveConnector.
Note: The displayed values for App settings / Configuration parameter have to be modified
based on the environment where executed.

Now you can configure logging for the TWS project and the T24Connector service.
Logging plays a vital role in any application/product, TWS provides quality logging and ease
in its configuration. There are two files for logging configuration:
devenv.config – Used for logging purpose of TWS composer.
web.config – Used for Web service logging.
The logging technology used by TWS is Microsoft Enterprise Logging and configured under
<loggingConfiguration> element in the config file. There are 5 different categories of logging
such as:
Info – Provides the informative logs
Timing – Provides the time consumed in each layer
Debug – Provides detailed descriptive logs
Decrypted – Provides the decrypted message (OFS)
content
Error – Provides the error logs

By default, logging is enabled and the category filter is defaulted to Info and Error. The logs
are stored in the \External\Logs\ folder for every project created respectively.
There are two different log file names created:

• WebComposer.txt – This file is created to log the TWS composer log information.
• WebService.txt – This file is created to log the Web Service log information.
Note: To configure logging , the configuration files can be modified as required. It is

recommended to install Microsoft Enterprise Library 4.0 to modify the config with ease. Once
installed, right click on the web.config file and choose ‘Edit Enterprise Library configuration’.

web.config file is used for T24 Service Connector logging (Under the T24ServiceConnector
directory). The logging technology used by T24ServiceConnector is Microsoft Enterprise
Logging. There are 5 different categories of logging as discussed earlier.
By default Logging is enabled and the category filter is defaulted to Info and Error. The logs
are stored in the below path for every project created respectively:
T24ServiceConnector\External\Logs\
T24ServiceConnector.txt
This logging ensures that the log entries are consistent and that messages can be inter-
related by means of the request id.

Some hints before you try out this workshop:
1. TWS allows creating web services for Versions and Enquires not for applications.
2. TWS Harness is a tool used to check the connection and message syntax to T24 by
passing OFS Messages using ‘OFS Tester’ tab.
3. soapUI is a tool for functional testing, mainly of Web Services like SOAP based Web
Services and REST Web Services, but also HTTP based services and JMS Services
as well as databases. soapUI is an Open Source tool with a commercial companion,
soapUI Pro, with extra functionality for companies with mission critical Web Services.
4. Windows Communication Foundation (WCF) Test Client (WcfTestClient.exe) provided
by Microsoft is a GUI tool that enables users to input test parameters, submit that input
to the service, and view the response that the service sends back. It provides a
seamless service testing experience when combined with WCF Service Host.

In this unit , you learnt to
Install TWS .NET
Configure TWS .NET
Create, publish and test TWS .NET project
Use strong data type in TWS


Tws PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tws PDF

Uploaded by

Copyright:

Available Formats

Welcome to this learning unit on Installing TWS .NET.

You will learn how to install and setup

TWS3.Install TWS .NET-R12.01 1

Install TWS .NET

TWS3.Install TWS .NET-R12.01 2

Web service is typically an Application Programming Interface (API) or WebAPI that

Web Services Description Language (WSDL) is a XML document that describes

W3C Definition: A web service is a software system designed to support

TWS4.Install TWS EE-R12.01 3

n1 Please change the sentence

n2 Please clarify W3C definition

TWS3.Install TWS .NET-R12.01 4

TWS3.Install TWS .NET-R12.01 5

• Temenos packages these T24 services according to BIAN service landscape.

TWS3.Install TWS .NET-R12.01 6

1. Visual Studio 2010

4. IIS 5.1 and above

TWS3.Install TWS .NET-R12.01 7

TWS3.Install TWS .NET-R12.01 7

TWS3.Install TWS .NET-R12.01 8

TWS3.Install TWS .NET-R12.01 9

T24Service connector provides the following,

More about this configuration file is explained later in this session.

TWS3.Install TWS .NET-R12.01 10

a2 To deploy T24Connector, you need administrator or equivalent permission

For Windows XP or earlier operating system use httpcfg instead of netsh

TWS3.Install TWS .NET-R12.01 11

TWS3.Install TWS .NET-R12.01 12

TWS3.Install TWS .NET-R12.01 13

TWS3.Install TWS .NET-R12.01 14

1. T24 produces XML Schema to denote an underlying Business Operation.

2. A webservices generator (i.e.- TWS Composer), is used to create web services

TWS3.Install TWS .NET-R12.01 15

Gerard Thomas, 2/1/2011

TWS3.Install TWS .NET-R12.01 16

TWS3.Install TWS .NET-R12.01 17

TWS3.Install TWS .NET-R12.01 18

TWS3.Install TWS .NET-R12.01 19

TWS3.Install TWS .NET-R12.01 20

TWS3.Install TWS .NET-R12.01 21

TWS3.Install TWS .NET-R12.01 22

TWS3.Install TWS .NET-R12.01 23

TWS3.Install TWS .NET-R12.01 24

TWS3.Install TWS .NET-R12.01 25

TWS3.Install TWS .NET-R12.01 26

TWS3.Install TWS .NET-R12.01 27

TWS3.Install TWS .NET-R12.01 28

TWS3.Install TWS .NET-R12.01 29

TWS3.Install TWS .NET-R12.01 30

TWS3.Install TWS .NET-R12.01 31

TWS3.Install TWS .NET-R12.01 32

TWS3.Install TWS .NET-R12.01 33

TWS3.Install TWS .NET-R12.01 34

TWS3.Install TWS .NET-R12.01 35

TWS3.Install TWS .NET-R12.01 36

TWS3.Install TWS .NET-R12.01 37

TWS3.Install TWS .NET-R12.01 38

TWS3.Install TWS .NET-R12.01 39

TWS3.Install TWS .NET-R12.01 40

Publish will work with Adminstrator or equivalent rights

•Specify Service URL and Site/Application.

TWS3.Install TWS .NET-R12.01 41

TWS3.Install TWS .NET-R12.01 42