Showing posts with label J2EE CA. Show all posts
Showing posts with label J2EE CA. Show all posts

Saturday, August 17, 2013

Book review- Oracle SOA Suite 11g Performance Tuning Cookbook



This book covers almost all aspects of the performance tuning starting from the weblogic server to different SOA components. The highlight being detailed steps on different options available to analyze and troubleshoot the issues.
The modularization of the book is really good. The book starts with the soa infrastructure, listing the different options of monitoring the JVM’s, SOA suite and different components like bpel, rules, mediator which are actually really good. BPEL and BPMN tuning tips are already available as part of the performance guides/blogs ,but the authors have captured that as well in this book, which is good in one way so as it helps to bring all the performance tuning options together. Monitoring SOA suite, JVM Garbage collections, Platform tuning are very well covered in the book.  It was good to learn we could leverage multiple available options mentioned in the book  to monitor/troubleshoot different JVM/server issues.

          The book also covers the tuning aspects from process perspective as well as at environment level with equal importance. I recommend this book as a must read for SOA server Administrators as well as SOA Consultants, this book will help you to get most out of the SOA infrastructure. The book will make an interesting read for those people who love to take it the next level.

Link to the book @ http://bit.ly/12lrajU

Thursday, September 4, 2008

high-level architecture of J2EE CA

In this blog I will give a brief overview of the high-level architecture of J2EE CA.

At the heart of J2EE CA are several standardized contracts and interfaces between different parties. The parties are the backend enterprise information system (EIS), the different application components, the application server, and the resource adapter. Will explain each one of them:

· EIS: This is the backend legacy system that the application components must integrate with.

· Application components: These are Java or J2EE application components or middleware or Webservices that must integrate with the EIS.

· Application server: The application server (for instance, Oracle Application Server 10g) provides the runtime environment (container) in which the application components and the resource adapter execute. It also furnishes system-level services such as connection, transaction, and security management.

· Resource adapter: This connects application components with the EIS by implementing system-level services specific to the EIS, thereby shielding the application components from the EIS-specific system-level services. It plugs into the application server by using standardized system contracts.