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.
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:
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.
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.