The Infinity Service Bus Service Connector Component

The ISB Service Connector Component is a Camel Component to easily connect to systems via Java Connectors.

The Component is particularly focused on "SQL-like" access to systems where

is to be specified. Hence, this Component might be often used in Data Extraction and Transformation use cases.

This Camel Component can be accessed via the URI


and service of a system defined for this Component via






in a Camel Route.

Registration on Camel

To use the ISB Service Connector Component you need to register it as a bean in your Spring Configuration.

<bean name="isb" class="com.infinity.integration.service.ServiceConnectorComponent">

Note however, that on a Standard ISB Runtime Environment it will already be registered by default.
The connector is configured by default to lookup for the systems defined in the configuration. however, a susbset of systems to be used can be explicitly specified.

<bean name="isb" class="com.infinity.integration.service.ServiceConnectorComponent">
   <property name="systems">
          <entry key="omni">
             <ref bean="omniSystem" />

Connector Implementation Interfaces

Services connected via the Service Connector Component should implement one of the following Interfaces

package com.infinity.integration.service;

public interface SimpleService
	public Map<String, Object> doService(Map<String, Object>  input);
} public interface UpdateService { public Map<String, Object> doInquiryService(Map<String, Object> input);
public Map<String, Object> doUpdateService(Map<String, Object> input);
} public interface DaoService { public Map<String, Object> create(Map<String, Object> input);
public Map<String, Object> read(Map<String, Object> input);
public Map<String, Object> update(Map<String, Object> input);
public Map<String, Object> delete(Map<String, Object> input);
public Map<String, Object> find(Map<String, Object> input);
} public interface TransactionService { public Map<String, Object> addTransaction(Map<String, Object> input);
public Map<String, Object> removeTransaction(Map<String, Object> input);
public Map<String, Object> changeTransaction(Map<String, Object> input);
public Map<String, Object> deleteTransaction(Map<String, Object> input);
public Map<String, Object> find(Map<String, Object> input); }

System and Service Definition via Spring

Implementations of the interfaces in com.infinity.integration.service.* can be registered as Spring Beans like

<bean name="planOmniPlusDao" class="com.sungard.omni.PlanOmniPlusDao">
<property name="inputFields">
<entry key="name" value="planId" />
<entry key="name" value="maxRecords" />

</bean> <bean name="getParticipantBalanceBean" class="com.sungard.omni.GetParticipantBalanceBean">
<property name="inputFields">
<entry key="name" value="participantId" />

These Spring Beans are registered in turn for invocation in Camel Routes via

<bean name="omniSystem" class="com.infinity.integration.system.System">
<property name="name" value="omni">
<property name="services">
      <entry key="getPlan">
         <ref bean="planOmniPlusDao"/>
      <entry key="getFields">
         <ref bean="getFieldsImpl"/>
      <entry key="updateDemographicInfo">
	     <ref bean="updateDemographicInfo"/>

Payload Structure

It is expected that the Payload to services calls is provided in a "Map/List" structure. Hence, it allows to pass Structured Data Types in Stardust directly to Camel Endpoints based on the Service Connector Component.

The top level object is expected to be an instance of Map<String, Object>.

Service Invocation

The services underneath these Classes can then be invoked via

<to uri="isb://service/system/service"/>


<to uri="isb://service/omni/updateDemographicInfo/add"/>

The following table lists all Service Types and the corresponding invocation patterns:

Service Class Invocation Pattern Remark
SimpleService isb://service/system/service  

Limited Return Record Sets

You could also limit the data in the return record set:

The following code invokes the service findPlans on OMNI retrieving the fields PL011, ..., PL902, even if the Service findPlans would potentially more fields.

<bean id="findPlansInputFields" class="org.springframework.beans.factory.config.MapFactoryBean">
<property name="sourceMap">
<entry key="PL011" value=""/>
<entry key="PL933" value=""/>
<entry key="PL906" value=""/>
<entry key="PL091" value=""/>
<entry key="PL951" value=""/>
<entry key="PL902" value=""/>
<camelContext trace="true" xmlns="">
<from uri="..." />
<setHeader headerName="returnFields">
<to uri="isb://service/omni/findPlans"/>