Topic 10.2.1: About Multi Node Application

  • Standalone to Network Configuration

  • Earlier we discussed the standalone configuration you have been using up to this point. At this time you want to migrate over to a network configuration that will reflect four nodes accessing one Galaxy Repository. This will allow us to utilize a networked configuration to convey more complex concepts relating to connectivity, exporting objects and templates and other multi-node environmental considerations.
  • Each of the nodes contains the Bootstrap, the ArchestrA IDE, and a Galaxy Repository. Once you have reconfigured the environment there will be one machine (Node1) that will contain the Bootstrap, the ArchestrA IDE, and a Galaxy Repository. Three other nodes will be connected to the Galaxy on Node1. Those other three nodes will contain only the Bootstrap and the ArchestrA IDE.
  • In the networked architecture a common Galaxy Repository will be shared between a set of PCs allowing multiple users to simultaneously work on the same application.
  • The existing standalone environment is illustrated as follows:


  • The networked environment that you are migrating to is illustrated as follows:

  • Multi User Conversion Considerations

  • When migrating from a Stand Alone environmental configuration to a networked configuration there are some factors that must be taken into consideration. One of the key ones being that certain functions take place on the Galaxy Repository node BEFORE they take place from the connecting nodes.
  • There a need for only one PLC so the one residing on the resulting Galaxy Repository node is the one that is most likely the one desired for the network. Therefore, that is the one and only one that is to be exported in preparation for the network environment.
  • The node that contains the Galaxy Repository must do several tasks before any other nodes can connect. These include:
    • Create the Galaxy to which all other nodes will connect.
    • Create Platforms for other galaxy members.
    • Rename the node.
    • Name and deploy their own Platform as the first Platform deployed on the Galaxy Repository node.
  • Failure to follow these key steps before others connect and start deploying objects can produce less than desirable results.



Last modified: Friday, 10 April 2020, 4:21 PM