Load and run the Docker image to install Service Management Unite.
Before you begin
Before you install Service Management Unite by using the
Docker image, you must ensure that you have Docker installed on the server. Refer to the following
information to install Docker on Linux on System x or Linux on System z:
Note: It's highly recommended that you install Docker CE version 18.x.
Procedure
-
Download the SMU Docker archive depending on the architecture of your host system, for example
SMU_Enterprise_v1.1.6.0_Docker_Image_xLinux.tar for the SMU Docker image
running on xLinux (x86_64).
The SMU Docker archive is a compressed file. Run the command to extract the contained files
to a target
directory:
tar -xvf <SMU_Docker_archive.tar> --directory <target_dir>
Note: The
target directory must exist before tar can extract the files into it.
The
package contains the following files:
- An exported Docker image that includes all the prerequisite software and must be loaded into
your Docker environment: smu_image_v1160.tar
- The IBM SMU Docker Command Line Utility: A shell script with other necessary files that help you
to manage the SMU Docker image and perform common tasks like loading the Docker image or starting
and stopping the SMU Docker container.
This utility consists of the following files:
- eezdocker.sh: The key script that allows you to manage the Docker image and
container.
Run command
eezdocker.sh help for more details.
Note: The script must
be ran from a user who is allowed to use Docker, for example, root.
- eezdocker.cfg: A file that allows you to overwrite the default settings used
by eezdocker.sh. It must be in the same directory where
eezdocker.sh is located. If it doesn’t exist, eezdocker.sh
will use its default settings.
- util: A folder that contains utility files for the
eezdocker.sh script.
- A readme file with additional information about the SMU Docker image.
-
Edit file eezdocker.cfg if you want to change the default settings of
eezdocker.sh. For more information, see Customizing the SMU Docker Command Line Utility.
-
Use the IBM SMU Docker Command Line Utility to load the SMU Docker image into your Docker
environment by issuing the following command:
./eezdocker.sh load
To verify if the Docker image is loaded, issue command
eezdocker.sh status.
Sample output for checking the
status:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ IBM Service Management Unite Docker Command Line Utility +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Executing command status ...
Docker image smu_enterprise:1160 ---------------------------- Loaded.
Docker container smu_enterprise_1160 ------------------------ Not available.
Status of Docker container smu_enterprise_1160 -------------- Not started.
If
the load is successful, you can delete the smu_image.tar because it is not
needed anymore.
-
Use the IBM SMU Docker Command Line Utility to start the SMU Docker container by issuing the
following command:
./eezdocker.sh start
If you run this command for the first time, a new SMU
Docker container will be automatically created from the SMU Docker image.
The Tivoli Directory
Integrator server and WebSphere Application Server are automatically started when a Docker container
is started from the SMU Docker image.
Note: The Docker container is started with the Docker option
'–restart on-failure', which means it will be automatically restarted when the SMU Docker container
crashes or if the Docker runtime environment or the host system is restarted.
To verify if
the Docker container from the SMU Docker image is started, issue command eezdocker.sh
status.
Sample output for
eezdocker.sh
status:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ IBM Service Management Unite Docker Command Line Utility +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Executing command status ...
Docker image smu_enterprise:1160 ---------------------------- Loaded.
Docker container smu_enterprise_1160 ------------------------ Available.
Status of Docker container smu_enterprise_1160 -------------- Started.
Results
When the Docker container is successfully started, you can access the SMU dashboard via the
following URL:https://<hostname>:16311/ibm/console
The default SMU
administrative user ID and password are eezadmin
/eezadmin
.Note: It
might take up to 1 minute after the Docker container is started until all services are initialized
and available.
Access the WebSphere administrative console via the following
URL:
https://<hostname>:16316/ibm/console
The default WebSphere
Application Server administrative user ID and password are
wasadmin
/wasadmin
.You can use the WebSphere administrative
console to define more user IDs or change the password.
What to do next
Follow the steps to configure SMU to connect to backend systems:
- Define the functional user IDs that are used to connect to automation domains with the web configuration tool or the configuration tool
cfgsmu.
To start the GUI of
cfgsmu from within the
running Docker container, run the command:
eezdocker.sh cfgsmu
Note: The
command eezdocker.sh cfgsmu
tries to set the $DISPLAY variable
accordingly to point to the X Display server of your host system. If this command doesn't work as
expected, run the command xhost+local:all
before you run eezdocker.sh
cfgsmu to ensure that the Docker process can access the user's X session.
- Set up the IBM System Automation for z/OS (SA z/OS) E2E automation adapter to connect an SA z/OS
automation domain to SMU.
- Define the connection to the ITM Data Provider to get monitoring data from OMEGAMON agents.
For more information on how to configure SMU for your environment, refer to Configuring and administrating.