OK, so this posting is more as a reminder for me going forward than anything else. Last weekend I was working with the OI10 Alpha and I wanted to copy things from one instance of OI10 to another. However, I was blocked because I was only permitted to use one engine and it was being used by the first instance of OI. I thought that this might have been a restriction but I reported it anyway.
It turns out that this is another setting in the new .rxi file that is used by OpenInsight when first launched. I have a couple of .rxi files on my system, so the first challenge was to work out which one I needed to change. This is pretty easy to work out, you just follow these rules:
- If the RX switch is used in the shortcut, you’ll use that .rxi file.
- If none is defined then OI10 will look for a .rxi file with the same name as the application that you are loading with the /AP switch.
- If there is no application defined using the /AP switch, then Oi10 assumes SYSPROG and it’ll use that .rxi file.
So, after a quick check, I’m using SYSPROG, or the SYSPROG.rxi file in my bin32 folder under the OI installation.
I initially guessed that my issue was the <singleInstance> entry which was set to 1, but Carl quickly put me straight and told me that heading will shortly be changed. In the meantime, he’s told me to look at the <serverName> entry in my .rxi file. Because I have a serverName set, I am effectively trying to use the same engine as the first instance and Oi behaves correctly and stops the session. All I need to do is clear the entry by setting it to nothing and then OI will launch as many instances as my license count permits.
Starting OI10 is fully documented in the ‘OpenInsight 10 Presentation Server Object Model’ documentation. This is a work in progress document that is already into 272 pages but today has been yet another reminder of the numerous options that the guys are exposing to developers when launching OpenInsight.
Consider the .rxi file as a more powerful OInsight.ini file and you won’t go far wrong. Just don’t do what I did and blindly dive in. Please take some time to better understand the .rxi files as noted on Carl’s OI10 blog and also in the paperwork when eventually published and released.
For now, I’ll be back into my OI10 Alpha project later today for more learning.