smallworld 空间数据库使用端口，防火墙配置

 Question:
 What are the issues for using swmfs 5 through a firewall?

 Response:
 In order for a Smallworld session or swmfs utility to connect to swmfs via TCP/IP, whether on UNIX or on Windows, through a firewall, you must allow TCP connections from unreserved TCP ports on the client to the swmfs port on the server. By default, this is port 1590; you can change this to any other value by placing a suitable swmfs TCP entry in the Internet 'services' file or database on your client and server hosts.
 In order to participate in crash detection and recovery, a Smallworld session or swmfs utility on a client host must also be able to exchange UDP datagrams with swmfs on the server host. This is true for UNIX and for Windows. However, the server UDP port can be specified using the -udpport command-line option. These UDP datagrams use unreserved ports at both ends, and you must configure your firewall to allow this traffic.
 If you want to prevent the UDP traffic, you must also configure your Smallworld sessions and swmfs servers not to use crash detection and recovery (at least, for the client/server combinations in question).

 

swmfs_control

This utility is provided for Windows only, and is used to manage swmfs when run as a Windows service. Its command-line options are:

[ computername ] ...

If the first argument is a computer name, then operations are performed on that computer instead of the local one.

The following installs swmfs as a service and starts it. It will then automatically be restarted whenever the computer is booted.

-install [ options ]

The options are a subset of those recognised by swmfs itself:

-transports name,...
-keepalive wakeup,retries
-port number
-tcpflags value
-nocompress
-nochecksum
-udpport
-authopts