Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

WebSphere Traditional and IBM HTTP Server on Docker Hub

DZone's Guide to

WebSphere Traditional and IBM HTTP Server on Docker Hub

Docker images containing IBM WebSphere ASD and IBM HTTP Server are now available on Docker Hub! Read on to find out more.

· Cloud Zone
Free Resource

See how the beta release of Kubernetes on DC/OS 1.10 delivers the most robust platform for building & operating data-intensive, containerized apps. Register now for tech preview.

We are pleased to announce that pre-built Docker images containing IBM WebSphere Application Server for Developers V8.5.5.9 traditional and IBM HTTP Server are now available on Docker Hub.

This enables you to get WebSphere Application Server traditional and IBM HTTP Server up and running quickly in your Docker environment with only a single command.

Running WebSphere Application Server traditional is as simple as executing:

docker run --name test -h test -p 9043:9043 -p 9443:9443 -d ibmcom/websphere-traditional

You can watch the container logs as the server starts using:

docker logs -f --tail=all test

Once the server is started, you can access the administrative console on the host running Docker. Browse to https://<IP_address>:9043/ibm/console/logon.do; if you are running Docker on Windows or Mac, use the IP address of the virtual machine running the Docker Machine. Log in with the username wsadmin and the password that is in the password file under the /tmp folder in the Docker container. As covered in the usage information, you can provide your own password.

You can do the configuration either through the administrative console or by using wsadmin scripts.

If you want to use wsadmin to run a simple application you can create a new image with the application as part of the image using a Dockerfile that looks as follows:

1 2 3 FROM ibmcom/websphere-traditional:profileCOPY Sample1.war /tmp/RUN wsadmin.sh -lang jython -conntype NONE -c "AdminApp.install('/tmp/Sample1.war', '[ -appname Sample1 -contextroot /Sample1 -MapWebModToVH [[ Sample1.war Sample1.war,WEB-INF/web.xml default_host]]]')"


From the same directory as the Dockerfile, we can then build an image tagged app:

docker build -t app .


Then run the image:

docker run -d -p 9043:9043 -p 9443:9443 app

Browse to https://<IP_address>:9443/Sample1/SimpleServlet on the Docker host and directly access the application.

Similarly, you can get your IBM HTTP Server up and running quickly by running:

docker run –name ihs -h ihs -p 80:80 -d ibmcom/ibm-http-server


You can create an image with the webserver definition as part of the image using a Dockerfile like this:

1 2 3 FROM ibmcom/ibm-http-serverCOPY responsefile.txt /opt/IBM/WebSphere/Toolbox/WCT/RUN /opt/IBM/WebSphere/Toolbox/WCT/wctcmd.sh -tool pct -defLocPathname /opt/IBM/WebSphere/Plugins -defLocName loc1 -createDefinition -response /opt/IBM/WebSphere/Toolbox/WCT/responsefile.txt


If you experience any problems with the images, raise an issue on GitHub, where you can find the source Dockerfile for the WebSphere traditional and IBM HTTP Server image, or, for more general questions, post to dW Answers in the WASdev space.

New Mesosphere DC/OS 1.10: Production-proven reliability, security & scalability for fast-data, modern apps. Register now for a live demo.

Topics:
docker ,ibm ,websphere ,http server ,docker hub ,image

Published at DZone with permission of Kavi Suresh, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}