• Entries (RSS)
  • Comments (RSS)

Modifying the destination of selector

Posted by | Posted in Websphere Process Server / Integration Developer | Posted on 10-05-2010

Tagged Under : , ,

Modifying the destination of selector

Now we know how to create and configure selector. But after deployment of selector, how do we change the destination of a selector? WebSphere Process Server provides an interface in the admin console to change or add the destination of a selector. Follow the below steps to change/add destination of a selector.

We can use process server admin console to change the selector’s destination. For e.g.: If we have a selector deployed on the server pointing to Component1 and now we want to change the destination to Component2. Follow the below steps to achieve this.

Read the rest of this entry »

Share

Selectors in WebSphere Integration Developer

Posted by | Posted in Websphere Process Server / Integration Developer | Posted on 04-05-2010

Tagged Under : , , , ,

Selectors in WebSphere Integration Developer

A selector is a component that determines which implementation of a component should be invoked at run time based on a set of selection criteria. Every selector will have a default destination. When a selector is invoked it determines which component to invoke based on the date range entries and the selection criteria. A selector can route to any service component at run time.

Creating a Selector
Follow the below steps to create a selector

1. Right click on the module and select New ->Selector.

2. This will open the New Selector window. Enter the name for your selector. I have named it as MySelector. Click on Next.

3. In this page, we need to select the interface for the selector. I have used HelloInterface for this purpose.

4. Click Finish

Configuring the selector
Once we created our selector, we need to configure the selector. Open the selector in selector editor. Follow the below steps to configure the selector.

1. Click on ‘Enter SCA Component’ to configure the Default Component. This will list all the components available. (This will list only components that are having a matching interface). Select the component you want as the default component.

It is very important to provide the default component as an exception will be thrown if no selection criteria matches and no default component present.

2. Click on ‘Add Date selection entry’ icon (the + icon marked in the image).

3. Configure the dates.

My selector is configured to select component2 if the date range is May 01, 2010 to may 04, 2010.

4. Configure the ‘Selection Criteria’. Here we have three options to configure. Current Date, Java, and XPath. This should return a date.

Now add this selector to the assembly diagram and invoke when you want to route a service call dynamically to a component.

For those who want to try this, here is the PI for this example. HelloSelector

Share

Bindings in WebSphere Integration Developer

Posted by | Posted in Websphere Process Server / Integration Developer | Posted on 16-12-2009

Tagged Under : , , , ,

Bindings in WebSphere Integration Developer

Imports and exports in WebSphere Integration Developer need binding information. This binding information will contain the protocol or any other data required by other modules to use this export/import. The meaning of import binding is different from export binding.

Import binding talks about how to access an external service. The default binding method for import is SCA bindings.

An export binding talks about how the service will be published to other modules or other services. An export binding can be HTTP Binding, Messaging Binding(MQ Binding, JMS bindings, MQ JMS etc), SCA Binding and Web Service binding. If the modules are running in same server, it is recommended to use an SCA binding instead of web service or JMS bindings. It is more easy and fast.

Share

com.ibm.wbit.comptest.common.utils.TestException: Could not find module

Posted by | Posted in Websphere Process Server / Integration Developer | Posted on 29-11-2009

Tagged Under : , , , ,

Today I was trying to test a business process using the Integration Test client. First I right clicked on my module in the assembly diagram and clicked on Test Component to test my module. It showed me a message, its publishing the module and it gave me an error in my test client. The error was

com.ibm.wbit.comptest.common.utils.TestException: Could not find module XXX
	at com.ibm.wbit.comptest.controller.util.GeneralUtils.getModuleFor(Unknown Source)
	at com.ibm.wbit.comptest.controller.invocation.impl.Invoker.getModule(Unknown Source)
	at com.ibm.wbit.comptest.controller.invocation.impl.Invoker.managedRun(Unknown Source)
	at com.ibm.wbit.comptest.controller.invocation.impl.Invoker.run(Unknown Source)
	at com.ibm.wbit.comptest.controller.invocation.impl.BaseInvocationHandler.invoke(Unknown Source)
	..........................

I was not sure what the issue was. My module was there and it was showing as published. After few minutes search I got the solution. If your module is little big, first make sure that you have published your module and then start the test client. I think the test client does not have patience to wait for the module to be published and that was causing the problem :-)

Share

Receive choice activity or pick activity in WebSphere Process Server

Posted by | Posted in Websphere Process Server / Integration Developer | Posted on 12-08-2009

Tagged Under : , , , ,

Receive choice activity or pick activity in WebSphere Process Server

A receive choice activity or pick activity is used for receiving different messages (or operations). This activity is extremely useful if you have an interface with more than one operation and you want this interface as the Interface partner for a business process. If you pass an interface with more than one operation to a normal receive activity it would throw you an error message saying “The process does not implement the operation ‘xxx’ of the port type ‘xxx’”. In this case the only option for us to use the interface is to use receive choice activity. To use a receive activity, follow the below steps.

1. Delete the existing receive activity
2. Drag and drop receive choice activity to your business process. A receive choice activity will be created with one choice in it.

receive_choice

3. Add a new receive by right click on receive choice activity and select ‘Add Receive’.

add_receive

4. Select the first receive and go to Details tab in your properties window. Select your interface partner, operation and the input parameters. (Change the display name of receive if you want.).

change_partner_receive

5. Add a reply activity.

6. Repeat these steps for all the operation you have in your interface.

In my case I had two operations in my interface and after configuring receive choice activity my business process look like the one shown below.

receive_choice_final

If you are getting an error message saying, “The process is not startable. No receive choice or receive activity was found that creates a new process instance and does not have incoming links or preceding basic activities.”, make sure that you have checked the “Create a new process instance if one does not already exist” checkbox in the details tab of Receive choice properties window.

receive_choice_properties

Share