Composer 6.5 SP2 - Cannot install Workflow Template

I am getting an error when I install a Workflow Template from Composer 6.5 and I hope that someone will be able to assist with this issue.

I created a new Workflow Template in Workflow Manger and then imported it into a new project.

Currently this project contains the Workflow Template and its associated type, groups and roles.

For the type, groups and roles I selected the Upgrade option to be "Ignore Matching Objects", because all of these already exists in the repository.

The Upgrade option for the Process Template is: Overwrite Matching Objects.

This is a new process that has not been installed yet.

When I try to install this project I get the following error:

------------------------------------------------------------------------------------------------------------------------

[INFO] Executing post-install actions

[ERROR] Unexpected error occured during install

com.emc.ide.installer.PostInstallDelegateActionException: java.lang.NullPointerException

at com.emc.ide.artifact.bpm.installer.ActivityInstaller.doPostInstall(ActivityInstaller.java:281)

at internal.com.emc.ide.installer.DarInstaller.executeAllPostInstallActions(DarInstaller.java:1309)

at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:586)

at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:330)

at internal.com.emc.ide.installer.DarInstaller.doInstall(DarInstaller.java:301)

at com.emc.ide.installer.popup.actions.RunDARInstallerActionDelegate$2.run(RunDARInstallerActionDelegate.java:425)

at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

Caused by: java.lang.NullPointerException

at com.emc.ide.artifact.bpm.installer.ActivityInstaller.doPostInstall(ActivityInstaller.java:215)

... 6 more

[INFO] Restored Auto Build [Current Setting is ON]...

[INFO] Reseting installer Wed Feb 24 04:03:04 CAT 2010

[INFO] ECW3_Submissions install failed

------------------------------------------------------------------------------------------------------------------------

1) The referenced JRE System Library is jre 1.5.0_17.

2) I've tried installing the DAR using the Headless Composer; the same error occurred.

3) I created a new project on another PC and imported the workflow template from the repository.

I then installed this project on a different repository and the same error occurred.

4) If I only have the type in a project then it installs successfully.

5) This workflow has a number of auto-steps that are calling the dm_noop_auto_method_java method.

I noticed that this method was imported in the project.

I then changed the method from dm_noop_auto_method_java to dm_noop_auto_method on each auto step in the workflow

I created a new project and imported the updated workflow

When I installed the same error occurred again.

dctm_tools_2706984723097260382.log

Find more posts tagged with

Comments

Francois Dauberlieu

Did you try to install the workflow prior to importing it in a Composer project and installing the project ? just to see what happens...

ZeldaK

Hi,

Thanks for the suggestion, I tried it out but also no success.

I also changed the update options to see if that would make a difference.

What is interesting though is that I am able to install a very basic workflow.

So I am now rebuilding my workflow step-by-step to see if I can find the cause and installing it as I go along.

Francois Dauberlieu

That was going to be my next suggestion....

Let us kow how it goes

afitzpat

Hi,

Have you managed to find a fix for this problem? I am experiencing exactly the same error and have previously followed the same resolution steps you have. the only other thing I tried, which you have not mentioned, is to update the locations of each step of the workflow so that they are placed in the same folder as they were created in as as the default is to install the workflow to /System/Application/<DAR Project>.

Andrew

ZeldaK

Hi,

I tested a little bit and it seems that if I have a reject path to another task and both tasks have a "repeat" and "delegate" activated it causes issues.

Removing the "repeat" and "delegate" functions did not fix the issue.

I actually had to remove the task.

I unfortunately did not have enough time to properly investigate this issue or log a call with EMC.

I suspect there might be some bug.

I imported my workflow in Documentum Application Builder and created a docapp.

The docapp worked perfectly.

Good luck and if you do find the problem please will you let me know.

I'll also do some more investigation into this issue soon.

Regards,

Zelda

Swapna_Patro

There is a hotfix for composer 6.5 SP2 released on jan 11 which might solve this issue.

i suspect your problem might related to this bug.

CMPSR-1461: DAR creation of Workflow Templates and Work Queues succeeds, but the installation of the DAR to a 6.5 SP2 repository fails with a Java Null Pointer Exception

Thanks,

Swapna

Francois Dauberlieu

Can you let us know the Hot Fix Number, or even better if you still have it, the URL to get to it in PowerLink ?

Swapna_Patro

Sorry i donot have hotfix number. In that hotfix, no number has been mentioned.

i found it from subscribenet by searcing Composer...

Thanks,

Swapn

afitzpat

All,

I have been doing some digging and the bug detailed by Swapn is present in the ComposerHotfix.zip which is available from powerlink, I couldn't copy a link but to find it go to the Documentum download area, click Partner Packages> Documentum Composer> Documentum Composer SP2 and the file is in there.

I've also been stepping through my workflow and adding functionality to a copy workflow and installing into a different docbase. Of all the functionality I have used it appears to be the Timers on the Notification tab that cause the NullPointerException. If I set both of these I get the error on install, if I untick both of the timers I don't get the error on install.

Hope this helps, thank you all for answering.

Andrew

Imran_Yusubov

Hi,

could you solve the problem? I am getting the smae error.

jsilver

I've moved this discussion to the Documentum Developer Community, where it is more likely to be seen by other Documentum experts. The Documentum Connect Community is not the place for this type of discussion.