Hi All,

I found the TAO compatibility matrix, which states the latest HP ALM release being supported is 12.01

However, this matrix is last changed Jan 2015.

Can anybody confirm 12.01 is the lastest ALM version supported by TAO ?

Solution Manager 7.1 is completely configured in 2015, everything looks good till yesterday but today it is showing like SM_intern_ws user was locked. Can any one suggest me possible solution? or troubleshooting steps

Hello.

I configure CHARM in SM 7.2 SP2.

I received such error message:

No IBase component has been assigned to the document.

SMCR of SM 7.1 has PPF SMCR_ASSIGN_SOLMAN_IBASE.

I created  PPF ZMCR_ASSIGN_SOLMAN_IBASE. But this PPF isn't valid.

How to solve this problem?

Hi Experts,

I  adding my satellite system (Quality System) into Solution manager 7.1 , I have successfully add (push) trough SLD.

Now configuring my satellite system & i have successfully done 7 steps without any error. now i am on step 8 "configure automatically"

When i click on execute all button its giving me below error.

Error while calling Diagnostics setup web service

Error Detail:

SOAP:1.007 SRT: Unsupported xstream found: ("HTTP Code 401 : Unauthorized")

Please find below screen shot for your kind reference .

Please tell me what the issue & how i can resolve the same.

its very important for me.

Regards,

Sanjiv

Hi,

I am in the process of configuring technical monitoring in Solution manager

There are two alert types namely Red and Yellow

I want to add another alert type say RED_Critical which notifies multiple teams of very critical errors.

How do i achieve this

Hi experts,

Configured one urgent correction with multiple new status and sequence numbers. While importing to QA when there is an error, the status is not resetting to "In Development" but changing to the next status instead of going back.

When there is an error while importing into QA @ E0012 instead of resetting the status to E002 or E0017, even with error on the UC, the status value is being changed to E0018. Checked all the config, but could not find where the issue. Can you please help on where to find configuration to fix this issue.

thanks / Sandeep.

Hi all,

Users are deleting attachment from RFC and Change document. We want to restrict this. Kindly help me how to proceed further.

Thanks

Hi,

Any inputs on configuring Specific RFC's of types 3, G and T. for a Managed System.

I see we can configure RFC's via  BPMON but wanted to know if there is other way around to accomplish.

Solutionmanager we are @SP14

Thanks in advance.

Medha

I need to upgrade this Wily introscope in Linux platform. Kindly, provide the information about how to upgrade.

Hi friends facing some issues in solution manager configurations in basic and system Preparation.

Please can anyone guide me or provide me step by step document. I searched on web but not satisfied.

Regards,

Akshay

Part 1: Solution Manager 7.2 - Installation and Configuration - I - Installations

Part 2: Solution Manager 7.2 - Installation and Configuration - II - Configurations

Part 3: Solution Manager 7.2 - Installation and Configuration - III - Changes from 7.1 to 7.2

Part 4: Solution Manager 7.2 - Installation and Configuration - IV - Managed System Config - General Info

Part 5: Solution Manager 7.2 - Installation and Configuration - V - Managed System Config - ABAP System

Part 6: Solution Manager 7.2 - Installation and Configuration - VI - Managed System Config - HANA DB

Part 7: Solution Manager 7.2 - Installation and Configuration - VII - Managed System Config - Busines Objects

Part 8: Solution Manager 7.2 - Installation and Configuration - VIII - Managed System Config - Java System

This document is about the managed system configuration of a JAVA stack .

There are three main steps for the configuration. DAA Agent Installation, SLD registration and Managed System configurations.

1. Installation of Diagnostics Agent on all hosts

You must install Diagnostics Agent on the Server.

Detail description of the step can be found in the Installation of SMD Agent with SWPM section of Part 5

2. Connect Managed System to SLD

Create SLD Data Supplier for the solution manager system on SLD of the satellite Java system as seen below.

Use SLD Data Suppliers  function of nwa on satellite system and push the system data to all target SLDs as seen below.

After sending data you can check Solution Manager SLD and LMDB for the managed system.

3. Managed System Configuration of Java System

Run SOLMAN_SETUP and select Managed System Setup node.

Find your Java System as seen below and run Full Configuration Incl. Service Delivery EWA configuration.

There are 9 Steps for configuration.

1- Assign Product

In this step you define the product installed for the technical system.

Diagnostics-relevance is also set with product SAP NETWEAVER 7.4

2- Check Prerequisites

In this step, you check the prerequisites for the configuration of SAP Solution Manager automatically.

3- Assign Diagnostics Agent

In this step, you assign Diagnostics Agent to the server (host) on which managed system is running. You can also check the status and version of the DAA.

4- Enter System Parameters

In this step, you specify the system parameters required to configure the managed system, which depend on the type of the managed system.

You specify the Introscope EM, Managed System Load Balancer Host and port. And enable EWA alert inbox and system recommendations.

You use the created DB user in DB Parameters section and by saving you setup DBA Cockpit and DB extractors.

You also maintain message server host and port and a user for Java Parameters as seen below.

5- Enter Landscape Parameters

In this step, you can verify and add landscape parameters.

6- Maintain Users

In this step you create or update dialog or technical users and assign roles to those users.

7- Finalize Configuration

There are automatic and manual activities that needs to be fulfilled in Final Configuration step. You can leave postponed activities as is. For manual activities go to each transactioon or URL to perform the activity. Click display to get more help.

8- Check Configuration

In this step, you automatically check whether the system is configured correctly, and you update the statuses in the overview of the Managed Systems Configuration.

9- Complete

This step provides an overview of the steps that have been performed in this scenario, including information about the users who made the changes, and the status of each step.

This is the end of the configuration.

Managed System Configuration of PI System (Dual Stack) is coming next.

Thanks for your interests.

.

Part 1: Solution Manager 7.2 - Installation and Configuration - I - Installations

Part 2: Solution Manager 7.2 - Installation and Configuration - II - Configurations

Part 3: Solution Manager 7.2 - Installation and Configuration - III - Changes from 7.1 to 7.2

Part 4: Solution Manager 7.2 - Installation and Configuration - IV - Managed System Config - General Info

Part 5: Solution Manager 7.2 - Installation and Configuration - V - Managed System Config - ABAP System

Part 6: Solution Manager 7.2 - Installation and Configuration - VI - Managed System Config - HANA DB

Part 7: Solution Manager 7.2 - Installation and Configuration - VII - Managed System Config - Busines Objects

Part 8: Solution Manager 7.2 - Installation and Configuration - VIII - Managed System Config - Java System

This document is about the Managed System Configuration of a HANA DB system.

I did managed system configuration of HANA DB system according to below link on Solution Manager 7.1 and used the same link for 7.2 version, too.

Managed System Setup of HANA in SAP Solution Manager 7.1

You will find short descriptions and practice of the configuration below. For more details and explanations use the wiki link.

Here are the steps performed for Managed System Configuration of HANA DB System.

Install Diagnostics Agent on HANA host

The first step is to install the Diagnostics Agent on the HANA servers.

You need latest SWPM and the Kernel DVDs for Linux. Also latest SAPEXE, SAPHOSTAGENT, SAPJVM and SAPDIAGNOSTICSAGENT SAR files as seen below.

Download them and transfer them to your HANA DB server.

I used MobaXterm tool for connecting to server and running sapinst.

If prerequisies are met there won't be any "Condition not met" cases and you will install DAA on your HANA DB server successfully.

The parameters screens can be seen in previous blogs so I will not put them also in this document. If you want to have your agent's SP levels latest you should enter the current archive locations as seen above in the last step of parameter entry.

After the istallation DAA Instance is registered to your Solution Manager. You can check it using the URL http://<solmanjavahostname>:<portnumber>/smd/AgentAdmin

Sometimes the servername of your DAA isn't seen on the list. That time you can run below script to correct the name of your server.

Run the script smdsetup.bat changeservername servername:"evehrprd" in script folder as seen below.

Checking and Updating SAP Host Agent Version

When you install DAA instance SAPHOSTAGENT is also installed. Check the version using "saphostexec -version" script. You can see details in previous blogs of the series.

Since I have chosen the latest SAPHOSTAGENT*.SAR when I am installing DAA I donot need to upgrade Host Agent.

Creating Monitoring User in HANA

For Solution Manager connection you should create a HANA DB monitoring user.

Use HANA Studio to connect to DB and create the user and assign the roles MONITORING and PUBLIC to the user.

Use below SQL commands to make password of this user doesn’t have to be changed anymore.

ALTER USER <SID>MONITOR DISABLE PASSWORD LIFETIME;

CONNECT HRPMONITOR PASSWORD <password>;

Configure HDB User Store for SAP Host Agent

Login to system using <sid>adm.

Run below command to enable the SAP Host Agent to connect to HANA and can receive process information.

/usr/sap/hdbclient/hdbuserstore SET <SID>SAPDBCTRL <hana-master-host>:3<Sys-No>15 <SID>MONITOR password

Check the setup running below command:

/usr/sap/hdbclient/hdbuserstore LIST <SID>SAPDBCTRL

To check the setup there are some more commands that you can run. You can see the details in the mentioned wiki link at the top.

Register HANADB in SLD

Use HANA Platform Lifecycle Manager to register HANA in SLD:

Enter the SLD connection parameters as seen below.

And execute the registration process.

You can find HANA in the SLD of Solution Manager under Administration -> Content Maintenance -> HANA Database System:

You can also use HDBLCM tool to register HANA DB to SLD. You can see the details in wiki page.

Install HANA client software on SAP Solution Manager

If there is no HANA DB Client software installed on your Solution Manager before, download the client software and install it on your Solution Manager system. You can check the note 1597627 - SAP HANA connection for more.

Set DB parameter on Solution Manager

• Add X:\usr\sap\hdbclient path to the environment variable of Solution Manager sidadm user.
• Add "dbs/hdb/connect_property = DISTRIBUTION=OFF" parameter in the SAP Solution Manager DEFAULT.PFL profile.
• Restart Solution Manager System after these updates.

Check LMDB

Call LMDB transaction on your Solution Manager System, select your HANA DB System.

Check that product version is supplied.

Check the SAP HANA DATABASE software is marked as Installed on Instance

Check that all of the HANA services can be seen under Technical Instances

From LMDB initial screen select your ABAP system and check that the DB of your system is your HANA DB.

Run Managed System Setup for HANA

From SOLMAN_SETUP transaction you choose your HANA DB system and select configure system as seen below.

1- Assign Product

In this step you define the product installed for the technical system.

Diagnostics-relevance is also set with product SAP HANA PLATFORM EDIT. 1.0.

2- Check Prerequisites

In this step, you check the prerequisites for the configuration of SAP Solution Manager automatically.

3- Assign Diagnostics Agent

In this step, you assign Diagnostics Agents to each server (host) on which managed systems are running. You can also check the status and version of the DAA.

4- Enter System Parameters

In this step, you specify the system parameters required to configure the managed system, which depend on the type of the managed system.

You specify the Introscope EM, Managed System Load Balancer Host and port. And enable EWA alert inbox and system recommendations.

You use the created HANA DB user in DB Parameters section and by saving you setup DBA Cockpit and DB extractors.

5- Enter Landscape Parameters

In this step, you can verify and add landscape parameters. Verify the landscape parameters carefully, to avoid time-consuming error-handling.

6- Finalize Configuration

There are automatic and manual activities that needs to be fulfilled in Final Configuration step. You can leave postponed activities as is. Fot manual activities got to each transactioon or URL to perform the activity.

7- Check Configuration

In this step, you automatically check whether the system is configured correctly, and you update the statuses in the overview of the Managed Systems Configuration.

8- Complete

This step provides an overview of the steps that have been performed in this scenario, including information about the users who made the changes, and the status of each step.

Managed System Configuration of a Busines Objects Cluster is coming next.

Thanks for your interests.

.

Part 1: Solution Manager 7.2 - Installation and Configuration - I - Installations

Part 2: Solution Manager 7.2 - Installation and Configuration - II - Configurations

Part 3: Solution Manager 7.2 - Installation and Configuration - III - Changes from 7.1 to 7.2

Part 4: Solution Manager 7.2 - Installation and Configuration - IV - Managed System Config - General Info

Part 5: Solution Manager 7.2 - Installation and Configuration - V - Managed System Config - ABAP System

Part 6: Solution Manager 7.2 - Installation and Configuration - VI - Managed System Config - HANA DB

Part 7: Solution Manager 7.2 - Installation and Configuration - VII - Managed System Config - Busines Objects

Part 8: Solution Manager 7.2 - Installation and Configuration - VIII - Managed System Config - Java System

Manage System Configuration for a Business Objects System

There is no dedicated note or wiki to explain the setup of the BOE systems in Solution Manager 7.2 yet.

I asked this to SAP also to be sure about the configuration.

They told me that as it is mentioned in the note 2248724 - Root Cause Analysis in SAP Solution Manager 7.2  that SBOP BI PLATFORM 4.0 and 4.1 are supported in the Solution Manager 7.20. So I coud be able to perform all the configuration following the note 1975394 - SolMan 7.1: Managed Sys Setup - BI Platform 4.1 ignoring the steps to upload the extractors templates which are valid for Solman 7.10 only.

The SAP notes and wiki pages that I've read;

2248724 - Root Cause Analysis in SAP Solution Manager 7.2

1472465 - SAP Solution Manager 7.1 and 7.2 - System Landscape Setup Guide

2229953 - Solution Manager 7.2 SP Stack 01: recommended corrections

Maintenance of Product in the System Landscape

Managed System Setup of BOE 4.0 system in Solman 7.1

1975394 - SolMan 7.1: Managed Sys Setup - BI Platform 4.1

2137275 - AC Tool release NOTE

2164192 - KPIScript.jar && Coarsegrain.jar release note

1722874 - Troubleshooting Solution Manager Root Cause Analysis for BOE

Configurations Steps according to

Managed System Setup of BOE 4.0 system in Solman 7.1

First of all I followed the SAP Note 1975394 - SolMan 7.1: Managed Sys Setup - BI Platform 4.1 for the latest up to date information for SAP BOE 4.1. And did the configurations in this note as below.

1. Configuration of Managed System

Ignored this step which is valid for Solman 7.10 only.

2. Naming Convention for the SIDs

Decided to name SIDs of cluster and tomcat application servers as BOP_BOE and BOP_WAS.

3. Installation or upgrade of Wily introscope

Minimum version of SAP Introscope package is version 9 is needed.

Our Wily version was 9.7. So I didnot upgrade it.

If you want to upgrate your wily package you can find detailed information about the installation of Introscope Enterprise Manager in blog Part 2.

4. Configuration of Database Monitoring for Customer Databases

Refer to SAP Note 1265134 as an entry point for the configuration steps required.

5. Using the setup automation tool

Details are in below "Auto configure using AC tool" section.

6-11.  These steps are done by AC Tool automatically.

12 -13. These steps are for aolder versions of Solution Manager.  (only for solman lower than SP9 and the later one is for solman lower than SP11)

14. Replace "coarsegrain.jar" and "KPIScript.jar" on each host where BOE 4.X running

The latest version of these two jar files can be downloaded from Note 2164192.

2164192 - KPIScript.jar & Coarsegrain.jar release note

Summary:

KPIScript.jar and Coarsegrain.jar are used for BOE related monitoring functions. Please use the newest version, you can choose update the BI version or download from this Note and replace the old ones in the related folder.

Please download the latest version KPIScript.jar and Coarsegrain.jar from attachment.

The default path of these two jar files is (for Windows): %BOE_DIR%\SAP BusinessObjects Enterprise XI 4.0\java\lib\

15. Delete old logs for BOE4

The large number of BOE logs may cause 100% CPU consumption on the BOE host. Please delete old logs under BO dir regularly.

For troubleshooting issues with BOE managed system setup also refer to the note 1722874 - Troubleshooting Solution Manager Root Cause Analysis for BOE

Installation of Diagnostics Agent on all hosts

You must install Diagnostics Agents on BOE and Tomcat Servers.

Detail description of the step can be found in the Installation of SMD Agent with SWPM section of Part 5

Auto configure using AC tool

*Report BOE SLD data to SLD - This step is done by tool automaticallay

*Report BOE Web Application Server SLD data to SLD - This step is done by tool automaticallay

Reporting of BOE and WAS to SLD steps are performed by AC Tool. And the details of running ACTool is done according to the note

2137275 - AC Tool release NOTE

   Get the tool:

   Download URL: https://mdocs.sap.com/mcm/public/v1/open?shr=yuLDxZ8ZcJuCEUDfHeqahLr6tlMRpynsLfh0gMYe4vQ

   Download Pass: 12345

Use the guide ACTool User Guide.pdf

5 BOE Step by Step

5.2 Structure of file tree must be like below.

5.3 conf/boe.properties Preparation

Update boe.properties config file under conf folder as seen below. For details you can check the main wiki.

This file is used by the tool for configuration of BOE and Tomcat.

boe.home = E:\SAP BusinessObjects

boe.system = SAPBOPRD

boe.user = Administrator

boe.password = <YourPassword>

boe.os.user = <YourOSUuser>

saphostagent.install = false

saphostagent.install.path = C:\Program Files\SAP\hostctrl

saphostagent.password = <YourPassword>

sld.connectkey.replace = true

sld.server.host = solman.mycomp.com

sld.server.port = 50200

sld.server.user = SLD_DS_SID

sld.server.password = <SLD_DS_SID_UserPassword>

sld.server.https = n

boe.cmc.introscope.enable = true

boe.cmc.introscope.host = solman.mycomp.com

boe.cmc.introscope.port = 6001

boe.cmc.introscope.type = TCP

boe.cmc.ncs.level = 10

boe.cmc.smdagent.host = localhost

boe.cmc.smdagent.port = 6404

tomcat.service.name = BOEXI40Tomcat

tomcat.service.port = 8080

tomcat.http = http

tomcat.home = E:\SAP BusinessObjects\tomcat

tomcat.running.mode.WindowsService = true

tomcat.hostname.sld.url = localhost

wily.javaagent.install = true

wily.javaagent.installfolder = E:\usr\sap\CCMS

wily.javaagent.folder =

wily.EM.host = solman.mycomp.com

wily.EM.port = 6001

wily.EM.webport = 8081

jmx.user = smdAgentRole

jmx.password = <YourPassword>

jmx.port = 9004

jmx.solman.set = true

sld.warfile.replace = true

solman.version = other

smdagent.path = E:\usr\sap\DAA\SMDA98

sld.system.longSID = BOP_WAS

tomcat.sld.manualtransfer = true

jvmmond.install.path = E:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin

jvmmond.port = 1099

jvmmond.password = <YourPassword>

console.verbose = true

boe.node.restart = false

boe.service.name = BOEXI40SIASAPBOPRD

smdagent.windows.servicename = SAPDAA_98

5.7 Run ACTool with Interactive User Input

With an admin privilidged user run the batch file as below. It will start the tool and ask your selections.

After selecting SAP BI PLATFORM 4.X you select Execute and start configurations of all steps.

If your BOE and Tomcat servers are different run BOE steps on BOE Server and Tomcat Steps on WAS Server.

BOE and Tomcat restart are needed.

You could have problem after configurations and restarts. You can check below links for troubleshooting.

http://wiki.scn.sap.com/wiki/display/SMSETUP/Managed+System+Setup+of+Apache+Tomcat+System+in+Solman+7.1

1975394 - SolMan 7.1: Managed Sys Setup - BI Platform 4.1

E:\BOCD\actool>run_actool.bat

using JVM=E:\SAP BusinessObjects\\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sapjvm\bin

******************************************************************************

*    Auto Configurantion Tool for SAP products 2.23.0

******************************************************************************

AC Tool supports the configuration for the follwoing products:

-----------------------------------------------------------

1. SAP DATA SERVICES 4.X

2. SAP BI PLATFORM 4.X

------------------------------------------------------------

Please choose a product to config---

[ --- Input the product id 1 - 2, only single number supported! ]

[ --- Type 'quit' to exit from this application! ]

Please input:2

1. Execute

2. Check

Please choose the action you want to perform---

[ --- Please input number 1 - 2, only single number supported. ]

[ --- Type 'back' to go back to products selection. ]

[ --- Type 'quit' to exit from this application. ]

Please input:1

*****************************************************************

Configuration for product SAP BI PLATFORM  4.X

*****************************************************************

The configuration includes the following steps, you may multiple choose the steps to execute or check:

--------------------------------------------------------------------------------------

1. BOE - BI 4.0 Note 1653689 Step 6.1 - Enable SLD support for BO cluster

2. BOE - BI 4.0 Note 1653689 Step 8 - Enable Introscope for Java components

3. BOE - BI 4.0 Note 1653689 Step 9 - Enable Introscope for C++ components

4. BOE - BI 4.0 Note 1653689 Step 10 - Enable Saposcol process monitoring

5. BOE - BI 4.0 Note 1653689 Step 11 - Configure step of BOE 4.0(SP level lower than SP3)

8. BOE - Enable CSJNI - Update configurations of cs.cfg

9. BOE - Enable CSJNI - Update configurations of IntroscopeAgent_CSJNI.profile

10. BOE - Enable TDA service(BOE node need to be restarted.)

12. Tomcat Wiki Step 3 (BI 4.0 Note 1653689 Step 7)- Install Introscope Agent (Tomcat restart needed)

13. Tomcat Wiki Step 4.1 - Configure JMX (Tomcat restart needed)

14. Tomcat Wiki Step 4.2 - Configure JVM GC log (Tomcat restart needed)

15. Tomcat Wiki Step 4.3 - Check Tomcat logging (Tomcat restart needed)

16. Tomcat Wiki Step 5 (BI 4.0 Note 1653689 Step 6.2) - Install and run SLD Data Supplier

17. Tomcat - Enable TDA for Tomcat

18. TDA - Start Jvmmond.exe as OS service

-------------------------------------------------------------------------------------

Please choose the steps to configure---

[ --- Type step IDs(1 to 18) to execute or check. ]

[ --- For multiple selection please split the step number by ','. ]

[ --- Press ENTER directly to configure all steps. ]

[ --- Type 'back' to get back to Action selection. ]

[ --- Type 'quit' to exit from this application. ]

When you run "2. Check" you must see all steps are successful as seen in below picture in order to continue to the next step.

You can run the FAILURE steps to get SUCCESS after correcting the errors.  

5.10 Impact of All Steps on Managed System and How to Check

In this list you can see all steps, operations and final result checks.

Check the Technical System for BOE in LMDB

Run SOLMAN_SETUP and check the BOE System's properties from Managed System Configurations menu.

In Technical Systems Tab select your BOE System, select System Operations and Maintain System.

Then change Extended SID to BOP_BOE as seen below.

Make sure the product version list here are set with diagnostic flag as seen below after Setting Diagnostics-Relevance

Check Applications Servers and Central Management Servers on Technical Instances node. Also check software component versions as seen below.

And host information.

Setup of the BOE Database system

You can check below link for details.

How to perform the Database configuration for BOE 4.0 and 4.1 in Solman 7.10

You run LMDB and select technical System BOP_BOE.

Edit the system Database property as seen below and assign the DB of the BOE system.

Managed System setup for BOE 4.0

In SOLMAN_SETUP Managed System Configuration node you select the BOE system and select Configure System and Full Configuration Incl. for Service Delivery/EWA.

There are 8 steps to complete managed system configuration. I will share the screenshots of some of the steps below.

In step #1 "Assign Product"  SBOP BI PLATFORM 4.1 is assigned to BOP_BOE technical system.

In step #2 "Check Prerequisites" prerequisites are checked.

In step #3 "Assign Diagnostics Agent" the DAA agent is found and assigned to the BOP_BOE system.

In step #4 "Enter System Parameters" the system parameters according to system type is entered as seen below. DB parameters are provided. DB parameters are done after "Setup of the BOE Database System".

In step #5 "Enter Landscape Parameters" the landscape parameters are verified and provided. Mostly the default ones are saved as seen below.

In step #6 "Finalize Configuration" the automatic configuration steps like extracters setup, Introscope Host Adapter, Apply Settings for EWA and System Recommendations are executed.

In step #7 "Check Configuration" the configuration is checked and System Status is refreshed.

In step #8 "Complete" you can see all steps statuses and click Finish.

Configuration for BOP_BOE is done.

Managed System setup for Web Application Server with BOE 4.0 Web Application (Apache Tomcat)

Managed System Config of BOP_WAS is very similar to BOP_BOE. It has also 8 step to complete the configuration.

You select BOP_WAS technical system and start configuration.

Step #1 "Assign Product"  , step #2 "Check Prerequisites" and step #3 "Assign Diagnostics Agent" are like BOP_BOE system.

In step #4 "Enter System Parameters" you enter parameters as seen below.

In step #5 "Enter Landscape Parameters" the landscape parameters for BOP_WAS ave verified and provided as seen below.

In step #6 "Finalize Configuration" and In step #7 "Check Configuration" are similar to BOP_BOE.

In step #8 "Complete" you can see all steps statuses as seen below and click Finish.

Configuration for BOP_WAS is done.

Wily Introscope setup for BOE 4.0

For detailed information and follow the main wiki and the note 1540591 - Wily Introscope Setup for SAP BOE 4.X for Introscope configuration.

I will put some screenshots from my configuration.

I configured the Wily Introscope Java agent and SMD Agent configurations in CMC as seen below. (For details check BO installation guide's "To configure CA Wily Introscope Agent post installation" and "To configure SMD Agent post installation" sections)

Since our Introscope EM version is 9.7 I used the note 1579474 - Management Modules for Introscope delivered by SAP for deploying extra modules to EM as seen below.

<EM folder>/sap/extra_modules to deploy and then to <EM folder>/config/modules.

<EM folder>/Sap/extra_scripts to <EM folder>/scripts folder

Changed Java VM parameters of EM according to guide CA_Interescope_v97.pdf and restarted Introscope EM.

For the configuration of Introscope Java Agent profile for BOE Java Web Application I used ISAgentBOE40WebApp.pdf document attached to the mentioned note and changed the profile as seen below.

You can use the note 1438005 - Introscope Agent for Apache Tomcat and the document attached to this note for detail information.

Thread Dump Analysis Supportability

I didnot configure this section. In need can be done according to the note 1608714.

Problems and Solutions

When I get EWA report there were missing data and I investigated the cause.

There were problems on extractors and some infocubes and bi objects were not active on my Solution Manager BW.

I checked below documents for solutions.

How to Activate BW InfoCubes when Extractors Fail in the Extractor Framework

1722874 - Troubleshooting Solution Manager Root Cause Analysis for BOE

This is the end of the configuration.

Managed System Configuration of a Java System is coming next.

Thanks for your interests.

.

Hi Gurus,

We are in an implementation project in which, we would like to use SOLMAN 7.2 HANA on S/4 HANA implementation.

The methodology, we are using is Best Practices Activation.

We will be using Template Project methodology which will be rolled out globally.

Kindly help me in understanding following...

1. How the process should be done ? Means, in 7.1 we used to create a project and all the configuration used to get transported through single TR.

Will it happen in the same way in SOLMAN 7.2 ?

2. Apart from Servers and other hardware requirements, what all are the technical requirements for this approach of implementation ?

Will it be the same manner, we used to do for SOLMAN 7.1 ?

Please guide.

Thanks,

Hi All,

I am performing wily introscope configuration manual steps.

After the configuration i restart the java instance and the system get appear in webview.

When i expand the node of the system in webview , it just showing me the SAP NetWeaver but not the SAP HOST node.

Then i addded one more parameter com.sap.hostagnt.enable=true in IntroscopeAgent.Profile file of managed system and restart the java instance.

But no luck.

Please suggest.

With Reegars

Hi guys,

I have issue regarding missing some incidents, which where created recently few days ago.

Range of incidents from *1873-*1880 are missing.

Do you know why this happened?

Hi Friends,

Thanks for taking out time.

We are looking for project migration between 2 landscapes.

Main purpose of the project migration is for document migration.

We are looking to migrate around 18000 documents from one particular landscape to to Global SOLMAN.

In one particular project in source solman system, there are around 20k documents.

I got to know that we can perform project migration between 2 landscape systems.

Following are the steps which I am aware of:

1. Source System: Click on Transport button by the selecting the project & TR gets included and check the include all documents button

2. Once it is done release the TR from Source system

3. Inform the our local basis(cordillera) team about the TR for copying the co file and data file for the TR

4. Once copied the local basis team is informed about this.They will create a external TR by using this co file and data file

5. Once done import the changes

Requesting your valuable inputs for the project migration between 2 landscape systems.

Thanks & Regards,

Solman Starter

Hi All,

I would like to monitor batch jobs in Solution manager without setting up the Business process, found that there are two ways of doing the same.

1. CCMS batch controlling

2. Techinical Monitoring -> Job Monitoring.

However I would like to know what are the pros and cons of these two approaches and what is the best practice.

Best Regards

Manoj

hi all

we are currently using 7.1 for template project concept to handle the global roll outs. we have templates defined within template projects.

these templates will be available in " Scope " tab when the creating the implementation projects. so the implementation projects will have all the documents from template projects ( business process documents , test cases and training materials )

Now we need to replicate the whole process in 7.2 since the transport of project is not supported in 7.2 ( we can't transport 7.1 projects in to 7.2 unless we do a upgrade to 7.2. )

7.2 is completely based on solutions for documentation

i need to understand in 7.2 how to implement the template project concept using solutions in 7.2.

Any help is highly appreciated

Thanks

Sol man

Hi everyone,

I have problem with copying excel file xlsx in test case in Test Management (SOLMAN). I already solved problem with MIME Type according to Note 1062725, but when try copy document I get error message (see figure below).

MIME type settings:

I tried insert new excel documents xlsx again a generate new test plan. We have newest Solution Manager 7.1 SP8 with updated central notes. I tried compare problem in other Solution Managers (SP 05, SP 06) and it is still same. 

Could you anybody help me please?

Thx, by