Fiorano SOA Platform 9.2.1 Release Notes          

 

Product Name: Fiorano SOA Platform™

Version: 9.2.1

This document contains important information about Fiorano SOA Platform 9.2.1 release.

These notes are the most current information for the product and take precedence over all other documentation.

This release notes includes the following topics:

Release 9.2.1

Release 9.2.0

Release 9.1.1

Release 9.0.2

Release 9.0.2

Release 9.0.1

Release 9.0.0

Product Documentation  PAGEREF _Toc163893075 \h 7

System Requirements  PAGEREF _Toc163893076 \h 7

Customer Support PAGEREF _Toc163893077 \h 7

Phone Support PAGEREF _Toc163893078 \h 7

 

Note: To upgrade your current Fiorano environment to Fiorano SOA Platform 9.2.1, please refer to Fiorano Migration Guide located at $FIORANO_HOME/migration/FioranoSOAMigrationGuide.

 

Release 9.2.1

 

What's New?

 

This section lists all the new features added in Fiorano SOA Platform 9.2.1 release.

eStudio

• eStudio can be integrated to eclipse installation by adding it as a drop-in.

• The users can install their own plug-ins to eStudio. Integrating commercial XML tools, reporting tools, Source control plug-ins and so on can be done with ease using the Equinox P2 support.

• Option to import newly created service as a project into workspace.

• eMapper - Option to import mapper projects (.tmf) created by old mapper tool.

• Route Transformation

  • Option to convert XSLT component configured with Context-Body to Body mappings to an on-route transformation.

  • Option to provide custom XSL in an on-route transformation.

Dashboard

• Dashboard now provides the ability to re-inject tracked documents to the port on which they were tracked. User can optionally choose to edit the tracked document before re-injection. For more information, refer to section 5.7.4 in Fiorano SOA User Guide.

• Option to search tracked documents based on parameters 'Document ID' and 'Workflow Instance ID' in ESB web-console.

Components

• HL7 - Schemas for XML messages generated by pre-built HL7 components (HL7Sender, HL7Receiver, HL72XML and XML2HL7) are added to schema repository.

• SMTP - Option to specify character set of mail body.

• WSStub - WS-Security is now supported.

• Support for X.509 certificates

• DB - Option to define transactions across multiple messages.

• Routes which originate from a remote Service Instance are supported

 

TOP

What's Changed?

 

The following changes are included in the Fiorano SOA Platform 9.2.1 release: 

• eStudio

  • The Maximum size of file which can be stored in the workspace's local history has been increased to 10 MB.

  • eStudio is upgraded to use Eclipse Galileo (Version 3.5)

• HL7Reader and HL7Writer components are replaced with HL72XML and XML2HL7 components respectively which use HAPI library. The XML formats for HL7 messages are changed and confirm to schemas provided in schema repository.

• HAPI library used by HL7 components is updated to version 1.0.1.

• Responsibility of undeploying the webservice when a WSStub component is stopped is changed from Enterprise Server to Peer Server. This removes the unnecessary communication channel between the Enterprise Server and Peer Servers.

TOP

Resolved Issues

This section describes some of the customer issues resolved in the Fiorano SOA Platform 9.2.1 release.

• Improper replication of persistent messages sent to queue when the network between HA servers fluctuates that results in the failure to deliver such messages to connected clients.

• Unable to view policy details in the 'Policy Manager' tab when using web-console in Japanese language.

• [BC components]Messages are lost on stopping the component configured in scheduling mode and launched in InMemory.

• Component launched manually as NT service gets killed when user logs off.

• [Join] Unprocessed messages are lost on restarting the component.

• [DB] Monitoring does not work when component is configured in eStudio.

• [WebServiceConsumer 5.0] Component does not work if WSDL has target namespace.

• Unable to send event e-mail alerts after Enterprise Server is restarted.

• Sender Address specified under event mail configuration is not taken into account while sending event e-mail alerts.

• Instances of services which depend on a service are not stopped when the service is edited.

• [FileReader] Post-Processing MOVE Action does not work in scheduling mode when input is not specified.

• [BC Components]Message loss on fps restart when components are configured in scheduling mode.

• [WebServiceConsumer]Unable to invoke the webservice if both Proxy and HTTP authentication are required.

• [MSMQReceiver] Component crashes while receiving large messages.

• [XSLT] Unable to load the user documents specified in xsl.

• WebServiceConsumer cannot connect through HTTP Proxy which requires authentication

• SSL secured web service exposed using WSStub component is not undeployed while stopping the Event Process/WSStub component.

• Unable to add breakpoint on a route when different peer servers connect to Enterprise Server using different IPs of Enterprise Server machine.

Possible solutions:

1. Edit the Enterprise Server's connection factory named 'SERVICEPROVIDERCF' to specify Connection URL as hostname of the Enterprise Server machine.

2. Edit Enterprise Server profile to specify ServerAddress property as hostname of the Enterprise Server machine.

For both of the above solutions, user will have to map this hostname to an accessible Enterprise Server's IP address in each of the Peer Server machines.

• Enterprise Server's Connection factory properties are not persisted across server restart.

• Japanese text not correct on login page of ESB web-console.

• A resource added to a component is not sent to Peer Server at the time of CRC (Check Resources and Connectivity) if it's present directly under Fiorano installation in the Peer Server machine running on Windows OS.

• On machines with multiple network interfaces installed, the number of open file descriptors keeps increasing with time.

• Event Process having Japanese name and containing WSStub does not work after fps restart.

• [DB]Input parameters are not retained on creation of update queries when constant Column values are defined for all columns in SET or WHERE tabs.

 

TOP

Known Issues and Limitations

Known Limitations

This section contains the list of all known limitations for Fiorano SOA Platform 9.2.1 release.

eStudio – Limitations:

• XPath Editor is not implemented. User can not configure XPath selectors using UI on route.

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

• Users/Groups cannot be configured.

• Profiles cannot be configured.

• Event processes created prior to SOA 2007 SP4 cannot be imported.

eMapper - Limitations:

• Visually editing a DTD is not supported. Workaround - Use Edit Structure.

• Option to import an extension is not present.

• Validation of types is not present while compiling funclets.

• EDI and CSV formats are not supported.

• Features not supported:

  • Cannot use overloaded java functions for scripts imported from tmf file 

Known Issues

This section contains the list of known issues for Fiorano SOA Platform 9.2.1 release.

Bug ID	Description
12402	Message Selectors and Durable subscriptions do not work on some EDBC components
13007	[Firoano Studio] Unable to launch studio from directory other than studio/bin.
13304	[JMX Browser] Cannot edit/add alerts in online mode.
13670	Applications created prior to SOA 2007 SP3 that used WS Stub & HttpStub components are not compatible with the latest versions. Workaround: After importing reconfigure WS Stub & HttpStub instances
13780	Synchronize button not getting disabled even after application is launched.
13789	After HA failover, Error window shows peer not available even though its available
13797	Fes logs cannot be exported from Studio.
13832	Compression and Encryption on Route not working as expected
14056	Color of the component does not change in HAFES failover.
14535	Debugger set on an application fails in case of network failure. This is related to setting debugger in case of cable plug out scenario. All other cases related to cable pullout (without debugger) are working fine.
14558	ClassNotFoundException while trying to connect Weblogic server remotely. JMSIn / JMSOut/ JMSRequestor compoenents running on a Linux machine cannot connect to a Weblogic server running on a remote Linux machine using T3 (default) protocol. HTTP protocol should be used instead.
15686	Enterprise server does not start when its transport protocol is HTTP & security protocol is SUN_SSL
16637	There is a race condition which under rare circumstances leads to Peer Server's PUBSUB database corruption on multiple start/stop of an Event Process accompanied by multiple failovers of 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 in 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.
16924	Changes done to Event Process are not reflected when the Event Process is externally modified.
18773	No option to cancel Custom Property Sheet (CPS) dialog for components whose CPS launches in eStudio JVM. Connection test in CPS for components like DB becomes non-responsive for sometime if invalid connection parameters are provided.
19088	Component instances with Japanese characters in their display name do not get launched after Peer Server restart. Workaround: Restart Event Process after restarting Peer Server.

 

 

Release 9.2.0

 

What's New?

This section lists all the new features added in Fiorano SOA Platform 9.2.0 release.

Audit logging

• Audit capabilities to enable administrators to record various actions performed by users. Additionally, this feature allows you to record unauthorized attempts to access the Fiorano Servers.

For more information, refer to chapter 12 Audit Management in Fiorano SOA User Guide.

Component Control Protocol

• Component Control Protocol (CCP) is a new communication channel between the Peer Server and components to ensure predictable component behavior and to facilitate status information exchange.

For more information, refer to section 3.12 Component Communication Protocol (CCP) in Fiorano SOA User Guide.

Refer to javadocs located at $FIORANO_HOME/javadoc/esb/ccp/index.html for an overview of Component Control Protocol (CCP) APIs

Note: Fiorano pre-built components do not implement this protocol as of this release. This feature will be extended to Fiorano pre-built adapters in future releases.

Monitoring

• Server monitoring policy to raise SMTP and JMS alerts when server’s memory usage crosses a specified threshold.

• Support for SSL settings to send SMTP alerts.

Component Creation

• Option to specify whether the component can launch with default configuration or not.

• Support for CCP.

• New sample to demonstrate CCP using Simple JMS template.

Components

• [Encryption / Decryption] Support for encryption and decryption using AES algorithm.

• [POP3 / SMTP] Support for providing additional properties that are required for connection.

• Option to specify connection details in the input message to dynamically connect to different external systems.

For more information, refer to component help and section 10.4 Managed Connection Factory in Fiorano SOA User Guide.

• A new error handling action to discard the connection on connection failure is added in EDBC framework.

• [MQSeries] Support for multiple folders in RFH2 headers.

• [DB] Exception handling support for zero update count exception.

• [FileReader] Option to send post processing directory in input message.

eStudio

• RCP version of eStudio containing minimal set of plug-ins and perspectives required for Fiorano. It is also significantly smaller in size and much faster than its previous version.

• Option to specify the background for component icon to indicate the Peer Server on which a component is launched.

Default settings for service instances

• Default JVM settings and connection factory settings for components launched in separate process. These default values are set on each newly added service instance.

For more information, refer to section 12.2.3 Service Options in Fiorano eStudio User Guide.

Route transformation

• Support to define transformations on route.

• Support to import Event Processes with route transformations developed in previous releases.

• Support to work on route transformations from different Event Processes simultaneously.

Note: Only one transformation from an Event Process can be open at a time.

• Support to cancel the Custom Property Sheet (CPS) of components whose CPS is launched in an external process.

• Support to define the Application Context on component's output port.

• Notification dialog will be shown when a Peer Server becomes available or unavailable in an Enterprise network.

• For components whose Custom Property Sheet (CPS) is launched in a separate JVM process, a preference page is provided in Fiorano Preferences where the user can provide options like memory settings, classpath etc. that are to be applied on CPS process.

eMapper

• Support for selecting any of the derived types for a given type in the input structure or output structure. xsi:type attribute with selected derived type as value is added to the transformation.

Dashboard

• Password Strength Check

  Extensible list of rules to validate user password and calculate its strength are added. Users can provide their own implementations of validation and strength checks, thus over-riding default Fiorano implementation.

For more information, refer to section 8.3 Password Rules in Fiorano SOA User Guide.

• New tabs to define audit policies and view/search audit events.

• Option to view SBW exception documents from Latest Events Page.

• Option to restart/stop Enterprise/Peer Server(s) from dashboard.

• Storing configurable dashboard preferences e.g. grid size, window size, active page etc. in cookies and restoring the previous view after user logout/login actions.

For more information, refer to section 2.5.2 Remembering User Preferences in Fiorano SOA User Guide.

• Configurable page refresh time as opposed to previous hard-coded value of 5 seconds.

• Option to stop/start page refresh anytime. Useful when user does not want page to refresh automatically. This saves load on Enterprise Server.

• Refresh button to refresh the current page.

• Dashboard is now available in Japanese language too.

• Reduced memory usage of dashboard and faster load time. Dashboard now loads pages on demand (i.e. HTML pages will be loaded on need basis, whenever user navigates to that page).

• Dashboard now shows exception messages sent by server on an unsuccessful operation. This sometimes saves cumbersome task of checking dashboard logs each time an exception happens while performing an operation.

• Option to define policies and alerts to receive SMTP/JMS alerts whenever Server Memory Usage crosses a threshold value specified under the policy.

• Option to specify secure mail servers (i.e. mail servers requiring SSL authentication) as outgoing mail server for events/queue depth notifications.

Localization

• Japanese messages for UI messages in

  • Component CPS in eStudio

  • eStudio

  • eMapper

  • Dashboard

TOP

What's Changed?

 

The following changes are included in the Fiorano SOA Platform 9.2.0 release: 

• EDBC Framework

  • Interfaces and classes in EDBC framework have been extended to support CCP. For compatibility of previously created components refer to Component Migration section in Fiorano SOA Migration Guide

• [JMS Adapters:5.0] JMS connection is created without using username and password when username is not provided. MQ provider specific default user credentials will be used.

• Stopping an Event Process with debug routes whose source or target ports are on a disconnected Peer Server is not allowed.

• Peer Server code base has been re-organized to achieve better stability, predictability and to improve performance while handling commands from Enterprise Server.

• Server profile structure has been changed since previous Fiorano SOA releases. Users of Fiorano SOA 2007 SP5 or above may use the migration scripts provided under $FIORANO_HOME/migration/profilemigration to migrate server profiles from older versions to SOA 9.2.0 version.

• eStudio runtime data

  • Runtime data of previous releases is not compatible with current release. All services and applications have to be manually ported.

  • Default workspace location is changed from $FIORANO_HOME/eStudio/workspace to $FIORANO_HOME/runtimedata/eStudio/workspace.

  • All offline and online repositories are now present in the workspace.

  • Offline service repository is changed from $FIORANO_HOME/eStudio/eclipse/dropins/eStudio/plugins/com.fiorano.studio.repository_1.0.0\services to $FIORANO_HOME/runtimedata/eStudio/workspace/.repositories/Offline/Services

  • Offline application repository is changed from $FIORANO_HOME/eStudio/workspace to $FIORANO_HOME/runtimedata/eStudio/workspace/.repositories/Offline/Applications

• Preferences in eStudio have been reorganized. Preferences defined in previous release are not compatible with current release and have to be redefined.

• RMI APIs startEventProcess and checkResourcesAndConnectivity do not take environment argument anymore. The action will be taken by the server using the label under which Event Process has been saved.

TOP

Resolved Issues

This section describes some of the customer issues resolved in the Fiorano SOA Platform 9.2.0 release.

• [Decryption] Unable to decrypt the content encrypted with PGP algorithm.

• [HTTPStub] Component does not launch when configured to use SSL.

• Lag in notification of Enterprise Server shutdown to Fiorano eStudio client.

• Properties of multiple objects (ports, routes, service instances etc) cannot be changed at once.

• A component cannot be edited or deleted after configuring on Windows.

• Zombie component processes are left running for ever in a few cases like:

  • Abrupt Peer Server shutdown

  • HA Failover where an ACTIVE Peer Server switches to WAITING state and then to ACTIVE state again

• Performing actions such as Open, Run, CRC, Launch and Stop on multiple Event Processes in Server Explorer view is not supported.

• If the Event Process is configured for a certain target environment, this preference is not restored on eStudio restart.

• State of Event Processes is not correctly reflected sometimes.

• Event Process repository is not visible in nStudio after repeated logins.

• [FileTransmitter/FileReceiver] CPS of the components cannot be finished.

• Custom property sheet of components created in nStudio cannot be opened in eStudio and vice-versa.

• External schemas are not shown in the schema viewer on ports.

• [DB] Parameters cannot be added or removed for SQL statement in eStudio.

• Event Process launched from dashboard is always launched in development environment.

• Unable to start server as service if server configuration file contains JVM arguments without '-X' prefix e.g. '-client'/'-server' argument.

• [DB] DateTime datatype is generated in XSD for column whose datatype is Time.

• StackOverflowError is observed in Enterprise Server while doing some operation from nStudio.

• [DB] Input and output parameters are cleared if an error occurs while editing the SQL statement even when they retain parameters options are checked.

• Custom Property Sheet of a component having accented characters in its configuration cannot be reopened.

• [WorkListExplorer] Japanese text is not rendered correctly in web pages of Fiorano Worklist Explorer.

• For components whose Custom Property Sheet is opened in a separate process, configuration cannot be finished when there is any route connected to the component's input port.

• [FTPPut] Overwrite functionality does not work if the FTP server does not allow a file to be renamed to a file already existing on the server.

• Sometimes messages pass through route containing breakpoints.

• Server logs containing Japanese characters do not appear properly in logs view of Fiorano Studio.

• Component logs do not contain log messages with SEVERE log level after setting component logger's 'All Modules' property to 'SEVERE' state.

• JMX/RMI clients can not connect to Enterprise/Peer Server if host IP address of Server machine is not reachable from client machine.

• [Exception Listener] Component does not work when password for admin user is changed.

• FESReplicated HA option gets disabled when you save the profile from the Dashboard.

• Occasional occurrence of NullPointerException on Peer Server console when Peer Server reconnects to Enterprise server after a network failure.

• [Cache] JMS message properties are lost when a message passes through cache component.

• [JMSAdapter:4.0] Component does not recover from connection errors when connected to WebLogic server even when retry connection is enabled.

• [FTPPut] Cannot put file on target system when LIST permissions are not available.

• [FTPPut] Component does not create temporary directory on some systems.

• Exception while migrating runtimedata from a previous installation to new installation if some Sample Event Process was deleted from previous installation.

TOP

 

Release 9.1.1

 

What's New?

This section lists all the new features added in Fiorano SOA Platform 9.1.1 release.

 

Japanese localization

• Localization support for UI messages in Japanese for eStudio, eMapper and nStudio.

HA - Improved ping mechanism to determine if the local machine is out of network

• A new configurable property ping retry count is added to server profile that determines the number times the server should attempt to ping gateway server before the server assumes that it is out of network and switches to waiting state. This configuration is useful in avoiding unwanted failovers in network with a possible loss of ping packets.

  The ping retry count property is configurable in the server profile by navigating to Fiorano->HA->HAManager->FioranoHAManager.

  Note: Multiple pings are attempted only before acquiring lock or during server boot.

TOP

What's Changed?

 

The following changes are included in the Fiorano SOA Platform 9.1.1 release: 

 

Template engine

Generated custom component code, help files and javadocs will not contain Fiorano copyright.

TOP

Resolved Issues

This section describes some of the customer issues resolved in the Fiorano SOA Platform 9.1.1 release.

 

Release 9.1.0

 

What's New?

This section lists all the new features added in Fiorano SOA Platform 9.1.0 release.

eStudio Beta

• Two different perspectives for Online/Offline Event Process development.

• Persistent connection with Enterprise Server.

• Additional views - Server Explorer View and Event Process Repository View.

• Support for Localization of UI messages.

• Message browser and receiver on ports.

• Import/Export of Event Processes and components from/to any Enterprise Server.

• Ability to View/Export Server/component/Event Process logs.

• Snap to grid available in orchestration Editor.

• Improved UI for debugger view.

• Preferences for Event Processes to customize the look and feel.

• Copy/Cut/Paste options in Orchestration Editor.

• Support for importing nStudio Event Processes to eStudio.

• Support for opening Event Processes between nStudio and eStudio.

• Restoring debugger on Event Processes on server failure and restart.

• Support portal and online documentation accessible within eStudio.

 

eMapper

• Mapper project files are converted to split file format. All XSDs / DTDs used in mapper projects are stored in individual files.

• Multiple projects can be worked on simultaneously.

• Creating and testing multiple XSLs is supported. Loading multiple output structures, one for each required XSL is supported.

• Structure name can be provided when a new structure added.

• Imported XSDs can be specified while adding a XSD structure.

• Imported XSD files can be reused in the entire mapper project.

• Mapping is allowed to only a single element under Choice node. Auto-mapping also generates mapping to only one element under choice node.

• Copy/Paste of funclets is possible across different mapper projects.

• Support for overloaded Java functions.

• Validation of input XMLs can be done against relevant XSDs in test window.

• Projects created using old mapper can be imported into eMapper.

For more information, refer to Chapter 8 eMapper in Fiorano eStudio User Guide.

 

Improved ACL support

• Viewing, orchestration and running of Event Process is restricted based on the ACL defined for the user logged in.

• Destinations that are auto-created for applications are accessible only to the user who launches the Event Process. These ACL can be changed from Fiorano dashboard.

For more information, refer to section 8.7 Event Process Security in Fiorano SOA User Guide.

 

Improvements in Command Line Interface (CLI):

• Support for stopping and starting selected/all components of an Event Process using Command Line Interface (CLI)

• Support for exporting highest available version of a component using Command Line Interface (CLI).

For more information, refer to section 5.11 The Event Process Command Line Interface in Fiorano SOA User Guide.

 

Ability to monitor queue depth and send alerts when queue depth reaches specified threshold.

 

SBW/Event Tracking 

Support for disabling SBW/Event Tracking with a single option. This option can be helpful in cases where SBW/Event database remains unavailable for long period of time and user wants to avoid additional overhead on Enterprise Server to try to insert SBW/System events on periodic intervals.

For more information on SBW Tracking and Event Tracking, refer to section 2.7.6.1 and 2.8.1.1 respectively in Fiorano SOA User Guide

 

New version of JMS components - JMSIn 5.0, JMSOut 5.0 and JMSRequestor 5.0:

• Improved performance - The new components do not use intermediate JCA specific layers which are present in 4.0 versions of components.

• Listener mode in JMSOut 5.0 - JMSOut 4.0 requires using synchronous call in scheduling mode to simulate listener mode. JMSOut 5.0 supports both synchronous and asynchronous modes.

• Improved UI for configuring the components.

• Connection to JMS server is always maintained and recreated as and when necessary (based on error handling configurations).

• Option to send any type of message to target destination without any modifications to the message.

• Option to define XML interface for all types of message.

• JMSRequestor 5.0 - Consumers created on error destination also use consumer configurations provided in CPS.

• JMSOut 5.0 and JMSRequestor 5.0 - Option to remove durable subscriber when the durable subscription configurations are changed.

Refer to section 4.7 MOMs in Fiorano SOA User Guide or the component Help.

 

Enhancements in pre-built components:

MQSeriesOut:

Option to specify the action to be taken when there are no messages in the queue within the timeout specified. Option can be throw an exception, send an empty message or do nothing. This option is disabled if the wait time suggests to wait forever.

JMSOut:

Option to specify the action to be taken when there are no messages in the destination within the timeout specified. Option can be throw an exception, send an empty message or do nothing.

SimpleHTTP:

Support to cache the connections created and reuse them for processing subsequent requests.

HTTPAdapters:

Support for multipart/form-data (support to upload files) in HTTPAdapters.

WebServiceConsumer 5.0:

Connection timeout property is added 

 

Other enhancements

• ESB Samples
  • Sample program to determine the state of a HA server i.e. ACTIVE, PASSIVE, DEAD, STANDALONE etc. The utility is located in $FIORANO_HOME/esb/samples/SamplePrograms/HA directory.
  • Java samples for importing/exporting components/event processes.
• Default database used by Enterprise Server has been changed from Apache Derby to H2 database for better performance.
• In Fiorano HA, the last active / standalone server can be restarted without the passive server being available. In such case, the server switches to standalone state on restart.
• LDAP and RDBMS support for storing users, groups and ACLs. Refer to section 8.6 Changing Security Database Implementation in Fiorano SOA User Guide for instructions on how to configure servers to use LDAP/RDBMS store.
• Enhanced logging in servers to monitor all activities and enabling easy debugging of the problems.

 

TOP

What's Changed?

 

The following changes are included in the Fiorano SOA Platform 9.1.0 release: 

 

Server memory configurations

All server configuration files have been changed to include typical command-line options and environment variables that can affect the performance characteristics of the Java HotSpot Virtual Machine and hence that of ESB servers.

We recommend to turn on the following option when using JVM version 1.5 update 7 or above to run the servers. It is disabled by default. -XX:+HeapDumpOnOutOfMemoryError

Server configuration files are located at -

o         $FIORANO_HOME/esb/server/bin/server.conf,

o         $FIORANO_HOME/esb/fes/bin/fes.conf and

o         $FIORANO_HOME/esb/fps/bin/fps.conf.

For more information on configuring Fiorano Servers, please see section 7.6 Memory Management of Fiorano Peer Server in Fiorano SOA User Guide

 

Server profile structure changes

 

Runtime data folder structure changes     

The structure of runtimedata has been changed since previous Fiorano SOA releases. Users of Fiorano SOA 2007 SP5 or above may use the migration scripts provided under $FIORANO_HOME/migration/runtimedatamigration to migrate server runtimedata from older versions to SOA 9.1.0 version.

 

Ping enabled property in server profiles

PingEnabled flag has been set to true by default for all Enterprise/Peer Server profiles. This flag ensures that all client connections which are not reachable for a specified time get closed by the server. The value of this parameter can be configured by opening server profile in Studio and navigating to Fiorano->etc->FMQConfigLoader.

 

Event Process versioning

Event Process versioning is not supported. However, previously created Event Processes with a different version are still supported

 

JMS authentication details used by components

 

ESB java samples location

The path of ESB JAVA sample programs has been changed from $FIORANO_HOME/esb/samples to $FIORANO_HOME/esb/samples/SamplePrograms.

 

Password encryption

Passwords specified in various components will be stored in encrypted form in the Event Process XML file. The passwords will be encrypted on reconfiguration of components / profiles.

 

XSLT Component

XSLT component is changed to pure JMS component to improve the performance. The configuration of the component is completely backward compatible.

 

TOP

Resolved Issues

This section describes some of the customer issues resolved in the Fiorano SOA Platform 9.1.0 release.

• Event Process with durable routes sometimes fails to launch on backup Peer Server.

• Enterprise Server hangs during shutdown if SBW database is not reachable.

• Unable to install shared HA profile as linux service.

• Exception while synchronizing Event Process repository database of Enterprise Servers running in HA mode after a network failure.

• Unable to launch components in In-Memory mode if component creates external SSL connection.

• Multiple output structures are shown in XSLT Mapper in case where the structures are manually loaded first time and during reconfiguration both the Output and ON_EXCEPTION ports are connected to ports which have schema defined on them.

• [MSMQReceiver] Component doesn't work when configured for scheduling mode and sample input is not provided in Scheduler Configurations panel at configuration time.

• [WebService Consumer 5.0] Component doesn't launch when the webservice to be invoked is not available during the component launch time

• [HTTPAdapter] Unable to post text content, if the text contains CData.

• [All components / Server profiles] Passwords configured in profiles/component configurations are visible in clear text format in config files.

• Exception when opening or deleting an Event Process with version other than 1.0.

• Issues with sorting columns/drop-down boxes in dashboard.

• Message loss in shared HA when message size is large.

• Peer Server login failure from Studio if Peer Server is SSL enabled.

• Sometimes, Peer Server becomes unresponsive while stopping an Event Process or a component. This happened due to a deadlock in Peer Server.

• Studio shows wrong number of deliverable messages if message(s) expire.

•  [Dashboard] Administrator cannot reset password of any user without specifying the old password.

• Peer Server consumes huge amount of CPU cycles if it is running large number of components and server status page is ACTIVE in dashboard.

• When Peer Server is stopped, all component processes running in separate JVMs are not stopped. Some of these component processes are still present as ZOMBIE processes.

• Aggregator, Chat, Display, HTTPReceive, Join, SAPR3Monitor, Sleep, and XMLVerification components do not support durable subscription on input port.

• [EDBC Framework] Commits are not handled correctly when the session is transacted  and transaction size on input port is greater than 1.

• [MSMQ] Unable to send / receive messages when using remote queues.

• Pre-built compoenents do not support client acknowledge mode.

• [Join] Imported structures are not populated on ports

• [Java Script] Component not working, if it launched in InMemory

• User defined java script functions are not working in Fiorano Mapper

• Document Tracking Issues:

  • Dashboard does not display correct number of SBW workflows if SBW documents arrive at a fast rate.

  • Document tracking search does not return all matching documents when searching with messageText field.

  • Document tracking search page does not update properly when navigating to previous/next pages.

  • OOM issue in Enterprise Server due to improper closing of Result Set. The issue was observed in the scenario mentioned below:

Scenario:

      Using Oracle ojdbc14.jar driver.

      Large amounts of SBW data is handled.

TOP

 

Release 9.0.2

What's New?

This section list all the new features added in Fiorano SOA Platform 9.0.2 release.

• MQSeries Out Enhancements:

Note: The component understands and parses on RFH2 and MQMD headers. Any other headers present in an MQMessage will be sent out along with the body content.

• Join Enhancements:

o         Option to use and configure transformer implementation.

o         Option to select application context source for transformation.

o         Option to select source of properties / headers for the resultant message.

o         Option to select preference for common properties from input messages when properties from both input messages are required on the resultant message. Resultant message can contain values for common properties only from input message on IN_PORT1 or IN_PORT2

• DB Enhancements:

o        Support for commit or rollback based on a trigger on input. This feature can be used to develop database applications with distributed transaction support transaction support across different steps.

Note: A new sample application 'DB Transaction Support' is added to showcase this feature.

o        Improved batch mode support. User can determine whether batching is allowed or not and can choose an appropriate commit mode.

Note: Batching across different input requests is not supported.

• Script components enhancements:

  o         Support for groovy script 1.6.1

  o         Support for java script 1.7

• JMX connection across firewall:

While creating a JMX connection to servers, the JMX RMI connector opens two ports. One is for the RMI registry, which is fixed and known and other port is used to export JMX RMI connection objects. This second port is usually dynamically allocated at random. This causes problem if server is behind a firewall as one of the connection ports is random and it cannot be unblocked.

This release provides a way to configure the value for this second port. To configure this property, open the profile and navigate to Fiorano->jmx->connector->RMIBasedJMXConnector and specify the desired value for 'RmiPortExportObjects' property.

• Shared HA

Shared High Availability profiles are now available for ESB servers. These profiles combine the reliability of a Highly Available Server with that of the performance of a Standalone Server.

For more details on Shared HA including setup instructions, refer to section 5.5 in Fiorano SOA User Guide.

TOP

What's Changed?

The following changes are included in the Fiorano SOA Platform 9.0.2 release: 

Changing password for Admin user

• Exception while Subscribing/Browsing messages on service instance ports after changing admin user password in Peer Server. Browse/subscribe messages action on service instance ports will now use the username/password specified in the corresponding port properties.

• If source and target Peer Servers of a route are not same, route creation will use the username/password specified in the target port to create connection with the Target Peer Server.

Note: If Target Peer Server and Source Peer Server are same, username/password property is not used.

TOP

Resolved Issues

This section describes some of the customer issues resolved in the Fiorano SOA Platform 9.0.2 release.

• Exception while adding breakpoint on a route after changing admin user password in Enterprise Server.

• Pre-built components do not use username and password passed in JVM arguments for creating JMS connections.

• Passive Server takes approx. 20 minutes to become Active in case Active Server goes out of network when Lock File is on Linux machine.

  To resolve this, share and mount the Lock File using NFS4.

• Unable to start Enterprise Server after copying Event Process Repository from Fiorano SOA 2007 SP7 to Fiorano SOA Platform 9.0.x versions.

• Unable to delete a service from service repository of Enterprise Server after registering it when Enterprise Server is running on Windows machine.

 

Release 9.0.1

 

What's New?

This section list all the new features added in Fiorano SOA Platform 9.0.1 release.

• On Route Transformation support with Event Process Orchestration. This feature can be used to minimize the number of XSLT components used in an Event Process.

• Shutdown scripts for Enterprise Server and Peer Server have been enhanced to include an option to shut down both Primary and Secondary HA Servers simultaneously using one command. Refer to section 2.3.3 and 2.4.3 in Fiorano SOA User Guide for more details.

Note: In case HA profiles from previous versions are migrated to current version of the product, these profiles need to be re-configured to specify BackupRMIServerPort property to make use of this functionality.

• ClearDB scripts for Enterprise Server and Peer Servers have been enhanced to include more options while clearing the database. Refer to section 2.3.6 and 2.4.6 in Fiorano SOA User Guide for more details.

• Improved documentation for following components - DBQuery, DBProc,DBQueryOnInput, POP3, FTP, SMTP, MQSeries In, MQSeries Out, WSStub, SimpleHTTP, HTTPStub, HTTPReceive, HTTP Adapters, Exception Listener, File Reader, FileWriter, Cache, CBR, Join, XSLT, XMLSplitter, XMLVerification, Aggregator.

• Ability to register for SNMP and SMTP alerts for Gateway Machine Up/Down events when running Enterprise Server in HA mode. Configured alerts will be sent whenever Gateway machine configured for HA Enterprise Server goes down/comes back.

To listen for Peer Server Gateway Machine Up/Down notifications, user may register a notification listener with Peer Server using sample 'GatewayJMXNotification.java' provided in $FIORANO_HOME/esb/samples/Utilities.

• Added utility programs to perform following operations:

• Read BLOB/IMAGE data from Document Tracking database.

• Subscribe to Fiorano System Events etc.

These utility programs are available under $FIORANO_HOME/esb/samples directory.

TOP

What's Changed?

The following changes are included in the Fiorano SOA Platform 9.0.1 release: 

• HA Alogrithm:

To give preference to ACTIVE server to remain ACTIVE in case of network failure between HA servers, following changes have been done:

1. ACTIVE server tries to re-acquire lock on the LockFile after each configured interval.

2. PASSIVE server will wait for a specified time before trying to acquire the lock on LockFile in case of a network failure between HA servers.

Additionally, Gateway Server IP address and port properties needs to be specified for HA profiles. This has been done to detect network failure between HA server machine and gateway machine.

Note: Gateway Machine is the machine hosting the LockFile. For more details, refer to Chapter 5 in Fiorano SOA User Guide.

• Server profile structure has been changed since Fiorano SOA 2007 and SOA 9.0.0 releases. Users of Fiorano SOA 2007 SP5 or above may use the migration scripts provided under $FIORANO_HOME/antscripts/migration to migrate server profiles from older versions to SOA 9.0.1 version.

• Document Tracking queries used by ESB Webconsole will not be automatically fired on its startup. The queries can be manually triggered by a button provided in Webconsole for this purpose. This has been done to enable faster loading up of Webconsole when amount of Document Tracking data present is huge.

TOP

Resolved Issues

This section describes some of the customer issues resolved in the Fiorano SOA Platform 9.0.1 release.

• Unable to replace properties in an Event Process file using Command Line Interface (CLI).

• Unable to export Event Processes along with used Libraries using Command Line Interface (CLI).

• Unable to change log levels of Peer Server at run-time.

• Mapper generates an unwanted empty element in the output message if that element was just selected in the mapper output structure while configuring.

• MQSeries Out - In case of RawText Output Mode, if the Message Count is specified as 'n', only the nth message is retrieved and the remaining messages are discarded.

• No exception shown in Studio when changing password for a JMS User fails.

• JMSIn component does not startup once stopped after trying to send a message to a destination with negative permissions set for the user sending the message.

Security exceptions are not reported when sending messages to a destination with negative permissions set for the user sending the messages.

Note: In case the message being sent is Non-Persistent, Security exception will be reported if 'BatchingEnabled' property has been set to false in the connection factory being used by the connection. The exception may not be reported otherwise.

• Exceptions in Enterprise Server while sending SNMP traps for System Events. The issue was observed only with specific configurations of Linux Machines.

• Unable to import applications whose version value is not in the format n.0

• Incorrect calculation of execution time at document tracking ports.

• NullPointerException in saving profile configurations using FPS-JMX after editing certain properties.

TOP

 

Release 9.0.0

What's New

This section list all the new features added in Fiorano SOA Platform 9.0.0 release

Fiorano SOA Platform 9.0.0 comes with brand new eclipse based Studio called as eStudio - beta version along with previous version of Studio.

• eStudio - beta value-added  and new features

  • Offline application development

    With eStudio, event processes can be developed without connecting to any enterprise server. Enterprise server connection is required only when event processes have to be deployed.

  • EPLCM (Event Process Life Cycle Management)

    Allows user to move an Event Process in different labeled environments - Testing, Staging, QA, and Production - at the click of a button. Pre-created profiles for each environment are automatically picked up by the Server at the deployment time.

  • Subflows

    Concept of subflow (inserting an event process in another event process) is provided to ease composition of large applications.

  • Improved Debugger implementation

    Message injection is added to debug view.

  • Split file format for services and event processes

    ServiceDescriptor and Event process files are changed to split file formats which makes them more readable and reduces memory foot print of eStudio.

  • Service Descriptor Editor

    Simplified editor to edit services.

  • Faster CPS launch

    CPS launch is faster compared to previous versions.

  • Option to save incomplete service configurations

    Users can save and close the CPS of components even without providing complete configuration details.

  • New mapping tool: eMapper

    eStudio incorporates a brand new mapping tool developed ground-up in Eclipse. This new version fixes many bugs over past versions and has several other enhancements.

  • Different perspectives for mapper and event process developement

    eStudio incorporates different perspectives for mapper and event process development. Mapper need not be launched as a separate tool.

  • UI crafted for rich user experience

    Significant user feedback has been incorporated within eStudio to provide a rich user-experience. Most common operations can now be performed with a single click, with much less navigation than in previous versions.

  • Support for version control systems

    Users can now store applications into any version control system (SVN, CVS, or VSS) using Fiorano eStudio

  • Customization possible as an advantage of eclipse based product

    Since eStudio is developed over the Eclipse platform, users can now write their own plug-ins to customize eStudio

• Dashboard New Features

  • Enhanced and improved User Interface.

  • Added support for deleting system events and SBW events (also known as Document tracking events) through an interactive UI based on various filters.

  • Added ability to search for the exceptions/errors occurring in Fiorano Event Processes.

  • Added ability to view complete SBW message when double clicked on a search result appearing in Document tracking search tab.

  • Added support to show component performance monitoring data in both tabular view and graph view. The feature provides options to plot real time performance data as well as historical performance data for the chosen component.

  • Support for displaying Event Process configuration data for various environments in a single view.

• Event Process Life Cycle Management

  Event Process Life Cycle management refers to deployment of an event process in various environments i.e. Development, Testing, Staging and Production. Instead of creating new event processes for different environments, the user can specify the properties for service instances in an event process for various environments. This feature facilitates easy migration from one environment to other environment.

• Performance monitoring in JCA based components

  All JCA based components are provided with an option to publish performance data - min time per request, max time per request, average time per request and number of requests - after configurable time intervals, as events. These events can be viewed in dashboard

• Web Service Consumer 5.0 enhancements:

  • Proxy support is added.

  • Option to specify HTTP protocol to be used.

• Single Script to shut down HA servers

• BC Framework: Added an option to configure a component to discard connection on connection error.

• A new file version.properties containing build details has been included as a resource to each component.

• Javadocs for Fiorano SOA Runtime & Client Library (RTL) and Data Modeling Interface (DMI) for Fiorano SOA resources are now shipped with the installer.

TOP

What's Changed?

The following changes are included in the Fiorano SOA Platform 9.0.0 release: 

• Application and service descriptor xml files have been changed to multiple files to improve readability and reduce memory footprint of tools

• Schema for document tracking database tables has been changed to use just one table as opposed to 2 tables used earlier.

  Note: Please contact your sales representative for a migration utility to merge the SBW database tables.

• Default value of SNMP Agent port in Enterprise server has been changed to 1161 from 161 and the property has been made configurable.

• Logic for determining state changes in HA servers is changed:

  • Previous releases: State change is determined by a ping between the HA servers. In event of ping failure between HA servers, ping from HA server to gateway server is used.

  • This release onwards: State change is determined by a ping between the HA servers. In event of ping failure between HA servers, exclusive lock on a file on third machine is used.

  For more details, please refer to Chapter 5 in Fiorano SOA User Guide or Online Help.

• In-Memory Class Loading approach has been changed. Until SOA2007SP7, In-Memory service launch creates cached Hierarchical Class Loader. While this approach saves a lot of memory, it also had two known issues:

  1. User has to take utmost care while setting the dependencies of the services in order to resolve class path issues.

  2. If multiple instance of same component is launched in Memory, as class loaders are cached, each instance use the same class loaders. Hence any static variables are shared across multiple service instances.

  Fiorano SOA Platform 9.0.0 onwards, another approach is added for In-Memory service class Loading. This is UnCached Single URL Classloader approach. This solves the two problems addressed in Hierarchical class Loading. User has been given the option to choose between these two approaches. For more details, please refer to Section 3.4.8 In-Memory Launch in Fiorano SOA User Guide or Online Help.

TOP

Resolved Issues

This section describes some of the customer issues resolved in the Fiorano SOA Platform 9.0.0 release.

• Unable to browse messages on a queue from Studio when peer server is running on multi-homed machines

• Unable to register a service exported from studio, using 'ant register'

• CRC on windows times out when using In-Memory components

• Messages from ON_EXCEPTION port of WebServiceConsumer component version 4.0 are not compatible with the ON_EXCEPTION port schema

• HA Peer Server goes Out Of Memory in case of network failure

• Document tracking does not work with H2 database

• SBW DB connection tries to revalidate infinitely without any delay between successive attempts eating up CPU cycles when database is down

• Can not add Interceptor on routes when Enterprise server is running on multi-homed machine

• Schema errors in WSStub component when the schema provided contains <xsd:extension> elements

• Exception occurs while adding interceptor to a route with remote service instance

• Fiorano Mapper: Mappings cannot be pasted in funclet area of an output node which doesn't have any mappings defined

• FTPPut: No option to specify that temporary target directory on FTP server is not mandatory

• Cannot add Interceptor on routes when Enterprise server is running on multi-homed machine

• Perl script: Incorrect processing of messages in scheduler mode

• FTPGet/Put: Files are getting overwritten in processed directory while monitoring

• DB: Can't insert Clob data type using Oracle 11G and its jdbc driver

• SNMP MIB file structure was not consistent with SNMP trap definitions

• Enterprise Server does not start if SBW version table is truncated

• Sometimes value for number of tracked documents is not accurate in dashboard

• HA Enterprise server does not restore to previous state in case of network failure

• Unable to boot the enterprise server on change of password for the user 'anonymous' and cannot delete the user

• Resetting Studio deletes created server configurations

• ClearDB script for peer server does not work when Fiorano is installed as workstation

• Profiles cannot be imported using Studio

• [FTP] "TimeOut" property doesn't work

TOP

Product Documentation

The Fiorano documents are also available at Fiorano Documentation Center

Document Name	Description
Fiorano SOA User Guide	The Fiorano SOA User Guide has been developed for all users including advanced users who are familiar with using API documentation and runtime libraries to create, customize, test and deploy business components after testing their behavior. This guide comes in 2 formats, PDF format and WebHelp format.
Fiorano eStudio User Guide	The Fiorano eStudio User Guide has been developed for all the users who want to create application, flow, event process, and so on. This guide gives you a detailed description on all the functionality for running and using eStudio.
Getting Started	This document lists the steps required for simple installation and usage steps for setting up an ESB server and ESB peer on a single box, adding another ESB peer to the ESB network, and using Business Components.

TOP

System Requirements

Product	Operating Systems	Java	Minimum Hardware	Recommended Hardware
ESB Server	Windows NT Server 2003, Red Hat Linux 4, HPUx 11i, IBM AIX 5x, Solaris 10	1.5 and above	512 MB RAM 750 MB disk space 1 CPU	2 GB RAM 10 GB disk space 2 CPU
Peer Server	Windows NT Server 2003, Red Hat Linux 4, HPUx 11i, IBM AIX 5x, Solaris 10	1.5 and above	512 MB RAM 500MB disk space 1 CPU	8 GB RAM 10 GB disk space 4 CPU
Fiorano Studio	Windows NT Server 2003,	1.5 and above	128 MB RAM 500 MB disk space 1 CPU	512 MB RAM 500 MB disk space 1 CPU
	Red Hat Linux 4, Solaris 10	1.4
Fiorano Tools	Windows NT Server 2003, Red Hat Linux 4, Solaris 10	1.5 and above	128 MB RAM 500 MB disk space 1 CPU	256 MB RAM 500 MB disk space 1 CPU

TOP

Customer Support

• Evaluation Support: presales@fiorano.com
• Submit and track your support issues at http://support.fiorano.com

This requires a valid login; please contact your sales representative for an account on the Fiorano Support Portal.

TOP

Phone Support

United States:

1-800-663-3621 (Toll-Free within the USA) or +1-650-326-1136 (9 AM to 5 PM Pacific Time)

Asia Pacific:

+91 80 40170000 (9 AM to 5 PM India Standard Time)

Japan:

+81 3 5464 3874 (9 AM to 5 PM Japan Standard Time)

Europe and Middle East:

+44 (0) 1932 895005  (9 AM to 5 PM London Standard Time)

TOP

Copyright © 2008-2010, Fiorano Software Pte. Ltd. and affiliates. All rights reserved.