OSB Real Time Issues

OSB Real Time Issues

Application development and integration issues

– Lack of flexibility

– Not standards-based

– Project costs and long duration

Traditional methodologies

– Point-to-point

– Enterprise Application Integration

Service-Oriented Architecture is an IT strategy that organizes the discrete functions contained in enterprise applications into interoperable, standards-based services that can be combined and reused quickly to meet business needs

A service bus facilitates enterprise-wide reuse of services, and centralizes management of the services. It is valuable to the implementation of a Service-Oriented Architecture (SOA) as it

• Routes and transforms messages

• Executes transactions

• Orchestrates services

• Supports heterogeneous standards and message formats

The fundamental technologies on which a service bus is builtare:

• Web services

– Web Services Description Language

– Simple Object Access Protocol

– Universal Description, Discovery, and Integration

XML technologies

– XML schema

– XPath

– XQuery

– Extensible Stylesheet Language Transformations (XSLT)

Key Features of Oracle Service Bus Oracle Service Bus:

• Supports multiprotocol messaging

• Enables location transparency

• Handles dynamic routing

• Enables message transformation

• Enables service orchestration

• Supports message enrichment

• Provides service security

• Implements service-level agreements

Domain Topology: OSB Single Admin Server

Domain Topology: OSB Single Managed Server

Domain Topology: OSB Single Cluster

Domain Topology: OSB Coexistence

Domain Topology: OSB Multiple Clusters,Managed Servers---Not supported

Some of the resources that you can create:

• Proxy service

• Business service

• Split-Join

• WSDL

• XML schema

• WS-Policy

• JCA Binding

• XQuery transformation

• XSL transformation

• MFL file

• Alert destination

You can create resources by using the Project Explorer module in the OSB Console. The list of resources that you can create through the OSB Console are as follows:

• Proxy service: Proxy services are Oracle Service Bus definitions of services implemented locally on WebLogic Server.

• Business service: Business services are Oracle Service Bus definitions of the enterprise services with which you want to exchange messages.

• Split-Join: Split-Joins let you send message invocations in parallel (in addition tosequentially) and to aggregate the responses.

• WSDL: A WSDL (Web Service Definition Language) is the formal description of a proxyservice or a business service.

• XML schema: Schemas describe types for primitive or structured data.

• WS-Policy: Web Services Policy Framework (WS-Policy) is an extensible XML-based framework that extends the configuration of a web service with domain-specific security assertions and specifies the security requirements, expectations, and capabilities of the web service.

• JCA binding: JCA binding enables you to communicate with JCA-compliant Enterprise Information Systems (EIS) components and consume JCA resources.

• XQuery transformation: XQuery transformation maps can describe XML-to-XML, XML to non-XML, and non-XML to XML mappings.

• XSL transformation: Transformation maps describe the mapping between two datatypes. yp eXtensible Stylesheet Language Transformation (XSLT) maps describe XML-to-XML mappings.

• MFL file: A Message Format Language (MFL) document is a specialized XML document used to describe the layout of binary data. It is an Oracle proprietary language used to define rules to transform formatted binary data into XML data.

• Service account: A service account provides a username and password that proxy services and business services use for outbound authentication or authentication to a local or remote resource, such as an FTP server or a JMS server.

• Service key provider: A service key provider contains Public Key Infrastructure (PKI)credentials that proxy services use for decrypting inbound SOAP messages and for outbound authentication and digital signatures.

• JAR: A JAR (Java ARchive) is a zipped file that contains a set of Java classes. It is used to store compiled Java classes and associated metadata that can constitute a program.

• Alert destination: An alert destination resource captures a list of recipients that can receive alert notifications from the Oracle Service Bus. In typical system monitoring contexts, alerts generated by Oracle Service Bus bear significance to a finite set of users.

• Resources from URL: All Oracle Service Bus resources (for example, services, WSPolicies,WSDLs, XQuery transformations, and so on) reside in exactly one project.Projects do not overlap. Resources can be created directly under a project, or they can be further organized into folders. However, you can reference any resource regardless of the project in which it resides. You can perform a bulk import of resources available at a URL or on the file system. Bulk import lets you import a root resource, such as a WSDL, along with its dependents, such as other WSDLs and schemas.

• Zipped resources: You can select a zip or JAR file that contains the resources that you want to load. Oracle Service Bus locates and imports the resources from this zip file.

Enabling or Disabling a Service:

The ability to enable or disable a service is on the Operational Settings tabbed page for the selected service You can perform the following operational settings for proxy services and service. business services:

• State: Use this to enable or disable a service.

• Aggregation Interval: Use this to set the aggregation interval for the service.

• Monitoring: Use this to enable service monitoring at a specific level or above. You can also use this to disable service monitoring for proxy services.

• SLA Alerting: Use this to enable SLA alerting for services at a specific level of severity or above. You can also use this to disable SLA alerting for a service.

• Pipeline Alerts: Use this to enable pipeline alerting for proxy services at a specific severity level or above. You can also use this to disable pipeline alerting for proxyservices.

• Message Reports: Use this to enable or disable message reporting for proxy services.

• Tracing: Use this to enable or disable message tracing for proxy services at a specific detail level.

• Logging: Use this to enable logging at a specific severity level. You can also use this to disable logging for proxy services.

• Throttling: Use this to enable or disable throttling for a business service.

• Result Caching State: Enables you to activate result caching for the business service.You must also ensure that result caching is enabled globally.

Smart Search

View References

Performing Simple Actions on Resources The OSB Console enables you to perform simple actions on resources such as:

• Renaming

• Deleting

• Cloning

• Moving

Administrative Tasks in Oracle Service Bus You can manage OSB at run time by performing the following tasks:

• Modify service and policy configurations.

• Monitor system and operations tasks.

• Test proxy and business services.

• Modify the security configuration.

• Import and export resources.

• Bulk-change environment variables.

• Administer UDDI registries

Session Management

Importing to jar file

Exporting to Jar file

Applying Customization file

There are four predefined administration roles:

– By default default, each role is associated with a single user group.

– You can modify group membership or specify new roleconditions.

Role                                     Default Group

IntegrationMonitor          IntegrationMonitors

IntegrationDeployer      IntegrationDeployers

IntegrationOperator        IntegrationOperators

IntegrationAdmin        IntegrationAdministrators

Reporting and Monitoring

Service Bus Monitoring Operational data includes:

• Overall health of each server in a cluster

• Number of messages that were processed

• Ratio of successful to failed messages

• Average execution time for a service

• Service-level agreement (SLA) violations

• Security violations

• Custom message reports

• Log entries

OSB Monitoring Framework:

The OSB monitoring architecture consists of the following components:

• Collector: Each managed server in a cluster hosts a collector. The collector collects statistics on operational resources at regular intervals of time. It also keeps samples history within the aggregation interval for the collected statistics. OSB run time invokes a collector at the beginning of each minute. At every system-defined checkpoint interval, it stores a snapshot of current statistics into a persistent store for recovery purposes and sends the information to the aggregator in raw format, because raw format is optimized for fast collection and small footprint.

• Aggregator: The aggregator is present only on one managed server. The server on which this resides is selected arbitrarily when you generate a domain by using the Configuration Wizard. It aggregates all the statistics that are collected from all managed servers across all managed servers in a cluster. The OSB run time invokes the aggregator 25 seconds past each minute to enable collectors to collect data and send it to the aggregator. At system-defined checkpoint intervals, each managed server in the cluster sends a snapshot of its contributions to the aggregator. Data structures in the aggregator are optimized for aggregating and retrieving data.

• Alert Manager: The Alert Manager fires alerts based on the aggregated statistics

OSB can send alerts to any combination of the following:

• Email server

• JMS destination

• SNMP trap destination

• OSB reporting service

Alerts can also be written to the server log

OSB Debug Files:

You can enable and disable debugging by modifying the corresponding entries in the following debug XML files which are located in the root directory of your OSB domain:

• alsbdebug.xml: Contains ALSB-related debug flags

• configfwkdebug.xml: Contains configuration-related debug flags

If the XML files are not in the root directory or if they have been deleted, they are created again without any contents when the server starts

Some OSB resources are not targeted to the entire cluster:

• The Message Reporting Purger application asynchronously processes purge requests from the OSB Console.

• The Data Aggregator application receives and stores operational data sent from all managed servers.

• File, FTP, and Email pollers for proxy services