Artix and J2EE

1,076 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,076
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Artix and J2EE

  1. 1. Artix and J2EE Artix: Advanced SOA Infrastructure Suite Artix is an advanced SOA infrastructure suite designed to meet the integration needs of large, heterogeneous enterprise environments. It is a cost-effective and open solution that provides interoperability between multiple generations of technologies, products, and standards without having to replace or disrupt existing infrastructure. With over a decade of experience, IONA’s technology and expertise have the proven robustness to support the needs of demanding, mission-critical applications. Java 2 Platform Enterprise Edition (J2EE) is Java-based software infrastructure. Today, J2EE forms the basis of many of the leading Web systems software platforms, including IBM WebSphere, BEA WebLogic, Sun ONE and the open-source JBoss. J2EE version 1.4 incorporates full support for Web services standards and introduces a J2EE version of the Java Connector Architecture (JCA) to simplify connections and messaging from external resources. J2EE JCA allows Artix to provide end-to-end security and transaction capability between J2EE and arbitrary transports, Artix or third party Web services applications. Artix Role for J2EE Users The typical enterprise application environment involves multiple, long-lived business-critical systems. Few if any of these systems were originally designed with service-oriented architecture in mind. While they have enormous value, they have incompatible architectures, technologies, transports, security, transaction and data models from current generation applications as well as other legacy applications. These incompatibilities pose enormous integration challenges to developers adopting service-oriented architectures. Artix provides a layer of abstraction that insulates J2EE users from these incompatibilities
  2. 2. Artix Tech Note— Artix and J2EE 2 and yet allows enterprise architects to independently design and implement the integration infrastructure. Artix Integration Architecture Artix provides multiple options for connecting and interoperating between J2EE applications and the many middleware environments supported by Artix. The J2EE platform supports many of the protocols and messaging formats such as JMS, IIOP and HTTP that are part of the core J2EE offering. Beyond supporting basic interoperability with these common middleware standards, J2EE includes JCA for connecting J2EE compliant applications to heterogeneous information systems. Artix supports multiple options for working with JCA compliant adapters to allow non-J2EE applications to integrate with J2EE applications. Figure 1 illustrates the first option for how the J2EE Connector from IONA can be used as a bridge between J2EE and many other middleware environments including other Web services. It also illustrates that the Artix J2EE Connector can be used as a bridge between J2EE and a CORBA server that has been exposed as a Web service by Artix. Artix provides a standard J2EE Connector Architecture resource adapter that manages the connections between your J2EE applications and external applications. Figure 1: Artix J2EE Connector Exposing a Web Service to a J2EE Application The Artix J2EE Connector simplifies the job of connecting J2EE applications to Web Services. This approach allows J2EE components including servlets, Java Server Pages or EJBs to make requests
  3. 3. Artix Tech Note— Artix and J2EE 3 against a distributed Web service so that J2EE programmers do not need to know anything about other technologies. The Artix J2EE Connector connection management API allows connectivity within the J2EE paradigm, seamlessly propagating security and transaction context between the J2EE domain and Artix endpoints. The benefit for the user is that the interface to the connector is compliant with the J2EE architecture and standards, and all of the required coding follows the J2EE paradigm; an elementary application will include literally only four lines of code that require an understanding of the workings of the Artix JCA. Artix automatically generates a WSDL-to-Java mapping based on the JAX-RPC standard. Artix uses the same WSDL service contract to obtain the Java interfaces required to request a service from a Web Service, invoking on a CORBA object or interacting with any other Artix service-enabled endpoint. From the standpoint of the Artix endpoints, they are talking to an Artix client. Artix not only supports extensive connectivity but also supports enterprise level services by propagating security models often required for mission–critical applications. Exposing a J2EE Application as a Web Service Most J2EE implementations provide extensive support for exposing J2EE components as Web services. However, using the Artix J2EE Connector enables you to expose your J2EE applications as Web services while retaining all the extensibility and quality of service (QoS) benefits offered by Artix. As shown in Figure 2, applications written in a wide range of application technologies can access the EJB as a Web service while continuing to use a variety of protocols and message formats. Artix manages the mediation among the middleware systems. Both the application and the Artix J2EE Connector are deployed to the J2EE application server, and the Artix J2EE Connector passes incoming Web services requests to the application. The Artix approach is non-invasive for existing applications that need to request services from an EJB, Servlet or JSP J2EE component. Furthermore, the location or underlying technology for implementing the service can change by simply changing the WSDL-based service contract so the change is transparent to the client applications.
  4. 4. Artix Tech Note— Artix and J2EE 4 Figure 2: Exposing J2EE components as Web services Deploying Artix Java Server Code into an Application Server Artix can be deployed stand-alone as a Java library that can be used from simple java applications, or as a servlet to a servlet container where the extensibility and multi-protocol capabilities of Artix can be accessed without the rest of J2EE. Java Application Feature List Beyond the JCA connector technology, Artix offers a rich environment for Java developers. The following tables summarize development and run-time features often used when deploying Artix using Java. Development Features Description WSDL-to-Java code generation Auto-generate Java client stub and server skeleton code directly from WSDL file WSDL-to-ACL security generation Generate XML based Access Control List configuration used in support of role based authorization WSDL-to-CORBA IDL generation Auto-generate CORBA IDL directly from WSDL file WSDL-to-SOAP Automatically generate Web service endpoint definitions (SOAP over HTTP) defined in the WSDL Java-to-WSDL support Create WSDL directly from Java class files for fast creation of Web service interfaces IDL-to-WSDL for CORBA Create WSDL directly from CORBA IDL for existing CORBA servers written in Java WSDL validation tools Tests the validity of WSDL documents prior to deployment to aid interoperability WSDL service tool Generate services from the command line for mass service creation and scripting
  5. 5. Artix Tech Note— Artix and J2EE 5 Runtime Features Description Deployment Models Java API Java APIs that follow the JAX-RPC specification for simplified service development Orbix API integration Tight integration with the enterprise quality Orbix CORBA solution BEA WebLogic integration Bi-directional invocation integration using J2EE/JCA multi transport enabling WebLogic IBM WebSphere integration Bi-directional invocation integration using J2EE/JCA multi transport enabling WebSphere JBoss integration Bi-directional invocation integration using J2EE/JCA multi transport enabling JBoss Stand alone server (Transformer) Zero-touch, code free Web service enablement of existing services Interoperability Features 1 .NET Artix integrates seamlessly with the Microsoft Platform Apache AXIS Artix interoperates with Apache AXIS hosted services and clients JBoss Artix interoperates with JBoss services and client IBM WebSphere Artix interoperates with IBM WebSphere services and clients BEA WebLogic Artix interoperates with BEA WebLogic services and clients Transports HTTP(s) Artix HTTP(s) transport plug-in Servlet Transport (Tomcat) Allows Artix services to be integrated with a Servlet engine IIOP(s) Artix IIOP(s) plug-in enables Web service integration with CORBA resources IIOP(s) Tunnel / IMSRaw / Artix IIOP(s) tunnel plug-in enables all data formats to travel over reliable, secure IIOP CICSRaw JMS Artix JMS plug-in enables Web services to leverage JMS as a reliable messaging transport MQ Artix MQ plug-in enables Web services to leverage MQ as a reliable messaging transport TIBCO Artix TibRV plug-in enables Web service to leverage TibRV as a reliable messaging transport Payload Format SOAP Support for many types of WSDL (e.g. Rpc-Literal, Doc-Literal & Rpc-SOAP encoded) CORBA CORBA message format plug-in SOAP with Attachments Complete attachment support for broader service development options XML XML message format plug-in Fixed Fixed format message format plug-in – for use with MQSeries FML Tuxedo wire level message format plug-in TibMsg TIBCO RV wire level message format plug-in Tagged (supports G2++) Tagged message format plug-in that also G2++ message format QoS Transactions OTS/WS-AT/C ready Out of the box support for transaction support via OTS OTS/WS-AT/C Artix provides out of the box distributed transaction manager for ACID transactions 1 TM Artix Advanced has been Microsoft .NET certified
  6. 6. Artix Tech Note— Artix and J2EE 6 QoS Security WS-Security SOAP Header support Enable applications to interoperate without changing directory services, security and authentication Single Sign On/ Mutual Single sign-on makes it possible to access secured distributed services authentication Role based access control & IONA security functionality enables direct use of enterprise security systems for control authentication File Adapter plug-in Plug-in to security service, enables file based authentication resources to be integrated with Artix Netegrity plug-in Netegrity plug-in to security service, enables Netegrity authentication LDAP plug-in LDAP plug-in to security service, enables LDAP authentication Microsoft Active Directory Plug-in to security service, enables Microsoft AD authentication Kerberos Security Service Artix supports the validation of Kerberos tokens with RACF or an off-host iS2 server TLS plug-in Enables TLS applications to use a PKI system for authenticating each side of a TLS connection Client principal support Provides the ability to propagate a userid from a client through to IMS and CICS Routing Routing Support for port (transport), port property, operation and application based routing of Web service messages
  7. 7. Artix Tech Note— Artix and J2EE 7 QoS Locator Locator Dynamic Web services registration can be configured to support load-balancing, failover and more State/session management plug-in that enables Web service clients to conversationally interact with Session Manager stateful servers QoS HA Active – Active high availability Provides HA for Locator, session manager and application code (2n+1 out the box) HA API API provided to applications can utilize the HA capabilities QoS Management SNMP plug-in Provides the ability to throw SNMP traps that can be configured at info, warning and error message levels Operational logging Logging of key operational data, which includes request per interval and minimum, maximum and average response times Tivoli Integration Tight integration to Tivoli enables administration of large Artix deployments BMC Patrol Integration Tight integration to BMC Patrol enables administration of large Artix deployments CA-WSDM Integration Tight integration to CA-WSDM enables administration of large Artix deployments

×