Forte / Conductor not deploying the Conductor libraries tothe clients

Question

Good day!
We have a Forte 3.0.L.2 (NT) server for development, as well as a 3.0.L.2
(Unix) server for development and one for deployment. The developers code
in the NT environment, then we export the workspace to Unix. Recently we've
added Conductor (1.0.L.1) and WebEnterprise (1.0.D.1). All was working
fine, until I renamed the environment on the Unix development environment.
Previously, when clients pulled deployments, they would receive the
Conductor-related libraries, but now (after the environment name change) the
"wfclient" library no longer comes over with the deployment, as it used to.
I've rebuilt the environment (recreated via nodemgr and rebuilt the node
templates, as well as reinstalling it all back) but this didn't take care of
the problem. Forte states we need to install the Conductor client on the
client machines. However, our other three environments will still deploy
the "wfclient" and other conductor-related libraries to the clients. Do you
have any information on this behavior?
thanks in advance,
Sean Boone

Answer 1

Hi,
I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
Regards,
Sylvain