Difference between revisions of "Integration/ContentConnector"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
Line 5: | Line 5: | ||
== Tempus Serva setup (provider) == | == Tempus Serva setup (provider) == | ||
# Make the request that suits youre needs | |||
#* Filters and parameters | |||
#* Sorting / grouping | |||
#* Fields to display | |||
#* Fields to display | |||
#* Page size | |||
# Save the view | |||
# Click on the view and copy the parameters | |||
== CMS system setup (consumer) == | == CMS system setup (consumer) == |
Revision as of 20:03, 21 January 2014
CMS content provider
Tempus Serva setup (provider)
- Make the request that suits youre needs
- Filters and parameters
- Sorting / grouping
- Fields to display
- Fields to display
- Page size
- Save the view
- Click on the view and copy the parameters
CMS system setup (consumer)
Overcoming XSS protection
I cases where the TempusServa server and the CMS system is on different domains (ex. acme.shared.com and cms.acme.com), browsers will prevent pages from accessing content from other servers.
Three options exist
- Set up server to allow XSS (not recommended)
- Use server side includes (ok, but not supported everywhere)
- Set up a mini proxyserver
A mini proxyserver written i PHP is very simple (aspx/jsp will have similar features).
<?php echo file_get_contents("http://myserver.dk/TS/cmsinterface?q=".$_GET["q"]."&v=".$_GET["v"]);
Afterwards you just make the calls through the proxy using exact same parameters.