Why downloaded bof jar files doesn't get extension executable jar?

Hi Team

I have following jar files ( BOF Modules ) when it downloaded to the bof folder it gets extension like .dataservice, .approle and so on… rather than executable jar file which causes Class not found exception in bpm run time logs.

Has anyone seen this issue?

How to resolve this issue.

I have this issue after applying patch 05 for PE.

Find more posts tagged with

Documentum

Comments

stephanemarcon

hi Pinal, You semm to get the correct .jar extension but your os seems to be configured in such a way is doesn't display them. You certainly have the "hide extension for known file types" enabled in windows. Look at the second column, it says "Java Archive File (.jar)". Regards, Stephane

shahp

Hi Marcon

Thanks for the response. That's what I thought initially but that is not the case. I tried to uncheck hide extension but no difference.

This time I restarted JMS by pointing it to C:\Documentum\config\dfc.properties file and it worked.

I am still getting error below but I can see jar file under bpm.ear\lib as well as under bof cache folder.

Not sure why it's throwing this error after I deploy PE 7.0 P05

013-05-28 20:22:32,836 ERROR [http-0.0.0.0-9080-2] [com.documentum.bpm.services.BPSIntegrationMethod] - Could not initialize class com.emc.xcp.model.approle.AppRolePackage in Process Template: 'pinalsimpleprocess' - Activity: 'Set Process Data'.

Workitem: '4aab630c80002d13'

Workflow: 'pinalsimpleprocess 2013-05-28' - '4dab630c80002900'

Activity: 'Set Process Data' - '4cab630c800ae51a'

Process: 'pinalsimpleprocess' - '4bab630c800ae50e'

java.lang.NoClassDefFoundError: Could not initialize class com.emc.xcp.model.approle.AppRolePackage

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:169)

at com.emc.xcp.artifactmanager.internal.runtime.RuntimeArtifactManagerDependencies.getPackageClass(RuntimeArtifactManagerDependencies.java:164)

fainemr

Add .jar to the name of your jar definitions. This is how I worked around this problem.