So, you need to define name of ACSLS machine under CSI_HOSTNAME. SSI_BASE_SOCKET is not required unless you wish to restrict port usage.
Of course, you will have on server side so many ssi processes as many CSI machines you will define (single ssi can communicate only with single csi on ACSLS).
For other settings check ssi/mini_el/libstlstk manual.
ble1
4 Operator
•
14.4K Posts
0
January 30th, 2006 02:00
--------------------------
/usr/sbin/mini_el&
CSI_HOSTNAME=hcrvelin1
SSI_BASE_SOCKET=55555
export CSI_HOSTNAME
export SSI_BASE_SOCKET
/usr/sbin/ssi&
CSI_HOSTNAME=hcrvelin2
SSI_BASE_SOCKET=66666
export CSI_HOSTNAME
export SSI_BASE_SOCKET
/usr/sbin/ssi&
--------------------------
So, you need to define name of ACSLS machine under CSI_HOSTNAME. SSI_BASE_SOCKET is not required unless you wish to restrict port usage.
Of course, you will have on server side so many ssi processes as many CSI machines you will define (single ssi can communicate only with single csi on ACSLS).
For other settings check ssi/mini_el/libstlstk manual.
Message was edited by: hcrvelin
Message was edited by: hcrvelin
mmiglioranzi
19 Posts
0
January 30th, 2006 07:00