IBM Cloud App Management 2019.4.0 2019.4.0-IBM-ICAM-SERVER-IF0002 Readme

Below is a list of components, platforms, and file names that apply to this readme file.
 

Fix Download for Linux

Fix Download for Linux

• agentmgmt:  1.1.0-202001180234-005dac6
• alarmeventsrc:  1.0.1-202001171541-e37fa9d
• applicationmgmt: 1.3.1-202001201851-c148a08
• geolocation:  1.0.0-202001170243-3d3cf67
• ibm-hdm-metric-analytics-dev: 1.1.3
• metricprovider:   1.0.1-202001231740-729dad5
• metricsummarycreation: 1.0.1-202001151308-eb1de3e
• synthetic:  1.0.0-202001170727-6299924
• temacomm:  1.1.0-2020011715220c33b775
• temaconfig: 1.0.0-201912181737-afbad49
• temasda:  1.0.0-202001211513-cb6f12f 
• threshold:  1.0.0-202001200404-a472f46

• alarmeventsrc: 1.0.1-201912111512-843984e  (superceded by the newer version listed above)
• geolocation: 1.0.0-201912050329-d42c69c (superceded by the newer version listed above)
• ibm-cem: 2.5.0-20191212210439
• ibm-hdm-metric-analytics-dev: 1.0.29  (superceded by the newer version listed above)
• metricenrichment: 1.0.1-201912121857-a17e589
• temasda: 1.0.0-201912161959-4234f71  (superceded by the newer version listed above)

Note that the geolocation microservice was added to ICAM in an earlier Interim Fix. Also, Metric analytics remains a technical preview capability with this fix.

1. Go to the IBM Fix Central website and sign in. Using the root user, download the partial PPA file for IBM Cloud App Management 2019.4.0 IF0002 (2019.4.0-IBM-ICAM-SERVER-XLINUX-IF0002.tar.gz) to a temporary local directory on the computer where you installed IBM Cloud App Management.
2. Ensure you are logged in to the IBM Cloud Private cluster hosting your IBM Cloud App Management server. `cloudctl login -a $CLUSTER_ACCESS_URL --skip-ssl-validation`
   Where CLUSTER_ACCESS_URL is the IBM Cloud Private name you defined for your cluster, such as `https://<cluster_address>:8443`.
   If you did not specify a value, the default value is `https://mycluster.icp:8443`.
3. Identify the absolute path of the compressed fix pack and set to `FIX_PACK_ARCHIVE`; identify the target docker registry (set to `PRIVATE_REGISTRY`; The default value is `mycluster.icp:8500`)
4. Log in to the Docker private image registry:  `docker login MY_CLUSTER_CA_DOMAIN:8500`
   Where MY_CLUSTER_CA_DOMAIN is the certificate authority (CA) domain, such as `mycluster.icp`. If you did not specify a MY_CLUSTER_CA_DOMAIN, the default value is `mycluster.icp`.
5. Load the fix pack into the catalog: `cloudctl catalog load-archive --archive $FIX_PACK_ARCHIVE --registry $PRIVATE_REGISTRY`
6. Create or choose a directory for the new helm chart, set to `HELM_DIRECTORY`.
7. Extract only the helm chart from the fix package: `tar -C $HELM_DIRECTORY -xzvf $FIX_PACK_ARCHIVE charts`. The helm chart should now be at `$HELM_DIRECTORY/charts/`. Identify the name of the helm chart and set to `HELM_CHART` ($HELM_DIRECTORY/charts/ where HELM_DIRECTORY is an absolute path)
8. Go to a working directory for the helm upgrade. List the existing release `helm list --tls | grep ibm-cloud-appmgmt-prod` to get the release name, set to `RELEASE_NAME`.
9. Get the override values for the current release `helm get values $RELEASE_NAME --tls > $RELEASE_NAME-overrides.yaml`
10. Apply the fix using helm upgrade and the existing set of override values `helm upgrade $RELEASE_NAME $HELM_CHART --tls --values $RELEASE_NAME-overrides.yaml`
    
    Results:  'Release "$RELEASE_NAME" has been upgraded. Happy Helming!' followed by a block of text signifies a successful upgrade.
    You can watch the pods in the namespace where ICAM is deployed using `kubectl get pods --namespace $RELEASE_NAMESPACE` until all pods are ready. The duration is dependent on the environment.

1. Go to the IBM Fix Central website and sign in. Using the root user, download the partial PPA file for IBM Cloud App Management 2019.4.0 IF0002 (2019.4.0-IBM-ICAM-SERVER-XLINUX-IF0002.tar.gz) to a temporary local directory on the computer where you installed IBM Cloud App Management.
2. Ensure you are logged in to the IBM Cloud Private cluster hosting your IBM Cloud App Management server. `cloudctl login -a $MY_CLUSTER_URL --skip-ssl-validation`
   Where MY_CLUSTER_URL is the IBM Cloud Private name that you defined for your cluster such as `https://cluster_address:443`.
3. Identify the absolute path of the compressed fix pack and set to `FIX_PACK_ARCHIVE`.
4. Identify the namespace where the Cloud App Management server is installed and set `RELEASE_NAMESPACE` to this value.  Note, Cloud App Management with IBM Cloud Pak for Multicloud Management must be installed in the `kube-system` namespace.
5. As an OpenShift administrator, log in to the OpenShift Container Platform. `oc login`
6. Log in to the Docker registry. `docker login $(oc registry info) -u $(oc whoami) -p $(oc whoami -t)`
7. Load the fix pack into the catalog: `cloudctl catalog load-archive --archive $FIX_PACK_ARCHIVE --registry $(oc registry info)/$RELEASE_NAMESPACE`
8. Create or choose a directory for the new helm chart, set to `HELM_DIRECTORY`.
9. Extract only the helm chart from the fix package: `tar -C $HELM_DIRECTORY -xzvf $FIX_PACK_ARCHIVE charts`. The helm chart should now be at `$HELM_DIRECTORY/charts/`. Identify the name of the helm chart and set to `HELM_CHART` ($HELM_DIRECTORY/charts/ where HELM_DIRECTORY is an absolute path)
10. Go to a working directory for the helm upgrade. List the existing release `helm list --tls | grep ibm-cloud-appmgmt-prod` to get the release name, set to `RELEASE_NAME`.
11. Get the override values for the current release. `helm get values $RELEASE_NAME --tls > $RELEASE_NAME-overrides.yaml`
12. Apply the fix using helm upgrade and the existing set of override values `helm upgrade $RELEASE_NAME $HELM_CHART --tls --values $RELEASE_NAME-overrides.yaml`
    
    Results: 'Release "$RELEASE_NAME" has been upgraded. Happy Helming!' followed by a block of text signifies a successful upgrade.
    You can watch the pods in the namespace where ICAM is deployed using `kubectl get pods --namespace $RELEASE_NAMESPACE` until all pods are ready. The duration is dependent on the environment.

Performing the necessary tasks after installation

Steps to take after installation

If you intend to use the "Transaction Tracking for selected TEMA-based agents" capability, be aware that the WebSphere Application Server agent will need to be upgraded and a co-requisite TEMA patch applied to enable the capability end to end. 

The required TEMA patch will be installed when the WebSphere Application Server agent is upgraded.   It also can be separately downloaded here: 

TEMA Patch Download

The new version of the WebSphere Application Server agent was delivered as part of a recently published agent fixpack, IBM Cloud App Management V2019.4.0.1 Agents.  The part numbers that need to be downloaded can be found in the IBM Cloud App Management Knowledge Center at this link:

Part numbers for ICAM Agents fixpack

If you did not install any prior Interim Fix for 2019.4.0, you may wish to learn more about "Geolocation in Digital Experience Monitoring".  Please see this guide:
https://www.ibm.com/support/knowledgecenter/SS8G7U_19.4.0/com.ibm.app.mgmt.doc/content/overview_whatsnew.html

Additional information

The Secure Hash Algorithm 1 (SHA1) checksum of the image is as follows:

• HASH UPDATES NEEDED HERE
• 2019.4.0-IBM-ICAM-SERVER-XLINUX-IF0002.tar.gz  (a81fda38f756c35e31cc231e6f6a6f73b98e3476)
• 2019.4.0-IBM-ICAM-SERVER-PPC64LE-IF0002.tar.gz (00709901450710bfead8c8bc8ebc5a112fc3bd7d)

(Note that due to internal issue tracking changes, some issue numbers have 4 digits and some have 5 digits.)

Issues

• 1200  Add Transaction Tracking support for selected TEMA-based monitoring agents
• 1918  Liberty PSIRT PVR0146209/ADV0016859
• 12750  Metric summarization: should run daily aggregations against the hourly summaries instead of the raw data
• 1833  WAS threshold can't drill down to WAS application resource dashboard
• 1805  Performance:  remove timestamp attributes that change frequently from subscription for selected agents