8 Replies Latest reply on Aug 17, 2020 11:35 AM by Kiran Ruhil

    P360_JMS_Demo_DataQuality BPM workflow

    Kiran Ruhil Guru

      Hi all,

       

      I am exploring OOB the P360_JMS_Demo_DataQuality workflow for calling DQ rules from active vos. I have setup the required message queue configuration, and able to send message request using P360SendPortType partner. In response, error message is received as 'Unauthenticated'.

       

      Shipped workflow has variables P360User and Password, and have provided the PIM user and password with full permissions. Can anyone help me, what could be the issue?

        

      Partner details as follows:

       

      Any help will be very much appreciated.

       

      Regards,

      Kiran

        • 1. Re: P360_JMS_Demo_DataQuality BPM workflow
          Sai Narasimha Prasad Rebba Guru

          Hi Kiran,

           

          Did you setup Queues in the Avos Message Queue ? And also did you deploy the core project(workflow) that will be part of accelerators.

           

          Thank you

          Sai Prasad

          • 2. Re: P360_JMS_Demo_DataQuality BPM workflow
            Kiran Ruhil Guru

            Hi Sai

             

            I have setup Avos message queues and also deployed the core project part of accelerator.

             

            Regards,

            Kiran

            • 3. Re: P360_JMS_Demo_DataQuality BPM workflow
              Sai Narasimha Prasad Rebba Guru

              For me it looks like the rest user authentication issue or the the user details you might have provided for ActiveMQ was incorrect.

               

              Note: please have a check again once you made changes in project for rest user details make sure to save and redeploy the bpd.

               

              Thank you
              Sai Prasad

              • 4. Re: P360_JMS_Demo_DataQuality BPM workflow
                Lokesh Kumar Guru

                Hi Kiran,

                 

                Couple of things where there will be authorization checked:

                 

                 

                1. Is it happening with new processes as well and you see messages piling in ActiveMQ ? If so verify below.

                2. When ActiveVOS is sending message to MessageQueue. -> Verify credentials of configured MQ provider .

                3. When P360 server is consuming the message. -> verify the username,password at P360 side is same as defined in workflow.

                 

                - Lokesh Kumar

                • 5. Re: P360_JMS_Demo_DataQuality BPM workflow
                  Kiran Ruhil Guru

                  Hi Lokesh,

                   

                  I verified passwords are correctly mentioned. In workflow, we updated username and password to rest and heiler, same user is available in PIM environment.

                   

                  I can see messages as well in Active MQ.

                   

                  Few pointers which may help, do you think below settings are okay or do i have to change something

                  1. ActiveMQ messaging service is not marked as default JMS queue.

                  2. below properties are disbaled in server.properties

                   

                  Regards,

                  Kiran

                  • 6. Re: P360_JMS_Demo_DataQuality BPM workflow
                    Sai Narasimha Prasad Rebba Guru

                    Hi Kiran,

                     

                    Once you create a message Queue in ActiveMQ you should be able to see all the queue which you configured in server.properties

                     

                    some default properties in my local setup for your reference:

                     

                     

                    queue.default.type = ActiveMQ

                    queue.default.writer.count = 5

                    queue.default.consumer.count = 5

                    queue.default.url = tcp://localhost:61616

                    queue.default.username = admin

                    queue.default.password = admin

                    queue.default.message.format = XML

                    queue.default.delivery.delay = ${defaultDeliveryDelay}

                     

                    # Note: the ${defaultDeliveryDelay} is a calculated value. If more than 1 server node is configured in the network configuration, its value is 10000 and otherwise 0.

                     

                    queue.dq.type = ${queue.default.type}

                    queue.dq.writer.count = ${queue.default.writer.count}

                    queue.dq.consumer.count = ${queue.default.consumer.count}

                    queue.dq.url = ${queue.default.url}

                    queue.dq.username = ${queue.default.username}

                    queue.dq.password = ${queue.default.password}

                    queue.dq.message.format = XML

                    queue.dq.name = P360_DATA_QUALITY

                    queue.dq.label = Data Quality

                    queue.dq.delivery.delay = ${queue.default.delivery.delay}

                     

                    queue.bpm.type = ${queue.default.type}

                    queue.bpm.writer.count = ${queue.default.writer.count}

                    queue.bpm.consumer.count = ${queue.default.consumer.count}

                    queue.bpm.url = ${queue.default.url}

                    queue.bpm.username = ${queue.default.username}

                    queue.bpm.password = ${queue.default.password}

                    queue.bpm.message.format = XML

                    queue.bpm.name = P360_BPM

                    queue.bpm.label = BPM

                    queue.bpm.delivery.delay = ${queue.default.delivery.delay}

                     

                    queue.serviceapi.type = ${queue.default.type}

                    queue.serviceapi.writer.count = ${queue.default.writer.count}

                    queue.serviceapi.consumer.count = ${queue.default.consumer.count}

                    queue.serviceapi.url = ${queue.default.url}

                    queue.serviceapi.username = ${queue.default.username}

                    queue.serviceapi.password = ${queue.default.password}

                    queue.serviceapi.message.format = XML

                    queue.serviceapi.name = P360_SERVICE_API

                    queue.serviceapi.label = Service API

                    queue.serviceapi.delivery.delay = ${queue.default.delivery.delay}

                     

                    Yes these property need to uncomment. For more information have a look at documentation.

                     

                    ## Communication mode: QUEUE ##

                     

                    infa.bpm.trigger.queue.ids                = bpm

                    infa.bpm.consumer.serviceapi.queue.ids    = serviceapi

                    infa.bpm.taskRefreshInterval              = 10

                     

                    Thank you

                    Sai Prasad

                    • 7. Re: P360_JMS_Demo_DataQuality BPM workflow
                      Lokesh Kumar Guru

                      Hi Kiran,

                       

                      Make sure the user has Action Right "Queue Communication" . This is new right from v10.0 so that P360 server can authenticate/read messages from Message Queue using this user.

                       

                      - Lokesh Kumar

                      1 of 1 people found this helpful
                      • 8. Re: P360_JMS_Demo_DataQuality BPM workflow
                        Kiran Ruhil Guru

                        Thank you Lokesh for the hint. This new right was missing for rest user.

                         

                        Regards,

                        Kiran