Random issues faced during Business Process Monitoring (BPM) configuration on Solman 7.2

In this blog i will try to note some issues I faced during configuration of Business Process Operations. Issues are peculiar and might not be relevant for everyone.

A. Issue with Solman_setup -> Basic Configuration -> Activation of BW content (For UPL, RCA…)

During this i faced issue activating BW content. Error is as below. No other logs in SLG1 or ST22 in the system.

Solution: I had to restore the logical BW system from RSA1 to fix the issue.

RSA1 -> Modeling -> Source System -> BW -> Logical System

Ran activation again from Solman_Setup and everything went fine.

Probable Cause: We did a client copy to create a new client and something went wrong while running BDLS.

B. Issue with Solman_Setup -> Basic BPO Configuration -> Configure Solution Manager -> Configure Automatically

Activity “Activate BW Cubes” runs into error “BW content not activated”

Solution: Activated the related cubes ( 0SM_BPM, 0SM_BPMRH, OSM_BPMRD) manually from RSA1 as suggested by SAP Note 2434326.

C. Business process monitoring tile is not visible in Solman_workcenter.

Follow the below SAP Note:

2338589 – Troubleshooting for Blank Business Process Monitoring workcenter applications in SAP Solution Manager 7.2

1. Check and ensure that the user profile used has the following roles applied:
   i.    Run transaction SU01 and display the user profile.
   ii.   Navigate to the Roles tab and confirm that the following roles have been applied:
   –  SAP_SMWORK_BPO
   –  SAP_SMWORK_SM_ADMIN
2. Check and confirm that the necessary UI5 services are active:
   i.    Run transaction SICF.
   ii.   Enter /sap/bc/ui5_ui5 within the service path field and select Execute.
   iii.  Confirm that the following services are active:
   –  sap_bpm_alrep
   –  sap_bpm_hier
   –  sap_bpm_search
3. Clear the system cache and internet browser cache:
   i.    Complete all steps contained in the following SAP KBA:
   2319491 – How to clean up the cache after applying changes that affect SAP Fiori apps.
   ii.   Delete the browsing history of the workstation’s internet browser.

 

Important Notes:

2320230 – How to Confirm “Activate BPMon Services” in Solution Manager 7.2’s BPO Configuration

2491759 – Migration for Business Process Monitoring from Solution Manager 7.1 to 7.2

 

Configure VNC Or Xrdp server on a RHEL VM

On a newly created RHEL VM/EC2 instance graphical interface is not normally configured.

In the below blog, we will discuss about configuring the VNC server on a RHEL machine.

XRDP configuration is discussed at the end of this blog post.

Elevate your user with root privileges.

Install the required packages using below command:

yum install tigervnc-server -y

Set VNC password for the client sessions

vncpasswd

Make a note of password used.

Start a VNC session.

Note that you session number is 1.

Now to try to connect to your VNC session using a VNC client tool from you windows machine.

VNC uses port 59XX (where XX is the desktop instance number). In above case my instance number will be 5901. 

Make sure you have allowed this port on your cloud inbound security rule and also on the Linux firewall. 

After these changes, if you get a blank screen when connected to the session, check the run level of your system and follow the below steps:

GUI interface is not enabled in run level 3. Switch to run level 5 to enable the GUI mode.

You will need a server reboot for this change to take effect.

check the run level again after the reboot.

Now install the GUI server with the below command:

Once done you should be able to connect to the GUI screen using VNC viewer.

To configure XRDP, perform the below steps:

Download the RPM packages:

# rpm -Uvh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm

Note: Always use the updated URL.

Install the XRDP packages:

# yum install xrdp -y

Start XRDP service and make it persistent:

#service xrdp start

#chkconfig xrdp on

XRDP uses port 3389. 

Make sure you have allowed this port on your cloud inbound security rule and also on the Linux firewall.

Now you should be able to connect to your Linux machine using Microsoft Windows Terminal Services Client (MSTSC) from your windows machine.

Additional Notes for Ubuntu:

If you are not able to connect with XRDP, Execute following commands on Ubuntu:

Install xfce4

#sudo apt-get install xfce4

Add following lines to users .xsession file under home directory and comment out the rest of the line.

xfce4-session