Tib Amx Service Grid Release Notes

TIBCO ActiveMatrix® Service Grid

Release NotesSoftware Release 3.0.0May 2010

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIB, TIBCO, TIBCO Software, TIBCO ActiveMatrix, TIBCO Adapter, TIBCO Administrator, TIBCO Enterprise Message Service, Predictive Business, Information Bus, The Power of Now, and TIBCO Rendezvous are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. PLEASE SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 2005-2010 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 3.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

TIBCO ActiveMatrix Service Grid Release Notes

iv | Contents


| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Known Issues, page 5


2 | Release Notes

New Features

This section lists features added since the last release of this product.

Release 3.0.0• “Out-of-the-Box” policy enforcement

• Thread pool control and management at the individual service level

• Removed direct dependency on database connection

• New shared resources: (Hibernate, SMTP, and so on)

• OSGi-based container architecture

• Context propagation

• Support for intents

Administrator

• Component level life cycle management and control

• Late binding of endpoints

• Promotion of bindings to enterprise level

• Hot upgrade of components and bindings

• Centralized distribution of software and remote provisioning

• All administration commands and actions are available through Ant tasks

• Wire services across environments

• Graphical view and navigation for administration objects

• Dashboard view for basic monitoring and management

Business Studio

• Composite implementation type – reuse components in ActiveMatrix composites

• Composite debugger

• Declarative policy intents


New Features | 3

• QOS intents

— At least once

— At most once

— Transacted one way

• Logical distribution editor

• Fully scriptable composite creation including create and import projects, create and distribute DAAs

Java

• Transaction support across multiple Java based components running within the same Java-based node (same JVM)

• Access to request context

Mediation

• Support for ActiveMatrix 3.0 Intents

• AutoMediate Tool – Support added for ANT tasks.

• Custom XPath functions – Support for creating custom XPath functions.

• Improved wizards for creating custom mediations tasks.

• Mediation Fault Path – Includes a timeout fault that catches any timeouts encountered while executing the target operation.

• gXML: a Java API for the XQuery Data Model (XDM) and eXtensible Markup Language (XML) Processing. gXML provides a cohesive suite of XML processors including XPath, XSLT, and XQuery.

• Support for multiple message exchange patterns.

• Manage Context – Access security and context information directly within mediation flows.

Spring

Spring components conform to the SCA 1.0 final draft spec for Spring components:

http://www.osoa.org/download/attachments/35/SCA_SpringComponentImplementationSpecification-V100.pdf?version=1




4 | Release Notes

and thus supports the following elements used in the Spring ApplicationContext XML file.

— <sca:property> for injecting properties into Spring beans

— <sca:service> for exposing a Spring bean as a service

— <sca:reference> for consuming the service via a reference

• Spring components allow you to set the ThreadContext ClassLoader during runtime. The ThreadContext ClassLoader is by default set to that of the Spring component. This can be changed to either that of the bundle from which the application-context.xml is being loaded, or to none (null).

• A Spring component can be configured from an existing WSDL file, add a service, reference, or property to a Spring component, and generate Java code and Spring beans for the component. TIBCO Business Studio aalso generates the ApplicationContext XML file for the generated beans.

Web Application

The Web application component integrates Java EE web applications into the TIBCO ActiveMatrix platform. The integration conforms to the SCA Java EE Integration Specification (http://www.osoa.org/download/attachments/35/SCA_JAVAEE_Integration_V100.pdf?version=1).

• The web application component supports the Java Servlet 2.5 Specification (http://jcp.org/aboutJava/communityprocess/mrel/jsr154/index2.html).

• Support for top-down implementation - Start with a WSDL and generate a web application compnent implementation

• Support for bottom-up implementation - leverage an existing web application as a component. The existing web application could be a WAR (Web ARchive) file, WTP (Web Tools Platform) Project, or an OSGi-fied web application

• Support for properties

• Invoking a reference operation


Known Issues | 5

Known Issues

The tables in this section list known issues in this release.

Administrator

Key Summary/Workaround

AMRP-1681 Summary If a WSDL file’s schema has schema import, and the referenced schema’s schema components are not used withing the WSDLs schema section directly (but are used at the WSDL level, for example at the WSDL part level), the schema components from the imported XSDs are not resolved completely at the top level WSDL.

Workaround If the referred schemas are used from within the WSDL’s schema section to define components, and these WSDL defined schema components are used from within WSDL file (for example, at the WSDL part level), this issue does not arise.

AMRP-2090 Summary When a SOAP service or reference and a component are deployed on two different nodes, and the faultcode, faultrole are used through faultcontext mapping, there’s a serialization issue for across node communication in this specific case.

Workaround Deploy the SOAP service or reference and the component (or a component and a SOAP-Reference) on the same node so the serialization does not occur.

AMRP-2112 Summary On Windows (NTFS) the maximum file name length is 226 characters and on Linux (ext4fs) the maximum file name length is 226 bytes. ActiveMatrix uses application name, component name, nested composite name, service name and reference name as part of created folder and file names. If the maximum file length limit is exceeded, a java.io.FileNotFoundException might be thrown when applications are deployed.

Workaround Keep names short and limit the level of nested composites in an application.


6 | Release Notes

AMRP-2147 Summary If the endpoint URI of a SOAP/HTTP binding is configured as /abc/ then all URIs beginning with /abc/, for example, /abc/def , /abc/def/xyz will also be processed. This only occurs when the URI contains only the context root as in /abc/. It does not occur if the URI is specified as /abc/def/.

Workaround None.

AMSG-7243 Summary Re-installing into an existing TIBCO_HOME causes some post install Ant tasks to fail.

Workaround Do not re-install into an existing TIBCO_HOME; select a new TIBCO_HOME.

AMX-5860 Summary Every Administrator server requires a different TIBCO Enterprise Message Service server.

Workaround None.

BJMS-204 Summary Inline credentials on JMS resource templates and JNDI Connection Configuration are lost after being imported by the New Application wizard.

Workaround Recreate the credentials in Administrator.

BJMS-223 Summary When a JMS SSL connection fails, the application containing JMS SSL resource instance still shows running successfully.

Workaround Check the logs to see if the JMS SSL connection did complete successfully.

BJMS-234 Summary Adding a JMS binding is not supported in Administrator UI.

Workaround Use the Administrator CLI to create the binding.

BJMS-244 Summary When creating any of the JMS resource templates or JNDI Connection Configuration from Administrator CLI, inline credentials are not honored.

Workaround Create the JMS resource template and JNDI Connection Configuration inline credentials from the Administrator UI.

BJMS-246 Summary JMS reference that uses a SonicMQ JMS provider hangs after one processing one message.

Workaround None.



Known Issues | 7

CL-1303 Summary If you use HSQLDB as the log service database, and you set the logging level of an logging configuration to Debug, the database will crash. If you use Oracle 11g and MSQL 2008 server for the log service database with a Debug log level, performance will degrade.

Workaround Specify the cache parameter for the DB URL which is valid for only HSQL-DB jdbc:hsqldb:hsql://localhost:1234/amx1;hsqldb.default_table_type=cached.

CL-1308 Summary A SystemNode logging configuration cannot be configured to use a JMS appender. The log service runs inside SystemNode. If SystemNode's logging configuration is changed to use JMS appender, then an infinite loop will form.

Workaround Leave the SystemNode logging configuration as is, which uses a file appender.

CL-1313 Summary Model extensions logs to a JMS appender fail.

Workaround Do not use Model Extension if you intend to use a JMS appender.

CL-1319 Summary You cannot have multiple log services on multiple nodes running in the same Administrator server.

Workaround None.

MCR-521 Summary If a node is stopped or started several times while SystemNode is down, the last stop or start time of SystemNode is used to calculate the node’s uptime percentage. Other stops and starts are missed and not used in uptime calculation.

Workaround None.

MCR-572 Summary In the Dashboard > Infrastructure screens, Request Queued metric does not always reset to zero even after the requests have been processed.

Workaround None.

MCR-659 Summary If a machine is put in stand by/hibernate mode and then restarted the performance statistics aggregator does not process the messages from the TIBCO Enterprise Message Service server queue.

Workaround Restart the amx.goverance.mcr.aggregator application after the system is woken up from hibernation.



8 | Release Notes

MCR-717 Summary When a component throws undeclared faults, the following components metrics are invalid:

- Requests Queued: shows the request as queued until next node restart

- Faults, %Success, Requests Dispatched, Responses, Response Time (Avg), Fault Rate, Success, Request Rate, Comp. processed Rate: do not include statistics from requests resulting in undeclared faults.

Workaround Change business logic to catch all runtime exceptions and throw only declared faults.

MCR-732 Summary Dashboards > Infrastructure: Since started time window does not restart when application or node is restarted.

Workaround None.

MCR-753 Summary In the Dashboards > Infrastructure screens the application request count includes requests counts from all services promoted to application level. In addition, it incorrectly includes reference invocations count from all references promoted to application level.

Workaround None.

MCR-800 Summary When a component reference is promoted, component reference metrics show zero values. All metrics are shown on the promoted reference and reference endpoint.

Workaround View metrics on the promoted reference.

MCR-802 Summary Dashboards > Infrastructure. The Average Comp Process Time on Application tab is always 0.

Workaround View Average Comp Process Time statistics in Application drill down or Component tab.

PER-49 Summary When configuring an LDAP Authentication resource template in Administrator, the option to generate SAML 1.1 assertion is not supported by platform policies.

Workaround When configuring an LDAP Authentication resource template, accept the default setting to generate SAML 2.0 tokens.



Known Issues | 9

PER-586 Summary Incorrect behavior when deploying or redeploying a DAA that contains policy sets

Deploy, redeploy and undeploy commands in Administrator cause actions related to the DAA at the node. Within a node, the component framework (CF) arranges the application, and also requests that the governance agent (GAgt) arrange policies as specified in the DLL. However, this release has a defect in the communication between CF and GAgt, which affects the following three cases.

PER-586 Case 1 Situation Deploy a DAA. The application deploys correctly and runs correctly, but the policies fail to deploy.

Expected Result The entire DAA would fail. CF would automatically remove the application from the node.

Actual Result Warning. The application runs, but the policies do not. GAgt does not notify Administrator that policies failed to deploy. This case can be dangerous; for example, security policies cannot ensure encryption, nor prevent unauthorized use of the application.

Workaround After a DAA successfully deploys, review node logs for policy deployment errors, and empirically test whether critical policies are operating as expected. Node logs are on the computer where the node is running, in this location:

CONFIG_HOME/tibcohost/InstanceName/nodes/NodeName/logs/NodeName.log

If you find that policy deployment failed, stop and undeploy the application, fix the policies, recreate the DAA, deploy the new DAA, and verify policy deployment.

PER-586 Case 2 Situation Deploy a DAA. The application fails to deploy, but the policies deploy correctly.

Expected Result The entire DAA would fail. GAgt would automatically remove the policies from the node.

Actual Result Policies remain in the node. GAgt does not notify Administrator that policies are deployed.

Workaround Do not modify policies after an application fails to deploy; wait until after you fix the application in the DAA. After you fix the DAA and the application deploys correctly, GAgt reconnects the remaining policies to the application, and they operate correctly. Subsequently undeploying the DAA correctly removes the reconnected policies.



10 | Release Notes

PER-586 Case 3 Situation Redeploy a DAA after modifying properties.

Expected Result The node would update all property values.

Actual Result The node updates properties associated with the application, but not values associated with policies.

Workaround Undeploy the DAA, then deploy the updated DAA.

TAP-1593 Summary If you undeploy a Policy Agent application it fails the first time with a provisioner error.

Workaround Undeploy again using the Administrator CLI.

TAP-1603 Summary Administrator doesn’t warn if component properties are mapped to resource instances that are not existing on runtime node.

Workaround Ensure that you install all required resource instances on target nodes before deploying an application.

TAP-1605 Summary Applications that get into an unrecoverable intermediate state cannot be deleted from the Administrator GUI.

Workaround Use the Administrator CLI with force flag set to true to delete such applications from Administrator.

TAP-1616 Summary .An SMTP resource template does not accept a substitution variable for the port number with a dot(.) in it. For example, %%smtp.port%% does not work.

Workaround Use %%smtpPort%% instead.

TAP-1618 Summary .An HTTP connector resource template does not accept a substitution variable for the port number.

Workaround Use an integer value instead.

TAP-1619 Summary .An HTTP client resource template does not accept a substitution variable for the port number with a dot(.) in it. For example, %%http.port%% does not work.

Workaround Use %%httpPort%% instead.

TAP-1628 Summary .When Administrator is invoked from within TIBCO Business Studio and the default browser is Internet Explorer 8, an error pop-up displays.

Workaround After dismissing the error pop-up, the Administrator login screen appears and the Administrator UI comes up normally.



Known Issues | 11

TAP-3698 Summary On Windows, the folder containing a Tibco Host instance cannot be moved, copied, or deleted when the RuntimeWorkArea file name length is longer than 255.

Workaround Delete the folder using rmdir /s /q.

TAP-3900 Summary Substitution variables used in the Connection Properties section of the JDBC XA resource template configuration are not being substituted by Administrator.

Workaround None.

TAP-4181 Summary If resource instances are mapped to nodes through New Application wizard, the instances need to be manually installed on nodes before deploying.

Workaround Don't deploy from the wizard. Instead Save and exit from the wizard and then either Create the resource instances manually on the nodes and then deploy application or deploy the application which will open a dialog to resolve errors. Once the instances are mapped in this dialog, Administrator will automatically install the instances before deploying the application. .

TAP-4464 Summary .Administrator cannot deploy applications created from projects that have spaces in the project names.

Workaround Do not put spaces in application or project names.

TAP-4599 Summary When creating an Administrator server if the username specified in the external database configuration for an Oracle database has DBA privileges the Administrator server creation will fail.

Workaround Specify a username that does not have DBA privileges.

TAP-4602 Summary When session times out or server is becomes unavailable instead of showing timeout the Dashboard > Infrastructure screen doesn't display any data.

Workaround Click a menu item to navigate to another screen or log out.

TAP-4637 Summary The header columns in case of Component details page in the Dashboard don't show correctly.

Workaround Minimize and maximize the gadget and it should refresh the columns correctly. .



12 | Release Notes

TAP-4645 Summary In the Dashboards > Infrastructure screens, resource instances cannot be filtered by promoted reference or promoted service.

Workaround In the Application Screen, check properties of the reference or service bindings.

TAP-4707 Summary A host bound by a user who isn't superuser can't be seen by that user.

Workaround A Superuser can explicitly give the binding user owner permission to the host.

TAP-4761 Summary Administrator displays a success message if you select Infrastructure > Hosts > hostname > Security > Enable Secure Management Communication even if the Administrator is not running TIBCO Credential Server. After that, you cannot create new nodes on the host.

Workaround Restart the Administrator server and then restart the hostname host.

TAP-4771 Summary Undeploying an application that has property that references a Teneo resource instance fails.

Workaround

1. Select to Infrastructure > Nodes > nodeName > Configuration > Features.

2. Remove the feature that is pending for Uninstall.

3. Click Save.

4. Click Apply with Refresh.

TAP-4777 Summary When the components are distributed manually through the Administrator UI from the Distribution tab, and Save button is clicked the "Saving Data" message doesn’t resolve to green to say "Changes are Saved ..". even though the changes are saved correctly.

Workaround Close the "Saving Data" box and proceed.

TAP-4809 Summary While starting a node, you might observe java.io.FileNotFoundException: http://<hostname>:<port>/amxadministrator/svn/trunk/artifacts/keystore/admin_default_keystore.jceks in the node log.

Workaround Restart the node.



Known Issues | 13

TAP-4813 Summary When a binding is contained in a logical node, promoting the reference using the binding to the environment is not allowed because the binding is deleted. This is not supported.

Workaround Recreate application template without placing the reference binding in a logical node.

TAP-4834 Summary After upgrading an application, the application deployment goes into the waiting for dependencies state.

Workaround After uploading and choosing the upgraded version of the application, go to the Nodes screen, select the node where the application is deployed, and click Install. Now redeploy the upgraded application.

TAP-4835 Summary Dashboards > Infrastructure. Picking items in the filter list that are of the same type as the list being displayed are ignored. For example if you went to the application tab and there were 6 listed and then went over to the filter tab and selected 2 of them, you would expect to see only 2, but would continue seeing 6.

Workaround Type the appropriate name in the keyword filter next to the column picker icon.

TAP-4877 Summary A NullPointerException is thrown while creating service binding through the Administrator CLI if the value of "style" attribute is not specified for the binding.

Workaround Create the ervice binding using the Administrator UI, as the UI has drop-down with default value for Style attribute or provide the value for style attribute in the data file as follows:

<Binding xsi:type="amxdata_binding:SoapServiceBinding"name="soapjms.service1.binding"description="SOAP/JMS Service Binding"style="document"encoding="literal">

TAP-4892 Summary "Error in dashboard "tibco.dash.Error.Requesttimeout" window pops up when you access Dashboards > Infrastructure. This happens the first time you go to the dashboard regardless of whether or not the aggregator is available, if the aggregator application isn't running, your session times out, or the SystemNode stops or becomes unavailable.

Workaround Dismiss the pop-up.



14 | Release Notes

TAP-4893 Summary Deployment fails if a malformed feature is provisioned to a node.

Workaround

1. Select Infrastructure > Software Management > Features and remove the malformed feature from the node.

2. Select Infrastructure > Nodes > nodeName > Configuration > Features, select the malformed feature (with status as Marked for Uninstall) and click Apply with Refresh.

TAP-4899 Summary When running with Microsoft SQLServer the Administrator server becomes slower in responding after some time.

Workaround Restart the Administrator server.

TAP-4919 Summary Sometimes node gets into unrecoverable state if install/uninstall is performed several times and the node cannot be force deleted.

Workaround Contact TIBCO Global Support for assistance.

TAP-4927 Summary If you invoke the Install action on a node whose Synchronization value is In Sync the node becomes unusable.

Workaround Restart the node.

TAP-4929 Summary All of the CLI samples copied CONFIG_FOLDER/admin/enterprisename/samples folder don't work as is.

Workaround In each build file, edit the line <import file="../bin/taskdef.xml"/> and set file to point to TIBCO_HOME/administrator/3.0/bin/taskdef.xml. Edit the remote_props.properties file and set the adminURL, username, and password properties appropriately for your Administrator server configuration.

TAP-4939 Summary Permissions are not honored in the Dashboard if multiple users access Administrator from the same browser.

Workaround Restart the browser or use different browser instances.

TAP-4949 Summary Life cycle actions from the Dashboard screens don't work.

Workaround Perform life cycle actions from the respective object's configuration screen under Infrastructure and Applications.



Known Issues | 15

Business Studio

TAP-4959 Summary In some cases the gadgets in a Dashboard screen may show up as empty.

Workaround Reload the Administrator page in the browser.

TAP-4963 Summary In the New Application wizard, when you upload a DAA that is a different version of existing DAA, the wizard displays a duplicate application error.

Workaround Cancel the wizard. The error is spurious and the newly uploaded DAA is saved.

TRUP-201 Summary If you change the business name through a UDDI server's UI, Administrator does not reflect the change. So the business name in Server or UDDI publication tab will still show the old name, and another business name with that name will be created when service are published.

Workaround Only change a business name in Administrator.

TRUP-211 Summary If thefollowing tModels are deleted through a UDDI server's UI,

• uddi:tibco.com:admin:host

• uddi:tibco.com:admin:node

• uddi:tibco.com:admin:enterprise

• uddi:tibco.com:admin:environment

• uddi:tibco.com:admin:appfolder

• uddi:tibco.com:admin:application

publication will fail.

Workaround None.Those tModels, along with UDDI bootstrap tModels such as all the tModels with key prefi "uddi:uddi.org:" should never be deleted.

TRUP-212 Summary If you navigate to Infrastructure > Servers, after your login session expires an empty page displays.

Workaround Log out and log in again.



16 | Release Notes


BJMS-139 Summary If you rename an operation in a WSDL file, JMS bindings on composite services/references are not updated correctly.

Workaround Create new JMS binding after renaming the WSDL operation or re-assign the WSDL to existing JMS binding.

BJMS-192 Summary A JMS binding requires an outbound connection factory even if the MEP is in-only.

Workaround Specify an outbound connection factory resource.

BJMS-207 Summary If a JMS reference is set up for a static reply destination, the JMSReplyTo destination is not set in outgoing messages.

Workaround The consumer of these messages is supposed to know the JMSReplyTo destination offline. Also you must copy the correlation ID from request to the response.

BJMS-229 Summary Although SonicMQ is supported as a JMS vendor, the SonicMQ initial context factory and its default provider URL does not appear in the drop-down in the JNDI Connection Configuration.

Workaround Type in com.sonicsw.jndi.mfcontext.MFContextFactory for Initial Context Factory and tcp://localhost:2506 (default) or otherwise for the Provider URL.

BJMS-247 Summary For JNDI Connection Configuration resource template, you cannot switch back and forth between username/password and identity provider credentials.

Workaround Create a new JNDI Connection Configuration resource template if you want to switch between username/password and identity provider credentials.

PER-557 Summary The policy AuthorizationByRole does not support nested groups.

Suppose user A is a member of group B, which is a subgroup of group C. If group C has access permission to request an operation, and user A attempts to request that operation, then the request fails. That is members of group B do not inherit access permission from group C.

Workaround Configure access permissions directly in each subgroup (in this example, in group B).


Known Issues | 17

PER-609

PER-623

Summary Incompatible policies: UsernameTokenAuthentication and WSSProvider.

These two policies have redundant functionality, but they cannot co-exist on the same SOAP service.

• UsernameTokenAuthentication authenticates using only the username token in the WS-Security header.

• WSSProvider authenticates using any available information in the WS-Security header.

Both policies remove the WS-Security header from the message after successful authentication. If both policies are in effect at the same service, when the first one (WSSProvider) succeeds, the second (UsernameTokenAuthentication) must fail, because the WS-Security header is no longer available. This failure causes request messages with proper credentials to fail erroneously.

Workaround Do not apply the policies WSSProvider and UsernameTokenAuthentication together at the same SOAP service.

PER-632 Summary For proper policy enforcement, every composite containing a web application component must have a different context root.

Workaround None.

SDS-1415 Summary After changing the name of the composite, a launch configuration that references the composite shows composite unresolved and error that composite was not found in the workspace.

Workaround Delete the launch configuration, create a new launch configuration, and add the renamed composite.

SDS-3055 Summary Generating a WSDL file when the transport is HTTPS is not supported.

Workaround None.

SDS-3482 Summary In some cases a composite containing a web application can be launched in RAD, but will throw a NullPointerException. A dialog will display that the launch couldn't proceed because of errors in the application.

Workaround Resolve the errors in the application before launching.

SDS-3511 Summary Business Studio does not support substitution variables of the format %%keystoreURL%%/JKS/server-CAs.jks.

Workaround Set the value in Administrator.



18 | Release Notes

Java

SDS-3513 Summary SOAP services and references do not retain context mapping settings.

1. Create a promoted service wired to a component service.

2. Create two context parameters in component service.

3. Sync the SOAP binding of the composite service for context parameters and change the mapping to map the context parameters to some non-default settings.

4. Create another context parameter in the component service.

5. Sync SOAP binding and go to the context mapping.

6. The settings for the first two context mappings from step 3 are lost and gone back to default.

Same behavior for SOAP reference.

Workaround Re-enter the values that were lost.

SDS-3630 Summary In the Create deployment archive wizard unrelated features will not be packaged in the same DAA even if added explicitly through the wizard.

Workaround Configure the features to express the correct dependencies.



SDS-3621 Summary Code generation fails when the target namespace in the WSDL file forms a URI in such a way that the "host" segment can not be determined by the Java APIs The case where we have seen this happen is in namespaces on which we appended "_gen" at the end.

Workaround None.


Known Issues | 19

Mediation


MED-1525 Summary The Generate Mediation Implementation quick fix action creates an empty mediation flow file with the Create mediation file wizard.

Workaround This generic eclipse shortcut to create the implementation is not supported for mediation.

MED-1538 Summary The mapper tree in the Catch All path of Catch Target fault does not contain the Timeout fault message when you uncheck the checkbox for the Timeout fault path.

Workaround Check the checkbox for the TimeoutFault in the Catch configuration and handle it explicitly instead of handling it in the catch-all path.

MED-1652 Summary The Message type context property does not specify an unbound Message even though the selection list contains all Message elements in the WSDL. An unbound Message is one that is not used for Input, Output, or Fault parts.

Workaround Only select unbound Message elements for context properties.

MED-1702 Summary The Java primitive type byte is not supported but is available in the Custom XPath Wizard.

Workaround None at at this time.

MED-1703 Summary Creating schema using the Create button creates the schema for CMT model plugin wizard but does not set it.

Workaround Once the schema is created, you can browse and select the schema in the wizard to set it for both Input and Output Schemas in the plugin wizard.

MED-1738 Summary Error markers appear on all input and output flow paths when there is a data mismatch on at least one of the paths.

Workaround The markers disappear after updating the configuration to make the message data match and after saving the mediation flow.


20 | Release Notes

Spring

MED-1739 Summary When adding a PortType with many ( about 50+) operations, the validation begins before the mediation flow is fully updated. This causes error markers to appear on the mediation operations when no actual problems exist.

Workaround Select Project/Clear from the menubar and the validation will restart. The error markers will disappear, unless there are actual problems that remain.

MED-1827 Summary Deploying a mediation application that uses custom XPath functions and if the custom XPath function plug-in is not deployed, results in errors at the time of deployment.


MED-1844 Summary The Endpoint Reference drop-down list of the Set Dyanamic Reference task is not supported for this release.


MED-1868 Summary A MOZILLA_FIVE_HOME not set or MOZILLA_FIVE_HOME libraries not found error is seen during design time when there is a mismatch of Mozilla libraries on a 32-bit or 64-bit RedHat Linux machines. For example, when you install a 32-bit build on a 64-bit machine there's a mismatch of mozilla librarie.s

Workaround Make sure you download the correct set of libraries from the Mozilla site.



ISPR-175 Summary If the beansfile folder name is manually removed from the bin.includes section of the plugin manifest/build.properties, then the UI does not flag a validation error.

Workaround After doing a clean build on the project, the proper error marker is shown. Go to Project > Clean > Check the SOA Project name > OK.


Known Issues | 21

Web Application

ISPR-168 Summary After adding a reference to a Spring component and generating Spring implementation, the bean configuration XML file shows a "reference bean not found" warning.

Workaround None.

ISPR-165 Summary Refactoring of WSDLs/PortTypes does not work for Spring IT.

Workaround None. Once the implementation is generated, do not rename or move WSDL and/or PortType.

ISPR-133 Summary While creating a property with the reserved name that ends with an underscore (_), an error is thrown.

Workaround Do not end the property names with an underscore (_).

ISPR-134 Summary While creating a property with the reserved name, the beans.xml file throws an error.

Workaround Do not use reserved keywords for property names.

ISPR-135 Summary When using special characters in the Bean Id, the bean configuration XML file shows an error.

Workaround Do not use special characters in the Bean Id names.

ISPR-4 Summary In the spring beans xml file, when you press the Ctrl key and hover the mouse pointer over the elements of the bean tag, the tooltip text shows 'Unknown Hyperlink'.

Workaround None.



IWAP-224 Summary In the web.xml file, resource-ref elements are not supported.

Workaround None.


22 | Release Notes

IWAP-212 Summary If the Web Application component is added by right clicking on the composite, the Generate Servlet Implementation option is not available under the Quick Fixes option.

Workaround Select the Web Application component, right-click, and select Generate Servlet Implementation.

IWAP-72 Summary The WebApplication component does not have an option to modify the Web Application connector during deployment in TIBCO Administrator UI.

Workaround To configure or change the connector name in TIBCO Administrator:

1. In TIBCO Business Studio, open the project containing the Web Application component.

2. Promote the defaultConnector property to a composite level:

a. Select the defaultConnector property on the component.

b. Right-click and select Promote.

3. Make the composite property a substitution variable so it can be substituted in TIBCO Administrator before deployment.

4. Right-click on composite and select Create DAA.

5. In TIBCO Administrator, make sure a connector with the same name is created in TIBCO Administrator and deployed on to the node before the Web Application DAA is deployed.



Tib Amx Service Grid Release Notes

Documents

Transcript of Tib Amx Service Grid Release Notes