cancel
Showing results for 
Search instead for 
Did you mean: 

Is there any discrepancies while using work order and notification push with the same Port???

Former Member
0 Kudos

Hi Team,

       

        We are currently enabling the two pushes in our application .Is there any discrepancies related to the Port Since both Notification and Work Order push is mapped to the same Port..

We have done all the changes in the both Agentry and also in the config panel..But it unable to push the value to the device

Give us a suggestion over here...

Please find the screenshot below represent the error occurs in the log file...

Regards,

Vignesh Anandhan

Accepted Solutions (0)

Answers (1)

Answers (1)

mark_pe
Active Contributor
0 Kudos

Vignesh,

In theory no discrepancy in SMP 3.0+ for both Workorder and Notification.  You also need to make sure you are not using an older version of SMP 3.0 or SMP 2.3. There were reports before on very old SMP 3.0 version SP06 or earlier about infinite definition load looping so hopefully you are in newer versions.

It seems like the picture you shown is in the middle of an update or upload or new deployment of a development definition. Normally when you do a publish from the cockpit, there will need to be some time wherein it needs to load the definition. It seems the picture is at this point. 

Did you somehow just publish a new application or forgot to do the Settings -> Agentry App Restart?  Another thing that could happen is that the prior shutdown was not successfully completed.  Sometimes when you shut down the system (SMP), it may not completely shut down and this could also be a cause perhaps? Need to make sure that your dev. load loop is not causing the port issue as well.

Regards,

SAP Mobile Support Team