Tag Archives: WebSphere

Deploy WebSphere Liberty Profile applications to Bluemix using Maven


The IBM WebSphere Application Server Liberty Buildpack is used to deploy Liberty applications to Bluemix and other Cloud Foundry-based platforms. The Liberty buildpack deploys compiled artifacts such as .war or .ear files, server packages (.zip files), or server directories. In combination with thecloudfoundry-maven-plugin and the liberty-maven-plugin you’re able to integrate all build, test and deployment steps with Maven.

This blog post will show how you can setup the Liberty Profile Server, run and test your application on it, create a packaged server and deploy it to Bluemix – All done with Maven.

An alternative approach would be to deploy the source and execute a Maven build on the Bluemix server using the Heroku buildpack for Java applications as described here.

Working with the JMS Connector in WebSphere Cast Iron, Part 1: Configuring JMS in WebSphere Application Server

via Working with the JMS Connector in WebSphere Cast Iron, Part 1: Configuring JMS in WebSphere Application Server.

Part 1 of this tutorial series explains how to configure Java™ Messaging Service (JMS) to create the Queue Connection Factory in WebSphere Application Server (hereafter called Application Server) and connect to the JMS Connector in WebSphere® Cast Iron Studio and Appliance. You will learn to configure JMS to send messages between two or more clients in Application Server.

IBM® WebSphere Cast Iron is an offering from IBM that provides clients with a platform for integrating cloud-based applications from leading SaaS (Software as a Service) providers with on-premise applications from IBM and others. IBM Cast Iron Studio (herafter called Studio) is a development tool that is used to design, test, and publish integration projects to an IBM Cast Iron Integration Appliance. Studio provides numerous entities that you can drag into a workspace and configure as part of one, or more, business-process orchestrations that comprise an integration project.

WebSphere Application Server offers options for a faster, more flexible Java application server runtime environment with enhanced reliability and resiliency for building and running applications, including cloud and mobile. Application Server implements two main messaging sub-systems. The default messaging provider is internal to WebSphere and the WebSphere MQ messaging system.

Java Message Service (JMS) provides a common interface to standard messaging protocols and also to special messaging services in support of Java programs. Messages can involve the exchange of crucial data between systems and contain information such as event notification and service requests. Messaging is often used to coordinate programs in dissimilar systems or written in different programming languages. By using the JMS interface, you can invoke the messaging services like IBM’s WebSphere MQ, formerly known as MQ Series, and other popular messaging products. In addition, JMS supports messages that contain serialized Java objects and messages that contain XML-based data.

Connectors provides the ability for the Cast Iron Appliance or Cast Iron Live to interact with the enterprise server and perform certain activities, just by configuration with no coding approach. Orchestrations are the main component of a Cast Iron integration solution. All functionalities in an integration solution are controlled by the orchestration. The orchestration contains a set of activities that are performed in an order that is defined within the orchestration editor or workspace.

Configure JRebel with Docker containers

via Configure JRebel with Docker containers – Tech Tip #81 – Miles to go 2.0 ….

JRebel allows you to skip build and redeploy process by instantly deploying your application to the application server of your choice. It is supported in all the major IDEs such as NetBeans, Eclipse, and IntelliJ. It is also supported in a wide variety of application servers such as JBoss EAP, WildFly, WebLogic, WebsFear (err, WebSphere), Tomcat, and many others.

You can easily get started with JRebel in JBoss Developer Studio  or Integrate JRebel with JBoss on your local desktop. It can also be easily used with JBoss Developer Studio and Ticket Monster on OpenShift.

This Tech Tip will explain how do you set up JRebel with Docker containers. Specifically, we’ll use the sample application provided by Java EE 7 Hands-on Lab (jrebel branch), JBoss Tools with Eclipse Mars M5, and running the sample application in WildFly Docker container.

Many thanks to Adam Koblentz (@akoblentz) for helping me through the steps!

Lets get started!

Don’t use System.exit() on Java Web Application

Click to Read

I have recently come across a code snippet, where programmer was using System.exit() if application failed to acquire necessary resource after couple of retry. His reasoning was that since, application cannot function, if essential resources like database is not available or there is no disk space to write records in File system. Ok, I hear you; but System.exit() in Java Web application, which runs inside either web server or application server, which itself is Java program is not a good idea at all. Why? because invoking System.exit() kills your JVM, invoking this from Tomcat or Jetty, will not only kill your application but most likely server itself. This can be potentially dangerous, if that server also host other critical application, which is not uncommon at all. As per my experience, System.exit() calls are quite common in overly broad try-catch blocks in web application start-up code that loads environment variables, properties files, connect to MQ Series, establishes database connection, opens socket connections, etc. This is still ok, if you are writing core Java based server, where each application has their own JVM, but with web application deployed on Tomcat, JBoss, WebSphere, Weblogic or any other application server, using System.exit() is big mistake. In worst case can result in outage for lots of other critical application. On the other hand, there are ways to prevent your web application from someone else’s mistake, by enabling Security Manager. System.exit() and Runtime.exit() both goes through the security manager. Enabling Security manager will catch these calls and reduce them into an exception rather than shutting down the whole VM. It’s not difficult to enable the security manager in most application servers, Tomcat, JBoss both has documented steps to enable security Manager.

Build applications with the IBM DataCache service

Build applications with the IBM DataCache service

As software architects, we constantly juggle business requirements, available resources, and deadlines. Non-functional requirements, such as performance, are usually looked at later in the game. However, it is not as challenging to address non-functional requirements when the technical infrastructure is already in place.

Building applications in IBM Bluemix™ and using the IBM DataCache service allows us to improve our applications’ performance as needed.

What you’ll need to build a similar app

  • A basic knowledge of Javascript
  • A basic knowledge of Java Server Pages (JSP)
  • A basic knowledge of WebSphere® Extreme Scale APIs
  • The Eclipse IDE

Environment setup

To build an application that uses the IBM DataCache service you must set up the proper environment. You must install the Cloud Foundry client to deploy the data cache application in the IBM Cloud environment. For development, you will need to install WebSphere Application Server Liberty Profile and WebSphere Extreme Scale. You must also have the Eclipse IDE already installed.