What's New in Director 8.5 > The Server Application > Configuring the server > Using the Multiuser.cfg file |  |

Using the Multiuser.cfg file

There are many other settings that can also be changed by editing the Multiuser.cfg file. Examples of each of these can be found in the Multiuser.cfg file that came with your server. Comments can be added to any of the configuration files by preceding each comment line with a pound sign (`#`). You can also add a `#` character to the beginning of an optional parameter line to prevent it from being read by the server. For parameters that can take more than one value, place a space and a backslash (\) after the first value and place the next value on the next line. If the server does not recognize a particular setting name or a setting is invalid, it displays an error message in its console window and does not allocate any incoming connections. For changes to the file to take effect, the server must be restarted.

When you edit the Multiuser.cfg file, keep a copy of the original file provided with the server installation.

The following server settings can be edited:

Echo allows you to add text that is displayed in the Server window when the server reads the Multiuser.cfg file at startup.

ServerOwnerName is an optional parameter that allows you to enter your name so that it appears in the server window at startup.

ServerSerialNumber allows you to enter your Director serial number. This lets you increase the number of possible server connections from the default value (50) up to 1000. Both Macintosh and Windows serial numbers work on either platform's version of the server.

ServerPort specifies the communications port used by the server. The Shockwave Multiuser Server is assigned port 1626 so that it will not conflict with other server applications running on the same computer. You may change this if you find it necessary to do so.

ServerIPAddress is an optional parameter that allows you to specify an IP address if your server computer uses more than one. Most computers use only one IP address. You can also use this parameter to make the server listen for messages on multiple port numbers on a single IP address.

MaxMessageSize sets the amount of memory to use for the incoming and outgoing message buffers. The total memory used is twice the number you specify. The value must be in bytes and should be a multiple of 1024 (1 kilobyte).

ConnectionLimit is an optional parameter that specifies the maximum number of users that can connect to the server. It defaults to the number indicated by the license you purchased. You can use this parameter to limit the connections to a smaller number.

LogonRejectionDelay is an optional parameter that lets you set the number of seconds to wait before sending a message informing a client whose log-on has not been accepted. The default is 10 seconds.

EncryptionKey is an optional parameter that lets you specify a string to use for encrypting user name and password information when users connect to the server. If you use this parameter, you must include an identical string when using the `connectToNetServer` command in a client movie.

UserLevel lets you specify required user levels for each of the database commands and server commands. You can choose any number between 0 and 100 for each command you want to control access to. By using different numbers for different commands, you can create custom privileges for users of different levels. For the default values for each command, see the original Multiuser.cfg file that came with your server.

MovieCFGPath is an optional parameter that lets you specify the directory where movie-specific configuration files are located.

LogFileName is an optional parameter that lets you specify the name and location of the text file the server generates with its status messages. This file contains all the information displayed in the server's application window and is useful for looking back at server activity and debugging movies.

AllowMovies is an optional parameter that lets you specify the names of movies that you want to allow to connect to the server. If this parameter is not used, any movie may connect.

MoviePathName is an optional parameter that lets you specify the absolute Internet addresses of movies that you want to allow to connect to the server. The server checks a movie's address against the `MoviePathName` settings only if the movie uses the property list format of `connectToNetServer()`. This prevents movies from connecting from any location other than the one the author intended. See `connectToNetServer()`.

IdleTimeOut is an optional parameter that lets you specify how many seconds to let movies stay connected to the server if they are not sending any messages. Movies that remain idle for longer than the time you specify are disconnected by the server. If omitted, this parameter defaults to 1 hour.

ScanTimeReportInterval lets you set the number of seconds between each Server Response Time message in the server's application window. This takes effect only when the Server Response Time item in the server's View menu is turned on.

You can change the default settings for which types of messages are displayed in the server's application window by editing the following parameters. These parameters change which items in the server's View menu are turned on and off at startup. A value of 1 turns the item on, and a value of 0 turns the item off.

ShowLogonMessages corresponds to the Users Log On and Off item in the View menu.

ShowCreateMovieMessages corresponds to the Movie Creation and Deletion item in the View menu.

ShowScantimeMessages corresponds to the Server Response Time item in the View menu.

ShowCreateGroupMessages corresponds to the Group Creation and Deletion item in the View menu.

ShowJoinGroupMessages corresponds to the Users Join and Leave Groups item in the View menu.

The following parameters specify which server Xtras the server loads at startup and which commands each Xtra provides:

ServerExtensionXtras lets you specify the names of Server Xtras to load at startup. These names are the internal names of the Xtras, and not necessarily their file names. The Xtras need to be located in the Xtras folder at the same directory level as the server.

XtraConfigCommands lets you specify which Xtra is referred to by the `XtraCommands` that follow it. Each series of `XtraCommand` entries should be preceded by an `XtraConfigCommands` entry.

XtraCommand lets you specify each command that a particular Xtra uses. This makes the server aware of what strings may be sent as commands for the Xtra. The default Multiuser.cfg file that comes with the server has a series of commands declared for the ObjectDB Xtra, which controls the use of database objects with the server and determines whether users without a preexisting `DBUser` object can log on to the server. For details on these log-on controls, see the Multiuser.cfg file that was installed with your server.