Recomendation: Which JDK best suites SUN Java or JRockit

I have always come across this dialama, which JDK between SUN Java (Hotspot) and JRockit  to use when we are installing Oracle Integration Products, i.e, SOA BPEL, BPM, BAM etc.

Here are some of my findings and recomendations:

First we will need to understand What is the difference between the Sun JVM and JRockit JVM?
 
The most well know JVM is the implementation from Sun. The Sun JVM is called HotSpot. The Sun JVM is shipped in the Java Developer's Kit (JDK) and Java Runtime Environment (JRE) from Sun.

The JRockit JVM from is optimized for reliability and performance for server side applications. To achieve this, JRockit JVM uses technologies such as code generation, hot spot detection, code optimization, advanced garbage.

To know more about the differences or futures of JRockit refer Oracle JRockit Frequently Asked Questions
 
Also as JRockit has been the propitiatoryJDK for BEA, I would use JRockit in Production or similar environment.

For developer environment I believe we should be OK to use either or. If you plan to debug or examine your code with Java Mission Control or want extended futures from Flight recorder than undoubtedly JRockit is your JDK.

If you have more to add please comment below.

Chaw.

When to use Oracle BPEL and OSB?

Often for the newbies of (Oracle) SOA Technologies, this question pops in mind stating when to use BPEL and OSB.

Fundamentally if you read the docs, you will see that both the now Oracle products have similar orchestration capabilities. This blog is written in the intention to clarify the question.

I will cover the one line answer and provide some references I found in the web.

One Liner:

Use of BPEL: State-full, high involvement of Data Manipulation.
Use of OSB: Stateless, Low involvement of Data Manipulation.

For a briefer differentiation, I found another blog in the web space which made my job easier. I have copied the content across to this blog.

Note: the copyright of the below content belongs to the author of the blog page.

Use OSB for:

• Endpoint routing (providing location transparency) so that we do not care about the physical location of the endpoint.
• Endpoint abstraction (interface transparency) so that we do not care about the exact data formats required by the endpoint because the OSB will take care of transformations.
• Load balancing so that we do not care about which of multiple service implementations will actually service a request. 
• Throttling so that we do not care about how use of services is restricted.  
• Enrichment so that we do not care about how additional data is provided to the request to match the expected request and response formats.
• Simple synchronous composition so that we do not care if our abstract service call is actually made up of two or more physical service calls.
• Protocol conversion so that we do not care what physical transports are being used.
• Sync/async abstraction so that we can treat services as fire and forget or query response according to the needs of the client.

Use BPEL for:

• Complex composition of parallel flows that involve more than a couple of services.
• Long running compositions that may run for minutes, hours or days.
• Asynchronous compositions that require correlation of requests and responses.
• Process abstraction that enables us to track processes and their interactions with multiple services.
• Human workflow

Enterprise Integration EAI vs SOA vs ESB

Hi All,

Had some time to browse the net and to brush up on the basics. Came across this interesting paper presentation in the site

ggatz Consulting

Though the site was basic with not much information, I continued reading the paper presented by an author: Anurag Goel.I could not find out the age of the paper as could not find the Source location or date of the article.

I found the article from this link:

http://ggatz.com/images/Enterprise_20Integration_20-_20SOA_20vs_20EAI_20vs_20ESB.pdf

I have also made the paper available here.

Note: The copyright of the article belongs to the Author.

This paper takes us through the comparison of EAI, SOA and ESB and their current/future role in the IT integration Industry. Also explains the relevance between EAI Patterns and current so called SOA Integration Patterns.

 

I like the summary section, as follows (on page 6):

6 TAKEAWAYS SUMMARY
1. SOA brings cost effective, reusable and low lead time solutions to an organization
but EAI and SOA are both going to coexist.
2. SOA is more then web services, in fact web services alone can not handle the
complex, secure and SLA based applications of an enterprise.
3. Enterprise service bus would enable low cost integration and would be used by
companies with limited IT resources
4. Packaged EAI solutions in future would have SOA as basic tenet and would continue
to be the prime choice for large scale integration. 

Happy Reading.

Oracle WebLogic Server Basic Concepts - Domain, Admin server, Managed Server

I found this great resource to answer the following questions:

1. What is a weblogic Domain?
2. What is a Weblogic Admin Server?
3. What is a Managed Server?
4. What is a Weblogic Cluster

and many more basic conscepts of weblogic Server.

Please go to this link: Oracle WebLogic Server Basic Concepts

This will be an eye opener presentation, if you are new to Weblogic Server.

nohup: Execute Commands After You Exit From a Shell Prompt

Most of the time you login into remote server via ssh. If you start a shell script or command and you exit (abort remote connection), the process / command will get killed. Sometime job or command takes a long time. If you are not sure when the job will finish, then it is better to leave job running in background. However, if you logout the system, the job will be stopped. What do you do?

nohup command

Answer is simple, use nohup utility which allows to run command./process or shell script that can continue running in the background after you log out from a shell:

nohup Syntax:

nohup command-name &

Where,

• command-name : is name of shell script or command name. You can pass argument to command or a shell script.
• & : nohup does not automatically put the command it runs in the background; you must do that explicitly, by ending the command line with an & symbol.

nohup command examples

1) Login to remote server
$ ssh user@remote.server.com
2) Execute script called pullftp.sh
# nohup pullftp.sh &
Type exit or press CTRL + D exit from remote server.
# exit
3) Find all programs and scripts with setuid bit set on, enter:
# nohup find / -xdev -type f -perm +u=s -print > out.txt &
Type exit or press CTRL + D exit from remote server.
# exit
Please note that nohup does not change the scheduling priority of COMMAND; use nice for that:
# nohup nice -n -5 ls / > out.txt &
As you can see nohup keep processes running after you exit from a shell. Read man page of nohup and nice command for more information. Please note that nohup is almost available on Solaris/BSD/Linux/UNIX variant.

Update:
# 1: As pointed out by Jason you can use at command to queue a job for later execution. For example, you can run pullftp.sh script to queue (one minute) later execution
$ echo "pullftp.sh" | at now + 1 minute
# 2: You can also use screen command for same. Brock pointed out disown shell internal command for same purpose. Here is how you can try it out:
$ pullftp.sh &
$ disown -h
$ exit

Reference or Source: http://www.cyberciti.biz/tips/nohup-execute-commands-after-you-exit-from-a-shell-prompt.html

This is a complete copy from the source. 

Aditional Info: less Nohup.out

Provides you with the output of the <command&>. This is some thing similar to tail -f on a live log file.