PrintIt goes without saying that software standards are important to ensure interoperability with existing IT assets. But with an emerging business process management (BPM) market, there are other important reasons why companies should pay attention to how well vendors adhere to standards. BPM standards are not yet fully mature, so it is important to select a vendor that is committed to comply with standards as soon as they become available. A BPM vendor that aggressively drives and adopts standards gives Global 2000 companies the confidence to invest now — knowing that their process assets are portable. This gives CIOs the flexibility to deploy today with TeamWorks even though they may have significant enterprise investments in IBM, BEA, SAP and Oracle infrastructure. As the immature BPM offerings from these platform providers mature, our customers are assured of interoperability and portability.
TeamWorks supports the following key industry standards:
|
BPMN BPEL BPDM Eclipse J2EE |
JSR-168 .NET Web Services WSRP |
The Business Process Modeling Notation (BPMN) specification provides a graphical notation for expressing business processes in a Business Process Diagram (BPD). The objective of BPMN is to support business process management by both technical users and business users by providing a notation that is intuitive to business users yet able to represent complex process semantics. TeamWorks was one of the first BPM platforms to support BPMN. With a position on the BMPI Steering Committee, Lombardi continues to help drive adoption and innovation for BPMN in the future. In 2005, BPMI merged with the Object Management Group (OMG) to combine activities focused on all aspects of business process management. For more on BPMN, please visit http://www.omg.org/technology/rfc-form.htm.
Web Services Business Process Execution Language (WS-BPEL) provides a language for the formal specification of business processes and business interaction protocols. By doing so, it extends the Web Services interaction model and enables it to support business transactions. WS-BPEL defines an interoperable integration model that should facilitate the expansion of automated process integration in both the intra-corporate and the business-to-business spaces. TeamWorks supports earlier versions of WS-BPEL (BPEL4WS V1.1) as well as the latest version (WS-BPEL TC). For more on WS-BPEL, please visit www.oasis-open.org.
the Business Process Definition Metamodel (BPDM) standard will define a business process definition metamodel, which is platform independent with respect to specific business process definitions. This metamodel will define an abstract representation for the specification of executable business processes that execute within an enterprise (with or without human involvement); and may collaborate between otherwise-independent business processes executing in different business units or enterprises. For more on BPDM, please visit www.bpmi.org.
Eclipse is an open platform for tool integration that gives developers freedom of choice over their software technology in a multi-language, multi-platform, multi-vendor environment. Lombardi joined the Eclipse Foundation as a charter member in 2004. The Eclipse Foundation includes IBM, Oracle, HP, Intel, SAP and CA among its many members. TeamWorks integrates Eclipse with its exclusive Shared Model architecture, giving organizations the ability to model, simulate, execute, monitor and change business processes in a configurable, extensible environment. For more on Eclipse, please visit www.eclipse.org.
Lombardi leverages the Java™ Platform, Enterprise Edition (J2EE) technology and its components to provide our customers with a secure, robust, and interoperable BPM platform. Such standards include XML, EJB, JSP, XML, JAAS, JTA, JMS, JCA, JDBC, JNDI, Servlets, and JavaScript. These standards are extensively used and supported throughout the presentation, business logic, engine, integration, and repository layers of TeamWorks to provide and open architecture and platform. Lombardi is committed to ensuring that TeamWorks continues to be fully interoperable with the industry's open standards. For more on J2EE, please visit the J2EE Web site.
Managed by the Java Community Process(JCP), Java Specification Request (JSR) 168 is a specification for enabling interoperability between Portals and Portlets. This specification defines a set of APIs for Portal computing addressing the areas of aggregation, personalization, presentation and security. TeamWorks Portal is JSR-168 compliant. For more on JSR-168, please visit the JCP Web site.
Lombardi is a Microsoft Gold Certified Partner with competencies in Information Worker Solutions and ISV/Software Solutions. Additionally, TeamWorks has achieved Microsoft's Premium .NET Connected Certification. The .NET Connected Logo indicates Lombardi Software's TeamWorks is exposed through, or is programmatically enhanced by the consumption of, Web services that comply with industry Web service standards. These standards currently include XML Schema 1.0, SOAP 1.1 and WSDL 1.1 with optional use of UDDI. For more on the Microsoft Gold Certified Partner program, please visit the program Web site. For more on the .NET Connected program, please visit the .NET connected Web site.
Lombardi provides extensive support for Web Services and Service Oriented Architectures (SOA). The TeamWorks connector framework is based on industry standards (SOAP, WSDL) and Web Services built using TeamWorks are accessible by any Web Services enabled programs including ones that are built using Microsoft .NET, BEA Workshop, IBM, SunONE, and Oracle. We support defining Web Services based on existing TeamWorks Processes as well as calling any existing Web Service via the provided TeamWorks SOAP Connector. For more on Web Services, please visit the World Wide Web Consortium (W3C) Web site.
Managed by OASIS, Web Services for Remote Portals (WSRP) defines a set of interfaces and related semantics which standardize interactions with components providing user-facing markup, including the processing of user interactions with that markup. This allows applications to consume such components as providing a portion of the overall user application without having to write unique code for interacting with each component. TeamWorks is WSRP compliant. For more on WSRP, please visit the OASIS Web site.