By default, MDEX Web services are accessible from Experience Manager and other Workbench tools only if the MDEX Engine and Workbench are hosted on the same domain.
For example, if Workbench
is hosted on
apps.example.com, the MDEX must also be accessible
at
apps.example.com, and Experience Manager must be
configured to access the MDEX Engine at
"apps.example.com". Using the host's IP address or
an alias hostname, such as
"localhost" causes a "Security Error" alert box to
appear in Experience Manager when an editor attempts to access the MDEX Engine.
If the MDEX Engine is hosted on a different domain from Workbench, you must set up a cross-domain policy file on the MDEX Engine server. These steps apply to any Flex client application that communicates with an MDEX Engine via Web services.
To configure cross-domain access to MDEX Web services from a Flex client:
Navigate to the
/conf/dtd/xformdirectory of your MDEX Engine installation, for example:C:\Endeca\MDEX\6.4.0\conf\dtd\xformCreate an Adobe Flash cross-domain policy file,
crossdomain.xml.Configure your
crossdomain.xmlfile to grant access to all domains hosting instances of Workbench.An example is provided below:
<?xml version="1.0"?> <!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd"> <cross-domain-policy> <allow-access-from domain="*.example.com" /> <allow-http-request-headers-from domain="*" headers="SOAPAction" /> </cross-domain-policy>
The
<allow-access-from>element grants access to the local MDEX Web service from a set of domains. Thedomainattribute may be specific, or may include a wildcard, as shown above. You can include any number of<allow-access-from>elements, each for a different domain.The
<allow-http-request-headers-from>element as specified above is required. It enables Flash clients to communicate with the MDEX using the SOAP protocol.
For a complete specification of the cross-domain policy file format, please see the Adobe documentation at http://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html.
