Page History

Versions Compared

Old Version 2

changes.mady.by.user Prathewraj M

Saved on Apr 17, 2015

compared with

New Version Current

changes.mady.by.user Prathewraj M

Saved on Apr 28, 2015

Key

This line was added.
This line was removed.
Formatting was changed.

...

The default maximum JVM heap size is 64 MB. The Fiorano tools leave the JVM parameters as the default parameter, that is, 64 MB heap memory for each of the components. This JVM parameter can be fine tuned to reduce the memory footprint of individual service component microservice instances. The amount of memory allocated per JVM can and should be reduced for smaller components (such as flow-control components) or increased for memory-heavy components (such as, XSLT, Database Adapter, and so on).

...

Use Port Bindings to connect multiple flows running on a single Peer in place of External Business components. For example, if the Business Process definition requires data to flow from one process to another, then the output port of the last service microservice in one Event Process is bound to a specific destination and then bound input port of the first service microservice of the other Event Process to the same destination as specified on the output port earlier.

...

Click the output port of the last service microservice in EventProcess1; the port turn blue in colour.
In Properties panel, select the following values in the JMS Destination tab:
- Destination Type: Topic
- Custom Destination: Yes
- Destination Name: Click the button present on the right side of the property and select 'EVENTS_TOPIC' (choose as per preference).
Similarly, configure the same settings with the same destination on the input port of the first service microservice present in EventProcess2.

Figure 2: Output Port Properties for the last service microservice in EventProcess1

Figure 3: Input Port Properties for the first service microservice in EventProcess2

Anchor
_Toc372741531
_Toc372741531
Size of Event Flows

...

Keep the sizes of each message flowing through the Fiorano workflow small and not greater than 1 MB. If a given message is too large, then split the message into smaller ones using the XMLSplitter service microservice, or in case of the Database adapter, limit the response size to an appropriate value.

...

Note

Please note that the above technique works even when the flow executes across distributed machines. The technique is to store large binary attachments in one location (essentially a file somewhere on the network), pass just a reference around the flow and then on the appropriate step to access the (large) binary as needed. Also, the binary attachment in most cases is not parsed at every step of the event process. As such, it is not needed at each step of the process and a simple reference will do.
Not all messages can be split. Splitting works only when each of the final messages become a standalone document after the split. For this reason the XMLSplitter cannot be used for all large messages.

Anchor
_Toc372741533
_Toc372741533
DB

...

Microservice Tuning

Use a larger number of SQL queries per DB service microservice instead of using separate DB services microservices per SQL query. Additionally, use the DBQuery/DBProc components wherever possible in place of DB, as the latter is a much heavier component.