Disabling end point applications of the passive adapter

Problem:-
In the active-passive configuration mode of the adapters, the endpoint application of the passive adapter instance also listens to the events or messages even if the enableHASupport property is set to True.
Cause
By default, in WebSphere Application Server, version 7.0, the alwaysactivateAllMDBs property in the JMS activation specification is set to True. This enables the endpoint application of all the adapter (active or passive) instances to listen to the events.
Solution
To stop the endpoint application of the passive adapter instance from listening to the events, you must set the alwaysactivateAllMDBs property value to False. The JMS activation specification is associated with one or more MDBs and provides the necessary configuration to receive events. If the alwaysActivateAllMDBs property is set to False, then the endpoint application of only the active adapter instance
receives the events. Perform the following procedure, to set the alwaysActivateAllMDBs property to
False.
1. Log on to the administrative console.
2. Go to Resources> JMS > Activation specifications.
3. Click the activation specification corresponding to the application from the list.
4. Click Custom properties under Additional properties.
5. Click alwaysActivateAllMDBs.
6. Change the value to False.
7. Click Apply and OK.
Result:
The endpoint application of only the active adapter instance listens to the events.

Function Selectors Usage in BPMv7.5

 

What is Function Selector?

During inbound processing, a function selector returns the appropriate operation to

be called on the service.

Filename Function Selector:-

Filename Function Selector is a rule-based function selector that provides object

name resolution based on regular expressions that map to file names. A regular

expression is a string that is used to describe or match a set of strings according to

certain syntax rules. As shown below .

Here  “customer” is business object name and “CUST*.xml” regular expression

It only poll the files  which have file name Starts with CUST and  extension as .xml.

Note :- Make sure that native method must be “emitcustomer” because  customer is business object name.

EmbeddedNameFunctionSelector:-

EmbeddedNameFunctionSelector is used for content-specific business objects, where the object name is embedded in the event file. It returns the function name based on the required content data, and not on the wrapper. For example, if the content-specific business object is customerWrapperBG, the function returned by the function selector is emitcustomer. This function selector must be configured with a data handler. The data binding must be the adapter-specific WrapperDataBinding, and it must be configured to use the same data handler that is configured with the function selector.

RootNameFunctionSelector:-

RootNameFunctionSelector is used only for global elements in business objects, where the global element name is the root element name in the event XML file. It returns the function name based on the global element name. For example, if the global element name is CustomerType1, the function returned by the root name function selector is ‘emit CustomerType1'. RootNameFunctionSelector should be used only for global elements with XML Datahandler or UTF8XMLDatahandler.

Note: To use global Elements with Delimited Datahandler or FixedWidth Datahandler, you should use FilenameFunctionSelector instead of RootNameFunctionSelector. RootNameFunctionSelector does not require a Datahandler configuration, as it does not depend on the data handler to determine the function name.