| Your Rating: |
![]() ![]() ![]() ![]()
|
Results: |
![]() ![]() ![]() ![]()
|
18 | rates |
August 9, 2011
© 2011 Adobe Systems Incorporated and its licensors. All rights reserved.
This file contains important information that was not available when the product documentation was written. Review this information before you run the Experience Services on Adobe® Digital Enterprise Platform 10.0.
Contents
Additional release notes:
Introduction
The Adobe® Digital Enterprise Platform (ADEP) Experience Services is a composite content application platform for rapidly deploying Adobe's Customer Experience Solutions and building custom applications. Delivered as a single Jar file Experience Server offers a range of "Experience Services" designed to support activities by end users via Rich Internet Applications (RIAs). These Experience Services are:
CRX: Formerly Day Software’s Content Repository Extreme, CRX provides the Content Repository, Web framework and Java runtime container for your application.
Composite Application Services: Composite Application Services allows you to deploy and manage a web application as modular components managed in the Content Repository and customized by end users.
Data Services: Data Services provides Flex Remoting, Data Management and Data Modeling capabilities for Rich Internet Applications (RIAs) that display and manage data from multiple data sources, including the Content Repository.
Task Management: Provides User Task Management, with the option of using the Content Repository for persistence of task data or integration with the Document Server, to help manage BPM User Tasks within an RIA.
Security: Services for performing authentication and single sign with third party Identity Services in an RIA.
Document Service integration: These services help you leverage the Document Server and its range of Document Services within a RIA.
Platform SDK: Each of the technologies (Security, Content, Data Services, Client Component Framework) span the client and server tiers. These capabilities are delivered as a single SDK package (containing SWC and JAR files) through PackageShare and once downloaded can be placed on the developer's file system and referenced by Adobe Flash Builder.
Experience Services Tooling: Includes software and plug-ins for Adobe Flash Builder that enable you to create applications using Flex, Data Services, and Composite Application Framework.
Samples: Includes Test Drive samples for Experience Services and Data Services, as well as Composite Application Framework.
For detailed overview of ADEP platform and its architecture and capabilities, see Adobe Digital Enterprise Platform Overview.
General
Due to a vulnerability in the Flex SDK, many Flex applications built using Adobe Digital Enterprise Platform - Experience Services are vulnerable to cross-site scripting (XSS) attacks, and must be patched in order to protect user data.
For information on which applications are vulnerable and solutions, see http://kb2.adobe.com/cps/925/cpsid_92559.html.
Installation Notes
Before installing Adobe Digital Enterprise Platform Experience Services or any of the Customer Experience Solutions, see the Before You Install for important information.
Installation Issues
[Ref # 2935385-ADEP10.0] - When you install Experience Services by double-clicking the Quickstart JAR file, the crx-quickstart working directory could be created in the system32 Windows directory. Typically, the crx-quickstart should get created in the same directory from where the Quickstart is run.
To fix this issue:
- Stop the Experience Server.
- Re-install the 64-bit Sun JDK 6 update 26 or later.
- Re-run the Quickstart JAR file.
[Ref # 2872569-ADEP10.0] - Experience Services Tooling plug-ins are not removed completely after installation - On uninstalling the Adobe Experience Services Tooling plug-ins for Flash Builder, you will receive the following warning:
Adobe Experience Services Tooling for Flash Builder cannot be fully uninstalled because other installed software requires it. The parts that are not required will be uninstalled.
Although the plug-ins are removed from the Installed Software tab, they still appear in the Plug-ins tab. To avoid this issue and to completely uninstall the Experience Services Tooling plug-ins, you must uninstall the Adobe Digital Enterprise Platform Document Services - Discovery Plug-in for Flash Builder.
Java 7 not supported by Experience Server
Before installing Experience Server, you are required to install the 64 bit version of Sun™ Java™ 6, update 26 or a higher. Java 7 is not supported at this time. Note: The 32-bit version is supported for evaluation and development purposes.
[Ref # 2925196-ADEP10.0] - After completing the uninstall and install procedure provided in "Appendix - Install mosaic release package for Composite Application Framework" in Installing ADEP Experience Services, the following message may be displayed: "No resource found (404)". To resolve this issue, do the following:
- Stop Experience Server.
- Re-start Experience Server.
- Reinstall the release variant of the mosaic package for Composite Application Framework.
Clustering Issues
[Ref # 2900853-ADEP10.0] - In the case of CRX deployed in an application server, it is recommended to use the GUI setup for CRX feature pack 2.2.0.9 and later. Clustering of nested earlier versions, inside of an application server, is not supported.
Administration
CRX Admin searching
[Ref # 2905899-ADEP10.0.1] If you use the search capability in the CRX Admin, all categories and sub categories are returned even if they do not match your search criteria.
Composite Application Framework
[Ref # 2904737-ADEP10.0] - All label attributes and category and tag content are limited to 600 bytes. When composite application label attributes or category and tag content is larger than 600 bytes, an ActionScript error 1009 is displayed. For example, when users save a view, the description for the view cannot be larger than 1,000 characters.
[Ref # 2907709-ADEP10.0] - You cannot write a Flex project that uses Services Discovery and codes against the destinations created by a model that is already deployed. Instead, write a separate library project for the model and its CRUD operations and distribute the library.
[Ref # 2909127-ADEP10.0] - Date and Array objects do not work for when you are adding communication between tiles using contexts. For example, the Context.setAttribute() and Context.getAttribute() methods do not work for Date and Array types in JavaScript. However, they do work in ActionScript.
[Ref # 2916399-ADEP10.0] - The amount of memory that a composite application uses steadily increases when a user repeatedly adds and deletes tiles that are not module tiles, or adds and deletes views that contain the tiles. To avoid this problem, create tiles as module tiles.
[Ref # 2893812-ADEP10.0] - The Project > Clean option forces the Flash Builder compiler to rebuild all resources in a project. However, for projects for which Composite Application Framework Services is enabled, the complier does not remove all files from the project’s bin-debug folder. These files include the .gxml, .cxml, .axml, and .zip files that Experience Services generates when you deploy the application and are found in the output folder. To complete the clean build process, manually delete these files.
[Ref # 2908749-ADEP10.0] - Views saved in a composite application by a non-admin user are by default assigned to an admin user. Use the following steps to give a user the permissions required to access saved views
- Log in to Experience Server as an administrator.
- In the ADEP Experience Services Welcome page, click User. By default, the URL of the welcome page is http://localhost:4502/libs/crx/core/content/welcome.html.
- In the User Administration window, click Create User.
- To create the new user, enter values for UserID and Password, and then click the green checkmark button.
- Close the User Administration window.
- In the ADEP Experience Services Welcome page, click Content Explorer.
- Locate the new user at /home/users/[first letter of user ID]/[first two letters of user ID]/[user ID] and select it.
- Click Security > Access Control Editor.
- In the Applicable Access Control Policies, select ACL, and then click Set Selected Policies.
- Click New ACE.
- For Principal, enter the UserID value for the user. For Privileges, select jcr:read.
- For the new ACL list item, click the OK button (green with checkmark) to save your changes.
- Click OK to close the Access Control Editor.
[Ref # 2922841-ADEP10.0] -When using Experience Services and deploying composite applications, ensure HTTP Basic Authentication is not enabled in the Apache Felix Web Console Configuration (http://localhost:4502/system/console/configMgr). Setting HTTP Basic Authentication is not supported.
[Ref # 2932764-ADEP10.0] - When you use the Show View Link command that is provided with some Composite Application Framework sample applications, you cannot generate a link to a view more than once. For example, you click Show View Link for a saved view and then paste the link in the View Link dialog into a new browser window to view the saved view. If you update this saved view and save the update, and then click the Show View Link option and paste the link in the View Link dialog to another a new browser window, the message "Cannot open view (copied link) View does not exist..." is displayed.
[Ref # 2919832-ADEP10.0] - You cannot successfully deploy a release version of a composite application that contains a UIComponent tile using Experience Services. Use Ant or Maven to deploy release versions of this type of composite application instead.
[Ref # 2915624-ADEP10.0] - The image for a custom login splash screen does not scale correctly. You create a custom login splash screen using the SlateInitStyles sample. To solve this problem, use s:BitmapImage instead of mx:Image for your image statement. For example:
<s:BitmapImage width="100%" height="50%" source="@Embed('/assets/MyImage.png')" fillMode="scale" scaleMode="stretch"/>
[Ref # 3019842-ADEP10.0.0.0] - You can override the files that Experience Services generates in the mosaic/generated folder by adding custom versions of the files to mosaic folder. When you create a custom GXML file, ensure that the filename is different from the associated tile. If the custom GXML file and the tile have the same name, Experience Services modifies the catalog to use the GXML file that it generates automatically.
Data Services
General
[Ref # 2801622-ADEP10.0] - A data member whose data type is a byte array may be null when you call a FiberAssembler object’s getAll method. That is, assume you create a Java class named foo that has a data member whose data type is a byte array. Then you create a FiberAssembler class that has a getAll method. If there is data load issue (for example, you attempt to load video data from a source where the connection is slow), the data member of the returned foo item may be null when getAll is called from a client application.
[Ref # 2917061-ADEP10.0] - This issue is with Modeler Design View. For the representation of the model in Design view, read-only is being set to false, but mappedBy properties are read-only. The Source view has the actual XML and the model saves without error there. When you return to Design View after that, the error goes away. The workaround is to go into Source view, make a change of any kind (add a space or linebreak) and save the model. After that, Design view is in sync and there are no errors.
[Ref # 2914977-ADEP10.0] - The RemoteFileServiceImpl object’s createFile method throws an exception when the URL that is passed to the createFile method is an IPv6 address. Consider the following code:
fs = new RemoteFileServiceImpl(baseUrl); file = fs.createFile(new ByteArrayInputStream(bytes),"application/pdf", null, fo);
When the baseURL is an IPv6 URL such as [http://[IPv6|http://[] address]: port, the following exception is thrown:
File fails to create with following error Caused by: java.net.UnknownHostException: \[2001) at java.net.InetAddress.getAllByName(InetAddress.java:1039) at java.net.InetAddress.getAllByName(InetAddress.java:1019
Instead of using an IPv6 URL for the Experience Server, specify the address as http://<IPv6 mapped host name>:port.
[Ref # 2903029-ADEP10.0] - Sometimes, relationship line disappear if the reference collection property in the entity is moved. This does not remove the relationship, the lines are not rendered in the canvas. To workaround this issue, please move the property again.
[Ref # 2895050-ADEP10.0] - Due to this issue when ChannelSet is receiving a constant stream of messages, it is unscheduling and rescheduling heartbeats constantly which meant that no heartbeat is sent to the server at all to keep the session alive. To workaround this issues, users can use a timer to resubscribe. One possible way to do this is described below:
public function set valueObject(value:First):void { form.valueObject = value var t:Timer = new Timer(20 * 60 * 1000, 0);//20 minutes * 60 seconds per minutes * 1000 ms per second t.addEventListener([TimerEvent].TIMER, resubscribe); } private function resubscribe(event:[TimerEvent]):void { consumer.subscribe(); }
[Ref # 2889955-ADEP10.0] - Several NoClassFoundExceptions may be thrown during the debug of an android application. These will be with flex.messaging.util.PrettyPrinter and flex.messaging.util.BasicPrettyPrinter classes. However, you can just continue to run the program by stepping past these exceptions.
[Ref # 2885878-ADEP10.0] - The DataServiceFaultEvent should catch the error when trying to access a lazy loaded item that was not loaded while on-line, which it doesn't. The workaround is to add an event listener for Event.FAULT which will catch the error and allow the application to continue.
[Ref # 2867102-ADEP10.0] - The Platform Quickstart needs to be restarted when ever any package with a new Database driver is installed.
[Ref # 2810520-ADEP10.0] - Introspected entity misses attribute from the original model and causes deployment failure. The workaround is to use the Data Services destination drag and drop for introspection.
[Ref # 2776440-ADEP10.0] - Reloading the services-config.xml file causes 'java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path'. This exception is thrown by the SAP JCo library and does not affect the functioning of the feature in any way.
[Ref # 2775184-ADEP10.0] - If Producer gets authentication failure due to session principal being cleared, cannot login again. The workaround is to disconnect and reconnect the channel.
[Ref # 2677357-ADEP10.0] - If paging is enabled on a Data Management fill and the data maintained on the server is modified while the server is not running, a running client will not function correctly until a new fill operation is performed.
[Ref # 2920315-ADEP10.0] - When you use a web client to interact with the Document Server, JavaScript object types are returned as their primitive type. For example, if you pass a Number Object type using object var num = new Number(3) to the Document Server, it is returned as a primitive data type number with a value of 3.
[Ref # 3008176-ADEP10.0] - If your Flex application uses the SearchResultsGrid UX component, a null pointer error may be displayed when there are less than a page of items in the grid and a user uses Page Down to navigate the grid.
Data Modeler
[Ref # 2656053-ADEP10.0] - A Model with lazy loaded many-to-one associations with multiple ID properties will not correctly insert new data with createItem().
[Ref # 2873607-ADEP10.0] - This readme item is related to model driven development by using Experience Services Extension tooling for persisting entity data in the Experience Service repository instead of a database. Assume that you create a CRX based entity and deploy the model into the Experience Server repository. Then you import the service and VO for this entity in another project.
From the Data/Services view, you right click the CreateEntity (or the UpdateEntity or DeleteEntity) operation and then click Generate Form. This action results in a set of flex controls being added to the MXML. The auto-generated form that is created cannot be used without further modifications to it. That is, you have to make modifications in the code to ensure that the auto-generated form works correctly.
In the button_click handler, notice that the following code is generated:
// Please uncomment the below line if Data Management is enabled for HelloFlexEntity // and createHelloFlexEntity is used as the create function. //var helloFlexEntity:HelloFlexEntity = new HelloFlexEntity(); helloFlexEntity.id = idTextInput.text;
You have to uncomment line 3 and comment line 4 as follows:
// Please uncomment the below line if Data Management is enabled for HelloFlexEntity // and createHelloFlexEntity is used as the create function. var helloFlexEntity:HelloFlexEntity = new HelloFlexEntity(); //helloFlexEntity.id = idTextInput.text;
Similar corrections would need to be made for update and delete calls as well.
[Ref # 2639635-ADEP10.0] - recreate-httpsession-after-login does not work with streaming channels.
[Ref # 2600839-ADEP10.0] - Modeler: The Modeler does not preserve comments.
[Ref # 2600826-ADEP10.0] - Modeler: Invalid entity creation: same table defined in multiple schemas creates duplicate fields in entity model.
[Ref # 2600592-ADEP10.0] - Modeler Expression Builder: Cannot use "up" and "down" keyboard arrow keys to scroll through the list of functions or the function categories.
[Ref # 2600562-ADEP10.0] - Model-driven form: Adding a model-driven form in Flash Builder design mode takes a long time and causes a flicker. This does not occur when using a Flex form, or if either type of form is added in source mode.
[Ref # 2600120-ADEP10.0] - Model-driven form: Model-driven form created against an entity with a datatype column of type float causes rounding of that type based on the numericStepper's stepValue.
[Ref # 2600017-ADEP10.0] - Model-driven development: No error when table creation fails on deploy due to JDBC driver fail to load. RDS view does show an error for same issue.
[Ref # 2599996-ADEP10.0] - Client-side data management: autocommit doesn't work properly when the entity has a complex key with an association.
Documentation
The Experience Services product documentation is available online on the Adobe website at www.adobe.com/go/learn_dep_documentation_10.
[Ref #2924208-ADEP10.0] - The APIs provided with Adobe Digital Enterprise Platform Experience Services - Content 10.0 are incorrectly tagged as AIR 1.0 or AIR 2.6 in the ActionScript 3.0 Reference for the Adobe Flash Platform. The APIs in the Experience Services - Content do not support Adobe AIR. The issue occurs in the following packages:
- com.adobe.livecycle.content
- com.adobe.ep.ux.content.event
- com.adobe.ep.ux.content.factory
- com.adobe.ep.ux.content.handlers
- com.adobe.ep.ux.content.managers
- com.adobe.ep.ux.content.model.asset
- com.adobe.ep.ux.content.model.preview
- com.adobe.ep.ux.content.model.relation
- com.adobe.ep.ux.content.model.search
- com.adobe.ep.ux.content.model.toolbar
- com.adobe.ep.ux.content.search
- com.adobe.ep.ux.content.services
- com.adobe.ep.ux.content.services.load
- com.adobe.ep.ux.content.services.permissions
- com.adobe.ep.ux.content.services.preview
- com.adobe.ep.ux.content.services.providers
- com.adobe.ep.ux.content.services.query
- com.adobe.ep.ux.content.services.relationships
- com.adobe.ep.ux.content.services.search.lccontent
- com.adobe.ep.ux.content.services.version
- com.adobe.ep.ux.content.view
- com.adobe.ep.ux.content.view.components.activate
- com.adobe.ep.ux.content.view.components.grid
- com.adobe.ep.ux.content.view.components.grid.hover
- com.adobe.ep.ux.content.view.components.grid.hover.component
- com.adobe.ep.ux.content.view.components.grid.renderers
- com.adobe.ep.ux.content.view.components.relationships
- com.adobe.ep.ux.content.view.components.review
- com.adobe.ep.ux.content.view.components.search.renderers
- com.adobe.ep.ux.content.view.components.searchpod
- com.adobe.ep.ux.content.view.components.toolbar
- com.adobe.ep.ux.content.view.components.toolbar.controlRenderers
- com.adobe.ep.ux.content.view.components.version
Additional Licenses and Copyrights
By installing this product, in addition to the Adobe license terms, you also agree to be bound by the third-party terms specified in the product documentation and at www.adobe.com/go/thirdparty. Adobe recommends that you review these third-party terms.
Release Notes - Adobe Digital Enterprise Platform Experience Services - August 5, 2011<!- /* Style Definitions */ table.MsoNormalTable
-->The Content Repository Connector DSC
Labels
Comments (1)
- Hide Comments Show Comments
- Collapse All Collapsing… Expanding… Expand All

Aug 24, 2011
DanDan Jia says:
Samples was mentioned in the introduction part, which includes theTest...Samples was mentioned in the introduction part, which includes theTest Drive samples for Experience Services and Data Services, as well as Composite Application Framework. But in addition to that, it also includes the Application Use Case samples, this should also be mentioned.