Tuesday March 04, 2008
Tuesday March 04, 2008 After months of spotty blogging, two posts in one day. You lucky monkeys!
Follow up on Burton Group report of HP stalling their investment in IdM - HP's Identity Retrenchment
So you don't have to buy the whole report, but you should still.
Anyway, as mentioned before, this blog is called Identity Crisis. This is an example of why I call it that.
Today's winners are the HP customers who now have to live with the idea the software they invested in will not be "end-of-lifed" but no new sales or products will be added to the mix. Only investments will be to keep the current customer base happy. Yep, we all know how that goes.
If their IdM products were senior managers, this is the equivalent to being replaced and put on a "special project" (usually followed by a resignation to spend more time with the family).
Ouch.
Doubt you loyal HP customers will sleep well these next few nights. We actually do feel for you and hope to help.
While not trying to appear to be an ambulance chaser, would like to extend an invitation to those sleepy HP customers to look into our complete Identity Management stack. We have partners and professional services to help get you to a safer place.
Follow up on Burton Group report of HP stalling their investment in IdM - HP's Identity Retrenchment
So you don't have to buy the whole report, but you should still.
Anyway, as mentioned before, this blog is called Identity Crisis. This is an example of why I call it that.
Today's winners are the HP customers who now have to live with the idea the software they invested in will not be "end-of-lifed" but no new sales or products will be added to the mix. Only investments will be to keep the current customer base happy. Yep, we all know how that goes.
If their IdM products were senior managers, this is the equivalent to being replaced and put on a "special project" (usually followed by a resignation to spend more time with the family).
Ouch.
Doubt you loyal HP customers will sleep well these next few nights. We actually do feel for you and hope to help.
While not trying to appear to be an ambulance chaser, would like to extend an invitation to those sleepy HP customers to look into our complete Identity Management stack. We have partners and professional services to help get you to a safer place.
HP is Withdrawing from Identity Management
Seems the word is quietly leaking out. From the analysts and European bloggers.
HP has cut the oxygen off from their Identity Management Team. And, ergo, those loyal customers who bought into their half hearted Identity effort. I am a veteran of HP's investment in BroadVision at the turn of the century, so I know their pain.
This has also been confirmed with the Burton Group Analysts in their recent report:  "Provisioning Market 2008: Survival of the Fittest". Guess HP was not one.  I would reprint the snippet here, but its their IP and you should go read the whole thing. Excellent work. You will need Client access to get the report.
There is also mention on the Völcker Infomatik website:
HP surprisingly withdraws from Identity Management
HP withdraws from Identity Management business. For analysts this step is surprising because this segment is considered as profitable and promising. "With HP's withdrawal from this segment gives a clear signal" sais Peter Weierich, spokesman at Völcker Informatik.
At the HP Identity website, they are still pitching their capabilities for Identity. Does it bother anyone that a company would choke off its identity software, but keep pitching it in public on their website?  SO, for anyone considering an HP Identity solution, hope your company kept up its Burton subscription running.
So, to all of you HP customers, you now know why I call this blog "Identity Crisis". It war out here and the next wave is just beginning. Give us a call. We can help (see above Burton report as well).
Technorati Tags: HP Sun IdM Provisioning
HP has cut the oxygen off from their Identity Management Team. And, ergo, those loyal customers who bought into their half hearted Identity effort. I am a veteran of HP's investment in BroadVision at the turn of the century, so I know their pain.
This has also been confirmed with the Burton Group Analysts in their recent report:  "Provisioning Market 2008: Survival of the Fittest". Guess HP was not one.  I would reprint the snippet here, but its their IP and you should go read the whole thing. Excellent work. You will need Client access to get the report.
There is also mention on the Völcker Infomatik website:
HP surprisingly withdraws from Identity Management
HP withdraws from Identity Management business. For analysts this step is surprising because this segment is considered as profitable and promising. "With HP's withdrawal from this segment gives a clear signal" sais Peter Weierich, spokesman at Völcker Informatik.
At the HP Identity website, they are still pitching their capabilities for Identity. Does it bother anyone that a company would choke off its identity software, but keep pitching it in public on their website?  SO, for anyone considering an HP Identity solution, hope your company kept up its Burton subscription running.
So, to all of you HP customers, you now know why I call this blog "Identity Crisis". It war out here and the next wave is just beginning. Give us a call. We can help (see above Burton report as well).
Technorati Tags: HP Sun IdM Provisioning
Monday March 03, 2008 
So, welcome to the MySQL team; there is a tidal wave of blogs and stories, so won't go into 4-part harmony analysis what it means (its a good thing, just as everyone says). But I did want to add about what it means for Sun Identity manager and the use of MySQL as the repository. Sun IdM 7.X has supported MySQL as a repository for development environments only. Now that we own MySQL, how will that change?
Well, the short answer is, in the near term, no change in position. The problem occurs when scaling MySQL to large scale deployments. Over 8 CPUs, MySQL has thread contention problems and the scaling drops off. As IdM uses a blobby, object oriented type database, with quite a bit of system information kept in XML snippets, our developers were noticing some problems when they tried to stress the database. And at the time (close to a year ago), Sun did not have a formal support agreement with MySQL, so they would not give it the thumbs up to put in production. Development would be supported by Sun, but production support would be withheld until we could be sure we could get solid support from the MySQL team to possibly address customer problems.
Well, that was then and this is now. We bought MySQL just so we could help them solve this type of support problem that has been keeping many large customers from large scale deployments in production. Now, we will own the support problems(lucky us ;-) ).
So I am confident we will solve this problem and certify MySQL across the board for IdM. But the ink is still drying on the acquisition agreement. Give us some time to weld the technical and support teams together. Until then, even though MySQL is now a Sun product, we will leave things the way they are (development support only) until we get things up and supported.