Harish's SOA Blog

(WMQ) Post a message

2018-04-13T10:48:00.003-07:00

In recent times, we faced a lingering issue in production while posting messages to a remote queue (MQV5.3) using MQ import binding (connections management via server settings) where the connections from client are remained alive/active despite connections are broken from remote side. We applied several settings suggested in Technote but it didn't help. We also checked firewall and TCP settings but no luck.

PMR suggested that its due to older version of MQ which is no longer supported by IBM and we were advised to upgrade. Since MQ is remote and we have no control on it we end up making/managing connections using Java code, which is performing really well as of this writing. Here is the code snippet:

import java.io.BufferedReader;
import java.io.FileReader;
import java.util.Date;
import java.util.Properties;
import javax.jms.JMSException;
import com.ibm.jms.JMSTextMessage;
import com.ibm.mq.jms.MQQueue;
import com.ibm.mq.jms.MQQueueConnection;
import com.ibm.mq.jms.MQQueueConnectionFactory;
import com.ibm.mq.jms.MQQueueSender;
import com.ibm.mq.jms.MQQueueSession;

public static void postMessage(String msg) {

Properties p = new Properties(System.getProperties());

//Setting below properties based on Link1 and Link2
p.put("com.ibm.mq.cfg.TCP.Connect_Timeout", "30");
p.put("com.ibm.mq.cfg.MQRCVBLKTO", "30");

System.setProperties(p);

MQQueueSession session = null;
MQQueueSender sender = null;
MQQueueConnection connection = null;

try {

FileReader fr = new FileReader(
"C:\\Harish\\Msg.txt");
BufferedReader br = new BufferedReader(fr);
String s;
StringBuffer str = new StringBuffer();
while ((s = br.readLine()) != null)
str.append(s);

fr.close();

msg = str.toString();
MQQueueConnectionFactory cf = new MQQueueConnectionFactory();
cf.setHostName(HOST);
cf.setPort(PORT);
cf.setTransportType(1);
cf.setQueueManager(QM);
cf.setChannel(CHANNEL);

connection = (MQQueueConnection) cf.createQueueConnection();
session = (MQQueueSession) connection.createQueueSession(false, 1);
MQQueue queue = (MQQueue) session
.createQueue("queue:///QUEUE");
sender = (MQQueueSender) session.createSender(queue);
JMSTextMessage message = (JMSTextMessage) session
.createTextMessage(msg);

connection.start();
sender.send(message);
System.out.println("Sent message");
} catch (JMSException jme) {
System.out.println("JMSException occurred");
jme.printStackTrace();
} catch (Exception e) {
System.out.println("Exception occurred");
e.printStackTrace();
}

finally {
try {
sender.close();
System.out.println("sender closed");
} catch (Exception ex) {
System.err.println("sender() : " + ex.getLocalizedMessage());
}
try {
session.close();
System.out.println("session closed");
} catch (Exception ex) {
System.err.println("session.close() : "
+ ex.getLocalizedMessage());
}
try {
connection.close();
System.out.println("connection closed");
} catch (Exception ex) {
System.err.println("connection.close() : "
+ ex.getLocalizedMessage());
}
}
}

(SOAP) Post a soap message over an url

2017-12-04T17:32:00.000-08:00

//Replace highlighted in yellow variables as per your requirement.

import java.io.File;
import org.apache.commons.httpclient.HttpClient;
import org.apache.commons.httpclient.methods.FileRequestEntity;
import org.apache.commons.httpclient.methods.PostMethod;
import org.apache.commons.httpclient.methods.RequestEntity;

public class PostSOAP {

public static void main(String[] args) throws Exception {
String strURL="END_POINT";
String strSoapAction = "SOAP-ACTION";
String strXMLFilename = "REQUEST.xml";
File input = new File(strXMLFilename);
PostMethod post = new PostMethod(strURL);
RequestEntity entity = new FileRequestEntity(input, "text/xml; charset=ISO-8859-1");
post.setRequestEntity(entity);
post.setRequestHeader("SOAPAction", strSoapAction);

HttpClient client = new HttpClient();

try {
int returnCode = client.executeMethod(post);
//To print the http response code.. 200 for success.
System.out.println("Response status code: " + returnCode);
//To print the output.
System.out.println(post.getResponseBodyAsString());
} finally {
post.releaseConnection();
}
}
}

(WID/WPS) Issue CWWBF0060E : com.ibm.websphere.sca.ServiceRuntimeException: Component not found

2012-11-28T05:53:00.002-08:00

This particular exception is nothing to do with the coding or deployment, its just a build issue.
This exception arises while running any business process (from any test client) when there is problem in building the EJB project.

This is how this can be solved.

Solution 1 :
1) Make sure you have closed all opened file taking part in building the project (Better do not open any file)
2) Clean build & then deploy.

Solution 2 :
1) Go to Resource Perspective delete all .class files carefully.
2) Do clean then build. (on EJB project only!)
3) Ensure you have no EJB related files open ( as this does cause problems)
4) Go back to The Integration perspective then clean + build.

(WID/WPS) Testing components using Ant Script

2012-06-15T07:00:00.000-07:00

This post shows how to test component developed in WID using a script.

In scenarios where we do regression testing with predefined set of test data, its very tedious to do manual testing. Ideally we should create a test project for the module with test cases under a Test suite.

Below diagram show a snapshot of Test suite testing:

Script:
<project name="Automated OP Test Case Run" basedir="." default="run">
<property name="test" value="ScriptTest"/>
<property name="module" value="Script"/>


<target name="test">
<get dest="C:/OPTest.xml" src="http://localhost:9081/${test}Web/TestServlet"/>
</target>

In above script "Script" is the name of the module & ScriptTest is Test project.
It also exports test result in specified location which is C:/OPTest.xml in above example.

We can also run all the test cases of a test suite using this url
http://localhost:9081/ScriptTestWeb/TestServlet

TestServlet is a servlet (com.ibm.wbit.comptest.ct.servlet.TestServlet)

PI

(WID/WPS) Security QOS

2012-06-15T02:20:00.000-07:00

Security Identity qualifier specifies the identity under which implementation will run at the runtime. A role is specified to the identity. This role dictates whether the component or implementation is authorized to invoke downstream methods. Security Identity is equivalent to the RunAs Role used for delegation in Websphere Application Server.

One of the steps to deploy secured application is to assign users and groups to the Roles that were defined when the application was constructed. This step can be achieved by following the step entitled as "Map security Roles to User and Groups". You can add new users and groups or modify the existing information during this step.

One more step that one has to configure which is entitled as "User RunAs Role". In this step you have to sepcify the user name and password of a user and assign to a role. Important is that user for which you have entered username and password should be the member of that role.

For example, if the RunAs role is assigned user "bob", and the client, "alice", is invoking a BPEL component that invokes method on other secured component, then invocation will happen under the identity of 'bob'. In this case 'bob' must be a authorized user to the invoked secured component. If the user is not authorized a security permission exception is raised.

For more info

http://publib.boulder.ibm.com/infocenter/dmndhelp/v7r0mx/index.jsp?topic=%2Fcom.ibm.websphere.wps.doc%2Fdoc%2Ftsec_deploying.html

Scenario 1 (Setting the Security permission)

Case 1 : When user is not assigned to any role, currently user is harish

Result :
[6/15/12 12:14:57:191 IST] 000002d0 ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "transactionRequiredActivitySessionNotSupported" on bean "BeanId(SecuritySampleApp#SecuritySampleEJB.jar#Module, null)". Exception data: com.ibm.websphere.sca.ServiceRuntimeException: Permission denied: harish is not in role Caller

Case 2 : When user/group , this time its user = harish is assigned to the Caller role.

Assigning harish to Caller role.

Result : Worked correctly.

Scenario 2 (Setting the Security Identity)

Note : Here privilege = ProIdentity

Case 1 : When no Run as property is set.
Result:

[6/15/12 12:26:07:273 IST] 000002cd ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WID62\pf\wps\logs\ffdc\server1_000002cd_12.06.15_12.26.07_0.txt
[6/15/12 12:26:07:273 IST] 000002cd ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WID62\pf\wps\logs\ffdc\server1_000002cd_12.06.15_12.26.07_0.txt
[6/15/12 12:26:07:273 IST] 000002cd ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "transactionRequiredActivitySessionSupports" on bean "BeanId(SecuritySampleApp#SecuritySampleEJB.jar#Module, null)". Exception data: com.ibm.websphere.sca.ServiceRuntimeException: The run-as authentication data is not configured for role ProIdentity.....

Case 2 : Caller : managers group , ProIdentity : harish

Result:
[6/15/12 12:37:41:887 IST] 000002cb ExceptionUtil E CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "transactionRequiredActivitySessionNotSupported" on bean "BeanId(SecuritySampleApp#SecuritySampleEJB.jar#Module, null)". Exception data: com.ibm.websphere.sca.ServiceRuntimeException: Permission denied: harish is not in role Caller

Note : Here harish is not a member of managers group (which is actually mapped to the Caller role)

Case 2 : Caller : managers group , ProIdentity : man & ProIdentity Role is assigned to man & harish users.

Note : Here man is a member of managers group.

Result : Worked properly

Attached PI

(WID/WPS) Integrated Test Client

2012-06-14T04:51:00.000-07:00

This post is kind of must read post for all WID/WPS developers, because what we develop today, we test that sooner or later with unit or integration testing.

Highlights of the post are:

Component Testing.
Module Testing.
Testing modules from external application (Attaching to a module)
Emulation (Manual/Programmatic)
Creating reusable Test Cases.
Data pool (Reusing values)
Testing using Ant script

Few very very useful links:

Getting the most out of the WebSphere Integration Developer integration test client
http://www.ibm.com/developerworks/websphere/techjournal/0712_gregory/0712_gregory.html

Taking component testing to the next level in WebSphere Integration Developer
http://www.ibm.com/developerworks/websphere/library/techarticles/0806_gregory/0806_gregory.html

Testing SOA applications with WebSphere Integration Developer and Ant scripts
http://www.ibm.com/developerworks/websphere/library/techarticles/0903_bist/0903_bist.html

A doc on test client
http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/topic/com.ibm.iea.wid_v7/wid/7.0/Testing/WBPMv7_WID_TestClientLab.pdf

(WID/WPS) How does Human Task Manager work ?

2012-06-11T06:54:00.001-07:00

Prerequisite for this post is basic understanding of human tasks.

When we model a human task, we can set a verb and a parameter that can be used to build a query to the user registry.Tasks are then created and assigned for all users in the result set of that query.

Below figure shows the link between modeling time and runtime.
The attribute role of an activity is set to Potential Owner.
The verb is set to Group Members and the parameter to Approvers.
At runtime, this is used to build a SELECT ALL query. This query returns two users, John and Jane. John and Jane are members of the group Approvers and become potential owners of this new task.

Assigning tasks to users at runtime

Interaction between HTM & user registry

The Human Task Manager runs as a container within the application server.It is accessible through SCA or by way of specific APIs.These APIs or the client SCA interface can create a new task.When a new task is created, it follows following steps:

HTM retrieves information from its database to build the query.
HTM passes the query to the Staff Plug-in Provider using the Staff Service.
The query is executed against the staff repository to retrieve a user or group of users.
The query results are returned to the HTM.
The new tasks that are created for the selected users are then stored in the database by the HTM.

(WID/WPS) Sending/Receiving Message using JMS Export

2012-06-08T06:08:00.001-07:00

Following code shows how to use JMS export binding to send message to the mediation module & get response back from the same.

Flow is like:
JMS Export ->> Mediation Module ->> Web Service Import (Can be any service provider)

Code Snippet for JMS Client :
try{
String icf = "com.ibm.websphere.naming.WsnInitialContextFactory";

//the Provider URL
String url = "iiop://localhost:2809";

//The Queue Connection Factory used to connect to the bus
String sampleQCF = "jms/sampleQCF";

//The Queue used to send requests to the mediation module
String sampleSendQueue = "jms/profileServiceExportIn";

//The Queue used to receive responses from the mediation module
String sampleReceiveQueue = "jms/profileServiceExportOut";

//The XML representation of a Profile which is the Business Object required by the add operation on the ProfileService Interface.
String message = "<?xml version=\"1.0\" encoding=\"UTF-8\"?>";
message += "<profile xmlns:ns2=\"http://BookOrderResources\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xsi:type=\"ns2:Profile\">";
message += "<name>"+request.getParameter("name")+"</name>";
message += "<address>";
message += "<street>"+request.getParameter("street")+"</street>";
message += "<city>"+request.getParameter("city")+"</city>";
message += "<country>"+request.getParameter("country")+"</country>";
message += "</address>";
message += "<creditCardNum>"+request.getParameter("creditCardNum")+"</creditCardNum>";
message += "<lastUpdate>2006-02-16</lastUpdate>";
message += "</profile>";

java.util.Hashtable env = new java.util.Hashtable();
env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, icf);
env.put(javax.naming.Context.PROVIDER_URL, url);
javax.naming.Context ctx = new javax.naming.directory.InitialDirContext(env);

//Lookup the ConnectionFactory
javax.jms.ConnectionFactory factory = (javax.jms.ConnectionFactory)ctx.lookup(sampleQCF);

//Create a Connection
javax.jms.Connection connection = factory.createConnection();

//Start the Connection
connection.start();

//Create a Session
javax.jms.Session jmsSession = connection.createSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE);

//Lookup the send Destination
javax.jms.Destination sendQueue = (javax.jms.Destination) ctx.lookup(sampleSendQueue);

//Create a MessageProducer
javax.jms.MessageProducer producer = jmsSession.createProducer(sendQueue);

//Create the TextMessage that will hold out profile as text
javax.jms.TextMessage sendMessage = jmsSession.createTextMessage();

//Set the content of the message to be the XML defined Profile
sendMessage.setText(message);

//Set the operation to call on the ProfileService interface to be add
sendMessage.setStringProperty("TargetFunctionName", "add");

//Send the message
producer.send(sendMessage);

//Lookup the receive Destination
javax.jms.Destination receiveQueue = (javax.jms.Destination) ctx.lookup(sampleReceiveQueue);

//Create a MessageConsumer
javax.jms.MessageConsumer consumer = jmsSession.createConsumer(receiveQueue);

//Wait 15 seconds to receieve the response
javax.jms.TextMessage receiveMessage = (javax.jms.TextMessage) consumer.receive(15000);

if (receiveMessage != null) {
System.out.println(receiveMessage.getText());
}

//Close the Connection
connection.close();
}
catch (Exception e) {
e.printStackTrace();
}

Server run time configuration:

We need to create both the queues & QCF along with activation specification so that the module can register the input queue with its message listener as follows:

Click Resources → JMS Providers → Default messaging.
Under Activation Specifications, click JMS activation specification.
Click New to create an activation specification

Set the name field to sampleAS.
Set the JNDI name field to jms/sampleAS.
Select the destination type as Queue.
Set the Destination JNDI name to jms/profileServiceExportIn.
Select the SCA.APPLICATION.esbCell.Bus bus from the Bus name menu.

Following are the screen shots for business object & interface:

Business objects used in ProfileService interface

ProfileService interface

Attached PI

(WID/WPS) Mapping Bindings

2012-06-07T05:06:00.001-07:00

One of the crucial functionality provided by WESB is the protocol transformation or in other words "transport binding transformation".

In the example given below I have done mapping from SOAP/HTTP Web service binding to JMS binding.

Background:
Bindings can be defined on an import or export. On an export, they describe how a client or an SCA component communicates with the mediation module. On an import, they describe how the mediation module communicates with the defined service.

Server Runtime configuration:
Creating a new Destination (Queue)

Run the administrative console and log in.
Select Service integration -> Buses.
Click the SCA.APPLICATION.xxxCell.Bus link. (xxx is either wid or esb)
Under Destination resources on the right-click Destinations.
We will see two predefined destinations, a topic, and a queue.
Click New to create a new destination on the bus.
The next screen shows four types of destination that can be specified. Select
Queue and click Next.
The queue attributes screen is displayed. Enter JMSImportOut as the identifier
then click next & complete the queue attribute creation.

Creating a QCF & Queue

Select Resources -> JMS Providers -> Default messaging.
Under Connection Factories, click JMS queue connection factory, click New.
Fill in the properties of the queue connection factory:

Set the Name as sampleBindingQCF.
Set the JNDI Name to jms/sampleBindingQCF.
From the list for Bus name, choose SCA.APPLICATION.xxxCell.Bus.
Click OK at the bottom of the screen.

Select Resources -> JMS Providers -> Default messaging.
On the right, under Destinations, click JMS queue and then click New.
Create the queue.

Set the Name to JMSImportOut.
Set the JNDI Name to jms/JMSImportOut.
Select SCA.APPLICATION.xxxCell.Bus from the Bus Name menu.
Select JMSImportOut from the Queue Name menu.
Click OK at the bottom of the screen.

Click the Save link at the top of the console and confirm the changes to the master configuration by clicking Save.

After successful completion code & testing, to the message in queue follow the below steps:

Select Service integration -> Buses -> SCA.APPLICATION.xxxCell.Bus -> Destinations -> JMSImportOut -> Queue points -> JMSImportOut@xxxNode.server1-SCA.APPLICATION.xxxCell.Bus.

We can see the current message depth is 1, to see whats there in message,click the Messages link in Additional properties (right)

Now click on Identifier link to see the message body.

Attached PI

(WID/WPS) FlatFile Inbound Adapter issue & fix

2012-05-28T02:06:00.002-07:00

If you deploy your application to WebSphere Process Server 6.1 or 6.2 containing WebSphere Application Server 6.1.0.23 through 6.1.0.25, the polling function does not work for inbound adapter

Here is the fix, just one property needs to be set.
Very very useful as I wasted approx a month to get it done :(

http://www-304.ibm.com/support/docview.wss?rs=695&context=SSMKUK&dc=D600&uid=swg21394864&loc=en_US&cs=UTF-8&lang=en

(WID/WPS) Dynamic EndPoints in Mediation Flow

2012-04-11T03:46:00.002-07:00

The concept of Dynamic End Points provide the runtime support, in fact it provides an enhancement to the WESB (and WPS) runtime to:

Allow the mediation programming model to select (or to influence the selection of) service endpoints at the runtime.
Allow the selection at runtime of a service endpoint that has not been predefined in the mediation flow

With the support provided by Dynamic End Points, the mediation flow designer
can use a Callout Node in the flow in a dynamic way. For a dynamic callout, the associated reference provided on the component need not be wired to an import. At runtime, the dynamic callout retrieves an element from the SMO which provides the endpoint address to be used by the callout as the service endpoint.

Note : The highlighted property should be checked to achieve this functionality.

Callout Node property to get dynamic behaviour

The endpoint address can be passed along with the input message or can be retrieved within the flow by calling db or performing any business logic.

This endpoint address should be mapped to /headers/SMOHeader/Target/address using a map or custom mediation primitive.

Mapping of endpoint address to '/headers/SMOHeader/Target/address'

Following are assembly diagrams for ServiceProvider & DynamicEndpointsPOC projects :

Note : There is no wiring from DynamicLookup Mediation component to any of the import as it will be determined at runtime by callout node.

How to run : We can have a client project to call the standlalone reference asking user for the endpoint address :

For calling the SCA export binding : sca://ServiceProvider/JavaCompExport
For calling the webservice export binding : http://localhost:9081/ServiceProviderWeb/sca/IServiceExport1
For calling the HTTP export binding : http://localhost:9081/ServiceProviderWeb/HttpCompExport/doTest

How to call a standalone reference : http://harishonsoa.blogspot.com/2012/04/standalone-reference-client.html

Attached the PI.
Note : HTTP binding works only if Data objects are used for input & output.

Alternative way of setting the SMOHeader.Target :

String port = "9081";
String hostname = "localhost";
String URI = "http://"+hostname+":"+port+"/";
String serviceIdentification =
((commonj.sdo.DataObject)smo.getContext().getTransient() ).getString("ID");
if(serviceIdentification.equals(" Provider1"))
{
URI = URI + "Export1";
}
else if(serviceIdentification.equals("Provider2"))
{
URI = URI + "Export2";
}
com.ibm.websphere.sibx.smobo.TargetAddressType targetAddress =
com.ibm.websphere.sibx.smobo.ServiceMessageObjectFactory
.eINSTANCE.createTargetAddressType();
targetAddress.setAddress(URI);
smo.getHeaders().getSMOHeader().setTarget(targetAddress);
out.fire(smo);

Updated on April 4th, 2017

In cases, alternate endpoints need to be configured (Actual endpoint failed and mediation should retry to alternate endpoints), this can be done as below:

<context>

      <propertySets>
        <group>CalleeMediation.ServiceProviderMediationFlow</group>
        <properties>
          <name>ServiceProviderInfcPartner_processName_Callout.retryCount</name>
          <value>3</value>
        </properties>
        <properties>
          <name>ServiceProviderInfcPartner_processName_Callout.retryDelay</name>
          <value>2</value>
        </properties>
        <properties>
          <name>ServiceProviderInfcPartner_processName_Callout.retryOn</name>
          <value>1</value>
        </properties>
        <properties>
          <name>ServiceProviderInfcPartner_processName_Callout.tryAlternateEndpoints</name>
          <value>true</value>
        </properties>
      </propertySets>
    </dynamicProperty>
</context>
<headers>
    <SMOHeader>
      <MessageUUID>387185A6-015B-4000-E001-563E8EAE73C4</MessageUUID>
      <Version>
        <Version>7</Version>
        <Release>0</Release>
        <Modification>0</Modification>
      </Version>
      <Target>
        <address>http://localhost:9080/CalleeMediationWeb/sca/ServiceProviderInfcWSExportWrong</address>
      </Target>
      <AlternateTarget>
        <address>http://localhost:9080/CalleeMediationWeb/sca/ServiceProviderInfcWSExporta1</address>
      </AlternateTarget>
      <AlternateTarget>
        <address>http://localhost:9080/CalleeMediationWeb/sca/ServiceProviderInfcWSExpora2</address>
      </AlternateTarget>
      <AlternateTarget>
        <address>http://localhost:9080/CalleeMediationWeb/sca/ServiceProviderInfcWSExport</address>
      </AlternateTarget>
    </SMOHeader>
</headers>

Callout Prop:

Above promoted properties can be configured on need basis.

TryAlternateEndpoints should be true to try alternate endpoints otherwise it will retry same endpoint (based on retryCount value)

Retry_On=1

#Retry on values
# Never - 0
# Any fault - 1
# Modeled fault - 2
# Unmodeled fault – 3

Code:

DynamicPropertySetType dynamicPropertySet = ServiceMessageObjectFactory.INSTANCE.createDynamicPropertySetType();
dynamicPropertySet.setGroup("CalleeMediation.ServiceProviderMediationFlow");

PropertyType property1 = ServiceMessageObjectFactory.INSTANCE.createPropertyType();
property1.setName("ServiceProviderInfcPartner_processName_Callout.retryCount");
property1.setValue(Retry_Count_Value));

PropertyType property2 = ServiceMessageObjectFactory.INSTANCE.createPropertyType();
property2.setName("ServiceProviderInfcPartner_processName_Callout.retryDelay");
property2.setValue(Retry_Delay_Value));

PropertyType property3 = ServiceMessageObjectFactory.INSTANCE.createPropertyType();
property3.setName("ServiceProviderInfcPartner_processName_Callout.retryOn");
property3.setValue(Retry_On_Value));

PropertyType property4 = ServiceMessageObjectFactory.INSTANCE.createPropertyType();
property4.setName("ServiceProviderInfcPartner_processName_Callout.tryAlternateEndpoints");
property4.setValue(TryAlternateEndpoints_Value));

// Add the properties
dynamicPropertySet.getProperties().add(property1);
dynamicPropertySet.getProperties().add(property2);
dynamicPropertySet.getProperties().add(property3);
dynamicPropertySet.getProperties().add(property4);

DynamicPropertyContextType dynamicPropertyContext = ServiceMessageObjectFactory.INSTANCE.createDynamicPropertyContextType();
dynamicPropertyContext.getPropertySets().add(dynamicPropertySet);
smo.getContext().setDynamicProperty(dynamicPropertyContext);

TargetAddressType targetAddress1 =   ServiceMessageObjectFactory.eINSTANCE.createTargetAddressType();
targetAddress1.setAddress(URI1);

TargetAddressType targetAddress2 =   ServiceMessageObjectFactory.eINSTANCE.createTargetAddressType();
targetAddress2.setAddress(URI2);

TargetAddressType targetAddress3 =   ServiceMessageObjectFactory.eINSTANCE.createTargetAddressType();
targetAddress3.setAddress(URI3);

smo.getHeaders().getSMOHeader().getTarget().setAddress(URI4);

smo.getHeaders().getSMOHeader().getAlternateTarget().add(targetAddress1);
smo.getHeaders().getSMOHeader().getAlternateTarget().add(targetAddress2);
smo.getHeaders().getSMOHeader().getAlternateTarget().add(targetAddress3);

(WID/WPS) StandAlone Reference Client Implementation

2012-04-10T06:07:00.000-07:00

Following imports are required to implement this :

<%@ page import="com.ibm.websphere.sca.ServiceManager" %>
<%@ page import="com.ibm.websphere.sca.Service" %>
<%@ page import="commonj.sdo.DataObject" %>
<%@ page import="com.ibm.websphere.bo.BOFactory" %>

Code snippet :

ServiceManager serviceManager = new ServiceManager();
BOFactory bofactory = (BOFactory) serviceManager.locateService("com/ibm/websphere/bo/BOFactory");

// Create the request DO
DataObject input = bofactory.createByElement("http://WSLib/IProviderSync", "syncOp");
input.setString("in", "My_Input");

// "http://WSLib/IProviderSync" is the namespace of the interface containing "syncOp" operation, // which are going to call through standalone reference.
// "in" is the input name of the operation.

// Send the request
Service service = (Service) serviceManager.locateService("IProviderSyncPartner");
// "IProviderSyncPartner" is the name of the reference partner of the standalone reference.
DataObject output = (DataObject)service.invoke("syncOp", input);

// Get the response
String outputDoTest = output.getString("out");
// "out " is the output name of the operation.

Interface

Standalone reference property

Note : We should bundle this client app into the EAR which has standalone reference.

(WID/WPS) Message Logger Primitive

2012-03-28T08:06:00.006-07:00

This post gives brief information about Message Logger primitive with few implementation details.

The purpose of a MLP is to log selected content of the service message object, or SMO.
The message is written in XML format. We configure the primitive using an XPath expression so that all or part of the SMO is written. The default is to log the message payload, as identified by the XPath expression /body.
The message logger primitive provides we with the choice between two different implementations.
One implementation writes log records to a relational database.
The other implementation option, which was introduced in version 6.2, is custom logging. It makes use of the Java logging APIs. With this option, we can choose a default implementation provided by the product that writes log records to a file, or we can provide our own Java logging implementation.
The SMO is not updated by the message logger.

First Implementation (DB)

Here user defined relational database is being used.

Note :

Data source name : jdbc/mediation/mymessageLog; by default this value was jdbc/mediation/messageLog which is the jndi name for default WPS or WESB database.
ESBLOG.MSGLOG table was created in the user defined DB.(Default table where this data will be stored)

CREATE SCHEMA ESBLOG;

CREATE TABLE ESBLOG.MSGLOG (TIMESTAMP TIMESTAMP NOT NULL, MESSAGEID VARCHAR(36) NOT NULL, MEDIATIONNAME VARCHAR(256) NOT NULL, MODULENAME VARCHAR(256), MESSAGE CLOB(100000K), VERSION VARCHAR(10));

ALTER TABLE ESBLOG.MSGLOG ADD CONSTRAINT PK_MSGLOG PRIMARY KEY (MESSAGEID, TIMESTAMP, MEDIATIONNAME);

As the table columns describes what every column means.

Server admin console configuration is also required for this to work.

Second Implementation (Custom)

User defined logging handler (To know about what to have in this handler read http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.wpi_v6/wpswid/6.2/MediationPrimitives/WBPMv62_MessageLoggerPrimitive/player.html)

Promotable Properties : If we want to have control on certain properties at runtime , configure this.

Administrating these properties :

For PI : https://docs.google.com/open?id=0ByotHxAO08TDb2VuaHEycFhRWUd5dGlaOFQ2ZVVBUQ

(WMB) Timestamp Conversion

2012-03-21T05:35:00.000-07:00

Often we require to change time stamp from one format to another.
Below esql code shows how to convert an incoming data (which is a time stamp in string) into time stamp or String of the desired format.

Declare srcFormat CHARACTER; -- Source (Incoming time stamp format)
Declare targetFormat CHARACTER; -- Target (Expected time stamp format)
DECLARE InTime TIMESTAMP;
SET srcFormat = 'yyyy-MM-dd HH:mm:ss.SSS';
SET targetFormat = 'yyyy-MM-dd''T''HH:mm:ss.SSS';

-- Converting string into time stamp of same format.
SET InTime = cast(InputBody.time as TIMESTAMP FORMAT srcFormat);

-- Converting time stamp to string of target format.
SET OutputRoot.XMLNSC.out.time = cast(InTime as CHARACTER FORMAT targetFormat);

(WID/WPS) Diverging/Converging Gateway types

2012-03-19T07:43:00.000-07:00

GeneralizedFlow

A diverging gateway is made available for an activity when two or more links (excluding fault links) start at this activity. We can specify one of three types of diverging gateway :

Split, in which only the first link (going left to right) with a transition condition of true is navigated.

Fork, in which all links are navigated in parallel.

Inclusive OR, in which all links with transition conditions of true are navigated.

A converging gateway is made available for an activity when two or more links (including fault links) end at this activity. We can specify one of three types of converging gateway :

Merge - exclusive pathway. When the first link is followed with a "true" flag, the gateway is evaluated and the activity commences. No synchronization happens with the remaining incoming links.

Join - parallel pathways. All incoming links are synchronized, the gateway is evaluated when all links are followed. When all links are followed with a "true" flag the activity commences. When all links are followed with a "false" flag the activity is skipped. When some links are followed with a "true" flag but some with a "false" flag the run time throws an exception.

Note: In cases where this exception can happen, a warning is displayed while modeling the process or when deploying the process.

Inclusive OR - exclusive and/or parallel pathways. This gateway can be used to merge exclusive paths, or to join parallel paths, or both. When merging exclusive paths, the gateway is evaluated and the activity commences when the first link is followed with a "true" flag. When joining parallel paths, all incoming links are synchronized, the gateway is evaluated when all links are followed. When one or more links are followed with a "true" flag the activity commences. When all links are followed with a "false" flag the activity is skipped. When exclusive and parallel paths converge at this gateway, it is evaluated in the reverse order of the opposite converging gateways. See troubleshooting for more information.

(WID/WPS) Whats new in WID 6.2

2012-03-19T06:59:00.000-07:00

The Solution view is a new view that shows how our modules, mediation modules, and libraries relate each other. (Integration solutions)
Included Generalized Flows (formerly called Cyclic Flows), Repeat Until loops, and Collaboration Scope.
In previous releases, business object maps were only used in the assembly diagram. Now we can use a business object map as a step of our business process.
Support for Services Gateway pattern.

Mediation Related Changes :

The Mediation Flow editor has improved support for protocol specific headers, including CICS and IMS messages.
Mapping has been improved to support very large business objects.
Mediation flows and XSLT transformations can now be included in a business module, rather than needing their own module. Performance is improved by eliminating the hop between modules, improving efficiency.Multiple mediation components can now be placed into a single module. Since a mediation flow is treated like any other component now, there is no longer a need for a specialized mediation module. A mediation can be part of any module now.
A new construct called a mediation subflow can be used to encapsulate reusable mediation logic.

For more info :
http://www.ibm.com/developerworks/websphere/bpmjournal/0812_fasbinder6/0812_fasbinder6.html

(WID/WPS) Collaboration Scope

2012-03-19T04:27:00.002-07:00

It is used to create enhanced dynamic workflows.
It is the preferred tool for the case paradigm.
A "CASE" is the product of a workflow or a part of a workflow used to handle knowledge intensive business flows.
A case can be any number of things, including : Evaluation of job application , Ruling on an insurance claim.
Any business process can be handled as a case, but it is ideally suited to situations where the task owner uses knowledge and experience to :

Trigger sub-process : doctor orders an additional blood test.
Repeat a number of activities : a job applicants second interview.

Case handling support is provided by combining dynamic features and the collaboration scope activity.
BPEL Process Choreographer Explorer runs Business Space support process dynamically at runtime.
We can create business logic within our collaboration scope by adding basic activities.
We can't include structured activities in a collaboration scope.
Exit conditions allow us to automatically skip and repeat steps.
We set the administrators for the collaboration scope to specify the people allowed to perform manual skips and jumps at run-time.(default setting is everybody)

For more information :

http://ibmprocessserver.blogspot.com/2012/01/practice-collaboration-scope-in-process.html

(WID/WPS) Fault Links

2012-03-16T06:29:00.000-07:00

When faults occur in our business process, fault handlers are typically engaged to deal with the fault. The generalized flow activity offers a simplified fault handling procedure.
From any scope or basic activity (excluding the Throw and Rethrow activities) we can add one or more "fault links".

A fault link in an activity is followed if the specified fault occurs while the activity is running. We can define "catch" fault links for various conditions, or we can create a "catch all" fault link, which will be followed should any fault occur that is not covered by a catch fault link. If multiple fault links are modeled for the same activity, best match decides which fault link will be followed. The fault catching rules are the same as for fault handlers.

Fault link considerations:

When we use fault links in our business process, consider the following:

A fault link is activated for faults that occur within the source activity only. The evaluation of conditions of normal links is not part of the execution of the activity.
If the source activity of the fault link is a scope activity, the fault handler of the scope activity is evaluated first when a fault occurs inside the scope. However, the fault handler can rethrow the fault. In this case, a fault link of the scope can catch the fault and can be navigated.
If an activity is the source of multiple fault links, only one of the fault links can be navigated when a fault occurs.
The target activity of the fault link will be executed normally. Compensate and rethrow activities in fault handlers cannot be the target of a fault link.
When a fault contains fault data, a variable of the fault data type needs to be declared on the surrounding scope. The fault link must reference this variable so that the target activity of the fault link has access to the fault data.

Following business process shows the fault link usage along with fault handler.

FaultBO used for the fault :

Interface used for Invoke activity :

When invoke activity throws any fault say fault1, Fault handler enclosed with the activity will try to handle this fault first. When it is rethrown from fault handler it will be following the corresponding fault link path defined on the scope level.

Code snippet for throwing a fault {Invoke activity implementation}:
private DataObject createFault(String severity, String messageID, String message, String shortText)
{
BOFactory bof =(BOFactory)ServiceManager.INSTANCE.locateService ("com/ibm/websphere/bo/BOFactory");
DataObject faultBo = bof.create("http://FaultLinkModule", "FaultBO");
faultBo.setString("severity", severity);
faultBo.setString("messageID", messageID);
faultBo.setString("message", message);
faultBo.setString("shortText", shortText);
return faultBo;
}

public Boolean doValidation(String input) {
boolean value=true;
if(<<Condition1>>)
{
value=false;
throw new MyServiceBusinessException(createFault("1", "111", "This is Fault 1", "FAULT1"),"fault1");
//throw new MyServiceBusinessException(new String("Fault 1 Thrown"), "fault1");//Fault Name : fault1
}
else if(<<Condition2>>)
{
value=false;
throw new MyServiceBusinessException(createFault("2", "222", "This is Fault 2", "FAULT2"),"fault2");//Fault Name : fault2
//throw new MyServiceBusinessException(new String("Fault 2 Thrown"), "fault2");
}
return value;
}

//Where MyServiceBusinessException is a user defined class extending ServiceBusinessException class.

Download the PI: https://docs.google.com/open?id=0ByotHxAO08TDQWtJbjBDaTNSdTJYaEZEV3ZaVFA1UQ

Note :

(WID/WPS) Querying Business Process & Human Task

2012-03-13T04:03:00.000-07:00

LocalBusinessFlowManagerHome bfmHome = null;
InitialContext context = new InitialContext();
bfmHome = (LocalBusinessFlowManagerHome) context.lookup("local:ejb/com/ibm/bpe/api/BusinessFlowManagerHome");
LocalBusinessFlowManager flowManager = bfmHome.create();

String processTemplate = "MyProcess";
String selectClause = "DISTINCT ACTIVITY.AIID";
String whereClause = "PROCESS_TEMPLATE.NAME = '" + processTemplate+ "'";

QueryResultSet result = flowManager.query(selectClause, whereClause, (String) null,(Integer) null, (TimeZone) null);
System.out.println("\n > query(), result size: " + result.size());

if (result.size() == 0)
{
System.exit(0);
}

while (result.next())
{
AIID aiid = (AIID) result.getOID(1);
System.out.println("AIID : " + aiid.toString());
ActivityInstanceData aid = flowManager.getActivityInstance(aiid);
System.out.println("App Name " + aid.getApplicationName());
System.out.println("Display Name " + aid.getDisplayName());
System.out.println("ProcessTemplate Name "+ aid.getProcessTemplateName());

// Below code is for human task only :

flowManager.claim( aiid ); // For Claiming the humantask
flowManager.createWorkItem( aiid, WorkItemData.REASON_READER, "admin");
flowManager.createWorkItem( aiid, WorkItemData.REASON_EDITOR, "admin");
System.out.println( "Created Work Item ");

// transfer this EDITOR -workItem from admin to harish
flowManager.transferWorkItem( aiid, WorkItemData.REASON_EDITOR, "admin", "harish");
System.out.println( "Transferred Work Item");

flowManager.deleteWorkItem( aiid, WorkItemData.REASON_READER, "admin");
flowManager.deleteWorkItem( aiid, WorkItemData.REASON_EDITOR, "harish");
System.out.println( "Deleted Work Item");
}

// To work with input & output of Human Task

ClientObjectWrapper input = flowManager.claim( aiid );
DataObject activityInput = null ;
if ( input.getObject()!= null && input.getObject() instanceof DataObject )
{
activityInput = (DataObject)input.getObject();
System.out.println("activity Input:in : "+activityInput.getString("in"));
}

// To Complete
ActivityInstanceData activity = flowManager.getActivityInstance(aiid);
ClientObjectWrapper output = flowManager.createMessage(aiid, activity.getOutputMessageTypeName());
DataObject myMessage = null ;
if ( output.getObject()!= null && output.getObject() instanceof DataObject )
{
myMessage = (DataObject)output.getObject();
myMessage.setString("out","output is this");
}
flowManager.complete(aiid, output);

(WID/WPS) Calling a Business Process using BPE API

2012-03-13T03:54:00.000-07:00

To call a Microflow :
Preferred Interaction style can be Any (Sync/Async/Any)

Join Transaction should be 'True'.

Use call method.
//ClientObjectWrapper cowProcessOut = flowManager.call("MyProcess",cow);

For complete java code :
https://docs.google.com/file/d/0ByotHxAO08TDNnZKX3hfMm5TamlFTW53dk9TQlpMQQ/edit

To call a Long Running Process :
Preferred Interaction style can only be 'Async'.
Join Transaction should be 'False'.
Use initiate method.(PIID piid = flowManager.initiate("MyProcess",cow))

//MyProcess is the process name.

(WID/WPS) Query Tables

2012-03-02T04:31:00.000-08:00

Query tables support task and process list queries on data that is contained in the BPC database schema.This includes human task data and business process data that is managed by BPC, and external business data.

Predefined query tables
Predefined query tables provide access to the data in the BPC database.
They are the query table representation of the corresponding predefined Business Process Choreographer database views, such as the TASK view or the PROCESS_INSTANCE view.

Query tables have the following properties : Name, Attributes, Authorization.

Predefined query tables containing instance data :
TASK
PROCESS_INSTANCE
ACTIVITY
ACTIVITY_ATTRIBUTE
ACTIVITY_SERVICE
ESCALATION
ESCALATION_CPROP
ESCALATION_DESC
PROCESS_ATTRIBUTE
QUERY_PROPERTY
TASK_CPROP
TASK_DESC

Predefined query tables containing template data :
APPLICATION_COMP
ESC_TEMPL
ESC_TEMPL_CPROP
ESC_TEMPL_DESC
PROCESS_TEMPLATE
PROCESS_TEMPL_ATTR
TASK_TEMPL
TASK_TEMPL_CPROP
TASK_TEMPL_DESC

Supplemental query tables
Supplemental query tables in BPC expose to the query table API business data that is not managed by BPC. With supplemental query tables, this external data can be used with data from the predefined query tables when retrieving business process instance information or human task information.

Composite query tables
Composite query tables in BPC comprise predefined query tables and supplemental query tables. They combine data from existing tables or views. Use a composite query table to retrieve the information for a process instance list or task list, such as My To Dos.

Sample code to access all the predefined query tables with its columns & values :

String predefinedTables[] = {

"TASK",
"PROCESS_INSTANCE",
"ACTIVITY",
"ACTIVITY_ATTRIBUTE",
"ACTIVITY_SERVICE",
"ESCALATION",
"ESCALATION_CPROP",
"ESCALATION_DESC",
"PROCESS_ATTRIBUTE",
"QUERY_PROPERTY",
"TASK_CPROP",
"TASK_DESC",
"APPLICATION_COMP",
"ESC_TEMPL",
"ESC_TEMPL_CPROP",
"ESC_TEMPL_DESC",
"PROCESS_TEMPLATE",
"PROCESS_TEMPL_ATTR",
"TASK_TEMPL",
"TASK_TEMPL_CPROP",
"TASK_TEMPL_DESC"
};

Context ctx = new InitialContext();
com.ibm.bpe.api.LocalBusinessFlowManagerHome bfmHome = (LocalBusinessFlowManagerHome)ctx.lookup("local:ejb/com/ibm/bpe/api/BusinessFlowManagerHome");
BusinessFlowManagerService bfmService = bfmHome.create();
for(int counter=0; counter<predefinedTables.length;counter++){
EntityResultSet ers = bfmService.queryEntities(predefinedTables[counter], null, null, null);
if (ers != null) {
com.ibm.bpe.api.EntityInfo ei = ers.getEntityInfo();
java.util.List aiList = ei.getAttributeInfo(); //Gives the list of columns
System.out.println("\n\n");
System.out.println("Query Table Name : "+predefinedTables[counter]);
for (int i = 0; i < aiList.size(); i++) {
com.ibm.bpe.api.AttributeInfo ai = (com.ibm.bpe.api.AttributeInfo) aiList.get(i);
System.out.print( ai.getName() +"\t\t\t\t");
}
System.out.println();
for (int i = 0; i < ers.getEntities().size(); i++) { // loop thru all the rows.
com.ibm.bpe.api.Entity entity = (com.ibm.bpe.api.Entity) ers.getEntities().get(i);
System.out.println();
for (int o = 0; o < aiList.size(); o++) {
com.ibm.bpe.api.AttributeInfo ai = (com.ibm.bpe.api.AttributeInfo) aiList.get(o);
System.out.print("\t\t\t\t");
if (entity.getAttributeValue(ai.getName()) != null) {
if (! ai.isArray()) {
if (ai.getType() == com.ibm.bpe.api.AttributeType.TIMESTAMP) {
System.out.print(((java.util.Calendar) entity.getAttributeValue(ai.getName())).getTime());
} else {
System.out.print(entity.getAttributeValue(ai.getName()));
}
} else {
System.out.print("arrays not supported");
}
} else {
System.out.print("n/a");
}
System.out.print("\t\t\t\t");
}
System.out.println("");
}
}
}

For more info : http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/index.jsp?topic=/com.ibm.websphere.bpc.620.doc/doc/bpc/c6bpel_querytables.html

(WID/WPS) Querying Human Tasks

2012-02-29T04:32:00.000-08:00

This post shows how to query task related information from BPEDB .

To retrieve task instances of a particular task template :

String selectClause = "DISTINCT TASK.TKIID";
String whereClause = "TASK_TEMPL.NAME='RequestTask' AND TASK_TEMPL.NAMESPACE="http://ToDoTask/bpc/samples";
//Add "TASK.STATE = TASK.STATE.STATE_READY" to retrieve only those tasks which are in ready state.
QueryResultSet instances = taskManager.query(selectClause, whereClause, null, null, null, null);

boolean b = instances.first();

b = instances.next();

TKIID tkiid = (TKIID) instances.getOID(1);

Task task = taskManager.getTask(tkiid);

To retrieve all the participating task templates :

String whereClause = "TASK_TEMPL.KIND = TASK_TEMPL.KIND.KIND_PARTICIPATING";
TaskTemplate[] templates = taskManager.queryTaskTemplates(whereClause, null, null, null);
System.out.println( " No of templates :" + templates.length);
System.out.println("***** Displaying TaskTemplateInfo ***** ");
for (int i = 0;i<templates.length;i++){
System.out.println(" Task Template Name :" + templates[i].getName());
System.out.println(" Task NameSpace :" + templates[i].getNamespace());
}

To retrieve all Escalation instances of ready tasks :

QueryResultSet escInstances = taskManager.query("DISTINCT ESCALATION.ESIID, ESCALATION.TKIID","TASK.STATE = TASK.STATE.STATE_READY ",(String)null, (Integer)null, (TimeZone)null );

System.out.println("No of Instances :"+escInstances.size());

boolean b2 = escInstances.first();

b2 = escInstances.next();

ESIID esiid = (ESIID) escInstances.getOID(1);

Escalation esc =  taskManager.getEscalation(esiid);

System.out.println("Escalation Name :"+esc.getName());

System.out.println("DurationUntilEscalated :"+esc.getDurationUntilEscalated());

To retrieve task instances with custom property name/value :

QueryResultSet instances = taskManager.query (" DISTINCT TASK.TKIID, TASK_CPROP.NAME, TASK_CPROP.STRING_VALUE",
"TASK_TEMPL.NAME = 'MyTask'",
String)null, (Integer)null, null );
while(instances.next()){ // looping thru all the rows
TKIID tkiid = (TKIID) instances.getOID(1);
System.out.println("TKIID "+tkiid);
System.out.println(instances.size()); // No of Rows
System.out.println(instances.getColumnDisplayName(1)); // TKIID
System.out.println(instances.getColumnDisplayName(2)); // NAME
System.out.println( instances .getColumnDisplayName(3)); // STRING_VALUE
System.out.println( instances .getString(2)); // Custom Property Name
System.out.println( instances .getString(3)); // Custom Property Value

}

Note : By executing escInstances.next()we shift to the next tuple(Row).

(WID/WPS) Ad-hoc Task Creation

2012-02-28T06:05:00.002-08:00

This post shows the code for creating the ad-hoc task template & task on the fly:

To create the task template :

try{
javax.naming.Context ctx = new javax.naming.InitialContext();
com.ibm.task.api.LocalHumanTaskManagerHome localHumanTaskManagerHome = (com.ibm.task.api.LocalHumanTaskManagerHome)ctx.lookup("local:ejb/com/ibm/task/api/HumanTaskManagerHome");

com.ibm.task.api.LocalHumanTaskManager taskManager = localHumanTaskManagerHome.create();

// Modelling of HumanTask at runtime
// ClientTaskfactory is used to create a resourceset that contains definition for a newly created Task Model

ClientTaskFactory factory = ClientTaskFactory.newInstance();
ResourceSet bundle = factory.createResourceSet();

// load the wsdl definition
Definition definition = factory.loadWSDLDefinition(bundle, "Customer.wsdl");
PortType portType = definition.getPortType(new QName(definition.getTargetNamespace(),"Customer"));
Operation operation = portType.getOperation("info", (String) null, (String) null);

TTask task = factory.createTTask(bundle, TTaskKinds.HTASK_LITERAL, "Ad-hoc-Sample", new UTCDate( "2012-02-28T00:00:00" ), "http://adhoctask", portType, operation);

//Task Name : Ad-hoc-Sample & namespace : http://adhoctask
TaskModel taskModel = ClientTaskFactory.createTaskModel( bundle );

ValidationProblem[] validationProblems = taskModel.validate();

if (validationProblems.length == 0) {
System.out.println("No Validation problems");
TKTID template = taskManager.createTaskTemplate(taskModel, "AccessHumanTask");
//APPLIC_NAME : AccessHumanTask (The Module name)

System.out.println(" Template created ");
}

}catch(Exception e){
e.printStackTrace();
}

Note :

Above code should run once as we can not create the same template more than once.
This template survives server bounce.
Customer.wsdl should be at runtime (Export as jar & keep in server-lib or put in shared lib)

To create the instance of the task :

TKIID tkiid = taskManager.createTask("Ad-hoc-Sample", "http://adhoctask");
ClientObjectWrapper cow = taskManager.createInputMessage(tkiid);
DataObject dataObject = (DataObject) cow.getObject();
dataObject.setString("input","<<Your Input>>");
taskManager.startTask(tkiid, cow, null);

(WID/WPS) Serialization & Deserialization

2012-02-27T01:48:00.000-08:00

This post shows the sample Java code for Serialization & Deserialization.

//String to DataObject (Deserialization)
private DataObject deserialize(String serializedBO)
{
DataObject dataObject = null;
try {
if(serializedBO != null) {
ByteArrayInputStream bais = new ByteArrayInputStream(serializedBO.getBytes());
BufferedInputStream bis = new BufferedInputStream(bais);
BOXMLSerializer serializer = (BOXMLSerializer)ServiceManager.INSTANCE.locateService("com/ibm/websphere/bo/BOXMLSerializer");
dataObject = serializer.readXMLDocument(bis).getDataObject();
bis.close();
}
}
catch (IOException e) {
e.printStackTrace(System.out);
}
return dataObject;
}

//DataObject to String (Serialization)
private String serialize(DataObject dataObject)
{
String serializedBO = null;
if(dataObject != null)
{
try {
ByteArrayOutputStream baos = new ByteArrayOutputStream(1024);
BufferedOutputStream bos = new BufferedOutputStream(baos);
BOXMLSerializer serializer = (BOXMLSerializer)ServiceManager.INSTANCE.locateService("com/ibm/websphere/bo/BOXMLSerializer");
//InputData is the BusinessObject name.
serializer.writeDataObject(dataObject,"http://JMSSampleLibrary/bpc/samples","InputData",bos);
bos.flush();
bos.close();
serializedBO = baos.toString("UTF-8");
}
catch (IOException e) {
e.printStackTrace(System.out);
}
}
return serializedBO;
}

(WMQ) PCF commands Intro

2012-02-24T02:08:00.001-08:00

The purpose of WebSphere® MQ programmable command format (PCF) commands is to allow administration tasks to be programmed into an administration program. In this way, from a program we can manipulate queue manager objects (queues, process definitions, namelists, channels, client connection channels, listeners, services, and authentication information objects), and even manipulate the queue managers themselves.

PCF commands cover the same range of functions provided by MQSC commands. We can write a program to issue PCF commands to any queue manager.

Each PCF command is a data structure that is embedded in the application data part of a WebSphere MQ message. Each command is sent to the target queue manager using the MQI function MQPUT in the same way as any other message. Providing the command server is running on the queue manager receiving the message, the command server interprets it as a command message and runs the command. To get the replies, the application issues an MQGET call and the reply data is returned in another data structure. The application can then process the reply and act accordingly.

Sample Java code for creating local queues :

Imports are :

import com.ibm.mq.MQC;

import com.ibm.mq.MQMessage;

import com.ibm.mq.MQQueueManager;

import com.ibm.mq.constants.CMQC;

import com.ibm.mq.constants.CMQCFC;

import com.ibm.mq.headers.pcf.MQCFIN;

import com.ibm.mq.headers.pcf.MQCFST;

import com.ibm.mq.headers.pcf.PCFAgent;

import com.ibm.mq.headers.pcf.PCFParameter;

import com.ibm.mq.pcf.MQCFH;

import com.ibm.mq.pcf.MQCFSL;

private static void createQueues(String[] queues)throws Exception {

MQQueueManager qMgr;

qMgr = new MQQueueManager("QM");

PCFAgent agent = new PCFAgent (qMgr);

MQMessage [] responses;

int queueCounter =0;

for(;queueCounter<queues.length;queueCounter++)

{

PCFParameter [] parameters =

{

new MQCFST (CMQC.MQCA_Q_NAME, queues[queueCounter]),

new MQCFIN (CMQC.MQIA_Q_TYPE, MQC.MQQT_LOCAL)

};

MQCFH cfh;

responses = agent.send (CMQCFC.MQCMD_CREATE_Q, parameters);

cfh = new MQCFH (responses [0]);

if(cfh.reason==4001)

System.out.println("Queue Name : "+queues[queueCounter] +" is already present");

else if(cfh.reason==0)

System.out.println("Queue Name : "+queues[queueCounter] +" is created");

}

Sample Java code for displaying all the local queues in queue manager:

private static void getQueueNames() throws Exception {

MQQueueManager qMgr;

qMgr = new MQQueueManager("QM");

PCFAgent agent = new PCFAgent (qMgr);

MQMessage [] responses;

PCFParameter [] parameters =

{

new MQCFST (CMQC.MQCA_Q_NAME, "*"),

new MQCFIN (CMQC.MQIA_Q_TYPE, MQC.MQQT_LOCAL)

};

MQCFH cfh;

MQCFSL cfsl;

responses = agent.send (CMQCFC.MQCMD_INQUIRE_Q_NAMES, parameters);

cfh = new MQCFH (responses [0]);

if (cfh.reason == 0)

{

cfsl = new MQCFSL (responses [0]);

for (int i = 0; i < cfsl.strings.length; i++)

{

System.out.println ("Queue: " + cfsl.strings [i]);

}

}

Jars required :

com.ibm.mq.headers.jar
com.ibm.mq.jar
com.ibm.mq.jmqi.jar
com.ibm.mq.pcf.jar

For more info : http://publibfp.dhe.ibm.com/epubs/pdf/csqzac05.pdf