CA SiteMinder r12 (formerly Netegrity SiteMinder) is on the horizon, and soon your firm will study the date when your latest SiteMinder version will no longer be supported. The time is now to delivery planning for this present day and your eventual upgrade, so you can proceed receiving assist and take competencies of the numerous merits that SiteMinder r12 brings.Framingham, MA, November 05, 2009 --(PR.com)-- A SiteMinder web access supervisor R12 improves upon the functionality attainable in SiteMinder 6.x in a couple of areas. in addition to exceptional-grained delegation through the new administration person interface, R12 improves listing mapping, adds assist for web functions, bundles federation guide in the past simplest available through the option Pack and introduces best-grained authentication capabilities. whereas these elements warrant improve consideration on their personal, an eventual end-of-lifetime of SiteMinder 6.x will require an improve of your current environment. As you start the manner of upgrading your atmosphere to R12, cautious consideration is required to make certain the migration goes smoothly. New add-ons like an software server are required and even the way policies are kept has changed with the addition of the prolonged policy objects. SiteMinder deployments provide mission critical performance and the upgrade ought to be accomplished with minimal chance or downtime. To ensure a easy improve course, make certain that you spend sufficient time planning for every phase of the flow to SiteMinder R12. Your upgrade approach As you analyze your method for upgrading to SiteMinder R12, you need to agree with here: make certain that you've got particular guidance on each and every part of your SiteMinder environment bear in mind your renovation windows make sure that you have got a superb healing and rollback plan Map out the upgrade order of the accessories analysis When breaking down your present SiteMinder ambiance, take into account here SiteMinder add-ons: There are several issues to consider as you analyze your current ambiance. be sure that you simply minimally have the following particulars: The variety of policy servers and brokers you have got deployed and the models of every element. The audit logs on the policy servers can also be reviewed to catch this assistance. Which policy servers are getting used through every agent. whereas the host config object can provide some particulars here, don’t forget that the SmHost.conf file includes the bootstrap policy server for the agent and that assistance is not saved centrally. you could use the audit logs to support slim this down extra. check if your brokers are working in failover or round-robin modes and which brokers are offering single signal-on for unified applications. cautious overview of the upgrade documentation is required to make sure that single sign-on and correct managing of failover and circular-robin modes are maintained right through the upgrade manner. investigate which authentication schemes are being used and ensure that there are not any required configuration alterations for those authentication schemes. Map out your whole 3rd-celebration and custom components. you are going to need to validate that your third-birthday party add-ons are appropriate with R12. Any customized components would require testing and might need to be recompiled. Spending the time to bring together this information will help you map out an in depth plan. you can combine this with assistance in your preservation home windows and off-top times to lower the upgrade affect and cut back possibility. restoration approach if in case you have the luxurious of standing-up a further environment after which migrating over to your new systems, restoration is comfortably a count of switching returned to the historic ambiance. in a similar way if you are the use of VMWare or equivalent virtualized techniques, this give you the flexibility or taking your current photo, upgrading it after which deploying it while being in a position to roll lower back to the old image if needed. in case you’re like most of us, the most effective approach to do this is inline. before upgrading, make sure to backup. apart from backing up the computing device, make sure you backup the following: policy save using smobjexport Configuration files just like the WebAgent.conf conf, SmHost.conf personalized types and different FCC’s, and so forth. web Server configuration files like Apache’s httpd.conf improve Plan upon getting accomplished the evaluation of the ambiance put together a plan that ensures that each one accessories within the atmosphere will continue to be appropriate. The usual method is to improve the coverage servers first after which the web brokers. This may additionally trade depending on the edition of the brokers deployed. after you have run the installer for R12, that you would be able to’t revert lower back without uninstalling. So, be certain that you’ve mapped out a powerful recuperation method. make certain that you've established the improve in several environments just before rolling this out to creation. Having a smartly documented and established method takes a while to position together, but the reduced chance and put up-upgrade issues is smartly value the investment. For a restrained time, CoreBlox is providing a free consultation on approaches that you would be able to prepare for your SiteMinder r12 upgrade. they are going to seek advice from your web site and meet together with your infrastructure group to benefit an knowing of your ambiance, including user shops, policy shops, LDAP and database directories. Please visit their net site for extra assistance.