-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Durbo Serializer (response.bin payload generation) #5
Comments
Hi @jbertman! I don't have much knowledge about Durbo serialization format. What I did to construct response.bin. I configured reverse replication between AEM publish and AEM author instances on my test stand. Then I created node with JSP script on publish instance and launched reverse replication process. By sniffing traffic I created response.bin file. Later I checked that this file worked with script that mimics AEM server. |
Thanks for the pointer, @0ang3el! I'll give that a shot. |
I don't want to turn this into a support channel, but I'm having issues in even creating a reverse replicator that triggers on the content you have in the aem-rce sling script, hoping you can help. I'm able to create the content without issue (using your script), and it works perfectly on the Publish instance, but I can't seem to trigger the reverse-replication (putting the content in the outbox). Could you share how you went about setting up the agent? I tried doing it via the Sling API, miscadmin, as well as setting Thanks in advance! |
I have since figured out a decent setup utilizing the /bin/replicate Sling API. The un-intuitive key to getting replication to succeed on my end was to uncheck I was then able to manually activate my desired payload using the Sling API, like:
|
Fantastic work here @0ang3el, thanks for the hard work!
I was wondering if you could share your process for generating the response.bin payload. Hex-editing the one you have just isn't working for additional features I'd like to add to the resulting JSP. Do you have any documentation for serializing/generating the replication-ready binary?
Thanks in advance!
The text was updated successfully, but these errors were encountered: