...
The sections below list certain best practices and relevant features that enable user users to get the most out of the Fiorano platform capabilities in various sections. The sections outlined are applicable to both developers as well as environment management teams.
| Tip |
|---|
It is assumed that the reader is well aware of Fiorano Architecture. Please contact Fiorano Support at support@fiorano.com for any clarifications. |
| Panel |
|---|
Development |
Event Process
...
It is a good practice to limit the number of components in an event process in the range of 15 to 20. This results in quick start up times and manageable workflows. If the requirement seems to grow beyond this these many number of services, it is better to use remote service instances to enable inter event process communication.
...
Use Service Launch Order
In certain cases, it might be important for an order to be present while different components in an event process are getting launched. To launch and/or stop microservices , present in an event process , in in a predefined order order, use Service Launch Order.
...
Customize Business logic of new components by modifying the logic. Refer the Modifying Business Logic section.
Samples
Fiorano provides an extensive set of samples which provide best practices to affect certain changes to the components generated using Fiorano SDK, like providing multiple ports, generating user defined CPS. Each of the samples are is accompanied by a readme.txt which lists out the steps to make changes.
...
Improve the security of messages that flow between components through an active flow by adding Port or Route Encryption to the messages. Refer the Message Encryption section.
Server Security
Establish secure communication between Enterprise server and Peer server by configuring the protocol parameters in the server profiles; refer the Enable Server Level Security section.
...
Web Service Security
It is critical that web services which are exposed in Fiorano are secured properly. Security can be different for different types of web services and can be enforced at different levels.
...
Windows users can enable to write Write Fiorano logs Logs to Windows Event Viewer for convenience. Refer the Write Fiorano Logs to Windows the convenience of viewing logs in Event Viewer section..
Monitor using Callouts
For more fine-grained monitoring of events happening in a flow, it is possible to define SBW callouts at the port level. The callout option allows to perform custom Business Activity Monitoring out of the data being processed by the ESB in an asynchronous manner. Refer the Configure SBW Callout section to understand how this works.
Tracking documents for reinjection and Creating SBW Tables manually
The documents that are passing through the entire flow can be tracked using the Dashboard by enabling Document Tracking option.
...
It is important to understand a topology that is best suited for an environment. Fiorano is a completely distributed system where the different servers in Fiorano architecture can be deployed in different parts of network based on the requirements like the location of DMZ servers, need for disaster recovery etc. To understand the different topologies, refer this pagethe Deployment Topology section.
Cloud Setup
Refer this section Cloud Setup to understand the best practices and configuration changes required to deploy the Fiorano server in the cloud and hybrid environments.
...
To achieve stable, high throughput, and highly optimized memory usage of the Fiorano Environment, it is very important to tune the heap memory allocated to each service component and the Fiorano servers. Refer Tuning Component Memory section.
Also refer Also refer Component Configuration to restrict or expand memory used by a component based on the requirement by appending appropriate Maximum Heap Size (-Xms) and Initial Heap Size (-Xmx) values as JVM parameters. This section also covers the below sections:
...
| Panel |
|---|
Change Management |
Use Named Configuration
Configuration The configuration set for a particular service instance can be stored by a name to reuse the configuration in other service instances in future. Using named configuration support, configurations can be predefined and the name of the predefined configuration can be linked/transferred to all Service Instances. Though the actual configuration has only one location, as it is referred to by multiple Service Instances, making changes to the named configuration will affect all Service Instances automatically. So, to advance the process of Event Process Orchestration and Change Management within the Fiorano Event Processes, refer the Named configurations section.
...
Event Processes in Fiorano can be assigned a label which denotes the environment in which it should run and configuration can be defined for all required environments. When required, the event process can be changed from one environment to another by a click of a button in eStudio or can be automated using scripts. Refer this page to understand how it works.
...
To make changes to resource URLs (like URL in HTTPAdapters) based on the environment in such scenarios, the environment value is provided as a JMS property in the message. It can be used in scripts/if-then-else funclets to adapt to the URL based on the environment. Refer Change Resources based on Environment property section to check how to do this.
| Panel |
|---|
System Management |
Linux Level Configuration
Refer While using Linux/Unix OS, there are various configurations that may be changed to optimize the availability of resources to Fiorano. This is discussed in the Manage Linux System-level Configuration section page.
Clone VM
It is a good practice to clone the VM that is preconfigured with Fiorano installation and set up with Java, lock files etc. Use cloning to make copies of a virtual machine from an already configured machine; these copies reflect the entire file system (with the installation files etc), configuration and settings of the VM from which it is copied. To understand how to prepare your system to clone with Fiorano and changes that needs to be done after a machine is cloned, refer the Clone a Virtual Machine section.
...
It is recommended to have tracking points in flows where a manual replay of messages is not possible or is cumbersome. Fiorano document tracking enables defining important points in an event process and replay any failed transaction from that point. The messages to be tracked are saved in a data store in an asynchronous manner without any affect on server performance. Refer the Re-injecting Failed Documents section to perform this.
...
To save some disk space, you may schedule a deletion task for the old SBW documents that are tracked; refer How to schedule Deletion of SBW Documents section. This helps in avoiding issues like Low Disk Space error.
events Events are temporarily stored in a persistent database that are created during runtime data of the Enterprise Server. After an event has been processed, it gets deleted from the temporary store. If these events are not able to be processed, the temporary data store may grow to occupy a large amount of disk-space. To delete the data present in various profiles of Enterprise Server, clear Clearing ESB Server Database
...