Multi Seat Mode - Multiple X Servers on 1 Machine

Question

I need to configure a SunBlade 2000 configured with an XVR1000 graphics board to be used by 2 people simultaneously with the own keyb & mouse.
To summarize :
1 Sun Blade 2000
1 Xvr1000
First Port connected to one monitor /dev/fbs/gfb0a
Second Port Connected to a second monitor /dev/fbs/gfb0b
2 Keyb & 2 mouse connected to the 4 USB ports
The 2 monitors must be handled by to istances of X server (2 dtlogin prompt) so the 2 people can work
indipendently.
I tried the following procedure with NO success.
Does anybody can help me ?
Thanks in advance
Luigi Paganini
=============================================================================
In recent versions of Solaris, the Xsun keyboard & mouse DDX modules
have been extended to support multiple keyboards and mice on Solaris.
The Xorg server on Solaris x86 has similarly been extended to support
multiple mice, but not yet multiple keyboards.
Unfortunately, this is not a very well documented feature, though it is
supported - but you must pay close attention to the configuration
instructions and Limitations described below.
There are currently two choices for configuring X on a machine with
multiple input devices:
* One X server with the extra devices available via the X Input
extension (commonly used for accessibility helper programs, or for x86
laptop users)
* Multiple X servers, each with its own set of input & output
devices ("multi-seat" mode)
The two methods can be mixed on a single machine - when configuring you
simply need to determine which X server each device is going to be
associated with.
Requirements
* Solaris 9 FCS or later (SPARC or x86)
* USB-capable machine
* For Solaris 9, USB patch 115338-01 (sparc)/115339-01 (x86) or
newer. For Solaris 10, s10_17 or newer.
Limitations
Due to the nature of USB and Sun's implementation, USB devices may get
different numbers when initialized or hot-plugged in a different order.
A partial solution is to use the full path name under the /devices
hierarchy - this is tied to the physical port a device is plugged into,
so the order is no longer a problem, but devices must always be plugged
into the same port this way.
Xsun Configuration
The following sections may be added to either
/etc/openwin/server/etc/OWconfig or /usr/openwin/server/etc/OWconfig.
Xsun reads both when starting up and merges their contents.
* 1. Run ls -l /dev/usb/hid* to see what the existing device names are.
* 2. Attach the additional input devices to the machine
* 3. ls -l /dev/usb/hid* to see what the newly attached device names
are. Note at the end of each symlink line it will list whether it is a
keyboard or a mouse.
* 4. Add lines of the following form to OWconfig, one for each
device, and each with a unique name beginning with "IMOUSE" or "IKBD":
# sun Keyboard module
class="XINPUT" name="IKBD2"
dev="/dev/usb/hid2" strmod="usbkbm"
ddxHandler="ddxSUNWkbd.so.1"
ddxInitFunc="ddxSUNWkbdProc";
# sun Mouse module
class="XINPUT" name="IMOUSE2"
dev="/dev/usb/hid3" strmod="usbms"
ddxHandler="ddxSUNWmouse.so.1"
ddxInitFunc="ddxSUNWmouseProc";
* 5. To configure multiseat mode, add a section to OWconfig to
associate each keyboard, mouse, and frame buffer with a specific display
(in this case ":1"):
class="XDISPLAY" name="1"
coreKeyboard="IKBD2" corePointer="IMOUSE2"
dev0="/dev/fb1";
* 6. Test your configuration. For multiseat mode, run an Xserver on
the display you listed (xinit :1 or add a line for :1 to
/etc/dt/config/Xservers ). For use with the X input extension, restart X
and run xinputdev -l (source code here) to list the devices the server
sees. You can also run xinputdev -k & xinputdev -m to switch your core
keyboard and mouse to the specified devices.

Answer 1

The report gets called via the rwservlet (hope that answers your question correctly)
The application is in OAS.
The separation i require is both in the database and the reports themselves.
For example let's say i have devapp and testapp - both the exact same app. But they both need to access reports under the same key, but the report needs to get its info from its respective dev and test databases. The key is hardcoded so can't change.
If i understand correctly (a big "if"), the cgicmd.dat file tells wich report to grab and which database to connect to based on the key. Is there a way to have separate key map files (cgicmd.dat) called by separate applications? So that devapp will get Report1 using devdatabase, where testapp wil get Report1 using testdatabase?
It may not be possible to do this kind of server consolidation, I just need to know one way or another for sure - and if it is possible, how to proceed.