WebSphere brand IBM WebSphere Premises Server 6.1 Feature Pack for Sensor Event Services

Working with Reusable Components

Reusable Components are WebSphere® Premises Server task agents that can react to handle a sensor event or to provide information back to the caller or onto an SIBus.

Configuring Reusable Components

Each Reusable Component is a task agent and has configuration properties that can be modified in the WebSphere Premises Server Administrative Console. For details on how to use the WebSphere Premises Server Administrative Console to modify an agent, see Working with agents in the WebSphere Premises Server information center.

The common configuration properties for all Reusable Components are:

ruc.targetBackend
This property should be set to the value of the back-end integration implementation, such as ruc.epcis, ruc.premises, or ruc.rfidic. For example:
  • Setting the value to ruc.epcis in the Observation Reusable Component means you want the output to go to a standard EPCIS interface.
  • Setting the value to ruc.premises in the EPC Reusable Component means you want to generate EPCs using WebSphere Premises Server.
  • Setting the output to ruc.rfidic in the Validation Reusable Component queries InfoSphere™ Traceability Server directly.
action-name.output.success
The topic to use for a response from the message-driven bean (MDB) when an action is successful.
action-name.output.failure
The topic to use a response from the MDB when an action is unsuccessful.

Each Reusable Component can have multiple actions, so you may need multiple versions of the action-name.output.success and action-name.output.failure properties. Also, certain Reusable Components have additional properties that are further explained in the individual topics for each Reusable Component.

You also use the WebSphere Premises Server Administrative Console to set the endpoints for the Reusable Components. The endpoints are necessary when you are using Web services to call InfoSphere Traceability Server. You can set the endpoints as properties in either the WebSphere Premises Server SystemAgent or in each individual Reusable Component task agent. Setting the endpoints in the SystemAgent means that any Reusable Component can use them, while setting the endpoints in individual Reusable Component task agents means you that particular agent will use those endpoints. You can also leave the endpoint property value empty in a task agent if you are not using ruc.epcis or ruc.rfidic as the back-end implementation in that specific Reusable Component.

You can specify an endpoint in two ways:
  • Using the full value, such as ruc.epcis.endpoint=http://localhost:9080/com.ibm.rfidic.web/services/EPCglobalEPCISServicePort.
  • Using the extension, meaning the part of the URL that comes after the port number. For example, ruc.pedigree.endpoint.extension= com.ibm.epcis.pedigree.ws/services/PedigreeServicePort.
Important:
  • Priority is given to the endpoint property over the extension property, if they are both provided.
  • Priority is given to the value of the endpoints in the Reusable Component task agents over the value of the endpoints in the SystemAgent, if they are both provided.

Methods for invoking Reusable Components

There are three methods for invoking Reusable Components: stateless session beans, Web services, and MDBs.

Stateless session beans and Web services are synchronous calls, meaning that if those methods returns a value, then they will return that value directly. The MDBs are asynchronous, meaning that when a message is sent to the Reusable Component, the Reusable Component sends a response to the SIBus, instead of directly returning the response value. To retrieve the response value, you must subscribe to the response message topic. The topic names are configurable for each action in each Reusable Component.

Stateless session bean methods
To use this method, refer to the exact API for each Reusable Component that is explained in each Reusable Component topic. The API is also in the Javadoc information.
Web services interfaces
To use Web services interfaces, refer to the API that is a subset of the session bean methods, as indicated in each Reusable Component topic. Also, a set of WSDL files that you can copy is available in the IBM_RFID_HOME\iFeature\wsdl path.
Message-driven beans
Invoking the Reusable Components as MDBs requires you to configure the activation specifications for Reusable Components and their message selectors. You must configure for the following actions:
  • Sending the input message to the Reusable Component
  • Receiving the response from the Reusable Component

Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.