Rumba Session ID
When a session is created for Blue Prism to use in Rumba as per below, you need to ensure for each machine the "Session ID" in the options is changed for each VM or machine.
By launching the session file manually or by using a robot you may find a problem that it says an instance is already in use or logged in, when this is not the case.
Reason behind this is that each machine or VM is using the same session file and each machine needs its own session file.
In this example each machine had their own session file on the C Drive, however, the session file was saved using the save ID of the session.
for example.
Machine VAD session 55A
Machine VBD session 56A
Machine VCD session 57A
all machines used a session with the id saved as 56A.
Therefore we could not run multiple sessions of Rumba.
The below illustrates the ID on launching the Rumba session for machine VCD.
Therefore each machine had to have the session file tweaked to ensure it could open up multiple sessions.
To do this go to "Options" as per the below screen, then select the second Tab that corresponds to the error message you were getting, in this case Tn3270.
See highlighted the 57A, this was originally 56A on machine VCD.
it has been changed to 57A to ensure mutliple sessions can be opened
now you will be able to have multiple sessions opened
