Re: Shared Workflow across ARS Servers

[Rodney Harris]

** Hi Conrad,   What you are describing should work just fine. You can do client side operations such as active links and table fields across multiple servers. The main limitation with this approach is that the client must be logged in to each server. That usually means that their passwords must be synchronised across both servers. In your case it sounds like the user you are testing with has no access to one of the forms on one of the servers or is not logged in to one of the servers. Just as you added the second server in the admin tool each user must do the same in their user tool.   This feature also works across the web as long as both servers are connected to the same mid-tier.     Rod Harris   CMS Asset Solutions       From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Conrad Pereira Sent: Monday, 18 September 2006 3:20 PM To: arslist@ARSLIST.ORG Subject: Shared Workflow across ARS Servers   ** Hi Listers,   I have installed two ARS Servers on one Server. I have some workflow that has to be executed between the two ARS servers. In the Admin Tool -> Accounts dialog box both the servers are added. When doing an Active Link, in the Set fields action, both the servers show up and a workflow has been done to Set a Value calling from the second ARS server form to the first ARS server form. The Active Link has been saved successfully. When testing it in the user tool, it gives the error "Form does not exist on server". We were informed that in order for this kind of shared workflow to work, both the servers need to be licensed with a Server License. We licensed the servers now, however the problem still persists.   Has anyone done this kind of development before? Is there a limitation that this works only for active links and not for other objects?   Looking forward for your reply.   Thanks,   Conrad Pereira CyberMAK Information Systems Manama, Bahrain __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___