How to reinstall the OC robot wasp probe manually
search cancel

How to reinstall the OC robot wasp probe manually

book

Article ID: 279674

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Sometimes it is necessary to reinstall wasp on the Operator Console. This KB Article contains the steps to do so. 

This process has been tested and shown to be successful in a lab environment as well as several customer environments.

Sometimes the wasp probe doesn't start after an upgrade is completed and turns red.

Possible causes/symptoms

  • Error-> Controller: Max. restarts reached for probe 'wasp' (command = <startup java>)

  • The data_engine parameter and value may not be configured with the data_engine NimBUS address in the wasp.cfg

  • wasp ump_common section in the wasp.cfg may not be fully updated/configured

  • certificate.pem is corrupt and needs to be re-copied over from the Primary hub to the OC Robot and referenced by the cryptkey parameter in the robot.cfg.

  • There is an old/deprecated webapp in the wasp.cfg, e.g., umpjslib

  • Interference from Anti-virus

  • Wrong/old java_jre version

  • A child container failed to start:
    Error-> Caused by: java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: A child container failed during start.

    Note that if the wasp log shows a child container error, e.g., for a deprecated webapp such as umpjslib, either deactivate the webapp or delete it from the wasp.cfg. Then click Ok. Deactivate, then Activate wasp.

  • Wasp remains green, but cannot obtain an IP and port and PID recycles in a loop every 5 minutes.

Environment

  • DX UIM 20.4, 23.4

Cause

  • wasp probe is red, and not running. Or Wasp doesn't start completely.

Resolution

wasp - manual installation process

1. Deactivate wasp

2. Save off the wasp folder for safekeeping on the OC Robot.

3. Delete the current wasp folder from the file system on the OC Robot

    Note that the OC Robot you use must sit directly under the Primary hub AND it must be on the same network subnet.

    Installing an Operator Console instance on a robot that reports to a Secondary hub is NOT supported.

4. Using IM, distribute the required Operator Console (OC) server packages from the local Archive on the Primary hub to the OC robot in the order listed below.

5. Ensure that you drag each of the ump_portletname packages that are required for your environment from the local Archive.

    If you need to gather up all of the packages you need because you are missing one or more packages for a particular cumulative update (CU#), go to this page:

DX Unified Infrastructure Management - Cumulative Updates & Patches

6. Then choose the OC version CU number you're trying to install from scratch, for example, -> "Operator Console 20.4 - Cumulative Update 5" to see if there are any packages you need for this CU, e.g., java_jre version, patches/hotfixes etc. The required package, e.g., wasp 20.4.7 for DX UIM 20.4.7, or wasp 23.4 for DX UIM 23.4, etc...

7. Deploy the required wasp/webapp packages from the local Primary hub archive to the OC Robot.

- java_jre
- wasp
- wasp_service_wrapper
- nisapi_wasp
- ump
- ump_slm
- ump_operatorconsole
- wasp_alarmviewer_api
- policy_management_ws
- mcsuiapp_portlet
- ump_cabi
- ump_accountadmin
- ump_dashboard
- uim_listdesigner
- uim_reportscheduler
- uim-custom-pages-portlet (23.4 or higher)

7. Configure the data_engine address

Configure the wasp probe to use the correct data_engine probe address from the Primary Hub, for example, under the setup section set the data_engine to /<uim_domain>/<uim_hub>/<uim_robot>/data_engine> otherwise wasp will not start as it cannot get the data_engine connection string.

8. Configure the wasp-> ump_common section

Use Raw Configure mode to modify the <ump_common> section of the wasp configuration to specify the following probe addresses:
Here is a simple example:

<ump_common>
    maintenance_mode = /<uim_domain>/<uim_hub>/<uim_robot>/maintenance_mode
    ems = /<uim_domain>/<uim_hub>/<uim_robot>/ems
    nas = /<uim_domain>/<uim_hub>/<uim_robot>/nas
    mcs_ui_app_url = /mcs-ui-app/
    automated_deployment_engine = /<uim_domain>/<uim_hub>/<uim_robot>/automated_deployment_engine
    discovery_server = /<uim_domain>/<uim_hub>/<uim_robot>/discovery_server
    mpse = /<uim_domain>/<uim_hub>/<uim_robot>/mpse
    lists_use_java_cache = false
    sla_engine = /<uim_domain>/<uim_hub>/<uim_robot>/sla_engine
    udm_manager = /<uim_domain>/<uim_hub>/<uim_robot>/udm_manager
</ump_common>

9. Set the wasp loglevel to 5 and add a key for logsize and set it to 10000.

10. Click Apply, then Ok.

11. Activate the wasp probe. It should obtain a PID. It usually takes ~5-6 minutes to startup.

12. When the wasp probe is activated, the PID should display and remain the same. If it changes in a few minutes then the wasp probe is restarting.

13. Hit the OC url and login and check all OC webapps

Powered by Wolken Software