mobile presentation format url

Hello,

Has anyone had any experience with having an additional format for certain CTD ? What is the best way to 'translate' the non-default format url?

For our mobile presentation, the default OT rendered url is http://<our domain url>/channel/ci.contentname.mobile. We would like to translate that to http://<ourmobile domain url>/channel/contentname. The default format is already being translated with ootb furl as http://<our domain url>/channel/contentname. The only difference between the mobile format url and default format url is the domain url.

Do you create your own custom mapper class, url translator class? From what I gather from the sparse documentation, you have to have both, correct?

Any suggestions, experience would be helpful.

Thanks!

Find more posts tagged with

Comments

Evgeniy_Vassaev

Hello, You can observe the Apache reverse proxy.

Please, See ProxyPass, ProxyPassReverse, Substitute and so on.

For example (httpd.conf):

ProxyRequests On

ProxyVia On

RewriteEngine On

RewriteRule /ci.contentname.mobile (.*) $http://<ourmobile domain url>/channel/contentname$1 [P,NS]

RewriteRule /mobile/(.*)$ http://<ourmobile domain url>/$1 [P,NS]

ProxyPass /vgn-ext-templating/ http://<ourmobile domain url>/vgn-ext-templating/

ProxyPassReverse /vgn-ext-templating/ http://<ourmobile domain url>/vgn-ext-templating/

ProxyPass / http://<ourmobile domain url>/channel/

ProxyPassReverse / http://<ourmobile domain url>/channel/

AddOutputFilterByType SUBSTITUTE text/html

Substitute "s|(href=\"/channel/)|href=\"/|i"

Substitute "s|(action=\"/channel/)|action=\"/|i"

……………………..

</VirtualHost>

From: eLink Entry: Discussion Group - Web Experience Management [mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Wednesday, October 02, 2013 5:20 PM
To: eLink Recipient
Subject: mobile presentation format url

mobile presentation format url

Posted byhowellc@franklin.edu (Howell, Christine) On 10-02-2013 09:05

Hello,

Has anyone had any experience with having an additional format for certain CTD ? What is the best way to 'translate' the non-default format url?

For our mobile presentation, the default OT rendered url ishttp://<our domain url>/channel/ci.contentname.mobile. We would like to translate that tohttp://<ourmobile domain url>/channel/contentname. The default format is already being translated with ootb furl ashttp://<our domain url>/channel/contentname. The only difference between the mobile format url and default format url is the domain url.

Do you create your own custom mapper class, url translator class? From what I gather from the sparse documentation, you have to have both, correct?

Any suggestions, experience would be helpful.

Thanks!

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Content Server:	Knowledge Center

Christine_Howell

Thank you for the response.

How about if the url is our 'default' url based on our website on pcs (non-mobile)? If we send an email with a link to the default url, is it possible to 'switch' to the mobile format if we determine the user clicked on the link in a mobile device?

default url: www.domain.com/channel/ciname

'default' mobile url (that is rendered as): www.domain.com/channel/ci.ciname.mobile

Is it possible to 'sniff' the device and choose the correct format to display? Ideally we'd LIKE the url to show up as something like m.domain.com/channel/ciname. But this is not as critical as know how we can select the correct format to display based on the device (pc or mobile). We already have a sniffer program on our webserver.

Thanks.

Christine_Howell

Hello,

I finally found the answer to my question. There is a generic resource attribute named request.context.modifier. Here is the description lifted from the Open Text Web Experience Management Dynamic Site and Portal Modules Configuration Guide:

request.context.modifier=
Optional – An implementation of com.vignette.ext.templating.link.

RequestContextModifier that enables you to use a custom class to modify the
request context to set specific state based on the current request.

For example, using a request modifier, you can dynamically determine a format
value based on whether the incoming HTTP request is from a wireless device or
a web browser.

I used the http://detectmobilebrowsers.com/download/jsp to help detect the device and set the format. Create a jar file containing this class and then put it in your vgn-ext-templating/WEB-INF/lib folder, restart tomcat. Also, set the request.context.modifier attribute to this class.

One key thing I found out is that you can only have one value for this attribute so if you have multiple modifier needs, put them all in a single class.