declarative transaction management Transaction bound event Application server-specific integration IBM WebSphere Oracle WebLogic Server Solutions to common problems Use of the wrong transaction manager WebSphere Spring applications may run on a container that itself provides an implementation of JCL, e.g. IBM’s WebSphere Application Server (WAS). This does not cause issues per se but leads to two different late 2017, JDK 6 is being phased out and therefore also Spring’s JDK 6 support. Oracle as well as IBM will terminate all commercial support efforts for JDK 6 in 2018. While Spring will retain its JDK 6

Application server-specific integration .............................................................. 402 IBM WebSphere ........................................................................................ WebSphere Spring applications may run on a container that itself provides an implementation of JCL, e.g. IBM’s WebSphere Application Server (WAS). This does not cause issues per se but leads to two different late 2017, JDK 6 is being phased out and therefore also Spring’s JDK 6 support. Oracle as well as IBM will terminate all commercial support efforts for JDK 6 in 2018. While Spring will retain its JDK 6

monitoring Extend configuration Programmatically 43. What to read next VI. Deploying to the cloud 44. Cloud Foundry Binding to services 45. Heroku 46. CloudBees 47. Openshift 48. What to read next Chapter 7. Advanced topics Lastly, we have a few topics for the more advanced user. Deploy to the cloud: Cloud Foundry | Heroku | CloudBees Build tool plugins: Maven | Gradle Appendix: Application Properties can be used for production deployment. As they are self contained, they are also ideally suited for cloud-based deployment. For additional “production ready” features, such as health, auditing and metric

........... 96 VI. Deploying to the cloud ......................................................................................................... 97 44. Cloud Foundry ............................. 7. Advanced topics Lastly, we have a few topics for the more advanced user. • Deploy to the cloud: Cloud Foundry | Heroku | CloudBees • Build tool plugins: Maven | Gradle • Appendix: Application Properties can be used for production deployment. As they are self contained, they are also ideally suited for cloud-based deployment. For additional “production ready” features, such as health, auditing and metric

........... 96 VI. Deploying to the cloud ......................................................................................................... 97 44. Cloud Foundry ............................. 7. Advanced topics Lastly, we have a few topics for the more advanced user. • Deploy to the cloud: Cloud Foundry | Heroku | CloudBees • Build tool plugins: Maven | Gradle • Appendix: Application Properties can be used for production deployment. As they are self-contained, they are also ideally suited for cloud-based deployment. For additional “production ready” features, such as health, auditing and metric

monitoring Extend configuration Programmatically 43. What to read next VI. Deploying to the cloud 44. Cloud Foundry Binding to services 45. Heroku 46. CloudBees 47. Openshift 48. What to read next Chapter 7. Advanced topics Lastly, we have a few topics for the more advanced user. Deploy to the cloud: Cloud Foundry | Heroku | CloudBees Build tool plugins: Maven | Gradle Appendix: Application Properties can be used for production deployment. As they are self-contained, they are also ideally suited for cloud-based deployment. For additional “production ready” features, such as health, auditing and metric

declarative transaction management Transaction bound event Application server-specific integration IBM WebSphere Oracle WebLogic Server Solutions to common problems Use of the wrong transaction manager people run their Spring applications in a container that itself provides an implementation of JCL. IBM Websphere Application Server (WAS) is the archetype. This often causes problems, and unfortunately working. In such cases with WAS the easiest thing to do is to invert the class loader hierarchy (IBM calls it "parent last") so that the application controls the JCL dependency, not the container. That

monitoring Extend configuration Programmatically 48. What to read next VI. Deploying to the cloud 49. Cloud Foundry Binding to services 50. Heroku 51. Openshift 52. Google App Engine 53. What to read Chapter 7. Advanced topics Lastly, we have a few topics for the more advanced user. Deploy to the cloud: Cloud Foundry | Heroku | CloudBees Build tool plugins: Maven | Gradle Appendix: Application Properties HSQLDB database. spring-boot-starter-cloud- connectors Support for “Spring Cloud Connectors” which simplifies connecting to services in cloud platforms like Cloud Foundry and Heroku. spring-boot-starter-data-

253 5.10. Cloud Foundry Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 5.10.1. Disabling Extended Cloud Foundry Actuator Actuator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 5.10.2. Cloud Foundry Self-signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.1. Deploying to the Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.1.1. Cloud Foundry . . . . . . . . .

253 5.10. Cloud Foundry Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 5.10.1. Disabling Extended Cloud Foundry Actuator Actuator Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 5.10.2. Cloud Foundry Self-signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 6.2. Deploying to the Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 6.2.1. Cloud Foundry. . . . . . . . .