Marcy, It seems like what you're envisioning is to have a "service" image to run catcher.exe (slight correction: it's actually catcher.exe rather than panel.exe) to facilitate TKE Workstation interactions with various Crypto Express CCA mode physical features (and associated domains) spread across several machines. That all seems fine to me, but one threshold question that comes to mind is whether sharing a single IP address supports "fast enough" operations. What I mean is that with a single IP address you'll only be able to have one instance of this service image running at any one time. If you're in a future situation where you have to perform lots of TKE operations across multiple machines/features/domains very quickly -- some sort of calamity involving rapid fire TKE operations -- your operational "throughput" *could* be significantly limited with only one running service image at a time.
A slight, simple variation here would be to have a single service image with a default startup IP address but then allow an authorized operator to switch the image to a different IP address once that image starts up. That way you could have multiple instances of this service image running as long as only one of them is starting up at any one time. - - - - - - - - - - Timothy Sipples I.T. Architect Executive Digital Asset & Other Industry Solutions IBM Z & LinuxONE - - - - - - - - - - E-Mail: [email protected] ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
