Abstract: A system and method for controlling rates for a Lightweight Directory Access Protocol (LDAP) over MQSeries (LoM) server. The system includes a health metrics engine that calculates an actual delay value, a LoM server that asynchronously obtains the actual delay value from the health metrics engine and place the delay value between one or more requests, and a LDAP master that accepts the one or more requests and send information in the one or more requests to a LDAP replica.

Abstract: A system and method for controlling rates for a Lightweight Directory Access Protocol (LDAP) over MQSeries (LoM) server. The system includes a health metrics engine that calculates an actual delay value, a LoM server that asynchronously obtains the actual delay value from the health metrics engine and place the delay value between one or more requests, and a LDAP master that accepts the one or more requests and send information in the one or more requests to a LDAP replica.

Abstract: A system and method for controlling rates for a Lightweight Directory Access Protocol (LDAP) over MQSeries (LoM) server. The system includes a health metrics engine that calculates an actual delay value, a LoM server that asynchronously obtains the actual delay value from the health metrics engine and place the delay value between one or more requests, and a LDAP master that accepts the one or more requests and send information in the one or more requests to a LDAP replica.

Abstract: A system and method for controlling rates for a Lightweight Directory Access Protocol (LDAP) over MQSeries (LoM) server. The system comprises a health metrics engine configured to calculate an actual delay value, at least one LoM server configured to asynchronously obtain the actual delay value from the health metrics engine and place the delay value between one or more requests, and a LDAP master configured to accept the one or more requests and send information in the one or more requests to a LDAP replica.

Abstract: A system and method for controlling rates for a Lightweight Directory Access Protocol (LDAP) over MQSeries (LoM) server. The system includes a health metrics engine that calculates an actual delay value, a LoM server that asynchronously obtains the actual delay value from the health metrics engine and place the delay value between one or more requests, and a LDAP master that accepts the one or more requests and send information in the one or more requests to a LDAP replica.

Abstract: A method is provided to control access to a software application and, more particularly, to control access to a first software application using a second trusted application. The method comprises extracting data from a decrypted client request and determining a request type from the extracted data. The method further comprises ascertaining an entry type value from at least one of the extracted data and an entry and creating at least one string by prepending the entry type value to one or more attributes associated with the entry. Additionally, the method includes comparing the at least one string to one or more record entries to determine whether a client has permission to perform the request type.

Abstract: Access to data in a file created by a mail and calendaring client application is provided to other applications without the need for use of the mail and calendaring client. A request is received from the other application for a document in the file. The document is retrieved in XML form. Sections are expanded by creating URLs and inserting these into the retrieved document. Content of sections is then retrieved in HTML form from the file and inserted into the document at the location of the corresponding URLs. Data for attachments, image tags and other links is obtained and inserted into the document. An object is created containing the entire expanded document and sent to the requesting application.

Abstract: A system and method for controlling rates for a Lightweight Directory Access Protocol (LDAP) over MQSeries (LoM) server. The system comprises a health metrics engine configured to calculate an actual delay value, at least one LoM server configured to asynchronously obtain the actual delay value from the health metrics engine and place the delay value between one or more requests, and a LDAP master configured to accept the one or more requests and send information in the one or more requests to a LDAP replica.

Abstract: A method and system is provided so that requests to a first application (e.g., an LDAP directory) are routed to a second application, the second application being trusted by the first application. The second application validates the requests and sends the request to the first software application when the first application is available. Requests may be queued for processing until the first application is available so that the requests remain pending. A reply may be sent to the requester indicating the results of the request. The second software application processes authentication and validation of the request thereby relieving the first application of this function. Since the second application is a trusted application, the request to the first application may be applied with improved efficiencies increasing the overall performance of the first software application.

Abstract: A method is provided to control access to a software application and, more particularly, to control access to a first software application using a second trusted application. The method comprises extracting data from a decrypted client request and determining a request type from the extracted data. The method further comprises ascertaining an entry type value from at least one of the extracted data and an entry and creating at least one string by prepending the entry type value to one or more attributes associated with the entry. Additionally, the method includes comparing the at least one string to one or more record entries to determine whether a client has permission to perform the request type.

Abstract: Access to data in a file created by a first application is provided to other applications without the need for use of the first application. A request is received from the other application for a document in the file. The document is retrieved in XML from using a specially developed database. Sections in the document may be expanded by retrieving content in HTML form from the file and inserting into the retrieval document. Data for attachments, image tags, and iframe links is obtained and inserted into the document. A complex XML object is created containing the entire expanded document. The object is converted into a SOAP message according to a complex set of rules and sent back to the requesting application over a communication link using any transmission protocol such as HTTP or HTTPS.

Abstract: Access to data in a file created by a first application is provided to other applications without the need for use of the first application. A request is received from the other application for a document in the file. The document is retrieved in XML from using a specially developed database. Sections in the document may be expanded by retrieving content in HTML form from the file and inserting into the retrieval document. Data for attachments, image tags, and iframe links is obtained and inserted into the document. A complex XML object is created containing the entire expanded document. The object is converted into a SOAP message according to a complex set of rules and sent back to the requesting application over a communication link using any transmission protocol such as HTTP or HTTPS.

Abstract: Access to data in a file created by a mail and calendaring client application is provided to other applications without the need for use of the mail and calendaring client. A request is received from the other application for a document in the file. The document is retrieved in XML form. Sections are expanded by creating URLs and inserting these into the retrieved document. Content of sections is then retrieved in HTML form from the file and inserted into the document at the location of the corresponding URLs. Data for attachments, image tags and other links is obtained and inserted into the document. An object is created containing the entire expanded document and sent to the requesting application.