Overview of Java Compute Node in MB
A JavaCompute node has three output terminals — out, alternate and failure — which enable routing to be performed through the out or alternate terminals. This procedure is not as flexible as the nodes that use ESQL for their processing. The Filter node and the enhanced WebSphere Message Broker V6
Compute node both have more than three output terminals. If you are using Java and require more than three output terminals. a full Java plug-in node would be required. Due to the similarities in structure between the code required for a JavaCompute node and a Java plug-in, it is easy to create a new Java plug-in node based on code previously developed for a JavaCompute node. Doing so can provide a new level of reuse for a team, since pre-built function can be added to a message flow developer’s palette in the form of a new plug-in node.If a JavaCompute node needs to communicate with a database, there are three ways to do it:-
1. MbSQLStatement class, which is part of the Java API specific to WebSphere Message Broker
and which lets a node access any ODBC datasources that WebSphere Message Broker can
connect to. This procedure provides full transactional support between a database and other
recoverable resources that support the XA protocol, such as WebSphere MQ.
2. JDBC type 2 or type 4 connection. In this case WebSphere Message Broker is not able to
provide transactional support for database operations.
3. SQLJ. A new facility that became available in WebSphere Message Broker V6 Fix Pack 1. In
this case WebSphere Message Broker is not able to provide transactional support for database
operations.
Benefits of the JavaCompute node
1: Java may be the language of choice for an enterprise or may be a preferred option for productivity
reasons.
2:A key benefit of the JavaCompute node is the wide range of function available in the base Java
classes. In addition, a wide variety of third-party class libraries are available on the Internet.
3:An enterprise may have already developed Java class libraries to perform key business functions.
4:WebSphere Message Broker V6 ships with a number of sample message flows that demonstrate the
use of different class libraries. For example, one sample flow demonstrates basic message
transformation, and another shows how the JavaCompute node can be used to call the Google API.
A JavaCompute node has three output terminals — out, alternate and failure — which enable routing to be performed through the out or alternate terminals. This procedure is not as flexible as the nodes that use ESQL for their processing. The Filter node and the enhanced WebSphere Message Broker V6
Compute node both have more than three output terminals. If you are using Java and require more than three output terminals. a full Java plug-in node would be required. Due to the similarities in structure between the code required for a JavaCompute node and a Java plug-in, it is easy to create a new Java plug-in node based on code previously developed for a JavaCompute node. Doing so can provide a new level of reuse for a team, since pre-built function can be added to a message flow developer’s palette in the form of a new plug-in node.If a JavaCompute node needs to communicate with a database, there are three ways to do it:-
1. MbSQLStatement class, which is part of the Java API specific to WebSphere Message Broker
and which lets a node access any ODBC datasources that WebSphere Message Broker can
connect to. This procedure provides full transactional support between a database and other
recoverable resources that support the XA protocol, such as WebSphere MQ.
2. JDBC type 2 or type 4 connection. In this case WebSphere Message Broker is not able to
provide transactional support for database operations.
3. SQLJ. A new facility that became available in WebSphere Message Broker V6 Fix Pack 1. In
this case WebSphere Message Broker is not able to provide transactional support for database
operations.
- Note-JDBC Type4 Driver is better than ODBC Driver(Type1) in performance.
Benefits of the JavaCompute node
1: Java may be the language of choice for an enterprise or may be a preferred option for productivity
reasons.
2:A key benefit of the JavaCompute node is the wide range of function available in the base Java
classes. In addition, a wide variety of third-party class libraries are available on the Internet.
3:An enterprise may have already developed Java class libraries to perform key business functions.
4:WebSphere Message Broker V6 ships with a number of sample message flows that demonstrate the
use of different class libraries. For example, one sample flow demonstrates basic message
transformation, and another shows how the JavaCompute node can be used to call the Google API.
No comments:
Post a Comment