Product Name: Fiorano SOA Platform ™
Version: 9.4.0
This document contains important information about Fiorano SOA
Platform 9.4.0 release.
These notes are the most current information for the product and take precedence over all other documentation.
Note: To upgrade your current Fiorano environment to Fiorano SOA Platform 9.4.0, please refer to
Fiorano Migration Guide located at $FIORANO_HOME/migration/FioranoSOAMigrationGuide.
Release 9.4.0
What's New?
This section lists all the new features added in
Fiorano SOA Platform 9.4.0 release.
Adapters
eStudio
1.
Patch to Install/Uninstall
64bit JVM
Patch to install/uninstall 64bit JVM
libraries in eStudio is available for
download at
http://www.fiorano.com/latest/soa/.
Using this patch the libraries can be
installed or uninstalled by executing a
single command.
2.
Flat File Schema Editor tool to
define flat file schemas used for text
to xml conversion is added in eStudio.
More enhancements have been made in the
tool to generate the schemas based on
the sample flat file data.
3.
Support to add xsi:type
attributes to the transformed output XML
is provided in Fiorano eStudio Mapper
4.
Option to generate empty output
elements when no mappings are defined is
added in Fiorano eStudio Mapper.
5.
Standalone ESB tools like
Deployment Manager, Event Manager and
License Manager are available in Fiorano
eStudio.
6.
Visual clue on routes and
component ports is shown when a message
selector is configured on them.
7.
Support to transform FIX message
to any XML message and vice-versa is
provided in the eStudio Mapper tool. A
list of different FIX versions and
message types is displayed where the
messages to be transformed can be chosen
and the mappings can be defined on the
loaded schemas.
Supports repeating groups and custom
message types.
ESB
- New 'Component Low Memory Policy' can be configured to receive Alerts when Component Memory reaches critical limits.
- Document Tracking Workflow counters Reset button can now be reset while keeping the Documents in the Database.
- SNMP Traps can now be received for HA state change events.
TOP
What's Changed?
The following changes are
included in the Fiorano SOA Platform 9.4.0 release:
-
Subject and
Body for Monitoring Policies can
now be specified in the Policy
configuration itself, enabling
reuse of Alerts.
-
Dashboard
contents are cleared when after
Enterprise Server disconnects
-
The Low
Memory Policy now has a time
interval field to manage the
frequency of received alerts.
-
The
Security Datastore can no longer
be cleared from clearDB scripts.
The same can be achieved from a
provided option in Dashboard's
Security tab.
-
For Servers
running in background mode on
Linux, the runContainer logs are
now created in the respective
runtimedata directories instead
of profiles directories.
-
Search
capability is provided in
eStudio profile manager to
search for server profile
component instances.
-
Clearing Logs of Enterprise and
Peer Servers from Studio will
now clear the corresponding MQ
logs as well.
-
Increased
efficiency of Document Tracking
search from Dashboard.
TOP
Resolved Issues
This section describes some of the customer issues resolved
in the Fiorano SOA Platform 9.4.0 release.
-
[DB]
Timestamp is not updated
properly when an exception is
thrown while executing a
statement in PostgreSQL.
-
[WorkListManager]
Node on which the component has
to launched changes when logged
in from explorer.
-
Multiple output messages are
sent for a single message when
multiple sessions are used on
input port of
WebserviceConsumer[5.0], XSLT,
XML2PDF, PRINTPDF and EDBC
custom components
-
[DB] Extra
new lines appear if a new line
is added to the query in eStudio
CPS.
-
[JMS
Replier] Component does not
start if number of retries is
set to -1.
-
[CCP] Peer
server does not release CPU
cycles when CCP enabled
components launched in in-memory
launch mode are stopped.
-
[DB] "Map
To" column is not populated for
insert query while configuring
upsert.
-
[BC
Components] Peer server thread
count increases when components
launched in in-memory mode and
restarted
-
[File
Writer] Component overwrites
files when the property Append
on timeout is enabled.
-
[SAPR3]
Dynamic input does not work when
"Use Connection Details From
Input" set to yes.
-
[Join]Properties
"Use properties and headers
from" and "Prefer properties and
headers from" does not work
-
HTTPStub
and RESTStub components do not
work when password for user
Aryton is changed.
-
[DB] Cannot
insert null values for SDO_POINT
type in SDO_GEOMETRY for Oracle
DB
-
[HttpReceive]
Error actions configuration is
not serialized in nStudio
-
[MSMQReceiver]
Chinese characters are received
in garbled state.
-
[BC
Components] Minor memory leaks
in BC Components
-
[DB]
Component does not support
Stored Procedures with Object
data type parameters.
-
[DB] Zero
SQL decimal converted to
scientific notation for MS SQL
Server
-
[JMS 5.0]
Connection Failure error Actions
like try reconnection, stop
component do not work
-
[POP3]
Component does not delete mails
from server even though property
"Leave messages on server" is
set to no
-
Native libraries(if any) loaded
during component configuration
are not unloaded after the
configuration is finished.
TOP
Release 9.3.0
What's New?
This section lists all the new features added in
Fiorano SOA Platform 9.3.0 release.
Components
-
RESTConsumer -
New component to consume RESTful
webservice.
-
RESTStub
- New component to expose an
event process as a RESTful
webservice.
-
HTTPStub - Basic
authentication support
-
FTP
Named
Configuration
This feature eases up the process of
configuring Event Processes.
Configurations from an event process
can be saved against some name in
configuration repository and then it
can be referred in other Event
Process/component configurations.
Also, eases up the process of change
management where changes can be just
done at one single place in
configuration repository and it gets
reflected across all Event Processes
referring to that particular
configuration. This feature applies
to route, port and service instance
configurations. Refer to Chapter 14:
Named Configuration in SOA User
Guide for more details.
eStudio
-
Admin
Connections - Provision to
connect to Fiorano Servers (FMQ,
FES and FPS) to view JMS Objects
like Destinations, Clients,
Connection Factories etc is
provided.
-
JMX
Connections - Provision to
connect to Fiorano Servers (FMQ,
FES and FPS) to change JMX
properties at runtime and to
invoke JMX operations is
provided.
-
Support to define default log
manager settings is provided in
eStudio preferences. These
settings will be applied to all
the newly added service
instances in the Event
Processes.
-
Option to
use XSLTC transformer factory is
provided in eStudio Mapper and
in on-route transformations to
reduce the transformation
processing time.
-
Support to launch using a
specific java version is
provided for Separate Process
and Manual launch modes of the
components.
-
External CPS launch components
in eStudio (XSLT, CBR,
Aggregator etc) can be
configured to launch using a
specific java version.
-
Profile
Management
Added support to configure Server
Profiles
Component
Creation
Option to
support variables in .classpath and
build.properties file
Option to generate model objects
based on the port schemas of the
custom components.
Document Tracking
Whenever an application is deleted,
the user is provided with an option
to delete the tracked document
records, events etc for that
application.
Dashboard
Dashboard now shows memory usage of
CCP (Component Control Protocol)
enabled components.
Backlog
Policy
A single backlog policy can now
specify multiple threshold values
for which alerts should be sent as
opposed to single threshold per
policy for previous versions of the
product.
Libraries
An endorsed lib
directory has been setup which is
present at $FIORANO_HOME/esb/lib/endorsed
where all the jars to be endorsed by
servers/components and tools can be
put up.
Servers
A new
configurable option has been added
to Enterprise and Peer Server
profiles using which Jetty Server
launch can be avoided at the time of
server startup.
TOP
What's Changed?
The following changes are
included in the Fiorano SOA Platform 9.3.0 release:
-
HTTPStub -
Connection pooling is removed since
the component now uses a single
connection.
-
At the time of
CRC, Peer Server intelligently
recognizes the changed services
automatically even if cache
component is set to yes and
re-fetches those changed services
from Enterprise Server.
-
The system
library jaxp 4.0 is removed. The API
is shipped with JDK 1.5.
-
Components
which stops functioning due to some
condition (like scheduling mode,
error handling condition, etc.)
preserve their stopped state after
Peer Server restart.
-
Names of log
modules are changed in some
pre-built services. User might have
to redo the changes to log levels of
these components:
-
Aggregator, Cache, CBR,
DiskUsageMonitorService,
Display, DistributionService,
ExceptionListener, Feeder,
HL72XML, XML2HL7, HttpReceive,
HttpStub, JMSReplier, Join,
Sleep, Timer, XMLVerification.
TOP
Resolved Issues
This section describes some of the customer issues resolved
in the Fiorano SOA Platform 9.3.0 release.
-
Encryption/decryption on route does
not work properly.
-
[HttpStub] Component stops after
processing the first request when
Connection pooling is disabled.
-
Sometimes, components in a running
Event Process stop automatically
after running successfully for a
long time.
-
Some issues with JMS message
selector on a component in-port.
-
[JMSRequestor 5.0] Schema configured
for request gets set on the response
port.
-
Exception
Listener fails when the event
process of the exception causing
components are restarted.
-
SSL enabled
WSStub components exported from SOA
9.0.1 or earlier can not be
launched.
-
[Web Service
Consumer 5.0] Number of file handles
keeps increasing until GC.
-
[DB] Data
duplication occurs when fetch size
is greater than zero in case of
PostgreSQL database.
-
Components are
not shown in running state when an
Event Process is launched whose name
starts with T_ or Q_.
-
In Linux
machines, servers can not be started
if installation directory has spaces
in its path.
-
Unable to run
server service as non-root user in
Linux machines when logged-in as
root.
-
Unable to add
User Defined javascript function
from route transformation mapper.
-
Enterprise
Server does not startup when SSL is
enabled over HTTP protocol for
Enterprise Server profile. As a
consequence, FES and Peer Servers
can not be configured to talk
securely over an SSL channel.
-
Custom
Component creation fails when using
foreign (Japanese, accented etc.)
characters in the custom component
creation wizard.
-
Event Processes
which have components running on two
peer servers, one of which is SSL
enabled and the other is not, can
not be launched if there is a route
from SSL enabled Peer Server to the
non-SSL enabled Peer Server.
-
Static external
schemas present in a service are not
deployed when the service is
registered with Enterprise Server.
-
Release 9.2.2
What's New?
This section lists all the new features added in
Fiorano SOA Platform 9.2.2 release.
Web service support enhancements
-
Support in WSStub to define multiple operations in a single web service.
-
Support in Dashboard for multiple operations in a single web service.
-
Support in WSStub to create a web service from a predefined WSDL.
-
Support for SOAP 1.2.
-
Input and output messages confirm to SOAP schema.
-
New WSStub CPS catering for both experienced and new users of WSDL.
-
Optimizations, performance improvement and improved error handling.
Wrapper libraries upgrade
-
Support for 64bit Windows, Linux, Solaris, Mac platforms.
-
Support for sending email(non SSL) alerts based on certain predefined
wrapper events indicating jvm state.
-
Support for generating automatic thread dump when jvm stops
responding.
-
Support for managed shutdown of all orphan child processes
in case of unexpected jvm exit.
Components
-
[HTTP and WebService] Options to accept server certificates
and ignore hostname mismatches when using SSL.
-
[JMSRequestor] Messages received on error destination contain
a property IsErrorResponse set to true.
eStudio
Dashboard
TOP
What's Changed?
The following changes are
included in the Fiorano SOA Platform 9.2.2 release:
-
Classpath of components now includes directories that
contain normal files as resources.
-
SBW Events are not sent to RTL by default. This behavior
is configurable in FES profile via the expert property named 'RTLToReceiveSBWEvents'
present at node 'Fiorano -> Esb -> Sbw -> SBWManager -> SBWManager -> config'.
-
Jetty has been upgraded from version 6.1.5 to version 6.1.25
for improved security.
-
[XSLT] XSLT engine in CPS will not be populated with XSLT
engine configured in mapper UI (view->Xslt Properties) on closing mapper.
TOP
Resolved Issues
This section describes some of the customer issues resolved
in the Fiorano SOA Platform 9.2.2 release.
-
Weak network link between HA servers sometimes leads to failure
in message replication or cause some modules to malfunction.
-
Components fail to launch with InstanceAlreadyExistsException when
using JDK 1.6.18 or above.
-
States of running applications are not restored on Enterprise Server
restart in rare cases.
-
Breakpoints that are removed sometimes re-appear when Enterprise Server
restarts after an improper termination.
-
HA Enterprise Servers do not switch to ACTIVE/PASSIVE states if
application/component/alert/policy repository synchronization fails, thus requiring manual
intervention to bring servers to consistent states.
-
If a service in the Enterprise Server's repository is corrupted,
reregistering that service does not work unless the Enteprise Server is restarted
-
Enterprise Server loads all the applications in memory even if
they are not launched leading to a high memory usage.
-
Event Process Already Running exception occurs while launching
an Event Process in following scenarios:
-
Normal files added as resources to service dependencies are not
available in the classpath. Example: tcEXPRESS.ini file for connecting to DB2.
-
[DB] Ping SQL is not saved.
-
[HTTPReceive] Resource base for providing static content is not working.
-
[WebServiceConsumer:4.0] Elements that are defined in default
namespace in the WSDL are incorrectly defined in the targetNamespace of the schema set on ports.
-
[JMSRequestor:4.0] Input schema does not contain JMS header elements
when configured for XML messages.
-
EStudio
-
[WSStub] Messages sent to failure port are lost.
-
[WSStub] Improper error notification mechanism:
-
Messages sent to failure port are not treated as errors
unless the message is an XML containing element Error.
-
Messages sent to response port are treated as errors if the
message is an XML containing element Error.
TOP
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
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
-
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
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
For more information, refer to chapter 12 Audit
Management in Fiorano SOA User Guide.
Component Control Protocol
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
Component Creation
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
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
Dashboard
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
TOP
What's Changed?
The following changes are
included in the Fiorano SOA Platform 9.2.0 release:
-
EDBC
Framework
-
[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:
-
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
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.
-
Unable to install Enterprise Server as a service on windows platform when value to mode argument is provided in upper case.
-
Changes in component code are not reflected at runtime if the component is running In-Memory.
-
Exception in sequence stop and start, an Event Process after applying a backlog monitoring policy.
-
Backlog policies do not work for user-defined destinations.
-
Unable to purge messages on service instances port using Queue Browser window.
-
Unable to browse/receive messages on service instances port which does not allow anonymous user to browse/receive the messages.
-
Exception while removing debugger from a route after changing password of anonymous user.
-
Messages do not flow through route when source and target components are on different Peer Servers and the target destination is a user defined destination.
-
[C# component] Custom C# component do not copy message properties from input message to output message.
-
[MQSeries] MQSeries components do not recover from connection errors.
-
[MQSeriesIn] Messages sent from MQSeriesIn component in text mode without variable data defined in RFH structure have additional characters at the beginning of the payload.
-
[Join] Unable to launch Join components in in-memory Mode.
-
[FileReader] FileReader scans entire source directory for the required file even when there are no wild characters in the file name.
-
[JMSAdapters 5.0] Unable to export 5.0 versions of JMSIn, JMSOut and JMSRequestor components.
-
Properties that are encrypted in environment files are not decrypted correctly. Ex. Password field in DB component is changed when the CPS is reopened.
-
Event Process created in Fiorano SOA 2007 SP7 or earlier versions cannot be opened in eStudio.
-
Profiling in eStudio for Event Processes created in nStudio was not working properly.
-
Error handling actions configured for components in eStudio do not work correctly.
-
Cannot select some output ports of CBR component when the number of routing rules are greater than 3.
-
On English version of OS with language settings changed to Japanese and Japanese fonts installed, component name and note are not displayed properly when the text provided is Japanese.
TOP
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.
For more
information on Queue Depth monitoring, refer to Chapter
11 Backlog Monitoring in
Fiorano SOA User Guide.
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
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.1.0 version.
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
Authentication details in the properties of ports of
components are
removed. Authentication details of the user logged in will be used instead.
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.
Support for RFH2 headers.
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.
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
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.
o
Support for groovy
script 1.6.1
o
Support for java script
1.7
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 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.
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:
To give preference to ACTIVE server to remain
ACTIVE in case of network failure between HA servers, following changes
have been done:
-
ACTIVE server tries to re-acquire lock on the
LockFile after each configured interval.
-
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:
-
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:
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:
-
User has to take utmost care while setting the
dependencies of the services in order to resolve class path issues.
- 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
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. |
|
Fiorano SOA Installation Guide |
This document provides instructions on how to
install Fiorano SOA Platform. |
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 |
2 GB RAM
5 GB disk space
1 CPU |
4 GB RAM
10 GB disk space
2 Dual Core CPU |
|
Peer Server
|
Windows NT Server 2003, Red
Hat Linux 4, HPUx 11i, IBM AIX 5x, Solaris 10 |
1.5 and above |
2 GB RAM
5 GB disk space
1 CPU |
8 GB RAM
10 GB disk space
2 Dual Core CPU |
|
Fiorano Studio and Tools |
Windows NT Server 2003, Red
Hat Linux 4, Solaris 10 |
1.5 and above
|
1 GB RAM
1 GB disk space
1 CPU |
2 GB RAM
2 GB disk space
1 Dual Core CPU |
|
TOP
Customer Support
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-2011, Fiorano
Software Pte. Ltd. and affiliates. All rights reserved.
This software is the
confidential and proprietary information of Fiorano Software ("Confidential
Information"). You shall not disclose such Confidential Information and shall
use it only in accordance with the terms of the license agreement enclosed with
this product or entered into with Fiorano.
|