is there any option like : repctl exportrepository all, so all tasks exported in separate json files

[selvakumars]

is there any option like : repctl exportrepository all, so all tasks exported in separate json files

I understood, 

repctl -d <"...Attunity\Replicate\data"> exportrepository <------ This will export all tasks in single json file

repctl -d <"...\data"> exportrepository exportrepository task=<"taskname"> <--- will export a single task in a single json

Is there any option like:

repctl -d <"...\data"> exportrepository all  <<<<<< something like this, which will export all tasks but in separate individual json files?

Kindly advise

with regards,

Selvakumar S

[selvakumars]

Thank you John / Heinvandenheuvel.

I will open a support ticket.  Thank you

[selvakumars]

Hi John Wang, 
00166147 has been raised, can you please check this ticket and update

[sureshkumar]

Hello @selvakumars 

Thanks for opening a support ticket, our Support Team members will work on the issue.

Regards,

Suresh

[DesmondWOO]

Hi @selvakumars ,

QEM lists all tasks from different Replicate servers. Are these 79 tasks originating from the same Replicate server?

Regards,
Desmond

[DesmondWOO]

Hi @selvakumars ,

Thanks for submitting a ticket, but I would recommend checking repcmd.log whether you find any error during exporting.

Regards,
Desmond

[Heinvandenheuvel]

>>> 00166147 has been raised, can you please check this ticket and update

Once you submitted a ticket you have to trust the system. There will be a triage, a priority assigned and a support engineer will look at it, based on that. You'll be update when there is significant information.

Back to the 30 out of 79 - I maintain that the only reasonable explanation is the you are not providing the live data directory on the REPCTL command line. Did you verify with the "-d" option provided in the command line for the running server process? For Linux, just use ps -ef | grep  repctl or similar. For windows use the task manager go to details and add the command line column.

You may also want to go to the source. Use a SQLliteBroswer to check on C:\Replicate\data\tasks\RepoGlobal.repo (in your data directory, not mine 🙂 ).  In the repobjects table look for 'type=3'. More importantly look in the 'tasks' table and check the 'last_run_time', 'last_save_time' columns. Do those make any sense?

Back to the original SPLIT problem.

I think it will be best to give this as text parsing an exercise  to an intern or resident geek. Look for the command_definition ... tasks and the first tasks.task.name while copying everything verbatim into 'header'. grab the name for output file name, copy header + task text. Once the end of the task array is reached skip the rest until "_version" top element. This is required to be as the 'tail'. You may want to pre-scan the input json first to get that tail to tag onto the individual tasks.

Having said that, and it being a rainy slow morning here, I made and attempt to perform this parsing the JSON first. For years I have a PowerShell script  to do various manipulations to Replicate (or AEM) JSON exports. It was easuy enough to add a -SplitTasksDir and -SplitEndPointsDir option to that.

What can I say... it works for me. Only tested with json file input and outputs, not with AEM. Because it uses Powershell ConvertTo-Json to generate the text it looks different from to original with respect to whitespace. There is some post-processing done to make it look more similar (good enough for Windiff to be useful).

Attached as .txt

Hein

[john_wang]

Greatly agree with @Heinvandenheuvel . Besides that we noticed some tasks name length exceeds 32 chars which may introduce potential issues. Please take note the limitation: The name cannot exceed 32 characters. For example:

CDC-OraERPTST_DISTRIBUTION_DOMAIN HIST To SnowTST CDC-OraERPTST_DISTRIBUTION_DOMAIN To SnowTST

CDC-OraERPTST_PROCUREMENT_DOMAIN HIST To SnowTST CDC-OraERPTST_PROCUREMENT_DOMAIN To SnowTST

These tasks name length exceeds 32 chars, their first 32 characters are identical, making it difficult for Replicate to distinguish between them. Please shorten and rename the tasks to ensure they are properly identified.

Regards,

John.