Bannikov

Internal Notifications points

Discussion created by Bannikov on Jun 2, 2010
Latest reply on Jul 19, 2010 by aabrodsky

Hello!

 

We just tried to deploy Notifications for one customer with very small PI Server and have surprised. After our Notifications was on his way, we noticed that 7 new points are added to PI Point Table, with such names:

 

4a1ce2b6-e53d-44fb-9081-9f1fc3b7496d_Action
4a1ce2b6-e53d-44fb-9081-9f1fc3b7496d_Comment
4a1ce2b6-e53d-44fb-9081-9f1fc3b7496d_ContactID
4a1ce2b6-e53d-44fb-9081-9f1fc3b7496d_InstanceID
4a1ce2b6-e53d-44fb-9081-9f1fc3b7496d_Priority
4a1ce2b6-e53d-44fb-9081-9f1fc3b7496d_State
4a1ce2b6-e53d-44fb-9081-9f1fc3b7496d_TimeOffset

 

All these points have point source 'PINotifications-InternalUse'. I understand that these points are for some internal processing, but we have deleted our first notification, and these points are remaining in point table.

 

Maybe somebody can advise me, how can I trace to which notification object are these points connected (maybe GUID part of tag name can be used?)

 

Second question: I haven't found any trace about these points in manuals, but the presence of these points significantly affect our work - we can't add as many notifications as we want - our PI Server size doesn't allow this, and we haven't count it before because I don't know of this. It's the same thing as with MDB -- for particular solution (like IT Organizer) many modules are created, and thye number of available points decreased significantly...

 

 

 

 

Outcomes