Sign inSign up

ibmcom/xsld

By ibmcom

•Updated over 5 years ago

IBM WebSphere eXtreme Scale Liberty Deployment (XSLD) 8.6.1.5

Image
10

50K+

ibmcom/xsld repository overview

Image of IBM Logo

⁠What is WebSphere eXtreme Scale Liberty Deployment?

The 'WebSphere® eXtreme Scale Liberty Deployment (XSLD)' is a distributed in-memory cache feature. It provides Liberty caching servers, caching operation tools, an administration console, and the out-of-the-box REST administration services based on the latest industry standards and specifications. XSLD is built based on the core IBM WebSphere eXtreme Scale technology.

Some of the main highlights of XSLD are:

  • An easy-to-deploy, easy-to-configure distributed caching solution based on eXtreme Scale technology
  • The latest IBM Liberty technology;
  • Simple and easy to use administrative console.
  • Out-of-the-box administrative REST API and caching operational REST API in order to scale your caching environment up or down through the console or with REST APIs.
  • Full customization to support all eXtreme Scale caching use cases
  • Easily configurable and integrates within your caching environment in minutes via the out-of-the-box scripts and tools
  • JCACHE (JSR107) support

See (http://www.ibm.com/support/knowledgecenter/SSTVLU_8.6.1/com.ibm.websphere.extremescale.doc/cxsgetstartxsld.html⁠) for more details.

⁠License

XSLD Docker release is licensed under the IBM International License Agreement for Try and Buy Programs. This license for XSLD Try and Buy can be found online⁠. Note that this license does not permit further distribution.

To learn more and order, contact your Americas Call Centers, local IBM representative, or your IBM Business Partner. To identify your representative or partner call 800-426-4968. For more information, contact the Americas Call Centers. Phone: 800-IBM-CALL (426-2255) Fax: 800-2IBM-FAX (242-6329)

⁠Supported tags
  • latest (8.6.1.3 including APAR PH08443 and all previous APARs)
  • 8613
  • 8612
  • 8611
  • 8610
⁠Set up Docker environment

Instructions to set up Docker engine (https://docs.docker.com/engine/installation/⁠) After the Docker engine is set up, run docker login to logon to your Docker Hub user account from your Docker engine.

⁠How to use this image:

This docker image has to be deployed to Docker Engine on one of supported Cloud providers or your own system. The instructions for creating Docker Engine⁠ vary by Cloud provider.

In order to use the image, it is necessary to accept the terms of the XSLD license. This is achieved by specifying the environment variable LICENSE equal to accept when running the image.

1 - Create a docker volume to store XSLD persistent data for the container

docker volume create --name vol-xsld

2 - Start an XSLD container

docker run -e LICENSE=accept -itd --net=host --volume vol-xsld:/vol  --name xsld-1 ibmcom/xsld:latest  cg1 m1 1 s3cretKey! xsadmin4Me!

 Input Parameters: [cacheGroup]  [memberName]  [capacity] 
                   [secret_key]  [adminPassword]
    - cacheMemberGroup is the name of the cache member group 
      to be deployed. e.g. cg1
    - memberName is the name of the cache member  added. 
      for example: m1
    - capacity is the total number of memory (in GB) to be 
      allocated for XSLD instance. for example: 1
    - secret_key is the cache member group secret_key used to 
      manage the cache member group  
    - xsadminPassword is the password for the xsadmin user

 Environment Variables: The above input commands can also be entered as environment 
      variables using the -e option
    - CACHE_GROUP is the name of the cache member group 
      to be deployed. e.g. -e CACHE_GROUP=cg1
    - MEMBER_NAME is the name of the cache member  added. 
      for example: -e MEMBER_NAME=m1
    - MEMBER_CAP is the total number of memory (in GB) to be 
      allocated for XSLD instance. e.g. -e MEMBER_CAP=1
    - SECRET_KEY is the cache member group secret_key used to 
      manage the cache member group. e.g. -e SECRET_KEY=s3cretKey!
    - XSADMIN_PWD is the password for the xsadmin user. e.g. -e XSADMIN_PWD=xsadmin4Me!
  
   **Note**: The password and secret key must contain at least
             one number[0-9], one upper case character[A-Z], 
             one special character[~!@#$%^&*()_-+=:;'[]{}|<>,.?/] 
             and be at least 10 characters

   If the container failed to start due to invalid parameters passed in 
   (e.g. invalid password rule),  you may need to run the following docker 
   command in order to remove the XSLD container that was just created
   and then re-run this step again:    "docker rm xsld-1"
  • By specifying -e LICENSE=accept parameter, you are accepting this License⁠ to use the software contained in this image.

3 - Monitor the container output using the docker logs command until the following line is outputted "XSLD Nanny Watchdog started, please monitor the logs at /opt/ibm/WebSphere/eXtremeScale/wlp/startscripts/nanny/log/nanny.log"

docker logs -f xsld-1

4 - Monitor the Watchdog log until all servers are started

docker exec -it xsld-1 tail -f /opt/ibm/WebSphere/eXtremeScale/wlp/startscripts/nanny/log/nanny.log

After all servers are started, XSLD is ready to use. You can access the XSLD dashboard at https://:9443 Note: logon using xsadmin and the xsadmin password specified earlier.

NOTE "Docker for Mac" user, use the following command when running step 2 above to start your XSLD container:

docker run -e LICENSE=accept -itd -p 1099-1110:1099-1110 -p 9443-9445:9443-9445 -p 6601-6603:6601-6603 -p 4809-4821:4809-4821 --volume vol-xsld:/vol --name xsld-1 ibmcom/xsld:latest cg1 m1 1 s3cretKey! xsadmin4Me!

When launching XSLD console, use the machine's address as the URL: https://<public_address>:9443

⁠Documentation & Other Information
⁠Upgrade XSLD

XSLD image uses Docker volume to keep the persistent data needed for support upgrade. To upgrade to the latest XSLD image without losing your current XSLD persisted data, do the following:

1 - Use Docker Pull Command to get the latest XSLD upgrade image from this web site to your Docker engine

2 - Stop XSLD container

  docker stop xsld-1

3 - Remove XSLD container

  docker rm -f xsld-1

4 - Start the container with the latest XSLD image

docker run -e LICENSE=accept -itd --net=host --volume vol-xsld:/vol  --name xsld-1 ibmcom/xsld:latest

5 - Monitor the container output using the docker logs command until the following line is outputted "XSLD Nanny Watchdog started, please monitor the logs at /opt/ibm/WebSphere/eXtremeScale/wlp/startscripts/nanny/log/nanny.log"

docker logs -f xsld-1

6 - Monitor the Watchdog log until all servers are started

docker exec -it xsld-1 tail -f /opt/ibm/WebSphere/eXtremeScale/wlp/startscripts/nanny/log/nanny.log

After all servers are started, XSLD instance is upgraded and is ready to be used again. You can access the XSLD dashboard at https://:9443

⁠Uninstall XSLD

If you no longer need the XSLD container, you can follow the steps below to uninstall XSLD:

1 - Stop XSLD container

  docker stop xsld-1

2 - Remove XSLD container

  docker rm xsld-1

3 - Remove XSLD volume

  docker volume rm vol-xsld

Tag summary

Content type

Image

Digest

Size

542.5 MB

Last updated

over 5 years ago

docker pull ibmcom/xsld