ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins.Read more for important details.
Absent Member.
Absent Member.
5176 views

Removing old SOAP nitifications ?

Hi,
does anybody know a method of removing old SOAP Notification List entries ?
I mean with GWcheck or alike.

This is how you can check your own:
http://10.0.47.6:7181/notifyList

BTW: Removing them with Event Configuration List doesn't work, it removes them in the Event list but they stay on the notify list.

This is a issue with old mobile and Blackberry servers as well.
Labels (1)
0 Likes
22 Replies
Absent Member.
Absent Member.

see tid 7005743... not sure if this helps.
0 Likes
Absent Member.
Absent Member.

This will only remove the events, which can be done thru the webinterface as well (starting with 802).
0 Likes
Absent Member.
Absent Member.

mconradt wrote:

> This will only remove the events, which can be done thru the webinterface as
> well (starting with 802).


I have a POA for a site that doesn't really use SOAP (no Mobility server) that
was trying SOAP with BES and it failed horribly, so we reverted them back to
OAPI. I COULD NOT get the events to clear out, and eventually had to turn SOAP
off on the POA just to clean things up. Ultimately the SOAP list was trying to
contact a BES that got replaced about a month ago, and so there were constantly
errors on the POA that the event notifications were failing. While one would
think that maybe it was benign, we were starting to see really odd issues with
BES users who were also in caching mode, getting errors for events almost every
time they touched a message, so it just made sense to totally turn SOAP off for
that POA. I'm hoping when they need to turn it back on, things will have
quieted down 🙂

--
Danita Zanrè
Novell Knowledge Partner
Get up and running with Novell Mobility!
http://www.caledonia.net/gw-mobility.html
0 Likes
Absent Member.
Absent Member.

mconradt wrote:

>
> This will only remove the events, which can be done thru the
> webinterface as well (starting with 802).


Yes, but that should do the trick... at least through the web interface
as long as you also check "delete event configuration."

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Absent Member.
Absent Member.

"Joseph Marton" <jmarton@no-mx.forums.novell.com> wrote:
> mconradt wrote:
>
>>
>> This will only remove the events, which can be done thru the
>> webinterface as well (starting with 802).

>
> Yes, but that should do the trick... at least through the web
> interface
> as long as you also check "delete event configuration."



This did Not remove the notification but only the events.
What exactly is the notification list ?
Looks like a list of seen applications which did register to the po.
Or is it a list the poa tries to notify when there's a new event for the
registered user.
Because I would really need to remove my old mobile server...
0 Likes
Absent Member.
Absent Member.

<mc@inetra.de> wrote:

> This did Not remove the notification but only the events.
> What exactly is the notification list ?
> Looks like a list of seen applications which did register to the po.
> Or is it a list the poa tries to notify when there's a new event for
> the registered user.
> Because I would really need to remove my old mobile server...


Well, here's what I've seen. Let's say you have 10 users who were on
GMS, they are now on Mobility. When you look at the event
configuration list you'll see 20 items, 10 showing the old IP & port
for GMS, the other 10 showing the new IP & port for Mobility. If you
go into each user's GMS entry one-by-one and check both "delete events"
and "delete event configuration" this should get rid of each user's old
configuration. Once you've done this for the 10 GMS entries you
shouldn't get any more "event notification errors" on the POA.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Absent Member.
Absent Member.

Joseph Marton wrote:

> Once you've done this for the 10 GMS entries you shouldn't get any more "event
> notification errors" on the POA.


In my experience Once was not enough 🙂 I think I finally did get rid of it
all at a site I was working on, but I would delete both the events and
configuration, the user would disappear from the list, and a few minutes later
would pop back up with a new notification. It was arduous to keep at it long
enough for them to really go away.

--
Danita Zanrè
Novell Knowledge Partner
Get up and running with Novell Mobility!
http://www.caledonia.net/gw-mobility.html
0 Likes
Absent Member.
Absent Member.

DZanre wrote:

> In my experience Once was not enough 🙂 I think I finally did get
> rid of it all at a site I was working on, but I would delete both the
> events and configuration, the user would disappear from the list, and
> a few minutes later would pop back up with a new notification. It
> was arduous to keep at it long enough for them to really go away.


Wonder in that situation if deleting the trusted app out of GW for the
old server, assuming it was no longer in use, would keep them from
popping back up?

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Absent Member.
Absent Member.

DZanre wrote:
> Joseph Marton wrote:
>
>> Once you've done this for the 10 GMS entries you shouldn't get any more "event
>> notification errors" on the POA.

>
> In my experience Once was not enough 🙂 I think I finally did get rid of it
> all at a site I was working on, but I would delete both the events and
> configuration, the user would disappear from the list, and a few minutes later
> would pop back up with a new notification. It was arduous to keep at it long
> enough for them to really go away.


We are hitting this issue now when moving users from GMS to GWMobility..
Really need to manually remove this for over 200 users? what a nice
design ;D

-sk

HAMK University - OES, NW, GW, NCS, eDir, Zen, IDM, NSL - www.hamk.fi
0 Likes
Absent Member.
Absent Member.

Sami Kapanen wrote:

> We are hitting this issue now when moving users from GMS to
> GWMobility.. Really need to manually remove this for over 200 users?
> what a nice design ;D


You shouldn't normally have to manually do it for everyone. This is
usually more for when an old server is just shutdown as the POA doesn't
know about it. If you actually delete the users from GMS as you move
them to Mobility, the deletion in GMS should remove the event
configuration for that user from the POA.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Cadet 3rd Class
Cadet 3rd Class

jmarton;2037847 wrote:
Sami Kapanen wrote:

> We are hitting this issue now when moving users from GMS to
> GWMobility.. Really need to manually remove this for over 200 users?
> what a nice design ;D


You shouldn't normally have to manually do it for everyone. This is
usually more for when an old server is just shutdown as the POA doesn't
know about it. If you actually delete the users from GMS as you move
them to Mobility, the deletion in GMS should remove the event
configuration for that user from the POA.

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms


I deleted GMS users several days ago but the entries for these users are still in the list at the POA.
We also deleted users from our Mobility test server and activated them at our live server, now these users have 3 SOAP entries (GMS, Mobility test and Mobility live)...

-Mikael
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.