Monday Jan 25, 2010

DSEE 7 Gives Engineers More Free Time: What do they do with it?

Importing an ldif file is a common task that every engineer needs to create a directory service.  This is also a task that some engineers need to perform when restoring an instance in their topology.  DSEE 7 has introduced new innovations into the code has resulted in 5x improvements in performance. 

Wajih Ahmed, this Wednesday, will detail how he used the new F-20's to improve import times using DSEE 7.  This improvement results in real measurable time/cost savings.  Since these tasks sometimes take place over weekends or during maintenance periods this means engineers will have more time to do other things.  We want to know what are they doing with that time?  

Here is a potential list of activities they might be doing with that extra time:
  1. Spending time with their families
  2. Downloading and creating a POC for OpenSSO
  3. Attending a soccer game for their daughter
  4. Setting up their Super Bowl pool favoring their favorite team
  5. Finding cheats to get promoted in HALO ODST.
  6. Arranging a family movie night
  7. Learn about Fine Grained Access Control with OpenSSO here
  8. Writing a blog post on why they should allow dedicated server versions of Modern Warfare 2
  9. Checking out the IT platform that will manage, capture and deliver the Vancouver Winter Olympics
  10. Perusing Facebook to find out what is going on with their friends today.

If you have other creative ideas on what engineers should be doing with this extra time that DSEE 7 has given back, please share below.  I think everyone should be getting ready for the Olympics so I have included the latest video on the Torch Relay from the Vacouver Winter Olympics site.

Friday Jan 22, 2010

OpenDS and DSEE 7 Offer Compression

This week we have been sharing the different ways customer's can use compression to improve performance and reduce cost within your Directory Server Enterprise Edition environment.  On Wednesday, Brad Diggs, shared how customer's can use compression to reduce their storage footprint by 60%. Today, Ludo Poitou, Community Manager for OpenDS, wrote a great blog post on how to use compression in your OpenDS 2.2 instance.  Ludo shows how OpenDS can reduce the overall size of your directory instance.  He also gives pointers to how to configure in your directory environment.

Next week, Wajih Ahmed will be talking about how customer's can "Improving Import Speed Through ZFS Caching of LDIF import file".  He will show import rate of ds7 and opends with and without primary and secondary cache disabled vs. enabled.  This is another great example of the proven performance that Sun on Sun provides.  

Wednesday Dec 16, 2009

Sun OpenDS Standard Edition 2.2 Released

Sun OpenDS TM Standard Edition (SE) 2.2 is an updated version of newest member of the Sun Directory Server family of products. It includes an LDAP core that is designed for easy installation, embedding, and configuration as well as a new Directory Proxy Server for load-balancing, high availability and data distribution.

Sun OpenDS SE 2.2 is a high-performance, highly-extensible, pure Java directory server that delivers a fully compliant LDAPv3 server that passes all of the compliance, interoperability and security tests suites. Furthermore, Sun OpenDS SE 2.2 implements most of the standard and experimental LDAP extensions defined in the IETF as RFCs or Internet-Drafts, ensuring maximum interoperability with LDAP client applications.

With a limited footprint allowing the server to be embedded in other Java applications, OpenDS has a very rich set of APIs making it easy to extend and increase usage scope.

Sun OpenDS SE 2.2 also supports a multi-master replication model with optional assured replication that guarantees the high availability of the data for all operations, searches or updates. While theoretically unlimited with regards to the number of masters, the Sun OpenDS SE 2.2 server has been stressed under heavy and durable load with 8 Masters.

This 2.2 version significantly increases performance both in read and write, making it one of the most efficient commercial directory servers available.

Sun OpenDS SE 2.2 is based on the open source community project OpenDS that is constructing next generation directory service software. The initial effort is led by Sun and the primary contributions are by Sun employees, but the goal is to attract developers and other interested parties from around the world. Sun OpenDS SE is the Sun commercial offering based on this project.  

You can find out more information about Sun OpenDS SE 2.2 commercial release at:

http://wikis.sun.com/display/sunopends

Wednesday Sep 02, 2009

LDAPCon2009

Our very own, Ludo Poitou will be presenting with other luminaries in the identity industry at The 2nd.International conference on LDAP, LDAPCon 2009 will be held on September 20th and 21st at Waterfront Marriot Hotel , Portland OR, USA.

LDAP is gaining renewed attention as the identity repository for enterprise, telco's, global partner networks, healthcare and education institutions.  The LDAP repositories have been faced with massive growth over the last five years and the performance and availability they have come to rely upon is being tested. New requirements driven by the growth of users, the explosion of security requirements imposing more "writes" and the access to web services security and policies are forcing LDAP experts to look at new innovations.

You should attend, if you want to be apart of hearing how LDAP experts are innovating and addressing these business and technical challenges.  If you haven't registered yet, please register NOW here!

The registration fee includes access to the LinuxCon 2009 (Sep 21 - 23), and if you still need to be convinced that it's worth attending, you can check the agenda here.

Thursday Mar 05, 2009

Are you a Directory Hero?

Are you a Directory Hero?  We want to know. 

In the last three months we have heard from several of you via the IRC chat on OpenDS.org at identity conferences or at user groups around the world about the great projects that leverage the innovations from the OpenDS community.  We have been able to share a few of the great stories via the blogs story site.  Everyone learns from hearing about the ways in which you are using LDAP in your organization.  It is this sharing in the open that makes being a part of an Open Source Software project exciting and a great learning experience. I am reminded of a truism "Share comes before success".

Therefore, we are annoncing a new opportunity for you to share your stories with us at Sun.  If you have deployed OpenDS and are using it please send us a story at the following email address.  Here are some suggested questions that you can answer.  Alternatively, blog or create a video about your implementation and send us the link.  We want to show our appreciation for sharing so for the top 30 stories we receive we will send you a free t-shirt.  Please include an address in your submission. 

Here is what to do:

  1. Step 1:  Download the questionaire.
  2. Step 2:  Answer the questions that apply to your deployment
  3. Step 3:  Create blog or videocast and post somewhere
  4. Step 4:  Share:  Send us the link at the email address above and include questionaire, link to your blog or video and an address for us to send the t-shirt.

Here is the suggested questionaire to guide you through what information the community would like to hear about your implementation.

Questions (Download here) and you don't have to answer them all:

  1. Can you tell us more about your company ?
  2. Can you tell us about the application, site, or service in which you have adopted OpenDS?   [ Note: this is where you can hopefully get some publicity for your  own business or project.  So consider including any hyperlinks,  screenshots, etc. that you would like for us to use in that context.  Also, are you embedding OpenDS in your application?]
  3. How and when did you first find out about OpenDS?
  4. Did you go through an evaluation process before selecting OpenDS? If so, can you tell us a little bit about the process and results?
  5. What specific version of OpenDS are you using?
  6. On what operating system do you run OpenDS? Do you use the same OS for both development and production deployment?
  7. On what hardware platform do you run OpenDS? Do you use the same platform for both development and production deployment?
  8. Have you purchased a OpenDS license? If not, have you thought about doing so and do you know it includes access to patches and sustaining releases (more details from http://wikis.sun.com/display/sunopends)?
  9. What specific features of OpenDS are you using?
  10. What do you like most about OpenDS?
  11. What would you most like to see improved in OpenDS?
  12. Does your application also use a database? If so, which one?
  13. Are there any figures about the scale of your adoption which you would like to share (such as how much traffic is being handled, how many entries are stored in OpenDS, how many servers are used)?
  14. How has OpenDS performed since your application/service went live? Have you run into any production issues which you would attribute to OpenDS?
  15. Would you recommend OpenDS to others? Why?
  16. How does OpenDS figure in your future plans?
  17. How would your describe your participation in the OpenDS project (e.g. user only, submitter of bug reports and RFEs, developer who has contributed code)?
  18. Is there anything else you think would be of interest in a story about your OpenDS adoption?



Wednesday Feb 25, 2009

Directory Server 6.3.1 Released: Download Today

Sun  Directory Server Enterprise Edition 6.3.1 released.

The 6.3.1 release is a patch to existing 6.x deployment that provides customers with a way to apply the latest fixes and updates found in Directory Server, Directory Proxy Server and Directory Server Control Center components in one installation event. 

Specifically,  the Directory Server 6.3.1 provides fixes to replication issues in mixed DS 5.2 and 6.x topologies, on Directory Proxy Server it improves support for Virtualization (Join and JDBC) and includes additional performance related improvements.  Furthermore this patch release improves overall quality and robustness of deployments.  You can read a consolidated view of all the fixes and updates contained in the release in the Release Notes located here.

It is available in the following forms:
  • Native patch - patches to upgrade Directory Server Enterprise Edition 6.0, 6.1, 6.2 and 6.3 native packages installed using the Java ES installer
  • Zip compressed archive distribution - patches to Directory Server Enterprise Edition 6.0, 6.1, 6.2 and 6.3 zip installations

Directory Server Enterprise Edition 6.3.1 patches are available through SunSolve Patchzip :

  • 126748-05: Sun Java(TM) System Directory Server Enterprise Edition 6.3.1 : SunOS 5.9/5.10 Sparc patchzip
  • 126749-05: Sun Java(TM) System Directory Server Enterprise Edition 6.3.1 : SunOS 5.9_x86 patchzip
  • 126750-05: Sun Java(TM) System Directory Server Enterprise Edition 6.3.1 : SunOS 5.10_x86, x64 patchzip
  • 126751-05: Sun Java(TM) System Directory Server Enterprise Edition 6.3.1 : Linux RHEL3 RHEL4 patchzip
  • 126752-05: Sun Java(TM) System Directory Server Enterprise Edition 6.3.1 : HP-UX 11iv2 PA Risc patchzip
  • 126753-05: Sun Java(TM) System Directory Server Enterprise Edition 6.3.1 : Windows 2000/2003 Server patchzip

Native Package :

  • 125276-08: Directory Server Enterprise Edition 6.3.1 : SunOS 5.9/5.10 Sparc Native Patch
  • 125277-08: Directory Server Enterprise Edition 6.3.1 : SunOS 5.9_x86 Native Patch
  • 125278-08: Directory Server Enterprise Edition 6.3.1 : SunOS 5.10_x86, x64 Native Patch
  • 125309-08: Directory Server Enterprise Edition 6.3.1 : Linux RHEL3 RHEL4 Native Patch
  • 125311-08: Directory Server Enterprise Edition 6.3.1 Windows MSI Native Patch

For the detailed information on what you need to install based on your current installation, refer to the Sun Java System Directory Server Enterprise Edition 6.3.1 Release Notes.

Directory Server Enterprise Edition
Marketing Team


Tuesday Jul 29, 2008

Sun OpenDS Standard Edition 1.0 Released

Sun OpenDS TM Standard Edition (SE) 1.0 is the newest member of the Sun Directory Server family of products. This directory server includes an LDAP core that is designed for easy installation, embedding, and configuration. 

Sun OpenDS SE 1.0 is a high-performance, highly-extensible, pure Java directory server that delivers a fully compliant LDAPv3 server that passes all of the compliance, interoperability and security tests suites. Furthermore, Sun OpenDS SE 1.0 implements most of the standard and experimental LDAP extensions defined in the IETF as RFCs or Internet-Drafts, ensuring maximum interoperability with LDAP client applications.

With a limited footprint allowing the server to be embedded in other Java applications, Sun OpenDS SE 1.0 has a very rich set of APIs making it easy to extend and increase usage scope.

Sun OpenDS SE 1.0 also supports a multi-master replication model that guarantees the high availability of the data for all operations, searches or updates. While theoretically unlimited with regards to the number of masters, the Sun OpenDS SE 1.0 server has been stressed under heavy and durable load with 4 Masters.

Sun OpenDS SE 1.0 is based on the open source community project OpenDS that is constructing next generation directory service software. The initial effort is led by Sun and the primary contributions are by Sun employees, but the goal is to attract developers and other interested parties from around the world. Sun OpenDS SE is the Sun commercial offering based on this project.  

You can find out more information about Sun OpenDS SE 1.0 commercial release at:

http://wikis.sun.com/display/sunopends

 

Sunday Apr 20, 2008

DSEE 6.3 Released

We have just released the latest update in the Directory Server Enterprise Edition 6.x product line.  

This patch release brings:

  • Improved performance for some specific deployments. For example, deletion of a suborganization is now faster.

  • Support for the SuSE 10 operating system. See Operating System Requirements for details.

  • Support for HP-UX 11.23 (PA-RISC). See Operating System Requirements for details.

  • Increased flexibility and security for deployments, with the Directory Service Control Center registry allowing port change and listening on addresses defined by an IP address.

  • Reduced disk space used, by purging replication metadata using a new purge-csn option in the dsadm command.

  • Improved interoperability with other products through the Directory Proxy Server, with improved LDAP control support.

  • The Directory Proxy Server allows bind operations to multiple data sources including Active Directory and to Sun Java System Directory Server. Bad password attempts now block users from multiple data sources, increasing security.

  • Install the ZIP distribution as any user on Windows.

You can download Sun Java System Directory Server Enterprise Edition 6.3 software from the following location.

http://www.sun.com/software/products/directory_srvr_ee/get.jsp

The download page serves as a starting point to direct you to the proper downloads depending on the distribution type you need to download.

Directory Server Enterprise Edition 6.3 is available in the following full distributions.

  • ZIP Full distribution (Solaris, Red Hat, SuSE, HP-UX, Windows) - standalone delivery to install Directory Server Enterprise Edition 6.3 or upgrade Directory Server Enterprise Edition 6.0 and 6.1 and 6.2 ZIP installations.

Identity Synchronization for Windows is not delivered in the Directory Server Enterprise Edition native package distribution and is only available in the ZIP distribution.

Directory Server Enterprise Edition 6.3 is available in the following patch distributions.

  • Native patch – patches to upgrade Directory Server Enterprise Edition 6.0, 6.1 and 6.2 native packages installed using the Java ES installer.

  • ZIP patch distribution – standalone delivery to install Directory Server Enterprise Edition 6.3 or upgrade Directory Server Enterprise Edition 6.0 and 6.1 and 6.2 ZIP installations.

    If you are not familiar with the difference between the Native installation and ZIP installation please read the following information in the documentation before upgrading or installing DSEE 6.3:  Directory Server Enterprise Edition Software Distributions


Note –
  1. The patch release for native installations of Directory Server Enterprise Edition 6.3 on the Microsoft Windows platform is not available at the same time as the patch releases on other platforms. The patch release for native installations of Directory Server Enterprise Edition 6.3 on the Microsoft Windows platform will be available at a later time and we will update this blog when we have a known date for this.

    Zip distribution is currently available for on the Microsoft Windows platform.

  2. The localization patch files for the native installations have not been released yet on SunSolve but should be available within a week. The ZIP downloads contain all the localization files so there are no extra downloads required for ZIP installations.  We will update this blog once they are available on native installations.

For information on patch numbers, see Software Installation in Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

For the detailed information on what you need to install based on your current installation, refer to the Installation Procedure Quick Reference in Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

Directory Server Enterprise Edition
Marketing Team


Wednesday Apr 16, 2008

DSEE 6.2 Sun Alert - Database integrity issues

http://sunsolve.sun.com/search/document.do?assetkey=1-66-235361-1

Please see the above link for the official Sun Alert document.  The below information is provided for quick reference only.  

For additional details please also see previous blog entry on this topic: http://blogs.sun.com/dsee/entry/directory_server_6_2_database


Document Audience: PUBLIC
Document ID: 235361
Title: Sun Java System Directory Server 6.2 Database integrity may be compromised
Copyright Notice: Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved
Update Date: Mon Apr 14 00:00:00 MDT 2008

Solution Type Sun Alert
Solution  235361 :   Sun Java System Directory Server 6.2 Database integrity may be compromised

Bug ID: 6642430
Product: Sun Java System Directory Server 6.2, Enterprise Edition
Date of Resolved Release: 14-Apr-2008
SA Document Body: Sun Java System Directory Server 6.2 Database integrity may be compromised

1. Impact

A race condition may cause database pages for Sun Java System Directory Server to not sync to disk, resulting in possible Directory Server Database integrity issues. Depending on which pages are affected, the impact may vary.

2. Contributing Factors

This issue can occur in the following releases for all platforms (Solaris 8, 9, and 10 SPARC and x86 Platforms, Linux, Windows, HP-UX):
  • Sun Java System Directory Server Enterprise Edition 6.2
Note: Directory Server 6.1, 6.0, 5.2 and 5.1 are not affected by this issue.


To determine if the Directory Server running on a system is affected, the following command can be used:

$ dsadm -V

If the output contains the version string 6.2, the system is affected.

3. Symptoms

Depending on which database page is affected and which operation tries to access it, the resulting error messages can be different, but in the most frequent cases a message similar to the following is logged:

DEBUG - conn=-1 op=-1 msgId=-1 -  libdb: PANIC: fatal region error detected; run recovery

4. Workaround

There is no workaround for this issue. Please see the Resolution section below.

5. Resolution

This issue is addressed in the following releases: (please see blog entry http://blogs.sun.com/dsee/entry/dsee_6_3_released for more details)

DSEE 6.3 Native Package Versions:
  • Solaris 9 and 10 with SPARC patch 125276-07 or later
  • Solaris 9 x86 with patch 125277-07 or later
  • Solaris 10 x86 and x64 with patch 125278-07 or later
  • Linux with patch 125309-07 or later
  • Windows with patch 125311-07 or later
DSEE 6.3 PatchZIP (Compressed Archive) versions:
  • Solaris 9 and 10 with SPARC patch 126748-04 or later
  • Solaris 9 x86 with patch 126749-04 or later
  • Solaris 10 x86 and x64 with patch 126750-04 or later
  • Linux with patch 126751-04 or later
  • Windows with patch 126753-04 or later
  • HP-UX with patch 126752-04 or later
Note: After patches have been applied: Since the database integrity issue can be present but undetected, it is recommended to rebuild the database by exporting to an ldif file and reimporting the ldif file. In a replicated environment, all servers need to be rebuilt or reinitialized. Export/Import and initializing servers in a replicated environment is documented in the DSEE reference guide at:


This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.


Tuesday Apr 15, 2008

DSCC High Availability

DSCC is the Directory Services Control Center (web console) that is used for configuring and managing the Directory and Directory Proxy servers in your deployment.  We have seen a number of questions from customers around how they can deploy multiple DSCC instances and create a HA environment across all of these DSCC instances.  The simple answer is that yes this can be done and it is supported in the product today.   See the documentation links below for more details on how this can be achieved.

Configuring Failover for DSCC

These additional documentation links can provide more background information into how the new DSCC web console works and uses a directory instance to store its information.  

DSEE Administration Framework

Architectural Changes in Directory Server

There are also some additional configuration changes you can make to the DSCC installation which are documented at the following location: Configuring DSCC


Directory Server 6.2 - Possible Database Integrity Issues

We have become aware of a bug in Directory Server 6.2 only that could cause database integrity issues.   We have a hotfix for this issue, and if you are running Directory Server 6.2 and run into this problem then you should contact Sun Support and ask for the fix for the following bug

6642430: DB corruption (zero’d pages) when performing db2ldif against large 20GB ldif file.

The sunsolve record for this bug can be found at http://sunsolve.sun.com/search/document.do?assetkey=1-1-6642430-1.

NOTE: This issue does not affect Directory Server 6.0 or 6.1 release so you only need this fix if you are running Directory Server 6.2.

After you have the hotfix for this issue on Directory Server 6.2 and have applied the hotfix, then you will have to re-initialize the database from an LDIF backup to fully correct the corruption issue. Simply applying the hotfix will not fix the database if the database is already corrupted. Database corruption can be present though not detected with data in binary formats. You must therefore rebuild the database by importing an LDIF backup.

Directory Server Enterprise Edition 6.2 is no longer available for download and Directory Server Enterprise Edition 6.3, which includes a fix for this issue, will be available for download early April.  When upgrading to Directory Server 6.3 from 6.2 (not needed if you are on 6.0 or 6.1), make sure you export the database (db2ldif) prior to the upgrade and then re-import the database after the upgrade to fully re-initialize the database and to ensure that no corruption issues remain.

Recommended patch or upgrade procedures:

  1. Shut down each directory server instance, as described in Starting, Stopping, and Restarting a Directory Server Instance.

  2. Perform an LDIF export of the database, as described in Backing Up to LDIF.

  3. Install the hotfix for bug 6642430 on Directory Server 6.2, or upgrade your Directory Server 6.2 instance to Directory Server 6.3 once Directory Server 6.3 is available for download (early April). You will need to login to Sunsolve in order to see this bug description.

  4. Re-initialize the database from the LDIF exported in step 2, as described in Importing Data From an LDIF File.

    If you are running replicated instances of Directory Server, make sure you read Restoring Replicated Suffixes as well.

About

This blog provides information regarding the Oracle Directory Server Enterprise Edition and Oracle Unified Directory products. Use this blog to get the latest breaking information regarding releases and updates plus other technical and non-technical information.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today