Directory Volume Configuration
Open a project
When the project is created, it is found in the administrator project tree. You open a project
by activating 'Open Project' in the popupmenu for a ProjectReg object.
You can also use the 'sdf' command to attach to a project. sdf takes the project name as
argument
> sdf trafficcross1
The directory volume is now opened by the command
> pwrs
pwrs is defined as 'wb pwrp pwrp', i.e. it is logging in as user pwrp. If you have defined
other users for development, you have to redefine 'pwrs' or use the 'wb' command directly.
wb takes user and password as arguments (and also volume as third argument).
If the volume is empty, a guide to help with the configuration is started. To create a simple
project with a node and a volume you just have to press the 'Next' button.
The guide looks for volumes registered for the project. If there are no volumes registred it
suggests volumes with suitable volume names and free volume identities, and registers the
volumes if the suggestions are approved. The guide also creates all the configuration objects
in the directory volume and inserts suitable data into them.
If you later will expand the systems with more nodes and volumes, it is good to have some
knowledge of how the configuration is done, thus we describe how to configure the volume manually.
The Configuration Editor
The configuration editor displays two windows, and for the DirectoryVolume, the left shows
the volume configuration, and the right the node configuration.
Configure Volumes
First we configure all the root volumes, sub volumes and class volumes in the project. This
is done in the volume window in the directory volume. We start by creating a RootVolumeConfig
object the configures a root volume.
- Enter the edit mode from the menu 'Edit/Edit mode'. Now the palette is visible to the right
in the window, and maps can be opened with a click on the map symbol or a double click on
the text.
- Open the Volume map and select the 'RootVolumeConfig' class.
- Click with MB2 in the volume configuration window, and the object is created.
- Select the object and open the object editor from the menu 'Functions/Open Object'.
- Select ObjectName and activate 'Functions/Change value' in the object editor menu.
- Enter the name of the object. The name should be the same as the name of the volume.
- Close the object editor.
Create the RootVolumeConfig objects for the other rootvolumes of the project. For the following
objects you can control the position of the object. If you click with MB2 on the object name of
an object, the new object will be a sibling to this object. If you click on the leaf or map
symbol, the object will be a child.
Also subvolumes and classvolumes are configured in a similar way with SubVolumeConfig and
ClassVolumeConfig objects.
It is also possible to display the attributes of an object directly in the configuration editor:
- Press Shift and click MB1 on the object to open the object
- Select an attribute and activate Functions/Change value to modify a value.
Configure the nodes
In the right window, the nodes in the project are configured. You group the nodes by which
QCOM bus they communicate on. We create two BusConfig objects, one for the production nodes
and one for simulation. In the BusNumber attribute the busnumber is defined.
As children to the BusConfig object, the NodeConfig objects are created, one for each process
and operator station. When the NodeConfig objects are created, some additional objects are
created
- a RootVolumeLoad object that states the rootvolume to load when the runtime environment is
started on this node. The name of the object should be equal to the name of the root volume.
- a Distribute object that configures which files are copied from the development environment
to the process or operator station.
Open the NodeConfig object an enter nodename, operating system and ip address.
Below the BusConfig object for the simulation bus it is suitable to place a NodeConfig object
for the development station, and below this, a RootVolumeLoad that states the volume of the
process station you are going to work with first. In this way you can start the volume in
runtime and test it on the development environment. State the name, operating system and
ip address of the development station in the NodeConfig object.
System object
Create also a $System object in the node configuration window. The system object has the
attributes SystemName and SystemGroup.
- The system name in this state is often equal to the project name.
- The system group attribute makes the system a member of a system group in the user database,
which defines the users for the system. Once the system object is created you have to state
a valid username and password when entering the workbench.
Save
Save the session from the menu 'File/Save'. If the configuration passes the syntax check, you
will receive a question if you want to create the configured volumes. Answer Ok to these
questions and create the volumes.
If the volume selection window is opened now, 'File/Open' in the menu, all the configured
volumes are displayed. The next step is to configure a RootVolume.