Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
361 views

Rename workflow engine-id?

Hello
Is it possible to rename a cluster engine-id? If so, how?

Thanks
Labels (1)
0 Likes
2 Replies
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: Rename workflow engine-id?

Presumably on JBoss... I believe this only exists in the startup script
(start-jboss.sh or something) for JBoss, for example:


exec /opt/novell/idm/jboss/bin/run.sh -Djboss.service.binding.set=ports-01
-c IDMProv -b 0.0.0.0 -Dcom.novell.afw.wf.engine-id=IDMPRODUA0 ....


As long as they are consistent you should be fine, or at least I never
noticed any issues when changing them in the past. In case it is not
obvious, be sure they're unique per cluster, just like your multicast
connection information, to avoid mixing prod/non-prod setups.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Rename workflow engine-id?

On 07/30/2015 10:14 AM, ab wrote:
> Presumably on JBoss... I believe this only exists in the startup script
> (start-jboss.sh or something) for JBoss, for example:
>
>
> exec /opt/novell/idm/jboss/bin/run.sh -Djboss.service.binding.set=ports-01
> -c IDMProv -b 0.0.0.0 -Dcom.novell.afw.wf.engine-id=IDMPRODUA0 ....
>
>
> As long as they are consistent you should be fine, or at least I never
> noticed any issues when changing them in the past. In case it is not
> obvious, be sure they're unique per cluster, just like your multicast
> connection information, to avoid mixing prod/non-prod setups.
>

Greetings,

1) As Aaron outlined, if your are utilizing JBoss then this is
controlled in the start-jboss.sh file. If your are deployed on a
different Application server (WebLogic, WebSphere, or Tomcat) then where
the value is set is a bit different.

2) Each node in the cluster must have a unique value for the engine id

3) If you change an Engine ID while it has any workflows that are still
running (in progress), you will have an issue. As the Engine ID that
the workflow was started on, owns it. Which means if you change the
value, that workflow will not be able to complete because the Engine
that owned it is not running. So there are "issues" with changing
workflow Engine Names.

You have two options:
a) Make sure all WF owned by the Engine ID in question have completed
before you change the name
b) Utilize the SOAP endpoint to move the Workflow(s) to an Engine that
is running.
--> Note: The Workflow Administration plugin in iManager has this
feature (meaning it is using the SOAP endpoint so you do not need to
either write a client or use a different tool like soapUI).

--

Sincerely,
Steven Williams
Lead Software Engineer
Micro Focus
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.