DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • How to Keep AI Agents From Going Rogue Using Docker Sandbox
  • When One Docker Swarm Replica Became Unreachable Over an Overlay Network: A Production Case With Traefik
  • Docker Sandboxes Beyond the Laptop: Running AI Agents in the Cloud
  • Understand the Sidecar Pattern by Deploying n8n to AWS Fargate

Trending

  • When One Docker Swarm Replica Became Unreachable Over an Overlay Network: A Production Case With Traefik
  • Event-Driven AI Systems With Kafka and Autonomous Agents
  • Idempotency Under Concurrency: Why Your Application Check Isn't the Last Line of Defense
  • Build Software Faster With Three Simple Principles

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Software Design and Architecture
  3. Cloud Architecture
  4. WebSphere Traditional and IBM HTTP Server on Docker Hub

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.

By 
Kavi Suresh
·
Jun. 17, 16 · Tutorial
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
11.4K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

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 3FROM 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 3FROM 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.

Docker (software)

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

Opinions expressed by DZone contributors are their own.

Related

  • How to Keep AI Agents From Going Rogue Using Docker Sandbox
  • When One Docker Swarm Replica Became Unreachable Over an Overlay Network: A Production Case With Traefik
  • Docker Sandboxes Beyond the Laptop: Running AI Agents in the Cloud
  • Understand the Sidecar Pattern by Deploying n8n to AWS Fargate

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook