Skip Navigation Links | |
Exit Print View | |
Sun Java System Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2 Release Notes |
What's New in Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2
Directory Server Hardware Requirements
Directory Proxy Server Hardware Requirements
Software Dependency Requirements
Identity Synchronization for Windows Requirements in a Firewall Environment
Directory Server Plug-in Requirements in a Firewall Environment
Supported Browsers for Directory Service Control Center
Installation Privileges and Credentials
Native Package-Based Distributions
Upgrading Directory Server Enterprise Edition to 6.3.1.1.2 Using Native Packages
To Upgrade Shared Components Using Patches
To Upgrade Directory Server Enterprise Edition Using Native Packages
Upgrading Directory Server Enterprise Edition to 6.3.1.1.2 Using ZIP distribution
To Upgrade Directory Server Enterprise Edition to Bundle Patch 6.3.1.1.2 Using ZIP Distribution
Upgrading Directory Server Enterprise Edition 6.3.1 Native Packages to a 6.3.1.1.2 Zip installation
To Install Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2
3. Directory Server Bugs Fixed and Known Problems
4. Directory Proxy Server Bugs Fixed and Known Problems
5. Identity Synchronization for Windows Bugs Fixed and Known Problems
6. Directory Editor Bugs Fixed and Known Problems
7. Directory Server Resource Kit Bugs Fixed and Known Problems
Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2 delivers bug fixes mainly for Directory Service Control Center, Directory Proxy Server, and Directory Server. Only the upgrade mode is offered within version 6.3.1.1.2 using Native Packages or ZIP distribution.
Upgrade is supported only from Directory Server Enterprise Edition 6.3.1 or 6.3.1.1.1 to Bundle Patch 6.3.1.1.2. If you are using a pre-6.3.1 Directory Server Enterprise Edition version , you must upgrade to Directory Server Enterprise Edition 6.3.1 before you can apply Bundle Patch 6.3.1.1.2.
This section covers the following parts.
Upgrading Directory Server Enterprise Edition to 6.3.1.1.2 Using Native Packages
Upgrading Directory Server Enterprise Edition to 6.3.1.1.2 Using ZIP distribution
Upgrading Directory Server Enterprise Edition 6.3.1 Native Packages to a 6.3.1.1.2 Zip installation
The following table identifies information for you to use to upgrade Directory Server Enterprise Edition to version 6.3.1.1.2 based on your current installation and the type of distribution you are using.
Table 2-1 Upgrade Paths to Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2
|
Note - In general, it is a good practice to back up the directory databases regularly and particularly before upgrading the directory server. See the Sun Java System Directory Server Enterprise Edition 6.3 Administration Guide for information about backing up the database.
You must stop all Directory Server and Directory Proxy Server instances before applying Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2.
All Directory Server and Directory Proxy Server instances, including the DSCC registry, must be stopped before Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2 is applied.
To use the localized console, apply the Directory Server Enterprise Edition 6.3.1 localized patch (if it is not already applied) before the Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2. If you apply the Bundle Patch 6.3.1.1.2 before applying the 6.3.1 localization patch, then run the following commands in the specified order.
# dsccsetup console-unreg # dsccsetup console-reg
For more information, see bug 12207124/6583131 in Known Directory Server Issues in Bundle Patch 6.3.1.1.2.
All Directory Server and Directory Proxy Server instances must be stopped before the Directory Server Enterprise Edition Bundle Patch 6.3.1.1.2 zip distribution is applied on top the 6.3.1 zip installation.
Note that the patchzip is not applied to the Directory Service Control Center until you undeploy and then redeploy the WAR file. This requirement is related to bug 12207124/6583131 in Known Directory Server Issues in Bundle Patch 6.3.1.1.2.
Before You Begin
Before upgrading Directory Server Enterprise Edition to 6.3.1.1.2 using native packages, you must upgrade the shared components. On Solaris systems you must be root to perform this procedure.
Using patches, you can upgrade shared components on Solaris. .
Select the platform as per your requirements and install all the patches specified for that platform. If newer patch revisions become available, use the newer ones instead of those shown in the table. Note that DPS631U1 has been upgraded to 6.3.1.1.2 and validated with the level of shared components listed in this table
|
Choose the right NSS/NSPR/JSS patch for your system by getting the package version of SUNWpr and SUNtls on your system.
# pkginfo -l SUNWpr | grep VERSION # pkginfo -l SUNWtls | grep VERSION
Then choose the right patch series from the table below.
|
# cacaoadm stop # smcswebserver stop
For more information on how to obtain the patches, see Getting the Software.
Read the README.patchID file for detailed patch installation procedures.
Read the README.patchID file for verification procedure.
# cacaoadm start # smcswebserver start
$ cd /var/mps/serverroot/lib $ ln -s /usr/lib/mps/secv1/libnssdbm3.so libnssdbm3.so $ ln -s /usr/lib/mps/secv1/libnssutil3.so libnssutil3.so $ ln -s /usr/lib/mps/secv1/libsqlite3.so libsqlite3.so $ cd /var/mps/serverroot/lib/sparcv9 $ ln -s /usr/lib/mps/secv1/sparcv9/libnssdbm3.so libnssdbm3.so $ ln -s /usr/lib/mps/secv1/sparcv9/libnssutil3.so libnssutil3.so $ ln -s /usr/lib/mps/secv1/sparcv9/libsqlite3.so libsqlite3.so
Before You Begin
Make sure all the shared components are up-to-date. For more information, see To Upgrade Shared Components Using Patches.
If you already have Directory Server Enterprise Edition 6.3.1 or 6.3.1.1 installed, upgrade to version 6.3.1.1.2 using the following procedure.
You must be root to perform these steps.
All the Directory Server instances, Directory Proxy Server instances, and configuration information remain unaffected after you complete the Directory Server Enterprise Edition upgrade.
The following table displays the patch numbers that are required to upgrade Directory Server Enterprise Edition on different platforms. If newer patch revisions become available, use the newer ones instead of those shown in the table.
|
Note - To make the localized Directory Server Enterprise Edition work successfully, install the localized patches before installing the core patches.
Each localization patch contains all the supported languages for the selected platform.
# dsadm stop /var/opt/SUNWdsee/dscc6/dcc/ads
See Getting the Software for more details.
Before upgrading Directory Server Enterprise Edition, you must install 119254-38 on Solaris 10 SPARC and 119255-38 on Solaris 10 x64. See Getting the Software for information on downloading patches.
Alternatively, use -G with the patchadd command on Solaris 10 SPARC and Solaris 10 x64 while applying the Directory Server Enterprise Edition upgrade patch. For example:
# patchadd -G patch-id
For other versions of Solaris, use the following command:
# patchadd patch-id
# dsadm start /var/opt/SUNWdsee/dscc6/dcc/ads
Before You Begin
You can install the zip distribution as a non-root user.
Note - In general, it is a good practice to back up the directory databases regularly, and particularly before upgrading the Directory Server. You cannot restore an earlier Directory Server configuration later. This advice applies to both Zip and Native Packages installations. See the Sun Java System Directory Server Enterprise Edition 6.3 Administration Guide for information about backing up the database.
The dsee_deploy command automatically updates the installation if it finds any previous installation. However, in the case of SuSE Linux 9 and HP-UX, before you upgrade the Directory Server Enterprise Edition installation, you must first upgrade the operating system to SuSE Linux 9 SP4 and HP-UX 11.23 respectively. Then use following procedure to upgrade your Directory Server Enterprise Edition installation to 6.3.1.1.2.
Upgrade SuSE Linux 9 SP3 to SuSE Linux 9 SP4.
On SuSE 64-bit, .pam-32bit-9-yyyymmddhhmm.rpm is a prerequisite for CACAO to start, and you must install it if it is not already present on your system.
Refer to the operating system documentation for information about how to upgrade the operating system, how to preserve the partition where Directory Server Enterprise Edition is installed, and where to get the latest patch bundles.
Refer to the following table for information about the appropriate zip patch for your system. If newer patch revisions become available, use the newer ones instead of those shown in the table.
All the multilingual files are included in the above mentioned patches.
|
$ ./dsee_deploy install -i install-path -p cacao-port options
On Windows installations, browse to the zip distribution folder that contains the dsee_deploy command and run the following command:
dsee_deploy install -i install-path options
For example, the following command upgrades your existing Directory Server Enterprise Edition previously installed at /local directory, assuming that you have write access to the directory.
$ ./dsee_deploy install -i /local
You can also use the --no-inter option to install in non-interactive mode, accepting the license without confirmation. Non-interactive mode is particularly useful for silent installation.
During the installation process, a WAR file is saved on your system. The WAR file contains the DSCC web application which when deployed with the application server enables you to access and manage the server instances through web console. The functionality is similar to DSCC in native packages. For more information about the WAR file, see “Installing Directory Service Control Center From Zip Distribution” in the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.
During the installation process, the multilingual packages are also installed.
For step-by- step information, refer to “Installing Directory Service Control Center From Zip Distribution” in the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.
To upgrade Directory Server Enterprise Edition 6.3.1 Linux or Windows native packages to a 6.3.1.1.2 zip installation, you must complete the following procedures:
Before You Begin
In general, it is a good practice to back up the directory databases regularly, and particularly before upgrading the Directory Server. You cannot restore an earlier Directory Server configuration later. This advice applies to both Zip and Native Packages installations. See the Sun Java System Directory Server Enterprise Edition 6.3 Administration Guide for information about backing up the database.
# cacaoadm-path list-params
# dsadm-path info ads-path
On Linux
# /opt/sun/ds6/bin/dsconf export -p port cn=dscc /tmp/dscc.ldif
On Windows
# "C:\Program Files\Sun\JavaES5\DSEE\ds6\bin\dsconf.exe" export -p port -e cn=dscc c:\temp\dscc.ldif
Stop all running Directory Servers (including DSCC registry).
# dsadm-path stop instance-path # dsadm-path stop ads-path
Stop all running Directory Proxy Servers.
# dpadm-path stop instance-path
For any Directory Server instance registered to start at boot, type the following command:
# /opt/sun/ds6/bin/dsadm autostart --off instance-path
For any Directory Proxy Server instance registered to start at boot, type the following command:
# /opt/sun/dps6/bin/dpadm autostart --off instance-path
For any Directory Server instance registered to start at boot, type the following command:
# "C:\Program Files\Sun\JavaES5\DSEE\ds6\bin\dsadm.exe" disable-service --type WIN_SERVICE instance-path
For any Directory Proxy Server instance registered to start at boot, type the following command:
# "C:\Program Files\Sun\JavaES5\DSEE\dps6\bin\dpadm.exe" disable-service --type WIN_SERVICE instance-path
# dsccsetup-path cacao-unreg
# cacaoadm-path stop
# dsccsetup-path console-unreg
Run the following command:
# dsee_deploy install -i install-path options
This command works properly only if a Common Agent Container is not yet running on the default port, 11162. If you don't stop your previous Common Agent Container (step 7 of previous section), specify a different port using the -p option.
# dsee_deploy install -i install-path -p port options
This command installs a Common Agent Container with the local Directory Service Control Center agent as well, allowing you to use DSCC to create server instances.
# install-path/dsee6/cacao_2/cacao/bin/cacaoadm list-params
Update if needed:
# install-path/dsee6/cacao_2/cacao/bin/cacaoadm stop # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param snmp-adaptor-port=snmp-port # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param snmp-adaptor-trap-port=snmp-trap-port # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param jmxmp-connector-port=jmxmp-port # install-path/dsee6/cacao_2/cacao/bin/cacaoadm start
# install-path/dsee6/cacao_2/cacao/bin/cacaoadm list-params
Update if needed:
# install-path/dsee6/cacao_2/cacao/bin/cacaoadm stop # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param snmp-adaptor-port=snmp-port # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param snmp-adaptor-trap-port=snmp-trap-port # install-path/dsee6/cacao_2/cacao/bin/cacaoadm set-param jmxmp-connector-port=jmxmp-port # install-path/dsee6/cacao_2/cacao/bin/cacaoadm start
# install-path/dscc6/bin/dsccsetup ads-create -p port -P secure-port
On Linux
# install-path/ds6/bin/dsconf import -p port /tmp/dscc.ldif cn=dscc
On Windows
# install-path\ds6\bin\dsconf.exe import -p port -e c:\temp\dscc.ldif cn=dscc
# install-path/dscc6/bin/dsccreg remove-server instance_path
# install-path/dscc6/bin/dsccreg add-server instance_path
During the installation process, a WAR file is saved on your system. The WAR file contains the DSCC web application which, when deployed with the application server, enables you to access and manage the server instances through web console.
To Deploy the WAR File with Sun Java System Application Server
Create an application server instance.
$ mkdir /local/domainroot $ setenv AS_DOMAINS_ROOT /local/domainroot $ cd app-server-install-path/bin $ asadmin create-domain --domaindir ${AS_DOMAINS_ROOT} --adminport 3737 \ --adminuser boss dscc
Edit the server.policy file.
Open the server.policy file.
$ vi ${AS_DOMAINS_ROOT}/dscc/config/server.policy
Add the following statements to the end of the file:
// Permissions for Directory Service Control Center grant codeBase "file:${com.sun.aas.instanceRoot}/ applications/j2ee-modules/dscc/-" { permission java.security.AllPermission; };
This configures the application server to grant all of the Java permissions to the DSCC application.
Deploy the WAR file in your application server instance.
$ asadmin start-domain --domaindir ${AS_DOMAINS_ROOT} --user boss dscc $ cp install-path/var/dscc6/dscc.war ${AS_DOMAINS_ROOT}/dscc/autodeploy
For more information about creating and configuring application server instances and deploying the WAR file, refer to the Sun Java System Application Server Online Help.
Open DSCC.
Use http://hostname:8080/dscc or https://hostname:8181/dscc based on the configuration of your application server.
The Directory Service Manager Login page displays.
To Deploy the WAR File with Tomcat
Identify your Tomcat installation and instance.
$ setenv CATALINA_HOME tomcat-install-path $ setenv CATALINA_BASE tomcat-instance-path $ setenv JAVA_HOME jdk-home-dir
For installing Tomcat and creating instances, refer to the Tomcat documentation.
Deploy the WAR file.
Create the DSCC directory as shown below:
$ mkdir ${CATALINA_BASE}/webapps/dscc
Copy the dscc.war file into newly created DSCC folder and unzip the dscc.war file.
$ unzip -d ${CATALINA_BASE}/webapps/dscc install-path/var/dscc6/dscc.war
Add the emphasized text in the ${CATALINA_BASE}/conf/web.xml file as shown below:
... <servlet> <servlet-name>jsp</servlet-name> <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class> <init-param> <param-name>fork</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>xpoweredBy</param-name> <param-value>false</param-value> </init-param> ...
<init-param> <param-name>enablePooling</param-name> <param-value>false</param-value> </init-param>
<init-param> <param-name>enablePooling</param-name> <param-value>false</param-value> </init-param> <load-on-startup>3</load-on-startup> </servlet> ....
Verify the permissions of startup.sh (tomcat5.exe on Windows) and run the following command:
$ ${CATALINA_HOME}/bin/startup.sh
Use http://hostname:8080/dscc to connect to DSCC.
The Directory Service Manager Login page displays.