Create and Deploy your WAR File to Liberty Application Server V8.5.5.8

To work with your Open Social Widget you have to deploy it to Liberty. Because Liberty is a little bit different then Tomcat…let me give you some hints.

Requirement:

RTC 6.0.1 or higher

Deployment “How To”:

  1. Go to your Liberty install directory i.e. “C:\IBM\JazzTeamServer602m3\server\liberty”. Change to “C:\IBM\JazzTeamServer602m3\server\liberty\servers\clm”.
  2. You will see a dropins directory. Copy the WAR File to this dropins directory.
  3. Edit the C:\IBM\JazzTeamServer602m3\server\liberty\servers\clm\server.xml
  4. Change the line <applicationMonitor dropinsEnabled=”false” pollingRate=”10s” updateTrigger=”mbean”/> to   <applicationMonitor dropinsEnabled=”true” pollingRate=”10s” updateTrigger=”mbean”/>
  5. Restart the App Server with setver.shutdown.bat and server.startup.bat inside C:\IBM\JazzTeamServer602m3\server.
  6. Test if you can access  https://ssejtsserver:9443/<WARFileName>/status.xml if you use a status.xml.

 

Create a WAR File from static content:

If you don’t have a WAR File you can create one for your static Files. This example assume that your Open Social Widget has the name “keyscript”.

  1. Create a “META-INF” and “WEB-INF” directory inside your Open Social Widget Dev directory “keyscript”.
  2. Create a MANIFEST.MF inside META-INF with the following content
    1. Manifest-Version: 1.0
    2. Created-By: 1.8.0_66 (Oracle Corporation)
  3. Create a web.xml inside your WEB-INF directory with the following content:
  4. <?xml version=’1.0′ encoding=’ISO-8859-1′?>

    <web-app xmlns=’http://java.sun.com/xml/ns/j2ee&#8217;

    xmlns:xsi=’http://www.w3.org/2001/XMLSchema-instance&#8217;

    xsi:schemaLocation=’http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd&#8217;

    version=’2.4′>

  5. <display-name>keyscript</display-name>

    </web-app>

  6. Create the WAR File with the command “jar cvf keyscript.war   .”

 

Avoid turnaround:

The turnaround of changeing something then create a new WAR File and deploy it, is too slow. I found a trick to avoid this.

  1. Unzip the WAR File inside the dropins folder
  2. Rename the directory from i.e. “keystore” to “keystore.war” (if your Widgetname is keystore)
  3. Remove the original WAR File

Now you can work inside the “keystore.war” and you will see the changes immediately.

 

 

  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: