Did you enable the model? If not, try that. (Look at the generated trigger to be sure that it is enabled).
If you did try that, check the ENABLED column in WMPROCESSDEFINITION table as arydewo suggested and make sure it is 1. If it is not 1, then you can try updating it to 1 and then running pub.prt.admin:scanPackage.
As for your 6.5 issue - the day that 6.5 was GA’d I tried installing it and there were numerous issues with the database scripts some relating to PRT tables. I ended up using some of the scripts from 6.1 to get things up and running. I have not since tried the scripts, so can’t say for sure if there are any issues remaining that may be affecting you.
If all else fails, you might want to:
- Delete the generated model package
- Run pub.prt.admin:scanPackage
- Remove the model definition from the database by running the following SQL:
[INDENT]
--remove custom field definitions
delete
from WMPROCESSMP.WMCUSTOMFIELDDEFINITION cust
where
cust.PROCESSKEY = '???';
--remove step transition definitions
delete
from WMPROCESSMP.WMSTEPTRANSITIONDEFINITION trans
where
trans.PROCESSKEY = '???';
--remove model step definitions
delete
from WMPROCESSMP.WMSTEPDEFINITION step
where
step.PROCESSKEY = '???';
--remove model definition
delete
from WMPROCESSMP.WMPROCESSDEFINITION proc
where
proc.PROCESSKEY = '???';
--commit the changes
commit;
You will, of course, need to substitute the ??? with the PROCESSKEY of your model (which you can find in Modeler or in the WMPROCESSDEFINITION table).
[/INDENT]–jeff
#webMethods#BPM#webMethods-BPMS