...
| 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 |
|---|
Deployment |
Topologies
...
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 the Deployment Topology section.
Cloud Setup
...
Refer Cloud Setup to understand the best practices and configuration changes required to deploy the Fiorano server in the cloud and hybrid environments.
| Panel |
|---|
System Management |
Linux Level Configuration
...
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 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 page.
| Panel |
|---|
Development |
Event Process
...
Components per Event Process
It is 's 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 these many number of services, it is better to use remote service instances to enable inter event process communication.
It is also a good practice Also, it's always good to develop flows which can be reused across different processes. To achieve this, remote service instances can be used in conjunction with route selectors.
Use Service Launch Order
In certain cases, it following an order of execution 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 a predefined order, use Service Launch Order.
Load Balancing
Used Use Load Balancing to distribute the messages to multiple business services for processing. To enable service-level load balancing on a service, run multiple instances of the service on the different ESB Peers and routes redirect the incoming data to the multiple running instances via a Distribution Service. Refer the Load Balancing section where an example is mentioned.
...
It is critical to ensure that the platform scales both with current projects (likely in themselves to be highly distributed, probably across company boundaries) and with future growth. To address scalability issues, refer the Scaling section.
...
Customize Business logic of new components by modifying the logic while creating them.
Samples
Fiorano provides an extensive set of samples which provide best practices to affect certain changes to the components generated using Fiorano SDK, like such as providing multiple ports , and generating user defined CPS. Each of the samples is accompanied by a readme.txt which lists out the steps to make changes.
...
Always define user permissions on Applications to control unauthorized access to sensitive information. To perform this, refer the Access Control List (ACL) based security section page.
Improve the security of messages that flow between components through an active flow by adding Port or Route Encryption to the messages.
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 page.
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.
...
Refer Document Tracking in Dashboard to track them in the Dashboard.
| Panel |
|---|
Deployment |
Topologies
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 the Deployment Topology section.
Cloud Setup
Refer Cloud Setup to understand the best practices and configuration changes required to deploy the Fiorano server in the cloud and hybrid environments.
| Panel |
|---|
Memory Management |
Optimize Memory
...
To avoid a class of serious problems that could occur because of improper configurations of the Virtual Machine (VM) on which the Server is running, memory , tuning and management need to be done at the server. Problems of this nature sort are very hard to reproduce and can create a lot of confusion with regards to the server behavior. Refer the Managing Peer Server Memory section page to manage peer server memory.
...
Use In-Memory Launch Mode
...
Use In Memory execution mode for components with less memory footprint such as XSLT and CBR. Server JVM will be used while using components in this mode. Refer the Using 'In Memory' Launch Mode section to understand how to use this mode.
| Panel |
|---|
Change Management |
Use Named Configuration
...
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 the Define Named Configuration and utilize EPLCM page to understand how it works.
Automate Environment Migration
...
When While migrating from one environment to otheranother, it is better to use CLI tools to automate the process. Refer Work with Command Line Interface (CLI)
Change Resources based on Environment property
...
To In certain scenarios, 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 page to check how to do this.
| Panel |
|---|
System Management |
Linux Level Configuration
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 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.
| Panel |
|---|
Recovery From Failures |
Disaster Recovery Environment
...
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 page to perform this.
| Panel |
|---|
Miscellaneous |
...
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 page. This helps in avoiding issues like Low Disk Space error.
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 the ESB Server database.