Setting up CQ 5.4 within a weblogic environment

Make sure that CRX, and Launchpad are deployed within a weblogic domain (and the application is deployed).

Make sure that that <enforce-valid-basic-auth-credentials> is set to false (this is configured in weblogic domain/config/config.xml):
 
Look for: 

<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials> and make sure it is "false" 

If you cannot find it add it before </security-configuration> 

Within a clustered CQ environment - ensure that the enforce-valid-basic-auth-credentials is between the following XML nodes: 
------
enforce-strict-url-pattern

enforce-valid-basic-auth-credentials

cross-domain-security-enabled
------

Ensure that CQ author or publish sling.properties is configured to be a specific author or publish instance

You will find the sling.properties inside the crx-quickstart/launchpad directory
 
 "sling.properties" is located in (this is configured in /crx-quickstart/launchpad/sling.properties):
 
 There should be the following entries for a author instance:
 
 sling.run.modes=author
 sling.jcrinstall.folder.name.regexp=.*/(install|config)(.author)?$
 sling.bootdelegation.weblogic.xml=weblogic.xml.*
 
 
 There should be the following entries for a publish instance:

 sling.run.modes=publish
 sling.jcrinstall.folder.name.regexp=.*/(install|config)(.publish)?$
 sling.bootdelegation.weblogic.xml=weblogic.xml.*
 
Login into CRX (as Admin), and upload the relevant CQ content via the package manager (I am using cq-content-5.4.0.20110218.zip)

This will install two packages:

* cq-content-5.4.0.20110218.zip
* crxde-support-content-2.2.0.zip
 


It is important to add the jcr:read access to everyone (this will prevent a sling authentication issue):

 * Open up crx (add "/crx" after your host name.  Login as admin.
 * Select Content Explorer (a new browser window will open).
 * Select Security -> Access Control editor (a new browser window will open).
 * Click the "New ACE" "button" (it is difficult to see - look carefully).
 * You will need to add a new "principal" which is "everyone", allow a privilege of "jcr:read".  Click the green "tick".
 * Press the apply button, then ok.  You will see that the "everyone allow jcr:read" has been added to the ACL.


 
Your CQ/CRX is now configured for Weblogic.


If you make any changes to repository.xml - ensure that you make the same changes in repository-template.xml
  
CQ message "AuthenticationSupport service missing. Cannot authenticate request." - you need to make sure the admin password on the author/publisher is the same as the Felix console


Change the post-range which CQ is using.  Open crx-quickstart-1/repository/repository.xml Look for:

    <Cluster>
        <Journal class="com.day.crx.persistence.tar.TarJournal">
                <param name="portList" value="8020-8029"/>
        </Journal>
    </Cluster>

Add the portList param.