Skip to content

How to set the server role

How to set server role for an Ascema managerlink

In order run the Ascema system in an enterprise environment you may choose to either run a single manager for the enterprise or have a number of managers installed more locally to the agents and connected to a single primary manager.

  • After installation of the manager the role will be set as Standalone as shown
  • To adjust the role of the manager you may change this to be either the Primary or a Secondary manager

How to set a Manager as the Primarylink

  • In an Ascema deployment one Manager may be set as a Primary
  • From the drop-down selection for Role for this manager select Primary
  • When you select Primary the screen will change to enable you to enter the required details
  • The Primary should be given a unique name, this will appear on the Dashboard, reports and on administrator screens

  • When you have entered a unique name for the Primary select the Set button
  • The name for the Primary is now set
  • The default port on which Secondary managers will connect is 61617
  • Enter a different port number if your Secondary managers will connect onto that rather than the default
  • If a different port number is entered select the Set button

  • When you are happy with both the name and port assignment select the button Set the role of this manager to Primary

  • The manager will now act as a Primary and will listen for connections from Secondary managers.

Info

Keep a note of the server details on which you set up the Primary manager and any changes you made to the port assignment. These details will be useful when configuring the Secondary managers.

How to set a Manager as a Secondarylink

  • In an Ascema deployment one or more Manager may be set as a Secondary
  • From the drop-down selection for Role for this manager select Secondary

  • When you select Secondary the screen will change to enable you to enter the required details
  • The Secondary should be given a unique name, this will identify it to the Primary and appear on the Dashboard and reports

  • When you have entered a unique name for the Secondary select the Set button
  • The name for the Secondary is now set
  • Using the details recorded when the Primary was configured enter the address of the Primary manager
  • Use the Test button to confirm that the Primary address is correct and a network connection can be made

  • When the Primary address has been tested the button Set the new role of this server to Secondary will be enabled
  • If the port number of the Primary was changed from its default then this port number should be entered now

  • When the details for the Secondary have all been entered select the Set the new role of this server to Secondary button

  • Once the Secondary role is set the button to do so will no longer be displayed
  • The other details you set for the Secondary role of the server will remain visible for future reference

Info

Once a Secondary has been fully set up it will appear after a short delay on the Primary. The new Secondary in this example can be seen here successfully connected and active on the Primary. Another Secondary has been disconnected in this example to illustrate the different icon for a disconnected Secondary.