The re-architecture approach reduces the mainframe costs and legacy risks by migrating the application off the mainframe and re-structuring it using all the modern software tools and capabilities at our disposal. However, this very process of re-structuring the application, and essentially re-building it using knowledge and business rules mined from existing code, introduces certain risks. How can we ensure that the new application maintains functional equivalence, and operational characteristics of the original? Can we meet the performance and scalability requirements not only of the current environment, but future growth needs as well? Can we deliver the new application within the time and budget constraints agreed to at the beginning of the project? The older the application, the larger its scope and volume of code, and the fewer original developers available, the higher these risks may be.
This article by Jason Williamson, Tom Laszewski and Mark Rakhmilevich, takes a look at an alternative approach that attempts to balance these risks in a different way. Re-host-based modernization approach is focused on migrating the application off the mainframe to a compatible software stack on an open-systems platform, preserving the language and middleware services on which the application has been built. It protects legacy investment by relying on a mainframe-compatible software stack to minimize any changes in the core application, and preserve the application's business logic intact, while running it on an open-system platform using more flexible and less expensive system infrastructure. It keeps open the customer's options for SOA enablement and re-architecture, by using an SOA-ready middleware stack to support Web services and ESB interfaces for re-hosted components. And using an extensible platform with transparent integration to J2EE components, BPM-based processes, and other key tools of the re-architecture approach means you can start to re-architect selected components at will, without requiring changes to the re-hosted services running the remainder of the business logic.Read Introduction to Re-Host based Modernization Using Tuxedo in full
To gain a greater understanding of concept of SOA applications, BPEL processes and JBI applications, and to enable us to develop enterprise level SOA applications, we need to understand JBI in further depth, and how JBI components can be linked together. This article by Frank Jennings and David Salter will show the JBI Service Engine is supported within the NetBeans Enterprise Pack.Read Need for Java Business Integration and Service Engines in NetBeans in full
A business process is a set of coordinated activities that are performed either by humans or by tools with an objective to realize a certain business result. The order of these activities and the efficiency of those who perform the activities determine the overall performance of a business process. It is very much in the interest of every company to have business processes that are efficient and include only necessary activities, because this will allow them to work faster and more efficiently. In this article by Matjaz B. Juric and Kapil Pant, we will look at business process modeling, the main objective of which is to develop a process model that defines the existing process flow in detail.Read Business Process Modeling in full
The first step in protecting web services is to authenticate and authorize the web service requests. Authentication in web services is the process of verifying that the user has valid credentials to access the web services and authorization is the process of validating that the authenticated user has appropriate privileges to access the web services. Besides restricting access to users with valid credentials and proper privileges, Oracle WSM can track who accessed which service and when—to provide detailed audit trails. In this article, Sitaraman Lakshminarayanan explores how Oracle Web Services Manager can be leveraged to authenticate and authorize the web services requests.Read Oracle Web Services Manager: Authentication and Authorization in full
The web services model brings into the system unique security challenges because the business data in the form of XML documents may be required to travel across untrusted networks and has the chance of being manipulated by external systems.
Throughout the entire business transaction, different classes of users and systems need access to the entire business transaction. If any part of this chain is compromised, the whole business application deployed as a service will fail. Web services are inherently about how to share the process of computing across a distributed network of systems. Web services' communication channel being XML, messages are text-based, readable, and self describing.Read Securing XML Documents in full
Enterprise Service Bus (ESB) is a standard-based middleware architecture that allows pluggable components to communicate with each other via a messaging system. In this article by David Salter, we will see in brief, the components inside the ESB architecture and how they communicate with each other. We will also look at how NetBeans SOA pack integrates with OpenESB and the various functionalities it offers with regards to the ESB.Read 10 Minute Guide to the Enterprise Service Bus and the NetBeans SOA Pack in full
This is a two article series by Sitaraman Lakshminarayanan.The article revolves around how to digitally sign and verify messages in web services using Oracle Web Services Manager.The first part will explain concepts like digital signatures,their importance,their functional use with respect to web services, but will mainly focus on how Oracle Web Services Manager can help generate and verify signatures in web services.In the next part,he will explain signature generation and signature verification along with an example.Read Digitally Signing and Verifying Messages in Web Services ( part 1 ) in full
This is the second part of the 2 series article by Sitaraman Lakshminarayanan on Digitally Signing and Verifying Messages in Web Services using Oracle.The article revolves around how to digitally sign and verify messages in web services using Oracle Web Services Manager.The first part explained concepts like digital signatures,their importance,their functional use with respect to web services, but mainly focussed on how Oracle Web Services Manager can help generate and verify signatures in web services.In the this part,he explain signature generation and signature verification along with an example. For all those who missed out the initial action just click onto : http://www.packtpub.com/article/digitally-signing-and-verifying-messages-web-services-part1Read Digitally Signing and Verifying Messages in Web Services ( part 2 ) in full
So far, the general approach towards SOA has been that it is just a tidying-up of application integration. SOA, according to this approach, is not about building new a business functionality but about organizing existing systems. In this article by Michael Havey, we will see that, in reality, SOA is more than merely getting organized. Its principal mandate is to build something new; indeed, SOA is fundamentally about building new processes. We will consider an approach to SOA architecture that is, yes, methodical, but has the burden of actually designing new and challenging orchestration and ESB processes.
In this article, we will build examples of choreography and orchestration, study best practices for message handling in orchestration processes, and develop fundamental orchestration concepts, such as interaction, invisible hub, and deferred choice.Read Modeling Orchestration and Choreography in Service Oriented Architecture in full
Integration is a necessary evil using which we can interconnect systems, applications and services to facilitate seamless information flow within and across Organization boundaries. We have been using technologies like JSP, EJB, JMS, etc. in the Java world for building Enterprise Applications (EA). But if we have to interconnect such applications, we will need Enterprise Application Integration (EAI). Many a times we also use EA technologies and tools to do EAI. This will give a short term solution to our integration problems, which may not scale up when we want to perform integration at Enterprise (Customers, Vendors, Partners, ...) level. Java Business Integration (JBI) is the new specification trying to fill this gap of EAI in the Java world. So next time when you want to integrate, don't write a single line of Java code, instead plug and assemble JBI based integration libraries to control your message flow! Does it looks promising? Believe it or read the article below to get yourself convinced.
In this article by Binildas Christudas, we will look into Integration in general and to JBI and ESB in particular. We will then explain few functionalities usually done by integration components like protocol conversions, content transformations, etc., with some code snippets too.Read Aggregate Services in ServiceMix JBI ESB in full