- Ozeki 10
- Installation guide
- Terms and Definitions
- Message Delivery Engine
- Message Routing
- Ozeki 10 Guide
- HTTP API
- Network speed calculate
- Bulk Messenger
- Cluster Software
- Developer tools
Terms and Definitions
Here you can see the most important, easily understood terms and definitions that builds up the pillars of Ozeki 10. You can discover simple relationships between them. The main purpose of these terms and definitions are to describe the journey of any message wondering through Ozeki 10 from one connection to another. By clicking on some terms, you can see them in a more detailed way.
Read the most important terms and definitions of sending messages through Ozeki 10. You should know that everything connected to Ozeki 10 can send or receive messages, including the applications installed on Ozeki 10's desktop. Scroll below to Figure 1 and 2 to see how Ozeki 10 uses the messaging engine to deliver message data between connections.
It is a communication software that routes messages between real world entities (Figure 1-2). It allows you to build routes between shared hardware and software resources of your system. It offers real time information, and provides various configuration options to route messages from traditional routing methods to routing with simple C# codes.
Check out Ozeki 10's home page (http://ozeki.hu/index.php?owpn=2970)
Every connection in Ozeki 10 is an interface to the outside world. At least two connections are needed. The first connection receives the message from the outside world, while the second connection forwards the message to a real world entity. Each connection has an inbox and outbox folder. You can handle these folders through Ozeki 10's GUI.
High speed connections with Ozeki 10 (http://ozeki.hu/index.php?owpn=5825)
Each connection in Ozeki 10 is identified by a connection address. The address starts with the connection name you have provided when creating the connection and ends with the IP address of the Ozeki 10 server. Both parameters are separated by a '@' symbol. For example 'My_Button_1@localhost' or 'My_Button_2@184.108.40.206'
The throughput of each connection is different. It defines the number of messages sent or received within a given timeframe. You can measure the speed of both incoming and outgoing messages. It is also advised to know the message length that a connection can handle. If the message flow is faster then the connection throughput, a message queue will be created.
If not provided, it will be sent to the default address configured on the connection form. Each message contains two delivery addresses. The first one is the 'From' address and the second one is the 'To' address. The address format depends on the connection that forwards it. For example in case of a GSM Modem, the 'To' address is a phone number.
Each message has a delivery status, which shows the routing engine what to do with the message. Each inbox and outbox message has it's own delivery status. Statuses available for inbox messages: In, Failed, Postponed and for outbox messages: Out, Scheduled, Sent, Not sent. The delivery engine can change the delivery status of any message it forwards.
What kind of message statuses exists (http://ozeki.hu/index.php?owpn=5826)
Each message is a data package going through a connection. Messages can either be thrown away or forwarded through a connection to the outside world. A message can contain any type of file including pictures and sounds. You can find messages in the inbox and outbox folder of each connection. Most message has a delivery address to an outside world entity.
How to label a message for delivery (http://ozeki.hu/index.php?owpn=5651)
Each message can get tags, so they can be handled by the message delivery engine. Tags cannot be created by the user. The most important tag is the message 'ID'. Other important tags are the 'To' and 'From' address, the 'Signature', the message 'Type', the 'HttpSession' and finally, the message 'Content'. The 'HttpSession' identifies the browser client running the Ozeki 10 GUI.
It is the process of selecting a path for traffic across a network, or between multiple networks. Routing is performed for many types of networks, including circuit-switched networks, such as the public switched telephone network (PSTN), and computer networks, such as the Internet. Routing is performed in Ozeki 10. It basicly connects outside world entities on all kind of networks like the internet, Modbus, M-Bus or other networks. These networks can be reached through the corresponding port of your Ozeki 10 server, like COM ports or the Ethernet port. The server can handle routes between the ports of each connection.
Message Delivery Engine
The delivery engine forwards messages between outside world entities through Ozeki 10. It uses the rules in the routing table or the rules you have written in Ozeki Robot Controller. It makes sure that each message is transferred from a connection's inbox to another connection's outbox. The message can be moved between folders according to the delivery status.
See the Message Delivery Engine work on the following diagram (http://ozeki.hu/index.php?owpn=5826)
Each time the inbox of a connection receives a message, it will be forwarded according to the routing table. A routing table consists of rows and each row is a single routing rule. If the message data fits one of the routing conditions, it will be forwarded to a connection. All message parameters for example the content and the status can be optionally modified by a routing rule.
Create message route with the following tutorial (http://ozeki.hu/index.php?owpn=5652)
In computer science, message queues and mailboxes are software-engineering components used for inter-process communication (IPC), or for inter-thread communication within the same process. They use a queue for messaging – the passing of control or of content. Communication systems like Ozeki 10 provide similar kinds of functionality.
It is a system of rules that allow two or more entities of a communications system to transmit information via any kind of variation of a physical quantity. The protocol defines the rules syntax, semantics and synchronization of communication and possible error recovery methods. Protocols may be implemented by hardware, software, or a combination of both.
The following workflow examples demonstrates how Ozeki 10 delivers messages between connections. The delivery engine is responsible to forward messages from one connection to another.
The 1st example shows on Figure 1 how a new message is generated by an outside world interraction like a press of a button. The message can be forwarded to any other Ozeki 10 connection with the help of the delivery engine. On figure 1 you can see your message delivered to any email address specified in the message's delivery address field.
Figure 1 - Ozeki 10's workflow example (2nd example below)
On the 2nd example all incoming SMS messages are forwarded to your projector. In this case an application is handled as a connection, so it can receive all forwarded messages. On Figure 2 you can see Ozeki SMS Gateway display incoming SMS messages with your projector. Ozeki 10 can handle all applications as connections.
Figure 2 - Ozeki 10 workflow's SMS Wall example