Some additional configuration steps may be required when deploying SuperSERVER on an IPv6 environment.
Command Line Options
The following command line options have been added to SuperSERVER and Metadata Server to enable configuration on IPv6 environments:
The address to bind on. This may be set to a specific address or hostname that resolves to this machine, or to any of the wildcard addresses:
|The port used for incoming connections.|
The address used to access this instance. This address is also reported as the SuperSERVER address to SuperADMIN and will show up when you run the
|That support for IPv6 should be disabled.|
|The 96 bit NAT64 prefix you want to use, specified in the form of an IPv6 address. This will automatically be prepended to the server address in outgoing connection attempts.|
The priority to give to different address types when making an outgoing connection, and when determining which address to bind to.
Outgoing connections will always be attempted on all resolved addresses, but this argument provides a way to tune performance for outgoing connections, based on your network configuration.
For binding addresses it determines which address will be selected by default to use in CORBA IORs.
This can be set to one of the following values (note that the names are not case sensitive):
|The path and file name of a log file for CORBA information.|
The level of logging information for CORBA. This can be set to one of the following values (the names are not case sensitive):
The port for Metadata Server can also be configured using the
MDServer_PORT option in the metadata.config.xml configuration file. If present, the setting in the XML file takes precedence over the command line setting or the mdserver_network.properties file.
Configuration Files for SuperSERVER and Metadata Server
As an alternative to setting the network properties through the above command line options, these can be configured in configuration files called network.properties (SuperSERVER) and mdserver_network.properties (Metadata Server). These files do not exist by default, so if you want to use them you need to create them in a text editor and save them to the SuperSERVER data directory (if you installed to the default location, this will be C:\ProgramData\STR\SuperSERVER SA on Windows; on Linux save the files to the same directory as the scsa executable).
Specify any options you want to set in the following format (replace
<option> with the command line option, minus any initial
# Which local IP address to bind to. This can be a IPv4 or IPv6 address. If you wish to bind to all local addresses, use "0.0.0.0" or "::" bind=:: port=9232 # Tell clients that your machine address is my-machine-name:9232 when constructing IORs proxy=my-machine-name:9232 corba-log-file=C:\SuperSERVER_log.txt corba-log-level=Info
# Which local IP address to bind to. This can be a IPv4 or IPv6 address. If you wish to bind to all local addresses, use "0.0.0.0" or "::" bind=:: port=8005 # Tell clients that your machine address is my-machine-name:8005 when constructing IORs proxy=my-machine-name:8005 corba-log-file=C:\MDCorba_log.txt corba-log-level=Info
Production Server Configuration
Additional configuration settings are now available for production system. These can either be set in the Production System configuration file (in the connection section) or on the command line:
See Configuration File for full details.
The following properties have been added to the
[General] section of the super.ini configuration file:
NAT64Prefixon both SuperSERVER and SuperCROSS. The
NAT64Prefixshould be the string prefixed to the IPv4 address to allow them to be accessed over the NAT64 bridge. This will be specific to your network configuration.
See super.ini for more details on the new SuperCROSS properties.