About setting up a Flex development environment
Oracle recommends setting up a Flex development environment for
creating your custom editors.
You can use a standalone
installation of Flash Builder, or set up your development environment in
Eclipse. Setting up an Experience Manager SDK project in Eclipse requires the
Flash Builder 4 plugin.
Configuring a Flash Builder 4.0 development environment
If you choose to develop using Flash Builder, you must use Flash
Builder 4.0. In addition, the version of the Flex SDK that Flash Builder uses
to compile must be 4.5.0 or higher. You should compile your editors using the
Halo theme for visual consistency.
To configure a Flash Builder development environment:
Confirm that you are running version 4.0 with the Flex 4.5 SDK:
Start Flash Builder 4.0.
Navigate to
→ .
In the tree control on the left, navigate to
→ .
Verify that the Flex 4.5 entry appears and is selected in the
list of
Installed SDKs.
Update your project to use the Halo visual theme:
In Flash Builder, navigate to
→ → .
Select
Halo.
Click
OK to save your changes.
Configuring Flex Framework dependencies as Runtime Shared Libraries
(RSLs)
Experience Manager includes Flex Framework dependencies as Runtime
Shared Libraries. Configure your editors to use these same dependencies in
order to avoid version conflicts.
The
following dependencies ship with Tools and Frameworks and are included within
the Endeca Configuration Repository at
ifcr/tools/xmgr
. You should configure the
resources below as Runtime Shared Libraries if they are dependencies of your
editor module:
com.adobe.flex.framework.rpc-4.5.1.21328.swc
com.adobe.flex.framework.framework-4.5.1.21328.swc
com.adobe.flex.framework.textLayout-4.5.1.21328.swc
com.adobe.flex.framework.spark-4.5.1.21328.swc
com.adobe.flex.framework.sparkskins-4.5.1.21328.swc
com.adobe.flex.framework.charts-4.5.1.21328.swc
com.adobe.flex.framework.spark_dmv-4.5.1.21328.swc
com.adobe.flex.framework.osmf-4.5.1.21328.swc
com.adobe.flex.framework.mx-4.5.1.21328.swc
com.adobe.flex.framework.advancedgrids-4.5.1.21328.swc
com.adobe.flex.framework.textLayout-4.5.1.21328.swc
com.endeca.ExperienceManagerAPI-4.0.0.swf
To configure a dependency as a Runtime Shared Library:
Update your project to use the
ExperienceManagerAPI-4.0.0.swc
and the Halo
theme:
In Flash Builder, navigate to
→ → .
Add the dependency..
For example,
ToolsAndFrameworks\4.0.0\editor_sdk\libs\ExperienceManagerAPI-4.0.0.swc
.
Beneath the new SWC in the tree view, select
Link Type: and click
Edit....
Select
Runtime shared library (RSL).
For the
Deployment Path/URL:, enter the location
of the dependency in the Endeca Configuration Repository.
For example,
/ifcr/tools/xmgr/com.endeca.ExperienceManagerAPI-4.0.0.swf
.
Click
OK.
Click
OK to save your changes.
Installing the Experience Manager API to a Maven repository
The Experience Manager Editor SDK includes a Maven script for
installing the included API package into a Maven repository.
These steps assume you have
Maven 3.0.4 installed as part of your development environment.
To install the Experience Manager API package:
Navigate to the
%ENDECA_TOOLS_ROOT%\editor_sdk\reference\build\maven
directory.
Open a command prompt.
Run the
install-api
profile in the Maven POM file using the
following command:
mvn -Pinstall-api
This installs
ExperienceManagerAPI-4.0.0.swc
to your Maven
repository.