Browser Installation-R10.01

8/19/2019 Browser Installation-R10.01

http://slidepdf.com/reader/full/browser-installation-r1001 1/81R2.Browser Installation-R10.01

Welcome to the learning unit on Browser Installation. This learning unit teaches you to

install a T24 area with browser as its front end.


http://slidepdf.com/reader/full/browser-installation-r1001 2/81R2.Browser Installation-R10.01

After completing this course you will be able to :

1. Explain the T24 architecture.

2. Explain Temenos Open Connectivity Framework

3. Identify the different Components required for Browser installation in both

the architectures

4. Create a T24 area with the Browser as its front end.

5. Install T24 Browser on Windows environment.


http://slidepdf.com/reader/full/browser-installation-r1001 3/81

Earlier the T24 architecture comprised of the following components – presentation layer, web layer, T24

application server layer and the database layer.

The Presentation Layer consists of web browser and the web server. Web browser - This is the front end

that the clients will be using to access data in T24. The web browser used can either be Internet Explorer

or Mozilla Firefox .

Web Server – Any request that is initiated from the Web Browser is always a HTTP or a HTTPS request.

T24 cannot understand this request directly so a Servlet named T24 Browser has been developed in order

to modify the HTTP request. In order to deploy a servlet , a servlet container is required and hence a Java

compliant Web Server is used. Why do we need this servlet? Any request that we send from the Web

Browser needs to be understood and converted into a form that T24 understands. It is the T24 Browser

Servlet that understands and converts all HTTP/HTTPS requests into Browser XML. Browser XML is a

request format that is directly understood by T24.At the moment this is not a published XML format and

hence third party systems that wish to communicate with T24 cannot send their request in this format. Now

that the request has been converted into a format that T24 understands, the request has to be sent to any

one of the T24 Application Servers.

How will the web server and the application server communicate with each other? The answer is – Using

components called Temenos Connector Client henceforth referred to as TCC and the Temenos Connector

Server henceforth referred to as TCS. As their names imply, these two components are based on a client

server architecture. The TCC will reside on the Web Server and the TCS will reside on T24 applicationServer. The job of TCC is merely to act as a mediator between the Web Server and the T24 Application

server. The Browser XML request that is formed by the T24 Browser Servlet will be passed on to the TCC.

TCC will send the request to TCS running on the T24 Application Server. It is the TCS that will send the

request to T24.All requests coming into T24 must come via the TCS.

The T24 Application Server Layer consists of Temenos Connector Server, T24 with the OFS module

installed and jBASE. This is the T24 server and there can be more than one of them. Each of these servers

will contain a separate T24 installation and jBASE installation. Each server must be a mirror image of the

other. TCS is the entry point into T24. Once the TCS passes the request to T24, the request is processed

as and T24 updates the data held in jBASE. If a database other than jBASE is used, the corresponding

Direct Connect Drivers must be installed and configured in order to communicate with the external

database.

R2.Browser Installation-R10.01



Database Server - T24 is database independent, and supports several different databases, including

Oracle,DB2,SQL Server and of course jBASE. This is where the T24 data will reside in XML format. There can be

multiple database servers only if the database supports clustering.




With the new architecture, the web server is now replaced by the application server. T24 Browser Servlet is

deployed in Jboss. Your TCC is now replaced by jremote-ra.rar.

Why do we need an application server rather than a web server?

A web server receives HTTP requests and responds with HTTP response. The delegation model of a web

server is fairly simple, it just hands over the request to an application best able to handle it. The webserver does not support transaction or database connection pooling features. On the other hand, an

application server provides access to the business logic for use by client application programs. An

application server provides more features than a web server. For example Load Balancing, Deployment

API, connection pooling and so on.

Earlier TCC communicates with the TCS to forward requests to T24. With the advent of the new

architecture, we no longer use the components – TCC and TCS. TCC is replaced by jremote and TCS is

replaced by the jbase_agent. So the requests are now forwarded to the jbase_agent. The jbase_agent

then forwards the incoming request to the T24 application server.

How does the Jboss app server and T24 application server communicate with each other?

Temenos has introduced a new framework to facilitate the communication between Jboss and T24.

Temenos Open Connectivity Framework (TOCF) is introduced with R09 architecture. From R09, TOCF

acts as the entry point to T24.

With the new architecture we now have the Temenos Application Framework that provides TAFC as the

runtime environment. The jBASE runtime environment is now known as TAFC!




Let us now look into the technical details of the new architecture,

Presentation Layer: The Presentation Layer consists of web browser. Web browseracts as the front end for the clients to access T24. All that the user needs to do is tosupply a ‘url’ that will enable him to connect to T24.

Application Server : Any request that is initiated from the Web Browser is always aHTTP or a HTTPS request. T24 cannot understand this request directly so a Servletnamed T24 Browser Servlet has been deployed. An application server is used todeploy the servlet. Why do we need this servlet? Any request that is sent from theWeb Browser needs to be understood and converted into a form that T24 understands.It is the T24 Browser Servlet that understands and converts all HTTP/HTTPS requestsinto Browser XML. Browser XML is a request format that is directly understood byT24.At the moment this is not a published XML format and hence third party systemsthat wish to communicate with T24 cannot send their request in this format.

The next step is to forward the request to any one of the T24 Application Servers.

Temenos Open Connectivity Framework (TOCF) has been introduced with R09architecture. TOCF acts as the entry point to T24. With TOCF ,T24 provides thefollowing features of an application server - connection pooling, security andconfiguration.

TOCF comprises of components that provides Java Enterprise Edition compliantconnectivity to T24. Java Component Architecture (JCA) is the J2EE standard forapplication server connectivity to external systems. The Connector Architecturedefines a common interface between application servers and EIS systems. The resultis simplified enterprise application integration, using a scalable, standard architecturethat leverages the benefits of the J2EE platform.




TOCF : Temenos Open Connectivity Framework provides the connectivity to T24application server. TOCF(EE) currently supports two architecture – AGENTarchitecture and JMS architecture.

The T24 Application Server Layer consists of T24 with the OFS module. This is theT24 server and there can be more than one of them. Each server must be a mirrorimage of the other. TOCF is the entry point into T24. Once TOCF passes the requestto T24, the request is processed and T24 updates the data held in JBase. If adatabase other than jBASE is used, the corresponding Direct Connect Driverscommunicates with the external database.

Database Server - T24 is database independent, and supports different databases,including Oracle,DB2,SQL Server and of course jBASE. It is in this database serverthat Oracle/DB2/SQL ServerJ4 is installed. This is where the T24 data will reside inXML format. There can be multiple database servers only if the database supportsclustering.

From R09, TOCF acts as the entry point into the T24 application server. So even yourexternal interfaces communicate with T24 using this TOCF.




TOCF supports two architectures – Agent architecture and JMS architecture.

AGENT allows the T24 Browser to connect directly to T24 using the TAFC JCA

(currently called jremote) and the jbase_agent .

Lets now look into the components of TOCF:

TAFC JCA – The T24 Browser sends requests to TOCF using TAFC JCA. TAFC JCA

is distributed as jremote. Jremote- is the client side jBASE component that sends

requests to T24 through TOCF. Lets now see which component handles the incoming

requests.

jbase_agent – Jremote communicates to TOCF using the jbase_agent. Jbase_agentis a server-side jBASE component responsible for accepting and processing incoming

client requests. This executable is the process you will see running on the T24 server

for each connection the application server has created. Communication is established

via TCP socket connections. Jbase_agent is a socket server listening on a user-

defined TCP port and has the capability to serve a wide range of client applications.




Let us now have a look at the components that are required for browser installation

using the agent architecture,

1.A browser – Temenos recommends the Internet Explorer

2. The latest version of Java Runtime Environment.

3. Install TAFC

4. The JBoss application server (4.2.3.GA) must be downloaded and installed on your

machine.




Install the components in the following order

1.First Java

2.Then install TAFC

3.Finally install Jboss




This learning unit deals with the installation on a Windows OS. You will first learn the

installation on a Windows platform. All components are installed on one system only.

In other words, this is a localhost installation process.




1.Audio for screen shot 1

The first component to be installed is Java. If Java is already installed in your

system, then check if it is the latest version by typing ‘java –version’ at the

command prompt. If an older version of Java is installed, uninstall it and thenre-install java 1.6.






The next component to be installed as part of browser installation is TAFC

1. Install TAFC under the C drive using the “TAFC_R10_GA_Win32” file




1.The JBoss application server (4.2.3.GA) must be downloaded and installed on your

machine. The JBoss Application Server can be downloaded from http://jboss.org/ .

2. To install the JBoss application server simply unzip the file onto your C directory,

which will extract the files onto a folder as displayed.




You can check if JBoss has been installed properly by executing the run.bat file from

the following path C:\jboss-4.2.3.GA\bin\run.bat. The console shown here will be

displayed to you and if no errors are encountered , you have successfully installed the

JBoss application server.




In order to enable the T24 Browser to communicate with TOCF, the following

configurations should be done at the JBoss application server level:

1. The client component jremote should be deployed in Jboss. Therefore copy

jremote-ra.rar to the path C:\Temenos\R10\jboss-4.2.3.GA\server\default\deploy

2. The jremote-ra.rar file can be copied from the following path ,

C:\TAFC\R10\java\lib

3. You have now configured the T24 Browser, but how will the browser communicate

to T24?

T24-ds.xml is the file where you will specify the ip address and port number using

which the browser communicates to T24. You will also specify the OFS.SOURCErecord id here. Save t24-ds.xml in the following path C:\Temenos\R10\jboss-

4.2.3.GA\server\default\deploy.

Note: t24-ds.xml can be downloaded from knowledge base.




1. JNDI stands for Java Naming and Directory Interface.

2. JNDI is a Java API for naming and directory service that allows Java software

clients to discover and look up data and objects via a name.

3. A naming service associates names with distributed objects, files, and devices so

that they can be located on the network using simple names instead of cryptic

network addresses.

4. Using JNDI, JMS clients can browse a naming service and obtain references to

administered objects without knowing the details of the naming service or how it is

implemented.




In t24-ds.xml the following information should be specified in order to enable the T24

browser to communicate with TOCF:

1. Jndi name – The jndi-name is used to connect to the T24 environment. The Java

Naming and Directory Interface (JNDI) is a naming service. It allows Java softwareclients to look up objects in a network via a name.

2. Ip address of the server

3. Port number

4. Id of ofs source record id




1. You may change the port on which the Jboss service gets executed. The

connector port for the jboss application server is configured in server.xml file which

can be found in the following path C:\Temenos\R09\jboss-

4.2.3.GA\server\default\deploy\jboss-web.deployer.

2. By default the connector port is set to port 8080. In the screen-shot shown the

connector port is assigned to port 9090.

Note: If you have an R08 area installed on your machine, Tomcat could be configured

on port 8080, Hence specify a different port for Jboss application server.




1.To ensure if JBoss is started, type http://localhost:9090 in the address bar of your

Internet Explorer Window to get to the admin page of JBoss as shown.




To deploy a T24 Browser in JBoss copy the BrowserWeb war file to the following

location:

[JBoss Install Directory] \server\default\deploy

For example, C:\jboss-4.2.3.GA\server\default\deploy.

Launch JBoss and ensure that the applications have been deployed correctly.




The next step is to configure the browserParameters.xml file. T24 Browser uses the

JCA connection method to send request to the T24 application server. The server

connection method is configured in browserParameters.xml file




How will the T24 browser forward the requests to jremote agent? From there how will

the jremote agent forward the request to T24?

The jndi-name specifies the connection object , which the browser has to check in t24-

ds.xml. So to check for the connection object in t24-ds.xml, the browser should know

the name of the connection object. The jndi name of the connection object is specified

in jboss-web.xml which can be found under the WEB-INF folder of BrowserWeb.war.

This should be the same jndi –name as configured in t24-ds.xml




1.Create a T24 area for the user. To do this -

1.1.Copy the file on to any location in your machine. Configure the bnk.run directory

.This is the HOME directory of the user. Check if the following variables are set

correctly – HOME and JAVA_HOME




1.Create an operating system level user by clicking on

Start->Settings->Control Panel->Administrative Tools->Computer Management->Local

Users And Groups->Users

Choose Action->New User from the menu bar

Type in User name, Full name ,Description as temenos and Password ,Confirm

password as password

Uncheck ‘User must change password at next logon’

Check ‘User cannot change password’

Check ‘Password never expires’

Click on the ‘Create’ Button.




1. Audio screen shot 1

For the user created as temenos , set the local path to the path of the ‘bnk.run’

directory by doing a Right click on the user ‘temenos’ and choose ‘properties’ and

input the HOME directory path for the fields ‘profile path’ and ‘Local path’.






1. Many default sign on names and passwords are available. Log in to check if the

T24 installation is a success. (AUTHOR/123456 or INPUTT/123456). Once logged in,

you may create your own USER profile.




You need to start the jbase agent before you login into T24 using the browser. To start

the jbase agent specify the following command from the jshell prompt – jbase_agent –

p [PORT_NUMBER]. For example jbase_agent –p 9797.




Start the JBoss application server by executing the run.bat file found under the bin

directory of JBoss.

Once the jbase_agent has been launched and JBoss is started you will be able to login

to T24 in the normal manner.




1. The first step towards connecting to T24 is to connect to the Jboss application

server. Since the application server server is installed on the local PC, we specify

localhost. You may choose to give the IP address of the PC as well. 9090 is the

port where Jboss is running. The port number is configurable in server.xml. The

default port for Jboss is 8080. Incase you wish to connect to an application serveron some other PC, all that you need to do is to replace localhost with the IP

address of the appropriate PC. BrowserWeb – Is the servlet that has been

deployed. servlet/BrowserServlet – Enables us to invoke the ‘BrowserWeb’

servlet.




Let us see how to configure multiple T24 environments with the new R09 architecture.

1.Deploy the T24 Browser Servlet. Ensure that you rename the BrowserWeb.war (the

default name) to a name that best describes the release of T24 that you are using

2.Start JBoss and wait until the servlet gets deployed. Invoke the Jboss webconsole

page and check if the new servlet is listed. The ‘Full Status’ column denotes that there

is one connection to this servlet.

In this example, the BrowserWeb.war file has been renamed to BrowserWeb2.war and

hence you see this servlet listed above.




For each of the T24 environment the following information should be configured in the

t24-ds.xml file:

1. Jndi name

2. Ip adress of the server

3. Port number – Specify a different port number for each of the T24 environments

4. Id of the OFS resource record

You have now specified the configuration information at the T24 level. How will the

browser get to know these configuration information?




After you specify the configuration information in t24-ds.xml, you need to set the

following configuration information at the browser level:

For each of the T24 environment , a servlet is deployed in the Jboss application

server. Each war file contains a jboss-web.xml file under the WEB-INF directory. In the

jboss-web.xml file you specify the jndi name configured for each T24 environment. For

example, BrowserWeb2.war holds the jndi name as

t24ConnectionFactoryBrowserWeb2. This should be the same jndi name configured in

the t24-ds.xml file.




1.After you specify all the configuration information, for each of the T24 environments

ensure that a record with ID T24BROWSER exists in the OFS.SOURCE application.

Otherwise create it with Source Type set to SESSION and Syntax type set to XML.




Open new telnet sessions and start the jbase_agents at the respective port numbers

as configured in t24-ds.xml




Start the JBoss application server by executing the run.bat file found under the bin

directory of JBoss.




1.Can we login to both the environments simultaneously? The answer is - yes




1. The JMS API is an integral part of the Java platform, Enterprise Edition.

2. The Java Message Service API is a messaging standard that allows application

components to send and receive messages. It enables distributed communication

that is loosely coupled, reliable, and asynchronous.

3. Java Message Service is the new standard for inter-client communication.

Enterprise messaging provides a reliable, flexible service for the asynchronous

exchange of messages throughout an enterprise.JMS provides a flexible and

powerful API that encourages a fine-grained, modular distribution of functionality

among application components.




The JMS architecture is introduced to provide enhanced resilience and load balancing.

Both the architectures are fundamentally the same, they both lookup the TAFC JCA

and they both call OFS.BULK.MANAGER as the entry point to T24.Let us now have a

look at the role of each component in the JMS architecture,

OFSMessageMDB - In the JMS architecture, the in coming requests are dropped onto

a queue. These in-coming requests should be processed by T24. Now who is going to

forward the requests to T24?

OFSMessageMDB is the component that picks up the requests from the queue. The

message driven bean acts like a listener.

jremote – The OFSMessageMDB hands over the request to the TAFC resource

adapter. The OFSMessageMDB looks up the TAFC resource adapter (currently called

the JRemote JCA) and performs a remote subroutine call to OFS.BULK.MANAGER.

When OFS.BULK.MANAGER has performed the T24 process the MDB then places

the response onto the response queue.




Ensure that the following components are installed on your machine before, you start

the installation process.

1.A browser – Temenos recommends the Internet Explorer

2. The latest version of Java. Ensure that you also set the environment variable

JAVA_HOME to the latest version of java installed.




The following are the components that are required for browser installation using the

JMS architecture,

1. Install TAFC

2. The JBoss application server (4.2.3.GA) must be downloaded and installed on

your machine.

3. Next step is to deploy the BrowserWeb.war file

4. After browser configuration, deploy the OFSMessage message driven bean. The

OFSMessageMDB can be found inside the tocfee.ear.

5. Finally deploy the TAFC resource adapter




What is an archive file?

An Enterprise ARchive, or EAR, is a file format used by Java EE for packaging one or

more modules into a single archive so that the deployment of the various modules

onto an application server happens simultaneously and coherently. It also contains

XML files called deployment descriptors which describe how to deploy the modules.

The following components can be found in tocfee.ear:

1. delivery-ejb.jar

2. ofsmessage-ejb.jar

3. tocfcommon.jar

4. tocflistener-ejb.jar

5. tocfplugin-ra.rar






1. When you execute the unpack.bat file, the artifacts of tocfee.ear will be extracted

onto a work directory as shown. Each of the artifacts will be extracted onto a folder

with .tmp extension.

2. The configuration files for ofsmessage-ejb.jar can be found under ofsmessage-ejb.jar.tmp. You can make changes to the files under this folder.




1. After you make the changes to the configuration file, you need to repack the

contents of tocfee.ear so that it is updated with the new configuration settings.

2. Execute the pack.bat file which will pack the artifacts again into a new ear file. The

new tocfee.ear file will be created under a temporary folder . Copy the tocfee.earfile to the deploy directory of jboss.






The server connection method is configured in browserParameters.xml file. For the

JMS architecture, the server connection method should be set to JMS in the file

browserParameters.xml.




The t24 data source connection file is used to specify the resource adapter for which,

you want a pool of connections for and the jndi name of this pool. A connection pool is

only required for “outbound” resource adapters – e.g. the TAFC resource adapter

(jremote-ra.rar)

After you specify the name of the connection object, you should also configure the ip

address of the host, port number and OFS source record id.

Now the jbase_agent will listen on port 9494 as per the configuration details.




The request and response queues are configured in the t24-destinations-service.xml

which, can be found under the deploy directory of Jboss. The screen shot displayed

here defines two queues called “t24OFSQueue” and “t24OFSReplyQueue”.

The message driven bean acts as a listener and processes the request that is droppedinto the request queue. Once the requests are processed, it is placed in the response

queue.




In the next step you will deploy a Message Driven Bean in Jboss. The

OFSMessageMDB can be found inside the tocfee.ear.




In order to deploy the tocfee.ear component you can make use of the utilities for

packing and unpacking the artifacts.

1. Copy the tocfee.ear, pack.bat and unpack.bat under any directory

2. Execute the unpack.bat file which will extract the contents of tocfee.ear onto a

directory called work. Each of the artifacts under tocfee.ear will be extracted onto a

temporary directory with .tmp extension. You may configure the files for

ofsMessageMDB and the ear file can be packed again with new configurations. To

pack the ear file execute the pack.bat file which will create the tocfee.ear file with

the new configuration settings.

3. To deploy the tocfee.ear file copy it to the deploy directory of jboss




After the requests are dropped in the request queue, you need a message driven bean

to pick up the request and process it. Therefore the message driven bean

configuration is specified in the ejb-jar.xml file of ofsmessage-ejb.jar. The

OFSMessage MDB looks up the TAFC resource adapter (currently called the JRemoteJCA) and performs a remote subroutine call to OFS.BULK.MANAGER with the OFS

request from the OFS request queue. When OFS.BULK.MANAGER has performed

the T24 process the MDB then places the OFS response onto the OFS response

queue.

Note: The ejb-jar.xml file can be found under the ofsmessage-ejb.jar.tmp folder.

Implement the changes to ofsmessage-ejb.jar and repack the tocfee.ear file.




The OFSMessageMDB should know from which queue it has to pick up the requests

and it should also know onto which queue it has drop the responses. These

configurations are specified in the file jboss.xml of ofsmessage-ejb.jar. Here the

requests are dropped in t24OFSQueue and the responses will be placed int24OFSReplyQueue.






Before you log into browser, the jbase_agent should be started on port 9797.




Now start the Jboss app server also.




1. Since the application server server is installed on the local PC, we specify

localhost. You may choose to give the IP address of the PC as well. 9080 is the

port where Jboss is running. The port number is configurable in server.xml.

BrowserWeb – Is the servlet that has been deployed. servlet/BrowserServlet –

Enables us to invoke the ‘BrowserWeb’ servlet.




You may need multiple T24 environments to work on. Here you will learn to configure

multiple T24 instances using the JMS architecture.

1. The components that are to be configured for multiple T24 environments are as

follows:

1.1 BrowserWeb

1.2 OFSMessageMDB

1.3 TAFC Resource Adapter – jremote

2. Files that are to be configured are :

2.1t24-destination-services.xml

2.2 ejb-jar.xml in ofsmessage-ejb.jar

2.3 jboss.xml in ofsmessage-ejb.jar

2.4 t24-ds.xml








You can use the same ofsmessage-ejb.jar that was deployed earlier.




The jremote component forwards your requests to the T24 application server using the

jbase_agent.




As you need to communicate to the T24 area now, you need to configure the request

and response queues. These queues are configured in the t24-destinations-

service.xml which, can be found under the deploy directory of Jboss. The screen shot

displayed here defines two queues called “t24OFSQueueTestArea” and

“t24OFSReplyQueueTestArea” . Henceforth these queues will be used for theTestArea.




You have configured the queues, but who is going to pick up the requests from the

queue?

To process these requests you need to create a Message Driven Bean. The message

driven bean acts as a listener and processes the request that is dropped into therequest queue. Once the requests are processed, it is placed in the response queue.

Lets us now see the steps to create a message driven bean. In order to create a MDB,

edit ejb-jar.xml in ofsmessage-ejb.jar and create a new message driven instance.

TestAreaOFSMessageMDB is the new MDB created for the new T24 environment.

Extract the artifacts of tocfee.ear. To modify the file ejb-jar.xml, use the ofsMessage-

ejb.jar.tmp folder under the work directory. After you make changes to this file, rebuild

the tocfee.ear file using the pack.bat file.

Note: To create a new MDB copy the set of tags from <meesage-driven> to</message-driven> and make the modifications to the latest copy and rebuild your jar.




Ensure that the T24 Queue Connection Factory is configured to

jms/jmsConnectionFactory.




The TestAreaOFSMessageMDB should know from which queue it has to pick up the

requests and it should also know onto which queue it has drop the responses.

These configurations are specified in the file jboss.xml of ofsmessage-ejb.jar.

1. The requests are dropped in t24OFSQueueTestArea

2. The responses will be placed in t24OFSReplyQueueTestARea

3. Also specify the JNDI connection object here.




The jndi name of the connection object should be specified in t24-ds.xml. Also specify

the ip address of the host, the port number and OFS source record id.

Important Note: Speciy a different port number to communicate to a new T24

environment.






1. Log into the telnet sessions and start the jbase agents for each T24 environment.




Start the Jboss App Server also.




You can now log into both the T24 areas simultaneously!




1. There are various components that are required for Browser to work on T24

2. Errors may arise in the process of installation of any of these components

3. Errors may arise in any of the following components

3.1 java

3.2 JBoss

3.3 jremote




1. Always ensure that java version of 1.5 or above is installed

2. The JAVA_HOME environment variable should point to the jdk 1.6




Earlier you used to set time out interval in tcserver which is the time limit upto which

the tcserver session waits for the response from T24 server for each request sent from

the browser. Now where do you specify the TIME OUT parameter?

To set time out parameter, you need to configure your t24-ds.xml and set the property

- actionTimeout. This property will cause the jbase_agent process to exit if T24 does

not process the request within the configured number of seconds.

Note: The reason T24 could take longer than 30 seconds is due to a lock collision or a

very slow query.




The error ‘ Could not connect to remote jBASE instance’ , has occurred when a user

has tried to loginto T24 . If you take a look at the displayed error message it tells you

about the host ip address and the port number using which the browser communicates

with T24. Therefore it implies that the jbase_agent has not been started on portnumber 7001.




netstat (network statistics) is a command-line tool that displays network connections

(both incoming and outgoing). You can specify the command netstat –a –n –p followed

by protocol name, to know the status of all connections for the specified protocol.

The –a option displays all active TCP connections and the TCP and UDP ports onwhich the computer is listening.

The –n option displays active TCP connections, however, addresses and port

numbers are expressed numerically and no attempt is made to determine names.

The -p Protocol : Shows connections for the protocol specified by option Protocol. In

this case, the Protocol can be tcp, udp, tcpv6, or udpv6. If this parameter is used with -

s it displays statistics by protocol.




By now you must be able to

1. Explain the T24 multi-tier architecture

2. Explain TOCF

3. Identify the different Components required for Browser installation.

4. Create a T24 area with the Browser as its front end .

5. Install T24 Browser on Windows




1. Who converts the http request into Browser xml?

a. Web Browser

b. jremote

c. T24 Browser

d. Jbase agent

2. Which is the entry point of T24 from third party systems?

a. Web Browser

b. T24 Browser

c. jremote

d. TOCF

3. Who sends the request to jbase agent?

a. Web Browser

b. Web Server

c. jremote

d. T24 Appl icat ion server

4. Which of the following request format is directly understood by T24?

a. HTTP

b. HTTPS

c. Browser XML

d. XML

5.In which layer does the business logic reside?

a. Presentati on layer

b. Web Server

c. Application Server layer

d. Database server layer

6.Which is the HOME directory of T24 user?

a. bnk.dict

b. Bnk.data

c. Bnk.run

d. Bnk.interface7.What is configured in t24-ds.xml?

a. Jndi connection object, ip address of the host , port number and OFS SOURCE record id.

b. Listeners

c. Channels

d. Listeners,channels

8. In which port does JBoss run run in case of l ocalhost?

a. 7001

b. 20001

c. 8080

d. 7002

9. ___________ enables us to invoke the servlet ‘Browser.Web’.

a. T24 Browser

b. TCS

c. TCC

d. Servlet/BrowserServlet




Date post:	07-Jul-2018
Category:	Documents
Upload:	donakomeah
View:	448 times
Download:	51 times

Browser Installation-R10.01

Documents