deploying DFS on Websphere 6.1

Deploying the DFS 6.5 SDK samples in websphere 6.1 is not straight forward. The OOTB build file will generate the .ear file, websphere dosent seem to like this .ear file. I will address the two issues(and solutions) I ran into while deploying this ear file in Websphere 6.1.

1. The META-INF/application.xml file generated by the emc defined ant task 'packageservice' does not have the right namespace definitions. When deploying the .ear file, websphere will complain about this right off the bat.

The 'application' tag generated by the emc ant task will look like this(without the <>)
application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4"

Change the above tag alone to the following(make sure to add <> at the start and end respectively)
application id="Example_ID" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"

IZarc provides a nice feature for editing a file(in this case application.xml) inside the ear file while preserving the folder path.

2. The ant target 'package' seem to add duplicate jar files in APP-INF/lib the file that is getting duplicated is 'emc-dfs-rt.jar'. This can be fixed by removing the following line from the build.xml file and rebuilding it(again without <>).

pathelement location="${dfs.sdk.libs}/emc-dfs-rt.jar'"/