Using secured DFS in Dynamic Web Service Activity

Deploying DFS on a seperate app server in SSL mode
1. Deploy emc-dfs.ear on the weblogic server.
2. generate self signed cert using keytool

keytool -genkey -alias webtopcert -keypass webtopcert -keystore webtopcert.bin -storepass webtopcert

3. copy webtopcert.bin generated in the above step to WL_HOME\server\lib
4. Configure the weblogic server to work in SSL mode at Environment->Server->Admin Server
5. On Configuration->General tab enable https.6. On the Configuration->Keystore tab add the keystore and identity. Point botht he trust and identity the webtopcert.bin created in step 1. and add 'webtopcert' without quotes as the password.7. On the Configuration->SSL tab fill in the alias and pass phrase
8. Activate changes and try the URL
https://hostname:7002/services/core/ObjectService. Make sure the hostname is same as the CN provided when creating the cert.

Exporting cert from IE and importing it to process builder and JMS
9. Export the certificate from the DFS site through IE.



10. Copy this .cer file to the machine where Process Builder and Java Method Server is installed and running.

11. Import the certificate generated from IE in the above step to the process builder JDK in C:\Program Files\Documentum\java\1.5.0_12\jre\lib\security using the following command.

C:\Program Files\Documentum\java\1.5.0_12\jre\lib\security>"C:\Program Files\Jav
a\jdk1.6.0_10\bin\keytool" -import -keystore cacerts -storepass changeit -alias webtopcert -file webtopcert.cer

12 Import the same certificate in the JDK for the Java Method server as well at
C:\Documentum\jboss4.2.0\jdk\jre\lib\security using the same command.

13. Verify the cert is added to the keystore using the following command
"C:\Program Files\Java\jdk1.6.0_10\bin\keytool" -list -keystore cacerts -storepass changeit

14. Restart the JMS and Process Builder.

Connecting DWS to secured DFS
15. Create a Dynamic Web Service activity in any workflow, go to the 'Web Service Configuration' tab of the Dynamic Web Service Activity's Activity Inspector and add the https URL in the 'URL path to WSDL file' field and hit the 'Read WSDL FIle' button. The 'Port Type' and 'Operatrion' drop downs should get populated.

You have now connected a Dynamic Web Service Activity with a secured DFS successfully!

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'"/