Start of change

Deploying IBM Text Search for Db2 for z/OS as Docker images

You can deploy Docker images to install IBM Text Search for Db2 for z/OS servers.

Before you begin

Ensure that your systems meet the requirements. For more information, see System requirements for enabling text search support and System requirements for installing a text search server.

Docker Engine must be installed on the server where you plan to deploy the text search server for IBM Text Search for Db2 for z/OS.

About this task

You can install a text search server with the Docker images on the following platforms (64-bit only):
  • SLES 12.4
  • Redhat 7.4
  • zLinux Redhat 7.6
  • Windows 10
Tip: Ensure that the text search server automatically starts each time that the operating system reboots by installing the text search server as a service. In service mode, the silent installation includes the scripts for starting and stopping the text search server as part of the operating system's start up and shutdown processes. To install a text search server as a service, the user ID installing the product must be a root user on the Linux® or Linux on IBM Z® server, or an administrator on the Windows server. If a user ID without the correct access installs a text search server, you can use the start and stop scripts each time that you want to start or stop the server.

Procedure

  1. Download the Docker image from IBM Text Search for Db2 for z/OS downloads.
    The following table shows the file names of the Docker images for the supported server platforms.
    Table 1. IBM Text Search for Db2 for z/OS Docker images by platform
    Server platform (64-bit only) File name
    zLinux Rehat 7.6 tsserver_v2_linux.tar
    Linux, including SLES 12.4 and Redhat 7.4 tsserver_v2_zlinux.tar
    Windows 10 tsserver_v2_windows.tar
  2. Open a command window, go to the download folder, and run the following commands.
    # docker load -i  tsserver_v2_platform.tar
    # docker run -d -p 9003:9003 tsserver:v2
    # docker ps
    The output contains the CONTAINER ID value.
    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES
    6fa66d5e8fdb        tsserver:v2         "/bin/sh -c 'bin/s..."            11 days ago         Up 11 days          9003/tcp   
    
  3. Run the following commands to get the configuration information, whether container-id is the CONTAINER ID.
     # docker logs container-id
    The result is similar to the following output.
    WARNING: The number of files per process value was not set to unlimited or to 65536 as required. The startup script changed this value to 65536.
    IQQG0337I The server started successfully. The server is listening on port 9003.
    The authentication token is printed below. This token is used to communicate with the server. Store the token if applicable.
    EPhhaz0=
    The encryption key is printed below. This key is used to encrypt the password during text index backup and restore operations. Store the key if applicable.
    EPhhaz2txoqZbGLjTb7Vfg==
    
    Tip: Start of changeSave the authentication token and encryption key returned in the message for use later when you populate the text search administration tables. For more information, see Populating the text search administration tables for Db2 for z/OS.End of change
Start of change

What to do next

Configure the text search server and Db2 for z/OS by completing the following tasks:

  1. Configure the IBM Text Search for Db2 for z/OS server.
  2. Start the text search server.
  3. Enable Db2 for z/OS for text search.
End of change
End of change