Installing and configuring Grafana _ Monitoring

 

Procedure

1. In the Red Hat OpenShift Container Platform console, select Operators > OperatorHub and search for the Grafana operator that is provided by Red Hat OpenShift.
2. Install the Grafana operator for the openshift-user-workload-monitoring namespace.
3. Create an instance of Grafana.
   1. Select Operator > OperatorHub > Grafana Operator and then select the Grafana tab.
   2. Click Create Grafana.
   3. On YAML tab, enter the following text:

      apiVersion: integreatly.org/v1alpha1
      kind: Grafana
      metadata:
        name: mas-grafana
        namespace: openshift-user-workload-monitoring
      spec:
        ingress:
          enabled: true
        dataStorage:
          accessModes:
            - ReadWriteOnce
          size: 10Gi
          class: ocs-storagecluster-cephfs
        config:
          log:
            mode: "console"
            level: "warn"
          security:
            admin_user: "root"
            admin_password: "secret"
          auth:
            disable_login_form: False
            disable_signout_menu: True
          auth.anonymous:
            enabled: True
        dashboardLabelSelector:
          - matchExpressions:
              - {key: app, operator: In, values: [grafana]}
      

      A route is created, and the public URL is included in that route definition in the openshift-user-workload-monitoring namespace project.
4. Remember to update the subscription.yaml file and add the following configuration so that Grafana scans for the dashboard across the whole cluster:

   Config:
          env: 
          - name: "DASHBOARD_NAMESPACES_ALL" 
             value: "true"

   After an update, the subscription.yaml file looks like the following:

   apiVersion: operators.coreos.com/v1alpha1
           kind: Subscription
           metadata:
             name: grafana-operator
             namespace: "{{ grafana_namespace }}"
             labels:
               operators.coreos.com/grafana-operator.{{ grafana_namespace }}: ''
           spec:
             channel: v4
             installPlanApproval: Automatic
             name: grafana-operator
             source: community-operators
             sourceNamespace: openshift-marketplace
             config:
               env:
                 - name: "DASHBOARD_NAMESPACES_ALL"
                   value: "true"

5. Run the following command to grant the user permission.

   oc adm policy add-cluster-role-to-user cluster-monitoring-view -z grafana-serviceaccount

6. Run the following command to obtain the BEARER_TOKEN.

   - oc serviceaccounts get-token grafana-serviceaccount -n openshift-user-workload-monitoring

7. Create the GrafanaDataSource, which points to the Prometheus instance that you installed earlier.
1. Select the Grafana Operator > Installed operators > GrafanaDataSource tab.
2. Enter the following text and replace the ${BEARER_TOKEN} value with the value that you obtained in a previous step.

   apiVersion: integreatly.org/v1alpha1
   kind: GrafanaDataSource
   metadata:
     name: prometheus-grafanadatasource
     namespace:  openshift-user-workload-monitoring
   spec:
     datasources:
       - access: proxy
         editable: true
         isDefault: true
         jsonData:
           httpHeaderName1: 'Authorization'
           timeInterval: 5s
           tlsSkipVerify: true
         name: Prometheus
         secureJsonData:
           httpHeaderValue1: 'Bearer ${BEARER_TOKEN}'
         type: prometheus
         url: 'https://thanos-querier.openshift-monitoring.svc.cluster.local:9091'
     name: prometheus-grafanadatasource.yaml

Reference Link : https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=dashboards-installing-configuring-grafana

MAS Manage - Adding trusted certificates in the user interface

Add certificates through the user interface when you configure Maximo Manage Maximo Health for deployment. The format of the certificate must be PEM.

Procedure

• Add certificates.
1. Log in to IBM Maximo Application Suite as a system administrator.
2. From Suite administration, select Workspaces from the side navigation menu and then select the workspace that you want to configure.
3. On the Overview tab for the workspace, select the Manage tile.
4. On the Manage panel, click Actions and select Update configuration.
5. In the Imported certificates row on the Update Manage configuration window, click the Edit icon.
6. In the Imported certifications section, click Add to add a certificate.

You might have to disable the System managed switch before you can add a certificate.

7. Specify the certificate alias and copy and paste the contents of the certificate.

Each alias name must be unique within the workspace.

8. Click Confirm to save your changes.
9. Select one of the following options:
• If you are configuring a new deployment, click Activate.
• If you are updating a deployment, click Apply changes.
• Add certificates.
1. In IBM Maximo Application Suite click Administration and then click Catalog.
2. Select the Manage tile.
3. On the application details page, click Actions and select Update configuration.
4. In the Imported certificates row on the Update Manage configuration window, click the Edit icon.
5. In the Imported certifications section, click Add to add a certificate.

You might have to disable the System managed switch before you can add a certificate.

6. Specify the certificate alias and copy and paste the contents of the certificate.

Each alias name must be unique within the workspace.

7. Click Confirm to save your changes.
8. Select one of the following options:
• If you are configuring a new deployment, click Activate.
• If you are updating a deployment, click Apply changes.

Reference Link : https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=administering-trusted-certificates

How to import attachments into MAXIMO using MIF

 How to upload file using MIF (Maximo Integration Framework)?

1. Create Object Structure.

You have two scenarios:

1. Send only the attachment using table DOCLINKS.
2. Send the attachment owner with DOCLINKS table, like WORKORDER,SR, ITEM, etc. To know if the desired table is supported, a tip is execute query below:

select parent from maxrelationship where child = 'DOCLINKS';

Observation: You can also create an Enterprise Service, but in this example, we will use only Object Structure.

 

2. Create Web Service.

I am not going to enter in every detail of Web Service creation. You just need to create and deploy Web Service. You can do that using Web Services Library application.

3. Submit the XML.

You can use any tool to submit XML into Web Service. I usually use SoapUI, it’s simple and easy to use.

https://www.soapui.org/
 

The XML below is just a sample having the required attributes.

XML:

1. Scenario 01: In this scenario you are going to upload the file to the server into doclinks folder. (In my case C:\doclinks\attachments)

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/&quot; xmlns:max="http://www.ibm.com/maximo"&gt;    <soapenv:Header/>    <soapenv:Body>       <max:SyncMXDOCLINK>          <max:MXDOCLINKSet>               <max:SR action="AddChange">                <max:DESCRIPTION >Test 01 SR description</max:DESCRIPTION>                 <max:ORGID>EAGLENA</max:ORGID>                 <max:SITEID>BEDFORD</max:SITEID>                  <max:DOCLINKS>                   <max:ADDINFO>1</max:ADDINFO>                   <max:COPYLINKTOWO>0</max:COPYLINKTOWO>                   <max:DESCRIPTION>Example of Attach </max:DESCRIPTION>                   <max:DOCTYPE>Attachments</max:DOCTYPE>                   <max:DOCUMENT>Test 01</max:DOCUMENT>                   <max:DOCUMENTDATA>MTIzMTMyMzE=</max:DOCUMENTDATA>                   <max:OWNERTABLE>SR</max:OWNERTABLE>                   <max:UPLOAD>1</max:UPLOAD>                   <max:URLNAME>C:\DOCLINKS\ATTACHMENTS\testfile01.txt</max:URLNAME>                   <max:URLTYPE>FILE</max:URLTYPE>                </max:DOCLINKS>             </max:SR>          </max:MXDOCLINKSet>       </max:SyncMXDOCLINK>    </soapenv:Body> </soapenv:Envelope>

 

Reference Link : https://www.ibm.com/support/pages/how-import-attachments-maximo-using-mif 

 

IBM MAS - Getting the Manage admin Docker image

 Getting the Manage admin Docker image:

Prerequisites for this activity. Use the following steps to install Docker.

1.       Install Docker from https://docs.docker.com.

2.       Make sure that the docker daemon is running.

Procedure

1)         In your Linux® terminal, run the oc login command.

$ oc login --token=sha256~yLcd9N_ih1UX7tGcq9REywmoliEGvK4R-rtDu_xxxxx --server=https://api.mas-app-sb123.cp.fyre.ibm.com:6443

2)      Expose the internal registry to external using Route.

$ oc patch configs.imageregistry.operator.openshift.io/cluster --patch '{"spec":{"defaultRoute":true}}' --type=merge

3)      Verify the internal registry route hostname.

$ oc get route -n openshift-image-registry

NAME            HOST/PORT         PATH  SERVICES        PORT      TERMINATION      WILDCARD

default-route   default-route-openshift-image-registry.apps.mas-app-sb1.cp.fyre.ibm.com         image-registry  all       reencrypt        None

image-registry  image-registry.openshift-image-registry.svc        image-registry  5000-tcp  reencrypt        None

4)      Log in by using the default registry route hostname.

docker login -u <user_name> -p $(oc whoami -t) default-route-openshift-image-registry.apps.<clustername>.<basedomain>

$ sudo docker login -u kubeadmin -p $(oc whoami -t) https://default-route-openshift-image-registry.apps.mas-app-sb123.cp.fyre.ibm.com

Remember: If you get x509: certificate signed by unknown authority error message, then you must place the Router trusted CA on your host.

5)      Extract the CA from Red Hat® OpenShift® Container Platform cluster, where the registry is configured.

$ oc extract secret/router-ca --keys=tls.crt -n openshift-ingress-operator

6)      Perform on the node, where the image pulling throws x509 error.

$ sudo cp tls.crt /usr/local/share/ca-certificates/.

$ sudo update-ca-certificates

7)      Make sure that the docker daemon is running.

$ ps -aux | grep dockerd

root       203  0.0  0.0  10508  4232 pts/0    T    01:28   0:00 sudo dockerd

root      2397  0.0  0.0  11016  4612 pts/1    S    16:49   0:00 sudo dockerd

root      2398  0.0  0.4 1538160 111260 pts/1  Sl   16:49   0:07 dockerd

sarika    3999  0.0  0.0   8160   724 pts/1    S+   23:26   0:00 grep --color=auto dockerd

 8)      Pull admin docker latest image: docker pull <Public image Repository> From the Manage project in OpenShift console, get the Public Image Repository value from the <instanceid>-<workspaceid>-admin in ImageStreams under Builds.

$ sudo docker pull `default-route-openshift-image-registry.apps.mas-app-sb1.cp.fyre.ibm.com/mas-sb1-manage/sb1-masdev-admin`

 9)      Get Image ID: docker images

$ sudo docker images

REPOSITORY                                       TAG      IMAGE ID      CREATED      SIZE

default-route-openshift-image-registry.apps.mas-app-sb1.cp.fyre.ibm.com/mas-sb1-manage/sb1-masdev-admin  latest   c0e655398e6b  3 weeks ago  7.87GB

 10)   Run the docker pulled admin image docker run -d <image id>.

$ sudo docker run -d c0e655398e6b

1f2dfad8d3c813792798dc1f220bf27b7935f604c4817f47346a1f96e2336a92

time="2021-06-26T16:54:46.067182200-04:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/1f2dfad8d3c813792798dc1f220bf27b7935f604c4817f47346a1f96e2336a92 pid=2832

 11)   Get the container ID for the pulled admin image. docker ps -a

$ sudo docker images

REPOSITORY                  TAG      IMAGE ID      CREATED      SIZE

default-route-openshift-image-registry.apps.mas-app-sb1.cp.fyre.ibm.com/mas-sb1-manage/sb1-masdev-admin  latest   c0e655398e6b  3 weeks ago  7.87GB

12)   Copy the Manage code locally.

$ sudo docker cp d3544a11901e:/opt/IBM/SMP/maximo/latest.zip /mnt/c/temp/.

13)   Optional: Run tools such as integrity checker.

docker exec -it <container id> /bin/bash

Update the Maximo properties in /opt/IBM/SMP/maxio/applications/maximo/propertiesfolder.

Execute /opt/IBM/SMP/maxio/applications/maximo/validate_integ.sh.

Reference Link : https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=preparing-getting-manage-admin-docker-image

Applying Customization Archive into IBM Maximo Manage

 Reference Link :https://www.ibm.com/support/pages/applying-customization-archive-ibm-maximo-manage

User Management in Maximo Application Suite

The latest version of MAS 8.8/Manage 8.4, the user creation process has been modified, and to alleviate any unnecessary confusion, I’m going to show what you need to know and walk you through this new process.

One change effective with MAS 8.8 and above is that a display name and a User ID are created when a user is created in MAS. The User ID is a primary key that identifies a user, and it cannot be changed after the user is created.

Reference Link : https://www.ibm.com/support/pages/user-management-maximo-application-suite

IBM Cloud Pak for Integration documentation - Reference Link

 https://www.ibm.com/docs/en/cloud-paks/cp-integration

Red Hat OpenShift Container Platform Support

IBM Maximo Application Suite will run anywhere that you can run a supported Open Shift release on AMD64 architecture.

CP		General Availability	End of Support	Supported MAS Releases
4.10		March 10, 2022	September 10, 2023	8.9 - 8.10
4.111		August 10, 2022	February 10, 2024	8.9 - 8.10
4.12		January 17, 2023	January 17, 2025	8.9 - 8.10

Cloud Pak for Data covers the following application's dependencies:

• Assist: Watson Discovery, Watson Text to Speak, Watson Speach to Text, Watson Assistant
• Health & Predict Utilities: Watson Studio
• Predict: Watson Studio, Watson Machine Learning, Watson Analytics Service, Watson Openscale

OCP		Cloud Pak for Data				Supported MAS Releases
		Release	General Availability	End of Support
4.10		4.6.3	February, 2023	TBD		8.9 - 8.10

Reference Link : 

https://access.redhat.com/support/policy/updates/openshift/