Chuyển đến nội dung chính

[ENVIRONMENT] Author and Publish environments (codes, bundles) out of sync

ISSUE:

I have configured two environments of CQ5.5, Author (at 4502) and Publish (at 4503). Initially, when I just created pages based on default templates, the publishing went on just fine. I even activated using workflows..
However, when I created my own components/templates/jsp's, the pages stop getting fdeployed on Publish Environment. Now, even after activation (green light), the pages on publish environment display just a blank page and nothing else.
I checked and found that all my new components/templates/jsp's etc. are not present in the 4503 node. Any way to keep them in sync ?

RESOLVED:

The issue isn't that your pages aren't being activated. They are likely in fact being activated just fine. You can verify this by examining the content tree on your publish instance. The issue is that the components you created and are using on those pages aren't present on the publish instance - as you noted. It's important to keep in my that CQ won't activate components / templates associated with a Page. You need to deploy your code - there a number of ways you can do this, the best will depend on your environment / needs. A few possible options are the following:
  • Create a Package of your code and activate the package
  • Use Tree activation to activate everything you've created under /apps (http://localhost:4502/etc/replication/treeactivation.html)
Note that if you added any OSGI Bundles to Felix via the Web Console, then you'll need to manually add those to your publish instance via the Felix Web Console there. However, I'd really recommend adding any necessary Bundles to your application code at /apps/<application>/install. This will allow the Bundles to be included in either of the 2 methods mentioned above.

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene...
Đăng nhận xét
Đọc thêm

How to custom CQ Login Module

In order to manage the login process in our project, we will use a custom CQ Login Module. We will admit the root URL of CQ instance is: http://localhost:4502/ . This value may change depending of your environment. The %CQ_HOME% variable we will mention refers to the CQ install path. It admits you have defined %CQ_HOME% as an environment variable. 1.         Update the repository definitions The login module must be referenced in the repository definitions. You have to edit the next file: %CQ_HOME%/crx-quickstart/repository/repository.xml Do a copy of repository.xml to repository.xml.original In repostiory.xml, replace  security  part of repository.xml with following: <Security appName="com.day.crx">         <SecurityManager class="com.day.crx.core.CRXSecurityManager"> <WorkspaceAccessManager class="org.apache.jackrabbit.core.security.simple.SimpleWorkspaceAccessManager"/>  ...
Đăng nhận xét
Đọc thêm

[DAM] Custom DAM management / Add 'Alt' into images

Issue: We need, for each asset to be able to edit the ‘alt’ text. The ‘alt’ text must be used on the site each time an asset is displayed. When displaying an asset, the mechanism is the following : -       Get the Locale from the request -       When getting the asset, get the associated Alt property corresponding to the locale. -       Populate the alt attribute with this value. Resolution: To achieve this, we can customize the DAM Asset Editor. The AssetEditor is the form used to input asset properties and metadata. Below is a screenshot of a customized form with four “alt” input (for four different locales). The DAM uses the following nodes to render Asset Editor forms: -       /libs/dam/content/asseteditors/formitems -       /libs/dam/content/asseteditors/images/formitems -      ...
Đăng nhận xét
Đọc thêm