Configuring IZSME
After installing IBM Z Service Management Explorer, the next step is to configure it for your environment. You can add, edit, or delete a Tivoli Enterprise Portal Server (TEPS) for IZSME.
When you open IZSME for the first time, a window displays with a message that there is no Tivoli Enterprise Portal Server (TEPS) defined as the default server. You must configure at least one TEPS to use as the default server, and the TEPS must be running in order to use IZSME.
Adding a new TEPS to the list
- From the window that displays the No default TEPS is configured message, click on the Settings gear icon in the top right corner. The Settings screen will be displayed.
- Click the Add new button at the top of the screen. The Add Connection window is displayed.
- Specify values for the following fields. Note: Chinese characters are not supported in any of the fields in the configuration user interface. To connect IZSME to TEPS databases, Tivoli Data Warehouse, and LDAP servers, you will not be able to use Chinese characters for the following fields:
- Database schema name
- Administrator username and password for connecting to databases and LDAP servers
- DNS names for TEMS and other servers configured here
- Zowe authentication
- Specify whether or not Zowe authentication should be enabled. When Zowe authentication is enabled (the default), users will be authenticated against Zowe when they choose this configuration upon launching IZSME.
- TEMS properties – Host
- Specify the host name or IP address for this Tivoli Enterprise Monitoring Server (TEMS). This setting is the host name or IP address of the machine where the hub TEMS is installed.
- TEMS properties – Port
- Specify a numeric value for the port. The standard port value is 1918.
- Hot Standby TEMS Host (optional)
- This optional field allows you to specify a secondary High Availability TEMS host in case the primary TEMS is not available. If you wish to specify a secondary TEMS, specify the host name or IP address of the machine where the secondary TEMS is installed. If you do not want to specify a secondary High Availability TEMS, leave this field blank.
- Database properties – Host
- Specify the host name for this TEPS database.
- Database properties – Port
- Specify a numeric value for the port. The standard port value is 50000.
- Database properties – Username
- Specify the user ID of the person who has access to this database.
- Database properties – Password
- Specify the password associated with the Username.
- JDBC URL
- This URL is built for you automatically based on the values you specify in the other fields on
this screen. If you are using the default database name (TEPS), you do not need to change the URL.
However, if you are not using the default database name, you can change the URL to suit your
environment. Any changes made to the URL will be changed in the fields above vice versa.
Also, you may need to specify the currentSchema special register. For example, if the schema for TEPS tables is ITMUSER (and that is not the database username you entered), you would edit the JDBC URL as shown in this example:
jdbc:db2://myhost:50000/TEPS
Change to:
jdbc://myhost:50000/TEPS:currentSchema=ITMUSER;
Note: The JDBC URL must end with a semi-colon (;) or an error message will display.
- TEPS properties – Host
- Specify the host name or IP address for this Tivoli Enterprise Portal Server (TEPS). This setting is the host name or IP address of the machine where the TEPS is installed.
- TEPS properties – Port
- Specify a numeric value for the port.
- Click Test, on the right side of the Database properties section, to verify that these values are acceptable. If not, try a different value.
- Click Save to add this TEPS to the list.
Editing a TEPS configuration
- Click the Settings gear icon in the top right corner.
- On the Settings window, highlight the line you want to change.
- Click the kabob menu (three vertical dots) in the header bar. (You may need to page right to see the rest of the screen.)
- Click Edit.
- The Edit Connection window displays the current settings for this highlighted line.
- Change the values you need to adjust and click Save. If you do not want to make any changes, click Cancel.
Viewing a list of existing Tivoli Enterprise Portal Servers (TEPS)
To view a list of TEPS servers that have already been defined for IZSME, click the Settings gear icon in the top right corner. A star appears next to the first item on the list, indicating that this TEPS is the default server. All of the information in this window was provided when each of the TEPS was added to the list.
- Available – The connection is good.
- Error – No connection was made.
- Unknown – No connection has been attempted yet.
- Available – The connection is good.
- Error – No connection was made.
- Unknown – No connection has been attempted yet.
Configuring an LDAP connection
IZSME uses Lightweight Directory Access Protocol (LDAP) to connect to various directories. You can specify one LDAP connection for each TEPS:
- Click the Settings gear icon in the top right corner. You will see the Settings screen with several columns of data and the LDAP column on the far right side.
- Right-click anywhere in the LDAP column to see a list of options. Choose Configure LDAP.
- Turn on LDAP authentication by moving the slide to "On".
- Specify the LDAP Host.
- Specify a number for the LDAP Port. An example of the port number is 389.
- Specify the Username and Password for the Root directory.
- The Repository base entry distinguished name field is where all the values you have previously specified are listed as one long name. An example is listed under the entry field.
- Click Save. The Settings screen will indicate On for LDAP in the default TEPS database.
Configuring Java Sidecar
javaListenerPort
property in the
pluginConfig.json configuration file:{
"javaListenerPort": "20202",
"javaVMArguments": [],
"classPath": "../lib/jar/*",
"cache": {
[etc.]
The javaListenerPort
property specifies "the first of 20 ports the Java Sidecar
will try to listen on." So in the above example, the Java Sidecar will start with port 20202, and if
that port is not available, will continue with the next port, until it finds an available port, if
there is one in that group of 20 ports.
javaListenerPort
.Address space naming
By default, Java Sidecar will start with the same address space name as the App Server (Node.js
process). For example, if you accept the default ZOWE_PREFIX
(ZWE), both the App
Server and the Java sidecar would have the name ZWE1DS1
(for ZOWE_INSTANCE=1).
The Java Sidecar is started by the App Server process, so its name will always relate to the name of the App Server. If there are different values for ZOWE_PREFIX and ZOWE_INSTANCE, then App Server and Java Sidecar will have slightly different names. However, the root of the names will be the same (starting with ${ZOWE_PREFIX}${ZOWE_INSTANCE}. See Creating and configuring the Zowe instance directory for more information about Zowe naming.
Normal Login to IZSME
After you have configured a default TEPS, the login screen will appear the next time you start IZSME. The default database is listed under the Log in to IZSME heading. This is the TEPS database that you specified when configuring LDAP.- Logon ID
- Type the logon ID, such as a user ID, that was assigned to you to access IZSME.
- Password
- If a password is required for this logon ID, type the password here.