Separate logger configuraiton for workflows | Community
Skip to main content
GK-007
GK-007
Level 9
October 16, 2015
Solved

Separate logger configuraiton for workflows

  • October 16, 2015
  • 16 replies
  • 2959 views

Hi All,

I have custom workflow and we are seeing issues while it's running but we are not getting any relevant information in error.log.

I heard to configure a separate log for workflows we need to include out of the box workflow packages.

If anyone knows please give me the those out of box packages and i will configure a log.

Thanks,

Kishore

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 GK-007

Finally ,

I have solved this issue by following below steps.

And observed my instances folder is created with incorrect sling:resourceType not sure why it's creating like that.

http://aemtips.blogspot.in/2013_05_01_archive.html

Issue while initiating workflow

 

 

Problem: I've deleted 'instances' folder inside /etc/workflow/ directory.  When I initiate the workflow, the folder 'instances' is automatically created under /etc/workflow/ but the workflow is not triggered on the payload.

Solution:

  • Make sure to delete the instances folder.
  • Save the changes
  • Create a instances node of type sling:folder
  • To the instances node add a property sling:resourceType with value equal to ‘cq/workflow/components/instances’

        Also add property jcr:title Instances

  • Restart the workflow bundle from felix console or restart the instance    

16 replies

Show previous replies
GK-007
GK-007Author
Level 9
October 16, 2015

Selecting page in site admin and then right click on it selecting workflow option from context menu,select workflow name.

I have followed the same steps mentioned and added payload but workflow is not starting.

Thanks,

Kishore

GK-007
GK-007Author
Level 9
October 16, 2015
I got below response when hitting http://<hostname>:<port>/libs/cq/workflow/content/console/workflows.json {"workflows":[{"wid":"/etc/workflow/models/eLibrary-Approval-Workflow/jcr:content/model","label_xss":"eLibrary Approval Workflow","label":"eLibrary Approval Workflow","description_xss":"No Description","description":"No Description","isCqPage":true}],"results":1}

Still seeing same exception.

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
October 16, 2015

You only have a single workflow in your system?

When you go to the launcher tab, is your workflow definitely enabled? /libs/cq/workflow/content/console.html

Is the runmode the right one for the instance you are testing this? (You are on the author instance, right?)

Regards,

Opkar

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
October 16, 2015

Are you stills seeing the same error you posted previously?

What happens when you hit the url: http://localhost:4502/libs/cq/workflow/content/console/workflows.json

Regards,

Opkar

GK-007
GK-007AuthorAccepted solution
Level 9
October 16, 2015

Finally ,

I have solved this issue by following below steps.

And observed my instances folder is created with incorrect sling:resourceType not sure why it's creating like that.

http://aemtips.blogspot.in/2013_05_01_archive.html

Issue while initiating workflow

 

 

Problem: I've deleted 'instances' folder inside /etc/workflow/ directory.  When I initiate the workflow, the folder 'instances' is automatically created under /etc/workflow/ but the workflow is not triggered on the payload.

Solution:

  • Make sure to delete the instances folder.
  • Save the changes
  • Create a instances node of type sling:folder
  • To the instances node add a property sling:resourceType with value equal to ‘cq/workflow/components/instances’

        Also add property jcr:title Instances

  • Restart the workflow bundle from felix console or restart the instance    
GK-007
GK-007Author
Level 9
October 16, 2015

yes ,i have only single workflow in my AEM instance.

Actually my workflow need not be triggered on any repository based events ,user will select the page in siteadmin and trigger workflow on it.

Once again thanks for sparing time on this issue.

Terms & ConditionsAccessibility statement

Loading footer...