Release Notes

TIBCO ActiveMatrix ® Implementation Type for Microsoft CLR Release Notes Software Release 3.3.0 November 2013

Two-Second Advantage®

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 THE LICENSE FILE) 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. TIBCO, The Power of Now, TIBCO ActiveMatrix, TIBCO Adapter, TIBCO Administrator, TIBCO AutoMeditate, TIBCO Enterprise Message Service, Predictive Business, Information Bus are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or 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. SEE THE README 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 © 2011-2013 TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ix ix ix ix

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 2 2 3

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 4 4 4

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 5 5 5

Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Release 3.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 6 6 6

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

TIBCO ActiveMatrix Implementation Type for Microsoft CLR Release Notes

iv

| Contents


|v

Preface

TIBCO ActiveMatrix® is a scalable and extensible platform for developing, deploying, and managing applications that conform to a service-oriented architecture. You can create and deploy Windows Communication Foundation (WCF) service implementations to the TIBCO ActiveMatrix platform by using TIBCO ActiveMatrix Implementation Type for Microsoft CLR.

Topics •

Typographical Conventions, page vi

•

Connecting with TIBCO Resources, page ix


vi

|

Preface

Typographical Conventions The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention

Use

TIBCO_HOME

Many TIBCO products are installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

ENV_NAME

Other TIBCO products are installed into an installation environment. Products installed into different installation environments do not share components. Incompatible products and multiple instances of the same product must be installed into different installation environments. An installation environment consists of the following properties: •

Name Identifies the installation environment. The name is a component of

the path to the product in the Windows Start > All Programs menu. This directory is referenced in documentation as ENV_NAME. •

Directory The directory into which the product is installed. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME

depends on the operating system. For example, on Windows systems the default value is C:\Program Files\tibco\amx-3. CLR_HOME

The Implementation Type for Microsoft CLR installs into a directory inside ENV_NAME. This directory is referenced in the documentation as CLR_HOME. The value of CLR_HOME depends on the operating system and product software release. For example, on Windows systems the default directory for software release 3.3 is ENV_NAME\amx_it_clr\3.3\.

CONFIG_HOME

A TIBCO configuration home stores configuration data generated by TIBCO products. Configuration data can include sample scripts, session data, configured binaries, logs, and so on. This folder is referenced in documentation as CONFIG_HOME. The default location of the folder is USER_HOME/ENV_NAME/data. For example, on Windows, the default location is C:\Documents and Settings\UserName\Application Data\ENV_NAME\data.

code font

Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the foo process.


Typographical Conventions vii

|

Table 1 General Typographical Conventions (Cont’d) Convention

Use

bold code

Bold code font is used in the following ways:

font

•

In procedures, to indicate what a user types. For example: Type admin.

•

In large code samples, to indicate the parts of the sample that are of particular interest.

•

In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font

Key combinations

Italic font is used in the following ways: •

To indicate a document title. For example: See Concepts.

•

To introduce new terms. For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

•

To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C. Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q. The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances. The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result. The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 2 Syntax Typographical Conventions Convention

Use

[ ]

An optional item in a command or code syntax. For example: MyCommand [optional_parameter] required_parameter


viii

|

Preface

Table 2 Syntax Typographical Conventions Convention

Use

|

A logical OR that separates multiple items of which only one may be chosen. For example, you can select only one of the following parameters: MyCommand para1 | param2 | param3

{ }

A logical group of items in a command. Other syntax notations may appear within each logical group. For example, the following command requires two parameters, which can be either the pair param1 and param2, or the pair param3 and param4. MyCommand {param1 param2} | {param3 param4}

In the next example, the command requires two parameters. The first parameter can be either param1 or param2 and the second can be either param3 or param4: MyCommand {param1 | param2} {param3 | param4}

In the next example, the command can accept either two or three parameters. The first parameter must be param1. You can optionally include param2 as the second parameter. And the last parameter is either param3 or param4. MyCommand param1 [param2] {param3 | param4}


Connecting with TIBCO Resources ix

|

Connecting with TIBCO Resources

How to Join TIBCOmmunity TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access All TIBCO Documentation After you join TIBCOmmunity, you can access the documentation for all supported product versions here: https://docs.tibco.com

How to Contact TIBCO Support For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows. •

For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: http://www.tibco.com/services/support

•

If you already have a valid maintenance or support contract, visit this site: https://support.tibco.com Entry to this site requires a user name and password. If you do not have a user name, you can request one.


x

|

Preface


|1

Release Notes

This document includes release notes for TIBCO ActiveMatrix Implementation Type for Microsoft CLR, Software Release 3.3.0. 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

•

Changes in Functionality, page 4

•

Deprecated and Removed Features, page 5

•

Migration, page 6

•

Closed Issues, page 7

•

Known Issues, page 9


2

|

Release Notes

New Features This section lists the features added since the last major (x.0) release of this product.

Release 3.3.0 .NET Framework 4.5 Support The .NET Framework 4.5 is now supported. This framework provides backward compatibility. Platform Support The following platforms are now supported: •

Windows 8 (32-bit and 64-bit)

•

Windows Server 2012 (64-bit)

At Least Once Policy Support TIBCO ActiveMatrix Implementation Type for Microsoft CLR now supports At Least Once policy for the CLR Component. The At Least Once policy ensures that the messages are delivered at least once to the recipients in case of exception scenarios. For more information on the At Least Once policy, refer to the TIBCO ActiveMatrix Service Grid Component Development guide. Cheatsheets Cheatsheets are now added for TIBCO ActiveMatrix Implementation Type for Microsoft CLR for the HelloWorld sample project. These cheatsheets guide you through the steps to create a CLR HelloWorld project and run it.

Release 3.2.0 •

WCF Configuration File Editor Added An editor has been added to TIBCO Business Studio that can be used to add, remove, or change TIBCO ActiveMatrix Implementation Type for Microsoft CLR endpoints on a service.


New Features 3

|

For information, see the WCF Configuration File Editor chapter in the TIBCO ActiveMatrix Implementation Type for Microsoft CLR Component Development guide. •

•

WCF Client to AMX Reference Mapping Enhanced The list of available clients on the Implementation tab of the component's Properties view presents all possible clients from which you can choose. 64-Bit Design Time Support added for Windows 64-bit design-time

environment. •

Push from UNIX TIBCO Administrator The TIBCO ActiveMatrix Implementation Type for Microsoft CLR can be installed on a UNIX machine, then pushed to a Windows machine via TIBCO Administrator. See instructions in the installation guide.

•

Windows Server 2008 R2 Support for Windows Server 2008 R2 has been

added. •

Support for Security Context Propagation The security context can be

propagated from the service to the reference in cases where a TIBCO ActiveMatrix component is calling another TIBCO ActiveMatrix component. •

Runtime Installed with SOA Development Profile The runtime portion of

TIBCO ActiveMatrix Implementation Type for Microsoft CLR is now also installed when you select the SOA Development profile in the installer. This allows for testing with RAD in TIBCO Business Studio without the need to install Administration when TIBCO ActiveMatrix Service Grid is installed.

Release 3.1.2 The following are new features in this release. •

Deploy WCF Services Create and deploy Windows Communication

Foundation (WCF) service implementations to the TIBCO ActiveMatrix platform. •

.NET Support Supports the .NET Framework versions 3.5 and 4.0.

•

Samples Includes working samples showing basic component development,

faults, partners, and parameters. •

Resource Sharing Components sharing an Application Domain are able to share resources using the standard .NET resource sharing method.

•

Faults Support for both declared and undeclared faults is included.

•

Integrated Logging Integrated .NET logging is provided on the runtime side.


4

|

Release Notes

Changes in Functionality This section lists changes in functionality since the last major (x.0.0) release of this product.

Release 3.3.0 There are no changes in functionality in this release.

Release 3.2.0 Location of Configuration Files Have Changed Previously, there were TIBCO

ActiveMatrix Implementation Type for Microsoft CLR configuration files in the node’s \bin directory, which is not a suitable location for those files. Therefore, they have been moved to other locations. For information about the new location of all configuration files, see the Overview chapter in the TIBCO ActiveMatrix Implementation Type for Microsoft CLR Component Development guide.

Release 3.1.2 There are no changes in functionality in this release.


Deprecated and Removed Features 5

|

Deprecated and Removed Features This section describes the deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features. This section also lists features that are removed (if any).

Release 3.3.0 The following platforms are no longer supported: •

Windows Server 2003

•

Windows Vista

Release 3.2.0 No features are deprecated in this release.

Release 3.1.2 No features are deprecated in this release.


6

|

Release Notes

Migration This section explains how to migrate from a previous release to this release.

Release 3.3.0 The location of the upgrade ant script folder is now changed. See the Migration and Upgrade chapter in the TIBCO ActiveMatrix Implementation Type for Microsoft CLR Installation guide for more information.

Release 3.2.0 The location of many configuration files changed in version 3.2.0. (For information about the new location of all configuration files, see the Overview chapter in the TIBCO ActiveMatrix Implementation Type for Microsoft CLR Component Development guide.) Part of the configuration file location change was to move files from the node’s \bin directory to various directories. As some these were configuration files, they may have included custom settings. Therefore, if you are upgrading from version 3.1.x to 3.2.0, the Ant scripts that you must run as part of the upgrade (see Migration and Upgrade chapter in the TIBCO ActiveMatrix Implementation Type for Microsoft CLR Installation guide) automatically creates a backup of all of the files in the node’s \bin directory and copies them to the node’s \bin-backup directory. This allows you to manually migrate any custom changes in the configuration files after the upgrade.

Release 3.1.2 The process used to migrate TIBCO ActiveMatrix software release 2.x .NET Container services to the Implementation Type for Microsoft CLR is documented in the TIBCO ActiveMatrix Implementation Type for Microsoft CLR Installation guide.


Closed Issues 7

|

Closed Issues The table in this section lists the closed issues in this release. Closed in Release

Key

Summary

3.2.0

MSFT-638

Cannot log application domain messages to the node’s log file. The procedure to redirect application domain log messages to the node’s log file is documented in the TIBCO ActiveMatrix Implementation Type for Microsoft CLR Component Development guide.

3.2.0

MSFT-566

C# types marked with a TIBCO ActiveMatrix property attribute are not all surfaced correctly in TIBCO Business Studio.

3.2.0

MSFT-558

A TIBCO ActiveMatrix Implementation Type for Microsoft CLR component cannot be configured if the service contract and service implementation are not in the same assembly.

3.2.0

MSFT-557

The message "index=0; size=0" is shown for many errors, instead of a more meaningful message.

3.2.0

MSFT-520

AppSettings in the implementation’s .config file is not being copied to the runtime .config file.

3.2.0

MSFT-515

There are potential problems with having TIBCO ActiveMatrix Implementation Type for Microsoft CLR code in the node’s \bin directory. This fix resulted in configuration files being moved from their previous locations. For information about the new locations, see the TIBCO ActiveMatrix Implementation Type for Microsoft CLR Component Development guide.

3.2.0

MSFT-467

AMDR throws an error when the implementation class has a variable of a static type, where the type is defined in a reference assembly.

3.2.0

MSFT-461

A runtime exception is thrown if an RPC-style operation is used with MessageContractAttribute. This limitation has been added to the documentation.


8

|

Release Notes

Closed in Release

Key

Summary

3.2.0

MSFT-459

If the length of an assembly’s path exceeds the Microsoft Windows limit when the assembly is being loaded, the error message is not meaningful. The error message now indicates the assembly’s path exceeds the limit.

3.2.0

MSFT-453

Logger statements are not written to the log file when TraceSource.TraceEvent is used.

3.2.0

MSFT-442

Dragging and dropping a WCF assembly onto a composite in TIBCO Business Studio does not cause the CLR version to be shown in the Target Framework field on the Implementation tab.

3.2.0

MSFT-432

When a WSS SAML Credential Mapping Policy is applied to a CLR-IT component reference, the following error is thrown: "CallProxy

error: SOAPException, msg = Authentication

subject is not available for WSS SAML credential mapping".

3.2.0

MSFT-431

When a Username Token Credential Mapping Policy is applied to a CLR-IT component reference, the following error is thrown: "CallProxy

error: SOAPException, msg =

com.tibco.governance.pa.action.api.ActionException: No user credentials were found for credential mapping action".

3.2.0

MSFT-424

When AMDR settings are changed, the artifacts are not re-parsed nor are the indexes updated.

3.2.0

MSFT-408

If the .exe in a project is replaced with an .exe of a different version of CLR, the target CLR shown in the Target Framework field on the Implementation tab is not getting updated.

3.2.0

MSFT-405

Multiple configured references (clients) are not getting invoked from a CLR-IT component; only one reference is getting invoked.

3.2.0

MSFT-385

Need to clean up error logic in the TIBCO Business Studio Composite Editor when .NET assemblies referenced by the implementation cannot be found.


Known Issues 9

|

Known Issues The table in this section lists the known issues in this release. Key

Summary/Workaround

MSFT-748

Summary The ActiveMatrix Implementation Type for Microsoft CLR component reference does not participate in the At Least Once policy. For example, the composite is SOAPCLR1CLR2 and the At Least Once policy is applied on the SOAP binding. Workaround Apply the At Least Once policy on the reference of every ActiveMatrix Implementation Type for the Microsoft CLR component.

MSFT-707

Summary The application fails to start while upgrading the application by

adding newly created DAA using the Upload DAA or EAR option in the General tab. Workaround To recover after the failure, undeploy the application and then redeploy it. To avoid the failure, undeploy the application, upgrade it, and then redeploy it.

MSFT-703

Summary If some changes are made in the Visual Studio project and the respective .exe, .config and .dll files are copied into the TIBCO Business Studio project, then the TIBCO Business Studio workspace becomes unresponsive. Workaround If you encounter this issue, restart TIBCO Business Studio with a new workspace and import the updated TIBCO Business Studio project with newly copied binary files.

To avoid this issue, do either of the following:

MSFT-574

•

Copy new binary files on the file system and refresh the TIBCO Business Studio project (right click on the project and select Refresh).

•

Clean the project (Project > Clean) in TIBCO Business Studio before copying new binary files in the TIBCO Business Studio project.

Summary If logging is configured to use a JMS Appender, the machine on which TIBCO ActiveMatrix Implementation Type for Microsoft CLR is installed must have a JMS C# client installed. Workaround None


10

|

Release Notes

Key

Summary/Workaround

MSFT-387

Summary If you are using a message-type context parameter in the implementation, when the implementation is assigned to an ActiveMatrix Implementation Type for Microsoft CLR component in TIBCO Business Studio, then the composite is saved, an error is displayed saying the message context parameter is not configured properly, even though the values in the configured fields look correct. Workaround Navigating to the context parameter configuration area on the component and selecting the message parameter, which opens a selection dialog and essentially reselects what is already there, resolves the error.
