So, what exactly happened in Vegas… I mean Adobe Summit 2017?

Share Button

The Clouds split! Literally. If you don’t know what I mean, here’s a visual.

Of significance is the introduction of the new Adobe Advertising Cloud. Here’s the live tweet that is relevant:

Adobe Analytics is now it’s own Cloud offering and combined with Audience Manager (a product to capture non-authenticated user data) into a single Analytics Cloud.

and Adobe Marketing Cloud has had significant upgrades. We will summarize the significant updates below –

Adobe Experience Manager 6.3 has been introduced. With 6.3, you can now re-use content across experiences using Content Fragments and Experience Fragments.

AEM 6.3 Assets also receives significant performance upgrade.

And Adobe Marketing Cloud comes with better integration with Creative Cloud products (like Photoshop)

With over 70% (by our guestimates) of the attendees either using or interested in Adobe Analytics, it goes without saying that Adobe Analytics and Audience Manager products received several updates.

Adobe Campaign released a new version and has better integrations with AEM and Analytics.

So, where is Adobe placing it’s bets for the future?

What’s a blog without comments, right? Do share your comments below – we would love to hear your perspective of the Adobe Summit!

How OpenText TeamSite meets Gartner’s WCM standards

Share Button

On Nov 10, 2011 and again in 2012, 2013 and 2014, Gartner released it’s annual “Magic Quadrant for Web Content Management“. As seen in the quadrant, HP Autonomy product stack is a clear leader. In this post we  take each fundamental WCM feature that Gartner puts forth and discuss it from an HP Autonomy Product stack’s implementation perspective.

Gartner’s comments are in italics and bold. Read on, and feel free to provide your comments below.

Continue reading “How OpenText TeamSite meets Gartner’s WCM standards”

Getting Vanity URLs right in an Adobe AEM implementation

Share Button

So your friendly marketing executive calls to say he needs a Vanity URL for a page on your AEM hosted site. And you cringe. How do you get this done right without getting penalized by Search Engines? Should you do this at the Load Balancer level? Within AEM Dispatcher configurations? within AEM Publish instance? What about horizontal replication of these configurations? And oh, who’s going to maintain this? It’s not like your Dev Ops team is necessarily twiddling their thumbs waiting for work.

This post will address a few different ways to accomplish Vanity URLs within an Adobe AEM implementation and discuss some pros and cons.

Most well-architected AEM implementations have a 80-20 or even a 90-10 rule. ie., serve 80 or 90% of web traffic from your Dispatcher without hitting the AEM publish instance. That means it is best to implement URL rewrites (ie., Vanity URLs) at the Webserver or the Dispatcher level.

Here’s a good resource on  how it can be done using in Apache HTTP server (note that this has nothing to do with Adobe AEM):

http://httpd.apache.org/docs/2.0/misc/rewriteguide.html

However, if you want to approach this entirely from an AEM product stack perspective, you can achieve that as follows.

1. Setting Vanity URLs within the AEM page properties:
Here’s a screenshot that shows how the Vanity URL for a page is set. This is a great technique WHEN you are fine with the content authors having the ability to change this property.

aem-vanity-url
In addition CQ5 provides the “Alias” page property. See screenshot below.

aem-alias2

 

Aliases do not change the path to the page, but rather provide an alternate name to the page. For example, this is useful when you would like the pagename to be different in different languages.

 

2. Now, let’s say you are positive that you do not want your content team making changes to vanity URLs or Aliases, you could rely on Apache Felix (the underlying application server that hosts your Publish and Author instance). These configurations are typically only allowed for Administrators. The following screenshot of the Sling Resource Resolver should help you with this configuration.

aem-sling-resource-resolver

Programmatically, you may access the mapping like so:

resourceResolver.map(slingRequest,path);

3. Now, there’s yet another way to accomplish rewrites within AEM, which is to configure your /etc/map. Here are the steps:

1. configuration tree located below /etc/map
2. create a new folder: type sling:Mapping
3. define sling:match – partial regular expression which is used instead of the node’s name to match the incoming request
4. define sling:redirect or sling:internalRedirect depending on the type of redirect

 

I hope that gave you an idea on different ways in acheiving similar goals.

 

Until next time!

6 takeaways from Adobe Summit 2015 #AEM6

Share Button

summit

Even before the Adobe Summit, that took place in March 9th to 13th, 2015 in Salt Lake City, UT, Forrester had this to sayAdobe was a runaway winner across a broader digital experience delivery portfolio”. 

Adobe put a great show (including a concert by Imagine Dragons!) and displayed a wide range of digital marketing products and integrations. It was fun. It was Radioactive!

“Marketing” for marketing aside, there was a lot of ‘meat’ in the conference as well. So, without much ado, here are our 6 takeaways from Adobe Summit 2015.

      1. Adobe Marketing Cloud now has two new stars, if you get the pun – Adobe Audience Manager and Adobe PrimetimeAudience Manager is just another name for what the industry calls ‘customer segmentation’. The difference here is that it provides a central data platform to aggregate all your customer profiles from various data sources and group them into ‘audiences’. These audience profiles can then be used to target your marketing across channels and devices. Primetime integrates with Adobe’s analytics platform and also Audience Manager and is most helpful, as you may have guessed, to organizations that generate revenue based on advertising. For example, using Primetime you may target an ad to XBox users meeting certain criteria. You can read more about Primetime here.
      2. As with prior Adobe Summit conferences, Analytics played a big role in Adobe’s messaging. This is not surprising from the fact that historically, the Salt Lake City, UT conference was an Omniture/ SiteCatalyst (now called Adobe Analytics) conference. Adobe announced new features to advance the analytics platform including Contribution Analysis and Customer Attributes.Contribution Analysis: If you have ever tried to read a web (or other) analytics report, you will know there are always outliers and anomalies that skew the data. With Contribution Analysis, you can now navigate to the anomalies section and get a concise understanding of these anomalies without necessarily having to do all the hard work ofsieving through the data. In short, integrating with Analytics, it helps with the following:
        • Analyzes immense amount of data in seconds, rather than consuming weeks of data scientist time
        • Provides automated advanced analytics usable by non-quant analysts
        • Offers a rich, intuitive, interactive user experience tied to segment creation
        • Analyzes customer attributes including offline ones imported from your CRM solution
        • Customer Attributes: Customer attributes is useful if you need to tag your customer after logging in, and surface/tag the customer across the experience. This is similar, yet different from classification and provides a powerful way to track your customer behavior end-to-end. The caveat, is that implementing a useful customer attributes solution can be complex.
      3. Adobe Experience Manager also received several updates. AEM (previously called CQ5 or Day Communique) has matured significantly over the last couple of years and it was no surprise that there was a lot of activity in the form of hands-on labs, customer stories and new announcements. Notably,
        AEM version 6.1 will be available in Q2, 2015.
        As of this writing (March, 2015), the latest AEM version available is 6.0 Service Pack 2. One Adobe Engineering manager I talked to encouraged us to be part of the beta program for 6.1 – which  we recommend to our clients as well, if they have development cycles and sand-box environments to spare.There has been a major overhaul of the underlying content repository from version 5.6, which uses CRX2 to 6.x which uses Apache Jackrabbit OAK as the storage repository. There are some things to consider when you upgrade and since Apache Jackrabbit OAK is at version 1.0.xxx, there are some gotcha’s that customers need to be aware of. Talk to us if you are in the process of an AEM upgrade and we can help you navigate through some pitfalls.
      4. From an overall solutions perspective, the ElasticPath commerce integration with AEM is noteworthy. ElasticPath, a commerce product vendor, announced it’s upgraded Cortex API, that integrates with AEM 6.x versions. Unlike other integrations we have seen, this solution provides an easy to integrate, Java OSGi based Component model. There was a client session, where Adobe, ElasticPath and McGraw Hill Education (client) discussed their solution. This was a great example of multiple parties coming together to put together a solution that other organizations could benefit from.
      5. Adobe announced new development tools for AEM which was well received by the technical community at the Summit. Sightly, the new front-end development tool is gaining popularity with AEM 6.0 customers. Sightly version 1.1 is to be announced in Q2, 2015. As with most ‘easy’ to use development tools, Sightly comes with some performance considerations. Adobe engineers told us that with version 1.1, Sightly is just as performant as using JSP within your Components. As with most performance metrics, one needs to be careful how it is used. Autowoven can help make the right choice, so talk to us if you are considering switching to Sightly as your front-end development language.
      6. Adobe announced AEM Screenscoke-aem-screensAEM Screens was demonstrated during the key note sessions and it wow’ed the audience. During the demo, using a few clicks within AEM, a content author was able to “slide” a new promotion from their system to .. and this needs a pause.. to .. the Times Square billboard! A new, personalized Coke promotion was pushed to the giant Times Square billboard in Manhattan in just a few clicks and swipes. Social media reaction to this announcement was.. priceless!

 @davidnuescheler “I injured my shoulder throwing assets across the screen” #priceless #AdobeSummit

 

Did you attend the Summit? Let us know your comments. Interested in scheduling a time to talk with autowoven’s Adobe Certified experts? Contact Us for a free discovery session. 

Adobe AEM (CQ5) and OpenText TeamSite: 10 things in common

Share Button

Among  enterprise-class web experience management systems, the two most sophisticated systems that are often pitted against each other are HP TeamSite and Adobe Experience Manager. Both Forrester and Gartner rank these products highly and often place them as leaders in the digital experience (aka content marketing/ web experience management/digital engagement/ customer experience management) space.

Technologically, at their core, the products are very different. A developer may cringe to read “similar” and these product names in the same sentence. However, we are going to look at it from the perspective of a business user – a marketer who potentially uses this system versus a technical administrator or developer.

Continue reading “Adobe AEM (CQ5) and OpenText TeamSite: 10 things in common”

Top 5 reasons TeamSite Migration / Upgrade projects fail

Share Button

At autowoven we have seen our share of new TeamSite implementations as well as migration / upgrade projects.  While there are quite a few reasons why migration projects could fail. Here are the top 5 reasons.

  1. Not following the proper TeamSite version upgrade path
  2. Project led by an entity (team lead / professional services team) not having prior migration experience
  3. Not allocating necessary down time of systems
  4. Not considering encoding issues (visual format/ tinymce)
  5. Assuming APIs used in customizations are forward compatible

 

For details on how to avoid the many pitfalls and complete projects on time and within budget, talk to us today!

7 takeaways from HP Engage 2014

Share Button
HP Engage 2014

 

HP brought together it’s customers and partners of it’s digital marketing line of products in Phoenix, AZ this fall. The event held in September over 3 days included analysts, partners and customers interested in the following line of products:

  • HP Exstream
  • HP Qfiniti
  • HP TeamSite
  • HP IDOL
  • HP Optimost
  • HP Explore
  • HP MediaBin
  • HP Aurasma

 

Autowoven was a proud silver sponsor and the team demonstrated  capabilities in Mobile First integration, HP TeamSite, LiveSite and IDOL products.


Without further ado, here are the 7 takeaways on the HP Engage 2014 event:
Continue reading “7 takeaways from HP Engage 2014”

5 things you need to know about TeamSite Mobile module

Share Button

UPDATED September 16, 2014 – to reflect new, on-the-field, experiences delivering Mobile First design…

 

 

Starting TeamSite 7.4, HP users can  avail the mobile add-on module. Here are 5 things you need to know about this module:

Continue reading “5 things you need to know about TeamSite Mobile module”

Migrating/ Upgrading TeamSite Installations

Share Button

Migrating TeamSite Installations

 

This article describes how to take an existing TeamSite installation and rebuild or replicate it on a new server or on a new TeamSite release. It describes particular compatibility issues with backing store migration and lists some of the configuration and customization information that needs to be copied. Although this document is meant to address migration issues across all the supported platforms, it also gives steps needed to migrate from old TeamSite 6.x on Linux or AIX to TeamSite 7.1 on Linux.

Continue reading “Migrating/ Upgrading TeamSite Installations”

TeamSite 7.4.1 Patch / Update 1

Share Button

HP TeamSite 7.4.1 along with LSCS and LSDS has over 100 updates and bug fixes since version 7.3.2.

While this includes several usability features, the new 7.4.1 version does have a bug. This blog post gives some background on the affected feature and the bug information. If you are not an existing HP TeamSite user, you may ignore this blog post 🙂

Continue reading “TeamSite 7.4.1 Patch / Update 1”