• Install for Load Balancing
  • Install for Load Balancing
  • "55c4e872-a62b-4274-8ddb-56796f93e299
  • When setting up an environment using load balancing technology, the configuration must be the same on each server used in the environment. When load balancing the Developer or Knowledge Center database, an exact replica must be maintained or synchronized across databases. In the setup example below, it is assumed that you are using multiple Developer or Knowledge Center servers and one Developer or Knowledge Center database.
  • When using Windows authentication, each server must be able to get authentication for the Windows users. That is, all servers should be able to get authentication for all Windows accounts rather than each knowing a subset of users. This is most likely to work when the servers are all within the same Windows domain.
  • Note:
  • To install the Developer servers for a load-balanced multi-user environment:
  • Install the Developer server to the first server as desired. Make a note of your chosen Application (virtual directory) name, Authentication mode and Database configuration.
  • Run the installer for all subsequent Development servers
  • , using the information below for the screens indicated:
  • Choose Web Site
  • Database System
  • : Click the
  • SQL Script Options
  • Yes, the scripts have already been run for this version
  • : Click the
  • Internet Information Services Option
  • option.
  • Yes, continue with the installation
  • or
  • Oracle Database Login
  • Microsoft SQL Server Login
  • or
  • Schema Options
  • Database Options
  • Use existing schema
  • Use existing database option
  • Install and configure the Developer clients as desired, including using the administrator account to give users access to Developer (or create users if Standard authentication is used).
  • To install Knowledge Center servers for a load-balanced environment:
  • Install Knowledge Center to the first server as desired. Make a note of your chosen Application (virtual directory) names, Authentication mode, Database configuration and domain account used for accessing the content root.
  • .
  • The installation creates a Content Root on the subsequent servers because the content folder is created locally. However, the Content Root folder created in the original installation should be replicated to each of the subsequent servers. The folders must be identical to that of the original server. This can either be done manually or through a replication service. Note that this is the content location and content is continually imported to this location through the software
  • Run the installer for all subsequent Knowledge Center servers, using the information below for the screens indicated:
  • Choose Web Site
  • : Use the same load balanced URL used in the first server noted in step 1.
  • URL Settings
  • Database System
  • SQL Script Options
  • Yes, the scripts have already been run for this version
  • Oracle Database Login
  • Microsoft SQL Server Login
  • Schema Options or Database Options
  • Use existing schema
  • Use existing database
  • Content Root Information
  • Content Root User
  • Edit the web.config files within KCenter and KData for all servers. Open the web.config file located in the Web Server\KCenter folder on the original install. Find the machineKey item in the config file (configuration -> system.web -> machineKey). If a secure website (SSL) is used, the Knowledge Center and Content Root applications will all be registered using the load-balanced URL, as long as the server certificate was issued to the load-balanced URL. If SSL is not being used, the Knowledge Center and Content Root URLs should be updated using Manager to match the load-balanced URL.