Expand my Community achievements bar.

SOLVED

AEM 6.1 siteadmin page on publisher

Avatar

Level 2

Hi,

I tried to install aem 6.1 with "java -jar cq-publish-p8081.jar -r publish,nosamplecontent" option and when I login to publisher with admin user and go to http://localhost:4503/siteadmin. The page is an empty page with no content. If I do the same without nosample content option then all works fine as expect. Can some one help on this issue ?

Thanks

Bipin

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi,

if installing I am installing AEM on a server, I always use the following approach:

First I unpack the jar file

java -jar <aem-version>.jar -unpack

Once unpacked I edit the start script in "crx-quickstart/bin"

Change the runmode, add any options such as nosampleconent, modify the HEAP allocated. Here is an example script for an author instance[0]. I then use the script to start AEM. 

Regards,

Opkar

[0]https://gist.github.com/jayankandathil/47bf5113d91e42903ddb

View solution in original post

11 Replies

Avatar

Level 10

Hi Bipin,

According to your command, your publish instance should be started with port 8081. Can you try with http://localhost:8081/siteadmin

Avatar

Administrator

Hi 

As mentioned by Lokesh, It seems that your Publish instance is on Port 8081, try with http://localhost:8081/siteadmin.

Please have a look at the section of Documentation below :-

Link:- https://docs.adobe.com/docs/en/cq/5-6-1/getting_started/download_and_startworking.html

Installing a Publish Instance

NOTE

 

 

If you are installing both your author and publish instances on an Amazon EC2 web service, see Installing AEM on an Amazon EC2 web service before starting the Publish instance. You must modify some start settings or the Publish instance will not function.

 

To set up a publish instance on port 4503 of the desired host, you perform the same steps as in installing an author instance except that you create a directory named publish (instead of author) and you rename the quickstart.jar file ascq5-publish-p4503.jar. You can select any port number.

To install a publish instance:

  • On the host file system, create a directory and name it publish.

  • Copy the cq5-<version>.jar file into publish/.

  • Rename cq5-<version>.jar to cq5-publish-p4503.jar.

    If you need a different port this can be set in the filename.

  • Copy a valid license.properties file into publish/ as well (the same directory as the cq5-publish-p4503.jar file).

    If you do not provide the license.properties file, AEM will redirect you to the Welcome screen when starting the application, where you can enter a valid license key. You will need to request a valid license key from Adobe if you do not yet have one.

  • Start AEM Quickstart using one of the following methods:

    • If using a GUI file-system explorer, double-click the cq5-publish-p4503.jar file.
    • If using the command line, for a 32bit VM type:

      java -Xmx1024M -jar cq5-publish-p4503.jar

      Or, for a 64bit VM, type:

      java -XX:MaxPermSize=256m -Xmx1024M -jar cq5-publish-p4503.jar
    • Use a custom script located in the crx quickstart folder, such as start.bat to start AEM.

      The Start and Stop scripts are for UNIX, Linux, and Macintosh. The start.bat and stop.bat scripts are for Windows.

      You cannot use a custom script when you install the AEM quickstart jar file (the first time it is started) unless you expand the file first. Use the -unpack option on the command line to unpack the contents before running the script as in java -jar cq5-publish-p4503.jar -unpack.
  • When the installation is completed, you can browse your site (for example,http://localhost:4503/content/geometrixx/en/company.html

    I hope this would help you.

    Thanks and Regards

    Kautuk Sahni



    Kautuk Sahni

    Avatar

    Administrator

    Reference Link:- https://docs.adobe.com/docs/en/aem/6-1/administer/security/production-ready.html

    // Running AEM in Production Ready Mode

    In order to run AEM in production ready mode all you need to do is add the nosamplecontent via the -r runmode switch to your existing startup arguments:

         
    1
    java -jar aem-quickstart.jar -r nosamplecontent

    Code samples are intended for illustration purposes only.

    For example, you can use the production ready to launch an author instance with MongoDB persistence like this:

         
    1
    java -jar aem-quickstart.jar -r author,crx3,crx3mongo,nosamplecontent -Doak.mongo.uri=mongodb://remoteserver:27017 -Doak.mongo.db=aem-author

     

    I hope this would help you.

    Thanks and Regards

    Kautuk Sahni



    Kautuk Sahni

    Avatar

    Level 2

    Sorry my bad I typed wrong port in my questions above. I actually used http://localhost:8081/siteadmin only. It still fails.

    Also does the name of the start file have to be "aem-quickstart" to run production ready mode ? or can i use cq-publish-p8081 ? is it cq-publish-p8081 or cq5-publish-p8081 ?

    Avatar

    Level 10

    you can use cq or cq5 or aem in the filename and it should work. You dont have to say 'publish' are -r as the file name itself say it is publish in your case. Can you try with this 

    "java -jar cq-publish-p8081.jar -r nosamplecontent

    Avatar

    Level 2

    I tired that and if I dont give publish then the instance loads in author mode.

    Avatar

    Level 6

    please try below

    java -jar cq-publish-p4504.jar 

    and check siteadmin console and provide erorr log.

    Avatar

    Level 2

    java - jar cq-publish-p4504.jar does work but we need to setup AEM 6.1 publishers for production, hence we are trying production ready mode as "java -jar cq-publish-p8081.jar -r publish,nosamplecontent". I checked all logs and don't see any errors reporting.

    Avatar

    Level 2

    Found the fix as per the documentation here https://docs.adobe.com/docs/en/aem/6-1/administer/security/production-ready.html "Apache Sling GET Servlet" settings are changed.

    For publisher mode json.maximumresults is made 100. I changed this setting in my publisher as same as author which is changing back to 1000 (publisher is set to 1000 when you dont install AEM with nosampleconent) fixed the issue. May be its a bug in AEM 6.1

    Thanks for all the comments.Hope this helps

    Avatar

    Correct answer by
    Employee

    Hi,

    if installing I am installing AEM on a server, I always use the following approach:

    First I unpack the jar file

    java -jar <aem-version>.jar -unpack

    Once unpacked I edit the start script in "crx-quickstart/bin"

    Change the runmode, add any options such as nosampleconent, modify the HEAP allocated. Here is an example script for an author instance[0]. I then use the script to start AEM. 

    Regards,

    Opkar

    [0]https://gist.github.com/jayankandathil/47bf5113d91e42903ddb