![]() Swarm installs include the Swarm Helix Core Server extension file and trigger scripts required for Swarm to get the events it needs from your Helix Core Server. Swarm needs to know about a number of Helix Core Server events to operate correctly, this can be done by using Helix Core Server Extensions (recommended) or Helix Core Server Triggers. Helix Core Server Extensions are easier to install and maintain than Triggers. Triggers are still supported, but we recommend you use Helix Core Server Extensions. For more information on how to delete and reload cache, see Cache Info. For the new Helix Core Server configuration to take effect, the configuration cache must be deleted and reloaded. To configure a specific Helix Core Server instance, add a config.php file in the /data/servers/ directory. For example, to override the global value of jira configuration for a specific server, you can provide a different value for jira configuration in the server specific configuration file. You can override the default values by using a server specific configuration file. The root element in the /data/config.php configuration file contains default values for all Helix Core Server instances. The port, user, password, and sso items are specific to the Helix Core Server instance they are nested under. ![]() The total length of the server label and Redis namespace combined is limited to ≤ 127 characters.The labels must not contain any spaces or any characters that require URL encoding, and.The labels must be URL-friendly labels.serverA and serverB are labels that identify the individual Helix Core Servers.'password' => ' admin user ticket or password for serverB', 'password' => ' admin user ticket or password for serverA', Ĭonfigure the Swarm configuration file for multiple Helix Core Server instances:Įnter a label for each Helix Core Server instance and enter the server connection details under the server label. You can still connect directly to the other P4D instances by including the Helix Core Server label in the URL for each instance, for example. If Swarm fails to connect to the primary Helix Core Server, Swarm cannot display any of the Helix Core Server instances in the global dashboard. The first Helix Core Server in the p4 item is the primary Helix Core Server, this instance renders the global dashboard. For a list of Helix Core Server versions supported by Swarm, see Helix Core Server requirements. The Helix Core Server instances do not have to all be at the same version but they must all be versions that Swarm supports. ![]() Optional Helix Authentication Service is available for users to log in to Swarm but is not enforced.ĭisabled Helix Authentication Service is not available to Swarm. sso if the Helix Core Server is configured for the Helix Authentication Service, set to one of the following:Įnabled all users must use Helix Authentication Service to log in to Swarm.password is the ticket or password for the Helix Core Server user.user is a userid that has admin privileges for the Helix Core Server.port is the P4PORT for your Helix Core Server.'sso' => 'disabled', // default value is 'disabled' 'password' => ' admin user ticket or password', When Swarm is configured for a single Helix Core Server instance the p4 item looks like this: array( Navigate to the User id dropdown menu, select System Information, click the Cache Info tab, and click the Reload Configuration button. You must be an admin or super user to reload the Swarm config cache. If you make a configuration change, Swarm will not use it until the configuration cache has been reloaded, this forces Swarm to use the new configuration. The Swarm Helix Core Server connection details are configured using the p4 item in the /data/config.php configuration file. Set up the Swarm configuration file for the Helix Core Servers Configure a cron job for each Helix Core Server instance.Set the Swarm trigger token and Swarm host variable for each Helix Core Server.Set up the Swarm configuration file for the Helix Core Servers.Swarm must be installed in its own virtual host.Ĭomplete the following steps to connect Swarm to multiple- Helix Core Server instances:.Workaround: Log in to them individually using the instance Log in button in the sidebar or by including the server instance name in the URL, for example. Issue: If Helix Authentication Service is enabled for Swarm and the Try to login to all available servers with these credentials checkbox or the All available servers option is selected in a login dialog, Swarm will not try to log in to any of the other Helix Core Server instances that are configured for Helix Authentication Service. ![]() Known limitations, only applies if you want to use Global Dashboard:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |