Sybase service-oriented architecture products use services to encapsulate business logic and data into reusable networked software components. A service can be as simple as a credit check process involving a single request-reply operation. A service can also be a complicated business process comprised of multiple services accessing a variety of systems using multiple service types. In Sybase SOA products, services are stored in Web Services Description Language (WSDL) files. All endpoints are modeled as services by using WSDL documents.
Services are developed, deployed, versioned, and managed as discrete units. They must be well defined, self-contained, and independent of the context or state of other services. These services can be published either to the Web or internally so that the business logic and data can be shared. The services can be reused without changes. For internally published services, a new service can be derived by using parts of the published service and adding new logic or data.
When you are searching for a service to re-use or from which to derive another service, you must be sure that you know the business logic of the service, any data associated with the service, and any dependencies, for example, on other services.
Sybase WorkSpace provides tools for creating, discovering, editing, sharing, deploying, and publishing services. Use the Service Development tooling to create the following types of services.
Enables the orchestration of events, activities, and other services to execute vital business processes. The data flowing through a business process can be enriched and transformed, and business rules can be applied to control the sequencing and distribution of business data. Like all services, a business process service can be consumed within clients or incorporated into other composite services, such as a Java service, resulting in a powerful network of resuable services.
Additionally, once a business process service is created, you can incorporate alert messaging, business activity monitoring, database event management, or the use of custom wire formats.
See Business Process Service for more information.
Exposes operations that can be performed on a specified database through the use of stored procedures or SQL statements. A database service can be deployed independently or incorporated into a composite service.
See Database Service for more information.
Enables integration of a Web service with Enterprise Java Bean endpoints by deriving a service interface directly from an EJB implementation. An EJB service can be deployed independently or incorporated into a composite service.
See EJB Service for more information.
Enables invocation of Java code within a business process by binding the Java service to a local Java class and the service operations to public methods within the Java class. Since a Java service can call other services through the Java service proxy interface, you can build composite services using a Java service to integrate process flow from many services into one service interface. A Java service can be deployed independently or incorporated into a composite service.
See Java Service for more information.
Enables applications to send and receive messages through interaction with external messaging systems, such as Java Message Service, JMS providers, file systems via FTP, flat files, and email servers via SMTP and POP3. A message service can be deployed independently or incorporated into a composite service.
See Message Service for more information.
Enables access to an external service that is described by a WSDL document. The SOAP service uses the WSDL document to construct a service definition that wraps the external service in an interface. After the service is deployed, it acts as a relay, receiving calls, forwarding the calls to the external Web service to which it is bound, awaiting a response from the external service, and then returning the response to the business process or composite Java service. A SOAP service can be deployed independently or incorporated into a composite service to call the external Web service.
See SOAP Service for more information.
Enables the implementation of data transformation between content models in a business process service. A transformation service can be deployed independently or incorporated into a composite service.
See Transformation service for more information.
The SOA allows you to develop and design without being tied to a platform or a language. Sybase WorkSpace enables service-oriented development of applications (SODA) with the very workable combination of consistent graphical development and the flexibility of code for complicated scenarios. You may need to reuse or reverse engineer existing applications as well as build new, standards-based, flexible solutions for your problems. SODA encapsulates and abstracts technologies such as databases, J2EE, .NET, and CORBA so that you do not have to interact with heterogeneous applications and systems infrastructures. SODA enables easier re-use by replacing coding and rework, especially as it encapsulates existing application functionality into new services.
Service orientation gives businesses a more effective way to achieve greater insight into their business activities. It also enables businesses to reuse existing investments in applications and application infrastructure to address newer business needs and support new channels of interaction with customers, partners, and suppliers. Service orientation in IT application development can replace disconnected application models as a way to build distributed systems. Service providers display their capabilities to handle certain requests through interfaces. SOA maps these interfaces so they can be organized into processes. For businesses, service orientation is essential for creating connected systems. A connected system pulls in a variety of services and devices to more effectively meet current business challenges.
Sybase WorkSpace allows you to select the right combination of service development and other component tooling depending on the characteristics of the targeted application:
J2EE-based service creation
Process-driven, event-driven, or data-driven development
Standard service discovery, description, and management
Combination of legacy and services-based functionality
Services-based process monitoring
Services-based integration
Modeling
Send your feedback on this help topic to Sybase Tech Pubs: pubs@sybase.com