Catálogo de publicaciones - libros
Definitive Guide to SOA: BEA AquaLogic® Service Bus, The
Jeff Davies Ashish Krishna David Schorow
Resumen/Descripción – provisto por la editorial
No disponible.
Palabras clave – provistas por la editorial
Software Engineering/Programming and Operating Systems
Disponibilidad
Institución detectada | Año de publicación | Navegá | Descargá | Solicitá |
---|---|---|---|---|
No detectada | 2007 | SpringerLink |
Información
Tipo de recurso:
libros
ISBN impreso
978-1-59059-797-2
ISBN electrónico
978-1-4302-0263-9
Editor responsable
Springer Nature
País de edición
Reino Unido
Fecha de publicación
2007
Información sobre derechos de publicación
© Apress 2007
Cobertura temática
Tabla de contenidos
Versioning Services
C hange is inevitable. That’s a basic fact of life and SOA doesn’t change that. SOA promises to make your company and IT systems more tolerant of change, more agile. You need to do your part by understanding the different types of change that can occur, and then developing and enforcing governance policies to manage changes in your services. Managing change is not just a technology problem; it’s also a governance problem that requires the full participation of the people responsible for IT governance.
Palabras clave: Mental Model; Life Cycle Stage; Service Consumer; Object Orientation; Service Client.
Pp. 233-251
Administration, Operations, and Management
D esign and development is only part of the ALSB life cycle. Modern IT shops usually deploy their software into distinct environments. Commonly, these environments can be classified as Development, Testing, Stage, and Production. That list is by no means definitive, but it is representative. As software is developed, it is deployed into multiple environments. This process is complicated by the fact that the software deployed in each environment is often tied to local software assets that are part of the environment, not part of the software itself. No product is complete without providing capabilities to ease these operational challenges. In this chapter, we will discuss administration, operations, and management capabilities of ALSB.
Palabras clave: Proxy Service; Service Client; Service Invocation; Node Manager; Authorization Policy.
Pp. 253-279
Custom Transports
Y ou can extend the capabilities of ALSB in several ways beyond those it has straight out of the box. The simplest way is to use the Java Callout action to invoke a POJO, as described in Chapter 7. In this chapter, we’ll discuss how you can extend ALSB’s capabilities by adding additional transports beyond the ones that come out of the box with ALSB, such as HTTP or JMS.
Palabras clave: Business Service; Response Message; Proxy Service; Incoming Message; Admin Server.
Pp. 281-333
How Do I...?
A lthough this book covers the details of using ALSB, we’ve found over the years that there are a set of commonly asked questions by our customers about specific uses of ALSB. They range from the simple to the unusual. In this chapter, we’ll provide answers to the most commonly asked questions. Furthermore, we’ve picked out a few questions that might be uncommon, but that demonstrate just how flexible ALSB is in practice. The questions are broken down into different categories, to help you find the answers. Some questions cross these categorical boundaries. Where appropriate, we’ve given credit to the folks who answered the original questions.
Palabras clave: Resource Type; Proxy Service; Character Length; Params Variable; Assign Action.
Pp. 335-353