Windows の場合は、server edition のみ。
Windows Server 2008 では、OpenJDK または Oracle JRE を事前にインストールする必要があります。
*nix プラットフォームでは、Web UI を正しくレンダリングするため、Microsoft* TrueType のコアフォントのインストールが必要になる場合があります。
With a named license, you are allowed a fixed number of "named users." A "named user" is a human being (not a machine) that is active in the past 30 days. Therefore, if some users never log in, or if a user leaves the group and doesn't log in again, that user does not count towards the named license. Named licensing is more appropriate when most users will be using the product daily.
With a concurrent license, you are allowed a maximum number of "concurrent users." A user is considered "active" if he/she has used the system in the past hour and has not explicitly logged out. Users with any Collaborator page open in a browser will remain logged in regardless of whether they are actively navigating through the site. Concurrent licensing is more appropriate when you have many users that will use the system only occasionally. In both cases, a "user" is a human being, not tied to a particular machine or client. This means that if someone uses both the Eclipse client, stand-alone client, and command-line client, plus uses Collaborator on a work machine and laptop, that all counts as one "seat" whether fixed or floating.
It's hard to give guidance because it varies quite a bit. Generally the best advice is: Just try Collaborator. There is a report on the User Administration page that tells you exactly how many named and concurrent licenses you would be using right now. Use that empirical information to determine which is best for your team. Typically, a trial doesn't involve everyone, and typically the usage pattern isn't exactly the same as when it will be deployed, so you'll have to estimate. Still, you'll be doing so with some real numbers.
If you have developers in many timezones, concurrent license usually becomes more economical.
If each person will be inside Collaborator at least once per day (either as author or reviewer), typically named licenses are cheaper. If less frequently than that, concurrent.
If you expect large spikes in usage - where perhaps everyone is online at once during a code review crunch - you'll want named. Otherwise, you have to get enough concurrent to handle that peak usage.
Remember that you can upgrade from named licenses to concurrent licenses later, with credit for your named license investment. So if it turns out you purchased the wrong model, or your needs change, we make it economical to upgrade anytime.