WAR File

The collaboration server software is shipped as a single .WAR file. The shipped file is sometimes called a WJAR, because it is a valid .war file but can also be started directly as an executable jar file (with something like java -jar unblu.war).

The WAR file supports exporting individual products as WAR or EAR file using special command line switches.

Note: You should refer to your servlet container documentation for information on how to install WAR files. By way of an example, you can find step-by-step (example) instructions on how to install unblu on a Tomcat server here: Installing on Tomcat

Note: If you intend to use an IBM WebSphere application server you must create an Enterprise Application Archive (EAR). See Running as an Enterprise Application Archive (EAR)

We recommend that you run unblu as the root application in your servlet container (context-path = /).

There are several ways to use the unblu WAR.

Running as .WAR on a Java Servlet Container

The WAR file can directly be deployed to a servlet container.

Note: After you have installed the web application, you should be able to reach the unblu login page at http://localhost: (port number on which your server runs)

Running as an Enterprise Application Archive (EAR)

Note: An EAR is a file with the .ear extension containing both .jar and .war files to be deployed on an application server. EAR files are used to deploy enterprise applications containing Enterprise Java Beans (EJBs), web applications, and 3rd party libraries. It is also a jar file. It has a special directory called APP-INF that contains the application.xml file. Note that APP-INF is WebLogic-specific and does not exist in the Java EE standard.

Prior to running the desired unblu product as an EAR it is necessary to export either the whole or the selected product as EAR.

Running the WAR in Standalone Mode

The unblu WAR file can also be used as a executable jar. An embedded jetty based web server is used in that case. Standalone mode is not suitable for production use.

To start the default product with default configuration use:

java -jar product.com.unblu.war

and run it in a jetty web server on an automatically selected TCP port in the range from 6060 to 7070. (To manually select the TCP port pass "-Dport=" on the command line.)

Command Line Options

When running the executable jar, the following command line options are available:

Options Description
-e,--export <arg> Type of export. Possible options: 'ear' or 'wjar'
-h,--help Display this help message
-l,--list Format of output: ( version: build: branch: )
-m,--migrationOnly use to shutdown the product after database migration is complete
-o,--output <arg> File to write the exported product to. If not given, output will default to STDOUT.
-p,--product <arg> ID of the product to start. For example product.com.unblu.enterprise (default)
-t,--test Include test bundles into product execution/export (not available in production versions).
-d,--diag Include diag bundles into product execution/export (not available in production versions).

Note: The 'product' switch is also available via System Properties and jndi.

  • deployonprem

results matching ""

    No results matching ""