Thursday, February 19, 2009

World Wide Developers Conference (Java Tech Days)

Java tech days 2009 is one the events conducted by Sun Microsystems on various emerging technologies from Sun.By God's grace I have been selected as one of the speaker in the conference for the subject "Simplifying IDM Solutions".In 2008 I was a listener in Java Tec days,but this time I made it as a speaker. It was an exiting experience in my life as I got an opportunity to address a crowd of Customers,Partners & Technology Folks around the world. I initially thought whether I have the capability & Courage to handle this? But thanks to god ,he gave me the courage & strength.

I was taken away by the opening cermony especilly the Jazz performace by 11 year old boy.

Above all, I got a chance to meet James Gosling, who is the "Father of Java".

Thursday, January 15, 2009

Gateway considerations while deploying Sun Identity Manager Solutions

Gateway servers are only required if deploying adapters for Windows-based APIs such as MS Active Directory / Exchange, Domino, Novell NDS, etc.

Gateways should be located as close as possible to resources managed through the gateway and should be architected in pairs to support availability.Application servers at remote sites should use whatever primary gateway is close to those resources managed through the gateway and failover to the secondary gateway at that same site. If all gateway-managed resources are located close to one site, or the sites are located close together,a pair of gateways may be removed. Gateways require minimal resources, so gateway services may run on an existing Windows-based server machine with appropriate clients installed.

Cost Mitigation for Identity Manager Implementation

Identity Manager typically requires 5 – 20 GB of schema space, depending on the size of engagement and level of auditing; existing DB infrastructures may be utilized to eliminate the purchase cost and additional maintenance of dedicated server hardware. Note, when fully leveraging compliance reporting, database footprint may vary dramatically based on number of audited resources, numbers of accounts, size of entitlements, and how long audit data is persisted in the database. Ensure that allocated schema has room to grow to upwards of 100 GB.

Pre-existing software / hardware load balancers may be used to provide availability, load balancing, failover, and SSL-acceleration, as determined by expected traffic. Load balancers should be configured for sticky sessions.

Ideally the test environment should exactly mirror the production environment to best facilitate testing, performance tuning, and issue resolution. To reduce costs this environment may be scaled down; however, it is recommended that number of instances remain sufficient for testing load balancing / failover and to reproduce / debug possible contention issues.

Given the high cost of database infrastructure and per-CPU licensing for enterprise applications, most customers allocate space on existing databases for Identity Manager. Note that Identity Manager is may be chatty in certain configurations, so sufficient space must be available for redo logs.

Thursday, January 8, 2009

Calculating Java Heap Size for Identity Manager implementation

How do we determine the Java Heap Size to be set on Sun Application server for a typical Identity Manager deployment?

This is the typical java heap size setting used for most of the projects which I have implemented in Sun Identity Manager on Solaris Platform

Assume that Physical Memory of Solaris = 4GB
Assume the memory used by OS = 256 MB

Java Heap size that should be set should be equivalent to 80% of remaing memory left.

((4096 - 256) * 0.8 = 3072)

The formula is

Java Hep size = (Physical Memory-Memory used by OS)*.8