In addition to the Dashboard, this is the second major site of the Streamsheet environment. Here, you find all resources and sections to configure and organize your Streamsheet environment. The Streams-resources Consumers, Producers and Connectors serve the purpose of defining data streams. Further, the Section “Security” serves all user-related organizational issues whereas “Organization” contains tools to group and structure bigger Stream Machine models.
The Stream-resources Consumers, Producers and Connectors serve the purpose of defining data streams. There is a hierarchy to these resources in which Connectors form the foundation for Consumers and Producers. Hence, the definition of a data stream consists either of a Connector-Consumer pair or a Connector-Producer pair. Each Consumer and each Producer runs on exactly one connector. Connectors, on the other hand, can have many consumers and producers.
As the name suggests, Connectors take information on overall connection parameters, such as addresses and authentication details. Especially if several message streams are on a broker, server or other “data space”, Connectors contain information which can be shared by Consumers and Producers. Consequently, shared information has to be defined only once in one place.
Consumers are used to define the input message stream of Streamsheets.
Producers are used to define outgoing message streams.
Connectors serve the base definition of streams. They contain the information to connect to brokers, servers, clusters and other data spaces. This includes usually addresses and authentication information, such as username and password or certificates.
other Connector examples:
Consumers are the Stream resource to specify data streams which serve as the input for Streamsheets, thus, they deliver messages to a sheet. You must first choose a Connector and then add the missing information to complete the definition of a data stream.
other Consumer examples:
This section contains tools to organize user-related aspects, such has users, their roles and policies which define a role.
Here you can add, modify and delete user and set their role and security settings. A user must have one role but can also have several. The “admin” user has full control and is inseperable of its “admin role”.
Roles bundle policies and are assigned to users. If a user does not have a role, he/she is not allowed to do anything. The “Admin Role” is inseperable from the “admin” user and the “AdminAllPolicy”.
Policies determine what users are allowed to do. Per default users are not allowed to do anything, but policies can be granted to them. There are different policy categories covering “Machines”, “Streams”, “Security” and “Label”. Adjust the switches to grant or revoke rights. Adding a Label constrains a policy. It hereafter only impacts objects, which also have been assigned the corresponding Label.
In the Organization menu it is possible administer the label hirachy and download or restore the current database.
In the Labelmanager it is possible to create, structure and assign Lable to a variety of objects. These objects include Stream Machines, Streams, Users, Roles and Policies. They can be used to manage authentificaion of users and further serve as a filtering mechanic in the dashboards.
Downloading a Database saves the current version of your Streamsheets installation. All Stream Machines, Streams, users, user roles, policies and labels are being saved in one big JSON file. This file can be restored in any Streamsheet installation at anytime. Restart the complete Streamsheets Application after restoring the database from a backup file to finish the restore process.