EC Gateway Remote can be installed on one of three UNIX platforms based on your key code—HP, IBM, or Sun.
EC Gateway Remote code was developed to work with DataDirect Technologies ODBC drivers. Drivers are available for HP, IBM, and Sun. DataDirect Connect for ODBC UNIX Release 5.0 is supported.
The installation CD creates a directory for a selected UNIX platform. The default path of each directory is listed below:
For HP UNIX, the directory is C:\ECEDIGS\ECRemote\HP.
For SUN UNIX, the directory is C:\ECEDIGS\ECRemote\Sun.
For IBM AIX, the directory is C:\ECEDIGS\ECRemote\IBM.
The content of these directories reflects your choice of with or without RTP. The appropriate files for implementing this choice have been placed in the directory by the installation CD. All of these directories contain software that is ODBC-capable.
Each of these directories contain these files:
wsproces
wsocksvr
wsocclnt
GENERIC.INI
readme.txt
libsafepwd.so, wsprocess.so, and libMQSWrap.so (Sun Solaris and IBM AIX only)
libsafepwd.sl, wsprocess.sl, and libMQSWrap.sl (HP-UX only)
Use the instructions below for processing the contents of these directories.
Installing EC Gateway Remote on UNIX
Copy or FTP files installed on the PC from the CD to the UNIX directory where you are installing EC Gateway Remote.
Use the UNIX chmod command to change the mode of the three ws files (wsocclnt, wsocksvr, and wsproces) to either +x to give execute-only privileges to all or 777 to give full (read-write-execute) privileges to all. We recommend that you grant execute-only privileges (+x).
Using a text editor, edit the GENERIC.INI file and select an appropriate TCP/IP port number for the script file processor port on the remote UNIX machine. In general, ports above 1024 are available for use by EC Gateway Remote. Save the file.
Using a text editor, add WSPATH to your .profile. Ensure that WSPATH is exported so that the UNIX getenv function returns the correct path for EC Gateway Remote. Enter:
WSPATH=<path containing wsocksvr> :export WSPATH
The path name must end with a slash.
Log back in to the remote UNIX machine. This ensures that the path variable is set correctly.
Start the socket listener by invoking the wsocksvr application.
