9

SDL Mobile consists of 3 parts – the API, known as the Context Engine Cartridge (CEC), the Mobile Device database, and Contextual Image Delivery (CID). The CEC is included with Tridion 2013 SP1, so it can be installed via the generic installer. However, do beware that SDL Mobile is a separately paid for module, you must have purchased this in order to use ...


8

SDL Mobile is an add-on to your existing setup. The existing setup should have the following: Content Manager Content Delivery (Deployer and CD web service) Content Presentation Ambient Data Framework XPM Once you have those items installed and working, SDL Mobile addons are: Context Engine Cartridge for the Ambient Data Framework. This includes a ...


7

The order of cartridges are not guaranteed by default, but you can control it a little bit by declaring one cartridge dependent on the output claim of another cartridge. The caveat is that the output claim must be listed in the configuration of that cartridge (and then listed as an input claim on the dependent cartridge). So if Cartridge A declares an ...


7

The problem was that the 'Repository' folder which contains the CE database was located within the /Bin/Lib folder and not directly under the /Bin folder. Moving this folder up a directory has resolved the issue.


7

John - your approach for doing some template magic sounds the right direction. You can replace the image URL with something like <img src="/cid/scale/<context:Eval runat="server" Expression="ui.thumbnailSize"/>/source/images/snow.png" /> Where ui.thumbnailSize is defined in the context vocabulary as an expression e.g. define <aspect name=...


6

Context Engine Cartridge documentation can be found here and within that information on how to download the latest device database is here EDIT (Nuno) Also check out Eric Huiza's excellent Community Webinar on this topic.


6

Bart, your comment was correct. It seemed that the target groups were published, but the extension dao (<Bundle src="storage_extension_dao_bundle.xml" />) wasn't properly set up, and the deployer_conf.xml also didn't contain the proper pipeline items (so this piece of the documentation wasn't properly installed : https://docs.sdl.com/LiveContent/...


5

DXA supports server-side responsiveness (e.g. image resizing) and uses (by default) the SDL Context Engine to get device data needed for that purpose. On SDL Web 8, DXA uses the Context Service to get access to the SDL Context Engine by default. It is also possible to configure it to get the context claims from ADF (which is used by default on 2013SP1). In ...


5

In order to successfully install/upgrade the Devices Database your server ip address needs to be added to the SDL Whitelist. Please contact to Customer Support or your sales contact in order to have this setup


4

I see 27 claims from the Context Engine. It will always create the claims, even when it cannot determine their value (that's what the Default values are for). My guess: you're not reading the right data.


4

Don't set multiple output claims: The relationship between Input and Output claims should be N-1 (so 1 output claim can have more input claims


4

This file is not mandatory. It adds client-side device detection details as you've established. If the file is not used, then the context engine will resolve the device properties using the remaining resolvers (eg user agent parser, the context device repository, or a custom expression). Clearly without the client detection JavaScript, there is no way of ...


3

If you do not have a license for SDL Mobile, but want to use the Context Engine you can use this JS file to provide most (?all) of the Context Engine claims in the ADF. It works by setting a cookie on the first page load, so any server side code using these claims will only work on second and subsequent requests (the Context Engine provides some defaults on ...


3

@Sayantan, in this case the issue is related to the iPhone's user-agent being vague. The discover-min.js can only discover the information that is made available by the vendors. In this case we can only blame Apple.


2

Have you tried setting a custom vocabulary for browser.displayWidth, but with a different default value? For example: <vocabulary> <aspects> <aspect name="browser"> <properties> <property name="displayWidth" type="integer" default="1024"/> </properties> </...


2

I looked at the code and this is how the cartridges are loaded: public static Engine newEngine() throws AmbientDataException { try { AmbientDataConfig ambientDataConfig = AmbientDataContext.getAmbientDataConfig(); Set cartridgeDefinitions = new HashSet(); Configuration config; for (Iterator i$ = ambientDataConfig....


2

Yes. You can maintain your Device Repository from a machine with internet access, and simply copy the repository to wherever it is needed. There is an undocumented Java system property that can be used to modify the location of the repository: repository.location There is also a boolean property that determines whether the repository is read only (by ...


2

Yes, you can use both libraries in the same web application. SDL Mobile capabilities are generally expressed through ADF claims so you might want to brush up on your ADF skills. DD4T doesn't itself integrate with SDL Mobile as it is essentially an MVC model provider. Your own controllers and views will have to get the information they need from SDL Mobile.


2

Do you have permissions to create the repository folder in the ..\services folder?] As per followup comment, try removing repository folder.


2

Above issue sure for cd_storage_config.xml issue on context service Here is the working config: <?xml version="1.0" encoding="UTF-8"?> <Configuration Version="8.5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../schemas/cd_storage_conf.xsd"> <Global> <ObjectCache Enabled="...


2

Check whether the "SDL Web Context Service" is running properly and "ContextServiceCapability"also properly registered in the discovery service. <Role Name="ContextServiceCapability" Url="http://tridion.sdldemo.com:8081/context.svc"/>


2

Looking at the DXA log file, the problem indeed seems to be in the Context Service: it returned an "invalid_grant" error. In general, CIS microservices do that if they are configured for OAuth authentication, but no OAuth bearer token is provided by the client (indeed, a browser will never do that). The CIL Context Client (used by DXA) should automatically ...


1

Based on Raimond's answer we contacted SDL Support who asked for our lib folders and configs. They then advised us to do two things (1) reinstall the context service (2) Add the dependent jars in our web application based off this page https://docs.sdl.com/LiveContent/content/en-US/SDL%20Web-v5/GUID-D1E194B2-E89E-45D2-8B89-26BA1940409F. Those 3x dependant ...


1

The taglib has move to context-client-taglib.jar, which is in Content Delivery/roles/context/extension-web/java/lib. As far as I know, you only need the following dependencies, apart from core CIL, including OData: context-service-common-8.5.0-*.jar context-api-8.5.0-*.jar context-client-8.5.0-*.jar


1

I think you can use the Web8 In Process Dlls from "SDL Web 8.1.1 release\Content Delivery\roles\api\in-process\dotNet\bin" inside your web application to continue using this piece of code. Indeed when using a standalone Context microservice, the devices database is part of the service, so you do not need it inside your webapp anymore, it is the main goal of ...


1

The answer in my case turned out to be incorrect values in the oauth-client-id and oauth-client-secret app settings in DXA web.config. Setting the log level to TRACE really helped here. <add key="log-level" value="TRACE" />


1

Perhaps is possible to try and detect the cookie in your app code, if it's not found, send the user to a page where this value is set ("proxy page"). Once set, then you can redirect to the relevant URL? Your proxy page can be really lightweight so you're not making major http requests etc, just a quick set of content, then move on.


1

You've not had an answer for a while so i'm going to have a go :) Is the inputDevices property functionally different between Browser Aspect and Device Aspect? Looking at the docs, they both seem to offer the same values. It's possible to use CE for more applications as well as websites so I suspect this to support any scenario. Are these based on ...


1

It looks like the ADF is using default values for the displayWidth and displayHeight claims, which means either: Your device database is not up to date (or been created) The Javascript/Cookie that sets these values in the absence of a device database is not functioning I would check that your browsers are not blocking JS or cookies, and that there are no ...


1

DXA (aka. SDL Tridion Reference Implementation) comes with a built in integration with SDL Mobile (see chapter Setting up Context Engine Cartridge (SDL Mobile) in the documentation), and since it is using DD4T as a content provider, it is the closests example I can think of that would answer your question with a clear Yes.


Only top voted, non community-wiki answers of a minimum length are eligible