The following sections list new/changed features, resolved issues, and known issues and limitations pertaining to this version:
- Fiorano Platform is now fully compatible with Java 8.
- Configuration Management utility to quickly setup new servers.
- Amazon Kinesis Connectors
- Amazon S3 Connector
- S3Download: To download files from Amazon Simple Storage Service (S3) complementing the S3Upload microservice that is already available.
- Amazon SQS Connectors
- MQTT: To publish and subscribe messages using MQTT Protocol.
- T24 Connectors
- OFSConverter: To transform data from XML format to Open Financial Service (OFS) message format and vice-versa.
- TextSplitter: To split and then group the incoming messages based on the Sort key values provided to generate the output in aTEXT/XML format.
- LambdaConnector: To invoke a function from the list of functions configured in Amazon Lambda service.
New API Management Policies
- Policy to verify SAML Assertion Token.
- Policy to monitor and manage SLAs corresponding to payload size, response times and API availability.
- Support for Connection Pooling in EDBC framework.
- REST Microservices: Support for gzip content encoding.
- MSCRM: Option to read OData metadata file and generate schema for entities.
- DB: Support for OUTPUT clause for Insert/Update/Delete query for MSSQL.
- HL7Sender: Option to enable/disable ACK Message validation.
- JMSOut 4.0: Option to configure Message Selector.
- SAPB1: Support for Connecting SAP B1 instances which are using MSSQL 2012 and MSSQL 2014 DB servers.
- Salesforce: Support for different named configurations for WSDL in different environments.
- POP3: Option to ignore attachments in XML mode.
- HttpAdapter 4.0, 5.0: Support to define response character set.
- LDAPLookup: Support to poll directories for changes in user objects.
- SocketAdapter: Support for named configurations.
- REST APIs for managing and monitoring the life cycle of Event processes and Microservices.
- JMX APIs to delete routes in an Event Process.
- Certificate management from ESB Dashboard.
- Option to set default Xmx value for components launched as separate java processes at Peer level.
- More debug information and time stamp is printed in the logs that are generated while CLI target is getting executed.
- Option to exempt some of the named configurations while exporting an application.
- Added documentation for 'changePeerServerNodes' target in readme files.
- New policy scope to define alerting and auditing actions in case of policy violations.
- Support to customize error messages in case of policy violations.
- Support to deploy, undeploy and export multiple projects.
- REST APIs to export and import API projects for better integration with DevOps engines.
- Option to view Server Process ID in Server Details section in the Server Status page.
- Option to view adapter patches in the Server Details section.
- Option to view port names in the orchestration editor.
- eMapper: New funclets in the
- JMS Message Functions category to get the environment of the event process and set/reset priority for a message
- Lookup Functions category to look up from a DB without cache
- Jetty server upgraded to version 9.2.14.
- Application Context changed from Object property to JSON content.
The API traffic store upgraded to use Apache Cassandra 3.x.
- DB: Provider name 'Microsoft SQL Server' is changed to 'Microsoft SQL Server 2000' and; Microsoft SQL Server will be treated as the latest version.
- Stability fixes for cases involving remote flows and durable subscriptions.
- Check resource and connectivity (CRC) fails when peer for durable route's target service instance is not available.
- TTL set on message is not persisted as messages flow through microservices.API Management.
- Changes to the quota of an API product are not immediately reflected in gateway servers.
- REST: Response is sent as byte data if the media type is configured as application/octet-stream in Response Configuration.
- RESTStub: Output port is not generated when media type is selected as 'application/octet-stream'
- POP3: Binary Attachments are not base 64 encoded if the attachment name contains 'text'/'edi'/'json'.
- XMLSplitter: Erratic behavior when there are more than 10 input sessions.
- JSONConverter: Issues with empty XML element with no target namespace while converting from XML to JSON.
- XML2EDI: Issues with empty segments while using UN/EDIFACT format.
- HttpStub: Microservice is not working in one-way mode.
- WebServiceConsumer 4.0: Endpoint address is not getting updated from Named Configuration even after microservice restart.
- HL7Receiver: Message properties are not added when 'Send custom responses' option is enabled.
Known Issues and Limitations
- If multiple eStudio clients are connected to the same Enterprise Server and working on the same Event Process, the changes made by one client will not be reflected to the other clients.
- There is a race condition which under rare circumstances leads to corruption of the Peer Server's PUBSUB database on multiple start/stop events of an Event Process accompanied by multiple failovers of a Shared HA Peer Server. The Peer Server refuses to start after this point. For exact sequence of steps that may lead to this issue, please refer to KB#3273 on the Fiorano Support Portal following the URL http://support.fiorano.com/
- Workaround: Clear Peer Server's PUBSUB database manually. The PUBSUB database is present under: $FIORANO_HOME/runtimedata/PeerServers/<PeerProfileName>/FPS/run/PUBSUB.
- While logging on to eStudio (server on Windows 2012), if the user is not logged in as admin, he/she could get exceptions while connecting to eStudio.The reason is that by default the NTFS file system does not provide necessary Write permissions to a Guest User. And if the default temp file location that java uses falls outside the permissible territory, it results in the aforementioned exceptions.
- Resolution: The 'java.io.tmpdir' property should be set to some location within permissible limits (in server.conf/fes.conf) or the user should be given explicit Write permissions.
- A Peer Server run as an NT Service under a Domain User account in Windows fails to deploy more microservices after about 75 microservices have already been deployed.
- JMSIn/JMSOut/JMSRequestor microservices running on a Linux machine cannot connect to a Weblogic server running on a remote Linux machine using the T3 (default) protocol; the HTTP protocol should be used instead.
- SBW search does not work properly with the MSSQL database when an Event Process name has Japanese characters.
- SimpleHttp Microservice fails when the length of IP and subnet are different in the system property "http.nonProxyHosts".
- Layouts will not be completely preserved when an Event Process is opened in eStudio and nStudio.
- Customization of Error Logs and Problems View to show only eStudio-related logs is not supported.
- Event Processes created prior to SOA 2007 SP4 cannot be imported.
- Option to import an extension is not present.
- Validation of Types is not present while compiling funclets.
- EDI and CSV formats are not supported.
- Feature not supported—Cannot use overloaded java functions for scripts imported from a TMF file.
- Applications created prior to SOA 2007 SP3 using WS Stub and Http Stub microservices are not compatible with the latest versions.
- Workaround: After importing, reconfigure WS Stub and Http Stub instances.