55 pages

English

FADA tutorial

Endrui

Le téléchargement nécessite un accès à la bibliothèque YouScribe
Tout savoir sur nos offres

55 pages

English

Le téléchargement nécessite un accès à la bibliothèque YouScribe
Tout savoir sur nos offres

A propos
Informations
Extrait

Description

FADA tutorialFADA tutorial - Revision historyDate Version Description Author30 June 2004 1.0 Initial Javier NogueraJ.N oguera 2FADA tutorial - Table of contentsTable of contentsTable of contents................................................................................................................2Foreword....... ... ..... ... ..... ... ..... ..... ... ..... ... ..... ... ..... ..... ... ..... ... ..... ... ..... ... ..... ..... ... ..... ... ..... ... ....3Int roduction........................................................................................................................4What is FADA ?...................................................................................................................5Why FADA ....... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ....... ..... ..... ..... ..... ..... ..... ..... ..... ..... ..... ....8FADA Ex amples..................................................................................................................9Do-it -y ourself.................................................................................................................9Fadagen..................... ..................... ................... ................... ..................... ..................16J2ee........................................... ........................................... ........................................22FADA nodes over a LAN ........................................ ...

Informations

Publié par	Endrui
Nombre de lectures	81
Langue	English

Extrait

FADA tutorial

Date 30 June 2004

Version 1.0

J.Noguera

Revision history

Description Initial

FADA tutorial -

Author Javier Noguera

Table of contents

FADA tutorial - Table of contents

Table of contents................................................................................................................2 Foreword.............................................................................................................................3 Introduction........................................................................................................................4 What is FADA ?...................................................................................................................5 Why FADA...........................................................................................................................8 FADA Examples..................................................................................................................9 Do-it-yourself.................................................................................................................9 Fadagen.......................................................................................................................16 J2ee..............................................................................................................................22 FADA nodes over a LAN....................................................................................................27 Renewal Event..................................................................................................................29 Security Wrapper..............................................................................................................31 Annex A............................................................................................................................33 Client and Service interface.........................................................................................33 Do-it-yourself...............................................................................................................36 Fadagen.......................................................................................................................44 j2ee..............................................................................................................................50

J.Noguera

Foreword

...

FADA tutorial - Foreword

We hope you find the information contained here complete and useful.

Enjoy it.

J.Noguera

The FADA development team.

Introduction

FADA tutorial - Introduction

This user manual tries to help programmers to work with FADA technology. It includes examples and explanations about the most important FADA scenarios. In the first chapter there is a short explanation about FADA itself and about FADA from the point of view of the client and the server. If you need further detailed information about FADA architecture you will find it in the file namedCore FADA. It explains in depth the bases of FADA, FADA nodes communication, etc. In the second chapter we there is a discussion about the use of FADA and the cases in which FADA may be necessary. In the third chapter there are some FADA scenarios: do-it-yourself, fadagen and fada J2EE. We will implement a solution in all three scenarios using FADA with the same example. You will find all the code for the three examples in the Annex A. It can be used as a reference.

Fada Node

J.Noguera

Fada Node

FADA network architecture

Fada Node

What is FADA ?

FADA tutorial - What is FADA ?

FADA stands for “Federated Advanced Directory Architecture”. It is a virtual Lookup Server in the sense that different Lookup Servers (FADA nodes) will work together to provide the LookupServer functionality from any entry point. Also, any of these Lookup Servers will cooperate with the rest to find implementations of services. The FADA is a truly distributed system, in the sense that there is no central authority or common communication channel. The FADA holds proxies for services. A proxy is a Java class that acts as a mediator between client and service provider performing communication with a real service, and that is downloaded at run-time by clients. Clients use the public methods on the proxies to access the services. These public methods are specified in Java interfaces that service proxies implement. A FADA node is a service that acts as an entry point and a container to the distributed database of services. Service providers must implement Java classes that act as a gateway to use their services, which may be written in Java or not. In case they aren't, the Java class they provide to the FADA clients, the service proxy from now on, can use whatever method to communicate with the service. For example, the service could be written in C, or it could be accessed through http, and the service proxy could open sockets to the proper ports to communicate with the service. Note that these proxy objects will be executed in the client's machine, so this fact must be taken in account when designing and implementing service proxies. Java, C, Php, Perl, Web Service, Corba, sp .NET, ...Proxy 1 Accessible by HTTP protocol Fada NodeProxy 2 ... Machine #2

Service 1 codebase Server Machine Situation after registration

J.Noguera

FADA tutorial - What is FADA ?

How FADA works Let's see now, more in detail, one FADA node and the steps used by the server to register a service and by the client to look for a service. One server who wants to register a service in a FADA node needs: 1.To have a service running. It is necessary to difference between service andproxy. The service must be running over any machine and can be implemented with any language or technology. The proxy is a little piece or code that knows how to communicate with the service. 2.To define a service interface. This interface will define the methods that the client can execute to communicate with the service. This interface is accessible to all clients and must be coded in Java language. 3.To code a service proxy. The proxy is the implementation of the service interfaceand it is the way in which the client executes the service on the server side. The proxy class will be executed on the client side, this has to be taken in account when implementing it. It has to be coded in Java language. 4.To register the proxy in one FADA node. When the proxy is uploaded to one FADA node it is available for any node within the FADA network. Clients now can discover and use the service. 5.Make accessible a jar file with libraries. Proxy implementation is not known by the clients so it has to be downloaded. The server needs to make accessible all extra classes in a jar file to be used by service proxy. The location of this jar file is named codebase.

Dynamically downloaded and loaded Proxy 1 Fada NodeProxy 2 ... 1. look up the serviceClient 2. download the proxyprogram and the extra classes Machine #2Proxy 1 codebase 3. execute service on serverJRE Client Machine Situation after discovering

J.Noguera

FADA tutorial - What is FADA ?

One client who wants to use a service (previously registered in the FADA network) needs to follow the next steps: 1.To have the service interface in the classpath. Client does not need to know anything about service or proxy implementation but service interface must be accessible for compiling.

2.Discover the service discover the service, client needs to. To know the name of the service interface (and optionally some of its entries) and the address of one FADA node that is part of the FADA network.

3.Download and execute the proxy. After discover the service, FADA framework will automatically download and load the proxy in memory using the codebase. Proxy is now ready to be used by client therefore client will communicate directly with the service running on the server.

J.Noguera

Why FADA

FADA tutorial - Why FADA

FADA allows the servers to publish one or more services and make them accessible to everyone. On the other hand, FADA allows to the clients to find any published service and use it. Client does not need to know how the service is implemented neither where it is. Client only must find the service and, this is the good thing, FADA assures us that the service is working. We can imagine, for example, that we usually use FADA to access to a printer service located over Internet (ie. A photo-shop store). One day the printer is moved (its IP and name have changed). This is not a problem, because a new proxy will be registered by the server. If the printer is changed and a new protocol is needed, it is not a problem either, because a new proxy will be implemented and re-registered in the FADA network. If the server is down and unaccessible the proxy will be unregistered automatically and no client will be able to use that printer. Thinking of FADA we can list situations in which it can be used and in which it improve the development, the performance and the accessibility: •If you need a distributed system over Internet (WAN) where many servers offer many services for clients. •the service nature is noncontinuous. In this scenario, clients If cannot access to the service at any moment. FADA assures the client will not find the service if it is down. If the service implementation can often change. The proxy will • code the new implementation without client knowledge. •f Ivehau yoteysmstnerepO itarS gnystem with diffea d sirtbitudes and/or different applications languages and you want to access in the same way them all... of course, in Java. • If you want to connect two or more different applications. To publish their service interfaces is the easiest way to integrate them.

J.Noguera

FADA Examples

FADA tutorial - FADA Examples

We will discuss now some scenarios in the use of FADA. This chapter is a technical reference for programmers where they can see how to use FADA API. The sample code can be found at the end of the document (Annex A) You can access directly to the most suitable scenario: • Do-it-yourself. The easiest way to understand FADA. There is a standalone service with and a customized protocol and it is necessary to code and register the proxy. • Fadagen. The easiest way to create a service. There is no service nor proxy but FADA will code them both for us. • J2EE. We can code the service like a servlet in an Application Server and register it at start up. We will use the same example in all three scenarios: “There is a server where users can be added or removed. A client looks for the service (discovers it over FADA network) and add his/her username. Clients can also get a list of usernames from the server”. Do-it-yourself scenario In the first case we begin with a server running and waiting for clients. It can be coded in any language and it can implement any protocol (http, simple xml, soap...). To register this service in the FADA network we only need to define the service interface and to code the proxy. Server In our example the server implements it own communication protocol: One character that indicates the action and one argument if needed. There are four possible actions: • name>”Add a user: “A <user _ •Remove a user: “R <user name>” _ •List usernames: “L”. Returns a list of usernames separated by “#” token.

J.Noguera

FADA tutorial - FADA Examples

•Quit: “Q”. This stops the server. We can run the service before registering the service. We will leave it listening on port 2727. java net.fada.examples.uptoyou.Userlist 2727 Users who do not want to use FADA can access to the server now. We will still wait until the service will be registered. Service interface Now we have to define the server interface. This interface is used by clients to access to the server, so, we need to define the methods to be used by clients. In this example we will authorize the clients to add, remove and get a list of usernames, but they will not stop the server. public interface RemoteUserList { public void register (String name); public void unregister (String name); public String getRoomName (); public String [] getList (); } We can notice three important aspects of the interface definition: First, we have not define a quit method, so we will not allow users to stop the server. Second, thegetList will return an array of method usernames instead of a usernames list separated by “#” token. And third, we have added an extra method calledgetRoomNamenot known by the server but, in this case, known by the proxy. Client must know the interface before compiling so it has to be well done and preview future changes. Changes in the implementation (proxy) will not affect to the client, changes in the interface will do. Now we have the definition of the service, let's implement it with the proxy class. Proxy The proxy class implements theRemoteUserList and, of interface course,java.io.Serializable. If the proxy does not implement java.io.Serializable will not be able to be register in the FADA it node. In our example, the proxy class will open a socket to the server for each action (exceptgetRoomName method) . As you can see, to implement the proxy it is necessary to know how to communicate with the server. It is also necessary to know the address and port

J.Noguera