External Zed.xml Configuration file.

The Zed server has a small configuration file called zed.xml that lives in the root directory of your server installation. For very infrequent tasks (such as configuring SSL) you may need to edit this file. You may edit this file with any text editor that you are familiar with. Your zed.xml file will look something like this:

<?xml version="1.0" encoding="UTF-8" standalone="no"?><Zed name="Zed">
	<Logs buffer_size="1000" clear_at_startup="false" enable_tail="false" file="zed.log" max_entries="100000" max_size="10240000" max_strings="512" reuse="false" string_table_size="102400">
		<Panic buffered_when_off="true" dump_when_hit="1000" onoff="true"/>
		<Error buffered_when_off="true" dump_when_hit="500" onoff="true"/>
		<Warn buffered_when_off="true" dump_when_hit="100" onoff="true"/>
		<Info buffered_when_off="true" dump_when_hit="0" onoff="false"/>
		<Debug buffered_when_off="true" dump_when_hit="0" onoff="false"/>
		<Trace buffered_when_off="true" dump_when_hit="0" onoff="false"/>
		<Sql buffered_when_off="true" dump_when_hit="0" onoff="false"/>
	</Logs>
	<LoginConfig file="zed.jaas"/>
	<IOAdapters>
		<IOAdapter class="com.zed.io.http.HttpIOAdapter" listen_ip="" listen_port="8081" name="Http" secure="false" httpdomain="" keystore="" storepass="" keypass=""/>
	</IOAdapters>
	<APIAdapters/>
	<ZedLogics zedLicenseCode="zed.lc.xml">
		<ZedLogic actionmap="com/zed/logic/utils/utils.actions.xml" class="com.zed.logic.utils.ZedUtils" dbsetup="com/zed/logic/utils/sql/utils.xml" name="ZedUtils"/>
		<ZedLogic actionmap="com/zed/logic/builder/builder.actions.xml" class="com.zed.logic.builder.ZedBuild" dbsetup="com/zed/logic/builder/sql/builder.xml" name="ZedBuild"/>
		<ZedLogic actionmap="com/zed/logic/planner/planner.actions.xml" class="com.zed.logic.planner.Planner" dbsetup="com/zed/logic/planner/sql/planner.xml" name="ZedPlanner"/>
		<ZedLogic actionmap="com/zed/logic/tracker/tracker.actions.xml" class="com.zed.logic.tracker.Tracker" dbsetup="com/zed/logic/tracker/sql/tracker.xml" name="ZedTracker"/>
		<ZedLogic actionmap="com/zed/logic/discussion/discussion.actions.xml" class="com.zed.logic.discussion.Discussion" dbsetup="com/zed/logic/discussion/sql/discussion.xml" name="ZedDiscussion"/>
	</ZedLogics>
	<ZedStorage>
		<ZedDB growby="4" isDefault="true" location="db/zed" maxconnections="20" name="Main"/>
	</ZedStorage>
	<ZedStaticHTML>
	   <ZedCustomHTML path="C:/static_content/" requiresSession="false" url="/StaticContent/"/>
	</ZedStaticHTML>
	<ZedServers></ZedServers>
</Zed>

Zed Root

The root element in the configuration file looks like this:

<Zed name="Zed">

There is only the name attribute, and it gives a name to your server. This name is what your other Zed servers will see this server as, and by default the install will set it to your machine name.

Logs

The logging section captures the information defined in Managing Server Logs and should not need to be edited directly. If you are having problems getting your server started, however, there are 2 entries here that are very useful:

• clear_at_startup If this is set to "true" then every time the server starts, it will erase any old log file that was in use and start a brand new one. This can be helpful when your server is having problems starting and you only want to see current log messages.
• enable_tail If this is set to "true" then every log message that is written to the server log file will also be written to system standard output so that you may see them on the console. The server log format is a binary optimized format, so when trying to diagnose startup problems, seeing the log messages output to the console can be very helpful.

LoginConfig

This section of the config file is reserved for future use.

IOAdapters

The Zed server is capable of listening on multiple different ports for inbound connections. Each port that you would like to listen on is represented by a specific IOAdapter entry in the IOAdapters section of the configuration file. Typically there will be only one configured port, but if you need multiple, you may define as many as you like.

IOAdapter

During installation your IOAdapter entry will have been configured properly for your system. This typically involves setting the listen_port and the httpdomain values. The full list of attributes is:

• class Defines the class file that is used as an IO Adapter for the Zed system.
• listen_ip This is the IP address that the IO Adapter will bind to and listen on.
• listen_port This is the port number that the IO Adapter will listen on.
• name This is the name of this IO Adapter.
• secure indicates whether SSL is in use.
• httpdomain indicates the full domain used in your server certificate.
• keystore the location of your keystore that contains your server certificate. (Defaults to "zedWeb.ks" if not provided)
• storepass the keystore password used to access your keystore. (Defaults to "zedWeb" if not provided)
• keypass the key password used to access your server certificate within your keystore. (Defaults to "zedWeb" if not provided)

APIAdapters

This section of the config file is reserved for future use.

ZedLogics

These are the logic modules that provide the functionality of your Zed system. Do not make any adjustments to this section of the configuration file.

ZedStorage

This is the area of the configuration file that allows you to define multiple databases. If you have multiple groups, all wanting to use the same Zed system, but each wanting their own "sandbox", this is how you would enable that scenario.

ZedDB

For each of these items, a fresh Database and Team Wiki will be created in your Zed System. Each will have it's own list of users, administrators, tasks, builds, discussions, and team documentation.

• isDefault This is the default database when one is not specified by inbound client communications.
• location This is the physical location and name prefix for the database files that will be created.
• name This is the name of the database and will be displayed in the LogOn screen, and will need to be used any time a connection is made to the Zed server by a client application.
• growby When the database connection pool maintained by the system is fully used, and another connection request comes in the connection pool (if it has not already reached the maximum size) will be increased by this value.
• maxconnections This is the maximum size that the connection pool will grow to. Ensure that this setting is high enough for your typical traffic load, but not so high to use memory unnecessarily.

ZedStaticHTML

Sometimes you will want to serve a series of static html pages in addition to the dynamic content that Zed provides. If this is the case, you can add a series of URL's to the Zed server and define for each URL which filesystem location will be accessed when content is requested.

ZedCustomHTML

This element defines an individual custom URL that will be served by Zed and mapped to a path on the filesystem.

• path This is the filesystem path where the static HTML content will be sourced.
• requiresSession This allows you to define whether or not a current Zed login will be required to access this static HTML content. If you specify "true" then only users who have already logged into Zed will have access to this URL. If you specify "false" then anyone will be able to access the content at this URL.
• url This is the URL Path that users will use to access this content.

ZedServers

This area of the configuration file is maintained by the Build Servers screen and should not be edited by hand.