Run AFECS platformFirst of all make sure that you set following environmental variables: EXPID, AFECS_HOME, COOL_HOME. Refer AFECS Installation & execution section for more details. Execute $AFECS_HOME/bin/platform. This will start platform normative agents, pub-sub server and front end container. In case you don't want to run an AFECS container on that particular node run platform script with the -nofe option.If you need more verbosity run platform with the -debug option. Run AFECS containerThe software architecture of AFECS is based on coexistence of multiple containers, providing complete run time environment for AFECS agent execution and allows several agents to concurrently run on the same host. AFECS design choice limits to only one container per control node. To run the container execute $AFECS_HOME/bin/container. By default it will run with the -NOmulticast option. This means that container will connect to the platform through direct TCP using host name defined in the $COOL_HOME/setup.xml file. In the case you are not sure where the AFECS platform is running, then run $AFECS_HOME/bin/container with the -multicast option. Start run control GUI Type $AFECS_HOME/bin/rcgui to start run control GUI. Synopsis of the rcgui is: rcgui -<option> <value> The list of rcgui options are shown in the table below.
rcgui option are non obligatory, and platform specific information (platform host name for example) from $COOL_HOME/setup.xml file will be used as default. Attention: rcgui will not start if it will not be able to find an AFECS platform to connect to. Connect GUI to a control system
|