Abstract: In accordance with an embodiment, described herein is a system and method for automatic porting of software applications into a cloud computing environment (cloud environment, cloud). A cloud service enables software developers to deploy user applications to run within the cloud environment. When a user application is deployed to the environment, a deployment logic determines those aspects of the application, such as certain service usages, that may be incompatible with features provided by the environment, or that should use a particular cloud service, and automatically ports the application, including the use of one or more handlers or extensions, for use within the environment. For example, a user application may have been originally developed to use JAVAMAIL™, which presents a security risk in a cloud environment. To minimize such risk, the application can instead be ported to use, for example, a REST-based e-mail service supported by the cloud environment.

Abstract: In accordance with an embodiment, described herein is a system and method for providing application security in a cloud computing or other environment. A plurality of hot-spot configurations define API usages which, for security reasons, are of interest to be monitored at runtime, such as invocations of particular methods that are likely to be used to attempt unauthorized access. Upon a user application being received for deployment to the cloud environment, an application compiler determines, for API usages expressed as method invocations within the source code of the application, one or more hot-spot configurations and associated policies or actions. The application compiler can then inject the user application to provide a security manager that, during runtime, monitors the methods and values invoked, and communicates with one or more security extensions to grant or deny access.

Abstract: In accordance with an embodiment, described herein is a system and method for automatic porting of software applications into a cloud computing environment (cloud environment, cloud). A cloud service enables software developers to deploy user applications to run within the cloud environment. When a user application is deployed to the environment, a deployment logic determines those aspects of the application, such as certain service usages, that may be incompatible with features provided by the environment, or that should use a particular cloud service, and automatically ports the application, including the use of one or more handlers or extensions, for use within the environment. For example, a user application may have been originally developed to use JavaMail, which presents a security risk in a cloud environment. To minimize such risk, the application can instead be ported to use, for example, a REST-based e-mail service supported by the cloud environment.

Abstract: A system and method for providing whitelist functionality for use with a cloud computing environment. In accordance with an embodiment, software applications being deployed to the cloud are restricted from using certain classes or application program interfaces (APIs). During provisioning by, e.g., a Java cloud services (JCS) infrastructure, or another component of the cloud environment, an application's resources, such as its classes or API calls, can be matched against a whitelist of acceptable resources. If the application fails to be validated against the whitelist, it will not be deployed to the cloud, and the customer/user notified accordingly. In accordance with an embodiment, a whitelist functionality can be packaged within a software development kit (SDK), which customers/users can use during development of their applications, to verify that the applications will comply with, or successfully validate against the whitelist, prior to attempting to deploy the applications to the cloud.

Abstract: In accordance with an embodiment, described herein is a system and method for providing application security in a cloud computing or other environment. A plurality of hot-spot configurations define API usages which, for security reasons, are of interest to be monitored at runtime, such as invocations of particular methods that are likely to be used to attempt unauthorized access. Upon a user application being received for deployment to the cloud environment, an application compiler determines, for API usages expressed as method invocations within the source code of the application, one or more hot-spot configurations and associated policies or actions. The application compiler can then inject the user application to provide a security manager that, during runtime, monitors the methods and values invoked, and communicates with one or more security extensions to grant or deny access.

Abstract: An aspect of the present invention facilitates testing of client systems consuming contractual services on different server systems. In one embodiment, a contract (for which the client system is sought to be tested) is first inspected to determine the set of contractual services present in the contract and a minimal implementation for each of the determined set of contractual services is generated. The minimal implementations are designed to merely provide arbitrary outputs consistent with the contract. On receiving a request to invoke a desired one of the set of contractual services from the client system, a corresponding response is sent due to invocation of the (minimal) implementation generated for the desired contractual service, thereby facilitating testing of client system for a different server system.

Abstract: An aspect of the present invention facilitates a service application to operate with different frameworks executing in application servers. In one embodiment, the different interfaces according to which the different frameworks are designed to operate with service application are identified, including the interface implemented by the service application. Wrapper modules are then generated based on the differences between the identified interfaces and the interface implemented by the service application. The generated wrapper modules are then deployed along with the service application to facilitate the service application to operate with different frameworks.

Abstract: An aspect of the present invention facilitates testing of client systems consuming contractual services on different server systems. In one embodiment, a contract (for which the client system is sought to be tested) is first inspected to determine the set of contractual services present in the contract and a minimal implementation for each of the determined set of contractual services is generated. The minimal implementations are designed to merely provide arbitrary outputs consistent with the contract. On receiving a request to invoke a desired one of the set of contractual services from the client system, a corresponding response is sent due to invocation of the (minimal) implementation generated for the desired contractual service, thereby facilitating testing of client system for a different server system.

Abstract: An aspect of the present invention facilitates a service application to operate with different frameworks executing in application servers. In one embodiment, the different interfaces according to which the different frameworks are designed to operate with service application are identified, including the interface implemented by the service application. Wrapper modules are then generated based on the differences between the identified interfaces and the interface implemented by the service application. The generated wrapper modules are then deployed along with the service application to facilitate the service application to operate with different frameworks.

Abstract: Automatic generation of a client program such as Web service client source code for a client application for enabling the client application access to the Web service, for testing interoperability of the client application with the Web service. The Web service client source code is automatically generated for different execution environments of the client application. In one embodiment, the Web service client source code is generated by analyzing a proxy code where the proxy code may be generated from a WSDL file that may describe various operations provided by the Web service. Alternatively, the Web service client source code may be generated based on configuration information that may provide data indicating the context in which the Web service client source code may be generated. Further, automatic generation of the test data to be sent from the client application to the web service in an interoperability test is also provided.