Contents

The sections below discuss changes in supported software configurations. Detailed information about supported platforms and software configuration is available in the Supported Platform Matrix. This document is available in the Knowledge Base at Serena Support. Search for solution S136409.

Web Servers and Operating Systems

The following Web server operating system platforms are not supported in this release:

• Microsoft Windows 2000 server
• Solaris, all versions
• Linux, all versions

The following Web servers are not supported in this release:

• Apache Web Server, all versions
• Sun Java System Web Server, all versions

The following client operating systems are now supported:

• Windows Vista for Mashup Administrator use

Database Management Systems

The following database management systems are now supported:

• Microsoft SQL Server 2008
• Oracle Database 11g
  Note: If you are upgrading from a TeamTrack system, refer to the note in Upgrade Notes if you intend to use Oracle 11g with Business Mashups.

The following database management systems are no longer supported:

• Microsoft SQL Server 2000
• Oracle Database 9i
• Microsoft Access, all versions
• IBM DB2 Universal Database, all versions
• Sybase Adaptive Server Enterprise, all versions

If you are upgrading from TeamTrack 6.6.1.x or earlier and you use one of these DBMS tools, you must convert your database into a supported database type before running the database upgrade. This includes the sample database provided with TeamTrack versions 6.6.1.x and earlier. For details, refer to the Moving to Serena^® Business Mashups.

Web Interface

The following Web browsers are now supported:

• Mozilla Firefox 3

Adobe Flash Player Requirements

If you choose to disable Rich Graphical Reports and your system contains data with CJK (Chinese, Japanese, or Korean) characters, you may want to change your system report font setting to ARIALUNI.tt. For details on specifying this font, refer to the "Specifying Graphical Report Fonts" section of the Serena^® Mashup Administrator Guide.

Web Services

The latest Application Engine Web service calls can be found in the aewebservices71 WSDL located here: <Installation Directory>:Serena\Business Mashups\Application Engine\webservices\bin. All TeamTrack Web services and earlier Business Mashups Web services (ttwebservices and aewebservices70) are still compatible with this release. However, these WSDLs have been deprecated and will not contain any of the new calls or parameters found in aewebservices71. For new Web service implementations, use the aewebservices71 WSDL.

New Installations of Serena Business Mashups 2009

If you have not yet installed Serena Business Mashups 2008 or TeamTrack 6.6.1.x, download version 2009 R1 from Serena Support and then follow the instructions in the Serena^® Business Mashups Installation Guide.

Upgrading From TeamTrack 6.6.1.x

Upgrades from TeamTrack 6.6.1.x are supported in this release. This version requires a database upgrade. Back up your existing database before installing this version.

If you have TeamTrack 6.6.1.x installed, download version 2009 R1 from Serena Support, and then follow the instructions in Moving to Serena^® Business Mashups.

Upgrading From Serena Business Mashups 2008 R2.x

Pre-upgrade Steps

Follow these steps before beginning the upgrade:

1. Back up your existing database before installing this version.
2. Download the release from Serena Support.
3. Stop the following services: Application Engine Web server (Internet Information Services – IIS), the Serena JBoss Server, and the Notification Server and Mail Client.

Upgrade Steps

Follow these steps to upgrade your installation and database:

1. Install version 2009 R1 over your existing installation. Note that you must replace all client and server components for all environments.
   Note: If in your previous installation of Business Mashups you installed Mashup Composer on your server machine using the suite installer, you must select the check box to install Mashup Composer at the end of the suite installer when you upgrade to 2009 R1. If you do not install Mashup Composer on the server machine by selecting the check box at the end of the suite installer, you must follow the instructions in S136850 in the Knowledge Base at Serena Support to upgrade the old version.
2. Launch the Mashup Administrator and upgrade the database. If you use multiple environments, you must perform this step for each database in each environment.
3. Review the database upgrade log file in the Program Files\Serena\Business Mashups\Application Engine\Log directory and correct any problems that occurred during the upgrade. If the log file is empty, no errors or warnings occurred during upgrade.
4. Merge custom modifications to HTML templates, javascript files, e-mail templates, and Web interface help files made in your 2008 R2 system to your upgraded files. Backup files are moved to the <installation directory>\Serena\Business Mashups\Application Engine\BackupPatch directory during installation.
5. If you performed step 4, open Mashup Administrator, select File, and then select Put Files in Database. ALL templates and images in the database are replaced by files on your local machine.

Post-Upgrade Steps

Follow these steps after installing the upgrade and upgrading the database:

1. Verify that these services are started: Application Engine Web server (Internet Information Services – IIS), the Serena JBoss Server, and the Notification Server and Mail Client.
2. Graphical report rendering has improved for Distribution, Trend, and Duration reports. Rich Graphical Reports offer dynamic charting and animation capabilities. Adobe Flash Player is required for users to run Rich Graphical Reports, which are enabled by default for your system. Follow these steps if you choose to disable Rich Graphical Reports after you upgrade:
   1. Open Mashup Administrator.
   2. Select Settings from the Options menu.
   3. Select the Display tab.
   4. Clear the Enable Rich Graphical Reports check box.
   5. Click OK.
3. If your 2008 R2.0x system was installed on multiple servers, refer to solution #S136475 in the Knowledge Base at Serena Support for post-upgrade instructions.
4. Instruct Mashup Composer users to install Mashup Composer using the client installer (SMC2009.exe). You may want to recommend that they download and install Microsoft .NET Framework 3.5 before they run the client installer.
5. Instruct administrators to install Mashup Administrator using the client installer (SMC2009.exe).

6. Instruct Mashup Composer users to open the latest versions of mashups from the Mashup Repository.

7. Instruct Web interface and Mashup Manager users to clear the cache in their Web browsers.
8. If you experience issues with any custom forms in the Web interface after you upgrade to version 2009 R1, open the mashup that contains the form in Mashup Composer, and the redeploy the mashup to the Mashup Server. For details, refer to Manually Upgrading Custom Forms.

Upgrading Mashups

After the upgrade to version 2009 R1, most deployed mashups will continue to run on the Mashup Server without manual intervention. In some cases, you may need to redeploy mashups that contain custom forms. For details, refer to Manually Upgrading Custom Forms.

Before mashups can be deployed or promoted, however, they must be upgraded in Mashup Composer. When you open mashups in Mashup Composer after the upgrade to 2009 R1, they are automatically upgraded the first time they are published to the Mashup Repository. This applies to mashups opened from the local cache or from the Mashup Repository.

Once mashups, mashup blueprints, and mashup snapshots are upgraded, they cannot be used in previous versions of Business Mashups.

Manually Upgrading Custom Forms

Handling References in Upgraded Mashups

In previous versions of Business Mashups, you created a link from an application in one mashup to an application in another mashup by merging the two mashups.

For example, suppose you had two independent mashups. One mashup was used by the Engineering department to handle issue and defect tracking. The other mashup was used by the Documentation department to handle documentation issues. You wanted to create a Post transition from the Engineering application to the Documentation application, so that Engineering issues that require documentation changes could be posted to the Documentation mashup.

To accomplish this, you had to merge the Documentation mashup into the Engineering mashup. The application in the Documentation mashup became part of the Engineering mashup.

After you upgrade to version 2009 R1, you use references to accomplish this. When you open the Engineering mashup, you see the application from the Documentation mashup in Mashup Explorer. If you want to make the two mashups independent, you need to create a reference to the Documentation application instead of having it be part of the Engineering mashup.

To separate the mashups, in the Engineering mashup, create a reference to the Documentation application that contains the Post transition. This removes the Documentation application from the Engineering mashup. A message warns you that if you want to continue to work on this application, you should make sure it exists in another mashup.

• If you distribute your Business Mashups installation across multiple server machines, such as separate servers for Application Engine, Orchestration Engine and Mashup Manager, refer to solution #S136476 in the Knowledge Base at Serena Support for post-installation instructions.
• TeamScripts stored on a file system rather than in the database are not upgraded correctly for TeamTrack customers who are running an Oracle DBMS. To work around this problem, open the TeamTrack Administrator before you upgrade, select the Scripts tab, and edit each script whose contents are stored on the file system. Manually copy the contents from the corresponding script file into the Edit Script dialog box, and clear the contents of the Script File Name box. Repeat this step for each script stored on the file system. If you do not take this step before you upgrade to Business Mashups, you can copy the script contents into the Script Editor in Mashup Composer after you upgrade, but you must be sure to copy the scripts into the application using the script. If scripts did not upgrade correctly, the contents of each script will be empty in the Script Editor.
  CAUTION:  Due to a defect in earlier versions of TeamTrack 6.6.1 that caused truncation of large scripts in Oracle, it is highly recommended that you upgrade to version 6.6.1.10 or later before migrating TeamScripts into the database using the TeamTrack Admnistrator.

• You may receive the following error when trying to create an ODBC data source from the Mashup Administrator:

   Unable to connect SQLstate=SQL1110 [Microsoft][ODBC
              Manager] Only SQL_DRIVER_NOPROMPT is allowed when 
             connection pooling is enabled.

  To work around this problem, create the data source using Windows Data Sources Administrative tool instead of the Mashup Administrator. The tool is launched from Control Panel | Administrative Tools | Data Sources (ODBC). For Oracle databases, be sure to create a system DSN using the Oracle driver.

• In some cases when you are uninstalling Business Mashups, pop-up dialog boxes asking you to confirm that you want to delete modified files open behind the main uninstaller dialog box, causing the process to appear to be halted. To work around this problem, press CTRL-ALT-TAB to view the hidden pop-up dialog boxes.
• If you previously installed Mashup Composer to a non-default location, such as a D:/ drive, you must select that non-default location when you install a new version of Mashup Composer.
• If you copy the Serena Business Mashups suite installer to a location and the path to that location includes certain characters, such as an exclamation point (!) or pound sign (#), the installer fails to install suite components.
• Exceptions related to adding tables and columns may occur when attempting to deploy a mashup if you are connecting to a remote SQL 2008 database but aren't using the SQL 2008 client driver. You should install the SQL Server 2008 client before performing the Business Mashups installation.
• Choosing to uninstall Mashup Manager by itself will remove files that are critical to the Application Engine and other server components that are installed on the same machine. To workaround this problem, uninstall and reinstall every component.
• During upgrades from TeamTrack 6.6.1 to Business Mashups 2009 R1, the installer will not allow you to install in the default path C:\Program Files\Serena if that path currently hosts an existing TeamTrack directory. As a workaround, install Business Mashups in a separate location less than 30 characters in length or backup the TeamTrack directory to a new location and delete it from C:\Program Files\Serena prior to installing Business Mashups in the default path.
• The Oracle sample database install fails if the system account or an account with system-like privileges is not used during the installation. The installation will fail with an error message that states: "Problem creating sample tablespace." As a workaround, you can either specify an account that has privileges equivalent to the system user (such that it can create the "sample" user and tablespace), or you can restore the sample.dmp manually after installation. If you restore the sample.dmp manually, you must create a new Oracle ODBC connection in Mashup Administrator and update the data source connection information in the Data Sources tab in Mashup Manager.
• A new proxy server is installed with Serena Common JBoss that allows external data from disparate domains to be loaded and manipulated in the Web interface (using one or more REST widgets, for example). This allows Business Mashups to not only load external data in the browser, but it also normalizes the data into a uniform language that can be processed by the Application Engine. Via use of the proxy server, all data that is loaded in the Web interface appears to be loaded from the same domain. If the Application Engine and Mashup Manager are installed on separate servers, the proxy server's worker.properties file--which is installed on the Mashup Manager machine--needs to be updated with the host name of the Application Engine server in order to enable proxy server support for REST grid widgets. Contact Support for additional details on configuring the worker.properties file.
• By default, the installer places the Oracle SID name specified during installation inside the SERVICE_NAME entry in the tnsnames.ora file. If you use a fully qualified service name to refer to your Oracle environment, you will need to edit the client's tnsnames.ora file and enter the fully qualified service name.
• In new or upgraded installations using an Oracle database, the wrong database driver is recorded in the LoggerConf.xml file. Therefore, the Common Log in Mashup Manager will not report Application Engine messages once Business Mashups is running. Contact Support for details on changing the driver information in LoggerConf.xml.

• Internet Explorer 6 only: The workable area in some views in the Navigation pane may be limited with certain screen resolutions. To work around this problem, expand the views of the Navigation pane.
• Internet Explorer only:The Printable View does not display results for Multi-View reports that contain Rich Graphical Reports.
• The Show TSV option that returns Trend and Distribution reports in a tab-delimited format is not available for Rich Graphical Reports. To work around this issue for most graphical report types, edit the report and select the rptexec.htm file from the Optional Report Template drop-down list located in the Additional Options section. You can then preview the report and select the Show TSV option. Cancel the report edit operation or select the default template from the Optional Report Template to return results in the Rich Graphical Report format.
• Internet Explorer 6 only: Pressing the Enter key has no effect when search criteria is provided on the Basic Search page. To work around this prbolem, users should click the Search button after providing search criteria.
• The Query-at-Runtime option is available when users select fields for the Completed Field Definition for Open and Completed Trend reports, but is ignored when users run the report.
• Zero values for tabular Distribution reports incorrectly show 0 instead of blank values.
• Optional HTML template settings are ignored for reports that are run from the page where reports are saved. To work around this problem, run the report from a report list.
• Multi-byte characters may not render correctly when users send e-mail messages from their preferred e-mail client in the Web interface. This problem typically occurs for pre-7 versions of Internet Explorer and pre-2007 versions of Microsoft Outlook.
• Users may be unable to submit new items that contain file attachments. To work around this problem, they should first submit the item without any file attachments, and then add attachments once the item has been successfully submitted.
• Mozilla Firefox only: The Change History section does not display correctly in custom forms.
• Numeric field types are not handled correctly in the Search Filter used to create a report. For example, you can enter multiple numbers and can enter letters in the Field Values box, and they become part of the expression.
• Internet Explorer 6 only: Periodically, the Quick Links drop-down list is rendered improperly while viewing an item from a report.
• The following user preferences are set only in the Web interface and are stored in cookies: Use Tabs When Viewing Items, Use Accessible Interface, and Tabs to Display. These preferences may be lost when users clear their browser cookies.
• Users may be unable to open file attachments of certain types, such as .zip, in the Web interface. To work around this problem, they should disable the HTTP 1.1 settings on the Advanced tab of the Internet Options dialog box.
• Intermittently, when viewing an item from a report, the scroll bar may not appear along the right side of the Web interface. To work around this problem, try reloading the item or closing and reopening the browser.

• Mashup Composer allows you to provide more than 256 characters as a default value for Text fields set as memo fields. Additional characters beyond 256 are removed after the mashup is deployed, however.
• If you search for the keyword "submit" in a mashup, a list of internal objects related to privileges appears in the results list. Other search keywords may also cause this to happen. These internal objects should not be included in the search results.
• The HideSection field method in the JavaScript API does not work for a GroupBox or Panel container control.
• The HideSection field method in the JavaScript API hides the header for a Tab container control, but does not hide the body.
• If you do an explicit check-in (independent of the Publish or Deploy operation), you cannot publish the local version of a mashup after you delete the mashup from the Mashup Repository. To work around this problem, export the mashup and then import it back into Mashup Composer.
• If you are using a WSDL that defines a SOAP header, renaming the Web service causes Mashup Composer to crash.
• If you search for log viewer messages using the Message Selector dialog box (accessed by clicking Set Filter in the Log Viewer), and some messages are returned, the relevant workflow is displayed in bold on the Overview tab (as expected). However, if you search for messages again, and no messages are returned, the workflow is still displayed in bold. To work around this problem, toggle the display of the Log Viewer from Common Views area of the Home tab on the Ribbon.
• If you import a mashup created in an earlier version into version 2009 R1, and validate or deploy the mashup, you could get the following validation error in the Message List: "Calculate Step has an invalid expression property." This is because Mashup Composer now validates that the parameters supplied to the CONCAT function are strings. If non-string parameters were used, this message is returned. To work around this problem, locate all CONCAT calls and explictly convert the non-string parameters to strings using the STRING function. For example, CONCAT("Output Text", STRING(MyNonStringData));
• A mashup snapshot does not contain the global mashup, even if there are references to the global mashup within the mashup contained in the snapshot. Because the global mashup contains the users, scripts, triggers, and other artifacts that might be referenced within the mashup snapshot, consider whether you need to take a snapshot of the global mashup separately and promote it along with the mashup that contains the references.
• Deployment fails if you have a mashup with a Transition action, but you did not specify a field to be affected by the action. To work around this problem, edit the Transition action to specify the field. To do so, click the blue "specified" field link. Then rebuild the rest of the action.
• A deleted Sub-Relational field in a mashup may not export with enough information for automatic reference resolution. This should only affect a mashup that is exported and then used as a template or a blueprint to create additional mashups. If the mashup is used as a template or a blueprint, the references to the same object as the deleted field may need to be manually resolved.
• A multi-line field with vertical fill will collapse to the height of a single line if there is no other control on the same line that may cause the height to be taller. To work around this problem, change the height of the field to top-align and "auto-size" or a fixed size.

• Mashup Composer cannot import RPC-bound Web services. RPC-bound WSDLs are not supported by Mashup Composer because they are multi-part and because they support operation overloading, where the same name can apply to different operations in different situations.
• WSDL binding provides different ports for supporting different types of binding. Only SOAP 1.1 bindings are supported, and you should select only the ports that correspond to SOAP 1.1.
• When you are creating orchestrations in Mashup Composer, you are able to use XPath functions as part of the definition of steps in an orchestration workflow. However, functions that are in XPath 2.0, but not in XPath 1.0, are not supported.
• Web services documentation that is displayed within the Mashup Composer user interface contains escaped HTML tags. For example:

  (line one)<br>(line two)

• Occasionally, a communication timeout between a mashup tool and the orchestration workflow it is trying to call might occur. This can happen for several reasons, but the timeout mostly occurs when Serena Business Mashups has recently been started. If a user receives an error when submitting a request, the user should try submitting the request again. (In the case of Serena Business Mashups/Salesforce.com integration, Salesforce.com is the mashup tool and the user initiates the request to the orchestration workflow from a customized interface presented by Salesforce.com.)
• If the size of a Web service response exceeds the allowable limit, execution of the orchestration workflow is stopped. An error message containing a SOAP fault appears in the Log Viewer for the associated Service step. The error message also indicates the maximum allowable size. To handle the fault, you should place the Service step within a Scope step and catch the fault in the Catch All branch of the FaultHandler. In addition, you should consider reducing the size of the response SOAP message's payload by redesigning the way you invoke the Service step. For example, you could add filtering if the Web service supports it.
  Note: See the Serena^® Business Mashups Installation Guide for information about setting the maximum allowable size.
• When creating expressions that contain a Catch branch, you must first type the name of the Catch branch and a period before you can complete the expression using the expression editor.
• You should not use Binary/Trinary fields that are configured as trinary in orchestration workflows. Because these fields can only be mapped as binary, you could lose data. In addition, for both binary and trinary fields, labels that you applied to the values will not be available in an orchestration workflow. The generic True/False values will be used instead.
• You can use working data elements of type Boolean in logic operations such as AND, OR, and NOT. However, if you use a data element of type Boolean in a Web service request or response, including a Boolean field defined in an application and passed into an orchestration workflow with EventNotice, that element cannot be used in a logic operation. To work around this problem, instead of the Boolean data element, use a working data element of type Boolean that contains the value of the Boolean data element.

  For example, assume that Var is a Boolean working data element and Field is a Boolean field defined in an application.

  Var AND something > 5 is supported.

  EventNotice.Extension.Field AND something > 5 is not supported, because it might return the wrong result.

• Working data elements cannot be named input or output, including any variations in capitalization such as Input or Output.

• If any or all of the following four error messages appears in the server.log file, you can ignore them. (The timestamp in your message will be different.)

  • ERROR 2008-11-25 12:15:52,893 org.hibernate.tool.hbm2ddl.SchemaUpdate -- Unsuccessful: alter table BPEL_ASSIGNOPERATION add constraint FK_COPY_TO foreign key (TO_) references BPEL_TO
  • ERROR 2008-11-25 12:15:52,894 org.hibernate.tool.hbm2ddl.SchemaUpdate -- There is already an object named 'FK_COPY_TO' in the database.
  • ERROR 2008-11-25 12:15:52,912 org.hibernate.tool.hbm2ddl.SchemaUpdate -- Unsuccessful: alter table BPEL_ASSIGNOPERATION add constraint FK_COPY_FROM foreign key (FROM_) references BPEL_FROM
  • ERROR 2008-11-25 12:15:52,912 org.hibernate.tool.hbm2ddl.SchemaUpdate -- There is already an object named 'FK_COPY_FROM' in the database.
• If you use a sub-element of the ForEach.item within a ForEach loop, and the ForEach loops on a collection with a range restriction, your mashup will fail to deploy or to export.
• When you use the Throw step, you must either map a value using the Pick a Source tool or provide a default value for the FaultCode or for the FaultString data elements. If you do not provide any values for the FaultCode or the FaultString data element, an error is logged in the Log Viewer when this step is executed. However, the Throw step still behaves as expected.
• When assigning a value to SOAP header data, you must map the value using the Pick a Source tool. If you assign the value using a Calculate step, your mashup will fail to deploy.
• If you rename a Service step for which SOAP header data is defined, the new name must be in the following format: ServiceStepName_WebServiceOperation. If you do not name the Service step correctly, your mashup will fail at runtime.
• Do not use an ampersand (&) in a static string in expressions such as in the Expression section of the Calculate step or in the Rule section of the ForEach step. If you do, the Orchestration Engine might interpret the single ampersand as two ampersands (&&) when you run your mashup. This condition could cause an orchestration workflow to fail at runtime. To work around this problem, do not use a static string containing an ampersand directly in an expression. Instead, use working data with the default value.
• If you delete an orchestration in Mashup Composer, you must also delete it in the runtime environment. If you do not, the orchestration workflows associated with it are still invoked when you run the mashup. The best way to correct this problem is to undeploy the mashup in Mashup Manager, delete the orchestration in Mashup Composer, and then redeploy the mashup.
• External events that are sent in the body of an email might not work if the mail server prepends or appends data to the email.
• To generate a client proxy for invoking the Event Manager using Apache Axis2, use the document/literal endpoint and WSDL. Refer to the "Raising External Events" chapter in the Serena^® Mashup Composer Guide for more information. Although you can use the Event Manager RPC/literal endpoint, creating a client proxy with Axis2 using the document/literal endpoint is recommended because it is less complex.
• You should avoid renaming orchestrations, if possible. When you rename an orchestration and then deploy it, a new event map is created. If you do not delete the old event map, the associated orchestration workflows that are invoked at runtime are invoked twice. If you must rename an orchestration, you should first undeploy the mashup in Mashup Manager, rename the orchestration in Mashup Composer, and then redeploy the mashup.
• In the expression STRING(COUNT(items.item)), items is a working data element of complex type and item is its child data element of type array. If you use this expression in a Calculate step and assign it to a working data element of type string, your mashup will pass validation, but it will not deploy. To work around this problem, assign COUNT(items.item) to a numeric working data element first, and then use the STRING function. For example, assign COUNT(items.item) to a numeric working data element named number, and then use it in the following expression: STRING(number).
• In the expression CONCAT(anystring, STRING(COUNT(items.item))), items is a working data element of complex type and item is its child data element of type array. If you use this expression in a Calculate step and assign it to a working data element of type string, your mashup will pass validation and then deploy, but it will fail at runtime. To work around this problem, assign COUNT(items.item) to a numeric working data element first, and then use the STRING function. For example, assign COUNT(items.item) to a numeric working data element named number, and then use it in the following expression: CONCAT(anystring, STRING(number)).
• When you use a Compensate step within an enclosing scope, then, on the General tab of the Scope menu, [Default Step] and the names of any immediately enclosed Scope steps should be displayed. For example, if ScopeA encloses both ScopeB and ScopeC, and you place a Compensate step within the CompensationHandler section of ScopeA, then you should be able to select from the following options on the Scope menu for ScopeA: [Default Scope], ScopeB, and ScopeC. However, if an enclosed scope is used within the Decision, While, or ForEach step, the name of that enclosed Scope step does not appear on the Scope menu of the enclosing scope. For example, if ScopeA encloses both ScopeB and ScopeC, and ScopeB is on a branch of a Decision step, then only [Default Scope] and ScopeC are available on the Scope menu for ScopeA.

The following are known issues with the Application Engine and Mashup Administrator:

• Certain labels, such as those for transition actions and field options, do not match between Mashup Administrator and Mashup Composer.
• The Backfill to Existing Items option is not available when you add new User, Multi-User, Multi-Group, Single Relational, Multi-Relational, and Folder fields.
• Selected field privileges do not display in bold text for managed administrators who are granted field administration privileges from their group membership.
• The License Usage log file location cannot be changed from the default location.
• If user names and passwords will contain non-ASCII characters, the Accept Information From Form/URL/Cookie option must be selected on the Server tab of the Settings dialog box in Mashup Administrator.
• Users may experience problems logging in to the Web interface or Mashup Manager if your system uses Oracle NTS authentication. If possible, use another authentication method for Oracle. If this is not possible, contact Serena Customer Support for assistance.
• A WSDL parsing error will appear in the Mashup Administrator when attempting to view Web services in a deployed mashup while connected Remotely via Web Server. Either connect via ODBC or view the Web service in the Mashup Administrator installed on the server.
• An error will appear in Mashup Administrator when you attempt to connect to your database if the Windows Vista setting "User Account Control" is enabled. To work around this issue, turn off "User Account Control" in the Vista User Accounts dialog.
• The Quick Administrator feature may add duplicate notifications and notification rules to your system when deploy new mashups for the first time. You will receive an error if you attempt to edit one of these notifications or notification rules in Mashup Administrator. To work around this problem, rename the notification or rule and then save your changes.
• The Copy Database operation will hang when the SQL Native Client 10.0 driver is used in the source database ODBC connection and the SQL Native Client driver is used in the destination database ODBC connection. As a workaround, use the SQL Native Client driver in the source database ODBC connection.
• Web service inputs may appear out of order when mapping parameters for a Web service call made via a notification in the Mashup Administrator. The same inputs appear in proper order when viewing the service in Mashup Composer.
• On Windows Vista systems, the Remember Remote Password and Reconnect at Start Up selections are not honored for Remote Connection to Web Server connections. You will need to enter your credentials and reconnect each time you try to connect remotely using the Mashup Administrator on Windows Vista systems.

• A mashup snapshot does not contain the global mashup, even if there are references to the global mashup within the mashup contained in the snapshot. Because the global mashup contains the users, scripts, triggers, and other artifacts that might be referenced within the mashup snapshot, consider whether you need to take a snapshot of the global mashup separately and promote it along with the mashup that contains the references. You need to promote the global mashup if you made changes to it that your mashup depends on (for example, if you added a new user or group and your mashup assigns that user or group to a role).
• The Quick Administrator feature may add notifications and notification rules with duplicate names to your system when you deploy new mashups for the first time. These duplicate items are created based on workflow names of new mashups. When you attempt to promote mashups that contain these duplicate notifications and notification rules, the promotion will fail. To work around this problem, rename duplicate notifications and rules in the originating environment before promoting the mashup.
• If Mashup Manager hangs when SSO is enabled, close the browser and then restart Mashup Manager.
• If you set a filter on the Event Manager Log page, there is no way to return to the No Filter state unless you delete the currently set filter. To work around this problem, create a filter that shows all events, and use that filter in place of a no filter state.
• BPEL deployment currently generates error messages related to a file named Sample.war when the JBoss application server starts up. You can safely ignore deployment-related error messages that refer to that file.
• You may see this transport error when you attempt to deploy an orchestration. This error message does not contain the information that it should, because of a bug in the version of Axis used by Mashup Manager in this release. If you see this error, the true cause may be a failure during the validation of the BPEL code created for the orchestration. You should check the server.log at:

  \common\jboss405\server\default\conf\server.log

  If there is an exception, you will be able to see it there. For more information, see the Serena^® Mashup Manager Guide
• Certain dialog boxes are not properly sized. To work around this problem, manually resize dialog boxes that do not show all contents.
• Deleting a mashup does not remove it from a server to which it has already been deployed or promoted. To completely remove a running mashup (other than the global mashup) from the Web interface, use the Undeploy Mashup command in Mashup Manager.
• Elements such as icons, style sheets, and scripts added to forms in tables in the Global Application are lost after promotion or after getting a mashup into Mashup Manager from the Application Engine.
• When you export a mashup containing an orchestration with a particular combination of working data elements, an extra working data element appears when the exported mashup is re-imported. If you see these extra working data elements, you should delete them; otherwise, the mashup will not be importable if exported again.
• Search conditions and column display options may be lost on Version Control Actions reports after they are promoted into an environment.
• Row and Column sorting values for Distribution reports may be lost after the reports are promoted into an environment.

• You can ignore warnings that look like this:

  WARN -- Import: Invalid Data 'SYSCODE-98-4' in node 'FieldID'.

  In Change History, Deleted Items, and VC Action reports.

  Note: These warning messages can be received during deployment.
• Application Engine error messages that contain non-ASCII characters are not displayed properly in the Mashup Manager Common Log or in the Mashup Composer Log Viewer; however, the messages are displayed properly in the Web interface.

• The Single-Sign On feature is not compatible with Internet Explorer 6 version SP1 6.0.2800. Users using this version of Internet Explorer should upgrade to a newer version.

• The client installation currently does not provide the ttwebservices.wsdl file. This file is available only by installing the Application Engine Web services component from the server installation.
• Support for invoking derived complex types in a third party Web service is not currently available. Thus, an error will occur if you attempt to publish or deploy a mashup that contains extended data input mappings. However, output mappings using extended data will work without issue. You will need to will to invoke a different Web service that does not contain derived complex types if you want to map Web service inputs using Application Data.
• Web service calls will fail if the WSDL contains Unicode characters. Data sent or received in a Web service call may contain Unicode characters; however, an error will appear during Web service invocation if the WSDL itself contains any Unicode characters.
• When updating a Journal field that is set to Append Only, the UpdateItem call will replace existing text with any new text provided in the value element. In order to preserve the existing text, you must provide the existing text in the new value element and manually append your new content. To avoid this problem, use the APPEND-VALUES option in Set-Value-Method.
• New sample Web services have been added in this release; however, the readme that accompanies these samples refers to artifacts from the TeamTrack sample database.

• In Chapter 24, "Raising External Events," of the Serena^® Mashup Composer Guide, the first sentence of the "Authenticating an External Mashup Event" section incorrectly implies that the authentication specifications apply for the on-demand environment only. The list of specifications also applies for the on-premise environment.

• In Chapter 22, "Orchestration Procedures," of the Serena^® Mashup Composer Guide, in the "Using the Scope, Throw, and Compensate Steps to Handle Faults From Web Services" section, under "Running the Fault Handling Mashup," the following steps might be needed in the "Tutorial: Running the CompensateAWF Project" section:

  • In step 5 after you click OK, you might need to click the Reload Item button to display the results.

    Note: Right-clicking anywhere in the tabbed area and then selecting Refresh on the menu has the same effect as clicking the Reload Item button.
  • In step 7, after you click OK, you might need to click the Reload Item button to display the results.
  • In step 10, after of click OK, you might need to click the Reload Item button to display the results.
  • In step 12, after you click OK, you might need to click the Reload item button to display the results.

• In Chapter 22,"Orchestration Procedures," of the Serena^® Mashup Composer Guide, in the "Using the Scope, Throw, and Compensate Steps to Handle Faults From Web Services" section, under "Using the Compensate Step," the first paragraph under step 7 of the "Tutorial: Creating an Empty Asynchronous Orchestration Workflow for the Throw Step" section should read as follows:

  NewGetTickerSymbolWorkflow appears under Step 1 and should be selected. Step 2 should read Invoke an orchestration workflow and continue executing, affect this item, invoke mashup event FaultHandlingPTable:ThrowAsynchAWF_New_GetTickerSymbol.

The Tracker Solution Wizard that creates Business Mashups applications based on Tracker projects has been deprecated. Follow these steps to create applications based on Tracker projects: