About the CORBA nodes sample

The CORBA nodes sample consists of multiple process flows within one message flow. These process flows include:

• Create a new stock item, specifying the product name and stock-keeping unit (SKU) product number. A user-defined exception is thrown if the SKU product number is out of range or the product name already exists.
• Increase stock quantity, specifying the SKU product number and quantity. A user-defined exception is thrown if the SKU product number does not exist.
• Get stock item details, specifying the product name only. A user-defined exception is thrown if the product name does not exist.
• Reduce stock quantity, specifying the SKU product number and quantity. A user-defined exception is thrown if the SKU product number does not exist or the quantity is too large.
• Delete the stock item, specifying the SKU product number. A user-defined exception is thrown if the SKU product number does not exist.

The following overview diagram shows the relationships between the message flow on IBM Integration Bus, the naming service, and the CORBA server Java application.

1. The stock control management system is hosted as a CORBA server Java application. The server application creates the CORBA object, binds this object to a reference and puts this object reference into the naming service.
2. At deployment time, the CORBARequest node contacts the naming service to get an object reference. The naming service is the mechanism that CORBA server applications use to put their object references. The naming service is started on a specific host name and port number.
3. The StockWarehouseClient message flow drives the requests to the CORBA server Java application by using the object reference and invoking the specific operation on the object in the CORBA server.

Routing the initial message request

This process flow consists of the following nodes:

• MQInput
• Compute (RouteOperation)
• RouteToLabel

The integration node receives a message request from a WebSphere MQ queue.

The Compute node:

1. Sets up routing of the message by specifying the correct label name to which to route in the local environment.
2. Copies the message to the local environment.

Creating a new stock item process

This process flow consists of the following nodes:

• Label
• CORBARequest (createNewStockItem)
• Compute (SetPriceOperation)
• CORBARequest (setPrice)
• Compute (createStockItemResponse)
• MQOutput (MQOutput)
• MQOutput (MQError)

The Label node receives the routed message request. The CORBARequest node invokes the createNewStockItem operation of the CORBA server application that is passing the input parameters, and returns a response.

A Compute node copies the response data to the local environment and sets up the input parameters for the next CORBA request. The next CORBARequest node invokes the setPrice operation of the CORBA server application that is passing the input parameters, and returns a response.

A final Compute node copies the response data to the local environment, then copies all the accumulated responses from the CORBARequest nodes to the message body to be propagated to a WebSphere MQ queue.

Any user-defined exceptions that are thrown from the CORBA server Java application are propagated down the Error terminal of the CORBARequest node to another WebSphere MQ queue.

Increasing stock quantity process

This process flow consists of the following nodes:

• Label
• CORBARequest (addStock)
• MQOutput (MQOutput1)
• MQOutput (MQError1)

The Label node receives the routed message request. The CORBARequest node invokes the addStock operation of the CORBA server application that is passing the input parameters, and returns a response that is propagated to a WebSphere MQ queue.

Any user-defined exceptions that are thrown from the CORBA server Java application are propagated down the Error terminal of the CORBARequest node to another WebSphere MQ queue.

Getting stock item details process

This process flow consists of the following nodes:

• Label
• CORBARequest (getSKU)
• Compute (GetPriceOperation)
• CORBARequest (getPrice)
• Compute (GetStockLevelOperation)
• CORBARequest (getStockLevel)
• Compute (getStockItemResponse)
• MQOutput (MQOutput2)
• MQOutput (MQError2)

The Label node receives the routed message request. The CORBARequest node invokes the getSKU operation of the CORBA server application that is passing the input parameters, and returns a response.

A Compute node copies the response data to the local environment and sets up the input parameters for the next CORBA request. The next CORBARequest node invokes the getPrice operation of the CORBA server application that is passing the input parameters, and returns a response.

Another Compute node copies the response data to the local environment and sets up the input parameters for the next CORBA request. The next CORBARequest node invokes the getStockLevel operation of the CORBA server application that is passing the input parameters, and returns a response.

A final Compute node copies the response data to the local environment, then copies all the accumulated responses from the CORBARequest nodes to the message body to be propagated to a WebSphere MQ queue.

Any user-defined exceptions that are thrown from the CORBA server Java application are propagated down the Error terminal of the CORBARequest node to another WebSphere MQ queue.

Reducing stock quantity process

This process flow consists of the following nodes:

• Label
• CORBARequest (reduceStock)
• MQOutput (MQOutput3)
• MQOutput (MQError3)

The Label node receives the routed message request. The CORBARequest node invokes the reduceStock operation of the CORBA server application that is passing the input parameters, and returns a response that is propagated to a WebSphere MQ queue.

Any user-defined exceptions that are thrown from the CORBA server Java application are propagated down the Error terminal of the CORBARequest node to another WebSphere MQ queue.

Deleting a stock item process

This process flow consists of the following nodes:

• Label
• CORBARequest (deleteStockItem)
• MQOutput (MQOutput4)
• MQOutput (MQError4)

The Label node receives the routed message request. The CORBARequest node invokes the deleteStockItem operation of the CORBA server application that is passing the input parameters, and returns a response that is propagated to a WebSphere MQ queue.

Any user-defined exceptions that are thrown from the CORBA server Java application are propagated down the Error terminal of the CORBARequest node to another WebSphere MQ queue.

Back to sample home