When starting CQ 5.6 author and publisher instances for the first and subsequent times, how can we provide them with an IP address rather than localhost? | Community
Skip to main content
LinearGradient
Level 6
October 16, 2015
Solved

When starting CQ 5.6 author and publisher instances for the first and subsequent times, how can we provide them with an IP address rather than localhost?

  • October 16, 2015
  • 1 reply
  • 767 views

Hi,

I am working on Dockerizing our CQ 5.6 deployment for local development.

For local development, we have 1 author instance, 1 publisher instance, 1 author dispatcher, and 1 publisher dispatcher.

The author instance is assigned an IP address of 192.168.78.1 and the publisher is assigned an IP address of 192.168.78.2.

When I start the instances for the first (and subsequent) time(s), how can I configure them so that they know they should communicate via the given IP addresses rather than localhost?

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JustinEd3

Hi,

You can do this by setting the transportUri property of /etc/replication/agents.author/publish/jcr:content and /etc/replication/agents.author/publish_reverse/jcr:content

e.g. with curl

curl -F"transportUri=http://192.168.78.2:4503/bin/receive?sling:authRequestLogin=1" -u admin:admin http://192.168.78.1:4502/etc/replication/agents.author/publish/jcr:content

This would first require testing that AEM was up (or otherwise looping until the curl command returned 200)

Regards,

Justin

1 reply

JustinEd3Adobe EmployeeAccepted solution
Adobe Employee
October 16, 2015

Hi,

You can do this by setting the transportUri property of /etc/replication/agents.author/publish/jcr:content and /etc/replication/agents.author/publish_reverse/jcr:content

e.g. with curl

curl -F"transportUri=http://192.168.78.2:4503/bin/receive?sling:authRequestLogin=1" -u admin:admin http://192.168.78.1:4502/etc/replication/agents.author/publish/jcr:content

This would first require testing that AEM was up (or otherwise looping until the curl command returned 200)

Regards,

Justin