Abstract: During a technique for estimating a scalability breakpoint of a software product, performance load tests of the software product are performed with different numbers of simulated concurrent users. For a given number of simulated concurrent users, a performance load test may include an associated set of transactions that are executed by the software product. Furthermore, during the performance load tests performance metrics for the transactions in the associated sets of transactions are measured. Then estimated total performance metrics for the transactions in the associated sets of transactions for the different numbers of simulated concurrent users are determined based on the measured performance metrics and the associated sets of transactions. Next, using the determined estimated total performance metrics, the estimated scalability breakpoint is calculated.

Abstract: An embodiment of the present invention provides a system that enables a user to securely invoke a REST (Representational State Transfer) API (Application Programming Interface) at an application server. A client can establish a secure communication channel with an application server, and can send a request to the application server to invoke the REST API. The client can then receive a security token from an authentication system in response to authenticating the user with the authentication system. Next, the client can receive a nonce and a timestamp from the application server. The client can then determine a security token digest using the security token, the nonce, and the timestamp. Next, the client can resend the request to the application server to invoke the REST API with the security token digest. The application server can invoke the REST API if the security token digest is valid.

Abstract: System and method for designing and implementing secure Web Services according to a Web Services Security Assessment structured methodology and design patterns. Lifecycles of the Web Services Security Assessment structured methodology may include, but are not limited to: vision and strategy, architecture design, development, integration, and deployment. In one embodiment, security components may be identified based on one or more use case requirements. Web Services objects that need to be protected may be identified. The object relationship for security protection may be defined, and associated trust domains, security policy and strategy and threat profiles may be identified. Protection schemes for these Web Services objects may be generated. Web Services security design patterns may be applied.

Abstract: During a technique for estimating a scalability breakpoint of a software product, performance load tests of the software product are performed with different numbers of simulated concurrent users. For a given number of simulated concurrent users, a performance load test may include an associated set of transactions that are executed by the software product. Furthermore, during the performance load tests performance metrics for the transactions in the associated sets of transactions are measured. Then estimated total performance metrics for the transactions in the associated sets of transactions for the different numbers of simulated concurrent users are determined based on the measured performance metrics and the associated sets of transactions. Next, using the determined estimated total performance metrics, the estimated scalability breakpoint is calculated.

Abstract: System and method for integrating Web Services using a Web Services Structured Methodology are described. Embodiments of a Web Services Structured Methodology may be used to integrate Web Services in Enterprise and Cross-Enterprise business systems, and to integrate legacy systems (e.g. legacy mainframe systems) with Web Services in Enterprise and Cross-Enterprise business systems. Embodiments may provide an integrated Web Services architecture design mechanism that may be used for Enterprise and Cross-Enterprise integration of Web Services. Embodiments may be used for Legacy Mainframe Integration and Interoperability with Web Services.

Abstract: System and method for designing and implementing Web Services according to a structured methodology and design patterns. Embodiments may incorporate a structured methodology, best practices and design patterns that address reliability, availability and scalability of Web Services architecture. Embodiments may provide mechanisms for integrating heterogeneous technology components into Web Services. Embodiments may provide a vendor-independent Web Services architecture framework and reusable Web Services design patterns, which may be used in creating end-to-end solutions based on past experience and best practices. Embodiments may include design patterns and best practices for delivering Web Services solutions with Quality of Services. One embodiment may provide a Business-to-Business Integration (B2Bi) integration framework for Web Services. Embodiments may provide a Web Security framework and design patterns for designing end-to-end Web Services security.

Abstract: System and method for generating Web Services using a Web Services Structured Methodology. One embodiment may be implemented as a Web Services architecture design mechanism. Lifecycles of the Web Services design process may include vision and strategy, architecture design, development, integration, and deployment. In one embodiment, the Web Services architecture design mechanism may implement a structured methodology design process for Web Services. One embodiment may include a reusable Web Services design pattern catalog and a mechanism for maintaining and updating the catalog and for using the catalog to apply design patterns when designing and implementing Web Services. One embodiment may be used for Enterprise And Cross-Enterprise Integration of Web Services. One embodiment may be used for Legacy Mainframe Integration and Interoperability with Web Services.

Abstract: An embodiment of the present invention provides a system that enables a user to securely invoke a REST (Representational State Transfer) API (Application Programming Interface) at an application server. A client can establish a secure communication channel with an application server, and can send a request to the application server to invoke the REST API. The client can then receive a security token from an authentication system in response to authenticating the user with the authentication system. Next, the client can receive a nonce and a timestamp from the application server. The client can then determine a security token digest using the security token, the nonce, and the timestamp. Next, the client can resend the request to the application server to invoke the REST API with the security token digest. The application server can invoke the REST API if the security token digest is valid.