Page History

...

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 page.

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.

...

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 redirect the incoming data to multiple running instances via a Distribution Service. Refer the Load Balancing section  page where an example is mentioned.

...

All SOAP and REST based web services in Fiorano are hosted in a Jetty Server. Jetty Server provides the baseline security for the web applications hosted.  Refer  Refer the Manage Jetty Security section  page to understand the best practices with respect securing Web Services hosted on Jetty.

...

SOAP web services are hosted using the WSStub component. It is a good practice to secure these web services using WS Security standards. Refer Web Service Security example and components documentation.

...

In case of REST services, API keys can be used to restrict access to certain users. Configuration and usage of API keys are explained in in the Additional configuration section in the RESTStub page.

Monitor using Event Process

...

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  page to understand how this works.

...

The documents that are passing through the entire flow can be tracked using the Dashboard by enabling Document Tracking option.

Refer to the Document Tracking page to know how to

• enable Document Tracking in a Workflow of an Event Process
• create SBW Tables Manually (if the servers lack permissions to create SBW tables)

...

Although Fiorano ESB architecture scales very well in a distributed environment, adopt the strategies mentioned in the Optimizing Memory section  page to manage memory more effectively.

...

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 Refer the Tuning Component Memory section page.

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 sectionstopics:

• Using same JVM settings in Multiple Microservice Instances
• Using same JVM settings in Multiple Environments
• Change Default JVM Configurations for Separate Process Components

...

Use In-Memory Launch Mode

...

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 page.

Event Process Life Cycle Management

...

In certain scenarios, to make changes to resource URLs (like URL in HTTPAdapters) based on the environment, 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 page to check how to do this.

Disaster Recovery Environment

...

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 page. This helps in avoiding issues like Low Disk Space error.

...