Run update.sh
This commit is contained in:
Docker Library Bot
parent
f8d7508376
commit
365a1cf284
|
|
@ -11,24 +11,44 @@ For more information about this image and its history, please see the [relevant
|
|||
|
||||
# Overview
|
||||
|
||||
This image contains IBM WebSphere Application Server for Developers Liberty Profile. For more information on WebSphere Application Server Liberty Profile, see the [WASdev](https://developer.ibm.com/wasdev/docs/category/getting-started/) site. Due to the current lack of geographic export controls on Docker Hub it has been necessary to remove the IBM JRE from this image. The image now builds on the Debian based `java:jre` OpenJRE official repository image. To build an Ubuntu image with the IBM JRE, use the Dockerfiles available in the [ibmjre](https://github.com/WASdev/ci.docker/tree/ibmjre/websphere-liberty/8.5.5) branch on GitHub.
|
||||
The images in this repository contain IBM WebSphere Application Server for Developers Liberty Profile. For more information on WebSphere Application Server Liberty, see the [WASdev](https://developer.ibm.com/wasdev/docs/category/getting-started/) site. Due to the current lack of geographic export controls on Docker Hub it has been necessary to remove the IBM Java Runtime Environment from these images. The images now build on the Debian based `java:jre` OpenJRE official repository image. To build an Ubuntu image with the IBM JRE, use the Dockerfiles available in the [ibmjre](https://github.com/WASdev/ci.docker/tree/ibmjre/websphere-liberty/8.5.5) branch on GitHub.
|
||||
|
||||
# Images
|
||||
|
||||
There are multiple images available in this repository. The image with the tag `beta` contains the contents of the runtime JAR for the latest monthly beta. The other images are all based on the latest generally available fix pack.
|
||||
|
||||
The `kernel` image contains just the Liberty kernel and no additional runtime features. This image can be used as the basis for custom built images that contain only the features required for a specific application. For example, the following Dockerfile starts with this image, copies in the `server.xml` that lists the features required by the application, and then uses the `installUtility` command to download those features from the online repository.
|
||||
|
||||
```dockerfile
|
||||
FROM websphere-liberty:kernel
|
||||
COPY server.xml /opt/ibm/wlp/usr/servers/defaultServer/
|
||||
RUN installUtility install --acceptLicense defaultServer
|
||||
```
|
||||
|
||||
The `common` image adds a set of features that are expected to be of use for a typical production scenario. These features are: `appSecurity-2.0`, `collectiveMember-1.0`, `localConnector-1.0`, `ldapRegistry-3.0`, `monitor-1.0`, `requestTiming-1.0`, `restConnector-1.0`, `sessionDatabase-1.0`, `ssl-1.0` and `webCache-1.0`. This image is the basis for the `webProfile6` and `webProfile7` images.
|
||||
|
||||
The `webProfile6` image contains the features required for Java EE6 Web Profile compliance. It also pulls in additional features to bring the contents in to line with the features available for download via the runtime JAR, most notably the features required for OSGi applications.
|
||||
|
||||
The `webProfile7` image contains the features required for Java EE7 Web Profile compliance. The `javaee7` image extends this image and adds the features required for Java EE7 Full Platform compliance. The `javaee7` image is also tagged with `latest`.
|
||||
|
||||
There are also corresponding image tags that contain the version number of the Liberty release contained within the image. These are primarily to signpost the current version in use and will be replaced when a subsequent release becomes available. Consequently, only use these tags if you explicitly want your build to break when a new release becomes available. The Liberty zero migration policy means that you can use the non-version specific tags with the confidence that your application will continue to work when a new release becomes available.
|
||||
|
||||
# Usage
|
||||
|
||||
In order to use the image, it is necessary to accept the terms of the WebSphere Application Server for Developers license. This is achieved by specifying the environment variable `LICENSE` equal to `accept` when running the image. You can also view the license terms by setting this variable to `view`. Failure to set the variable will result in the termination of the container with a usage statement.
|
||||
In order to use any of the images, it is necessary to accept the terms of the WebSphere Application Server for Developers license. This is achieved by specifying the environment variable `LICENSE` equal to `accept` when running an image. You can also view the license terms by setting this variable to `view`. Failure to set the variable will result in the termination of the container with a usage statement.
|
||||
|
||||
The image is designed to support a number of different usage patterns. The following examples are based on the Liberty [application deployment sample](https://developer.ibm.com/wasdev/docs/article_appdeployment/) and assume that [DefaultServletEngine.zip](https://www.ibm.com/developerworks/mydeveloperworks/blogs/wasdev/resource/DefaultServletEngine.zip) has been extracted to `/tmp` and the `server.xml` updated to accept HTTP connections from outside of the container by adding the following element inside the `server` stanza:
|
||||
The images are designed to support a number of different usage patterns. The following examples are based on the Java EE6 Liberty [application deployment sample](https://developer.ibm.com/wasdev/docs/article_appdeployment/) and assume that [DefaultServletEngine.zip](https://www.ibm.com/developerworks/mydeveloperworks/blogs/wasdev/resource/DefaultServletEngine.zip) has been extracted to `/tmp` and the `server.xml` updated to accept HTTP connections from outside of the container by adding the following element inside the `server` stanza:
|
||||
|
||||
```xml
|
||||
<httpEndpoint host="*" httpPort="9080" httpsPort="-1"/>
|
||||
```
|
||||
|
||||
1. The image contains a default server configuration that specifies the `webProfile-6.0` feature and exposes ports 9080 and 9443 for HTTP and HTTPS respectively. A WAR file can therefore be mounted in to the `dropins` directory of this server and run. The following example starts a container in the background running a WAR file from the host file system with the HTTP and HTTPS ports mapped to 80 and 443 respectively.
|
||||
1. Each image contains a default server configuration that specifies the corresponding features and exposes ports 9080 and 9443 for HTTP and HTTPS respectively. A WAR file can therefore be mounted in to the `dropins` directory of this server and run. The following example starts a container in the background running a WAR file from the host file system with the HTTP and HTTPS ports mapped to 80 and 443 respectively.
|
||||
|
||||
```console
|
||||
$ docker run -e LICENSE=accept -d -p 80:9080 -p 443:9443 \
|
||||
-v /tmp/DefaultServletEngine/dropins/Sample1.war:/opt/ibm/wlp/usr/servers/defaultServer/dropins/Sample1.war \
|
||||
websphere-liberty
|
||||
websphere-liberty:webProfile6
|
||||
```
|
||||
|
||||
Once the server has started, you can browse to http://localhost/Sample1/SimpleServlet on the Docker host.
|
||||
|
|
@ -40,13 +60,13 @@ The image is designed to support a number of different usage patterns. The follo
|
|||
```console
|
||||
$ docker run -e LICENSE=accept -d -p 80:9080 \
|
||||
-v /tmp/DefaultServletEngine:/opt/ibm/wlp/usr/servers/DefaultServletEngine \
|
||||
websphere-liberty /opt/ibm/wlp/bin/server run DefaultServletEngine
|
||||
websphere-liberty:webProfile6 /opt/ibm/wlp/bin/server run DefaultServletEngine
|
||||
```
|
||||
|
||||
3. It is also possible to build an application layer on top of this image using either the default server configuration or a new server configuration and, optionally, accept the license as part of that build. Here we have copied the `Sample1.war` from `/tmp/DefaultServletEngine/dropins` to the same directory as the following Dockerfile.
|
||||
|
||||
```dockerfile
|
||||
FROM websphere-liberty
|
||||
FROM websphere-liberty:webProfile6
|
||||
ADD Sample1.war /opt/ibm/wlp/usr/servers/defaultServer/dropins/
|
||||
ENV LICENSE accept
|
||||
```
|
||||
|
|
@ -63,7 +83,7 @@ The image is designed to support a number of different usage patterns. The follo
|
|||
Build and run the data volume container:
|
||||
|
||||
```dockerfile
|
||||
FROM websphere-liberty
|
||||
FROM websphere-liberty:webProfile6
|
||||
ADD DefaultServletEngine /opt/ibm/wlp/usr/servers/DefaultServletEngine
|
||||
```
|
||||
|
||||
|
|
@ -77,7 +97,7 @@ The image is designed to support a number of different usage patterns. The follo
|
|||
|
||||
```console
|
||||
$ docker run -e LICENSE=accept -d -p 80:9080 \
|
||||
--volumes-from app websphere-liberty \
|
||||
--volumes-from app websphere-liberty:webProfile6 \
|
||||
/opt/ibm/wlp/bin/server run DefaultServletEngine
|
||||
```
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue