XML Name Space..
http://www.rpbourret.com/xml/NamespacesFAQ.htm
Wednesday, June 4, 2008
Monday, June 2, 2008
Thursday, May 8, 2008
AquaLogic Service Bus Features
AquaLogic Service Bus is a true ESB product specifically targeted for service-oriented
integration, managing Web Services, and providing traditional message brokering across
heterogeneous IT environments. AquaLogic Service Bus’s lightweight, stateless,
high-performance architecture delivers an intermediary for use as a core element of distributed
services networks.
AquaLogic Service Bus is policy-driven. It enables you to establish loose coupling between
service clients and business services while maintaining a centralized point of security control and
monitoring
AquaLogic Service Bus is an intermediary that takes in messages, processes them to determine
where to route them, and transforms them as specified. It receives messages through a transport
protocol such as JMS and sends out messages again through the same or another specified
transport protocol. Message response follows the inverse path. The message processing by
AquaLogic Service Bus is driven by metadata specified as the message flow definition for a proxy
service in the AquaLogic Service Bus Console.
Routing Supports the following:
• Routes messages according to XQuery-based policies or callouts to
external Web services.
• Routing policies apply to both point-to-point and one-to-many routing
scenarios (publish). For publish, routing policies serve as subscription
filters.
Routing Transport
Protocols Supports the following:
• File
• FTP
• HTTP(S)
• JMS (including MQ using JMS, and JMS/XA)
• E-mail (POP/SMTP/IMAP)
Messaging Supports the following models:
• Synchronous
• Asynchronous
• Publish
• Subscribe
Message Types Supports the following message formats:
• E-mail with attachments
• JMS with headers
• MFL (Message Format Language)
• Raw Data. Raw data is opaque data—that is, non-XML data for which
there is no MFL file and therefore no known schema
• Text
• SOAP
• SOAP with attachments
• XML (XML that is or is not valid against a schema)
Transformations Supports the following functionality for the transformation or processing
of messages:
• Validates incoming messages against schemas
• Selects a target service or services, based on the message content or
message headers
• Transforms messages based on the target service
• Transforms messages based on XQuery or XSLT
• Supports transformations on both XML and MFL messages
• Message enrichment
• Supports call outs to Web services to gather additional data for
transformation (for example, country code, full customer records, and
so on.)
Logging and Monitoring Provides a rich set of functionality to audit and monitor services:
• You can gather statistics about message invocations, errors,
performance characteristics, messages passed, SLA violations, and so
on.
• The system also supports logging messages for both systems
operations and business auditing purposes, search capabilities, and so
on.
• Incoming messages may be logged to a reporting store. You can
extract key information from a message and use as it as a search index.
• The AquaLogic Service Bus Console provides a cluster-wide view of
service status and statistics.
• Both business services and AquaLogic Service Bus proxy services are
monitored, as are response times, message counts, and error counts.
• Statistics are gathered locally, then aggregated centrally.
• SLA rules run against aggregated data. The system raises alerts, and
you can enable or disable services.
Versioning
Provides the ability to deploy new versions of services and allow you to
have multiple versions of message resources such as WSDLs and schemas.
Versions can include changes to the WSDL, the message schema, the
headers, and the security parameters.
Service Level Agreements Administrators can set service level agreements (SLAs) on the following
attributes of proxy services:
• Average processing time of a service
• Processing volume
• Number of errors, security violations, and schema validation errors
• Administrators can configure alerts for SLA rule violations
Security Includes the following:
• Supports authentication, encryption and decryption, and digital
signatures as defined in the Web Services Security (WS-Security)
specification.
• Uses SSL to support traditional transport-level security for HTTP and
JMS transport protocols.
• Supports one-way and two-way certificate based authentication.
• Supports HTTP basic authentication.
Service Registry Supports the following:
• Stores information about services, schemas, transformations, WSDLs
(Web Service Definition Language), and WS Policies.
• Provides centralized management and distributed access
• Allows you to browse the service registry and import resources into
the registry from WebLogic Workshop or other applications.
• Allows the propagation of configuration data from environment to
environment (for example, from a development domain to a test
domain to a production domain). The system allows environment
specific settings to be overridden during import.
Error Handling Supports the following:
• Allows you to configure your system to format and send error
messages, and return messages for consumers of services who expect
a synchronous response.
• Allows you to configure error handling for stages in the pipeline, for
pipelines, and for proxy services
AquaLogic Service Bus is a true ESB product specifically targeted for service-oriented
integration, managing Web Services, and providing traditional message brokering across
heterogeneous IT environments. AquaLogic Service Bus’s lightweight, stateless,
high-performance architecture delivers an intermediary for use as a core element of distributed
services networks.
AquaLogic Service Bus is policy-driven. It enables you to establish loose coupling between
service clients and business services while maintaining a centralized point of security control and
monitoring
AquaLogic Service Bus is an intermediary that takes in messages, processes them to determine
where to route them, and transforms them as specified. It receives messages through a transport
protocol such as JMS and sends out messages again through the same or another specified
transport protocol. Message response follows the inverse path. The message processing by
AquaLogic Service Bus is driven by metadata specified as the message flow definition for a proxy
service in the AquaLogic Service Bus Console.
Routing Supports the following:
• Routes messages according to XQuery-based policies or callouts to
external Web services.
• Routing policies apply to both point-to-point and one-to-many routing
scenarios (publish). For publish, routing policies serve as subscription
filters.
Routing Transport
Protocols Supports the following:
• File
• FTP
• HTTP(S)
• JMS (including MQ using JMS, and JMS/XA)
• E-mail (POP/SMTP/IMAP)
Messaging Supports the following models:
• Synchronous
• Asynchronous
• Publish
• Subscribe
Message Types Supports the following message formats:
• E-mail with attachments
• JMS with headers
• MFL (Message Format Language)
• Raw Data. Raw data is opaque data—that is, non-XML data for which
there is no MFL file and therefore no known schema
• Text
• SOAP
• SOAP with attachments
• XML (XML that is or is not valid against a schema)
Transformations Supports the following functionality for the transformation or processing
of messages:
• Validates incoming messages against schemas
• Selects a target service or services, based on the message content or
message headers
• Transforms messages based on the target service
• Transforms messages based on XQuery or XSLT
• Supports transformations on both XML and MFL messages
• Message enrichment
• Supports call outs to Web services to gather additional data for
transformation (for example, country code, full customer records, and
so on.)
Logging and Monitoring Provides a rich set of functionality to audit and monitor services:
• You can gather statistics about message invocations, errors,
performance characteristics, messages passed, SLA violations, and so
on.
• The system also supports logging messages for both systems
operations and business auditing purposes, search capabilities, and so
on.
• Incoming messages may be logged to a reporting store. You can
extract key information from a message and use as it as a search index.
• The AquaLogic Service Bus Console provides a cluster-wide view of
service status and statistics.
• Both business services and AquaLogic Service Bus proxy services are
monitored, as are response times, message counts, and error counts.
• Statistics are gathered locally, then aggregated centrally.
• SLA rules run against aggregated data. The system raises alerts, and
you can enable or disable services.
Versioning
Provides the ability to deploy new versions of services and allow you to
have multiple versions of message resources such as WSDLs and schemas.
Versions can include changes to the WSDL, the message schema, the
headers, and the security parameters.
Service Level Agreements Administrators can set service level agreements (SLAs) on the following
attributes of proxy services:
• Average processing time of a service
• Processing volume
• Number of errors, security violations, and schema validation errors
• Administrators can configure alerts for SLA rule violations
Security Includes the following:
• Supports authentication, encryption and decryption, and digital
signatures as defined in the Web Services Security (WS-Security)
specification.
• Uses SSL to support traditional transport-level security for HTTP and
JMS transport protocols.
• Supports one-way and two-way certificate based authentication.
• Supports HTTP basic authentication.
Service Registry Supports the following:
• Stores information about services, schemas, transformations, WSDLs
(Web Service Definition Language), and WS Policies.
• Provides centralized management and distributed access
• Allows you to browse the service registry and import resources into
the registry from WebLogic Workshop or other applications.
• Allows the propagation of configuration data from environment to
environment (for example, from a development domain to a test
domain to a production domain). The system allows environment
specific settings to be overridden during import.
Error Handling Supports the following:
• Allows you to configure your system to format and send error
messages, and return messages for consumers of services who expect
a synchronous response.
• Allows you to configure error handling for stages in the pipeline, for
pipelines, and for proxy services
Subscribe to:
Posts (Atom)