My Intention for this blog is to publish (Blogish) my knowledge about development and management of systems integration softwere.
This can be useful to all it's readers.
Disclaimer: The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.
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.
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.
Have you been trying to make your MQ messages persist on the MQ server. Than you have landed in the right blog. Follow the steps below to set up MQ Transport to persist the MQ messages on the MQ server.
If you were familiar with weblogic JMS messaging, it is very easy to make a JMS message persist on the weblogic JMS server using OSB as the producer. You can do this by checking the Persistence check box in the business service. But it is not the case if you would want to perform the same for an MQ message on MQ server using OSB MQ transport.
Steps to make your MQ message persist on MQ server using OSB MQ transport:
a. You are using publish action to publish your MQ messages.
b. The below steps are performed on the OSB console.
1. Open your Proxy or Local Proxy Service
2. Navigate and Edit the Stage where Publish action exist.
3. Navigate to the Request action of Publish
4. Right Click --> Add an Action --> Communication --> Transport Headers.
5. Set "SET TRANSPORT HEADERS for" to "Outbound
Request" and Click "Add Header"
6. Click drop down for "SOAPAction" and select Persistence.
7. Click Expression and set the value to be set.
Note: you can repeat steps 5 to 7 to set various other MQ transport headers values. For the entire list of MQ transport headers and their description please visit the blow mentioned Oracle Document:
Document:Oracle® Fusion Middleware Developer's Guide for Oracle Service Bus