HttpPostToBoDataHandler.java

/*
* Author: Sudarsan Manickam
* Description: This Data handler is for converting a HTTP/POST parameter message into a BO message and send it to the SCA component
* Date: 20th September 2010
*
*/

import java.io.ByteArrayOutputStream;
import java.io.IOException;
import java.io.InputStream;
import java.io.Reader;
import java.io.UnsupportedEncodingException;
import java.net.URLDecoder;
import java.util.List;
import java.util.Map;

import javax.xml.namespace.QName;

import com.ibm.websphere.bo.BOFactory;
import com.ibm.websphere.sca.ServiceManager;
import com.ibm.ws.bo.bomodel.util.BOPropertyImpl;

import commonj.connector.runtime.BindingContext;
import commonj.connector.runtime.DataHandler;
import commonj.connector.runtime.DataHandlerException;
import commonj.sdo.DataObject;

@SuppressWarnings(“serial”)
public class HttpPostToBoDataHandler implements DataHandler{ private ServiceManager serviceManager;
private BOFactory boFactory;
private String encoding;
private String exclusionList;
private boolean caseSensitive;
private String targetNamespace;
private String localName;
private char listSeparator;

public HttpPostToBoDataHandler()
{
serviceManager = ServiceManager.INSTANCE;
boFactory = (BOFactory)serviceManager.locateService
(“com/ibm/websphere/bo/BOFactory”);

encoding = “UTF-8″;
}

public Object transform(Object source, Class target, Object options) throws DataHandlerException
{
//This transforms our source message into the target message System.out.println(“HttpPostToBoDataHandler”, “transform”, “Start of transformation”);

if ((source == null) || (target == null)){
return null;
}
// native data format to DataObject transformations
if (target == String.class) {
if (source instanceof InputStream)
{
System.out.println(“HttpPostToBoDataHandler”,
“transform”, “source and target is String and InputStream respectively”); // Transform InputStream to DataObject
InputStream inputstream = (InputStream)source;

byte[] bytes = readBytes(inputstream);
try
{
if (bytes.length > 0)
{
System.out.println
(“HttpPostToBoDataHandler”, “transform”, “Parsing input parameters”); String parms = new String(bytes, 0,
bytes.length, encoding);
System.out.println
(“HttpPostToBoDataHandler”, “transform”, “Parameters: ” + parms);

return createBusinessObject(parms);
}
}
catch (UnsupportedEncodingException e) {
System.out.println(“HttpPostToBoDataHandler – transform”, e);

}
}
else if (source instanceof Reader) {
// Transform Reader to DataObject
// we dont have to implement this for our
requirement
}
else {
// Transform Object to DataObject
// we dont have to implement this for our
requirement
}
}

if (target == DataObject.class) {
if (source instanceof InputStream)
{
System.out.println(“HttpPostToBoDataHandler”,
“transform”, “source and target is InputStream and DataObject respectively”);
// Transform InputStream to DataObject
InputStream inputstream = (InputStream)source;

byte[] bytes = readBytes(inputstream);
try
{
if (bytes.length > 0)
{
System.out.println
(“HttpPostToBoDataHandler”, “transform”, “Parsing input parameters”); String parms = new String(bytes, 0,
bytes.length, encoding);
System.out.println
(“HttpPostToBoDataHandler”, “transform”, “Parameters: ” + parms);

return createBusinessObject(parms);
}
}
catch (UnsupportedEncodingException e) {
System.out.println(“HttpPostToBoDataHandler – transform”, e);
}
}
else if (source instanceof Reader) {
// Transform Reader to DataObject
// we dont need to implement this for our
requirement
}
else {
// Transform Object to DataObject
// we dont need to implement this for our
requirement
}
}

// DataObject to native data format transformations if (source instanceof DataObject) {
if (target == InputStream.class) {
System.out.println(“HttpPostToBoDataHandler”,
“transform”, “source and target is DataObject and InputStream respectively”);
// Transform DataObject to InputStream
// we dont need to implement this for our
requirement
}
else {
// Transform DataObject to Object
// we dont need to implement this for our
requirement
}
}
throw new DataHandlerException(“Transformation not
supported”);
}

private DataObject createBusinessObject(String s) throws
DataHandlerException
{
System.out.println(“HttpPostToBoDataHandler”, “createBusinessObject”, “Creating a business object from string “+targetNamespace+” localName “+localName);
DataObject dataobject = boFactory.create(targetNamespace, localName); if(dataobject == null)
dataobject = boFactory.createByElement(targetNamespace, localName);

//Populating the business object with parameters from the string //Split the incoming parameters into individual tokens
String[] parms = s.trim().split(“&”);

for (int i=0; i < parms.length; i ++)
{
//Find next parameter name
String parmName = parms[i].substring(0, parms[i].indexOf(“=”)); if (parms[i].indexOf(parmName) != -1)
{
String updatedName = includeParameter(dataobject,
parmName);
if (updatedName != null)
{
try
{
//If parameter needs to be included then
String value = parms[i].substring(parms
[i].indexOf(“=”) + 1);
value = URLDecoder.decode(value, encoding);
dataobject.setString(updatedName, value);
} catch (UnsupportedEncodingException e) {
System.out.println
(“HttpPostToBoDataHandler – transform”, e);
}

}
}
}
return dataobject;
}

private String includeParameter(DataObject object , String name) {
//Find if we need to exclude some of the strings (in the given example we need to exclude parameters with the names ‘operation’ and ‘user’)
String[] excludedParms = exclusionList.split(String.valueOf (listSeparator));

//Check if the parameter is in the exclusion list
boolean exclude = false;
for (int j=0; j < excludedParms.length; j++)
{
if ((caseSensitive && name.equals(excludedParms[j])) ||
(!caseSensitive && name.equalsIgnoreCase
(excludedParms[j])))
{
return null;
}
}

//If the parameter does not need to get excluded then return the name to be set on the BO
if (caseSensitive && object.getInstanceProperty(name) !=
null)
return name;
else if (!caseSensitive)
{
List props = object.getInstanceProperties();
for (int n=0; n

psft.pt8.joa.JOAException: Distributed Object Manager: User ID=H_MGR1_EID Query=%2 (1,16)

User ID=H_MGR1_EID is specific to the sample CI that i used for testing, so ignore that. If you see any exception similar like this, then the reason would be because of the CI remote object is not properly instantiated at PeS end.

Hence try executing the get method of the CI like oHMdaGeitCrrUpdCi.get() which will instantiate the CI object in the PeS.

Hope this would help in your debugging.

Thanks,

Sudan

Please note this is not for beginners in Java

1. Java Identifiers can be of any length.
2. A java file can have many classes inside it. If it has a public class then the name of it should match the file name.
3. A java file can have only one public class and can have more than one public class.
4. A class with default access can be seen only by classes within the same package.
5. A class with public access can be seen by all classes from all packages.
6. An abstract class can have both abstract and non abstract methods.
7. The first concrete class to extend an abstract class must implement all of its abstract methods.
8. Interfaces are contracts for what a class can do, but they say nothing about the way in which the class must do it.
9. An interface can have only abstract methods, no concrete methods allowed.
10. Interfaces can have constants, which are always implicitly public, static, and final.
11. A legal non abstract implementing class has the following properties:
    1. It must not declare any new checked exceptions for an implementation method.
    2. It must not declare any checked exceptions that are broader than the exceptions declared in the interface method.
    3. It may declare runtime exceptions on any interface method implementation regardless of the interface declaration.

Make a class immutable by following these guidelines :

• ensure the class cannot be overridden – make the class final, or use static factories and keep constructors private
• make fields private and final
• force callers to construct an object completely in a single step, instead of using a no-argument constructor combined with subsequent calls to setXXX methods (that is, avoid the Java Beans convention)
• do not provide any methods which can change the state of the object in any way – not just setXXX methods, but any method which can change state
• if the class has any mutable object fields, then they must be defensively copied when passed between the class and its caller

public interface Hello {

public Hello(){};

}

• Most of them time when we work with Currencies, there might be a necessity of doing arithmetic operations. So, we use double as a data type for storing the decimal values.

eg:

double f = 0.05;

double f1 = 0.35;

System.out.println(f+f1);

output:

0.39999999999999997

So, the above output gives lots of problems. This is because of the 64 bit precision of Double. To solve this use the below code

double f = 0.05;

double f1 = 0.35;

NumberFormat nf = NumberFormat.getInstance();

nf.setMaximumFractionDigits(2);

System.out.println(nf.format(f+f1));

Output:

0.4

• A singleton is an class that can be instantiated once, and only once. This is a fairly unique property, but useful in a wide range of object designs. Creating an implementation of the singleton pattern is fairly straightforward – simple block off access to all constructors, provide a static method for getting an instance of the singleton, and prevent cloning.

public class SingletonObject
{

//It is declared private, just to ensure that no one outside this class calls this constructor. Which also means no one outside this class can instantiate this class
private SingletonObject()
{
// no code req’d
}

//It is made static, so that the caller can call this method without instantiating this class. It is synchronized to avoid the multiple calls by thread at the same time.
public static synchronized SingletonObject getSingletonObject()
{
if (ref == null)
// it’s ok, we can call this constructor
ref = new SingletonObject();
return ref;
}

//This is just to override the Object clone or any other super class that this singleton class might extend.
public Object clone()
throws CloneNotSupportedException
{
throw new CloneNotSupportedException();
// that’ll teach ‘em
}

private static SingletonObject ref;
}

what is Factory methods?

Factory methods are static methods that return an instance of the native class.

public class ComplexNumber {

/**
* Static factory method returns an object of this class.
*/
public static ComplexNumber valueOf(float aReal, float aImaginary) {
return new ComplexNumber(aReal, aImaginary);
}

/**
* Caller cannot see this private constructor.
*
* The only way to build a ComplexNumber is by calling the static
* factory method.
*/
private ComplexNumber (float aReal, float aImaginary) {
fReal = aReal;
fImaginary = aImaginary;
}

private float fReal;
private float fImaginary;

//..elided
}

The below code will describe how to do it.

DateFormat df = new SimpleDateFormat(“yyyy-MM-dd HH:mm:ss.S”);
Date dobDate;
try {
dobDate = df.parse(“1985-08-30 00:00:00.0″);
if (dobDate != null){
DateFormat dobFormat = new java.text.SimpleDateFormat(“dd-MMM-yyyy”);

//Please note that in above format “MMM” is in caps. This is to print the month in alphabets
System.out.println(dobFormat.format(dobDate));
}
} catch (ParseException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}

Thanks,

-Sudan

Today when i was working on my eclipse for some reason suddenly it got crashed and it didnt opened. I was working on lots of my POC projects in it. Now i forgot all of the projects and different workspace path. I tried searching the eclipse extract folder to find my workspace path. Finally after a big search i got the file where this is stored.

I thought i would share the file name where this data would be stored in the eclipse.

File name: eclipse\configuration\.settings\org.eclipse.ui.ide.prefs

The data in this file would be something like below(for me)

#Mon Mar 01 15:34:44 IST 2010
RECENT_WORKSPACES_PROTOCOL=3
MAX_RECENT_WORKSPACES=5
SHOW_WORKSPACE_SELECTION_DIALOG=true
eclipse.preferences.version=1
RECENT_WORKSPACES=D\:\\OpenBPEL\nD\:\\MDAServerTest\nD\:\\MDA\\automations\\eclipse_workspace\nD\:\\SMSFinal\nD\:\\SMS1

Guess this would help.

-Sudan

Today I would like to explain the POC that I was trying last week. Generally for connecting to PeS we have three ways as below

1. File Layout
2. Web Services Application Messaging
3. Component Interface

File Layout:

This is used to connect to PeS when we need file based polling integration. Generally the type of file used would be xml or csv’s. This method is still very popularly used in many applications.

Web Services Application Messaging:

This is a plain Web Service communication. Messaging architecture for both synchronous and guaranteed delivery asynchronous integration into and out of the Integration Broker

Component Interface:

This is Object-oriented, request/reply, component architecture that encapsulates PeopleSoft data and communicates.

I am interested in using Component Interface for PeS connectivity. Generally in market lots of adapters are available for doing this. The leaders are Oracle and IBM, they provide adapters for connecting to PeS. So, the developer doesnt have to code or worry about the PeS connectivity, they just need to send the data and get back the data they need. This makes life simple for developers

I have used IBM adapter in Websphere process server for PeopleSoft. The advantage i could see using is just easy development. But is it worth paying huge money for just getting this advantage. Why cant we develop our own component in process server which does this functionality.

The other advantage that adapter give is that we can discover the CI available in the PeS and just use the operation we want. All these things can be done using a good UI wizard. When we go for our own java implementations, we have to open each CI and create a java template for each.

We will go step by step tutorial for doing this.

PSJOA.jar -> This is the interface jar file which would help Java to interact with PeopleSoft through a component interface. It will be available in %PS_HOME%\class directory.

Create a record with a single field and put this on a page. Create a component and move it to a component interface. The component interface should have the following methods :- Cancel, Create, Find, Get and Save.

Now, open the component interface. Click on Build -> PeopleSoft APIs. This process would validate all the component interface and you will get some errors in this process. You can just skip the errors and continue the process. Select the “java” class option and specify the target location where the java files needs to be placed. For any component interface, PeopleSoft create four files like for CI name JobData, it would create

IJobDataCI.java

IJobDataCICollection.java

JobDataCI.java

JobDataCICollection.java

So, after compiling this, pack all the class files into a jar file, say PSFTCI.jar. So, now we have two jar’s PSJOA.jar and PSFTCI.jar

The next step is to create a java template. Open the component Interface, right click and click on generate a Java template. So, this would be saving your java template for that CI in some temp folder. Generally the Java template name would be the CI name itself, say JobDataCI.java

Now if we open the java template, we can see a code like

“oSession.connect(1, strAppServerPath, strOperatorID, strPassword, null)”

Here we can give the server name, username and password for the PeS we are trying to connect. This would take the default port. If we need to modify this port number to some specific value and have all these data coming from properties fil, we need to follow the below steps.

1. change the above code to “oSession.connect(1, strAppServerPath, strOperatorID, strPassword, null)”
2. create a property file pstools.properties in the java project with the following key names

server_port=<server_port>
server_name=<server_name>
logon_id=<logon_id>
logon_password=<logon_password>

That’s it, we are done. Just need to use the setter and getter methods in the java template to select or update the date in PeS.

This finishes the tutorial for connecting to PeS through java.

-Sudan

There would be some case, where we dont have access to the admin console, but have only access to the logs. In this case how can we find the HTTP and HTTPS port for default and admin.

To find the ports using Admin Console:

start the server, go to Servers->Application servers > server1 > Ports, scroll down to see the screenshot below

WC admin host: HTTP port for admin console

WC admin host secure: HTTPS port for admin console

WC defaulthost: HTTP port for default host

WC defaulthost secure: HTTPS port for default host

To find the ports using the System out logs:

Search for the below sentence in the logs

“Web Module WebSphere Admin File Transfer Application has been bound to admin_host” -  [*:HTTP,*:HTTPS]. This is for the admin HTTP and HTTPS ports

“Web Module Default Web Application has been bound to default_host” – [*:HTTP,*:80,*:HTTPS]. This is for the default HTTP and HTTPS ports

-Sudan

I was trying to do a file upload using jsp from a client to  server. For this when i searched the net, i got many code, at last i managed to edit one such code and customized it to my requirement. Here is the below code snippet of the form, which is used to upload a file.

File Name: FileUploadForm.jsp

<FORM ENCTYPE=”multipart/form-data” METHOD=”post” name=”main” action=”FileUploadAction.jsp”>
<br>
<tr>
<td align=”right”><b>Choose the file To Upload:</b></td>
<td><INPUT NAME=”F1″ TYPE=”file”></td>
</tr>
<tr>
<td>&nbsp;</td>
<td>
<INPUT TYPE=”button” VALUE=”Upload” onclick=uploadFile()>
</td>
</tr>
</FORM>

Below scriplet is the code of other file which does the file upload action to the server

File Name: FileUploadAction.jsp
<%
//to get the content type information from JSP Request Header
String contentType = request.getContentType();
//here we are checking the content type is not equal to Null and as well as the passed data from mulitpart/form-data is greater than or equal to 0
if ((contentType != null) && (contentType.indexOf(“multipart/form-data”) >= 0)) {
DataInputStream in = new DataInputStream(request.getInputStream());
//we are taking the length of Content type data
int formDataLength = request.getContentLength();
byte dataBytes[] = new byte[formDataLength];
int byteRead = 0;
int totalBytesRead = 0;
//this loop converting the uploaded file into byte code
while (totalBytesRead < formDataLength) {
byteRead = in.read(dataBytes, totalBytesRead, formDataLength);
totalBytesRead += byteRead;
}
String file = new String(dataBytes);
//for saving the file name
String saveFile = file.substring(file.indexOf(“filename=\”") + 10);
saveFile = saveFile.substring(0, saveFile.indexOf(“\n”));
saveFile = saveFile.substring(saveFile.lastIndexOf(“\\”) + 1,saveFile.indexOf(“\”"));

String timestamp = new SimpleDateFormat(“yyyy.MM.dd.HH.mm.ss.S.”).format(new Date());
saveFile = userId+timestamp+saveFile;
int lastIndex = contentType.lastIndexOf(“=”);
String boundary = contentType.substring(lastIndex + 1,contentType.length());
int pos;
//extracting the index of file
pos = file.indexOf(“filename=\”");
pos = file.indexOf(“\n”, pos) + 1;
pos = file.indexOf(“\n”, pos) + 1;
pos = file.indexOf(“\n”, pos) + 1;

int boundaryLocation = file.indexOf(boundary, pos) – 4;
int startPos = ((file.substring(0, pos)).getBytes()).length;
int endPos = ((file.substring(0, boundaryLocation)).getBytes()).length;

// creating a new file with the same name and writing the content in new file
String fileName = request.getRealPath(“”)+”\\excelFiles\\”+saveFile;
FileOutputStream fileOut = new FileOutputStream(fileName);
fileOut.write(dataBytes, startPos, (endPos – startPos));
fileOut.flush();
fileOut.close();

%>

But there is a serious problem in the above code, it works fine in the windows, whereas in linux machines this code fails. When i went through the everyline of the code, the line of code which gives different output in linux is,

String file = new String(dataBytes);
The above line is used to convert the file data in bytes to String. The reason we are doing is to find the boundary location of the file, now lets dont go deep in to this, this is more about file parsing formats. You can read the RFC which explains about the formats and parsing the file data from a HTML. But the strange that i could see in the above line is for the same file uploaded the String variable file length varies in windows server and linux server. I am not able to imaging the reason behind this.

After a long fight with the code and searching in the internet, i happen to see the apache commons api’s. This api is really cool and interesting. It does all the things that is required for parsing and reduces our load. FileUploadForm.jsp can be used the same. But i changes the code of FileUploadAction.jsp. Below is the code

File Name: FileUploadAction.jsp

<%@ page import=”java.text.SimpleDateFormat” %>
<%@ page import=”org.apache.commons.fileupload.FileItem” %>
<%@ page import=”org.apache.commons.fileupload.FileUploadException” %>
<%@ page import=”org.apache.commons.fileupload.disk.DiskFileItemFactory” %>
<%@ page import=”org.apache.commons.fileupload.servlet.ServletFileUpload” %>

<%@ page import=”java.io.*” %>
<%@ page import=”java.util.*” %>
<%

if (ServletFileUpload.isMultipartContent(request)){
ServletFileUpload servletFileUpload = new ServletFileUpload(new DiskFileItemFactory());
List fileItemsList = null;
try {
fileItemsList = servletFileUpload.parseRequest(request);
} catch (FileUploadException e) {
System.err.println(“inside uploadUpdateACtion while parsing Exception is ["+e.getMessage()+"]“);
}

Iterator i = fileItemsList.iterator();
//String comment = ((FileItem)i.next()).getString();
FileItem fi = (FileItem)i.next();
// filename on the client
String fileName = fi.getName();

fileName = fileName.substring(fileName.lastIndexOf(“\\”)+1);

String timestamp = new SimpleDateFormat(“yyyy.MM.dd.HH.mm.ss.S.”).format(new Date());
String saveFile = userId+timestamp+fileName;
// write the file
try {
fi.write(new File(request.getRealPath(“”)+”/excelFiles”, saveFile));
} catch (Exception e) {
System.err.println(“inside uploadUpdateACtion while writing the uploded file Exception is ["+e.getMessage()+"]“);
}

%>

For the above code to work we need two jars to be included in the classpath commons-fileupload-1.2.1.jar and commons-io-1.4.jar. Both the jars are available in the apache site. This code will work for all environments and platforms. It has lot of features to be explored by me.
Thanks for reading, Have a great day !!!!!!!!!!!!!!!!!!!!!!!!!!!

-Sudan