Gt3 software architecture model

For questions or feedback about this website: System level services are OGSI-compliant flobus services that are generic enough to be used by all other grid services. In particular, it is comprised of the following major subcomponents:. Please improve this by adding secondary or tertiary sources. The following figure illustrates the GT3 core architecture. About the Toolkit Documentation Downloads Support. This software and its surrounding architectures are in the process of evolution, and we will therefore concentrate our discussions in this chapter to the recent very stable release of the Globus GT3 toolkit.

Finally, our discussion ends with an implementation sample of a grid service to explain the concepts we have learned in the previous chapters of this book. Jerry JoyceMarianne Moon. It also allows you to activate and deactivate service instances. The core component of the Globus Toolkit version 3 contains the basic infrastructure needed for building grid services.

This list is incomplete ; you can help by expanding it. Windows Vista: The Missing Manual. Windows Vista For Dummies. Certified Ethical Hacker Exam Prep. Lotus Notes and Domino 6 Development 2nd Edition.

If you may any questions please contact us: flylib qtcs. Privacy policy. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are as essential for the working of basic functionalities of the website.

We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience. Necessary cookies are absolutely essential for the website to function properly.

This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information. Skip to content. By : admin September 9, This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. In such a managed environment, the container is responsible for managing and controlling these attributes. This helps to achieve a basic QoS requirement for the components.

In addition, the programming model becomes less complex to implement. In our previous discussions, we have explained these default implementation behaviors. It also provides a repository for service instance identity and management. Transport-independent, message-level security infrastructure supporting credential delegation, message signing, encryption, and authorization.

Among these, GT3 implementation provides the base implementation of GridService and Factory interfaces. This forms the basis of GT3 service implementation, container configuration, and the service invocation design pattern.

These implementations can be extended to provide more behaviors. We will see the implementation and configuration details of these interfaces later in the next chapter. However, these implementations are dependent on the service requirements. In complex scenarios, these implementations can be replaced with more sophisticated services pertaining to the service requirements.

For example, the simple point-to-point notification framework provided by GT3 may not always be sufficient, and should be replaced by asynchronous JMS-based message queues.

GT3 supports transport-level and message-level security. Another notable feature provided by GT3 is a declarative security mechanism for authentication and authorization using the service deployment descriptors.

This provides an extended plug-and-play security architecture using the JAAS framework. To communicate over this secure transport layer we need to use a different invocation scheme other than http; this is called httpg. We have to be aware that the current transport-level security may be depreciated in favor of the message-level security introduced through the WS-Security architecture.

Initially the client establishes a security context with the service, utilizing a system-level service known as the "Secure Conversation Service. On subsequent calls, it passes the shared secret key along with the message.

This provides additional flexibility, as any intermediary can validate the certificates and, hence, the message. We will discuss the details of the message, the transport-level security mechanisms, security programming, and the declarative security model for grid services in the next chapter.

The WS-Security then becomes the default message-level security mechanism. Figure In addition, the future security mechanisms must provide facilities for supporting WS-Federation, for federating across virtual organizations and trust domains. Some of the system-level services are introduced to provide a framework to achieve the required QoS in a production environment.

These services must provide logging, management, and administrate provisions for a grid environment. The functions can be used as standalone facilities, or they can be used in concurrence with each other. Some of the existing GT3 system-level services are:.

Logging service. This enables dynamic modifications of logging filters for the current runtime environment, or this can be persisted for subsequent executions. In addition, this service enables the grouping of log message producers to adjust the size of backlogs and to provide customizable message views.