In some DPS deployments, there is a high number of new connections being established. This high connection rate may lead to performances issues. It may be...
In some DPS deployments, there is a high number of new connections being established. This high connection rate may lead to performances issues. It may be useful to consider changing the tcp time wait interval: That parameter notifies TCP/IP on how long to keep the connection control blocks closed. After the applications drop the TCP/IP connection, the control blocks are kept for the specified time. When high connection rates occur, a large backlog of the TCP/IP connections...
In some DPS deployments, there is a high number of new connections being established. This high connection rate may lead to performances issues. It may be useful to consider changing the tcp time wait...
DSEE - Directory Services Enterprise Edition, provides a Web Services access (HTTP/SOAP binding) using the DSMLv2 standard. Development of WS clients using...
DSEE - Directory Services Enterprise Edition, provides a Web Services access (HTTP/SOAP binding) using the DSMLv2 standard. Development of WS clients using the contract-first approach requires a corresponding WSDL file describing the service. I recently wrote such WSDL file. I had to modify slightly some regular expressions present in the DSML types as IDEs like NetBeans or JDeveloper complain during xml binding generation, that's the reason why it may worth sharing this....
DSEE - Directory Services Enterprise Edition, provides a Web Services access (HTTP/SOAP binding) using the DSMLv2 standard. Development of WS clients using the contract-first approach requires a...
Today, my personal counter reached 200 on Sun (Oracle) Developer Forums. 200 posts, mostly in the Directory-related Forums. 200 posts to help the DSEE...
Today, my personal counter reached 200 on Sun (Oracle) Developer Forums. 200 posts, mostly in the Directory-related Forums. 200 posts to help the DSEE community, improve customer experience and collect tons of interesting feedbacks and use cases from the field to help improving our products. http://forums.sun.com/forum.jspa?forumID=761&start=0 Now, please use the corresponding Oracle forum on OTN at https://forums.oracle.com/forums/forum.jspa?forumID=877&start=0
Today, my personal counter reached 200 on Sun (Oracle) Developer Forums. 200 posts, mostly in the Directory-related Forums. 200 posts to help the DSEE community, improve customer experience and...
Outlook LDAP address lookup requires VLV and companion Server Side Sorting controls. If these controls are blocked by DPS, you may get errors messages like "The...
Outlook LDAP address lookup requires VLV and companion Server Side Sorting controls. If these controls are blocked by DPS, you may get errors messages like "The server is not configured to pass through control 1.2.840.113556.1.4.473" or "The server is not configured to pass through control 2.16.840.1.113730.3.4.9" To enable control pass-thru in DPS, use dpconf set-server-prop [...] allowed-ldap-controls:vlv-request \\allowed-ldap-controls:1.2.840.113556.1.4.473
Outlook LDAP address lookup requires VLV and companion Server Side Sorting controls. If these controls are blocked by DPS, you may get errors messages like "The server is not configured to pass...
Sun Directory Server Entreprise Edition 7.0 aka DSEE 7.0 has just been released today and is available for download...
Sun Directory Server Entreprise Edition 7.0 aka DSEE 7.0 has just been released today and is available for download at http://www.sun.com/software/products/directory_srvr_ee/get1.jsp
The JDBC URL structure indicated in the DPS doc set to access ORACLE databases is wrong somehow: Referring to the DPS admin guide, the db-url is in the...
The JDBC URL structure indicated in the DPS doc set to access ORACLE databases is wrong somehow: Referring to the DPS admin guide, the db-url is in the form jdbc:vendor:driver://dbhost:dbport. A correct db-url for Oracle is jdbc:oracle:thin:@localhost:1521:Using "//" instead of "@" may lead to errors similar to the one below:Snipplet from the Oracle EX logs:28-SEP-2009...
The JDBC URL structure indicated in the DPS doc set to access ORACLE databases is wrong somehow: Referring to the DPS admin guide, the db-url is in the form jdbc:vendor:driver://dbhost:dbport. A...
The IBM DB/2 jdbc driver db2jcc.jar has a accompanying license file called db2jcc_license_cu.jar. Both jar files must be part of the DPS java environment. If...
The IBM DB/2 jdbc driver db2jcc.jar has a accompanying license file called db2jcc_license_cu.jar. Both jar files must be part of the DPS java environment. If you don't, you'll get errors similars to "cannot connect to JDBC datasource ..... license is not present". To provide both jar files (driver and license), use dpconf command as follow: $ dpconf create-jdbc-data-source -b sample -B jdbc:db2://hostname:50000/ -J file:/path/to/db2jcc_license_cu.jar -J...
The IBM DB/2 jdbc driver db2jcc.jar has a accompanying license file called db2jcc_license_cu.jar. Both jar files must be part of the DPS java environment. If you don't, you'll get errors similars...
By default, DPS access and error logs are stored in <instance_dir>/logs. Default setting can be changed using the commands below: $ dpconf...
By default, DPS access and error logs are stored in <instance_dir>/logs. Default setting can be changed using the commands below: $ dpconf get-access-log-prop log-file-namelog-file-name : logs/access $ dpconf get-error-log-prop log-file-namelog-file-name : logs/error $ dpconf set-access-log-proplog-file-name:/a/path/to/a/new/location/access $ dpconf set-error-log-proplog-file-name:/a/path/to/a/new/location/error
By default, DPS access and error logs are stored in <instance_dir>/logs. Default setting can be changed using the commands below: $ dpconf get-access-log-prop log-file-namelog-file-name : ...
Unlike DS, DPS 6.3 etimes in the access log are in millisecs. For sake of performance, DPS uses a timeThread that gets the timeregularly (every 500ms only in...
Unlike DS, DPS 6.3 etimes in the access log are in millisecs. For sake of performance, DPS uses a timeThread that gets the timeregularly (every 500ms only in DPS 6.3) instead of performing a system call each time thecurrent time is needed so etimes shown in access logs may be biased to a large extend and show 0ms when the effective etime is < 500ms. Conversaly , etimes may show a value of 500ms when the effective time is smaller. TimeThread -----T1-----T2-----T3-----T4----T5...
Unlike DS, DPS 6.3 etimes in the access log are in millisecs. For sake of performance, DPS uses a timeThread that gets the timeregularly (every 500ms only in DPS 6.3) instead of performing a system...
