Fiorano SOA 9.0.2 Release Notes          

 

Product Name: Fiorano SOA

Version: 9.0.2

This document contains important information about Fiorano SOA 9.0.2 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.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 Fiorao SOA 9.0.2, please refer to the migration steps specified in $FIORANO_HOME/docs/Fiorano SOA Platform Migration Guide

Release 9.0.2

What's New?

This section lists all new features added in Fiorano SOA 9.0.2 release.

• Shared HA

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

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

   

• MQSeries Out Adapter Enhancements:

Support for RFH2 headers.

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

• Join Adapter 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. The resultant message can contain values for common properties only from input message on IN_PORT1 or IN_PORT2

• DB Adapter 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. The 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 Adapter 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 the other port is used to export JMX RMI connection objects. This second port is usually dynamically allocated at random. This causes a problem if the server is behind a firewall as one of the connection ports is random and 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 the 'RmiPortExportObjects' property.

• LDAP Samples to manage users, groups and ACLs when Fiorano MQ is configured to use LDAP security realm. The samples are located under $FIORANO_HOME/fmq/samples/Realms/LDAP directory.

• Utility to create/remove multiple routes across destinations for Fiorano MQ. The utility can be used in ESB environment as well to transfer messages across destinations without the need to create new Event Processes for this purpose. The utility is present in $FIORANO_HOME/fmq/Utilities/RouteUtility. Please refer to $FIORANO_HOME/fmq/Utilities/RouteUtility/RouteManagement.pdf for instructions on how to manage/create or remove the routes.

TOP

What's Changed?

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

• 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, Server will create a connection with the Target Peer Server using the username/password specified in the target port.

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

TOP

Resolved Issues

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

• Changing password for Admin user

  • Issues relating to Subscribing/Browsing messages on service instance ports and adding breakpoints on routes after changing the admin user password on the Peer Server.

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

• Failover takes unacceptable time (approx 20 minutes) in case Active Server goes out of network when the lock file is hosted in Linux Machine

• Unable to remove a service immediately after registering it with Fiorano Enterprise Server when it is running in Windows environment.

TOP

Known Issues and Limitations

Known Limitations

This section contains the list of all known limitation for Fiorano SOA 9.0.2 release.

• eStudio - Beta limitations:

  • Event processes and services created in eStudio do not work with previous version of studio and vice versa. Migration utilities will be provided with the final release.

  • Mapper cannot resolve schemas which contain elements defined in other schemas.

  • Schema editor to view schema on ports cannot resolve schemas which contain elements defined in other schemas.

  • Visual clues of service states are not reflected accurately at times.

  • User has to switch to Fiorano perspective after launching eStudio.

  • Though modification of an event process is supported, event process has to be stopped and redeployed.

  • Copy, cut, paste features are not fully supported

Known Issues

This section contains the list of all known issues for Fiorano SOA 9.0.2 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. Work around: 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	[SI: 2523] Compression and Encryption on Route not working as expected
13928	Studio does not show Component, Application and Peer repositories after continuous login/logouts. Workaround: Stop Studio and Start it again.
14056	Visual Status of the component is incorrect after FES HA 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. This particular case will be handled in next release.
14558	ClassNotFoundException while trying to connect Weblogic server remotely. JMSIn / JMSOut/ JMSRequestor adapters 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.
14796	User cannot open two FES/FPS profiles simultaneously through Studio. Workaround: Close the existing open profile and open the new profile.
14940	Application cannot be synchronized after changing port type Work Around: Stop the application to change the destination type
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.
16698	Adding interceptor on a route does not work after changing anonymous user password in Enterprise Server.

 

Release 9.0.1

 

What's New?

This section list all the new features added in Fiorano SOA 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 adapters - 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 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 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 9.0.0 release

Fiorano SOA 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 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 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 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 wants 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-408-354-3210 (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 © 1999-2008, Fiorano Software Technologies Pvt. Ltd. All rights reserved.

Copyright © 2008-2009, Fiorano Software Pty. Ltd. All rights reserved.