This document provides information about the HTTP Binding Component of Java CAPS. “Hi Guys, I’m struggling to understand the way JCAPS handles deployment. I have managed to build an EAR file using the eDesigner but it will not let me deploy. “Hi Folks, I am working on Seebeyond since , and currently working with ICAN havent been to any training in JCAPS. 1. Is there any doc which.

Author: Gojinn Kagalar
Country: Cape Verde
Language: English (Spanish)
Genre: Science
Published (Last): 9 September 2018
Pages: 155
PDF File Size: 4.59 Mb
ePub File Size: 3.71 Mb
ISBN: 510-7-46573-304-2
Downloads: 37726
Price: Free* [*Free Regsitration Required]
Uploader: Malanris

Software migration is as exciting as getting a new vehicle for ride, without changing the Passenger or Destination.

Likewise, migration provides the thrill of exploring new tools and functionalities, without changing the Business logic or Data. Let us also keep in mind Software has no resale value like your car.

SeeBeyond is the legacy version of the Middleware.

It provides us Monk and Java as Development medium. The architecture adopts Message oriented Middleware pattern. The components interact with each other or with the external components through Messaging Queues or Topics. It relies on Repository based development. The Development artifacts are stored internally in a Version Repository. The business logic is embedded in an EJB. The Adapters translate the Business data to a common Java Object.


Please refer to Additional resources for more details on SCA.


It exposes all your Business functions as Web Services. The major difference to the earlier approach is that the Common Interfacing mechanism is a Web Service instead of Java Objects.

The Business architechure is built as Service components a Web Service. The components can be connected together, in a typical plug and play fashion, via Composite architecture.

Please refer to the SCA architecture Document for further explanation. Now, we have an understanding of various Development patterns of the Products.

Migration JCAPS to OpenESB

Let us focus on the approaches we could take. This is easier migration path. The Development and testing efforts are less since the JEE components can be reused.

You just deployed the components from Glassfish server to Weblogic. This approach makes your code truly Web Service enabled and Business Process friendly Processes can be changed on the fly with configuration changes. No Java coding or Debug logs. Shall we try simplistic thinking, employed by George Boole to zip our entire Business logic into Ones and Zeroes. Let’s retrospect ourselves with few questions Do I need to do this migration? What are the target goals for this exercise?


How do I benefit from this migration?


If I opt for a complete rewrite, what are my Development Tools. Are you the next one?

A nice tutorial covering the basics of Service Component Architecture. The path to choose Peruse The archives.

Now, let’s get down to Business, on various approaches we could take on this Migration task. JCAPS has gone through constant revamp to catch up with the latest technologies. Seebeyond SeeBeyond is the legacy version of the Middleware. Just rewrite the code to Oracle Arcnitecture.

Additional development effort to rewrite the Java Components. Epilogue Migration is a challenging Process.