GMS API Mode

Question

Can anyone tell me if I can enable API mode for GMS. GMS with SOAP is just plain bad... Are BES never gives us any issues and that is because we run in api mode.
For those folks out there that are thinking of updating to GW801HP1 to fix soap issues, don't bother.
The version of GMS I'm running is 8.0.104.4.

Answer 1

I performed more testing and have decided to install Intellisync back on the workstations and kill GMS.
>>> On 2/10/2010 at 7:48 AM, Kirk White<[email protected]> wrote:
I bumped my threads back up from 5 to 10 to get the PDA's working again. I have figured this out in a week and that is GW801HP1 is worst than GW703HP2.
>>> On 2/9/2010 at 1:02 PM, Michael Rae<[email protected]> wrote:
Don't be too scared of BES 5.0, it's better than you may think when it comes to SOAP and it's a major improvment to 4.1.
Personally I think that the major issue with the POA and SOAP is GMS, I'm using several SOAP applications and the thing that creates most of the problems is GMS.
Since Novell isn't developing anything for GMS, I believe they are trying to work out the SOAP problems at the POA level rather addressing the source of the issue which is GMS, most GW installations only deal with GMS so that's what the majority of admin's see it.
"Kirk White" <[email protected]> wrote in message news:[email protected]...
Michael, thanks for the info.
So do you think Novell will have the SOAP problems fixed in GW 9... This reminds of back in the '90's Novell claimed that they had the fastest Java server in production. To bad they didn't have any programmers that could write Java Code.
I guess I won't be installing BES 5 when it comes out.
Config:
NetWare 6.5.8 Clusters with Protected Memory
Problems:
Sucks all the memory out of my servers.
Worst it brings my servers up to 100% utilization.
I do have maintenance. You're right do I need to create an incident so they can tell me that SOAP will be fixed in HP2, SP2, SP2HP1, SP2HP2, and so on.
If throttling back my threads don't work here are my option may be loading the intellisync back on the workstations.
>>> On 2/8/2010 at 5:57 PM, Michael Rae<[email protected]> wrote:
You are pretty much stuck with SOAP with GMS, yes the trusted app API is there to handle authentication but other than that, that's all they wrote and will right for GMS.
Get your SOAP fired up, in BES 5, it too will be all SOAP with no option for OAPI.
What type of issues are you having, just running out of memory on POA? Are you running the POA on Netware or SLES? I'm running mine on NetWare with a few minor with about 1100 users on a single PO.
How many GMS users do you have? One thing I found after new years day, my GMS wacked out the PO. Novell TAC & I never really figured out the problem however removing all the users from GMS fixed it (and letting them recreate themselves!) My GMS didn't appear to like the old inactive users esp the ones that existed in GMS but no longer were in eDir or GW.
No real earth shattering news on how to run SOAP successfully with GW, the 100% utilization is a known problem. Do you have paid maint? I would open a incident with support but the story you will hear is that it's a known problem and will be fixed in SP2....
Check your POA stats though web monitor, are your Soap threads not going idle? That's the problem I had, Soap thread would increase and REGARDLESS of how or few I allocated, the threads would not go idle and the server util would just keep rising including trying to unload the POA would lock the server up as it tried to release the threads.
Hang in brother, I feel your pain.
"Kirk White" <[email protected]> wrote in message news:[email protected]...
Can anyone tell me if I can enable API mode for GMS. GMS with SOAP is just plain bad... Are BES never gives us any issues and that is because we run in api mode.
For those folks out there that are thinking of updating to GW801HP1 to fix soap issues, don't bother.
The version of GMS I'm running is 8.0.104.4.