|
|
@@ -14,15 +14,15 @@ COPY server.xml /config/
|
|
|
RUN installUtility install --acceptLicense defaultServer
|
|
|
```
|
|
|
|
|
|
-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 by using the runtime JAR, most notably the features required for OSGi applications.
|
|
|
+The `webProfile8` image contains the features required for Java EE8 Web Profile compliance. The `javaee8` image extends this image and adds the features required for Java EE8 Full Platform compliance. The `javaee8` image is also tagged with `latest`.
|
|
|
|
|
|
-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`.
|
|
|
+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 `webProfile6`, `webProfile7` and `javaee7` images all also contain a common 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`.
|
|
|
+The `webProfile8`, `javaee8`, `webProfile7` and `javaee7` images also contain a common 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-2.0`, `sessionDatabase-1.0`, `ssl-1.0`, `transportSecurity-1.0` and `webCache-1.0`.
|
|
|
|
|
|
# Usage
|
|
|
|
|
|
-The images are designed to support a number of different usage patterns. The following examples are based on the Java EE7 Liberty [application deployment sample](https://developer.ibm.com/wasdev/docs/article_appdeployment/) and assume that [DefaultServletEngine.zip](https://github.com/WASdev/sample.servlet/releases/download/V1/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 EE8 Liberty [application deployment sample](https://developer.ibm.com/wasdev/docs/article_appdeployment/) and assume that [DefaultServletEngine.zip](https://github.com/WASdev/sample.servlet/releases/download/V1/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"/>
|
|
|
@@ -33,7 +33,7 @@ The images are designed to support a number of different usage patterns. The fol
|
|
|
```console
|
|
|
$ docker run -d -p 80:9080 -p 443:9443 \
|
|
|
-v /tmp/DefaultServletEngine/dropins/Sample1.war:/config/dropins/Sample1.war \
|
|
|
- %%IMAGE%%:webProfile7
|
|
|
+ %%IMAGE%%:webProfile8
|
|
|
```
|
|
|
|
|
|
When the server is started, you can browse to http://localhost/Sample1/SimpleServlet on the Docker host.
|
|
|
@@ -45,13 +45,13 @@ The images are designed to support a number of different usage patterns. The fol
|
|
|
```console
|
|
|
$ docker run -d -p 80:9080 \
|
|
|
-v /tmp/DefaultServletEngine:/config \
|
|
|
- %%IMAGE%%:webProfile7
|
|
|
+ %%IMAGE%%:webProfile8
|
|
|
```
|
|
|
|
|
|
3. You can also build an application layer on top of this image by using either the default server configuration or a new server configuration. In this example, we have copied the `Sample1.war` from `/tmp/DefaultServletEngine/dropins` to the same directory as the following Dockerfile.
|
|
|
|
|
|
```dockerfile
|
|
|
- FROM %%IMAGE%%:webProfile7
|
|
|
+ FROM %%IMAGE%%:webProfile8
|
|
|
ADD Sample1.war /config/dropins/
|
|
|
```
|
|
|
|
|
|
@@ -67,7 +67,7 @@ The images are designed to support a number of different usage patterns. The fol
|
|
|
Build and run the data volume container:
|
|
|
|
|
|
```dockerfile
|
|
|
- FROM %%IMAGE%%:webProfile7
|
|
|
+ FROM %%IMAGE%%:webProfile8
|
|
|
ADD DefaultServletEngine /config
|
|
|
```
|
|
|
|
|
|
@@ -81,7 +81,7 @@ The images are designed to support a number of different usage patterns. The fol
|
|
|
|
|
|
```console
|
|
|
$ docker run -d -p 80:9080 \
|
|
|
- --volumes-from app %%IMAGE%%:webProfile7
|
|
|
+ --volumes-from app %%IMAGE%%:webProfile8
|
|
|
```
|
|
|
|
|
|
# Providing your own keystore/truststore
|
|
|
@@ -119,15 +119,15 @@ Liberty writes to two different directories when running: `/opt/ibm/wlp/output`
|
|
|
```console
|
|
|
docker run -d -p 80:9080 -p 443:9443 \
|
|
|
--tmpfs /opt/ibm/wlp/output --tmpfs /logs -v /config --read-only \
|
|
|
- %%IMAGE%%:javaee7
|
|
|
+ %%IMAGE%%:javaee8
|
|
|
```
|
|
|
|
|
|
# Changing locale
|
|
|
|
|
|
-The base Ubuntu image does not include additional language packs. To use an alternative locale, build your own image that installs the required language pack and then sets the `LANG` environment variable. For example, the following Dockerfile starts with the `%%IMAGE%%:webProfile7` image, installs the Portuguese language pack, and sets Brazilian Portuguese as the default locale:
|
|
|
+The base Ubuntu image does not include additional language packs. To use an alternative locale, build your own image that installs the required language pack and then sets the `LANG` environment variable. For example, the following Dockerfile starts with the `%%IMAGE%%:webProfile8` image, installs the Portuguese language pack, and sets Brazilian Portuguese as the default locale:
|
|
|
|
|
|
```dockerfile
|
|
|
-FROM %%IMAGE%%:webProfile7
|
|
|
+FROM %%IMAGE%%:webProfile8
|
|
|
RUN apt-get update \
|
|
|
&& apt-get install -y language-pack-pt-base \
|
|
|
&& rm -rf /var/lib/apt/lists/*
|