Filter
Top Products
The expectation in this concept is that each server and database combination
are independent of any other. There is no communication between FlowMark
servers. However, this solution could, over time, be combined with the
following option.
Have processes on one or more servers perform subprocesses on other
servers. This function in V2.3, introduces the concept of domains. A domain is
what most people consider as the “FlowMark server,” the FlowMark Runtime
server and its database. In Buildtime, there is a new selection on the primary
menu called Servers. From there, you define each “server” in the system as an
object along with its network address and communications protocol. Then,
when you create a subprocess icon in process design, you specify on which
server this is to run, on the “Server” page in the notebook. That page also
allows the server to be specified in a data structure member of the process
activity's input (source) container. The subprocess template must be located in
the database of the other server, and all staff resolution (who does which
activities) is done on that other server based on the staff defined in its data
base. This would follow the regional and headquarters example discussed
above.
If you conclude that you need to have multiple OS/2 or NT servers, consider the
other server platform option, AIX. A single fast AIX server can do the same work
as several OS/2 or NT servers. It does involve a change in operating system,
which may have training and skill implications, but it may be the better choice.
These capabilities may not provide you with the ideal solution that you would like to
see immediately. But it is the goal of FlowMark developers to provide you with an
enterprise solution. They are working to give you increasing levels of function to
connect a growing number of users within the overall workflow framework. You will
implement your solution today within the current capabilities of FlowMark, but you
should design with the intent of eventually expanding the horizon.
3.2 Dedicating Your FlowMark Servers
It is best to have your FlowMark servers as dedicated machines. If you put other
applications on the server machines, there is a good possibility that you will
sometimes affect the service you give to your FlowMark users. Even “small”
applications that use resources only occasionally can use significant resources
during the few times they need them. These blips in usage can result in poor
response times for users who are sharing that server.
If you have excess capacity on a server and need to use it for something other
than FlowMark, then understand the risks and keep an eye on what these other
things do. They may impact processor utilization and may also cause conflicts in
memory (swapping) or disk I/O.
6 FlowMark V2.3 Design Guidelines