Update runtime environment to use HTTP

Update your runtime environment to use HTTP or to use an HTTP port other than the default.

Before you begin

Important:

With APAR OA64188, HTTPS is the default communication protocol for new runtime environments. For existing runtime environments, if you do not make the necessary manual configuration updates after applying the APAR, HTTPS will be the default protocol using the default HTTPS port number 3661.

To use HTTP, you must have parameter RTE_TEMS_TRANSPORT_MODE set to value HTTP in either RTEDEF(rte_name) for Configuration Manager or WCONFIG(rte_name) for PARMGEN before running the Configuration Manager GENERATE action or the PARMGEN $PARSE job, respectively, as described in this procedure.

About this task

Perform this task to specify HTTPs as the communication protocol to use between the Tivoli Enterprise Monitoring Server (TEMS) and other components, such as the SOAP server, the IBM Tivoli Monitoring Service Console, the tacmd CLI, and TEMS REST services.

To use the HTTP protocol, you must add the RTE_TEMS_TRANSPORT_MODE parameter with HTTP value as described by this procedure. Otherwise, HTTPS will be the protocol by default, which could impact your environment if AT-TLS is not fully set up.

You will use the following parameters when configuring your runtime environment to use HTTP:

For the TEMS:

Procedure

Add (or update) the parameters, as follows:
- Using Configuration Manager:
  For the TEMS:
  Add the following parameter to RTEDEF(rte_name):
```
RTE_TEMS_TRANSPORT_MODE    "HTTP"
```
  Add the following parameter to RTEDEF(KDS$PARM), RTEDEF(KDS$lpar), or both:
```
KDS_TEMS_HTTP_PORT_NUM    http_port_num
```
- Using PARMGEN:
  For the TEMS:
  Add the following parameters to WCONFIG(rte_name):
```
RTE_TEMS_TRANSPORT_MODE    "HTTP"
KDS_TEMS_HTTP_PORT_NUM    http_port_num
```
Refresh your runtime environment, as follows:
- Using Configuration Manager: Use the GENERATE action to re-create the runtime environment. Optionally, you can use the GENERATE action with the QUICKCONFIG or NOUSS options.
- Using PARMGEN: Recreate the runtime environment as described in Scenario RTE03: Changing parameters in an RTE.

Start your OMEGAMON started tasks. You should see the following messages in the log:

For the TEMS:

KDE_TRANSPORT=KDC_FAMILIES="HTTP:http_port_num USE:Y <...> " 

listening: ip.tcp.http:35646
listening: ip.tcp.http:1920

Test your HTTP connection using the following methods:
- If you have tacmd configured, issue tacmd commands using your TEMS IP or DNS and the HTTP port number. For example:
```
C:\Users\userID>tacmd login -s ip:http_port_num 
 Username? tso_user_id 
 Password? 

Validating user... 
KUIC00007I: User tso_user_id logged into server on http://ip:http_port_num 
KUIC00008W: The connection you are using is not secure. 
```
- Access the Service Console using http://ip:http_port_num. If the connection is successful, then the Service Console items will be displayed.
- Attempt to access the Service Console using https://. This attempt should fail.